Dell Powerconnect J Ex8216 Quick Reference Guide Software For JUNOS Version 10.3

Dell-Powerconnect-J-Ex8208-Quick-Reference-Guide-114078 dell-powerconnect-j-ex8208-quick-reference-guide-114078

Dell-Powerconnect-J-Srx240-Quick-Reference-Guide-114565 dell-powerconnect-j-srx240-quick-reference-guide-114565

Dell-Powerconnect-J-Srx210-Quick-Reference-Guide-114560 dell-powerconnect-j-srx210-quick-reference-guide-114560

2014-11-13

: Dell Dell-Powerconnect-J-Ex8216-Quick-Reference-Guide-114083 dell-powerconnect-j-ex8216-quick-reference-guide-114083 dell pdf

Open the PDF directly: View PDF PDF.
Page Count: 3660

DownloadDell Dell-Powerconnect-J-Ex8216-Quick-Reference-Guide- Software Guide For JUNOS Version 10.3  Dell-powerconnect-j-ex8216-quick-reference-guide
Open PDF In BrowserView PDF
Dell PowerConnect J-Series
Ethernet Switch
Complete Software Guide for Junos OS

Published: 2010-11-10

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 , Junos , NetScreen , ScreenOS , and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in the
United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE™ are trademarks of Juniper Networks, Inc.
All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks 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
© Copyright Dell, Inc. , 2010. All rights reserved.
Writing: Appumon Joseph, Aviva Garrett, Bhargava Y P, Brian Deutscher, Brooke Doverspike, Carolyn Harding, Greg Houde, Hareesh Kumar
K N, Hemraj Rao S, Janet Bein, Katherine Kearns, Keldyn West, Praveen G R, Regina Roman, Shikha Kalra, Tim Harrington, Vinita Kurup
Editing: Cindy Martin, Rajan V K, Taffy Everts, Chanchal Agrawal
Illustration: Faith Bradford Brown
Cover Design: Christine Nay
Revision History
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.
SOFTWARE LICENSE
The terms and conditions for using this software are described in the software license contained in the acknowledgment to your purchase
order or, to the extent applicable, to any reseller agreement or end-user purchase agreement executed between you and Juniper Networks.
By using this software, you indicate that you understand and agree to be bound by those terms and conditions.

ii

Generally speaking, the software license restricts the manner in which you are permitted to use the software and may contain prohibitions
against certain uses. The software license may state conditions under which the license is automatically terminated. You should consult
the license for further details.
For complete product documentation, please see the Juniper Networks Web site at www.juniper.net/techpubs.

END USER LICENSE AGREEMENT
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.
BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred
to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades
and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units
for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access
Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space
and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines
(e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single
chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limits to Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent
users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of
separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput,
performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use
of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software.
Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not
extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees
not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized

iii

copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software, in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software or any product
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold in the secondhand market; (f) use any ‘locked’ or key-restricted feature, function, service, application, operation, or capability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly
provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to
the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance
of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statement that accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
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

iv

restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without
an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer
with the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party
software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent
portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such
portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper
will make such source code portions (including Juniper 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxix
How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxix
Downloading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxx
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxx
Repair and Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxxi
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxxi

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 . . . . . . . . . . . . . . . . . . . . . . 13
Layer 3 Protocols Not Supported on J-EX Series Switches . . . . . . . . . . . . . . . . . . . 14
Security Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . . 16
High Availability Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . . 18
VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Graceful Protocol Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Redundant Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Virtual Chassis Software Upgrade and Failover Features . . . . . . . . . . . . . . . . 20
Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . . . . . 22
Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . . . 22
Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 2

Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
J-EX4200 Switches Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
J-EX4200 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Uplink Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Power over Ethernet (PoE) Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
J-EX4200 Switch Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
J-EX8208 Switch Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chassis Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Routing Engines and Switch Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
J-EX8216 Switch Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chassis Physical Specifications, LCD Panel, and Midplane . . . . . . . . . . . . . . 30

vii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Routing Engines and Switch Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Part 2

Complete Software Configuration Statement Hierarchy

Chapter 3

Complete Software Configuration Statement Hierarchy . . . . . . . . . . . . . . . . 37
[edit access] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 37
[edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 38
[edit class-of-service] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . 38
[edit ethernet-switching-options] Configuration Statement Hierarchy . . . . . . . . 40
[edit firewall] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 42
[edit forwarding-options] Configuration Statement Hierarchy . . . . . . . . . . . . . . . 43
[edit interfaces] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 44
[edit poe] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 48
[edit routing-instances] Configuration Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 55
[edit snmp] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 55
[edit virtual-chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . 55
[edit vlans] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Part 3

Software Installation

Chapter 4

Software Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Understanding Software Installation on J-EX Series Switches . . . . . . . . . . . . 61
Overview of the Software Installation Process . . . . . . . . . . . . . . . . . . . . . 61
Software Package Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Installing Software on a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Installing Software on J-EX8200 Switches with Redundant Routing
Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Installing Software Using Automatic Software Download . . . . . . . . . . . 63
Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Junos OS Package Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Understanding System Snapshot on J-EX Series Switches . . . . . . . . . . . . . . 64
Licenses Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Understanding Software Licenses for the J-EX Series Switch . . . . . . . . . . . . 65
Features Requiring a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
License Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
License Key Components for the J-EX Series Switch . . . . . . . . . . . . . . . . . . . 66

Chapter 5

Installing Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Downloading Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Preparing the Switch for the Software Installation . . . . . . . . . . . . . . . . . . . . . 72
Installing Software on the Backup Routing Engine . . . . . . . . . . . . . . . . . . . . . 73

viii

Table of Contents

Installing Software on the Default Master Routing Engine . . . . . . . . . . . . . . . 74
Returning Routing Control to the Default Master Routing Engine
(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Installing Software on J-EX Series Switches (J-Web Procedure) . . . . . . . . . . . . . . 75
Installing Software Upgrades from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Installing Software Upgrades by Uploading Files . . . . . . . . . . . . . . . . . . . . . . . 77
Rebooting or Halting the J-EX Series Switch (J-Web Procedure) . . . . . . . . . . . . . . 77

Chapter 6

Booting the Switch, Upgrading Software, and Managing Licenses . . . . . . . 79
Booting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Booting a J-EX Series Switch Using a Software Package Stored on a USB
Flash Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Creating a Snapshot and Using It to Boot a J-EX Series Switch . . . . . . . . . . . 80
Creating a Snapshot on a USB Flash Drive and Using It to Boot the
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Creating a Snapshot on an Internal Flash Drive and Using it to Boot the
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Upgrading Software Using Automatic Software Download on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Managing Licenses for the J-EX Series Switch (CLI Procedure) . . . . . . . . . . . 83
Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Saving License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Managing Licenses for the J-EX Series Switch (J-Web Procedure) . . . . . . . . 84
Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Displaying License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Downloading Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Chapter 7

Verifying Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Verifying That Automatic Software Download Is Working Correctly . . . . . . . 87
Verifying That a System Snapshot Was Created on a J-EX Series Switch . . . 88
Monitoring Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Monitoring Licenses for the J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . 88
Displaying Installed Licenses and License Usage Details . . . . . . . . . . . . 89
Displaying Installed License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 8

Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Recovering from a Failed Software Upgrade on a J-EX Series Switch . . . . . . 91
Rebooting from the Inactive Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 9

Configuration Statements for Software Installation . . . . . . . . . . . . . . . . . . . 95
[edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 95
auto-image-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

ix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 10

Operational Mode Commands for Software Installation . . . . . . . . . . . . . . . 97
request system license add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
request system license delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
request system license save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
request system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
request system software add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
request system software delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
request system software rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
request system software validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
show system autoinstallation status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
show system boot-messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
show system license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
show system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Part 4

User Interfaces

Chapter 11

User Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
User Interfaces—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
CLI User Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
CLI Help and Command Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
CLI Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
J-Web User Interface for J-EX Series Switches Overview . . . . . . . . . . . . . . . 129
Understanding J-Web Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Understanding J-Web User Interface Sessions . . . . . . . . . . . . . . . . . . . . . . . 133

Chapter 12

Using the Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Using the CLI Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Starting the J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Chapter 13

Operational Mode Commands for User Interfaces . . . . . . . . . . . . . . . . . . . . 137
set cli complete-on-space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
set cli directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
set cli idle-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
set cli prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
set cli restart-on-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
set cli screen-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
set cli screen-width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
set cli terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
set cli timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
show cli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
show cli authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
show cli directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
show cli history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
start shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

x

Table of Contents

Part 5

Junos OS for J-EX Series Switches System Setup

Chapter 14

System Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Junos OS—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
J-EX Series Switch Software Features Overview . . . . . . . . . . . . . . . . . . . . . . 157
Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . 158
Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . 158
Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Chapter 15

Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Connecting and Configuring a J-EX Series Switch (CLI Procedure) . . . . . . . . . . . 161
Connecting and Configuring a J-EX Series Switch (J-Web Procedure) . . . . . . . . 163
Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) . . . . . . . . . 166
Disabling or Enabling Menus and Menu Options on the LCD Panel . . . . . . . 166
Configuring a Custom Display Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuring Date and Time for the J-EX Series Switch (J-Web Procedure) . . . . . 167
Configuring System Identity for a J-EX Series Switch (J-Web Procedure) . . . . . . 168

Chapter 16

Configuration Statements for System Setup . . . . . . . . . . . . . . . . . . . . . . . . . 171
arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
auxiliary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
boot-server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
broadcast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
console (Physical Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
default-address-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
domain-name (Router) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
gre-path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
host-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
icmpv4-rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
icmpv6-rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
inet6-backup-router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
internet-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
ipip-path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
ipv6-duplicate-addr-detection-transmits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
ipv6-path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
ipv6-path-mtu-discovery-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
ipv6-reject-zero-hop-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
lcd-menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
menu-item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
multicast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
no-multicast-echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
no-ping-record-route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
no-ping-time-stamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
no-redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
no-tcp-rfc1323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
no-tcp-rfc1323-paws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

xi

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
tcp-drop-synfin-set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
traceoptions (SBC Configuration Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
trusted-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Chapter 17

Operational Mode Commands for System Setup . . . . . . . . . . . . . . . . . . . . . 201
clear chassis display message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
clear system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
request chassis pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
request chassis routing-engine master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
request system halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
request system logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
request system power-off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
request system scripts convert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
request system scripts refresh-from commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
request system scripts refresh-from event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
request system scripts refresh-from op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
request system storage cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
set chassis display message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
set date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
show chassis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
show chassis lcd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
show configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
show host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
show ntp associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
show ntp status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
show system firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
show system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
show system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
show system software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
show system storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
show system switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
show system uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
show system users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
show system virtual-memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
show task replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
show version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

xii

Table of Contents

Part 6

Junos OS for J-EX Series Switches Power Management

Chapter 18

Power Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Junos OS—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
J-EX Series Switch Software Features Overview . . . . . . . . . . . . . . . . . . . . . . 301
Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Understanding Power Management on J-EX Series Switches . . . . . . . . . . . 302
Power Priority of Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Power Supply Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Chapter 19

Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Configuring Power Supply Redundancy (CLI Procedure) . . . . . . . . . . . . . . . . . . . 307
Configuring the Power Priority of Line Cards (CLI Procedure) . . . . . . . . . . . . . . . 308

Chapter 20

Verifying Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Verifying Power Configuration and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Chapter 21

Configuration Statements for Power Management . . . . . . . . . . . . . . . . . . . . 311
fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
n-plus-n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
power-budget-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
psu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Chapter 22

Operational Mode Commands for Power Management . . . . . . . . . . . . . . . 315
show chassis power-budget-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Part 7

Junos OS for J-EX Series Switches Configuration Management

Chapter 23

Configuration Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Configuration Files—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Understanding Configuration Files for J-EX Series Switches . . . . . . . . . . . . . 321
Configuration Files Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Understanding Automatic Refreshing of Scripts on J-EX Series Switches . . 323
Understanding Autoinstallation of Configuration Files on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Typical Uses for Autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Autoinstallation Configuration Files and IP Addresses . . . . . . . . . . . . . 324
Typical Autoinstallation Process on a New Switch . . . . . . . . . . . . . . . . 324
J-EX Series Switches Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
J-EX4200 Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
J-EX8200 Switch Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Chapter 24

Managing Junos OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Using the Configuration Tools in J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Using the CLI Viewer in the J-Web Interface to View Configuration Text . . . . 331
Using the CLI Editor in the J-Web Interface to Edit Configuration Text . . . . . 331
Using the Point and Click CLI Tool in the J-Web Interface to Edit Configuration
Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

xiii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Using the Commit Options to Commit Configuration Changes (J-Web
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Managing Junos OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Uploading a Configuration File (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 336
Uploading a Configuration File (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . 337
Managing Configuration Files Through the Configuration History (J-Web
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Displaying Configuration History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Displaying Users Editing the Configuration . . . . . . . . . . . . . . . . . . . . . . . 339
Comparing Configuration Files with the J-Web Interface . . . . . . . . . . . 339
Downloading a Configuration File with the J-Web Interface . . . . . . . . . 340
Loading a Previous Configuration File with the J-Web Interface . . . . . . 340
Loading a Previous Configuration File (CLI Procedure) . . . . . . . . . . . . . . . . 340
Reverting to the Default Factory Configuration for the J-EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Reverting to the Default Factory Configuration by Using the LCD
Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Reverting to the Default Factory Configuration by Using the Load Factory
Default Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Reverting to the Rescue Configuration for the J-EX Series Switch . . . . . . . . 343
Setting or Deleting the Rescue Configuration (CLI Procedure) . . . . . . . . . . 344
Setting or Deleting the Rescue Configuration (J-Web Procedure) . . . . . . . . 345
Configuring Autoinstallation of Configuration Files (CLI Procedure) . . . . . . 345

Chapter 25

Verifying Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Verifying Autoinstallation Status on a J-EX Series Switch . . . . . . . . . . . . . . . . . . 349

Chapter 26

Configuration Statements for Configuration Management . . . . . . . . . . . . . 351
archival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
archive-sites (Configuration File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
commit synchronize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
configuration-servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
transfer-interval (Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
transfer-on-commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Chapter 27

Operational Mode Commands for Configuration Management . . . . . . . . 359
clear log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
clear system commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
file archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
file checksum md5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
file checksum sha1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
file checksum sha-256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
file compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
file copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
file delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
file list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
file rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

xiv

Table of Contents

file show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
request system configuration rescue delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
request system configuration rescue save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
request system scripts refresh-from commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
request system scripts refresh-from event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
request system scripts refresh-from op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
show system commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
show system configuration archival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
show system configuration rescue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
show system rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
test configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Part 8

User and Access Management on J-EX Series Switches

Chapter 28

User and Access Management on J-EX Series Switches Overview . . . . . . 391
J-EX Series Switch Software Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . . . . 392
Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . . 392
Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Chapter 29

User Access Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Configuring Management Access for the J-EX Series Switch (J-Web
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Generating SSL Certificates to Be Used for Secure Web Access . . . . . . . . . . . . . 398
Configuring MS-CHAPv2 to Provide Password-Change Support (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Chapter 30

Monitoring Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Managing Users (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Chapter 31

Troubleshooting User Access Management . . . . . . . . . . . . . . . . . . . . . . . . . 405
Troubleshooting Loss of the Root Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Chapter 32

Configuration Statements for User and Access Management . . . . . . . . . 409
allow-commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
allow-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
announcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
authentication (Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
authentication-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
change-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
class (Assigning a Class to an Individual User) . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
class (Defining Login Classes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
deny-commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
deny-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
full-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
idle-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
login-alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
login-tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
maximum-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

xv

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
minimum-changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
minimum-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
password (Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
radius-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
retry-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
root-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
root-login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
tacplus-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
tacplus-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
traceoptions (Address-Assignment Pool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
uid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
user (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

Chapter 33

Operational Mode Commands for User and Access Management . . . . . . 433
request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
show subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

Part 9

Junos OS for J-EX Series Switches System Services

Chapter 34

System Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
DHCP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
DHCP Services for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . 445
DHCP/BOOTP Relay for J-EX Series Switches Overview . . . . . . . . . . . . . . . 446

Chapter 35

System Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Configuring DHCP Services (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Configuring a DHCP SIP Server (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 450

Chapter 36

Monitoring System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Monitoring DHCP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

Chapter 37

Configuration Statements for System Services . . . . . . . . . . . . . . . . . . . . . . 455
boot-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
boot-server (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
bootp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
ca-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
cache-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
cache-timeout-negative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
certification-authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
client-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
connection-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
crl (Encryption Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
default-lease-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
domain-name (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
domain-search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

xvi

Table of Contents

encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
enrollment-retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
enrollment-url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
ftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
helpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
http . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
https . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
interface (BOOTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
interface (DNS and TFTP Packet Forwarding or Relay Agent) . . . . . . . . . . . . . . 475
ldap-url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
load-key-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
local-certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
maximum-certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
maximum-hop-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
maximum-lease-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
minimum-wait-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
name-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
no-listen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
outbound-ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
path-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
port (HTTP/HTTPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
port (SRC Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
protocol-version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
server (DHCP and BOOTP Relay Agent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
server (DNS and TFTP Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
server-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
service-deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
sip-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
source-address (SRC Software) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
source-address-giaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
static-binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
tftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
traceoptions (DHCP Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
traceoptions (DNS and TFTP Packet Forwarding) . . . . . . . . . . . . . . . . . . . . . . . 504
web-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
wins-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

xvii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 38

Operational Mode Commands for System Services . . . . . . . . . . . . . . . . . . 509
clear system services dhcp binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
clear system services dhcp conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
clear system services dhcp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
request ipsec switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
request security certificate (signed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
request security key-pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
request security certificate (unsigned) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
show system services dhcp binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
show system services dhcp conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
show system services dhcp global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
show system services dhcp pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
show system services dhcp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
show system services service-deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Part 10

Junos OS for J-EX Series Switches System Monitoring

Chapter 39

System Monitoring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Understanding Alarm Types and Severity Levels on J-EX Series Switches . . . . . 533
Dashboard for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
System Information Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Health Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Capacity Utilization Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Alarms Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Chassis Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

Chapter 40

Administering and Monitoring System Functions . . . . . . . . . . . . . . . . . . . . . 541
Monitoring System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Checking Active Alarms with the J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . 544
Monitoring Chassis Alarms for a J-EX8200 Switch . . . . . . . . . . . . . . . . . . . . . . . 545
Monitoring Switch Control Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Monitoring System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Monitoring Chassis Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Monitoring System Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure) . . 555
Cleaning Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Downloading Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Deleting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556

Chapter 41

Configuration Statements for System Monitoring . . . . . . . . . . . . . . . . . . . . 559
archive (All System Log Files) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
archive-sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
attributes-match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
console (System Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

xviii

Table of Contents

equals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
event-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
events (Associating Events with a Policy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
events (Correlating Events with Each Other) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
event-script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
event-script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
execute-commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
explicit-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
facility-override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
file (System Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
generate-event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
interface (Accounting or Sampling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
log-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
output-filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
output-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
raise-trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
refresh-from . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
remote-execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
retry-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
structured-data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
then . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
time-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
time-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
time-of-day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
time-zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
traceoptions (Commit and Op Scripts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
transfer-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
user (System Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
user-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
within . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
world-readable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609

xix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 42

Operational Mode Commands for System Monitoring . . . . . . . . . . . . . . . . . 611
clear log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
file archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
file checksum md5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
file checksum sha1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
file checksum sha-256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
file compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
file copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
file delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
file list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
file rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
file show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
monitor list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
monitor start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
monitor stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
request system configuration rescue delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
request system configuration rescue save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
request system scripts refresh-from commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
request system scripts refresh-from event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
request system scripts refresh-from op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
show chassis alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
show chassis environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
show chassis environment fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
show chassis environment routing-engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
show chassis fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
show chassis hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
show chassis led . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
show chassis location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
show chassis pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
show chassis routing-engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
show chassis temperature-thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
show log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
show pfe next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
show pfe route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
show pfe statistics ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
show pfe statistics ip6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
show pfe terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
show system alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
show system audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
show system buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
show system connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
show system core-dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
show system directory-usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
show system processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

xx

Table of Contents

Part 11

Virtual Chassis

Chapter 43

Virtual Chassis—Overview, Components, and Configurations . . . . . . . . . . 691
Virtual Chassis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Basic Configuration of a Virtual Chassis with Master and Backup
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Expanding Configurations—Within a Single Wiring Closet and Across Wiring
Closets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Global Management of Member Switches in a Virtual Chassis . . . . . . . . . . 693
High Availability Through Redundant Routing Engines . . . . . . . . . . . . . . . . . 693
Adaptability as an Access Switch or Distribution Switch . . . . . . . . . . . . . . . 693
Understanding Virtual Chassis Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Virtual Chassis Ports (VCPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Master Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Backup Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Linecard Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Member Switch and Member ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Mastership Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Virtual Chassis Identifier (VCID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Understanding How the Master in a Virtual Chassis Configuration Is Elected . . 698
Understanding Software Upgrade in a Virtual Chassis Configuration . . . . . . . . 698
Understanding Global Management of a Virtual Chassis Configuration . . . . . . 699
Understanding Nonvolatile Storage in a Virtual Chassis Configuration . . . . . . . . 702
Nonvolatile Memory Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Understanding the High-Speed Interconnection of the Virtual Chassis
Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Understanding Virtual Chassis Configurations and Link Aggregation . . . . . . . . . 702
Understanding Virtual Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Understanding Virtual Chassis J-EX4200 Switch Version Compatibility . . . . . . 705
Understanding Fast Failover in a Virtual Chassis Configuration . . . . . . . . . . . . . . 706
Supported Topologies for Fast Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
How Fast Failover Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Fast Failover in a Ring Topology using Dedicated VCPs . . . . . . . . . . . . . 706
Fast Failover in a Ring Topology Using Uplink Module VCPs . . . . . . . . . 708
Fast Failover in a Virtual Chassis Configuration Using Multiple Ring
Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Effects of Topology Changes on a Fast Failover Configuration . . . . . . . . . . . . 711
Understanding Split and Merge in a Virtual Chassis Configuration . . . . . . . . . . . . 712
What Happens When a Virtual Chassis Configuration Splits . . . . . . . . . . . . . 712
Merging Virtual Chassis Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Understanding Automatic Software Update on Virtual Chassis Member
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715

Chapter 44

Virtual Chassis—Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Example: Configuring a Virtual Chassis with a Master and Backup in a Single
Wiring Closet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet . . 722
Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727

xxi

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring
Closets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a
Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch . . 740
Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP
Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration
File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic
When a Virtual Chassis Member Switch or Intermember Link Fails . . . . . . . 763
Example: Assigning the Virtual Chassis ID to Determine Precedence During a
Virtual Chassis Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Example: Configuring Link Aggregation Groups Using Uplink Virtual Chassis
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Example: Configuring Automatic Software Update on Virtual Chassis Member
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

Chapter 45

Configuring Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Configuring a Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Configuring a Virtual Chassis with a Preprovisioned Configuration File . . . . 782
Configuring a Virtual Chassis with a Nonprovisioned Configuration File . . . 783
Configuring a Virtual Chassis (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 784
Adding a New Switch to an Existing Virtual Chassis Configuration (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Adding a New Switch to an Existing Virtual Chassis Configuration Within
the Same Wiring Closet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Adding a New Switch from a Different Wiring Closet to an Existing Virtual
Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
Adding a New Switch to an Existing Preprovisioned Virtual Chassis
Configuration Using Autoprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . 789
Configuring Mastership of the Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . 790
Configuring Mastership Using a Preprovisioned Configuration File . . . . . . . . 791
Configuring Mastership Using a Configuration File That Is Not
Preprovisioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) . . . . . . 792
Setting an Uplink VCP Between Two Member Switches . . . . . . . . . . . . . . . 794
Setting an Uplink VCP on a Standalone Switch . . . . . . . . . . . . . . . . . . . . . . 794
Setting an Uplink Module Port or a J-EX4200-24F Network Port as a Virtual
Chassis Port Using the LCD Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Configuring the Virtual Management Ethernet Interface for Global Management
of a Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Configuring the Timer for the Backup Member to Start Using Its Own MAC
Address, as Master of Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . 797
Configuring Fast Failover in a Virtual Chassis Configuration . . . . . . . . . . . . . . . . 798
Disabling Fast Failover in a Virtual Chassis Configuration . . . . . . . . . . . . . . . . . . 799
Disabling Split and Merge in a Virtual Chassis Configuration (CLI Procedure) . . 799
Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis
Merge (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800

xxii

Table of Contents

Configuring Automatic Software Update on Virtual Chassis Member Switches
(CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801

Chapter 46

Verifying Virtual Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Command Forwarding Usage with a Virtual Chassis Configuration . . . . . . . . . . 803
Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual
Chassis Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Verifying That the Virtual Chassis Ports Are Operational . . . . . . . . . . . . . . . . . . 808
Monitoring Virtual Chassis Configuration Status and Statistics . . . . . . . . . . . . . 809
Replacing a Member Switch of a Virtual Chassis Configuration (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Remove, Repair, and Reinstall the Same Switch . . . . . . . . . . . . . . . . . . . . . . 811
Remove a Member Switch, Replace with a Different Switch, and Reapply
the Old Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Remove a Member Switch and Make Its Member ID Available for
Reassignment to a Different Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Verifying That Graceful Routing Engine Switchover Is Working in the Virtual
Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

Chapter 47

Troubleshooting Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Troubleshooting a Virtual Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . .
Clear Virtual Chassis NotPrsnt Status and Make Member ID Available for
Reassignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Factory Default Does Not Commit on a Multimember Virtual
Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Member ID Persists When a Member Switch Is Disconnected From a Virtual
Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 48

815
815
815
815

Configuration Statements for Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . 817
[edit virtual-chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . 817
auto-sw-update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
fast-failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
graceful-switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
mac-persistence-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
mastership-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
no-management-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
no-split-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
package-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
preprovisioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
redundancy (Graceful Switchover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
serial-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
virtual-chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

xxiii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 49

Operational Mode Commands for Virtual Chassis . . . . . . . . . . . . . . . . . . . . 835
clear virtual-chassis vc-port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
request session member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
request virtual-chassis recycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
request virtual-chassis renumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
request virtual-chassis vc-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
request virtual-chassis vc-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
show system uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
show virtual-chassis active topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
show virtual-chassis fast-failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
show virtual-chassis status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
show virtual-chassis vc-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
show virtual-chassis vc-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
show virtual-chassis vc-port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854

Part 12

Interfaces on J-EX Series Switches

Chapter 50

Interfaces—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
J-EX Series Switches Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
Special Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Understanding Interface Naming Conventions on J-EX Series Switches . . . . . . 865
Physical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Logical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Wildcard Characters in Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Understanding Aggregated Ethernet Interfaces and LACP . . . . . . . . . . . . . . . . . 867
Link Aggregation Group (LAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Link Aggregation Control Protocol (LACP) . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Understanding Interface Ranges on J-EX Series Switches . . . . . . . . . . . . . . . . . 869
Understanding Layer 3 Subinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Understanding Unicast RPF for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . 872
Unicast RPF for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . 872
Unicast RPF Implementation for J-EX Series Switches . . . . . . . . . . . . . . . . . 873
Unicast RPF Packet Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Bootstrap Protocol (BOOTP) and DHCP Requests . . . . . . . . . . . . . . . . 873
Default Route Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
When to Enable Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
When Not to Enable Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
Limitations of the Unicast RPF Implementation on J-EX4200 Switches . . . 875
Understanding IP Directed Broadcast for J-EX Series Switches . . . . . . . . . . . . . 876
IP Directed Broadcast for J-EX Series Switches Overview . . . . . . . . . . . . . . 876
IP Directed Broadcast Implementation for J-EX Series Switches . . . . . . . . . 876
When to Enable IP Directed Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
When Not to Enable IP Directed Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . 877
High Availability Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . 877
VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
Graceful Protocol Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
Redundant Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879

xxiv

Table of Contents

Virtual Chassis Software Upgrade and Failover Features . . . . . . . . . . . . . . . 879
Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880

Chapter 51

Examples: Interfaces Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a
Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch . . . 881
Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP
Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an
Access Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
Example: Configuring Unicast RPF on a J-EX Series Switch . . . . . . . . . . . . . . . . 900
Example: Configuring IP Directed Broadcast on a J-EX Series Switch . . . . . . . . 904

Chapter 52

Configuring Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
Configuring Gigabit Ethernet Interfaces (J-Web Procedure) . . . . . . . . . . . . . . . . 909
Port Role Configuration with the J-Web Interface (with CLI References) . . . . . . 915
Configuring Gigabit Ethernet Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . . 919
Configuring VLAN Options and Port Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Configuring the Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Configuring the IP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Setting the Mode on an SFP+ Uplink Module (CLI Procedure) . . . . . . . . . . . . . . . 921
Configuring Aggregated Ethernet Interfaces (CLI Procedure) . . . . . . . . . . . . . . . 922
Configuring Aggregated Ethernet Interfaces (J-Web Procedure) . . . . . . . . . . . . 923
Configuring Aggregated Ethernet LACP (CLI Procedure) . . . . . . . . . . . . . . . . . . . 926
Configuring Unicast RPF (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
Disabling Unicast RPF (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
Configuring IP Directed Broadcast (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . 929
Configuring a Layer 3 Subinterface (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 930

Chapter 53

Verifying Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Monitoring Interface Status and Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Verifying the Status of a LAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
Verifying That LACP Is Configured Correctly and Bundle Members Are Exchanging
LACP Protocol Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Verifying the LACP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Verifying That the LACP Packets Are Being Exchanged . . . . . . . . . . . . . . . . 933
Verifying That Layer 3 Subinterfaces Are Working . . . . . . . . . . . . . . . . . . . . . . . . 934
Verifying Unicast RPF Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
Verifying IP Directed Broadcast Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937

Chapter 54

Troubleshooting Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
Troubleshooting Network Interfaces on J-EX4200 Switches . . . . . . . . . . . . . . . 939
The interface on the port in which an SFP or SFP+ transceiver is installed
in an SFP+ uplink module is down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
Troubleshooting an Aggregated Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . 940
Troubleshooting Interface Configuration and Cable Faults . . . . . . . . . . . . . . . . . 940
Interface Configuration or Connectivity Is Not Working . . . . . . . . . . . . . . . . 940
Troubleshooting Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Legitimate Packets Are Discarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941

xxv

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Troubleshooting Uplink Module Installation or Replacement on J-EX4200
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
Virtual Chassis port (VCP) connection does not work . . . . . . . . . . . . . . . . . 942

Chapter 55

Configuration Statements for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
[edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 943
[edit interfaces] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . 943
802.3ad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
aggregated-devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
aggregated-ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951
chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
device-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
family (for J-EX Series switches) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
force-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
interface-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
interfaces (for J-EX Series switches) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
lacp (802.3ad) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
link-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
link-speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
member-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
minimum-links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
native-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
periodic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
pic-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
port-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
rpf-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
sfpplus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
targeted-broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987

Chapter 56

Operational Mode Commands for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 989
clear ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
monitor interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
show ethernet-switching interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
show interfaces diagnostics optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000

xxvi

Table of Contents

show interfaces ge- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
show interfaces queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
show interfaces xe- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
show ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
show lacp interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
test interface restart-auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037

Part 13

Layer 2 Bridging and VLANs

Chapter 57

Bridging and VLANs—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
Understanding Bridging and VLANs on J-EX Series Switches . . . . . . . . . . . . . . . 1041
Ethernet LANs, Transparent Bridging, and VLANs . . . . . . . . . . . . . . . . . . . . 1041
How Bridging Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Types of Switch Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
IEEE 802.1Q Encapsulation and Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Assignment of Traffic to VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Ethernet Switching Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
Layer 2 and Layer 3 Forwarding of VLAN Traffic . . . . . . . . . . . . . . . . . . . . . 1045
GVRP and MVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
Routed VLAN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
Understanding Private VLANs on J-EX Series Switches . . . . . . . . . . . . . . . . . . . 1047
Understanding Virtual Routing Instances on J-EX Series Switches . . . . . . . . . . 1048
Understanding Redundant Trunk Links on J-EX Series Switches . . . . . . . . . . . . 1049
Understanding Q-in-Q Tunneling on J-EX Series Switches . . . . . . . . . . . . . . . . . 1051
How Q-in-Q Tunneling Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
Disabling MAC Address Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
Mapping C-VLANs to S-VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
All-in-One Bundling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Many-to-One Bundling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Mapping a Specific Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Routed VLAN Interfaces on Q-in-Q VLANs . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Limitations for Q-in-Q Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
How MVRP Works on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . 1054
Basics of MVRP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
MVRP Registration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
MRP Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
MRP VLAN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
Understanding Layer 2 Protocol Tunneling on J-EX Series Switches . . . . . . . . . 1056
Layer 2 Protocols Supported by L2PT on J-EX Series Switches . . . . . . . . . 1057
How L2PT Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
L2PT Basics on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
Understanding Proxy ARP on EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . 1059
What Is ARP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
Proxy ARP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
Best Practices for Proxy ARP on J-EX Series Switches . . . . . . . . . . . . . . . . 1060
Understanding MAC Notification on J-EX Series Switches . . . . . . . . . . . . . . . . 1060

xxvii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 58

Examples: Bridging and VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . 1063
Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch . . . . 1063
Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches . . 1070
Example: Connecting an Access Switch to a Distribution Switch . . . . . . . . . . . 1078
Example: Configure Automatic VLAN Administration Using GVRP . . . . . . . . . . 1087
Example: Configuring Redundant Trunk Links for Faster Recovery . . . . . . . . . . . 1101
Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches . . . . . . . . . . . . 1105
Example: Configuring a Private VLAN on a J-EX Series Switch . . . . . . . . . . . . . . 1107
Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
Example: Configuring Automatic VLAN Administration Using MVRP on J-EX
Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches . . . . 1126

Chapter 59

Configuring Bridging and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
Configuring VLANs for J-EX Series Switches (J-Web Procedure) . . . . . . . . . . . . 1133
Configuring VLANs for J-EX Series Switches (CLI Procedure) . . . . . . . . . . . . . . . 1136
Configuring Routed VLAN Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . 1137
Configuring MAC Table Aging (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
Configuring the Native VLAN Identifier (CLI Procedure) . . . . . . . . . . . . . . . . . . . 1139
Creating a Series of Tagged VLANs (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 1140
Configuring Virtual Routing Instances (CLI Procedure) . . . . . . . . . . . . . . . . . . . . 1142
Creating a Private VLAN (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
Configuring Q-in-Q Tunneling (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
Configuring GVRP (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
Configuring Redundant Trunk Groups (J-Web Procedure) . . . . . . . . . . . . . . . . . 1146
Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) . . . . 1147
Enabling MVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
Disabling MVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
Disabling Dynamic VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
Configuring Timer Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
Configuring MVRP Registration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149
Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
Configuring MAC Notification (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151
Enabling MAC Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
Disabling MAC Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
Setting the MAC Notification Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
Configuring Proxy ARP (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153

Chapter 60

Verifying Bridging and VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 1155
Verifying That a Series of Tagged VLANs Has Been Created . . . . . . . . . . . . . . . . 1155
Verifying That Virtual Routing Instances Are Working . . . . . . . . . . . . . . . . . . . . . 1157
Verifying That Q-in-Q Tunneling Is Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
Verifying That a Private VLAN Is Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
Monitoring Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
Monitoring GVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161
Verifying That MVRP Is Working Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
Verifying That MAC Notification Is Working Properly . . . . . . . . . . . . . . . . . . . . . . 1163

xxviii

Table of Contents

Verifying That Proxy ARP Is Working Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164

Chapter 61

Troubleshooting Bridging and VLAN Configuration . . . . . . . . . . . . . . . . . . 1165
Troubleshooting Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
MAC Address in the Switch’s Ethernet Switching Table Is Not Updated After
a MAC Address Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165

Chapter 62

Configuration Statements for Bridging and VLANs . . . . . . . . . . . . . . . . . . . 1167
[edit ethernet-switching-options] Configuration Statement Hierarchy . . . . . . . 1167
[edit interfaces] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . 1169
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . 1173
[edit routing-instances] Configuration Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 1180
[edit vlans] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 1180
arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
bridge-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
customer-vlans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
disable (MVRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185
dot1q-tunneling (Ethernet Switching) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185
dot1q-tunneling (VLANs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
drop-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187
ether-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188
ethernet-switching-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
group-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
instance-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
interface (MVRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198
join-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
join-timer (MVRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200
l3-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
layer2-protocol-tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
leave-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203
leave-timer (MVRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
leaveall-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
leaveall-timer (MVRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
mac-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
mac-notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
mac-table-aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210
members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211
mvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
native-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
no-dynamic-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214

xxix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

no-local-switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214
no-mac-learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
no-mac-learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
notification-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
port-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
primary-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
redundant-trunk-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
routing-instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
shutdown-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
vlan-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1222
vlans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223

Chapter 63

Operational Mode Commands for Bridging and VLANs . . . . . . . . . . . . . . . 1225
clear ethernet-switching layer2-protocol-tunneling error . . . . . . . . . . . . . . . . . . 1226
clear ethernet-switching layer2-protocol-tunneling statistics . . . . . . . . . . . . . . 1227
clear ethernet-switching table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1228
clear gvrp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229
clear mvrp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230
show ethernet-switching interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231
show ethernet-switching layer2-protocol-tunneling interface . . . . . . . . . . . . . . 1234
show ethernet-switching layer2-protocol-tunneling statistics . . . . . . . . . . . . . 1236
show ethernet-switching layer2-protocol-tunneling vlan . . . . . . . . . . . . . . . . . 1239
show ethernet-switching mac-learning-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
show ethernet-switching mac-notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
show ethernet-switching statistics aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244
show ethernet-switching statistics mac-learning . . . . . . . . . . . . . . . . . . . . . . . . 1246
show ethernet-switching table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
show gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
show gvrp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
show mvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
show mvrp dynamic-vlan-memberships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259
show mvrp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1260
show redundant-trunk-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1262
show vlans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263

Part 14

Spanning-Tree Protocols

Chapter 64

Spanning-Tree Protocols—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
Understanding STP for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
Understanding RSTP for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . 1276
Understanding MSTP for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278
Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
Understanding Root Protection for STP, RSTP, VSTP, and MSTP on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280

xxx

Table of Contents

Understanding VSTP for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . 1281

Chapter 65

Examples of Spanning-Tree Protocols Configuration . . . . . . . . . . . . . . . . 1283
Example: Configuring Faster Convergence and Improving Network Stability with
RSTP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
Example: Configuring Network Regions for VLANs with MSTP on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297
Example: Configuring BPDU Protection on STP Interfaces to Prevent STP
Miscalculations on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317
Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP
Miscalculations on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321
Example: Configuring Loop Protection to Prevent Interfaces from Transitioning
from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches . . 1325
Example: Configuring Root Protection to Enforce Root Bridge Placement in
Spanning Trees on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329

Chapter 66

Configuring Spanning-Tree Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335
Unblocking an Interface That Receives BPDUs in Error (CLI Procedure) . . . . . . 1335
Configuring STP (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
Configuring Spanning-Tree Protocols (J-Web Procedure) . . . . . . . . . . . . . . . . . 1336
Configuring VLAN Spanning Tree Protocol (CLI Procedure) . . . . . . . . . . . . . . . 1340

Chapter 67

Verifying Spanning Tree Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
Monitoring Spanning-Tree Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343

Chapter 68

Configuration Statements for Spanning-Tree Protocols . . . . . . . . . . . . . . 1347
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . 1347
alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354
block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355
bpdu-block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356
bpdu-block-on-edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357
bpdu-timeout-action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358
bridge-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359
configuration-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1362
disable-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364
force-version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
forward-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
hello-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1369
max-age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
max-hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1371
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1372
msti . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
mstp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374
no-root-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376

xxxi

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

revision-level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377
rstp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378
stp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1381
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
vlan (VSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1386
vstp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387

Chapter 69

Operational Mode Commands for Spanning-Tree Protocols . . . . . . . . . . 1389
clear ethernet-switching bpdu-error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
clear spanning-tree statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
clear spanning-tree statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
show spanning-tree bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1393
show spanning-tree bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398
show spanning-tree interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
show spanning-tree interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407
show spanning-tree mstp configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411
show spanning-tree mstp configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413
show spanning-tree statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414
show spanning-tree statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416

Part 15

Layer 3 Protocols

Chapter 70

Layer 3 Protocols—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
Layer 3 Protocols Supported on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . 1421
Layer 3 Protocols Not Supported on J-EX Series Switches . . . . . . . . . . . . . . . . . 1422
Understanding Distributed Periodic Packet Management on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424
Understanding VRRP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
Overview of VRRP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . 1425
Examples of VRRP Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
Understanding IPsec Authentication for OSPF Packets on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428
Authentication Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428
Encryption Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
IPsec Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
Security Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
IPsec Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1430

Chapter 71

Configuring Layer 3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431
Configuring BGP Sessions (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431
Configuring an OSPF Network (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . 1435
Configuring a RIP Network (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
Configuring Static Routing (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
Configuring Static Routing (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 1444

xxxii

Table of Contents

Configuring Routing Policies (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 1446
Configuring Distributed Periodic Packet Management on a J-EX Series Switch
(CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
Disabling or Enabling Distributed Periodic Packet Management Globally . . 1451
Disabling or Enabling Distributed Periodic Packet Management for Link
Aggregation Control Protocol (LACP) Packets . . . . . . . . . . . . . . . . . . . 1452
Configuring VRRP for IPv6 (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452
Using IPsec to Secure OSPFv3 Networks (CLI Procedure) . . . . . . . . . . . . . . . . . 1453
Configuring Security Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453
Securing OPSFv3 Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454

Chapter 72

Verifying Layer 3 Protocols Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 1455
Monitoring BGP Routing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455
Monitoring OSPF Routing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457
Monitoring RIP Routing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460
Monitoring Routing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461

Chapter 73

Configuration Statements for Layer 3 Protocols . . . . . . . . . . . . . . . . . . . . . 1465
accept-remote-nexthop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465
active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466
advertise-external . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
advertise-inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468
advertise-peer-as . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470
aggregate-label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471
allow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472
any-sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1473
area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474
area-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1475
as-override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1476
as-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477
asm-override-ssm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
authentication-algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1480
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1481
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482
authentication-key-chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483
authentication-key-chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484
authentication-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485
authentication-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486
autonomous-system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487
backup-pe-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488
backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1489
bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
bandwidth-based-metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
bfd-liveness-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493
bfd-liveness-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496
bfd-liveness-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498
bfd-liveness-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501
bfd-liveness-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503

xxxiii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

bgp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506
bgp-orf-cisco-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
bmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509
centralized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1510
check-zero . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511
checksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512
cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514
confederation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515
csnp-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516
damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
dead-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
default-lsa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519
default-metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
disable (IS-IS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523
disable (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1524
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526
domain-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
domain-vpn-tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
explicit-null . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1530
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1531
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
export-rib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
external-preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534
external-preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535
family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
fate-sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539
flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1540
flow-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
forwarding-cache (Flow Maps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
forwarding-cache (Multicast) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542
forwarding-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542
generate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1546
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1550
group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553

xxxiv

Table of Contents

group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555
hello-authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
hello-authentication-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557
hello-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
hello-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
hello-padding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560
holddown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
holddown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
hold-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562
hold-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1563
hold-time (IS-IS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
idle-after-switch-over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565
ignore-attached-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
ignore-lsp-metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1570
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
import-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
import-rib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1572
include-mp-next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573
indirect-next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573
inet6-advertise-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574
install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575
instance-export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
instance-import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
inter-area-prefix-export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
inter-area-prefix-import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
interface (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1583
interface (Multicast via Static Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
interface-routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585
interface-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1586
ipv4-multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
ipv4-multicast-metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
ipv6-multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588
ipv6-multicast-metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588
ipv6-unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589
ipv6-unicast-metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589
isis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1590
keep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
labeled-unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1592
level (Global IS-IS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593
link-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594
local-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595
local-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596
local-as . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1597

xxxv

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

local-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
local-preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599
log-updown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1600
loose-authentication-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
lsp-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
lsp-lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
lsp-metric-into-summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
martians . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1603
max-areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
maximum-bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
maximum-paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1605
maximum-prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606
med-igp-update-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607
mesh-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1608
message-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1610
metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1611
metric (Aggregate, Generated, or Static Route) . . . . . . . . . . . . . . . . . . . . . . . . . . 1612
metric-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1613
metric-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
metric-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615
metric-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1617
metric-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1618
metric-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619
mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620
multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
multihop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1622
multipath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1623
neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624
neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1627
neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1628
no-adjacency-holddown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629
no-aggregator-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1630
no-authentication-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
no-client-reflect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1632
no-csnp-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1633
no-eligible-backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1633
no-hello-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
no-ipv4-multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
no-ipv4-routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635
no-ipv6-multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635
no-ipv6-routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
no-ipv6-unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
no-nssa-abr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637
no-psnp-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637
no-qos-adjust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1638
no-rfc-1583 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1639
no-unicast-topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
no-validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640

xxxvi

Table of Contents

node-link-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1641
nssa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1642
options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1643
ospf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644
ospf3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644
out-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1645
outbound-route-filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646
overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647
overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1648
passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649
passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
peer-as . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1652
pim-to-igmp-proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1653
pim-to-mld-proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654
point-to-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654
policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655
policy (Flow Maps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
policy (SSM Maps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
ppm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1657
ppm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658
preempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1659
preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1660
preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1662
preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664
prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
prefix-export-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
prefix-export-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666
prefix-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667
priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1668
priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669
priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
qualified-next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1671
readvertise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674
receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675
redundant-sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
reference-bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
reference-bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677
remove-private . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1678
resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679
resolution-ribs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679
resolve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1680
restart-duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
retain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1682

xxxvii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

retransmit-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683
reverse-oif-mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684
rib (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685
rib (Route Resolution) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1686
rib-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1687
rib-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688
rib-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689
rib-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1690
rib-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691
rib-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1692
rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693
ripng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693
route-distinguisher-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
route-record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
route-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
route-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
route-type-community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
router-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
routing-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
rpf-check-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698
scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698
scope-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699
send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1700
send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701
shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1702
source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1702
source-routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703
spf-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
spf-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
ssm-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
ssm-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708
stub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1710
subscriber-leave-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1712
tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713
tcp-mss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714
threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715
timeout (Flow Maps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1716
timeout (Multicast) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1716
topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717
traceoptions (BGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1718
traceoptions (IS-IS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721
traceoptions (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724
traceoptions (RIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727
traceoptions (RIPng) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1730
traceoptions (All Routing Protocols) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1733
traffic-engineering (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735
transit-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736

xxxviii

Table of Contents

type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
type-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738
update-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
update-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
upstream-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
virtual-inet6-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
virtual-link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1742
virtual-link-local-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1743
vrrp-inet6-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744
wide-metrics-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745

Chapter 74

Operational Commands for Layer 3 Protocols . . . . . . . . . . . . . . . . . . . . . . . 1747
clear (ospf | ospf3) database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748
clear (ospf | ospf3) io-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
clear (ospf | ospf3) neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1752
clear (ospf | ospf3) statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753
clear bgp damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755
clear bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1756
clear bgp table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758
clear ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1759
clear isis adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1760
clear isis database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1762
clear isis overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
clear isis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766
clear ospf overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768
clear rip general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1769
clear rip statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1770
clear ripng general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771
clear ripng statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1772
show (ospf | ospf3) interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1773
show (ospf | ospf3) io-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1778
show (ospf | ospf3) log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1779
show (ospf | ospf3) neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1782
show (ospf | ospf3) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1787
show (ospf | ospf3) route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791
show (ospf | ospf3) statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796
show as-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1798
show as-path domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1802
show as-path summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1804
show bgp bmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805
show bgp group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806
show bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1812
show bgp summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824
show ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1828
show isis adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1830
show isis authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834
show isis backup coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836
show isis backup label-switched-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1838
show isis backup spf results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840

xxxix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

show isis database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1843
show isis hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1850
show isis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851
show isis overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855
show isis route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1858
show isis spf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1861
show isis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1866
show ospf3 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
show ospf database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1878
show policy damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886
show rip general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1888
show rip neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
show rip statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1891
show ripng general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894
show ripng neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895
show ripng statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1897
show route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1899
show route active-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
show route all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1908
show route aspath-regex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1910
show route best . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1912
show route brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916
show route community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1918
show route community-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1920
show route damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922
show route detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927
show route exact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
show route export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944
show route extensive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946
show route flow validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1958
show route inactive-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1960
show route inactive-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1963
show route instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965
show route label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1972
show route label-switched-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974
show route martians . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1976
show route next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1978
show route no-community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984
show route protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987
show route range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1996
show route receive-protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2000
show route resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007
show route snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2010
show route source-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018
show route summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2024
show route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026
show route terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2033
show vrrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2036

xl

Table of Contents

Part 16

IGMP Snooping and Multicast

Chapter 75

Understanding IGMP Snooping and Multicast . . . . . . . . . . . . . . . . . . . . . . 2047
IGMP Snooping on J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . 2047
How IGMP Snooping Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2047
How IGMP Snooping Works with Routed VLAN Interfaces . . . . . . . . . . . . 2048
How Hosts Join and Leave Multicast Groups . . . . . . . . . . . . . . . . . . . . . . . . 2051
IGMP Snooping Support for IGMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2051
Understanding Multicast VLAN Registration on J-EX Series Switches . . . . . . . 2052
How MVR Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2052
MVR Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2053

Chapter 76

Examples: IGMP Snooping and Multicast Configuration . . . . . . . . . . . . . 2055
Example: Configuring IGMP Snooping on J-EX Series Switches . . . . . . . . . . . . 2055
Example: Configuring Multicast VLAN Registration on J-EX Series Switches . . 2058

Chapter 77

Configuring IGMP Snooping and Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 2063
Configuring IGMP Snooping (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2063
Configuring IGMP Snooping (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 2064
Changing the IGMP Snooping Group Query Membership Timeout Value (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2067
Configuring Multicast VLAN Registration (CLI Procedure) . . . . . . . . . . . . . . . . 2068

Chapter 78

Verifying IGMP Snooping and Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . 2069
Monitoring IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2069
Verifying That the IGMP Snooping Group Query Timeout Value Has Been Changed
Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2070

Chapter 79

Configuration Statements for IGMP Snooping and Multicast . . . . . . . . . 2073
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . 2073
accounting (Per Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2080
accounting (Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2080
address (Anycast RPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2081
address (Local RPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2081
anycast-pim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2082
assert-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2083
auto-rp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2084
bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085
bootstrap-export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085
bootstrap-import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086
bootstrap-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086
data-forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087
dense-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2088
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2088
disable (PIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089
dr-election-on-p2p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2090
dr-register-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2090
embedded-rp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2091
export (Bootstrap) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2091
family (Bootstrap) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2092

xli

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

family (Local RP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2093
graceful-restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094
group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094
group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2095
group-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2096
group-ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2097
groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2098
hello-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2098
hold-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2099
igmp-snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2100
immediate-leave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2101
immediate-leave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2102
import (Bootstrap) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2103
import (PIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2103
infinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2104
install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2104
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107
join-load-balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2108
local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2109
local-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2110
mapping-agent-election . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
maximum-rps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2112
multicast-router-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2112
neighbor-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113
pim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114
priority (Bootstrap) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116
priority (PIM Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117
priority (PIM RPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118
promiscuous-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118
proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2119
query-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2119
query-last-member-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2120
query-response-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2120
receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2121
restart-duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2121
rib-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2122
robust-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2122
robust-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2123
rp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124
rp-register-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125
rp-set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2126
source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2126
source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2127
source-vlans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2127
spt-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128
ssm-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128

xlii

Table of Contents

static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2129
static (IGMP Snooping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2130
static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2130
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2131
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136
version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138
version (PIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2139
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2140

Chapter 80

Operational Mode Commands for IGMP Snooping and Multicast . . . . . . 2143
clear igmp membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2144
clear igmp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148
clear igmp-snooping membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2150
clear igmp-snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2151
clear multicast bandwidth-admission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2152
clear multicast scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154
clear multicast sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2155
clear multicast statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156
clear pim join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2157
clear pim register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2158
clear pim statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2159
mtrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2161
mtrace from-source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2163
mtrace monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2166
mtrace to-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2168
show igmp group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2171
show igmp interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175
show igmp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178
show igmp-snooping membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2181
show igmp-snooping route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2183
show igmp-snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2185
show igmp-snooping vlans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2187
show multicast flow-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2189
show multicast interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2191
show multicast mrinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2193
show multicast next-hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2195
show multicast pim-to-igmp-proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2197
show multicast pim-to-mld-proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2198
show multicast route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2199
show multicast rpf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2203
show multicast scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2207
show multicast sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2209
show multicast usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2211
show pim bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214
show pim interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216
show pim join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2219
show pim neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2224
show pim rps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2228

xliii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

show pim source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2233
show pim statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2235

Part 17

Access Control

Chapter 81

802.1X and MAC RADIUS Authentication Overview . . . . . . . . . . . . . . . . . 2245
Security Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . 2245
Understanding Authentication on J-EX Series Switches . . . . . . . . . . . . . . . . . . 2248
A Basic Authentication Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2248
802.1X Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2250
MAC RADIUS Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2250
Captive Portal Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2251
Static MAC Bypass of Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2252
Fallback of Authentication Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2252
802.1X for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2253
How 802.1X Authentication Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2253
802.1X Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2254
Supported Features Related to 802.1X Authentication . . . . . . . . . . . . . . . . 2254
Authentication Process Flow for EX Series Switches . . . . . . . . . . . . . . . . . . . . . 2255
Understanding Server Fail Fallback and Authentication on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2258
Understanding Dynamic VLANs for 802.1X on J-EX Series Switches . . . . . . . . 2259
Understanding Guest VLANs for 802.1X on J-EX Series Switches . . . . . . . . . . . 2259
Understanding 802.1X and RADIUS Accounting on J-EX Series Switches . . . . 2260
Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches . . . . 2261
Understanding 802.1X and VoIP on J-EX Series Switches . . . . . . . . . . . . . . . . . 2263
Understanding 802.1X and VSAs on J-EX Series Switches . . . . . . . . . . . . . . . . 2266

Chapter 82

Examples: Access Control Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2267
Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch . . . . 2267
Example: Configuring 802.1X Authentication Options When the RADIUS Server
is Unavailable to a J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2271
Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access
to Corporate Visitors on a J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . 2276
Example: Configuring Static MAC Bypass of Authentication on a J-EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2281
Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch . . 2286
Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant
Configurations on a J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2290
Example: Applying a Firewall Filter to 802.1X-Authenticated Supplicants Using
RADIUS Server Attributes on a J-EX Series Switch . . . . . . . . . . . . . . . . . . . 2296
Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2302
Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2309
Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2315
Example: Applying Firewall Filters to Multiple Supplicants on Interfaces Enabled
for 802.1X or MAC RADIUS Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 2318
Example: Setting Up Captive Portal Authentication on a J-EX Series Switch . . 2323

xliv

Table of Contents

Chapter 83

Configuring Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2329
Specifying RADIUS Server Connections on a J-EX Series Switch (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2330
Configuring 802.1X Interface Settings (CLI Procedure) . . . . . . . . . . . . . . . . . . . . 2331
Configuring 802.1X Authentication (J-Web Procedure) . . . . . . . . . . . . . . . . . . . 2332
Configuring Static MAC Bypass of Authentication (CLI Procedure) . . . . . . . . . 2334
Configuring MAC RADIUS Authentication (CLI Procedure) . . . . . . . . . . . . . . . . 2335
Configuring Server Fail Fallback (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 2337
Configuring 802.1X RADIUS Accounting (CLI Procedure) . . . . . . . . . . . . . . . . . 2339
Filtering 802.1X Supplicants Using RADIUS Server Attributes . . . . . . . . . . . . . . 2340
Configuring Match Statements on the RADIUS Server . . . . . . . . . . . . . . . . 2341
Applying a Port Firewall Filter from the RADIUS Server . . . . . . . . . . . . . . . 2343
Configuring LLDP (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344
Enabling LLDP on Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344
Configuring for Fast Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344
Adjusting LLDP Advertisement Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344
Adjusting SNMP Notification Settings of LLDP Changes . . . . . . . . . . . . . . 2345
Specifying a Management Address for the LLDP Management TLV . . . . . 2345
Configuring LLDP (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2345
Configuring LLDP-MED (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2346
Enabling LLDP-MED on Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2347
Configuring Location Information Advertised by the Switch . . . . . . . . . . . . 2347
Configuring for Fast Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2347
VSA Match Conditions and Actions for J-EX Series Switches . . . . . . . . . . . . . . 2348
Configuring Captive Portal Authentication (CLI Procedure) . . . . . . . . . . . . . . . 2350
Configuring Secure Access for Captive Portal . . . . . . . . . . . . . . . . . . . . . . . 2350
Enabling an Interface for Captive Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2351
Configuring Bypass of Captive Portal Authentication . . . . . . . . . . . . . . . . . 2351
Designing a Captive Portal Authentication Login Page on a J-EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2351

Chapter 84

Verifying 802.1X and MAC RADIUS Authentication . . . . . . . . . . . . . . . . . . 2355
Monitoring 802.1X Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2355
Verifying 802.1X Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2356

Chapter 85

Configuration Statements for Access Control . . . . . . . . . . . . . . . . . . . . . . 2359
[edit access] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 2359
[edit ethernet-switching-options] Configuration Statement Hierarchy . . . . . . 2359
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . 2362
access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2369
accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2370
accounting (Access Profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2371
accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2372
accounting-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2373
accounting-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2373
accounting-session-id-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2374
accounting-stop-on-access-deny . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2374
accounting-stop-on-access-deny . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2375
accounting-stop-on-failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2375

xlv

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

accounting-stop-on-failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2376
address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2376
address-pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2377
address-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2377
advertisement-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2378
attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2379
authentication-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2380
authentication-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2381
authentication-profile-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2382
authentication-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2383
authentication-whitelist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2383
authenticator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2384
captive-portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2385
ca-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2386
ca-value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2387
civic-based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2388
country-code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2389
custom-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2390
destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2392
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2393
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2394
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2394
dot1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2395
elin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2396
ethernet-port-type-virtual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2397
ethernet-switching-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2398
events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2400
exclude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2401
fast-start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2403
forwarding-class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404
guest-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405
hold-multiplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2406
ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2407
immediate-update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2407
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2408
interface-description-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2409
interface (Captive Portal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2410
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2411
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2412
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2413
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2414
lldp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2415
lldp-configuration-notification-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2416
lldp-med . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2417
location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2418
mac-radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2419
management-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2420
maximum-requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2420
nas-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2421

xlvi

Table of Contents

nas-port-extended-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2422
no-reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2423
options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424
order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2425
order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2425
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2426
port (RADIUS Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2426
port (TACACS+ Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2427
profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2428
ptopo-configuration-maximum-hold-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2429
ptopo-configuration-trap-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2429
quiet-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2430
quiet-period (Captive Portal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2430
radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2431
radius (Access Profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2432
radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2433
radius-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434
reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2435
retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2436
retries (Captive Portal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2436
retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2437
retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438
revert-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438
routing-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2439
secret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2439
secret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2440
secure-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2440
server (RADIUS Accounting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2441
server (TACACS+ Accounting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2441
server-fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2442
server-reject-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2443
server-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2444
server-timeout (Captive Portal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2445
session-expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2445
single-connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2446
source-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2446
source-address (NTP, RADIUS, System Logging, or TACACS+) . . . . . . . . . . . . 2447
static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2448
statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2449
supplicant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2450
supplicant-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2451
tacplus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2452
timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2453
timeout (RADIUS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2454
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2455
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2457
transmit-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2458
transmit-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2459
update-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2459

xlvii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

vlan-assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2460
vlan-nas-port-stacked-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2460
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2461
voip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2462
what . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2463

Chapter 86

Operational Commands for 802.1X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2465
clear captive-portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2466
clear dot1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2468
clear lldp neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2469
clear lldp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2470
show captive-portal authentication-failed-users . . . . . . . . . . . . . . . . . . . . . . . . 2471
show captive-portal firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2472
show captive-portal interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2474
show dot1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2477
show dot1x authentication-failed-users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2482
show dot1x firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2483
show dot1x static-mac-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2484
show ethernet-switching interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2486
show lldp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2489
show lldp local-information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2493
show lldp neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2495
show lldp remote-global-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2501
show lldp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2503
show network-access aaa statistics accounting . . . . . . . . . . . . . . . . . . . . . . . . 2505
show network-access aaa statistics authentication . . . . . . . . . . . . . . . . . . . . . 2506
show network-access aaa statistics dynamic-requests . . . . . . . . . . . . . . . . . . 2507

Part 18

Rate Limiting

Chapter 87

Rate Limiting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2511
Understanding Storm Control on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . 2511
Understanding Unknown Unicast Forwarding on J-EX Series Switches . . . . . . . 2512

Chapter 88

Example: Rate Limiting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2513
Example: Configuring Storm Control to Prevent Network Outages on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2513

Chapter 89

Configuring Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2515
Configuring Unknown Unicast Forwarding (CLI Procedure) . . . . . . . . . . . . . . . . 2515
Configuring Autorecovery From the Disabled State on Secure or Storm Control
Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2516

Chapter 90

Verifying Rate Limiting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2517
Verifying That Unknown Unicast Packets Are Forwarded to a Trunk Interface . . 2517
Verifying That the Port Error Disable Setting Is Working Correctly . . . . . . . . . . . 2518

Chapter 91

Configuration Statements for Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . 2519
[edit ethernet-switching-options] Configuration Statement Hierarchy . . . . . . 2519
action-shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2522
bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2523

xlviii

Table of Contents

disable-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2524
ethernet-switching-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2525
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2528
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2529
no-broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2529
no-unknown-unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2530
port-error-disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2531
storm-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2532
unknown-unicast-forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2533
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2534

Chapter 92

Operational Mode Commands for Rate Limiting . . . . . . . . . . . . . . . . . . . . 2535
show ethernet-switching interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2536
show ethernet-switching table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2539

Part 19

Port Security

Chapter 93

Port Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2545
Port Security for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . . . 2545
Understanding How to Protect Access Ports on J-EX Series Switches from
Common Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2546
Mitigation of Ethernet Switching Table Overflow Attacks . . . . . . . . . . . . . . 2547
Mitigation of Rogue DHCP Server Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . 2547
Protection Against ARP Spoofing Attacks . . . . . . . . . . . . . . . . . . . . . . . . . 2548
Protection Against DHCP Snooping Database Alteration Attacks . . . . . . . 2548
Protection Against DHCP Starvation Attacks . . . . . . . . . . . . . . . . . . . . . . . 2548
Understanding DHCP Snooping for Port Security on J-EX Series Switches . . . 2549
DHCP Snooping Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2549
DHCP Snooping Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2550
DHCP Server Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2551
Switch, DHCP Clients, and DHCP Server Are All on the Same VLAN . . 2551
Switch Acts as DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2553
Switch Acts as Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2553
DHCP Snooping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2554
Static IP Address Additions to the DHCP Snooping Database . . . . . . . . . . 2554
Snooping DHCP Packets That Have Invalid IP Addresses . . . . . . . . . . . . . 2554
Understanding DAI for Port Security on J-EX Series Switches . . . . . . . . . . . . . . 2555
Address Resolution Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556
ARP Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556
DAI on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556
Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX
Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2557
MAC Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2557
MAC Move Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2558
Actions for MAC Limiting and MAC Move Limiting . . . . . . . . . . . . . . . . . . . 2558
MAC Addresses That Exceed the MAC Limit or MAC Move Limit . . . . . . . . 2559
Understanding Trusted DHCP Servers for Port Security on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2559

xlix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Understanding DHCP Option 82 for Port Security on J-EX Series Switches . . . 2560
DHCP Option 82 Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2560
Suboption Components of Option 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2561
Configurations of the J-EX Series Switch That Support Option 82 . . . . . . . 2561
Switch and Clients Are on Same VLAN as DHCP Server . . . . . . . . . . . 2561
Switch Acts as Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2562
Understanding IP Source Guard for Port Security on J-EX Series Switches . . . 2563
IP Address Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564
How IP Source Guard Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564
The IP Source Guard Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564
Typical Uses of Other Junos OS Features with IP Source Guard . . . . . . . . 2565
Understanding Proxy ARP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . 2566
What Is ARP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566
Proxy ARP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566
Best Practices for Proxy ARP on J-EX Series Switches . . . . . . . . . . . . . . . . 2567

Chapter 94

Examples: Port Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2569
Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting,
and MAC Move Limiting, on a J-EX Series Switch . . . . . . . . . . . . . . . . . . . . 2569
Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC
Addresses, to Protect the Switch from Ethernet Switching Table Overflow
Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2576
Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch
from Rogue DHCP Server Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2579
Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation
Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2583
Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP
Spoofing Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2586
Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP
Snooping Database Alteration Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2590
Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series
Switch with Access to a DHCP Server Through a Second Switch . . . . . . . 2593
Example: Configuring IP Source Guard with Other J-EX Series Switch Features
to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces . . 2600
Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface
with a Voice VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2608
Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent
Between Clients and a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2615
Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay
Agent Between Clients and DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 2617
Example: Configuring Proxy ARP on a J-EX Series Switch . . . . . . . . . . . . . . . . . 2621

Chapter 95

Configuring Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2625
Configuring Port Security (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2626
Configuring Port Security (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2627
Enabling DHCP Snooping (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2630
Enabling DHCP Snooping (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 2631
Enabling a Trusted DHCP Server (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . 2632
Enabling a Trusted DHCP Server (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . 2632
Enabling Dynamic ARP Inspection (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 2633

l

Table of Contents

Enabling Dynamic ARP Inspection (J-Web Procedure) . . . . . . . . . . . . . . . . . . . 2634
Configuring MAC Limiting (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2635
Configuring MAC Limiting (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 2637
Configuring MAC Move Limiting (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 2639
Configuring MAC Move Limiting (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . 2641
Setting the none Action on an Interface to Override a MAC Limit Applied to All
Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2642
Configuring IP Source Guard (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 2643
Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2645
Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients
and DHCP Server (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2646
Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients
and DHCP Server (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2649
Configuring Proxy ARP (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2651
Configuring Autorecovery From the Disabled State on Secure or Storm Control
Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2652

Chapter 96

Verifying Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2653
Monitoring Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2653
Verifying That DHCP Snooping Is Working Correctly . . . . . . . . . . . . . . . . . . . . . 2654
Verifying That a Trusted DHCP Server Is Working Correctly . . . . . . . . . . . . . . . . 2655
Verifying That DAI Is Working Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2656
Verifying That MAC Limiting Is Working Correctly . . . . . . . . . . . . . . . . . . . . . . . . 2657
Verifying That MAC Limiting for Dynamic MAC Addresses Is Working
Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2657
Verifying That Allowed MAC Addresses Are Working Correctly . . . . . . . . . 2658
Verifying Results of Various Action Settings When the MAC Limit Is
Exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2658
Customizing the Ethernet Switching Table Display to View Information for
a Specific Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2660
Verifying That MAC Move Limiting Is Working Correctly . . . . . . . . . . . . . . . . . . . 2661
Verifying That IP Source Guard Is Working Correctly . . . . . . . . . . . . . . . . . . . . . 2662
Verifying That Proxy ARP Is Working Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . 2662
Verifying That the Port Error Disable Setting Is Working Correctly . . . . . . . . . . 2663

Chapter 97

Troubleshooting Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2665
Troubleshooting Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2665
MAC Addresses That Exceed the MAC Limit or MAC Move Limit Are Not
Listed in the Ethernet Switching Table . . . . . . . . . . . . . . . . . . . . . . . . . 2665
Multiple DHCP Server Packets Have Been Received on Untrusted
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2665

Chapter 98

Configuration Statements for Port Security . . . . . . . . . . . . . . . . . . . . . . . . 2667
[edit ethernet-switching-options] Configuration Statement Hierarchy . . . . . . 2667
[edit forwarding-options] Configuration Statement Hierarchy . . . . . . . . . . . . . 2669
allowed-mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2671
arp-inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2672
circuit-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2673
dhcp-option82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2674

li

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

dhcp-snooping-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2675
dhcp-trusted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2676
disable-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2677
ethernet-switching-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2678
examine-dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2681
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2682
ip-source-guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2683
mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2683
mac-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2684
mac-move-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2685
no-allowed-mac-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2686
no-gratuitous-arp-request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2687
port-error-disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2688
prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2689
prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2690
proxy-arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2691
remote-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2692
secure-access-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2693
static-ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2694
timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2695
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2696
use-interface-description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2698
use-string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2699
use-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2700
vendor-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2701
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2702
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2703
write-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2704

Chapter 99

Operational Mode Commands for Port Security . . . . . . . . . . . . . . . . . . . . 2705
clear arp inspection statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2706
clear dhcp snooping binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2707
clear dhcp snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2708
show arp inspection statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2709
show dhcp snooping binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2710
show dhcp snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2711
show ethernet-switching table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2712
show ip-source-guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2716
show system statistics arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2718

Part 20

Routing Policy and Packet Filtering (Firewall Filters)

Chapter 100

Firewall Filters—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2721
Firewall Filters for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . . . 2721
Firewall Filter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2721
Firewall Filter Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2722
Firewall Filter Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2723
Understanding Planning of Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2724
Understanding Firewall Filter Processing Points for Bridged and Routed Packets
on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2726

lii

Table of Contents

Understanding How Firewall Filters Control Packet Flows . . . . . . . . . . . . . . . . . 2727
Firewall Filter Match Conditions and Actions for J-EX Series Switches . . . . . . . 2728
Understanding How Firewall Filters Are Evaluated . . . . . . . . . . . . . . . . . . . . . . . 2746
Understanding Firewall Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . 2748
Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2748
Numeric Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2748
Interface Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2749
IP Address Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2749
MAC Address Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2750
Bit-Field Filter Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2750
Understanding How Firewall Filters Test a Packet's Protocol . . . . . . . . . . . . . . 2752
Understanding the Use of Policers in Firewall Filters . . . . . . . . . . . . . . . . . . . . . 2752
Understanding Filter-Based Forwarding for J-EX Series Switches . . . . . . . . . . . 2753

Chapter 101

Examples of Firewall Filters Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2755
Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX
Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2755
Example: Using Filter-Based Forwarding to Route Application Traffic to a Security
Device on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2773

Chapter 102

Configuring Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2779
Configuring Firewall Filters (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2779
Configuring a Firewall Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2779
Applying a Firewall Filter to a Port on a Switch . . . . . . . . . . . . . . . . . . . . . . 2782
Applying a Firewall Filter to a VLAN on a Network . . . . . . . . . . . . . . . . . . . 2782
Applying a Firewall Filter to a Layer 3 (Routed) Interface . . . . . . . . . . . . . . 2783
Configuring Firewall Filters (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 2784
Configuring Policers to Control Traffic Rates (CLI Procedure) . . . . . . . . . . . . . . 2788
Configuring Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2789
Specifying Policers in a Firewall Filter Configuration . . . . . . . . . . . . . . . . . . 2790
Applying a Firewall Filter That Is Configured with a Policer . . . . . . . . . . . . 2790
Assigning Multifield Classifiers in Firewall Filters to Specify Packet-Forwarding
Behavior (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2791
Configuring Routing Policies (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 2792

Chapter 103

Verifying Firewall Filter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2799
Verifying That Firewall Filters Are Operational . . . . . . . . . . . . . . . . . . . . . . . . . . 2799
Verifying That Policers Are Operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2800
Monitoring Firewall Filter Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2800
Monitoring Traffic for All Firewall Filters and Policers That Are Configured
on the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2801
Monitoring Traffic for a Specific Firewall Filter . . . . . . . . . . . . . . . . . . . . . . . 2801
Monitoring Traffic for a Specific Policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2801

Chapter 104

Troubleshooting Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2803
Troubleshooting Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2803
Firewall Filter Configuration Returns a No Space Available in TCAM
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2803

liii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 105

Configuration Statements for Firewall Filters . . . . . . . . . . . . . . . . . . . . . . 2805
[edit firewall] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 2805
Firewall Filter Configuration Statements Supported by the Junos OS for J-EX
Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2806
apply-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2809
as-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2809
as-path-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2810
bandwidth-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2811
burst-size-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2812
community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2813
condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2815
damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2816
dynamic-db . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2817
family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2818
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2819
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2820
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2821
filter-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2821
firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2822
from . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2823
if-exceeding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2824
interface-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2825
policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2826
policy-statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2827
prefix-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2829
routing-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2830
term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2831
then . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2832
then . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2833

Chapter 106

Operational Mode Commands for Firewall Filters . . . . . . . . . . . . . . . . . . . 2835
clear firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2836
clear firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2837
show firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2838
show firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2841
show firewall log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2844
show interfaces filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2846
show interfaces policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2848
show policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2850
show policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2852
show policy conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2854
test policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2856

liv

Table of Contents

Part 21

Class of Service

Chapter 107

Class of Service (CoS)—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2859
Junos OS CoS for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . . 2860
How Junos OS CoS Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2860
Default CoS Behavior on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . 2861
Understanding Junos OS CoS Components for J-EX Series Switches . . . . . . . 2862
Code-Point Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2862
Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2862
Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2862
Forwarding Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2863
Tail Drop Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2863
Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2863
Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2863
Understanding CoS Code-Point Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2864
Default Code-Point Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2864
Understanding CoS Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2867
Behavior Aggregate Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2867
Default Behavior Aggregate Classification . . . . . . . . . . . . . . . . . . . . . . 2868
Multifield Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2869
Understanding CoS Forwarding Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2870
Default Forwarding Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2870
Understanding CoS Tail Drop Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2872
Understanding CoS Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2873
Default Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2873
Transmission Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2874
Scheduler Buffer Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2874
Priority Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2874
Scheduler Drop-Profile Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2875
Scheduler Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2875
Understanding CoS Two-Color Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2876
Understanding CoS Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2876
How Rewrite Rules Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2876
Default Rewrite Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2877
Understanding Port Shaping and Queue Shaping for CoS on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2878
Port Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2878
Queue Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2878
Understanding Junos OS EZQoS for CoS Configurations on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2879
Understanding Using CoS with MPLS Networks on J-EX Series Switches . . . . 2880
Guidelines for Using CoS Classifiers on CCCs . . . . . . . . . . . . . . . . . . . . . . . 2880
Using CoS Classifiers with IP over MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 2881
Default Classifiers and Default Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . 2881
EXP Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2881
Policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2882
Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2882

lv

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 108

Examples: CoS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2883
Example: Configuring CoS on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . 2883
Example: Combining CoS with MPLS on J-EX Series Switches . . . . . . . . . . . . . 2898

Chapter 109

Configuring CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2911
Configuring CoS (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2911
Defining CoS Code-Point Aliases (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . 2912
Defining CoS Code-Point Aliases (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . 2914
Defining CoS Classifiers (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2914
Defining CoS Classifiers (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2916
Defining CoS Forwarding Classes (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . 2918
Defining CoS Forwarding Classes (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . 2918
Defining CoS Schedulers (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2920
Defining CoS Schedulers (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2920
Defining CoS Scheduler Maps (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . 2923
Defining CoS Drop Profiles (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 2923
Configuring CoS Tail Drop Profiles (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 2925
Defining CoS Rewrite Rules (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2925
Defining CoS Rewrite Rules (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 2926
Assigning CoS Components to Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . 2928
Assigning CoS Components to Interfaces (J-Web Procedure) . . . . . . . . . . . . . 2928
Configuring Junos OS EZQoS for CoS (CLI Procedure) . . . . . . . . . . . . . . . . . . . 2930
Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2931
Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect
(CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2932

Chapter 110

Verifying CoS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2935
Monitoring CoS Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2935
Monitoring CoS Forwarding Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2936
Monitoring Interfaces That Have CoS Components . . . . . . . . . . . . . . . . . . . . . . 2937
Monitoring CoS Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2938
Monitoring CoS Scheduler Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2939
Monitoring CoS Value Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2940
Monitoring CoS Drop Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2941

Chapter 111

Configuration Statements for CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2943
[edit class-of-service] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . 2943
broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2945
buffer-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2946
class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2947
class-of-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2948
classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2950
code-point-aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2951
code-points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2951
drop-profile-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2952
dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2953
dscp-ipv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2954
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2955
exp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2956

lvi

Table of Contents

family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2957
forwarding-class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2958
forwarding-classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2959
ieee-802.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2960
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2961
inet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2962
inet-precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2963
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2964
loss-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2965
multi-destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2966
policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2967
priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2968
protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2968
rewrite-rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2969
scheduler-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2970
scheduler-maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2971
schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2972
shaping-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2973
shared-buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2974
transmit-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2975
unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2976

Chapter 112

Operational Mode Commands for CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2977
show class-of-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2978
show class-of-service classifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2983
show class-of-service code-point-aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2985
show class-of-service drop-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2987
show class-of-service forwarding-class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2989
show class-of-service interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2991
show pfe statistics traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2994
show pfe statistics traffic cpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2997
show pfe statistics traffic egress-queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3001
show pfe statistics traffic multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3003

Part 22

Power over Ethernet

Chapter 113

Power over Ethernet (PoE)—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3009
PoE and J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3009
PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3009
PoE Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3009
PoE Power Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3009
Power Management Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3010
PoE Interface Power Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3011
PoE Configuration and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3011

Chapter 114

Examples: PoE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3013
Example: Configuring PoE Interfaces on a J-EX Series Switch . . . . . . . . . . . . . . 3013
Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3015

lvii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 115

Configuring PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3021
Configuring PoE (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3021
Configuring PoE (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3023

Chapter 116

Verifying PoE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3025
Monitoring PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3025
Monitoring PoE Power Consumption (CLI Procedure) . . . . . . . . . . . . . . . . . . . . 3026
PoE Power Consumption for the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . 3026
Current Power Consumption for PoE Interfaces . . . . . . . . . . . . . . . . . . . . . 3026
Power Consumption for PoE Interfaces over Time . . . . . . . . . . . . . . . . . . . 3027
Verifying PoE Configuration and Status (CLI Procedure) . . . . . . . . . . . . . . . . . . 3028
Number of PoE Ports on the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3028
PoE Controller Configuration and Status . . . . . . . . . . . . . . . . . . . . . . . . . . 3028
PoE Interface Configuration and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 3029
PoE SNMP Trap Generation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3029

Chapter 117

Troubleshooting PoE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3031
Troubleshooting PoE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3031

Chapter 118

Configuration Statements for PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3033
[edit poe] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 3033
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3034
duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3035
fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3036
guard-band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3037
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3038
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3039
management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3040
maximum-power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3041
notification-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3042
priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3043
telemetries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3044

Chapter 119

Operational Mode Commands for PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3045
show poe controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3046
show poe interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3048
show poe notification-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3050
show poe telemetries interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3052

Part 23

MPLS

Chapter 120

MPLS—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3057
Junos OS MPLS for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . 3057
Benefits of MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3057
Additional Benefits of MPLS and Traffic Engineering . . . . . . . . . . . . . . . . . 3058
Understanding Junos OS MPLS Components for J-EX Series Switches . . . . . . 3059
Provider Edge Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3059
MPLS Protocol and Label Switched Paths . . . . . . . . . . . . . . . . . . . . . 3059
Circuit Cross-Connect for Customer-Edge Interfaces . . . . . . . . . . . . . 3059

lviii

Table of Contents

IP over MPLS For Customer-Edge Interfaces . . . . . . . . . . . . . . . . . . . 3060
Provider Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3060
Components Required for All Switches in the MPLS Network . . . . . . . . . . 3060
Routing Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3061
Traffic Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3061
MPLS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3061
RSVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3061
Family MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3062
Understanding MPLS and Path Protection on J-EX Series Switches . . . . . . . . 3063
Understanding Using CoS with MPLS Networks on J-EX Series Switches . . . . 3064
Guidelines for Using CoS Classifiers on CCCs . . . . . . . . . . . . . . . . . . . . . . . 3064
Using CoS Classifiers with IP over MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 3065
Default Classifiers and Default Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . 3065
EXP Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3065
Policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3066
Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3066
Understanding MPLS Label Operations on J-EX Series Switches . . . . . . . . . . . 3067
MPLS Label Switched Paths and MPLS Labels on J-EX Series Switches . . 3067
Reserved Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3068
MPLS Label Operations on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . 3068
Ultimate and Penultimate Hop Popping . . . . . . . . . . . . . . . . . . . . . . . . . . . 3069

Chapter 121

Example of MPLS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3071
Example: Configuring MPLS on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . 3071
Example: Combining CoS with MPLS on J-EX Series Switches . . . . . . . . . . . . . 3085

Chapter 122

Configuring MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3097
Configuring Path Protection in an MPLS Network (CLI Procedure) . . . . . . . . . . 3097
Configuring the Primary Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3099
Configuring the Secondary Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3099
Configuring the Revert Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3100
Configuring MPLS on Provider Switches (CLI Procedure) . . . . . . . . . . . . . . . . . 3102
Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3104
Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect
(CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3105
Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) . . 3106
Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3107
Configuring the Ingress PE Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3108
Configuring the Egress PE Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3109
Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3111

Chapter 123

Verifying MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3115
Verifying That MPLS Is Working Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3115
Verifying the Physical Layer on the Switches . . . . . . . . . . . . . . . . . . . . . . . . 3115
Verifying the Routing Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116
Verifying the Core Interfaces Being Used for the MPLS Traffic . . . . . . . . . . . 3116
Verifying RSVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116

lix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Verifying the Assignment of Interfaces for MPLS Label Operations . . . . . . . 3117
Verifying the Status of the CCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3117
Verifying Path Protection in an MPLS Network . . . . . . . . . . . . . . . . . . . . . . . . . . 3118
Verifying the Primary Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3118
Verifying the RSVP-Enabled Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3119
Verifying a Secondary Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3119

Chapter 124

Configuration Statements for MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3121
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . 3121
connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3128
exp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3129
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3130
label-switched-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3131
mpls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3132
path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3133
policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3134
primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3134
remote-interface-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3135
revert-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3136
rsvp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3137
secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3137
standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3138
traffic-engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3138

Chapter 125

Operational Mode Commands for MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 3139
clear mpls lsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3140
clear rsvp session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3142
clear rsvp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3144
ping mpls l2circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3145
ping mpls l2vpn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3147
ping mpls l3vpn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3149
ping mpls ldp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3151
ping mpls lsp-end-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3153
ping mpls rsvp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3155
request mpls lsp adjust-autobandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3160
show connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3161
show connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3164
show link-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3168
show link-management peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3171
show link-management routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3173
show link-management statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3176
show link-management te-link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3178
show mpls admin-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3180
show mpls call-admission-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3181
show mpls cspf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3183
show mpls diffserv-te . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3185
show mpls interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3187
show mpls interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3188
show mpls lsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3189
show mpls path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3198

lx

Table of Contents

show route forwarding-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3199
show rsvp interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3206
show rsvp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3211
show rsvp session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3216
show rsvp session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3221
show rsvp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3229
show rsvp version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3233
show ted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3235
show ted link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3239
show ted protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3241

Part 24

Network Management and Monitoring

Chapter 126

Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3245
Port Mirroring—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3245
Understanding Port Mirroring on J-EX Series Switches . . . . . . . . . . . . . . . . 3245
Port Mirroring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3245
Port Mirroring Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3247
Examples: Port Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3249
Example: Configuring Port Mirroring for Local Monitoring of Employee
Resource Use on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . 3249
Example: Configuring Port Mirroring for Remote Monitoring of Employee
Resource Use on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . 3254
Configuring Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3260
Configuring Port Mirroring to Analyze Traffic (CLI Procedure) . . . . . . . . . . 3260
Configuring Port Mirroring for Local Traffic Analysis . . . . . . . . . . . . . . . 3261
Configuring Port Mirroring for Remote Traffic Analysis . . . . . . . . . . . . . 3261
Filtering the Traffic Entering an Analyzer . . . . . . . . . . . . . . . . . . . . . . . 3262
Configuring Port Mirroring to Analyze Traffic (J-Web Procedure) . . . . . . . . 3263
Verifying Port Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3265
Verifying Input and Output for Port Mirroring Analyzers on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3265
Configuration Statements for Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . 3266
[edit ethernet-switching-options] Configuration Statement Hierarchy . . . 3267
analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3270
egress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3271
ethernet-switching-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3272
ingress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3275
input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3276
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3277
loss-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3278
output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3279
ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3280
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3280
Operational Mode Commands for Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . 3280
show analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3281

lxi

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 127

sFlow Monitoring Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3283
sFlow Technology—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3283
Understanding How to Use sFlow Technology for Network Monitoring on a
J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3283
Sampling Mechanism and Architecture of sFlow Technology on J-EX
Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3283
Adaptive Sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3284
sFlow Agent Address Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3285
Example: sFlow Technology Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3285
Example: Configuring sFlow Technology to Monitor Network Traffic on J-EX
Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3285
Configuring sFlow Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3290
Configuring sFlow Technology for Network Monitoring (CLI Procedure) . . 3290
Configuration Statements for sFlow Technology . . . . . . . . . . . . . . . . . . . . . . . . 3291
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . 3292
collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3299
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3299
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3300
polling-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3301
sample-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3302
sflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3303
udp-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3304
Operational Mode Commands for sFlow Technology . . . . . . . . . . . . . . . . . . . . 3304
show sflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3305
show sflow collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3307
show sflow interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3308

Chapter 128

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3309
Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3309
Configuring SNMP (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3309
Configuration Statements for SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3312
[edit snmp] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . 3312
address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3313
address-mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3313
agent-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3314
alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3315
authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3316
bucket-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3316
categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3317
client-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3317
client-list-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3318
clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3318
commit-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3319
community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3320
community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3321
community-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3322
contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3323
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3323
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3324

lxii

Table of Contents

destination-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3324
engine-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3325
event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3326
falling-event-index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3326
falling-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3327
falling-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3328
falling-threshold-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3328
filter-duplicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3329
filter-interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3329
group (Configuring Group Name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3330
group (Defining Access Privileges for an SNMPv3 Group) . . . . . . . . . . . . . 3330
health-monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3331
history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3332
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3333
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3333
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3334
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3334
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3335
location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3335
logical-system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3336
message-processing-model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3336
name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3337
nonvolatile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3337
notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3338
notify-filter (Configuring the Profile Name) . . . . . . . . . . . . . . . . . . . . . . . . 3338
notify-filter (Applying to the Management Target) . . . . . . . . . . . . . . . . . . . 3339
notify-view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3339
oid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3340
oid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3340
owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3341
parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3341
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3342
read-view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3342
request-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3343
rising-event-index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3343
rising-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3344
rising-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3345
rmon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3345
rmon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3346
routing-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3347
routing-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3348
sample-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3348
security-level (Generating SNMP Notifications) . . . . . . . . . . . . . . . . . . . . . 3349
security-level (Defining Access Privileges) . . . . . . . . . . . . . . . . . . . . . . . . . 3349
security-model (Access Privileges) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3350
security-model (Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3350
security-model (SNMP Notifications) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3351
security-name (Security Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3351
security-name (Community String) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3352

lxiii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

security-name (SNMP Notifications) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3353
security-to-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3353
snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3354
snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3354
snmp-community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3355
source-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3355
startup-alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3356
syslog-subtag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3356
tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3357
tag-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3357
target-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3358
target-parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3359
targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3359
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3360
trap-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3362
trap-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3363
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3363
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3364
v3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3365
vacm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3367
variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3368
version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3368
view (Configuring a MIB View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3369
view (Associating a MIB View with a Community) . . . . . . . . . . . . . . . . . . . 3370
write-view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3370
Operational Mode Commands for SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3370
clear snmp rmon history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3371
clear snmp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3372
request snmp spoof-trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3374
show snmp health-monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3380
show snmp inform-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3387
show snmp rmon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3388
show snmp rmon history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3392
show snmp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3395
show snmp v3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3399

Chapter 129

Real-Time Performance Monitoring (RPM) . . . . . . . . . . . . . . . . . . . . . . . . 3403
RPM—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3403
Understanding Real-Time Performance Monitoring on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3404
RPM Packet Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3404
Tests and Probe Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3404
Hardware Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3405
Limitations of RPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3407
Configuring Real-Time Performance Monitoring (RPM) . . . . . . . . . . . . . . . . . . 3407
Configuring Real-Time Performance Monitoring (J-Web Procedure) . . . . 3407
Configuring the Interface for RPM Timestamping for Client/Server on a J-EX
Series Switch (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3414

lxiv

Table of Contents

Verifying Real-Time Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 3416
Viewing Real-Time Performance Monitoring Information . . . . . . . . . . . . . . 3416
Operational Mode Commands for Real-Time Performance Monitoring . . . . . . 3416
show services rpm active-servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3417
show services rpm history-results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3418
show services rpm probe-results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3421

Chapter 130

Ethernet OAM Link Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3427
Ethernet OAM Link Fault Management—Overview . . . . . . . . . . . . . . . . . . . . . . . 3427
Understanding Ethernet OAM Link Fault Management for a J-EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3427
Example of Ethernet OAM Link Fault Management Configuration . . . . . . . . . . 3428
Example: Configuring Ethernet OAM Link Fault Management on J-EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3428
Configuring Ethernet OAM Link Fault Management . . . . . . . . . . . . . . . . . . . . . . 3431
Configuring Ethernet OAM Link Fault Management (CLI Procedure) . . . . . 3431
Configuration Statements for Ethernet OAM Link Fault Management . . . . . . . 3434
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . 3434
action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3440
action-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3441
allow-remote-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3442
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3443
event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3445
event-thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3445
frame-error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3446
frame-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3446
frame-period-summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3447
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3448
link-adjacency-loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3449
link-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3449
link-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3450
link-event-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3450
link-fault-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3451
negotiation-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3452
no-allow-link-events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3452
oam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3453
pdu-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3455
pdu-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3455
remote-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3456
symbol-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3456
syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3457
Operational Mode Commands for Ethernet OAM Link Fault Management . . . 3457
show oam ethernet link-fault-management . . . . . . . . . . . . . . . . . . . . . . . 3458

lxv

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Chapter 131

Ethernet OAM Connectivity Fault Management . . . . . . . . . . . . . . . . . . . . . 3463
Ethernet OAM Connectivity Fault Management—Overview . . . . . . . . . . . . . . . 3463
Understanding Ethernet OAM Connectivity Fault Management for a J-EX
Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3463
Example of Ethernet OAM Connectivity Fault Management Configuration . . . 3464
Example: Configuring Ethernet OAM Connectivity Fault Management on
J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3465
Configuring Ethernet OAM Connectivity Fault Management . . . . . . . . . . . . . . . 3468
Configuring Ethernet OAM Connectivity Fault Management (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3468
Creating the Maintenance Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3469
Configuring the Maintenance Domain MIP Half Function . . . . . . . . . . 3469
Creating a Maintenance Association . . . . . . . . . . . . . . . . . . . . . . . . . . 3470
Configuring the Continuity Check Protocol . . . . . . . . . . . . . . . . . . . . . 3470
Configuring a Maintenance Association End Point . . . . . . . . . . . . . . . 3470
Configuring a Connectivity Fault Management Action Profile . . . . . . . 3471
Configuring the Linktrace Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3472
Configuration Statements for Ethernet OAM Connectivity Fault
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3472
[edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . 3472
action-profile (Applying to OAM CFM, for J-EX Series Switch Only) . . . . . 3479
age (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3480
auto-discovery (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . 3480
connectivity-fault-management (J-EX Series Switch Only) . . . . . . . . . . . . 3481
continuity-check (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . 3482
direction (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3482
hold-interval (OAM CFM, for J-EX Series Switch Only) . . . . . . . . . . . . . . . . 3483
interface (OAM CFM, for J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . 3483
interval (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3484
level (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3485
linktrace (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3485
loss-threshold (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 3486
maintenance-association (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . 3487
maintenance-domain (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . 3488
mep (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3489
mip-half-function (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . 3490
name-format (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3491
path-database-size (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . 3491
remote-mep (J-EX Series Switch Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3492
Operational Mode Commands for Ethernet OAM Connectivity Fault
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3492
clear oam ethernet connectivity-fault-management statistics . . . . . . . . . 3493
show oam ethernet connectivity-fault-management forwarding-state . . 3494
show oam ethernet connectivity-fault-management interfaces . . . . . . . . 3498
show oam ethernet connectivity-fault-management linktrace
path-database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3504
show oam ethernet connectivity-fault-management mep-database . . . 3506
show oam ethernet connectivity-fault-management mip . . . . . . . . . . . . . 3512

lxvi

Table of Contents

Chapter 132

Monitoring General Network Traffic and Hosts . . . . . . . . . . . . . . . . . . . . . . 3513
Monitoring Hosts Using the J-Web Ping Host Tool . . . . . . . . . . . . . . . . . . . . . . . 3513
Monitoring Network Traffic Using Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . 3515

Chapter 133

Configuration Statements for General Network Management and
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3517
archive-sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3517
class-usage-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3518
counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3519
destination-classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3519
fields (for Interface Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3520
file (Associating with a Profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3521
file (Configuring a Log File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3522
files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3522
filter-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3523
interface-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3524
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3525
mib-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3526
object-names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3526
operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3527
routing-engine-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3527
size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3528
source-classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3528
start-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3529
transfer-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3529

Chapter 134

Operational Mode Commands for General Network Management and
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3531
monitor traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3532
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3539
show snmp mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3542
traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3544

Part 25

Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3549

lxvii

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

lxviii

About This Guide
•

How to Use This Guide on page lxix

•

Downloading Software on page lxx

•

Documentation Conventions on page lxx

•

Repair and Warranty on page lxxi

•

Requesting Technical Support on page lxxi

How to Use This Guide
This guide, the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for
Junos OS, provides the following information about Juniper Networks Junos Operating
System (Junos OS) for J-EX Series switches: software feature descriptions, configuration
examples and tasks, management and monitoring instructions, and reference information.
To download the Dell PowerConnect J-EX Series documentation listed in Table 1 on
page lxix, see the following Dell support website:
http://www.support.dell.com/manuals

Table 1: List of J-EX Series Guides for Junos OS Release 10.3
Title

Description

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

Dell PowerConnect J-Series Ethernet Switch Complete
Software Guide for Junos OS

Software feature descriptions, configuration examples, and tasks for
Juniper Networks Junos OS for J-EX Series switches

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/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the release notes.

lxix

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Downloading Software
You can download Junos OS for J-EX Series switches from the Download Software area
at http://www.support.dell.com/ . To download the software, you must have a Juniper
Networks user account. For information about obtaining an account, see
http://www.support.dell.com.

Documentation Conventions
Table 2: 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.

Table 3: 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

Italic text like this

Plain text like this

< > (angle brackets)

lxx

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

Enclose optional keywords or variables.

stub ;

[edit]
root@# set system domain-name
domain-name

About This Guide

Table 3: Text and Syntax Conventions (continued)
Convention

Description

Examples

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

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

(string1 | string2 | string3)

[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 the “Getting Help” chapter in your hardware guide.

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.

lxxi

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

lxxii

PART 1

Junos OS for J-EX Series Switches Product
Overview
•

Software Overview on page 3

•

Supported Hardware on page 25

1

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

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 13

•

Layer 3 Protocols Not Supported on J-EX Series Switches on page 14

•

Security Features for J-EX Series Switches Overview on page 16

•

High Availability Features for J-EX Series Switches Overview on page 18

•

Understanding Software Infrastructure and Processes on page 22

J-EX Series Switch Software Features Overview
The following tables list the software features for J-EX Series Switches and the switches
on which they are supported:
•

Table 4 on page 4—Access Control Features

•

Table 5 on page 4—Administration Features

•

Table 6 on page 4—Class-of-Service (CoS) Features

•

Table 7 on page 5—High Availability and Resiliency Features

•

Table 8 on page 6—Interfaces Features

•

Table 9 on page 7—IP Address Management Features

•

Table 10 on page 7—IPv6 Features

•

Table 11 on page 7—Layer 2 Network Protocols Features

•

Table 12 on page 8—Layer 3 Protocols Features

•

Table 13 on page 9—MPLS Features

•

Table 14 on page 10—Multicast Features

•

Table 15 on page 10—Network Management and Monitoring Features

•

Table 16 on page 11—Port Security Features

•

Table 17 on page 12—System Management Features

3

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 4: Access Control Features
Feature

J-EX4200 Switches

J-EX8200 Switches

802.1X authentication

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Authentication fallback

Junos OS 10.3R1

Not supported

Captive portal authentication

Junos OS 10.2 or earlier

Not supported

Dynamic allocation of ternary content addressable
memory (TCAM) memory to firewall filters

Junos OS 10.2 or earlier

Junos OS 10.3R1

Dynamic firewall filters for 802.1X authentication

Junos OS 10.2 or earlier

Not supported

Firewall filters and rate limiting

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

For a list of supported firewall filter match conditions and actions, see “Firewall Filter Match Conditions and Actions for J-EX
Series Switches” on page 2728.
Firewall filters on LAGs

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Firewall filter on loopback interface

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Firewall filters with IPv6

Junos OS 10.2 or earlier

Junos OS 10.3R1

MAC RADIUS authentication

Junos OS 10.2 or earlier

Junos OS 10.3R1

Policing

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Server fail fallback

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

TACACS+

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Table 5: Administration Features
Feature

J-EX4200 Switches

J-EX8200 Switches

System logging (syslog) over IPv6

Junos OS 10.2 or earlier

Not supported

System logging (syslog) over IPv4

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

System snapshot

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Table 6: Class-of-Service (CoS) Features

4

Feature

J-EX4200 Switches

J-EX8200 Switches

Class of service (CoS)—Class-based queuing with
prioritization

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Chapter 1: Software Overview

Table 6: Class-of-Service (CoS) Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

CoS—DSCP, IEEE 801.p, and IP precedence packet rewrites
on routed VLAN interfaces (RVIs)

Junos OS 10.2 or earlier

Not supported

CoS—Interface-specific classifiers on routed VLAN interfaces
(RVIs)

Junos OS 10.2 or earlier

Not supported

CoS—multidestination

Not applicable

Junos OS 10.2 or earlier

CoS support on LAGs

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

CoS support on routed VLAN interfaces (RVIs)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Interface-specific CoS rewrite rules

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Junos OS EZQoS for CoS

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Port shaping and queue shaping

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Remarking of bridged packets

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Table 7: High Availability and Resiliency Features
Feature

J-EX4200 Switches

J-EX8200 Switches

Graceful protocol restart for BGP

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Graceful protocol restart for IS-IS

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Graceful protocol restart for OSPF

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Graceful Routing Engine switchover (GRES) for J-EX4200
Virtual Chassis configurations

Junos OS 10.2 or earlier

Not applicable

GRES for ARP entries

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

GRES for the forwarding database

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

GRES for port security

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Link Aggregation Control Protocol (LACP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

LACP support for dual-homing applications in data centers

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Link aggregation groups (LAGs)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Link aggregation groups (LAGs) over Virtual Chassis ports
(VCPs)

Junos OS 10.2 or earlier

Not applicable

5

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 7: High Availability and Resiliency Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

Redundant trunk groups

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Virtual Router Redundancy Protocol (VRRP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

VRRP for IPv6 (except authentication type and
authentication key)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Virtual Chassis

Junos OS 10.2 or earlier

Not applicable

Junos OS 10.2 or earlier

Not applicable

Junos OS 10.2 or earlier

Not applicable

Junos OS 10.2 or earlier

Not applicable

Feature

J-EX4200 Switches

J-EX8200 Switches

Digital optical monitoring (DOM)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Interface-range support

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Power over Ethernet (PoE)

Junos OS 10.2 or earlier

Not applicable

Power over Ethernet Plus (PoE+)

Not supported

Not supported

PoE power management mode

Junos OS 10.2 or earlier

Not supported

Unicast reverse-path forwarding (RPF)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

VLAN-tagged Layer 3 subinterfaces

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

•

Atomic software upgrade

•

Fast failover

•

Split and merge

Virtual Chassis
•

Automatic software update on prospective member
switches

•

Front-panel configuration of uplink module ports as
Virtual Chassis ports (VCPs)

Virtual Chassis
•

Autoprovisioning of Virtual Chassis ports (VCPs)

Virtual Chassis
•

Support for SFP uplink module ports

Table 8: Interfaces Features

6

Chapter 1: Software Overview

Table 9: IP Address Management Features
Feature

J-EX4200 Switches

J-EX8200 Switches

DHCP server and relay with option 82 for Layer 2 VLANs

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

DHCPv6 and IPv6 DNS

Junos OS 10.2 or earlier

Not supported

Local DHCP server

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Static addresses

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

J-EX4200 Switches

J-EX8200 Switches

Table 10: IPv6 Features
Feature

A separate software license is required for IPv6. See “Understanding Software Licenses for the J-EX Series Switch” on page 65.
IPv6 (except multicast protocols)

Junos OS 10.2 or earlier

Not supported

IPv6 CoS (multi-field classification and rewrite, scheduling
based on TC),

Junos OS 10.2 or earlier

Not supported

IPv6 multicast protocols (PIM, MLDv1/v2)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IPv6 Management and Services

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IPv6 Path MTU Discovery

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Feature

J-EX4200 Switches

J-EX8200 Switches

802.1Q VLAN tagging

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

BPDU protection for spanning-tree protocols

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

GARP VLAN Registration Protocol (GVRP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Layer 2 protocol tunneling (L2PT)

Junos OS 10.2 or earlier

Not supported

Link Layer Discovery Protocol (LLDP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Link Layer Discovery Protocol-Media Endpoint Discovery
(LLDP-MED) with voice over IP (VoIP) integration

Junos OS 10.2 or earlier

Not supported

Loop protection for spanning-tree protocols

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

MAC-based VLAN

Junos OS 10.2 or earlier

Not supported

Multiple VLAN Registration Protocol (MVRP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Table 11: Layer 2 Network Protocols Features

7

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 11: Layer 2 Network Protocols Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

Private VLANs (PVLANs)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Proxy ARP—restricted

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Proxy ARP—unrestricted

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Proxy ARP per VLAN

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Q-in-Q tunneling

Junos OS 10.2 or earlier

Not supported

Q-in-Q VLAN extended support for multiple S-VLANs per
access interface, firewall-filter-based VLAN assignment,
and routed VLAN interfaces (RVIs)

Junos OS 10.2 or earlier

Not supported

Root protection for spanning-tree protocols

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Spanning tree:

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

RSTP and VSTP concurrent configuration

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Storm control

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Unknown Layer 2 unicast forwarding

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

VLAN ID translation

Junos OS 10.2 or earlier

Not supported

VLAN range

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Feature

J-EX4200 Switches

J-EX8200 Switches

Bidirectional Forwarding Detection (BFD)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Border Gateway Protocol (BGP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

•

Spanning Tree Protocol (STP)

•

Rapid Spanning Tree Protocol (RSTP)

•

Multiple Spanning Tree Protocol (MSTP)

Spanning tree:
•

VLAN Spanning Tree Protocol (VSTP)

Table 12: Layer 3 Protocols Features

A separate software license is required for BGP and MBGP. See “Understanding Software Licenses for the J-EX Series Switch”
on page 65.
Filter-based forwarding

8

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Chapter 1: Software Overview

Table 12: Layer 3 Protocols Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

Intermediate System-to-Intermediate System (IS-IS)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

A separate software license is required for IS-IS. See “Understanding Software Licenses for the J-EX Series Switch” on page 65.
IPv6 protocols: Open Shortest Path First version 3 (OSPFv3),
RIPng, IS-IS for IPv6, IPv6 BGP

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IPv6 Layer 3 multicast protocols

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Jumbo frames on routed VLAN interfaces (RVIs)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Multicast Source Discovery Protocol (MSDP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

See the Junos OS Routing Protocols Configuration Guide at //www.juniper.net/techpubs/software/junos/index.html.
OSPF Multitopology Routing (MT-OSPF)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

See the Junos OS Routing Protocols Configuration Guide at //www.juniper.net/techpubs/software/junos/index.html.
OSPFv2

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

OSPF IPsec support

Junos OS 10.3R1

Not supported

Routed VLAN interfaces (RVIs)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Routing Information Protocol version 1 (RIPv1) and RIPv2

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Static routes

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Virtual routing and forwarding (VRF) with IPv4—virtual
routing instances

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

VRF with IPv4—virtual routing instances for multicast traffic

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

VRF with IPv6—virtual routing instances for multicast traffic

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

VRF with IPv6—virtual routing instances for unicast traffic

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Feature

J-EX4200 Switches

J-EX8200 Switches

MPLS with RSVP-based label switched paths (LSPs) and
MPLS-based circuit cross-connects (CCCs)

Junos OS 10.2 or earlier

Not supported

Table 13: MPLS Features

A separate software license is required for MPLS. See “Understanding Software Licenses for the J-EX Series Switch” on page 65.

9

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 13: MPLS Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

MPLS with class of service (CoS) and IP over MPLS

Junos OS 10.2 or earlier

Not supported

Feature

J-EX4200 Switches

J-EX8200 Switches

Internet Group Management Protocol (IGMP) version1 (v1)
and IGMPv2

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IGMPv3

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IGMPv1/v2 snooping

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IGMP snooping with routed VLAN interfaces (RVIs)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IGMPv3 snooping

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IGMPv3 snooping EXCLUDE modes

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Multicast Service Discovery Protocol (MSDP)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Table 14: Multicast Features

See the Junos OS Multicast Configuration Guide at http://www.juniper.net/techpubs/software/junos/.
Multicast VLAN registration (MVR)

Junos OS 10.2 or earlier

Not supported

Protocol Independent Multicast dense mode (PIM DM)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

See the Junos OS Multicast Configuration Guide at http://www.juniper.net/techpubs/software/junos/.
Protocol Independent Multicast source-specific multicast
(PIM SSM)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

See the Junos OS Multicast Configuration Guide at http://www.juniper.net/techpubs/software/junos/.
Protocol Independent Multicast sparse mode (PIM SM)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

See the Junos OS Multicast Configuration Guide at http://www.juniper.net/techpubs/software/junos/.
Single-source multicast

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Table 15: Network Management and Monitoring Features
Feature

J-EX4200 Switches

J-EX8200 Switches

802.1ag Ethernet OAM connectivity fault management
(CFM)

Junos OS 10.2 or earlier

Not supported

10

Chapter 1: Software Overview

Table 15: Network Management and Monitoring Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

Ethernet OAM link fault management (LFM)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Port mirroring

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Port mirroring enhancements

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Not supported

Real-time performance monitoring (RPM)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

RMON

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

sFlow monitoring technology

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

sFlow technology: Persistent IP addresses for agent IDs and
use in datagrams

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Simple Network Management Protocol version 1 (SNMPv1),
SNMPv2, and SNMPv3

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Time Domain Reflectometry (TDR)

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Feature

J-EX4200 Switches

J-EX8200 Switches

Automatic recovery for port error disable conditions

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

DHCP option 82

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

DHCP snooping

Junos OS 10.2 or earlier

Junos OS 10.3R1

Dynamic ARP inspection (DAI)

Junos OS 10.2 or earlier

Junos OS 10.3R1

IP source guard

Junos OS 10.2 or earlier

Junos OS 10.3R1

MAC limiting

Junos OS 10.2 or earlier

Junos OS 10.3R1

MAC move limiting

Junos OS 10.2 or earlier

Junos OS 10.3R1

Persistent storage for DHCP snooping

Junos OS 10.2 or earlier

Not supported

•

Layer 3 interface support

•

Multiple VLAN support

Port mirroring enhancements
•

Ingress-only and egress-only attributes on VLAN members
to avoid flooding mirrored traffic to member interfaces
of a VLAN on the intermediate switch

Table 16: Port Security Features

11

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 16: Port Security Features (continued)
Feature

J-EX4200 Switches

J-EX8200 Switches

Static ARP support

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Feature

J-EX4200 Switches

J-EX8200 Switches

Autoinstallation of configuration files

Junos OS 10.2 or earlier

Not supported

Automatic software download

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Configuration rollback

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

IP directed broadcast

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

J-Web interface, for switch configuration and management

Junos OS 10.2 or earlier

Junos OS 10.2 or earlier

Online insertion and removal (OIR) of uplink modules

Junos OS 10.2 or earlier

Not applicable

Power budget management

Not applicable

Junos OS 10.2 or earlier

Table 17: System Management Features

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.

Related
Documentation

12

•

High Availability Features for J-EX Series Switches Overview on page 18

•

Layer 3 Protocols Supported on J-EX Series Switches on page 13

•

Layer 3 Protocols Not Supported on J-EX Series Switches on page 14

•

J-EX4200 Switches Hardware Overview on page 25

•

J-EX8208 Switch Hardware Overview on page 27

•

J-EX8216 Switch Hardware Overview on page 30

Chapter 1: Software Overview

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 18 on page 13:

Table 18: Supported Junos OS Layer 3 Protocol Statements and Features
Protocol

Notes

For More Information

BGP

Fully supported.

See the Junos OS Routing Protocols Configuration
Guide at

http://www.juniper.net/techpubs/software/junos/.
BFD

Fully supported.

See the Junos OS Routing Protocols Configuration
Guide at

http://www.juniper.net/techpubs/software/junos/.
ICMP

Fully supported.

See the Junos OS Routing Protocols Configuration
Guide at

http://www.juniper.net/techpubs/software/junos/
IGMPv1, v2 and v3

Fully supported.

See the Junos OS Multicast Configuration Guide at

http://www.juniper.net/techpubs/software/junos/.
IS-IS

MLD

Supported, with the exceptions noted in “Layer 3
Protocols Not Supported on J-EX Series Switches”
on page 14.

See the Junos OS Routing Protocols Configuration
Guide at

Supported (MLD versions 1 and 2

See the Junos OS Multicast Configuration Guide at

http://www.juniper.net/techpubs/software/junos/.

http://www.juniper.net/techpubs/software/junos/.
MPLS

OSPFv1, v2 and
v3

PIM

Supported, with the exceptions noted in “Layer 3
Protocols Not Supported on J-EX Series Switches”
on page 14.

See the Junos OS MPLS Applications Configuration
Guide at

Supported, with the exceptions noted in “Layer 3
Protocols Not Supported on J-EX Series Switches”
on page 14.

See the Junos OS Routing Protocols Configuration
Guide at

Fully supported

See the Junos OS Multicast Configuration Guide at

http://www.juniper.net/techpubs/software/junos/.

http://www.juniper.net/techpubs/software/junos/.

http://www.juniper.net/techpubs/software/junos/.
RIP

Fully supported.

See the Junos OS Routing Protocols Configuration
Guide at

http://www.juniper.net/techpubs/software/junos/.
RIPng

Fully supported.

See the Junos OS Routing Protocols Configuration
Guide at

http://www.juniper.net/techpubs/software/junos/.
SNMP

Fully supported.

See the Junos OS Network Management
Configuration Guide at

http://www.juniper.net/techpubs/software/junos/.

13

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 18: Supported Junos OS Layer 3 Protocol Statements and Features (continued)
Protocol

Notes

For More Information

VRRP

Fully supported with exception of IPv6 support of
VRRP on routed VLAN interfaces (RVIs).

See “Understanding VRRP on J-EX Series Switches”
on page 1425. See also the Junos OS High Availability
Guide at
http://www.juniper.net/techpubs/software/junos/.

Related
Documentation

•

Layer 3 Protocols Not Supported on J-EX Series Switches on page 14

•

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 19 on page 14.

Table 19: 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 and subordinate statements

•

ES-IS

•

IPv6 in multicast routing
protocols

Logical routers

14

Chapter 1: Software Overview

Table 19: Junos OS Layer 3 Protocol Statements and Features That Are Not
Supported (continued)
Feature

Configuration Statements Not Supported on J-EX Series Switches

MPLS:

•

ldp and all subordinate statements

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

•

l2vpn and subordinate statements

•

ldp and subordinate statements

•

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

•

Fast Reroute (FRR)

•

Label Distribution Protocol
(LDP)

•

Layer 3 VPNs

•

Multiprotocol BGP
(MP-BGP) for VPN-IPv4
family

•

Pseudowire emulation
(PWE3)

•

Routing policy statements
related to Layer 3 VPNs and
MPLS

•

Virtual Private LAN Service
(VPLS)

Routing instances:
•

Routing instance forwarding

MPLS and
label-switched-paths

15

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 19: Junos OS Layer 3 Protocol Statements and Features That Are Not
Supported (continued)
Feature

Configuration Statements Not Supported on J-EX Series Switches

Traffic sampling and
fowarding in the
forwarding-options hierarchy

•

accounting and subordinate statements

•

family mpls and family multiservice under hash-key hierarchy

•

Under monitoring group-name family inet output hierarchy:

Related
Documentation

•

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

•

Layer 3 Protocols Supported on J-EX Series Switches on page 13

•

J-EX Series Switch Software Features Overview on page 3

Security Features for J-EX Series Switches Overview
Juniper Networks 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:

16

•

User and group accounts with password encryption and authentication.

•

Access privilege levels configurable for login classes and user templates.

Chapter 1: Software Overview

•

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:
•

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.

•

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.

17

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

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

•

802.1X for J-EX Series Switches Overview on page 2253

•

Firewall Filters for J-EX Series Switches Overview on page 2721

•

Port Security for J-EX Series Switches Overview on page 2545

•

Understanding Proxy ARP on J-EX Series Switches on page 1059

•

Understanding Storm Control on J-EX Series Switches on page 2511

•

Understanding the Use of Policers in Firewall Filters on page 2752

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 18

•

Graceful Protocol Restart on page 19

•

Redundant Routing Engines on page 19

•

Graceful Routing Engine Switchover on page 20

•

Virtual Chassis Software Upgrade and Failover Features on page 20

•

Link Aggregation on page 20

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 J-EX
Series 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

18

Chapter 1: Software Overview

and enabling traffic on the LAN to be routed without relying on a single routing platform.
Using VRRP, a backup J-EX Series 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.
For more information on VRRP, see “Understanding VRRP on J-EX Series Switches” on
page 1425.

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
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 J-EX Series 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
Two to ten J-EX4200 switches can be interconnected to create a Virtual Chassis
configuration that operates as a single network entity. Every Virtual Chassis configuration
has a master and a backup. The master acts as the master Routing Engine and the backup
acts as the backup Routing Engine. The Routing Engine provides the following
functionality:
•

Runs various routing protocols

•

Provides the forwarding table to the Packet Forwarding Engines (PFEs) in all the
member switches of the Virtual Chassis configuration

•

Runs other management and control processes for the entire Virtual Chassis
configuration

The master Routing Engine, which is in the master of the Virtual Chassis configuration,
runs Junos OS in the master role. It receives and transmits routing information, builds
and maintains routing tables, communicates with interfaces and Packet Forwarding

19

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Engine components of the member switches, and has full control over the Virtual Chassis
configuration.
The backup Routing Engine, which is in the backup of the Virtual Chassis configuration,
runs Junos OS in the backup role. It 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.

Graceful Routing Engine Switchover
You can configure graceful Routing Engine switchover (GRES) in a Virtual Chassis
configuration, allowing the configuration to switch from the master Routing Engine in
the master to the backup Routing Engine in the backup with minimal interruption to
network communications. When you configure GRES, 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 boot up 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
with the new master Routing Engine. The interruption to the traffic is minimal.

Virtual Chassis Software Upgrade and Failover Features
J-EX4200 switches provide these features for increased resiliency in Virtual Chassis
configurations:
•

Virtual Chassis atomic software upgrade—When you upgrade software in a Virtual
Chassis configuration, the upgrade will either succeed or fail on all member switches,
preventing the situation in which only some of the Virtual Chassis member switches
are upgraded.

•

Virtual Chassis fast failover—A hardware-assisted failover mechanism that
automatically reroutes traffic and reduces traffic loss in the event of a link failure.

•

Virtual Chassis split and merge—If there is a disruption to the Virtual Chassis
configuration due to member switches failing or being removed from the configuration,
the Virtual Chassis configuration splits into two separate Virtual Chassis.

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

20

Chapter 1: Software Overview

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.
You can select up to eight Ethernet interfaces and include them within a LAG. In a
J-EX4200 Virtual Chassis configuration, the interfaces that form a LAG can be on different
members of the Virtual Chassis. See “Understanding Virtual Chassis Configurations and
Link Aggregation” on page 702.
Related
Documentation

•

For more information on high availability features, see the Junos OS High Availability
Configuration Guide at http://www.juniper.net/techpubs/software/junos/.

•

Virtual Chassis Overview on page 691

•

Understanding Virtual Chassis Components on page 694

•

Understanding Virtual Chassis Configurations and Link Aggregation on page 702

•

Understanding VRRP on J-EX Series Switches on page 1425

21

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Understanding Software Infrastructure and Processes
Each switch runs 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.
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 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.

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.

•

Routing Engine and Packet Forwarding Engine on page 22

•

Junos OS Processes on page 23

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:
•

22

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

Chapter 1: Software Overview

•

Maintains the routing tables used by the switch and controls the routing protocols
that run on the switch.

•

Provides control and monitoring functions for the switch, including controlling power
and monitoring system status.

Junos OS Processes
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 Junos OS, for added flexibility.
Table 20 on page 23 describes the primary Junos OS processes.

Table 20: 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.

23

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Table 20: Junos OS Processes (continued)
Process

Name

Description

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.

Related
Documentation

24

•

For more information about processes, see the Junos OS Network Operations Guide at
http://www.juniper.net/techpubs/software/junos/.

•

For more information about basic system parameters, supported protocols, and
software processes, see the Junos OS System Basics Configuration Guide at
http://www.juniper.net/techpubs/software/junos/.

CHAPTER 2

Supported Hardware
•

J-EX4200 Switches Hardware Overview on page 25

•

J-EX4200 Switch Models on page 26

•

J-EX8208 Switch Hardware Overview on page 27

•

J-EX8216 Switch Hardware Overview on page 30

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 under 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 25

•

Uplink Modules on page 26

•

Power over Ethernet (PoE) Ports on page 26

J-EX4200 Switches
J-EX4200 switches provide connectivity for medium- and high-density environments
and scalability for growing networks. These switches can be deployed wherever you need
a 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 PoE. All models provide ports that have 10/100/1000Base-T Gigabit Ethernet
connectors and optional 1-gigabit small form-factor pluggable (SFP) transceivers or
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.

25

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

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
GRES (graceful Routing Engine switchover) and nonstop active routing.

•

Junos OS with its modular design that enables failed system processes to gracefully
restart.

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. J-EX4200 switches have partial (8-port) PoE capability.
Related
Documentation

•

J-EX4200 Switch Models on page 26

•

Field-Replaceable Units in J-EX4200 Switches

•

Site Preparation Checklist for J-EX4200 Switches

J-EX4200 Switch Models
The J-EX4200 switch is available with 24 or 48 ports and with partial Power over Ethernet
(PoE) capability. Table 21 on page 26 lists the J-EX4200 switch models.

Table 21: 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

Not applicable

320 W

26

Chapter 2: Supported Hardware

Related
Documentation

•

Front Panel of a J-EX4200 Switch

•

Rear Panel of a J-EX4200 Switch

•

J-EX4200 Switches Hardware Overview on page 25

J-EX8208 Switch Hardware Overview
Dell PowerConnect J-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 Junos OS interfaces that you use
for other Junos OS platforms—the Junos OS command-line interface (CLI) and the J-Web
graphical interface.
•

Software on page 27

•

Chassis Physical Specifications on page 27

•

Routing Engines and Switch Fabric on page 28

•

Line Cards on page 29

•

Cooling System on page 29

•

Power Supplies on page 29

Software
The Dell PowerConnect J-EX Series Switches—PowerConnect J-EX4200 Ethernet
Switches and PowerConnect J-EX8200 Ethernet Switches—run under 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 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 1 on page 28.

27

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Figure 1: 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. See LCD Panel in a J-EX8200 Switch.
The J-EX8208 chassis backplane distributes the data, control, and management signals
to various system components along with distributing power throughout the system.
See Chassis Physical Specifications of a J-EX8208 Switch.

Routing Engines and Switch Fabric
Switching functionality, system management, and system control functions of a J-EX8208
switch are performed by the Switch Fabric and Routing Engine (SRE) module. See Switch
Fabric and Routing Engine (SRE) Module in a J-EX8208 Switch. 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. See Slot Numbering for a J-EX8208 Switch.

28

Chapter 2: Supported Hardware

A base configuration J-EX8208 switch has one SRE module. A redundant configuration
J-EX8208 switch has a second SRE module. See J-EX8208 Switch Configurations.
The Switch Fabric (SF) module, working with the SRE module, provides the necessary
switching functionality to a base configuration 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. See Switch Fabric (SF) Module in a
J-EX8208 Switch.

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. They 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. See Slot Numbering for a J-EX8208 Switch. All line cards are
hot-removable and hot-insertable.
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. See 8-port SFP+ Line
Card in a J-EX8200 Switch.

•

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. See 48-port SFP Line Card in a
J-EX8200 Switch.

•

48-port 10/100/1000 RJ-45 line card: This line card had 48 10/100/1000 Gigabit
Ethernet ports with RJ-45 connectors on its faceplate. See 48-port RJ-45 Line Card in
a J-EX8200 Switch.

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. See Cooling System and Airflow
in a J-EX8208 Switch.

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 (200–240 VAC) or
1200 W at low voltage (100–120 VAC) to the J-EX8208 chassis.

29

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

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

•

Field-Replaceable Units in a J-EX8208 Switch

•

Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161

•

Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163

J-EX8216 Switch Hardware Overview
The Dell PowerConnect J-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 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 Junos OS interfaces that you use
for other Junos OS platforms—the Junos OS command-line interface (CLI) and the J-Web
graphical interface.
•

Software on page 30

•

Chassis Physical Specifications, LCD Panel, and Midplane on page 30

•

Routing Engines and Switch Fabric on page 32

•

Line Cards on page 33

•

Cooling System on page 33

•

Power Supplies on page 34

Software
The Dell PowerConnect J-EX Series Switches—PowerConnect J-EX4200 Ethernet
Switches and PowerConnect J-EX8200 Ethernet Switches—run under 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 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 2 on page 31 and Figure 3 on page 32 and Chassis Physical Specifications
of a J-EX8216 Switch.

30

Chapter 2: Supported Hardware

Figure 2: J-EX8216 Switch Front

31

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Figure 3: 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. See LCD Panel in a J-EX8200 Switch.
The J-EX8216 chassis midplane distributes the data, control, and management signals
to system components and distributes power throughout the system. See Midplane in
a J-EX8216 Switch.

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
modules are hot-insertable and hot-removable field-replaceable units (FRUs) that are

32

Chapter 2: Supported Hardware

installed in the front of the chassis in the slots labeled RE0 and RE1. A base configuration
(AC version) J-EX8216 switch has one RE module. A redundant configuration J-EX8216
switch has a second RE module for redundancy. See Routing Engine (RE) Module in a
J-EX8216 Switch and J-EX8216 Switch Configurations.
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. See Switch Fabric (SF) Modules in a J-EX8216
Switch.

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.
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. See 8-port SFP+ Line
Card in a J-EX8200 Switch.

•

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. See 48-port SFP Line Card in a
J-EX8200 Switch.

•

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. See 48-port RJ-45 Line Card in
a J-EX8200 Switch.

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
rear of the chassis. See Cooling System and Airflow in a J-EX8216 Switch.

33

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

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 (200–240
VAC) to the J-EX8216 chassis. Low-voltage 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. See AC Power Supply in a
J-EX8200 Switch and J-EX8216 Switch Configurations.

CAUTION: Mixing different types of power supplies in the same chassis is
not a supported configuration.

Related
Documentation

34

•

Field-Replaceable Units in a J-EX8216 Switch

•

Slot Numbering for a J-EX8216 Switch

•

Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161

•

Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163

PART 2

Complete Software Configuration
Statement Hierarchy
•

Complete Software Configuration Statement Hierarchy on page 37

35

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

36

CHAPTER 3

Complete Software Configuration
Statement Hierarchy
•

[edit access] Configuration Statement Hierarchy on page 37

•

[edit chassis] Configuration Statement Hierarchy on page 38

•

[edit class-of-service] Configuration Statement Hierarchy on page 38

•

[edit ethernet-switching-options] Configuration Statement Hierarchy on page 40

•

[edit firewall] Configuration Statement Hierarchy on page 42

•

[edit forwarding-options] Configuration Statement Hierarchy on page 43

•

[edit interfaces] Configuration Statement Hierarchy on page 44

•

[edit poe] Configuration Statement Hierarchy on page 48

•

[edit protocols] Configuration Statement Hierarchy on page 48

•

[edit routing-instances] Configuration Hierarchy on page 55

•

[edit snmp] Configuration Statement Hierarchy on page 55

•

[edit virtual-chassis] Configuration Statement Hierarchy on page 55

•

[edit vlans] Configuration Statement Hierarchy on page 56

[edit access] Configuration Statement Hierarchy
access {
profileprofile-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 ];
}
}
}

Related
Documentation

•

Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267

37

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

•

Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339

[edit chassis] Configuration Statement Hierarchy
chassis {
aggregated-devices {
ethernet {
device-count number;
}
}
auto-image-upgrade;
}
fpc slot {
pic pic-number {
sfpplus {
pic-mode mode;
power-budget-priority priority;
}
lcd-menu fpc slot-number {
menu-item (menu-name | menu-option);
}
}
psu {
redundancy {
n-plus-n;
}
}
redundancy{
graceful-switchover ;
}

Related
Documentation

•

Understanding Aggregated Ethernet Interfaces and LACP on page 867

•

Understanding Power Management on J-EX Series Switches on page 302

[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;
}
}

38

Chapter 3: Complete Software Configuration Statement Hierarchy

forwarding-classes {
class class-name queue-num queue-number priority ( high | low );
}
interfaces {
interface-name {
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;
}
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

•

Example: Configuring CoS on J-EX Series Switches on page 2883

•

Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point
Aliases (J-Web Procedure) on page 2912

39

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

•

Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web
Procedure) on page 2916

•

Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS
Forwarding Classes (J-Web Procedure) on page 2918

•

Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925

•

Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers
(J-Web Procedure) on page 2920

•

Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules
(J-Web Procedure) on page 2926

•

Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS
Components to Interfaces (J-Web Procedure) on page 2928

[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;
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;
}

40

Chapter 3: Complete Software Configuration Statement Hierarchy

redundant-trunk-group {
group-name name {
interface interface-name ;
}
}
secure-access-port {
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 );
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 );
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 );
(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-unknown-unicast;
}
}
traceoptions {
file filename     ;
flag flag ;
}

41

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

unknown-unicast-forwarding {
vlan (all | vlan-name) {
interface interface-name;
}
}
voip {
interface (all | [interface-name | access-ports]) {
vlan vlan-name ;
forwarding-class ;
}
}
}

Related
Documentation

•

Understanding Port Mirroring on J-EX Series Switches on page 3245

•

Port Security for J-EX Series Switches Overview on page 2545

•

Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches
on page 1278

•

Understanding Redundant Trunk Links on J-EX Series Switches on page 1049

•

Understanding Storm Control on J-EX Series Switches on page 2511

•

Understanding 802.1X and VoIP on J-EX Series Switches on page 2263

•

Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051

•

Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512

•

Understanding MAC Notification on J-EX Series Switches on page 1060

[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 {

42

Chapter 3: Complete Software Configuration Statement Hierarchy

policer-action;
}
}
}

Related
Documentation

•

Firewall Filter Configuration Statements Supported by Junos OS for J-EX Series Switches
on page 2806

•

Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series
Switches on page 2755

•

Configuring Firewall Filters (CLI Procedure) on page 2779

•

Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788

•

Firewall Filters for J-EX Series Switches Overview on page 2721

[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;
}
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;
}
}

43

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

Related
Documentation

•

Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between
Clients and a DHCP Server on page 2615

•

Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and
DHCP Server (CLI Procedure) on page 2646

•

Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560

•

DHCP/BOOTP Relay for J-EX Series Switches Overview on page 446

•

For more information about the [edit forwarding-options] hierarchy and all its options,
see the Junos OS Policy Framework Configuration Guide at
http://www.juniper.net/techpubs/software/junos/.

[edit interfaces] Configuration Statement Hierarchy
interfaces {
aex {
aggregated-ether-options {
(flow-control | no-flow-control);
lacp mode {
periodic interval;
}
link-speed speed;
minimum-links number;
}
description text;
disable;
hold-time up milliseconds down milliseconds;
mtu bytes;
no-gratuitous-arp-request;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
proxy-arp (restricted | unrestricted);
(traps | no-traps);
vlan-id vlan-id-number;
}
vlan-tagging;
}
fe-fpc/pic/port {
description text;
disable;
mtu bytes;
no-gratuitous-arp-request;
speed speed;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}

44

Chapter 3: Complete Software Configuration Statement Hierarchy

proxy-arp (restricted | unrestricted);
(traps | no-traps);
vlan-id vlan-id-number;
}
vlan-tagging;
}
ge-fpc/pic/port {
description text;
disable;
ether-options {
802.3ad aex {
lacp {
force-up;
}
}
(auto-negotiation | no-auto-negotiation);
(flow-control | no-flow-control);
link-mode mode;
speed (auto-negotiation | speed);
}
hold-time up milliseconds down milliseconds;
mtu bytes;
no-gratuitous-arp-request;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
proxy-arp (restricted | unrestricted);
rpm;
(traps | no-traps);
vlan-id vlan-id-number;
}
vlan-tagging;
}
interface-range interface-range name {
description text;
disable;
ether-options {
802.3ad aex {
lacp {
force-up;
}
}
(auto-negotiation | no-auto-negotiation);
(flow-control| no-flow-control);
link-mode mode;
speed (auto-negotiation | speed);
}
hold-time up milliseconds down milliseconds;
member interface-name;
member-range starting-interface name to ending-interface name;
mtu bytes;
unit logical-unit-number {
description text;

45

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

disable;
family family-name {...}
proxy-arp (restricted | unrestricted);
rpm;
(traps | no-traps);
vlan-id vlan-id-number;
}
}
lo0 {
description text;
disable;
hold-time up milliseconds down milliseconds;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
(traps | no-traps);
}
}
me0 {
description text;
disable;
hold-time up milliseconds down milliseconds;
no-gratuitous-arp-request;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
(traps | no-traps);
vlan-id vlan-id-number;
}
vlan-tagging;
}
vlan {
description text;
disable;
hold-time up milliseconds down milliseconds;
mtu bytes;
no-gratuitous-arp-request;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
proxy-arp (restricted | unrestricted);
(traps | no-traps);
}
}
vme {
description text;
disable;

46

Chapter 3: Complete Software Configuration Statement Hierarchy

hold-time up milliseconds down milliseconds;
mtu bytes;
no-gratuitous-arp-request;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
(traps | no-traps);
vlan-id vlan-id-number;
}
vlan-tagging;
}
xe-fpc/pic/port {
description text;
disable;
ether-options {
802.3ad aex {
lacp (802.3ad) {
force-up;
}
}
(auto-negotiation | no-auto-negotiation);
(flow-control | no-flow-control);
link-mode mode;
speed (auto-negotiation | speed);
}
hold-time up milliseconds down milliseconds;
mtu bytes;
no-gratuitous-arp-request;
traceoptions;
(traps | no-traps);
unit logical-unit-number {
description text;
disable;
family family-name {...}
proxy-arp (restricted | unrestricted);
rpm;
(traps | no-traps);
vlan-id vlan-id-number;
}
vlan-tagging;
}
}

Related
Documentation

•

Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919

•

Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922

•

Configuring a Layer 3 Subinterface (CLI Procedure) on page 930

•

Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137

•

Configuring the Virtual Management Ethernet Interface for Global Management of a
Virtual Chassis (CLI Procedure) on page 797

47

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

•

J-EX Series Switches Interfaces Overview on page 863

•

Junos OS Network Interfaces Configuration Guide at
http://www.juniper.net/techpubs/software/junos/

[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

•

Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch
on page 3015

•

Configuring PoE (CLI Procedure) on page 3021

•

PoE and J-EX Series Switches Overview on page 3009

[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;

48

Chapter 3: Complete Software Configuration Statement Hierarchy

quiet-period seconds;
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);
}
}
gvrp {
;
interface (all | [interface-name]) {
disable;
}
join-timer millseconds;
leave-timer milliseconds;
leaveall-timer milliseconds;
}
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 {
group ip-address;
}
}
proxy ;
query-interval seconds;
query-last-member-interval seconds;

49

Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS

query-response-interval seconds;
robust-count number;
}
}
lldp {
disable;
advertisement-interval seconds;
hold-multiplier number;
interface (all | interface-name) {
disable;
}
traceoptions {
file filename   
;
flag flag (detail | disable | receive | send);
}
}
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; alarm; } cost cost; 50 Chapter 3: Complete Software Configuration Statement Hierarchy edge; mode mode; no-root-port; priority priority; } 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); 51 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS maintenance-association ma-name { continuity-check { hold-interval minutes; interval (10m | 10s | 1m | 1s| 100ms); 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; 52 Chapter 3: Complete Software Configuration Statement Hierarchy interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } 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 number; } polling-interval seconds; sample-rate number; source-ip } stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { 53 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file filename ; flag flag; } 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 { alarm; block; } cost cost; disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } } Related Documentation 54 • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding MAC RADIUS Authentication on J-EX Series Switches • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Ethernet OAM Connectivity Fault Management for a J-EX Series Switch on page 3463 • Understanding Ethernet OAM Link Fault Management for a J-EX Series Switch on page 3427 Chapter 3: Complete Software Configuration Statement Hierarchy • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding How to Use sFlow Technology for Network Monitoring on a J-EX Series Switch on page 3283 • Understanding VSTP for J-EX Series Switches on page 1281 [edit routing-instances] Configuration Hierarchy routing-instances routing-instance-name { instance-type virtual-router interface interface-name } Related Documentation • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 [edit snmp] Configuration Statement Hierarchy snmp { rmon { history index { bucket-size number; interface interface-name; interval seconds; owner owner-name; } } } Related Documentation • Configuring SNMP (J-Web Procedure) on page 3309 • Junos OS Network Management Configuration Guide at http://www.juniper.net/techpubs/software/junos/ [edit virtual-chassis] Configuration Statement Hierarchy virtual-chassis { auto-sw-update { package-name-edit-virtual-chassis.xml package-name; } fast-failover (ge | vcp disable | xe); id id; mac-persistence-timer seconds; member member-id { mastership-priority number; no-management-vlan; serial-number; 55 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS role; } no-split-detection; preprovisioned; traceoptions { file filename ; flag flag ; } } Related Documentation • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Virtual Chassis Overview on page 691 [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)); } 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; } } 56 Chapter 3: Complete Software Configuration Statement Hierarchy Related Documentation • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Creating a Private VLAN (CLI Procedure) on page 1143 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 57 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 58 PART 3 Software Installation • Software Installation Overview on page 61 • Installing Junos OS on page 69 • Booting the Switch, Upgrading Software, and Managing Licenses on page 79 • Verifying Software Installation on page 87 • Troubleshooting Software Installation on page 91 • Configuration Statements for Software Installation on page 95 • Operational Mode Commands for Software Installation on page 97 59 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 60 CHAPTER 4 Software Installation Overview • Installation Overview on page 61 • Licenses Overview on page 65 Installation Overview • Understanding Software Installation on J-EX Series Switches on page 61 • Junos OS Package Names on page 63 • Understanding System Snapshot on J-EX Series Switches on page 64 Understanding Software Installation on J-EX Series Switches A J-EX Series Switch is delivered with 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 61 • Software Package Security on page 62 • Installing Software on a Virtual Chassis on page 62 • Installing Software on J-EX8200 Switches with Redundant Routing Engines on page 62 • Installing Software Using Automatic Software Download on page 63 • Troubleshooting Software Installation on page 63 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. 61 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for 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. 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. The previous software package is preserved in a separate disk partition, and you can manually revert back to it if necessary. 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. Software Package Security Junos OS is delivered in signed packages that contain digital signatures to ensure it is official software. For more information about signed software packages, see the Junos OS Installation and Upgrade Guide at http://www.juniper.net/techpubs/software/junos/. Installing Software on a Virtual Chassis You can connect individual J-EX4200 Ethernet Switches together to form one unit and manage the unit as a single chassis, 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. For ease of management, the 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. Installing Software on J-EX8200 Switches with Redundant Routing Engines To install software on a J-EX8200 Ethernet Switch that has two Routing Engines with minimal network disruption, you perform a Junos OS installation on each Routing Engine separately, starting with the backup. See “Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure)” on page 71. 62 Chapter 4: Software Installation Overview 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 82. Troubleshooting Software Installation If 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 91. 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 on page 69 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 75 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 71 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. 63 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • 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 75 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 71 • Downloading Software Packages from Juniper Networks on page 69 • Understanding Software Installation on J-EX Series Switches on page 61 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 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 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: 64 • 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 VC member creating the snapshot, executed, and the output is then returned to the switch that initiated the Chapter 4: Software Installation Overview 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. Related Documentation • Understanding Software Installation on J-EX Series Switches on page 61 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 80 • Understanding Software Licenses for the J-EX Series Switch on page 65 • License Key Components for the J-EX Series Switch on page 66 Licenses Overview Understanding Software Licenses for the J-EX Series Switch To enable and use some Junos OS features, you must purchase, install, and manage separate software licenses. The presence on the switch of the appropriate software license keys (“passwords”) determines whether you are eligible to configure and use certain features. Junos OS feature licenses are device specific. The same feature can be installed and configured on multiple switches. To conform to Junos OS feature licensing requirements, you must purchase a license for each switch. For a Virtual Chassis deployment, two licenses are recommended for redundancy. These licenses can be based on the serial numbers of any two member switches. If you add additional member switches to the Virtual Chassis configuration, you do not need additional licenses. 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 routing (except multicast protocols) • 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. 65 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS License Warning Messages For features that require a license, you must install and properly configure a license key to meet the requirements for using the licensable feature. To obtain a license key, use the contact information provided in your Advanced Feature License (AFL) certificate. If you have not purchased the AFL and installed the license key, you receive warnings after you commit a licensible feature. 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 from the show system alarms command displays the active alarms—for example: user@switch> show system alarms 1 alarm currently active Alarm time Class 2009-09-03 06:00:11 UTC Minor Description BGP Routing Protocol usage requires a license Every time you edit or view the configuration, a message displays the committed features that require a license. For example, when you edit the BGP configuration, a warning message appears—for example: [edit protocols] user@switch# bgp warning: requires ’bgp’ license Likewise, viewing the configuration causes the system to display a message—for example: user@switch> show configuration protocols ## Warning: requires 'bgp' license ## bgp { hold-time 10; damping; } Related Documentation • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 83 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 84 • Monitoring Licenses for the J-EX Series Switch on page 88 • License Key Components for the J-EX Series Switch on page 66 • 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: 66 Chapter 4: Software Installation Overview • 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 83 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 84 • Software Licenses for the J-EX Series Switch Overview on page 65 67 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 68 CHAPTER 5 Installing Junos OS • Downloading Software Packages on page 69 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 71 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 75 • Rebooting or Halting the J-EX Series Switch (J-Web Procedure) on page 77 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 63. 4. Download the software to a local host or to an internal software distribution site. 69 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 75 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 • Understanding Software Installation on J-EX Series Switches on page 61 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 Virtual Chassis or all members of a 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 71. To install software upgrades on a J-EX Series switch with a single Routing Engine using the CLI: 1. Download the software package as described in “Downloading Software Packages from Juniper Networks” on page 69. 2. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide at http://www.juniper.net/techpubs/software/junos/ 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: NOTE: A reboot, which will occur as part of the execution of the following command, is required to complete the software upgrade. If you want to reboot the switch at a later time, do not use the reboot option at this point of the procedure and enter the request system reboot command at a later time to reboot the switch. user@switch> request system software add source reboot Replace source with one of the following paths: • For a software package that is installed from a local directory on the switch—/pathname/package-name-m.nZx-distribution.tgz. • For a software package that is downloaded and installed from a remote location: • 70 ftp://hostname/pathname/package-name-m.nZx-distribution.tgz Chapter 5: Installing Junos OS • http://hostname/pathname/package-name-m.nZx-distribution.tgz where package-name-m.nZx-distribution.tgz is, for example, jinstall-ex-4200-10.2R1.8-domestic-signed.tgz. 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. 5. 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 75 • Troubleshooting Software Installation on page 91 • Junos OS Package Names on page 63 • See the Junos OS System Basics and Services Command Reference at http://www.juniper.net/techpubs/software/junos/ for details about the request system software add command. • Understanding Software Installation on J-EX Series Switches on page 61 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 disrupting network operation during a Junos OS upgrade by upgrading the Routing Engines separately, starting with the backup Routing Engine. 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 70. 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, switch device control to the backup Routing Engine. Finally, install the new software on the new backup Routing Engine. To upgrade the Junos OS on the switch, perform the following tasks: 1. Preparing the Switch for the Software Installation on page 72 2. Installing Software on the Backup Routing Engine on page 73 3. Installing Software on the Default Master Routing Engine on page 74 4. Returning Routing Control to the Default Master Routing Engine (Optional) on page 75 71 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 161. 2. Enter 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] user@switch# 3. Disable GRES (graceful Routing Engine switchover): [edit] user@switch# deactivate chassis redundancy graceful-switchover 4. Save the configuration change on both Routing Engines: [edit] user@switch# commit synchronize NOTE: To ensure the most recent configuration changes are committed before the software upgrade, perform this step even if GRES was previously disabled. 5. Exit out of the CLI configuration mode: [edit] user@switch# exit 6. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide at http://www.juniper.net/techpubs/software/junos/ for instructions on performing this task. 72 Chapter 5: Installing Junos OS Installing Software on the Backup Routing Engine Once the J-EX8200 switch is ready, you first install the software on the backup Routing Engine. This enables the master Routing Engine to continue operations, minimizing the disruption to your network. 1. Download the software by following the procedures in “Downloading Software Packages from Juniper Networks” on page 69. 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 backup Routing Engine’s console. 4. Install the new software package: user@switch> request system software add validate /var/tmp/package-name-m.nZx-distribution.tgz where package-name-m.nZx-distribution.tgz is, for example, jinstall-ex-8200–10.2R1.5–domestic-signed.tgz. For more information on the request system software add command, see the Junos OS System Basics and Services Command Reference at http://www.juniper.net/techpubs/software/junos/. NOTE: To abort the installation, do not reboot your device; instead, finish the installation and then issue the request system software delete package-name-m.nZx-distribution.tgz command, where package-name-m.nZx-distribution.tgz is, for example, jinstall-ex-4200–10.2R1.5–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 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 73 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Installing Software on the Default Master Routing Engine To switch device 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 device control to the backup Routing Engine: user@switch> request chassis routing-engine master switch NOTE: Because GRES 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. 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 using the request system software add command: user@switch> request system software add validate /var/tmp/jinstall-ex-8200-10.2R1.5-domestic-signed.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 GRES: [edit] user@switch# activate chassis redundancy graceful-switchover Re-enabling GRES allows any future Routing Engine switchovers to occur without the loss of any network traffic. 8. Enter the commit synchronize command to save the configuration change: [edit] 74 Chapter 5: Installing Junos OS user@switch# commit synchronize 9. 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: 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 75 • Troubleshooting Software Installation on page 91 • Junos OS Package Names on page 63 • Understanding Software Installation on J-EX Series Switches on page 61 • Understanding J-EX8208 Switch Component and Functionality Redundancy 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. 75 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for 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 76 2. Installing Software Upgrades by Uploading Files on page 77 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 69. 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 22 on page 76. 5. Click Fetch and Install Package. The software is activated after the switch has rebooted. Table 22: 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 76 Chapter 5: Installing Junos OS Table 22: 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 23 on page 77. 4. Click Upload and Install Package. The software is activated after the switching platform has rebooted. Table 23: 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 70 • Understanding Software Installation on J-EX Series Switches on page 61 • Troubleshooting Software Installation on page 91 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: 77 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for 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 78 • • 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 136 CHAPTER 6 Booting the Switch, Upgrading Software, and Managing Licenses • Booting the Switch on page 79 • Upgrading Software on page 82 • Managing Licenses on page 83 • Booting a J-EX Series Switch Using a Software Package Stored on a USB Flash Drive on page 79 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 80 Booting the Switch 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 80. 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 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 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: • A USB flash drive that meets the J-EX Series switch USB port specifications. See USB Port Specifications for a J-EX Series Switch. • 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. 79 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 69. 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 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 70 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 75 • See Rear Panel of a J-EX4200 Switch for USB port location. • See Switch Fabric and Routing Engine (SRE) Module in a J-EX8208 Switch for USB port location. • See Routing Engine (RE) Module in a J-EX8216 Switch for USB port location. • Understanding Software Installation on J-EX Series Switches on page 61 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 80 2. Creating a Snapshot on an Internal Flash Drive and Using it to Boot the Switch on page 81 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. 80 Chapter 6: Booting the Switch, Upgrading Software, and Managing Licenses 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. See USB Port Specifications for a J-EX Series Switch. 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 • 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 88 81 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Understanding System Snapshot on J-EX Series Switches on page 64 Upgrading Software • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 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. 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 at http://www.juniper.net/techpubs/software/junos/ for information about using the CLI to configure DHCP services and settings. See “Configuring DHCP Services (J-Web Procedure)” on page 447 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 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 82 • Verifying That Automatic Software Download Is Working Correctly on page 87 • Understanding Software Installation on J-EX Series Switches on page 61 • DHCP Services for J-EX Series Switches Overview on page 445 Chapter 6: Booting the Switch, Upgrading Software, and Managing Licenses Managing Licenses • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 83 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 84 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. 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 66. This topic includes the following tasks: • Adding New Licenses on page 83 • Deleting Licenses on page 84 • Saving License Keys on page 84 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: 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. 83 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 84 • Monitoring Licenses for the J-EX Series Switch on page 88 • Understanding Software Licenses for the J-EX Series Switch on page 65 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. Before you begin managing licenses, be sure that you have: 84 • 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 66. 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 85 • Deleting Licenses on page 85 • Displaying License Keys on page 86 • Downloading Licenses on page 86 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. 85 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 86 • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 83 • Monitoring Licenses for the J-EX Series Switch on page 88 • Understanding Software Licenses for the J-EX Series Switch on page 65 CHAPTER 7 Verifying Software Installation • Routine Monitoring on page 87 • Monitoring Licenses on page 88 • Verifying That Automatic Software Download Is Working Correctly on page 87 • Verifying That a System Snapshot Was Created on a J-EX Series Switch on page 88 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 boot file named jinstall-ex-4200-10.2R1.5-domestic-signed.tgz. If automatic software 87 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 82 • DHCP Services for J-EX Series Switches Overview on page 445 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 80 Monitoring Licenses • Monitoring Licenses for the J-EX Series Switch on page 88 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. 88 Chapter 7: Verifying Software Installation To monitor your installed licenses, perform the following tasks: • Displaying Installed Licenses and License Usage Details on page 89 • Displaying Installed License Keys on page 90 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 Expiry Licenses installed: License identifier: JUNOS204558 License version: 2 Valid for device: BN0208380000 Features: 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. 89 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 90 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 83 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 84 • Understanding Software Licenses for the J-EX Series Switch on page 65 CHAPTER 8 Troubleshooting Software Installation • Troubleshooting Software Installation on page 91 Troubleshooting Software Installation • Recovering from a Failed Software Upgrade on a J-EX Series Switch on page 91 • Rebooting from the Inactive Partition on page 92 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 install the new Junos OS package in a separate partition and both images will 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 79 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 displays, 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 displays. 3. Enter the following command: loader> install [– –format] [– –external] source 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 that of the most recently installed Junos OS package. 91 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • external—Use this option to install the software package onto an external media. • 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 as normal and ends with a login prompt. Rebooting from the Inactive Partition Problem A J-EX Series switch ships with 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. 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 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=diskmediaspartition: where media is either 0 (internal) or 1 (external) and partition indicates the partition number, 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 92 Chapter 8: Troubleshooting Software Installation Related Documentation • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 75 • Understanding Software Installation on J-EX Series Switches on page 61 93 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 94 CHAPTER 9 Configuration Statements for Software Installation • [edit chassis] Configuration Statement Hierarchy on page 95 [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); } psu { redundancy { n-plus-n; } } redundancy { graceful-switchover; } } Related Documentation • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 166 • Configuring Graceful Routing Engine Switchover in a Virtual Chassis Configuration (CLI Procedure) on page 801 95 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring Power Supply Redundancy (CLI Procedure) on page 307 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 • Configuring Nonstop Software Upgrade (CLI Procedure) 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 at http://www.juniper.net/techpubs/software/junos/index.html for information about using the CLI to configure DHCP services and settings. See “Configuring DHCP Services (J-Web Procedure)” on page 447 for information about using the J-Web interface to configure DHCP services and settings. Default Required Privilege Level Related Documentation 96 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 82 • Understanding Software Installation on J-EX Series Switches on page 61 • DHCP Services for J-EX Series Switches Overview on page 445 CHAPTER 10 Operational Mode Commands for Software Installation 97 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 List of Sample Output Output Fields request system license add 98 maintenance request system license add on page 98 When you enter this command, you are provided feedback on the status of your request. user@host> request system license add terminal Chapter 10: Operational Mode Commands for Software Installation request system license delete Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields request system license delete 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 request system license delete on page 99 When you enter this command, you are provided feedback on the status of your request. user@host> request system license delete G03000002223 99 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 List of Sample Output Output Fields request system license save 100 maintenance request system license save on page 100 When you enter this command, you are provided feedback on the status of your request. user@host> request system license save ftp://user@host/license.conf Chapter 10: Operational Mode Commands for Software Installation request system reboot Syntax Syntax (J-EX Series Switch) Release Information Description Options request system reboot request system reboot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reboot the software. none—Reboot the software immediately. all-members—(J-EX4200 switches only) (Optional) Reboot all members of the Virtual Chassis configuration. at time—(Optional) Time at which to reboot the software, specified in one of the following ways: • now—Stop or reboot the software immediately. This is the default. • +minutes—Number of minutes from now to reboot the software. • yymmddhhmm—Absolute time at which to reboot the software, specified as year, month, day, hour, and minute. • hh:mm—Absolute time on the current day at which to stop the software, specified in 24-hour time. in minutes—(Optional) Number of minutes from now to reboot the software. This option is an alias for the at +minutes option. local—(J-EX4200 switches only) (Optional) Reboot the local Virtual Chassis member. media (compact-flash | disk | removable-compact-flash | usb)—(Optional) Boot medium for next boot. media (external | internal)—(J-EX Series switches only) (Optional) Reboot the boot media: • external—Reboot the external mass storage device. • internal—Reboot the internal flash device. 101 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS member member-id—(J-EX4200 switches only) (Optional) Reboot 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 or rebooting the software. 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 slice—(J-EX Series switches only) (Optional) Reboot a partition on the boot media. This option has the following suboptions: Additional Information • 1—Power off partition 1. • 2—Power off partition 2. • alternate—Reboot from the alternate partition. Reboot requests are recorded in the system log files, which you can view with the show log command (see show log). Also, the names of any running processes that are scheduled to be shut down are changed. You can view the process names with the show system processes command (see show system processes). NOTE: To reboot a router that has two Routing Engines, reboot the backup Routing Engine (if you have upgraded it) first, and then reboot the master Routing Engine. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • clear system reboot on page 204 request system reboot on page 102 request system reboot (at 2300) on page 102 request system reboot (in 2 Hours) on page 103 request system reboot (Immediately) on page 103 request system reboot (at 1:20 AM) on page 103 When you enter this command, you are provided feedback on the status of your request. 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] 102 Chapter 10: Operational Mode Commands for Software Installation *** 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 103 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request system reboot Syntax Release Information Description request system reboot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reboot 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. 104 Chapter 10: Operational Mode Commands for Software Installation 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 204 When you enter this command, you are provided feedback on the status of your request. 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 105 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 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. 106 • re0—Create a snapshot on Routing Engine 0. • re1—Create a snapshot on Routing Engine 1. Chapter 10: Operational Mode Commands for Software Installation • 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 request system snapshot media external slice 1 view • show system snapshot on page 122 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 80 When you enter this command, you are provided feedback on the status of your request. user@switch> request system snapshot media external slice 1 107 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request system software add Syntax Release Information Description Options request system software add package-name Command introduced before Junos OS Release 10.2 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 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. 108 Chapter 10: Operational Mode Commands for Software Installation 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. unlink—(Optional) Remove the software package from this directory after a successful upgrade is completed. 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 109 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation List of Sample Output maintenance • request system software delete on page 111 • request system software rollback on page 113 • request system storage cleanup on page 227 request system software add validate on page 110 Output Fields When you enter this command, you are provided feedback on the status of your request. 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 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 ... 110 Chapter 10: Operational Mode 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 OS base software suite • jcrypto—(Optional, in domestic version only) Junos OS security software • jdocs—(Optional) Junos OS online documentation file • jkernel—(Optional) Junos OS kernel software suite • jpfe—(Optional) Junos OS Packet Forwarding Engine support • jroute—(Optional) Junos OS routing software suite • junos—(Optional) Junos OS 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 108 • request system software rollback on page 113 • request system software validate on page 115 request system software delete jdocs on page 112 111 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output Fields When you enter this command, you are provided feedback on the status of your request. 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] ... 112 Chapter 10: Operational Mode 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 Use this command only to recover from a failed software upgrade—you cannot issue this command to return to the previously installed software after using a jinstall package. To return to the previously installed software, use the corresponding jinstall package. A software rollback fails if any required package (or a jbundle package containing the required package) cannot be found in /var/sw/pkg. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • request system software add on page 108 • request system software delete on page 111 • request system software validate on page 115 • request system configuration rescue delete on page 376 • request system configuration rescue save on page 377 request system software rollback on page 114 When you enter this command, you are provided feedback on the status of your request. 113 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 114 Chapter 10: Operational Mode 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 add on page 108 • request system software delete on page 111 • request system software rollback on page 113 request system software validate (Successful Case) on page 116 request system software validate (Failure Case) on page 116 When you enter this command, you are provided feedback on the status of your request. 115 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 116 Chapter 10: Operational Mode Commands for Software Installation show system autoinstallation status Syntax Release Information Description Options Required Privilege Level show system autoinstallation status Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display autoinstallation status information. This command has no options. view List of Sample Output show system autoinstallation status on page 117 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 117 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 118 view Chapter 10: Operational Mode Commands for Software Installation show system license Syntax show system license Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display licenses and information about how they are used. Options 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 maintenance List of Sample Output show system license on page 120 show system license installed on page 120 show system license keys on page 120 show system license usage on page 120 Output Fields Table 24 on page 119 lists the output fields for the show system license command. Output fields are listed in the approximate order in which they appear. Table 24: 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. 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. Licenses needed • 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). Number of licenses required for features being used but not yet properly licensed. 119 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 24: show system license Output Fields (continued) Field Name Field Description Expiry Amount of time left within the grace period before a license is required for a feature being used. 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 0 0 0 0 0 0 0 0 Licenses installed 1 1 1 1 1 1000 1000 1000 Licenses needed 0 0 0 0 0 0 0 0 Expiry permanent permanent permanent permanent permanent permanent permanent permanent 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 show system license installed 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 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 Feature name 120 Licenses used Licenses installed Licenses needed Expiry Chapter 10: Operational Mode Commands for Software Installation subscriber-accounting 1 1 0 permanent subscriber-authentication 1 1 0 permanent subscriber-address-assignment 1 1 0 permanent subscriber-vlan 0 1 0 permanent subscriber-ip 0 1 0 permanent 121 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 show system snapshot media external 122 view • request system snapshot on page 106 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 80 • Verifying That a System Snapshot Was Created on a J-EX Series Switch on page 88 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: jbase : 10.0I20090726_0011_user jcrypto-ex: 10.0I20090726_0011_user Chapter 10: Operational Mode Commands for Software Installation 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 123 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 124 PART 4 User Interfaces • User Interfaces Overview on page 127 • Using the Configuration Tools on page 135 • Operational Mode Commands for User Interfaces on page 137 125 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 126 CHAPTER 11 User Interfaces Overview • User Interfaces—Overview on page 127 User Interfaces—Overview • CLI User Interface Overview on page 127 • J-Web User Interface for J-EX Series Switches Overview on page 129 • Understanding J-Web Configuration Tools on page 131 • Understanding J-Web User Interface Sessions on page 133 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 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 129. • CLI Overview on page 127 • CLI Help and Command Completion on page 127 • CLI Command Modes on page 128 CLI Overview 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. 127 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 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 128 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 at http://www.juniper.net/techpubs/software/junos/. 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 of these 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 127. 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. 129 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS The layout of the panes allows you to quickly navigate through the interface. Table 25 on page 130 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 25: J-Web Interface J-Web Interface Element Description Top Pane Host The hostname of the switch. Logged in as: username The user name 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 130 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 25: 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 affect 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 334 • J-EX Series Switch Software Features Overview on page 3 • J-EX4200 Switches Hardware Overview on page 25 • J-EX Series Switch Software Features Overview on page 3 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • CLI User Interface Overview on page 127 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 131 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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, so you can fully configure the switch without using the CLI. The J-Web interface provides three methods of configuring the switch: • Configure menu • Point & Click CLI Editor • CLI Editor Table 26 on page 132 gives a comparison of the three methods of configuration. Table 26: 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. For example, use the Virtual Chassis Configuration page to configure the Virtual Chassis parameters on the switch. Point & Click CLI editor • Switching • Virtual Chassis • Security • Services • System Properties • Routing Configure all switching platform services: • • System parameters • User Accounting and Access • Interfaces • VLAN properties 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. • Paste a complete configuration hierarchy into a scrollable text box, or edit individual lines. • Virtual Chassis properties • 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: • • • • 132 Interfaces Web browser pages divided into panes in which you can do any of the following: • CLI editor • Type commands on a line and press Enter to create a hierarchy of configuration statements. Configure all switching platform services: • 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 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 133 • J-Web User Interface for J-EX Series Switches Overview on page 129 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • Configuration Files Terms on page 322 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 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 398. 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 129 • Configuring Management Access for the J-EX Series Switch (J-Web Procedure) on page 395 133 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 134 CHAPTER 12 Using the Configuration Tools • Using the CLI Terminal on page 135 • Starting the J-Web Interface on page 136 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. 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. • 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 168 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. 135 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • 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 127 • Understanding J-Web Configuration Tools on page 131 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 136 • J-Web User Interface for J-EX Series Switches Overview on page 129 • Understanding How to Use the J-Web Interface to View System Information CHAPTER 13 Operational Mode Commands for User Interfaces 137 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 view • show cli on page 147 set cli complete-on-space on page 138 Output Fields When you enter this command, you are provided feedback on the status of your request. 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 138 Chapter 13: Operational Mode 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 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 • show cli directory on page 152 set cli directory on page 139 When you enter this command, you are provided feedback on the status of your request. user@host> set cli directory /var/home/regress Current directory: /var/home/regress 139 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 set cli idle-timeout 140 view • show cli on page 147 set cli idle-timeout on page 140 When you enter this command, you are provided feedback on the status of your request. user@host> set cli idle-timeout 60 Idle timeout set to 60 minutes Chapter 13: Operational Mode 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 view • show cli on page 147 set cli prompt on page 141 Output Fields When you enter this command, the new CLI prompt is displayed. set cli prompt user@host> set cli prompt lab1-router> lab1-router> 141 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 set cli restart-on-upgrade 142 view • show cli on page 147 set cli restart-on-upgrade on page 142 When you enter this command, you are provided feedback on the status of your request. user@host> set cli restart-on-upgrade on Enabling restart-on-upgrade Chapter 13: Operational Mode 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. The range of values, in number of lines, is 24 through 100,000. The default is 24. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields set cli screen-length 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 • set cli screen-width on page 144 • set cli terminal on page 145 • show cli on page 147 set cli screen-length on page 143 When you enter this command, you are provided feedback on the status of your request. user@host> set cli screen-length 75 Screen length set to 75 143 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS set cli screen-width Syntax Release Information Description Options 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 in a line. The range of values is 80 through 100,000. The default is 80. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields set cli screen-width 144 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 • set cli screen-length on page 143 • set cli terminal on page 145 • show cli on page 147 set cli screen-width on page 144 When you enter this command, you are provided feedback on the status of your request. user@host> set cli screen-width Screen width set to 132 Chapter 13: Operational Mode 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 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 • show cli on page 147 set cli terminal on page 145 This command provides no output. user@host> set cli terminal xterm 145 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 set cli timestamp 146 view • show cli on page 147 set cli timestamp on page 146 When you enter this command, you are provided feedback on the status of your request. user@host> set cli timestamp format '%m-%d-%T' '04-21-17:39:13' CLI timestamp set to: '%m-%d-%T' Chapter 13: Operational Mode 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 147 Table 27 on page 147 lists the output fields for the show cli command. Output fields are listed in the approximate order in which they appear. Table 27: 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. 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 CLI timestamp disabled CLI working directory is '/var/home/regress' 147 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 148 Chapter 13: Operational Mode 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 150 Table 28 on page 149 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 28: 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. 149 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 28: show cli authorization Output Fields (continued) show cli authorization 150 Field Name Field Description 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. reset Can reset or restart interfaces and system processes. rollback Can rollback 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. view-configuration Can view all configuration information (not including secrets). user@host> show cli authorization Current user: 'remote' login: 'user' class '' Permissions: admin -- Can view user accounts Chapter 13: Operational Mode Commands for User Interfaces 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 151 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 152 Table 29 on page 152 lists the output fields for the show cli directory command. Output fields are listed in the approximate order in which they appear. Table 29: show cli directory Output Fields show cli directory 152 Field Name Field Description Current directory Pathname of the current working directory. user@host> show cli directory Current directory: /var/home/regress Chapter 13: Operational Mode 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 153 Table 30 on page 153 lists the output fields for the show cli history command. Output fields are listed in the approximate order in which they appear. Table 30: show cli history Output Fields show cli history Field Name Field Description timestamp Time at which the command was entered. command-syntax Command that was entered. user@host> 11:14:14 11:22:10 11:27:12 show cli history -- show arp -- show cli authorization -- show cli history 153 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS start shell Syntax Release Information Description Options 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. 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@router% Required Privilege Level List of Sample Output shell and maintenance start shell csh on page 154 Output Fields When you enter this command, you are provided feedback on the status of your request. start shell csh user@host> start shell csh % exit % username@hostname% start shell sh % exit user@host> 154 PART 5 Junos OS for J-EX Series Switches System Setup • System Setup Overview on page 157 • Initial Configuration on page 161 • Configuration Statements for System Setup on page 171 • Operational Mode Commands for System Setup on page 201 155 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 156 CHAPTER 14 System Setup Overview • Junos OS—Overview on page 157 Junos OS—Overview • J-EX Series Switch Software Features Overview on page 157 • Understanding Software Infrastructure and Processes on page 158 J-EX Series Switch Software Features Overview The following tables list the J-EX Series Switches software features and the Junos OS release in which they were introduced: Related Documentation • Table 4 on page 4—Access Control Features • Table 5 on page 4—Administration Features • Table 6 on page 4—Class-of-Service (CoS) Features • Table 7 on page 5—High Availability and Resiliency Features • Table 8 on page 6—Interfaces Features • Table 9 on page 7—IP Address Management Features • Table 10 on page 7—IPv6 Features • Table 11 on page 7—Layer 2 Network Protocols Features • Table 12 on page 8—Layer 3 Protocols Features • Table 13 on page 9—MPLS Features • Table 14 on page 10—Multicast Features • Table 15 on page 10—Network Management and Monitoring Features • Table 16 on page 11—Port Security Features • Table 17 on page 12—System Management Features • High Availability Features for J-EX Series Switches Overview on page 18 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 14 157 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • J-EX8208 Switch Hardware Overview on page 27 • J-EX8216 Switch Hardware Overview on page 30 Understanding Software Infrastructure and Processes Each switch runs Junos OS for J-EX Series Switches on its general-purpose processors. The Junos OS includes processes for Internet Protocol (IP) routing and for managing interfaces, networks, and the chassis. 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 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 158 • Junos OS Processes on page 158 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. • Provides control and monitoring functions for the switch, including controlling power and monitoring system status. Junos OS Processes 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 Junos OS, for added flexibility. Table 55 on page 393 describes the primary Junos OS processes. 158 Chapter 14: System Setup Overview Related Documentation • For more information about processes, see the Junos OS Network Operations Guide at http://www.juniper.net/techpubs/software/junos/. • For more information about basic system parameters, supported protocols, and software processes, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. 159 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 160 CHAPTER 15 Initial Configuration • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 166 • Configuring Date and Time for the J-EX Series Switch (J-Web Procedure) on page 167 • Configuring System Identity for a J-EX Series Switch (J-Web Procedure) on page 168 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 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 341. 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 161 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Stop Bits—1 • DCD State—Disregard To connect and configure the switch from the console: 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-EX4200 switch—The console port is located on the rear 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-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. The configured parameters are displayed. Enter yes to commit the configuration. 162 Chapter 15: Initial Configuration The configuration is committed as the active configuration for the switch. 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 163 • Installing and Connecting a J-EX4200 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 CLI and the other is using the J-Web interface. This topic describes the J-Web procedure. 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. NOTE: Before you begin the configuration, enable a DHCP client on the management PC you will connect to the switch so that the switch can obtain an IP address dynamically. 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. The LCD displays a count-down timer when the switch is in initial setup mode. 163 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To connect and configure the switch using the J-Web interface: 1. Transition the switch into initial setup mode by using the Menu and Enter buttons located to the right of the LCD panel (see Figure 4 on page 164) Figure 4: LCD Panel in a J-EX4200 or J-EX8200 Switch a. Press the Menu button until you see MAINTENANCE MENU. Then press the Enter button. b. 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 only when the switch is set to the factory default configuration. c. 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-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. 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: a. Enter the hostname. This is optional. b. Enter a password and reenter the password. c. Specify the time zone. 164 Chapter 15: Initial Configuration d. 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. e. Click Next. 7. Use the Management Options page to select the management scenario: NOTE: On 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. 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. 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. Related Documentation • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Installing and Connecting a J-EX4200 Switch 165 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • 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 166 • Configuring a Custom Display Message on page 167 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. 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 166 Chapter 15: Initial Configuration 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 J-EX4200 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 switch or a J-EX8200 switch: user@switch> set chassis display message message permanent • On a J-EX4200 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. Related Documentation • LCD Panel in J-EX4200 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 31 on page 168. 3. Click one: • To apply the configuration, click OK. • To cancel your entries and return to the System Properties page, click Cancel. 167 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 334 for details about all commit options. Table 31: 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: • 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. • Related Documentation • 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 129 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 32 on page 169. 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 334 for details about all commit options. 168 Chapter 15: Initial Configuration Table 32: 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 167 169 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 170 CHAPTER 16 Configuration Statements for System Setup arp Syntax Hierarchy Level Release Information arp { aging-timer minutes; passive-learning; } [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. passive-learning—Configures backup VRRP routers or switches to learn the ARP mappings (IP-to-MAC address) for hosts sending the requests. By default, the backup VRRP router drops these requests; therefore, if the master router fails, the backup router must learn all entries present in the ARP cache of the master router. Configuring passive learning reduces transition delay when the backup router is activated. Default: 20 minutes Range: 5 to 240 minutes 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 ARP Learning and Aging Options for Mapping IPv4 Network Addresses to MAC Addresses • Junos OS Network Interfaces Configuration Guide 171 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 172 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring NTP Authentication Keys • broadcast on page 174 • peer on page 194 • server on page 197 • trusted-key on page 200 Chapter 16: Configuration Statements for System Setup auxiliary Syntax Hierarchy Level Release Information Description Default Options auxiliary { 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. 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 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 boot-server (NTP) Syntax Hierarchy Level Release Information Description boot-server address; [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. Options Required Privilege Level Related Documentation address—Address of an NTP server. You must specify an address, not a hostname. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Synchronizing and Coordinating Time Distribution Using NTP 173 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 174 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 175 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 176 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 Description Default Required Privilege Level Related Documentation default-address-selection; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Use the loopback interface, lo0, as the source address for all locally generated IP packets. The lo0 interface is the interface to the router’s or switch’s Routing Engine. The outgoing interface is used as the source address. 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 domain-name (Router) 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 177 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS gre-path-mtu-discovery Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation (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 host-name Syntax Hierarchy Level Release Information [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 178 host-name hostname; 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 Chapter 16: Configuration Statements for System Setup 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 179 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 180 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 181 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 DoS attacks. The remaining statements are explained separately. Required Privilege Level Related Documentation 182 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 • Configuring TCP MSS for Session Negotiation Chapter 16: Configuration Statements for System Setup 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 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 183 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 184 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 185 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS lcd-menu Syntax J-EX4200 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 switches only) Disable or enable the specified menu or menu options, where slot-number is: • 0—On a standalone J-EX4200 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 186 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 166 • LCD Panel in J-EX4200 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 187 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS menu-item Syntax Hierarchy Level Release Information Description Options menu-item (menu-name | menu-option); [edit chassis lcd-menu] 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 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 • 188 ''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 166 • LCD Panel in J-EX4200 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 189 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 190 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 191 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 192 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 193 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 194 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 { type terminal-type; } console { 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 195 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 OS kernel) Required Privilege Level Related Documentation 196 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 197 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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: 198 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 199 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 200 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 172 • broadcast on page 174 • peer on page 194 • server on page 197 CHAPTER 17 Operational Mode Commands for System Setup 201 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear chassis display message Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields clear chassis display message 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 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. none—Clear or stop a text message on the craft interface display. clear • Configuring the LCD Panel Display on J-EX Series Switches (CLI Procedure) on page 166 • set chassis display message on page 233 • show chassis craft-interface clear chassis display message on page 202 See show chassis craft-interface for an explanation of output fields. 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 Host fail LED: Off FPCs 0 1 2 3 4 5 6 7 202 Chapter 17: Operational Mode Commands for System Setup ------------------------------Green .. *.. * *. Red ........ LCD screen: +--------------------+ |host | |Up: 0+17:05:47 | | | |Temperature OK | +--------------------+ 203 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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. On a TX Matrix router, clear both Routing Engines on all chassis connected to the TX Matrix router. Likewise, on a TX Matrix Plus router, clear both Routing Engines on all chassis connected to the TX Matrix Plus router. 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 204 maintenance • request system reboot on page 101 clear system reboot on page 205 When you enter this command, you are provided feedback on the status of your request. Chapter 17: Operational Mode Commands for System Setup clear system reboot user@host> clear system reboot reboot requested by root at Sat Dec 12 19:37:34 1998 [process id 17855] Terminating... 205 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 configure 206 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 244 configure on page 206 When you enter this command, you are placed in configuration mode and the system prompt changes from hostname> to hostname#. user@host> configure Entering configuration mode [edit] user@host# Chapter 17: Operational Mode Commands for System Setup 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 For more information about Junos OS 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 364 • file checksum sha-256 on page 366 • file checksum sha1 on page 365 op on page 208 op url on page 208 207 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output Fields op op url 208 When you enter this command, you are provided feedback on the status of your request. 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 Chapter 17: Operational Mode Commands for System Setup 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 request chassis pic maintenance • show chassis hardware on page 643 • show chassis pic on page 650 request chassis pic on page 209 When you enter this command, you are provided feedback on the status of your request. user@host> request chassis pic pic-slot 0 online fpc-slot 0 FPC 0, PIC 0 is already online 209 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 210 Chapter 17: Operational Mode Commands for System Setup 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 request chassis routing-engine master acquire maintenance • show chassis routing-engine on page 653 request chassis routing-engine master acquire on page 211 request chassis routing-engine master switch on page 211 When you enter this command, you are provided feedback on the status of your request. 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. 211 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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. (The options removable-compact-flash and usb pertain to J Series routers only.) 212 Chapter 17: Operational Mode Commands for System Setup media (external | internal)—(J-EX Series switches only) (Optional) Halt the boot media: • 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 only) (Optional) Halt a partition on the boot media. This option has the following suboptions: Additional Information Required Privilege Level List of Sample Output Output Fields • 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 request system halt on page 214 request system halt (in 2 Hours) on page 214 request system halt (Immediately) on page 214 request system halt (at 1:20 AM) on page 214 When you enter this command, you are provided feedback on the status of your request. 213 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 214 Chapter 17: Operational Mode Commands for System Setup 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. (On a TX Matrix or TX Matrix Plus router, this command is broadcast to all chassis.) 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. Additional Information Required Privilege Level List of Sample Output Output Fields request system logout For information about using the configure exclusive command, see the Junos OS System Basics Configuration Guide. configure request system logout on page 215 When you enter this command, you are provided feedback on the status of your request. user@host> request system logout user tammy all Connection closed by foreign host. 215 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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.) 216 Chapter 17: Operational Mode Commands for System Setup media (external | internal)—(J-EX Series switches only) (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 only) (Optional) Power off a partition on the boot media. This option has the following suboptions: Required Privilege Level List of Sample Output Output Fields request system power-off • 1—Power off partition 1. • 2—Power off partition 2. • alternate—Reboot from the alternate partition. maintenance request system power-off on page 217 When you enter this command, you are provided feedback on the status of your request. 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] 217 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request system reboot Syntax Syntax (J-EX Series Switch) Release Information Description Options request system reboot request system reboot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reboot the software. none—Reboot the software immediately. all-members—(J-EX4200 switches only) (Optional) Reboot all members of the Virtual Chassis configuration. at time—(Optional) Time at which to reboot the software, specified in one of the following ways: • now—Stop or reboot the software immediately. This is the default. • +minutes—Number of minutes from now to reboot the software. • yymmddhhmm—Absolute time at which to reboot the software, specified as year, month, day, hour, and minute. • hh:mm—Absolute time on the current day at which to stop the software, specified in 24-hour time. in minutes—(Optional) Number of minutes from now to reboot the software. This option is an alias for the at +minutes option. local—(J-EX4200 switches only) (Optional) Reboot 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.) media (external | internal)—(J-EX Series switches only) (Optional) Reboot the boot media: • 218 external—Reboot the external mass storage device. Chapter 17: Operational Mode Commands for System Setup • internal—Reboot the internal flash device. member member-id—(J-EX4200 switches only) (Optional) Reboot 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 or rebooting the software. 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 slice—(J-EX Series switches only) (Optional) Reboot a partition on the boot media. This option has the following suboptions: Additional Information • 1—Power off partition 1. • 2—Power off partition 2. • alternate—Reboot from the alternate partition. Reboot requests are recorded in the system log files, which you can view with the show log command (see show log). Also, the names of any running processes that are scheduled to be shut down are changed. You can view the process names with the show system processes command (see show system processes). NOTE: To reboot a router that has two Routing Engines, reboot the backup Routing Engine (if you have upgraded it) first, and then reboot the master Routing Engine. Required Privilege Level Related Documentation List of Sample Output Output Fields request system reboot maintenance • clear system reboot on page 204 request system reboot on page 219 request system reboot (at 2300) on page 220 request system reboot (in 2 Hours) on page 220 request system reboot (Immediately) on page 220 request system reboot (at 1:20 AM) on page 220 When you enter this command, you are provided feedback on the status of your request. user@host> request system reboot Reboot the system ? [yes,no] (no) 219 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 220 Chapter 17: Operational Mode 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. 221 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 204 When you enter this command, you are provided feedback on the status of your request. 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 222 Chapter 17: Operational Mode 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 223 request system scripts convert xslt-to-slax on page 223 When you enter this command, you are provided feedback on the status of your request. 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 223 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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: 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from commit file config.txt url http://host1.juniper.net on page 224 request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> 224 Chapter 17: Operational Mode 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: 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from event file config.txt url http://host1.juniper.net on page 225 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> 225 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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: op 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from op file config.txt url http://host1.juniper.net on page 226 request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> 226 Chapter 17: Operational Mode Commands for System Setup request system storage cleanup Syntax Syntax (J-EX Series Switch) Release Information Description Options request system storage cleanup 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 request system storage cleanup dry-run 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 227 request system storage cleanup on page 228 When you enter this command, you are provided feedback on the status of your request. 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 4146B 4708B Size Date 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 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 /var/log/sampled.0.gz /var/log/sampled.2.gz 227 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 7068B 13.7K 890B 65.8M 63.1M request system storage cleanup Jan Dec Feb Oct Oct 16 27 22 26 26 18:00 22:00 17:22 09:10 09:13 /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) 228 Chapter 17: Operational Mode 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. 229 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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. 230 Chapter 17: Operational Mode 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. 231 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 restart interfaces 232 reset • Overview of Junos OS CLI Operational Mode Commands restart interfaces on page 232 When you enter this command, you are provided feedback on the status of your request. user@host> restart interfaces interfaces process terminated interfaces process restarted Chapter 17: Operational Mode 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 switches only) On the router, 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 set chassis display message (Creating) clear • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 166 • clear chassis display message on page 202 • show chassis craft-interface set chassis display message (Creating) on page 233 set chassis display message (Deleting) on page 234 See show chassis craft-interface for an explanation of output fields. 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" message sent user@host> show chassis craft-interface 233 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 | +--------------------+ 234 Chapter 17: Operational Mode 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. ntp-server—(Optional) Specify the IP address of one or more NTP servers. source-address source-address—(Optional) 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 view • show cli on page 147 set date on page 235 Output Fields When you enter this command, you are provided feedback on the status of your request. 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 235 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis firmware Syntax Release Information Description show chassis firmware Command introduced in Junos OS Release 10.2 for J-EX Series switches. On the routers, 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), and Flexible PIC Concentrators (FPCs). On a TX Matrix Plus router, display the version levels of the firmware running on the FPCs and the Switch Processor Mezzanine Board (SPMBs). 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-EX8200 Switch) on page 236 Table 33 on page 236 lists the output fields for the show chassis firmware command. Output fields are listed in the approximate order in which they appear. Table 33: show chassis firmware Output Fields show chassis firmware (J-EX8200 Switch) 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. user@host> show chassis firmware Part FPC 0 FPC 3 FPC 5 FPC 7 Routing Engine 0 236 Type U-Boot loader U-Boot loader U-Boot loader U-Boot loader U-Boot 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 Chapter 17: Operational Mode Commands for System Setup FreeBSD/PowerPC U-Boot bootstrap loader 2.2 Routing Engine 1 loader U-Boot loader U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 237 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis lcd Syntax Release Information Description Options show chassis lcd > > Command introduced before Junos OS Release 10.2 for J-EX Series switches. menu option introduced in Junos OS Release 10.2 for J-EX Series switches. Display the information that appears on the LCD panel of J-EX4200 and J-EX8200 switches. Display the status of the currently selected port parameter of the Status LED for each network port on the switch or line card. none—Display the information that appears on the LCD panel (for J-EX4200 switches configured as a Virtual Chassis, display the information for all Virtual Chassis members). Display the status of the currently selected port parameter of the Status LED for each network port. fpc-slot —(Optional) Display the information as follows: • For the standalone J-EX4200 switch (fpc-slot-number equals 0) • For all J-EX4200 switches in a Virtual Chassis (fpc-slot with no fpc-slot-number value specified) • For a specific Virtual Chassis member (fpc-slot-number equals member ID value) • For the line card in the specified slot on a J-EX8200 switch (fpc-slot-number equals slot number) menu—(Optional) Display the names of the menus and menu options that are currently enabled on the LCD panel. menu all-members—(J-EX4200 switches only) (Optional) Display the names of the menus and menu options that are currently enabled on the LCD panel for all Virtual Chassis members. menu local—(J-EX4200 switches only) (Optional) Display the names of the menus and menu options that are currently enabled on the LCD panel for the Virtual Chassis member from which you issued the command. menu member member-id—(J-EX4200 switches only) (Optional) Display the names of the menus and menu options that are currently enabled on the LCD panel for the specified Virtual Chassis member. Required Privilege Level Related Documentation 238 view • LCD Panel in J-EX4200 Switches • LCD Panel in a J-EX8200 Switch • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 166 Chapter 17: Operational Mode Commands for System Setup List of Sample Output Output Fields show chassis lcd (Two-Member Virtual Chassis) on page 239 show chassis lcd fpc-slot 1 (Virtual Chassis) on page 241 show chassis lcd (J-EX8200) on page 241 show chassis lcd fpc-slot 2 (J-EX8200) on page 243 show chassis lcd menu (J-EX4200) on page 243 show chassis lcd menu (J-EX8200) on page 243 Table 34 on page 239 lists the output fields for the show chassis lcd command. Output fields are listed in the approximate order in which they appear. Table 34: show chassis lcd Output Fields Field Name Field Description Front panel contents for slot FPC slot number of the switch whose content is being displayed. The number is always 0, except for J-EX4200 switches in a Virtual Chassis, where it is the member ID value. Front panel contents On J-EX8200 switches, no slot number is displayed. (J-EX8200 switches) LCD screen The first line displays the hostname (for Virtual Chassis members, displays the member ID, the current role, and hostname; for J-EX8200 switches, displays RE and the hostname). The second line displays the currently selected port parameter of the Status LED and the alarms counter. The Status LED port parameters are: • ADM—Administrative • SPD—Speed • DPX—Duplex • POE—Power over Ethernet (J-EX4200 switches only) LEDs status Current state of the Alarms, Status, and Master LEDs (chassis status LEDs). Interface Names of the interfaces on the switch. LED (ADM/SPD/DPX/POE) State of the currently selected port parameter of the Status LED for the interface. The Status LED port parameters are: NOTE: J-EX8200 switches do not have the POE port parameter. fpcx • ADM—Administrative • SPD—Speed • DPX—Duplex • POE—Power over Ethernet On J-EX4200 switches, member ID of the Virtual Chassis member whose LCD menu is displayed. show chassis lcd (Two-Member Virtual Chassis) user@switch> show chassis lcd Front panel contents for slot: 0 --------------------------------LCD screen: 239 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 00:BK switch1 LED:SPD ALARM 00 LEDs status: Alarms LED: Off Status LED: Green Master LED: Off Interface LED(ADM/SPD/DPX/POE) ------------------------------------ge-0/0/0 Off ge-0/0/1 Off ge-0/0/2 Off ge-0/0/3 Off ge-0/0/4 Off ge-0/0/5 Off ge-0/0/6 Off ge-0/0/7 Off ge-0/0/8 Off ge-0/0/9 Off ge-0/0/10 Off ge-0/0/11 Off ge-0/0/12 Off ge-0/0/13 Off ge-0/0/14 Off ge-0/0/15 Off ge-0/0/16 Off ge-0/0/17 Off ge-0/0/18 Off ge-0/0/19 Off ge-0/0/20 Off ge-0/0/21 Off ge-0/0/22 Off ge-0/0/23 Off Front panel contents for slot: 1 --------------------------------LCD screen: 01:RE switch2 LED:SPD ALARM 01 LEDs status: Alarms LED: Yellow Status LED: Green Master LED: Green Interface LED(ADM/SPD/DPX/POE) ------------------------------------ge-1/0/0 Off ge-1/0/1 Off ge-1/0/2 Off ge-1/0/3 Off ge-1/0/4 Off ge-1/0/5 Off ge-1/0/6 Off ge-1/0/7 Off ge-1/0/8 Off ge-1/0/9 Off ge-1/0/10 Off ge-1/0/11 Off ge-1/0/12 Off ge-1/0/13 Off ge-1/0/14 Off ge-1/0/15 Off ge-1/0/16 Off ge-1/0/17 Off 240 Chapter 17: Operational Mode Commands for System Setup ge-1/0/18 ge-1/0/19 ge-1/0/20 ge-1/0/21 ge-1/0/22 ge-1/0/23 Off Off Off Off Off Off The output for the show chassis lcd fpc-slot command is the same as the output for the show chassis lcd command. show chassis lcd fpc-slot 1 (Virtual Chassis) show chassis lcd (J-EX8200) user@switch> show chassis lcd fpc-slot 1 Front panel contents for slot: 1 --------------------------------LCD screen: 01:RE switch2 LED:SPD ALARM 01 LEDs status: Alarms LED: Yellow Status LED: Green Master LED: Green Interface LED(ADM/SPD/DPX/POE) ------------------------------------ge-1/0/0 Off ge-1/0/1 Off ge-1/0/2 Off ge-1/0/3 Off ge-1/0/4 Off ge-1/0/5 Off ge-1/0/6 Off ge-1/0/7 Off ge-1/0/8 Off ge-1/0/9 Off ge-1/0/10 Off ge-1/0/11 Off ge-1/0/12 Off ge-1/0/13 Off ge-1/0/14 Off ge-1/0/15 Off ge-1/0/16 Off ge-1/0/17 Off ge-1/0/18 Off ge-1/0/19 Off ge-1/0/20 Off ge-1/0/21 Off ge-1/0/22 Off ge-1/0/23 Off show chassis lcd Front panel contents: --------------------LCD screen: RE st-8200-r LED:ADM ALARM 01 LEDs status: Alarms LED: Yellow Status LED: Yellow Master LED: Green Interface LED(ADM/SPD/DPX) ------------------------------------------ 241 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/0 ge-0/0/1 ge-0/0/2 ge-0/0/3 ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 ge-0/0/8 ge-0/0/9 ge-0/0/10 ge-0/0/11 ge-0/0/12 ge-0/0/13 ge-0/0/14 ge-0/0/15 ge-0/0/16 ge-0/0/17 ge-0/0/18 ge-0/0/19 ge-0/0/20 ge-0/0/21 ge-0/0/22 ge-0/0/23 ge-0/0/24 ge-0/0/25 ge-0/0/26 ge-0/0/27 ge-0/0/28 ge-0/0/29 ge-0/0/30 ge-0/0/31 ge-0/0/32 ge-0/0/33 ge-0/0/34 ge-0/0/35 ge-0/0/36 ge-0/0/37 ge-0/0/38 ge-0/0/39 ge-0/0/40 ge-0/0/41 ge-0/0/42 ge-0/0/43 ge-0/0/44 ge-0/0/45 ge-0/0/46 ge-0/0/47 xe-2/0/0 xe-2/0/1 xe-2/0/2 xe-2/0/3 xe-2/0/4 xe-2/0/5 xe-2/0/6 xe-2/0/7 xe-3/0/0 xe-3/0/1 xe-3/0/2 xe-3/0/3 xe-3/0/4 242 Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Chapter 17: Operational Mode Commands for System Setup xe-3/0/5 xe-3/0/6 xe-3/0/7 xe-5/0/0 xe-5/0/1 xe-5/0/2 xe-5/0/3 xe-5/0/4 xe-5/0/5 xe-5/0/6 xe-5/0/7 xe-7/0/5 show chassis lcd fpc-slot 2 (J-EX8200) Off Off Off Off Off Off Off Off Off On On Off show chassis lcd fpc-slot 2 Interface LED(ADM/SPD/DPX) -----------------------------------------xe-2/0/0 Off xe-2/0/1 Off xe-2/0/2 Off xe-2/0/3 Off xe-2/0/4 Off xe-2/0/5 Off xe-2/0/6 Off xe-2/0/7 Off show chassis lcd menu (J-EX4200) user@switch> show chassis lcd menu fpc0: -------------------------------------------------------------------------status-menu status-menu vcp-status status-menu power-status status-menu environ-menu status-menu show-version maintenance-menu maintenance-menu halt-menu maintenance-menu system-reboot maintenance-menu rescue-config maintenance-menu vc-uplink-config maintenance-menu factory-default On a J-EX4200 switch in a Virtual Chassis, the output for the show chassis lcd menu all-members command is the same as the output for the show chassis lcd menu command. show chassis lcd menu (J-EX8200) user@switch> show chassis lcd menu status-menu status-menu sf-status1-menu status-menu sf-status2-menu status-menu psu-status1-menu status-menu psu-status2-menu status-menu environ-menu status-menu show-version maintenance-menu maintenance-menu halt-menu maintenance-menu system-reboot maintenance-menu rescue-config maintenance-menu factory-default 243 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show configuration Syntax Release Information Description Options show configuration Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the configuration that currently is running on the router or switch, which is the last committed configuration. none—Display the entire configuration. statement-path—(Optional) Display one of the following hierarchies in a configuration. (Each statement-path option has additional suboptions not described here. See the appropriate configuration guide or J-EX Series switch documentation for more information.) • access—Network access configuration. • access-profile—Access profile configuration. • accounting-options—Accounting data configuration. • applications—Applications defined by protocol characteristics. • apply-groups—Groups from which configuration data is inherited. • chassis—Chassis configuration. • chassis network-services—Current running mode. • class-of-service—Class-of-service configuration. • diameter—Diameter base protocol layer configuration. • ethernet-switching-options—(J-EX Series switch only) Ethernet switching configuration. 244 • event-options—Event processing configuration. • firewall—Firewall configuration. • forwarding-options—Options that control packet sampling. • groups—Configuration groups. • interfaces—Interface configuration. • jsrc—JSRC partition configuration. • jsrc-partition—JSRC partition configuration. • logical-systems—Logical system configuration. • poe—(J-EX Series switch only) Power over Ethernet configuration. • policy-options—Routing policy option configuration. • protocols—Routing protocol configuration. Chapter 17: Operational Mode Commands for System Setup Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields show configuration • routing-instances—Routing instance configuration. • routing-options—Protocol-independent routing option configuration. • security—Security configuration. • services—Service PIC applications configuration. • snmp—Simple Network Management Protocol configuration. • system—System parameters configuration. • virtual-chassis—(J-EX Series switch only) Virtual Chassis configuration. • vlans—(J-EX Series switch only) VLAN configuration. The portions of the configuration that you can view depend on the user class that you belong to and the corresponding permissions. If you do not have permission to view a portion of the configuration, the text ACCESS-DENIED is substituted for that portion of the configuration. If you do not have permission to view authentication keys and passwords in the configuration, because the secret permission bit is not set for your user account, the text SECRET-DATA is substituted for that portion of the configuration. If an identifier in the configuration contains a space, the identifier is displayed in quotation marks. view • Displaying the Current Junos OS Configuration • Overview of Junos OS CLI Operational Mode Commands show configuration on page 245 show configuration policy-options on page 246 This command displays information about the current running configuration. user@host> show configuration ## Last commit: 2006-10-31 14:13:00 PST by alant version "8.2I0 [builder]"; ## last changed: 2006-10-31 14:05:53 PST system { host-name nestor; domain-name east.net; backup-router 192.1.1.254; time-zone America/Los_Angeles; default-address-selection; name-server { 192.154.169.254; 192.154.169.249; 192.154.169.176; } services { telnet; } tacplus-server { 1.2.3.4 { secret /* SECRET-DATA */; 245 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ... } } } interfaces { ... } protocols { isis { export "direct routes"; } } policy-options { policy-statement "direct routes" { from protocol direct; then accept; } } show configuration policy-options 246 user@host> show configuration policy-options policy-options { policy-statement "direct routes" { from protocol direct; then accept; } } Chapter 17: Operational Mode Commands for System Setup show host Syntax Release Information Description Options Additional Information Required Privilege Level List of Sample Output show host show host hostname Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Domain Name System (DNS) hostname information. hostname—Hostname or address. The show host command displays the raw data received from the DNS server. view show host on page 247 user@host> show host snark snark.boojum.net has address 192.168.1.254 user@host> show host 192.168.1.254 Name: snark.boojum.net Address: 192.168.1.254 Aliases: 247 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ntp associations Syntax Release Information Description Options show ntp associations Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Network Time Protocol (NTP) peers and their state. none—Display NTP peers and their state. no-resolve—(Optional) Suppress symbolic addressing. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ntp status on page 250 show ntp associations on page 249 Table 35 on page 248 describes the output fields for the show ntp associations command. Output fields are listed in the approximate order in which they appear. Table 35: show ntp associations Output Fields Field Name Field Description remote Address or name of the remote NTP peer. refid Reference identifier of the remote peer. If the reference identifier is not known, this field shows a value of 0.0.0.0. st Stratum of the remote peer. t Type of peer: b (broadcast), l (local), m (multicast), or u (unicast). when When the last packet from the peer was received. poll Polling interval, in seconds. reach Reachability register, in octal. delay Current estimated delay of the peer, in milliseconds. offset Current estimated offset of the peer, in milliseconds. disp Current estimated dispersion of the peer, in milliseconds. 248 Chapter 17: Operational Mode Commands for System Setup Table 35: show ntp associations Output Fields (continued) Field Name Field Description peer-name Peer name and status of the peer in the clock selection process: show ntp associations • space—Discarded because of a high stratum value or failed sanity checks. • x—Designated "falseticker", by the intersection algorithm. • .—Culled from the end of the candidate list. • – —Discarded by the clustering algorithm. • +—Included in the final selection set. • #—Selected for synchronization, but the distance exceeds the maximum. • *—Selected for synchronization. • o—Selected for synchronization, but the packets-per-second (pps) signal is in use. user@host> show ntp associations remote refid st t when poll reach delay offset disp ============================================================================== *wolfe-gw.junipe tick.ucla.edu 2 u 43 64 377 1.86 0.319 0.08 249 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ntp status Syntax Release Information Description Options show ntp status Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the values of internal variables returned by Network Time Protocol (NTP) peers. none—Display the values of internal variables returned by NTP peers. no-resolve—(Optional) Suppress symbolic addressing. Required Privilege Level Related Documentation List of Sample Output show ntp status 250 view • show ntp associations on page 248 show ntp status on page 250 user@host> show ntp status status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg, version="ntpd 4.1.0-a Fri Jun 24 06:40:56 GMT 2005 (1)", processor="i386", system="JUNOS7.4-20050624.0", leap=00, stratum=2, precision=-28, rootdelay=6.849, rootdispersion=10.615, peer=38788, refid=ntp-server.company-a.net, reftime=c66705d9.06ee0f3c Fri, Jun 24 2005 15:21:13.027, poll=6, clock=c6670602.cf6db940 Fri, Jun 24 2005 15:21:54.810, state=4, offset=0.205, frequency=75.911, jitter=0.396, stability=0.005 Chapter 17: Operational Mode Commands for System Setup show system firmware Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show system firmware Command introduced before Junos OS Release 10.2 for J-EX Series switches. (J-EX8200 switches only) Display firmware information. compatibility—(Optional) Display firmware compatibility information. view show system firmware on page 251 show system firmware compatibility on page 251 Table 36 on page 251 lists the output fields for the show system firmware command. Output fields are listed in the approximate order in which they appear. Table 36: show system firmware Output Fields show system firmware Field Name Field Description Part Physical part on the router or switch affected by the firmware. Type Type of firmware on the router or switch. Tag Location of the firmware on the interface. Current version Firmware version on the affected router or switch parts. Available version New versions of firmware for upgrading or downgrading. Status Firmware condition on the router or switch. Action Whether you can upgrade or downgrade, or if no action is available (none). user@host> show system firmware Part Type Tag Current version 0 6.4.10 0 0 Available Status version OK OK user@host> show system firmware compatibility Part Type Tag Current version FPC 0 ROM Monitor 0 0 6.4.10 Routing Engine 0 RE BIOS 0 0 Available Action version None None FPC 0 ROM Monitor 0 Routing Engine 0 RE BIOS show system firmware compatibility 251 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system reboot Syntax show system reboot Syntax (J-EX Series Switch) show system reboot Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display pending system reboots or halts. none—Display pending reboots or halts on the active Routing Engine. all-members—(J-EX4200 switches only) (Optional) Display halt or reboot request information for all members of the Virtual Chassis configuration. both-routing-engines—(Systems with multiple Routing Engines) (Optional) Display halt or reboot request information on both Routing Engines. local—(J-EX4200 switches only) (Optional) Display halt or reboot request information for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display halt or reboot request information for 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 show system reboot 252 maintenance show system reboot on page 252 user@host> show system reboot reboot requested by root at Wed Feb 10 17:40:46 1999 [process id 17885] Chapter 17: Operational Mode Commands for System Setup 253 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 show system snapshot media external 254 view • request system snapshot on page 106 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 80 • Verifying That a System Snapshot Was Created on a J-EX Series Switch on page 88 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: jbase : 10.0I20090726_0011_user jcrypto-ex: 10.0I20090726_0011_user Chapter 17: Operational Mode Commands for System Setup 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 255 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system software Syntax show system software Syntax (J-EX Series Switch) show system software Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the Junos OS extensions loaded on your router or switch. none—Display standard information about all loaded Junos OS extensions. all-members—(J-EX4200 switches only) (Optional) Display the system software running on all members of the Virtual Chassis configuration. detail—(Optional) Display detailed information about available Junos OS extensions. local—(J-EX4200 switches only) (Optional) Display the system software running on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display the system software running on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. scc—(Routing matrix only) (Optional) Display the system software running on a TX Matrix router (or switch-card chassis). Required Privilege Level maintenance List of Sample Output show system software on page 256 show system software 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: 256 Chapter 17: Operational Mode Commands for System Setup Comment: JUNOS Kernel Software Suite [7.2R1.7] Information for jpfe: Comment: JUNOS Packet Forwarding Engine Support (M20/M40) [7.2R1.7] Information for jroute: Comment: JUNOS Routing Software Suite [7.2R1.7] Information for junos: Comment: JUNOS Base OS boot [7.2R1.7] 257 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system storage Syntax Syntax (J-EX Series Switch) Release Information Description Options show system storage show system storage Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display statistics about the amount of free disk space in the router's or switch’s file systems. none—Display standard information about the amount of free disk space in the router's or switch’s file systems. detail—(Optional) Display detailed output. all-members—(J-EX4200 switches only) (Optional) Display system storage statistics for all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Display system storage statistics for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display system storage statistics for 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 Output Fields view show system storage on page 259 Table 37 on page 258 describes the output fields for the show system storage command. Output fields are listed in the approximate order in which they appear. Table 37: show system storage Output Fields 258 Field Name Field Description Filesystem Name of the file system. Size Size of the file system. Used Amount of space used in the file system. Avail Amount of space available in the file system. Capacity Percentage of the file system's space that is being used. Chapter 17: Operational Mode Commands for System Setup Table 37: show system storage Output Fields (continued) show system storage Field Name Field Description Mounted on Directory in which the file system is mounted. user@host> show system storage Filesystem Size /dev/ad0s1a 77M devfs 16K /dev/vn0 12M /dev/vn1 39M /packages/mnt/jkernel-7.2R1.7 /dev/vn2 12M /packages/mnt/jpfe-M40-7.2R1.7 /dev/vn3 2.3M /packages/mnt/jdocs-7.2R1.7 /dev/vn4 14M /packages/mnt/jroute-7.2R1.7 /dev/vn5 4.5M /packages/mnt/jcrypto-7.2R1.7 mfs:172 1.5G /dev/ad0s1e 12M procfs 4.0K /dev/ad1s1f 9.4G Used 37M 16K 12M 39M Avail 34M 0B 0B 0B Capacity Mounted on 52% / 100% /dev/ 100% /packages/mnt/jbase 100% 12M 0B 100% 2.3M 0B 100% 14M 0B 100% 4.5M 0B 100% 4.0K 20K 4.0K 4.9G 1.3G 11M 0B 3.7G 0% 0% 100% 57% /tmp /config /proc /var 259 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system switchover Syntax show system switchover Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display whether graceful Routing Engine switchover is configured, the state of the kernel replication (ready or synchronizing), any replication errors, and whether the primary and standby Routing Engines are using compatible versions of the kernel database. NOTE: Issue the show system switchover command only on the backup Routing Engine. This command is not supported on the master Routing Engine. because the kernel-replication process daemon does not run on the master Routing Engine. This process runs only on the backup Routing Engine. Options Required Privilege Level view List of Sample Output show system switchover (Backup Routing Engine) on page 261 Output Fields Table 38 on page 260 describes the output fields for the show system switchover command. Output fields are listed in the approximate order in which they appear. Table 38: show system switchover Output Fields Field Name Field Description Graceful switchover Display graceful Routing Engine switchover status: Configuration database • On—Indicates graceful-switchover is specified for the routing-options configuration command. • Off—Indicates graceful-switchover is not specified for the routing-options configuration command. State of the configuration database: • Ready—Configuration database has synchronized. • Synchronizing—Configuration database is synchronizing. Displayed when there are updates within the last 5 seconds. • Kernel database Synchronize failed—Configuration database synchronize process failed. State of the kernel database: • Ready—Kernel database has synchronized. • Synchronizing—Kernel database is synchronizing. Displayed when there are updates within the last 5 seconds. • Version incompatible—The primary and standby Routing Engines are running incompatible kernel database versions. • Replication error—An error occurred when the state was replicated from the primary Routing Engine. Inspect /var/log/ksyncd for possible causes, or notify Dell Support (see “Requesting Technical Support” on page lxxi). 260 Chapter 17: Operational Mode Commands for System Setup Table 38: show system switchover Output Fields (continued) Field Name Field Description Peer state Routing Engine peer state: show system switchover (Backup Routing Engine) • Steady State—Peer completed switchover transition. • Peer Connected—Peer in switchover transition. user@host> show system switchover Graceful switchover: On Configuration database: Ready Kernel database: Ready Peer state: Steady State 261 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system uptime Syntax Syntax (J-EX Series Switch) Release Information Description Options show system uptime show system uptime Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the current time and information about how long the router or switch, router or switch software, and routing protocols have been running. none—Show time since the system rebooted and processes started. all-members—(J-EX4200 switches only) (Optional) Show time since the system rebooted and processes started on all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Show time since the system rebooted and processes started on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Show time since the system rebooted and processes started 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 Output Fields view show system uptime on page 263 Table 39 on page 262 describes the output fields for the show system uptime command. Output fields are listed in the approximate order in which they appear. Table 39: show system uptime Output Fields Field Name Field Description Current time Current system time in UTC. System booted Date and time when the Routing Engine on the router or switch was last booted and how long it has been running. Protocols started Date and time when the routing protocols were last started and how long they have been running. Last configured Date and time when a configuration was last committed. Also shows name of user who issued the last commit command. time and up Current time, in the local time zone, and how long the router or switch has been operational. users Number of users logged in to the router or router. 262 Chapter 17: Operational Mode Commands for System Setup Table 39: show system uptime Output Fields (continued) Field Name Field Description load averages Load averages for the last 1 minute, 5 minutes, and 15 minutes. show system uptime user@host> show system uptime Current time: 1998-10-13 19:45:47 UTC System booted: 1998-10-12 20:51:41 UTC Protocols started: 1998-10-13 19:33:45 UTC Last configured: 1998-10-13 19:33:45 UTC 12:45PM up 22:54, 2 users, load averages: (22:54:06 ago) (00:12:02 ago) (00:12:02 ago) by abc 0.07, 0.02, 0.01 263 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system users Syntax Release Information Description show system users Command introduced before Junos OS Release 10.2 for J-EX Series switches. List information about the users who are currently logged in to the router or switch. NOTE: The show system users command does not list information about the automated users that are currently logged in to the router or switch from a remote client application using Junos XML APIs, such as NETCONF. It only shows details of administrative users that are logged in to a router or switch using the CLI, J-Web, or an SSH client. Options none—List information about the users who are currently logged in to the router or switch. no-resolve—(Optional) Do not attempt to resolve IP addresses to hostnames. Required Privilege Level List of Sample Output Output Fields view show system users on page 265 Table 40 on page 264 describes the output fields for the show system users command. Output fields are listed in the approximate order in which they appear. Table 40: show system users Output Fields Field Name Field Description time and up Current time, in the local time zone, and how long the router or switch has been operational. users Number of users logged in to the router or switch. load averages Load averages for the last 1 minute, 5 minutes, and 15 minutes. USER Username. TTY Terminal through which the user is logged in. FROM System from which the user has logged in. A hyphen indicates that the user is logged in through the console. LOGIN@ Time when the user logged in. IDLE How long the user has been idle. WHAT Processes that the user is running. 264 Chapter 17: Operational Mode Commands for System Setup show system users user@host> show system users 7:30PM up 4 days, 2:26, 2 users, load averages: 0.07, 0.02, 0.01 USER TTY FROM LOGIN@ IDLE WHAT root d0 Fri05PM 4days -csh (csh) blue p0 level5.company.net 7:30PM - cli 265 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system virtual-memory Syntax show system virtual-memory Syntax (J-EX Series Switch) show system virtual-memory Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the usage of Junos OS kernel memory listed first by size of allocation and then by type of usage. Use show system virtual-memory for troubleshooting with Dell Support (see “Requesting Technical Support” on page lxxi). none—Display kernel dynamic memory usage information. all-members—(J-EX4200 switches only) (Optional) Display kernel dynamic memory usage information for all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Display kernel dynamic memory usage information for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display kernel dynamic memory usage information for 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 266 NOTE: The show system virtual-memory command with the | display XML pipe option displays XML output for the command in the parent tags: , , , , and with each child element as a separate XML tag. view show system virtual-memory on page 268 show system virtual-memory | display xml on page 272 Table 41 on page 267 lists the output fields for the show system virtual-memory command. Output fields are listed in the approximate order in which they appear. Chapter 17: Operational Mode Commands for System Setup Table 41: show system virtual-memory Output Fields Field Name Field Description Memory statistics by bucket size Size Memory block size (bytes). The kernel memory allocator appropriates blocks of memory whose size is exactly a power of 2. In Use Number of memory blocks of this size that are in use (bytes). Free Number of memory blocks of this size that are free (bytes). Requests Number of memory allocation requests made. HighWater Maximum value the free list can have. Once the system starts reclaiming physical memory, it continues until the free list is increased to this value. Couldfree Total number of times that the free elements for a bucket size exceed the high-water mark for that bucket size. Memory usage type by bucket size Size Memory block size (bytes). Type(s) Kernel modules that are using these memory blocks. For a definition of each type, refer to a FreeBSD book. Memory statistics by type Type Kernel module that is using dynamic memory. InUse Number of memory blocks used by this type. The number is rounded up. MemUse Amount of memory in use, in kilobytes (KB). HighUse Maximum memory ever used by this type. Limit Maximum memory that can be allocated to this type. Requests Total number of dynamic memory allocation requests this type has made. Type Limit Number of times requests were blocked for reaching the maximum limit. Kern Limit Number of times requests were blocked for kernel map. Size(s) Memory block sizes this type is using. Memory Totals In Use Total kernel dynamic memory in use (bytes, rounded up). Free Total kernel dynamic memory free (bytes, rounded up). 267 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 41: show system virtual-memory Output Fields (continued) Field Name Field Description Requests Total number of memory allocation requests. ITEM Kernel module that is using memory. Size Memory block size (bytes). LImit Maximum memory that can be allocated to this type. Used Number of memory blocks used by this type. The number is rounded up. Free Number of memory blocks available to this type. Requests Total number of memory allocation requests this type has made. interrupt Timer events and scheduling interruptions. total Total number of interruptions for each type. rate Interruption rate. Total Total for all interruptions. show system virtual-memory user@host> show system virtual-memory Memory statistics by bucket size Size In Use Free Requests HighWater 16 906 118 154876 1280 32 455 313 209956 640 64 4412 260 75380 320 128 3200 32 19361 160 256 1510 10 8844 80 512 446 2 5085 40 1K 18 2 5901 20 2K 1128 2 4445 10 4K 185 1 456 5 8K 5 1 2653 5 16K 181 0 233 5 32K 2 0 1848 5 64K 20 0 22 5 128K 5 0 5 5 256K 2 0 2 5 512K 1 0 1 5 Couldfree 0 0 20 81 4 0 0 1368 0 0 0 0 0 0 0 0 Memory usage type by bucket size Size Type(s) 16 uc_devlist, nexusdev, iftable, temp, devbuf, atexit, COS, BPF, DEVFS mount, DEVFS node, vnodes, mount, pcb, soname, proc-args, kld, MD disk, rman, ATA generic, bus, sysctl, ippool, pfestat, ifstate, pfe_ipc, mkey, rtable, ifmaddr, ipfw, rnode 32 atkbddev, dirrem, mkdir, diradd, freefile, freefrag, indirdep, bmsafemap, newblk, temp, devbuf, COS, vnodes, cluster_save buffer, pcb, soname, proc-args, sigio, kld, Gzip trees, taskqueue, SWAP, 268 Chapter 17: Operational Mode Commands for System Setup 64 128 256 512 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K eventhandler, bus, sysctl, uidinfo, subproc, pgrp, pfestat, itable32, ifstate, pfe_ipc, mkey, rtable, ifmaddr, ipfw, rnode, rtnexthop isadev, iftable, MFS node, allocindir, allocdirect, pagedep, temp, devbuf, lockf, COS, NULLFS hash, DEVFS name, vnodes, cluster_save buffer, vfscache, pcb, soname, proc-args, file, AR driver, AD driver, Gzip trees, rman, eventhandler, bus, sysctl, subproc, pfestat, pic, ifstate, pfe_ipc, mkey, ifaddr, rtable, ipfw ZONE, freeblks, inodedep, temp, devbuf, zombie, COS, DEVFS node, vnodes, mount, vfscache, pcb, soname, proc-args, ttys, dev_t, timecounter, kld, Gzip trees, ISOFS node, bus, uidinfo, cred, session, pic, itable16, ifstate, pfe_ipc, rtable, ifstat, metrics, rtnexthop, iffamily iflogical, iftable, MFS node, FFS node, newblk, temp, devbuf, NFS daemon, vnodes, proc-args, kqueue, file desc, Gzip trees, bus, subproc, itable16, ifstate, pfe_ipc, sysctl, rtnexthop UFS mount, temp, devbuf, mount, BIO buffer, ptys, ttys, AR driver, Gzip trees, ISOFS mount, msg, ioctlops, ATA generic, bus, proc, pfestat, lr, ifstate, pfe_ipc, rtable, ipfw, ifstat, rtnexthop iftable, temp, devbuf, NQNFS Lease, kqueue, kld, AD driver, Gzip trees, sem, MD disk, bus, ifstate, pfe_ipc, ipfw uc_devlist, UFS mount, temp, devbuf, BIO buffer, pcb, AR driver, Gzip trees, ioctlops, bus, ipfw, ifstat, rcache memdesc, iftable, UFS mount, temp, devbuf, kld, Gzip trees, sem, msg temp, devbuf, syncache, Gzip trees indirdep, temp, devbuf, shm, msg pagedep, kld, Gzip trees VM pgdata, devbuf, MSDOSFS mount UFS ihash, inodedep, NFS hash, kld, ISOFS mount mbuf, vfscache SWAP Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit isadev 13 1K 1K127753K 13 0 0 atkbddev 2 1K 1K127753K 2 0 0 uc_devlist 24 3K 3K127753K 24 0 0 nexusdev 3 1K 1K127753K 3 0 0 memdesc 1 4K 4K127753K 1 0 0 mbuf 1 152K 152K127753K 1 0 0 iflogical 6 2K 2K127753K 6 0 0 iftable 17 9K 9K127753K 18 0 0 ZONE 15 2K 2K127753K 15 0 0 VM pgdata 1 64K 64K127753K 1 0 0 UFS mount 12 26K 26K127753K 12 0 0 UFS ihash 1 128K 128K127753K 1 0 0 MFS node 6 2K 3K127753K 35 0 0 FFS node 906 227K 227K127753K 1352 0 0 dirrem 0 0K 4K127753K 500 0 0 mkdir 0 0K 1K127753K 38 0 0 diradd 0 0K 6K127753K 521 0 0 freefile 0 0K 4K127753K 374 0 0 freeblks 0 0K 8K127753K 219 0 0 freefrag 0 0K 1K127753K 193 0 0 allocindir 0 0K 25K127753K 1518 0 0 indirdep 0 0K 17K127753K 76 0 0 allocdirect 0 0K 10K127753K 760 0 0 bmsafemap 0 0K 1K127753K 72 0 0 newblk 1 1K 1K127753K 2279 0 0 inodedep 1 128K 175K127753K 2367 0 0 pagedep 1 32K 33K127753K 47 0 0 temp 1239 92K 96K127753K 8364 0 0 Size(s) 64 32 16,2K 16 4K 256K 256 16,64,256,1K,4K 128 64K 512,2K,4K 128K 64,256 256 32 32 32 32 128 32 64 32,16K 64 32 32,256 128,128K 64,32K 16,32,64K 269 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS devbuf 1413 lockf 38 atexit 1 zombie 0 NFS hash 1 NQNFS Lease 1 NFS daemon 1 syncache 1 COS 353 BPF 189 MSDOSFS mount 1 NULLFS hash 1 DEVFS mount 2 DEVFS name 487 DEVFS node 471 vnodes 28 mount 15 cluster_save buffer vfscache 1898 BIO buffer 49 pcb 159 soname 82 proc-args 57 ptys 32 ttys 254 kqueue 5 sigio 1 file 383 file desc 76 shm 1 dev_t 286 timecounter 10 kld 11 AR driver 1 AD driver 2 Gzip trees 0 ISOFS node 1136 ISOFS mount 9 sem 3 MD disk 2 msg 4 rman 59 ioctlops 0 taskqueue 2 SWAP 2 ATA generic 6 eventhandler 17 bus 340 sysctl 0 uidinfo 4 cred 22 subproc 156 proc 2 session 12 pgrp 16 ippool 1 pfestat 0 pic 5 lr 1 itable32 110 itable16 161 270 5527K 3K 1K 0K 128K 1K 1K 8K 44K 3K 64K 1K 1K 31K 58K 7K 8K 0 376K 98K 16K 10K 2K 16K 33K 3K 1K 24K 19K 12K 36K 2K 117K 1K 2K 0K 142K 132K 6K 2K 25K 4K 0K 1K 413K 3K 1K 30K 0K 1K 3K 10K 1K 2K 1K 1K 0K 1K 1K 4K 26K 5527K127753K 1535 3K127753K 2906 1K127753K 1 2K127753K 3850 128K127753K 1 1K127753K 1 1K127753K 1 8K127753K 1 44K127753K 353 3K127753K 189 64K127753K 1 1K127753K 1 1K127753K 2 31K127753K 487 58K127753K 479 7K127753K 429 8K127753K 18 0K 1K127753K 376K127753K 3228 398K127753K 495 17K127753K 399 10K127753K 42847 3K127753K 2105 16K127753K 32 33K127753K 522 4K127753K 23 1K127753K 27 24K127753K 16060 20K127753K 3968 12K127753K 1 36K127753K 286 2K127753K 10 122K127753K 34 3K127753K 5 3K127753K 2755 46K127753K 133848 142K127753K 1189 132K127753K 10 6K127753K 3 2K127753K 2 25K127753K 4 4K127753K 461 2K127753K 992 1K127753K 2 413K127753K 2 3K127753K 6 1K127753K 17 31K127753K 794 1K127753K 130262 1K127753K 10 3K127753K 3450 10K127753K 7882 1K127753K 2 2K127753K 34 1K127753K 45 1K127753K 1 1K127753K 47349 1K127753K 5 1K127753K 1 4K127753K 110 26K127753K 161 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 55 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16,32,64,128,256 64 16 128 128K 1K 256 8K 16,32,64,128 16 64K 64 16 64 16,128 16,32,64,128,256 16,128,512 0 32,64 64,128,256K 512,2K 16,32,64,128,2K 16,32,64,128 16,32,64,128,256 512 128,512 256,1K 32 64 256 16K 128 128 16,32,128,1K,4K 64,512,2K 64,1K 32,64,128,256 128 512,128K 1K,4K 16,1K 512,4K,16K 16,64 512,2K 32 32,512K 16,512 32,64 16,32,64,128,256 16,32,64 32,128 128 32,64,256 512 128 32 16 16,32,64,512 64,128 512 32 128,256 Chapter 17: Operational Mode Commands for System Setup ifstate pfe_ipc mkey ifaddr sysctl rtable ifmaddr ipfw ifstat rcache rnode metrics rtnexthop iffamily 694 0 250 9 0 49 22 23 698 4 27 1 57 12 Memory Totals: In Use 9311K ITEM PIPE: SWAPMETA: unpcb: ripcb: syncache: tcpcb: udpcb: socket: KNOTE: NFSNODE: NFSMOUNT: VNODE: NAMEI: VMSPACE: PROC: DP fakepg: PV ENTRY: MAP ENTRY: KMAP ENTRY: MAP: VM OBJECT: SIZE 192, 160, 160, 192, 128, 576, 192, 256, 96, 352, 544, 224, 1024, 192, 448, 64, 28, 48, 48, 108, 92, 159K 0K 4K 1K 0K 6K 1K 10K 805K 8K 1K 1K 9K 2K 792644 9863474 286510 390851 3596829 16 3880 27 0 0 0 0 0 380 395 122 1476 0 0 101 160K127753K 1K127753K 4K127753K 1K127753K 1K127753K 6K127753K 1K127753K 10K127753K 805K127753K 8K127753K 1K127753K 1K127753K 9K127753K 2K127753K Free 54K LIMIT 0, 95814, 0, 25330, 15359, 25330, 25330, 25330, 0, 0, 0, 0, 0, 0, 0, 0, 499566, 0, 35645, 0, 0, 1735 56218 824 9 30 307 22 48 698 4 285 3 312 12 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16,32,64,128,1K 16,32,64,128,1K 16,32,64 64 256 16,32,64,128,512 16,32 16,32,64,512,2K 128,512,2K 2K 16,32 128 32,128,256,512 128 Requests 489068 USED FREE REQUESTS 4, 81, 4422 0, 0, 0 114, 36, 279 5, 37, 5 0, 64, 5 23, 12, 32 14, 28, 255 246, 26, 819 27, 57, 71 0, 0, 0 0, 0, 0 2778, 43, 2778 0, 8, 40725 57, 71, 3906 73, 17, 3923 0, 0, 0 44530, 152053, 1525141 1439, 134, 351075 179, 119, 10904 7, 3, 7 2575, 109, 66912 cpu context switches device interrupts software interrupts traps system calls kernel threads created fork() calls vfork() calls rfork() calls swap pager pageins swap pager pages paged in swap pager pageouts swap pager pages paged out vnode pager pageins vnode pager pages paged in vnode pager pageouts vnode pager pages paged out page daemon wakeups pages examined by the page daemon pages reactivated 271 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 161722 0 84623 83063 7 535606 0 238254 2535 0 283379 0 190091 17458 29166 0 10395 134610 4096 183419 interrupt ata0 irq14 mux irq7 fxp1 irq10 sio0 irq4 clk irq0 rtc irq8 Total copy-on-write faults copy-on-write optimized faults zero fill pages zeroed zero fill pages prezeroed intransit blocking page faults total VM faults taken pages affected by kernel thread creation pages affected by fork() pages affected by vfork() pages affected by rfork() pages freed pages freed by daemon pages freed by exiting processes pages active pages inactive pages in VM cache pages wired down pages free bytes per page total name lookups cache hits (90% pos + 7% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% show system virtual-memory | display xml 272 total 113338 727643 1178671 833 3439769 4403221 9863475 rate 3 21 34 0 99 127 286 user@host> show system virtual-memory | display xml CAM dev queue 1 1 - 1 64 entropy 1024 64 - 1024 64 linker 481 1871 - 1145 16,32,64,4096,32768,131072 lockf 56 4 - 5998 64 devbuf Chapter 17: Operational Mode Commands for System Setup 2094 3877 - 2099 16,32,64,128,512,1024,4096,8192,16384,32768,65536,131072 temp 21 66 - 3127 16,32,64,128,256,512,2048,4096,8192,16384,32768,65536,131072 ip6ndp 0 0 - 4 64 in6ifmulti 1 1 - 1 64 in6grentry 1 1 - 1 64 iflogical 13 3 - 13 64,2048 iffamily 28 4 - 28 32,1024,2048 rtnexthop 127 18 - 129 32,256,512,1024,2048,4096 metrics 3 1 - 5 256 inifmulti 3 1 - 273 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3 64 ingrentry 6 1 - 6 64 rnode 68 2 - 76 16,32 rcache 4 8 - 4 65536 ifdevice 4 1 - 4 16 ifstat 40 22 - 40 512,16384,32768 ipfw 42 23 - 91 16,32,64,128,256,512,1024,16384,32768,65536,131072 ifmaddr 103 3 - 103 16,32 rtable 129 14 - 139 16,32,64,128,1024,16384 sysctl 0 0 - 14847 16,32,64,4096,16384,32768 ifaddr 29 3 - 274 Chapter 17: Operational Mode Commands for System Setup 29 64,128 mkey 345 6 - 2527 16,128 pfe_ipc 0 0 - 1422 16,32,64,128,512,1024,2048,8192,16384,32768,65536,131072 ifstate 594 51 - 655 16,32,64,128,256,1024,2048,4096,16384,32768 itable16 276 52 - 294 1024,4096 itable32 160 10 - 160 64 itable64 2 1 - 2 128 lr 1 1 - 1 16384 pic 5 1 - 5 64,512 pfestat 0 0 - 162 16,32,128,256,16384 gencfg 224 275 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 56 - 540 16,32,64,256,512,32768,65536 jsr 2 1 - 4 16 idl 0 0 - 13 16,32,64,128,256,4096,16384,32768,131072 rtsmsg 0 0 - 2 131072 module 249 16 - 249 64,128 mtx_pool 1 8 - 1 64,128 DEVFS3 109 12 - 117 256 DEVFS1 102 23 - 109 2048 pgrp 12 1 - 21 64 session 8 1 - 15 512 proc 2 276 Chapter 17: Operational Mode Commands for System Setup 1 - 2 16384 subproc 244 496 - 1522 2048,131072 cred 30 4 - 11409 256 plimit 17 4 - 133 2048 uidinfo 3 1 - 6 32,512 sysctloid 1117 34 - 1117 16,32,64 sysctltmp 0 0 - 743 16,32,64,1024 umtx 144 9 - 144 64 SWAP 2 209 - 2 64 bus 496 55 - 1196 16,32,64,128,32768 bus-sc 23 33 277 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS - 335 16,32,64,512,1024,2048,8192,16384,65536,131072 devstat 10 21 - 10 16,131072 eventhandler 35 2 - 36 32,128 kobj 93 186 - 111 65536 DEVFS 8 1 - 9 16,64 rman 71 5 - 433 16,32,64 sbuf 0 0 - 522 16,32,32768,131072 NULLFS hash 1 1 - 1 64 taskqueue 5 1 - 5 64 turnstiles 145 10 - 145 64 Unitno 8 1 278 Chapter 17: Operational Mode Commands for System Setup - 44 16,64 ioctlops 0 0 - 27622 16,64,8192,16384,131072 iov 0 0 - 18578 16,64,128,256,512,1024,2048,131072 msg 4 25 - 4 32768,131072 sem 4 7 - 4 16384,32768,131072 shm 9 20 - 14 32768 ttys 321 61 - 528 512,32768 ptys 1 1 - 1 128 mbuf_tag 0 0 - 23383 16 soname 115 12 - 24712 16,32,64,256 pcb 216 33 - 279 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 484 16,32,64,128,1024,2048,4096,16384,32768,65536 BIO buffer 43 86 - 405 65536 vfscache 1 256 - 1 65536 cluster_save buffer 0 0 - 2 32,64 VFS hash 1 128 - 1 32,64 vnodes 1 1 - 1 512 mount 290 23 - 535 16,32,64,128,256,4096,32768 vnodemarker 0 0 - 498 16384 pfs_nodes 25 3 - 25 128 pfs_vncache 27 1 - 53 32 STP 1 1 - 280 Chapter 17: Operational Mode Commands for System Setup 1 64 GEOM 146 11 - 1042 16,32,64,128,256,512,2048,16384,32768,131072 syncache 1 8 - 1 16,32,64,128,256,512,2048,16384,32768,131072 tlv_stat 0 0 - 8 16,32,64,128,256,512,2048,16384,32768,131072 NFS daemon 1 8 - 1 16,32,64,128,256,512,2048,16384,32768,131072 p1003.1b 1 1 - 1 16 MD disk 10 20 - 10 65536 ata_generic 1 1 - 6 16,16384,32768 ISOFS mount 8 1 - 15 512 ISOFS node 1440 135 - 1457 128 CAM SIM 281 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1 1 - 1 64 CAM XPT 6 1 - 9 16,64,16384 CAM periph 1 1 - 1 128 ad_driver 1 1 - 1 256 pagedep 1 32 - 106 64 inodedep 1 128 - 464 256 newblk 1 1 - 336 64,4096 bmsafemap 0 0 - 63 64 allocdirect 0 0 - 320 128 indirdep 0 0 - 17 32 allocindir 0 282 Chapter 17: Operational Mode Commands for System Setup 0 - 15 64 freefrag 0 0 - 12 32 freeblks 0 0 - 40 2048 freefile 0 0 - 101 32 diradd 0 0 - 465 64 mkdir 0 0 - 136 32 dirrem 0 0 - 168 32 newdirblk 0 0 - 1 32 savedino 0 0 - 157 512 UFS mount 15 36 - 15 2048,65536,131072 ata_dma 2 1 283 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS - 2 256 UMAHash 1 2 - 4 4096,16384,32768,65536 cdev 22 3 - 22 256 file desc 141 32 - 1583 16,1024,2048,16384 VM pgdata 2 65 - 2 64 sigio 1 1 - 20 32 kenv 24 5 - 27 16,32,64,131072 atkbddev 2 1 - 2 32 kqueue 15 9 - 19 1024,4096,32768 proc-args 57 3 - 1001 16,32,64,128,256,512,1024 isadev 21 2 - 284 Chapter 17: Operational Mode Commands for System Setup 21 64 zombie 0 0 - 1278 128 ithread 69 5 - 69 16,64,256 legacydrv 4 1 - 4 16 memdesc 1 4 - 1 131072 nexusdev 2 1 - 2 16 CAM queue 3 1 - 3 16 $PIR 4 1 - 4 32 KTRACE 100 10 - 100 128 kbdmux 5 9 - 5 128,2048,65536,131072 UMA Kegs: 136 0 285 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 71 1 71 UMA Zones: 120 0 71 19 71 UMA Slabs: 64 0 490 41 579 UMA RCntSlabs: 104 0 276 20 276 UMA Hash: 128 0 4 26 5 16 Bucket: 76 0 30 20 30 32 Bucket: 140 0 33 23 33 64 Bucket: 268 0 33 9 33 128 Bucket: 524 0 49 0 49 VM OBJECT: 128 0 2111 79 25214 MAP: 160 0 7 286 Chapter 17: Operational Mode Commands for System Setup 41 7 KMAP ENTRY: 68 35336 19 149 2397 MAP ENTRY: 68 0 2031 153 62417 PV ENTRY: 24 509095 57177 6333 1033683 DP fakepg: 72 0 0 0 0 mt_zone: 64 0 238 57 238 16: 16 0 2114 119 80515 32: 32 0 1335 134 10259 64: 64 0 3529 129 29110 96: 96 0 2062 58 4365 112: 112 0 361 164 287 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 24613 128: 128 0 359 61 942 160: 160 0 364 44 577 224: 224 0 422 20 1950 256: 256 0 204 36 1225 288: 288 0 2 24 10 512: 512 0 49 7 911 1024: 1024 0 213 11 1076 2048: 2048 0 199 113 640 4096: 4096 0 144 7 2249 Files: 72 0 665 77 16457 288 Chapter 17: Operational Mode Commands for System Setup MAC labels: 20 0 3998 227 21947 PROC: 544 0 116 10 1394 THREAD: 416 0 127 17 131 KSEGRP: 88 0 127 73 131 UPCALL: 44 0 0 0 0 SLEEPQUEUE: 32 0 145 194 145 VMSPACE: 268 0 57 13 1335 mbuf_packet: 256 180000 256 128 49791 mbuf: 256 180000 50 466 105183 mbuf_cluster: 2048 25190 387 165 5976 mbuf_jumbo_pagesize: 289 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 4096 0 0 0 0 mbuf_jumbo_9k: 9216 0 0 0 0 mbuf_jumbo_16k: 16384 0 0 0 0 ACL UMA zone: 388 0 0 0 0 g_bio: 132 0 0 174 69750 ata_request: 200 0 0 57 5030 ata_composite: 192 0 0 0 0 GENCFG: 72 1000004 57 102 57 VNODE: 292 0 2718 25 2922 VNODEPOLL: 72 0 0 0 0 S VFS Cache: 68 290 Chapter 17: Operational Mode Commands for System Setup 0 2500 76 3824 L VFS Cache: 291 0 51 14 63 NAMEI: 1024 0 0 8 53330 NFSMOUNT: 480 0 0 0 0 NFSNODE: 460 0 0 0 0 PIPE: 404 0 27 9 717 KNOTE: 72 0 42 64 3311 socket: 412 25191 343 8 2524 unpcb: 140 25200 170 26 2157 ipq: 52 216 0 0 0 udpcb: 232 25194 291 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 19 32 31 inpcb: 232 25194 40 28 105 tcpcb: 520 25193 40 16 105 tcptw: 56 5092 0 0 0 syncache: 128 15360 0 60 55 tcpreass: 20 1690 0 0 0 sackhole: 20 0 0 0 0 ripcb: 232 25194 5 29 5 SWAPMETA: 276 94948 0 0 0 FFS inode: 132 0 1146 72 1306 FFS1 dinode: 128 0 1146 292 Chapter 17: Operational Mode Commands for System Setup 24 1306 FFS2 dinode: 256 0 0 0 0 934906 1707986 33819 203604 1200636 60 1313 21 0 0 0 0 0 23094 23119 226 3143 0 0 8821 48364 31 74665 70061 85 191824 0 95343 3526 0 221502 0 75630 45826 13227 49278 10640 70706 4096 0 0 214496 92 5 0 0 0 0 293 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS irq0: clk 1243455 999 irq4: sio0 1140 0 irq8: rtc 159164 127 irq9: cbb1 fxp0 28490 22 irq10: fxp1 20593 16 irq14: ata0 5031 4 Total 1457873 1171 248524800 294 Chapter 17: Operational Mode Commands for System Setup show task replication Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show task replication Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) status. When you issue this command on the master Routing Engine, the status of nonstop active routing synchronization is also displayed. This command has no options. view show task replication (Issued on the Master Routing Engine) on page 295 show task replication (Issued on the Backup Routing Engine) on page 295 Table 42 on page 295 lists the output fields for the show task replication command. Output fields are listed in the approximate order in which they appear. Table 42: show task replication Output Fields show task replication (Issued on the Master Routing Engine) Field Name Field Description Stateful replication Displays whether or not graceful Routing Engine switchover is configured. The status can be Enabled or Disabled. RE mode Displays the Routing Engine on which the command is issued: Master, Backup, or Not applicable (when the router has only one Routing Engine). Protocol Protocol that are supported by nonstop active routing. Synchronization Status Nonstop active routing synchronization status for the supported protocols. States are NotStarted, InProgress, and Complete. user@host> show task replication Stateful Replication: Enabled RE mode: Master Protocol OSPF BGP IS-IS LDP show task replication (Issued on the Backup Routing Engine) Synchronization Status NotStarted Complete NotStarted Complete user@host> show task replication Stateful Replication: Enabled RE mode: Master 295 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show version Syntax Syntax (J-EX Series Switch) Release Information Description Options show version show version Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the hostname and version information about the software running on the router or switch. none—Display standard information about the hostname and version of the software running on the router or switch. brief | detail—(Optional) Display the specified level of output. all-members—(J-EX4200 switches only) (Optional) Display standard information about the hostname and version of the software running on all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Display standard information about the hostname and version of the software running on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display standard information about the hostname and version of the software running 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 296 view show version (J-EX8208) on page 297 show version (J-EX4200-24F) on page 297 Chapter 17: Operational Mode Commands for System Setup show version (J-EX8208) show version (J-EX4200-24F) user@switch> show version Model: DELL J-EX8208 JUNOS Base OS boot [10.2I20100329_2206_pappavu] JUNOS Base OS Software Suite [10.2I20100329_2206_pappavu] JUNOS Kernel Software Suite [10.2I20100329_2206_pappavu] JUNOS Crypto Software Suite [10.2I20100329_2206_pappavu] JUNOS Online Documentation [10.2I20100329_2206_pappavu] JUNOS Enterprise Software Suite [10.2I20100329_2206_pappavu] LC JUNOS Installation Software [10.2I20100329_2206_pappavu] JUNOS Routing Software Suite [10.2I20100329_2206_pappavu] JUNOS Web Management [10.2I20100329_2206_pappavu] {master:0} user@switch> show version fpc0: -------------------------------------------------------------------------Model: DELL J-EX4200-24F JUNOS Base OS boot [10.2I20100331_2208_pappavu] JUNOS Base OS Software Suite [10.2I20100331_2208_pappavu] JUNOS Kernel Software Suite [10.2I20100331_2208_pappavu] JUNOS Crypto Software Suite [10.2I20100331_2208_pappavu] JUNOS Online Documentation [10.2I20100331_2208_pappavu] JUNOS Enterprise Software Suite [10.2I20100331_2208_pappavu] JUNOS Packet Forwarding Engine Enterprise Software Suite [10.2I20100331_2208_pappavu] JUNOS Routing Software Suite [10.2I20100331_2208_pappavu] JUNOS Web Management [10.2I20100331_2208_pappavu] 297 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 298 PART 6 Junos OS for J-EX Series Switches Power Management • Power Management Overview on page 301 • Initial Configuration on page 307 • Verifying Power Management on page 309 • Configuration Statements for Power Management on page 311 • Operational Mode Commands for Power Management on page 315 299 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 300 CHAPTER 18 Power Management Overview • Junos OS—Overview on page 301 • Power Management on page 302 Junos OS—Overview • J-EX Series Switch Software Features Overview on page 301 J-EX Series Switch Software Features Overview The following tables list the J-EX Series Switches software features and the Junos OS Release in which they were introduced: Related Documentation • Table 4 on page 4—Access Control Features • Table 5 on page 4—Administration Features • Table 6 on page 4—Class-of-Service (CoS) Features • Table 7 on page 5—High Availability and Resiliency Features • Table 8 on page 6—Interfaces Features • Table 9 on page 7—IP Address Management Features • Table 10 on page 7—IPv6 Features • Table 11 on page 7—Layer 2 Network Protocols Features • Table 12 on page 8—Layer 3 Protocols Features • Table 13 on page 9—MPLS Features • Table 14 on page 10—Multicast Features • Table 15 on page 10—Network Management and Monitoring Features • Table 16 on page 11—Port Security Features • Table 17 on page 12—System Management Features • High Availability Features for J-EX Series Switches Overview on page 18 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 14 301 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • J-EX4200 Switches Hardware Overview on page 25 • J-EX8208 Switch Hardware Overview on page 27 • J-EX8216 Switch Hardware Overview on page 30 Power Management • Understanding Power Management on J-EX Series Switches on page 302 Understanding Power Management on J-EX Series Switches The power management feature for Dell PowerConnect J-Series J-EX8200 Ethernet Switches helps ensure that normal operation of the system is not disrupted because of insufficient power to the switch. It does so by employing a power budget policy. Power management does the following in its power budget policy: • Budgets power for each switch component that requires power. The amount that power management budgets for each component is the maximum power that component might consume. For example, for the fan tray, power management budgets the amount of power required to run the fans at their maximum speed setting. • Reserves a set amount of power for power supply redundancy. In its default configuration, power management manages the switch for N+1 power redundancy, which ensures uninterrupted system operation if one power supply fails. For example, if a switch has four online 3000 W power supplies, power management reserves 3000 W in its power budget policy for redundancy. It allocates the remaining 9000 W to normal operating power. • Specifies the rules under which components receive power. These rules are designed to ensure the least disruption to switch operation under conditions of insufficient power. For example, power management provides power to core system components, such as the Routing Engine, before it provides power to line cards. You can configure certain aspects of power management’s budget policy, specifically: • The power priority of individual line cards. By assigning different power priorities to the line cards, you can determine which line cards are more likely to receive power in the event of insufficient power. • The power redundancy configuration. The default power redundancy configuration is N+1; you can optionally configure N+N. For example, if you have deployed two independent AC power feeds to the switch, configure N+N redundancy. When you configure power management for N+N redundancy, it reserves the appropriate amount of power in its power budget and reports insufficient power conditions accordingly. These configurable items are discussed further in: 302 • Power Priority of Line Cards on page 303 • Power Supply Redundancy on page 304 Chapter 18: Power Management Overview Power Priority of Line Cards Power management powers line cards on or off based on the power priority of the slots they occupy: • When a switch powers on, power management provides power to the line cards in the order of their slot priority, with line cards in high priority slots receiving power first. Thus if available power (including redundant power) is exhausted before all line cards receive power, higher priority cards are powered on while lower priority cards remain powered off. • If the switch starts receiving insufficient power because of power supply failure or some other problem, power management powers off the line cards in reverse-priority order until power (including redundant power) is sufficient for the remaining cards. Thus higher priority line cards are more likely to retain power in power shortage conditions than are lower priority line cards. • Power management responds to changes in power availability and line card operating status by powering line cards on or off as appropriate. For example, if you add a power supply, lower priority cards that were powered off due to insufficient power are powered on in priority order. If you take a line card offline, power management no longer allocates power to it. If power to the switch is insufficient when you take a line card offline, power management allocates the freed power to a lower priority card that was offline due to lack of power and brings it online. Restarting a line card, however, does not affect the power allocated to it. Thus when power is insufficient, restarting a line card does not change its operating status or the operating status of other line cards. NOTE: Because power management does not allocate power to an offline line card, a line card that has been taken offline in a J-EX8200 switch is not automatically brought online when you commit a configuration. You must explicitly bring the line card online with the request chassis fpc slot slot-number online command. This behavior differs from other platforms running the Junos OS, which automatically bring an offline FPC online when you commit a configuration. The actual power priority of a slot is determined first by the slot’s assigned priority and second by the slot’s number. If more than one slot has the same assigned priority, power priority is determined by slot number, with the lowest-numbered slots receiving power first. By default, all slots are assigned the lowest priority. You can assign a priority to a slot using the CLI. If you do not explicitly assign priorities to slots, the slots receive power in ascending order of slot numbers. 303 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Because the purpose of power management is to ensure minimal system disruption when power is insufficient, slot power priority does not always determine which line cards receive power. In some cases, power management might provide power to a lower priority line card rather than a higher priority line card. For example: • If power is insufficient for a line card in a higher priority slot but is sufficient for a line card in a lower priority slot, the lower priority slot receives the power. For example, if an 8-port SFP+ line card requiring 450 W is in a higher priority slot than a 48-port SFP line card requiring 330 W, the 48-port SFP line card receives the power if there is more than 330 W but less than 450 W available. • In an operating switch that has insufficient power, power management does not power off operating line cards to provide power to a newly inserted line card or a line card that is brought online after being offline, even if the line card has a higher priority than the currently operating line cards. However, if you restart the switch, power management reruns the current power budget policy and powers line cards on or off based on their priority. As a result, line cards receive power strictly by priority order and previously operating line cards might no longer receive power. • If you change the assigned power priority of line cards when there is insufficient power for all the line cards, power management does not power down line cards that had been receiving power because they are now a lower priority. Power Supply Redundancy By default, power management in J-EX8200 switches is configured to manage the power supplies for N+1 redundancy, in which one power supply is held in reserve for backup if one of the other power supplies is removed or fails. You can configure power management to manage the power supplies for N+N redundancy. In N+N redundancy, power management holds N power supplies in reserve for backup. For example, if your switch has six power supplies and you configure N+N redundancy, power management makes three power supplies available for normal operating power and reserves three power supplies for redundancy (3+3). If you have an odd number of power supplies, power management allocates one more power supply to normal operating power than to redundant power. For example, if you have five power supplies, the N+N configuration is 3+2. Given the same number of power supplies, an N+N configuration usually provides less normal operating power than an N+1 configuration because the N+N configuration holds more power in reserve for backup. Table 43 on page 304 shows the effect on normal operating power in N+1 and N+N configurations. Table 43: Available Operating Power in N+1 and N+N Redundancy Configurations 304 Number of Power Supplies at n W Each Normal Operating Power in N+1 Configuration Normal Operating Power in N+N Configuration 2 1 x (n W) 1 x (n W) Chapter 18: Power Management Overview Table 43: Available Operating Power in N+1 and N+N Redundancy Configurations (continued) Number of Power Supplies at n W Each Normal Operating Power in N+1 Configuration Normal Operating Power in N+N Configuration 3 2 x (n W) 2 x (n W) 4 3 x (n W) 2 x (n W) 5 4 x (n W) 3 x (n W) 6 5 x (n W) 3 x (n W) To compensate for the reduced normal operating power, power management reserves less power to the chassis in an N+N configuration than in an N+1 configuration. This reduction in reserved chassis power allows a switch in an N+N configuration to power more line cards than it could without the reduction. For the J-EX8208 switch, the power reserved for the chassis is reduced to 1200 W from 1600 W; for the J-EX8216 switch, it is reduced to 1800 W from 2400 W. NOTE: To achieve the reduction in reserved chassis power, power management reduces the maximum fan speed to 60 percent in an N+N configuration from 80 percent in an N+1 configuration. Because the maximum fan speed is reduced, it is possible that a line card that overheats would be shut down sooner in an N+N configuration than in an N+1 configuration. Power management automatically recalculates the redundant power and normal operating power as power supplies go online or offline. For example, if you have an N+N configuration with three online 2000 W power supplies, power management allocates 2000 W to redundant power. If you bring a fourth 2000 W power supply online, power management then allocates 4000 W to redundant power. If a power supply goes offline again, power management once again allocates 2000 W to redundant power. When power is insufficient to meet the budgeted power requirements, power management raises alarms as follows: • If all the line cards are receiving power but insufficient redundant power exists to maintain the configured N+1 or N+N power configuration, power management raises a minor (yellow) alarm. If this condition persists for 5 minutes, the alarm becomes a major (red) alarm. • If one or more line cards are down because of insufficient power (including redundant power), power management raises a major (red) alarm. Power management clears all alarms when sufficient power is available to meet normal operating and redundant power requirements. Related Documentation • Understanding Alarm Types and Severity Levels on J-EX Series Switches on page 533 305 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 306 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 • Configuring Power Supply Redundancy (CLI Procedure) on page 307 • Verifying Power Configuration and Use on page 309 CHAPTER 19 Initial Configuration • Configuring Power Supply Redundancy (CLI Procedure) on page 307 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 Configuring Power Supply Redundancy (CLI Procedure) By default, the power management feature in J-EX8200 switches is configured to manage the power supplies for N+1 redundancy, in which one power supply is held in reserve for backup if any one of the other power supplies is removed or fails. You can configure power management to manage the power supplies for N+N redundancy. For example, to set up your AC power supplies for dual power feed, N+N redundancy is required. In N+N redundancy, power management allocates half of the online power supplies to normal operating power and half to redundant power. If you have an odd number of online power supplies, power management allocates one more power supply to normal operating power than to redundant power. This topic describes how to configure power management for N+N redundancy and how to revert back to N+1 redundancy if your deployment needs change. Before you configure power management for N+N redundancy, ensure that you have sufficient power supplies to meet the power requirements of this configuration. Use the show chassis power-budget-statistics command to display your current power budget. NOTE: To allow more power to be available to line cards, power management compensates for the reduced normal operating power in an N+N configuration by reserving less power to the chassis than it does in an N+1 configuration. For the J-EX8208 switch, the power reserved for the chassis is reduced to 1200 W from 1600 W. For the J-EX8216 switch, it is reduced to 1800 W from 2400 W. In determining whether you have enough power for an N+N configuration, take this reduction of reserved chassis power into account. The reduction in reserved chassis power is achieved by reducing the maximum fan speed to 60 percent in an N+N configuration from 80 percent in an N+1 configuration. Because the maximum fan speed is reduced, it is possible that a line card that overheats would be shut down sooner in an N+N configuration than in an N+1 configuration. 307 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To configure N+N redundancy: [edit chassis] user@switch# set psu redundancy n-plus-n To revert back to N+1 redundancy: [edit chassis] user@switch# delete chassis psu redundancy n-plus-n Related Documentation • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 • Verifying Power Configuration and Use on page 309 • Understanding Power Management on J-EX Series Switches on page 302 Configuring the Power Priority of Line Cards (CLI Procedure) The power management facility on J-EX8200 switches allows you to assign power priorities to the slots occupied by line cards. Power management provides power to the slots in priority order, which means that line cards in higher priority slots are more likely to receive power than line cards in lower priority slots if power to the switch is insufficient to power all the line cards. When assigning power priority to slots, keep these points in mind: • 0 is the highest priority. For a J-EX8208 switch, you can assign a priority of 0 through 7 to a slot. For a J-EX8216 switch, you can assign a priority of 0 through 15 to a slot. • All slots are assigned the lowest priority by default. • If a group of slots shares the same assigned priority, each slot’s power priority within the group is based on its slot number, with the lowest-numbered slots receiving power first. To assign or change the power priority for a slot: [edit chassis] user@switch# set fpc slot power-budget-priority priority For example, to set slot 6 to priority 0, enter: [edit chassis] user@switch# set fpc 6 power-budget-priority 0 Related Documentation 308 • Configuring Power Supply Redundancy (CLI Procedure) on page 307 • Verifying Power Configuration and Use on page 309 • Understanding Power Management on J-EX Series Switches on page 302 CHAPTER 20 Verifying Power Management • Verifying Power Configuration and Use on page 309 Verifying Power Configuration and Use Purpose Action Verify on a J-EX8200 switch: • What the power redundancy and line card priority settings are • Whether the N+1 or N+N power requirements are being met • Whether the switch has sufficient power for a new line card or an N+N configuration Enter the following command: user@switch> show chassis power-budget-statistics PSU 1 (EX8200-AC2K) : PSU 2 (EX8200-AC2K) : PSU 3 (EX8200-AC2K) : PSU 4 (EX8200-AC2K) : Total Power supplied by all Online PSUs : Power Redundancy Configuration : Power Reserved for the Chassis : FPC 5 (EX8200-48F ) : FPC 6 (EX8200-8XS ) : Actual Power Used : Power Available (Redundant case) : Total Power Available : Meaning 1200 1200 1200 1200 4800 N+N 1200 330 450 1980 420 2820 W W W W W W W W W W W Priority: 7 Priority: 0 The switch is configured for N+N redundancy. As shown by the Power Available (Redundant case) field, the switch has sufficient power to meet the N+N power requirements and has an additional 420 W available. The switch has insufficient power for an additional 8-port SFP+ line card while maintaining N+N redundancy, because the line card requires 450 W. However, it does have enough power for an additional 48-port SFP line card, which requires only 330 W. The 8-port SFP+ line card in slot 6 has a higher power priority than the 48-port SFP line card line card in slot 5. 309 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: The amount of power shown in the Actual Power Used field reflects the total power allocated in the power budget for the installed components rather than the actual power being used by the components. Because the power budget allocation is based on maximum power use, actual power consumption is likely to be much less. Related Documentation 310 • Configuring Power Supply Redundancy (CLI Procedure) on page 307 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 CHAPTER 21 Configuration Statements for Power Management 311 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS fpc Syntax Hierarchy Level Release Information Description fpc slot { pic pic-number { sfpplus { pic-modemode; } } power-budget-priority priority; [edit chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On a J-EX4200 switch, specify the port of the SFP+ uplink module for which you want to configure the operating mode. On a J-EX8200 switch, specify the line card slot for which you want to assign a power priority. Options slot—Number of the slot: • 0—Standalone J-EX4200 switches. The FPC refers to the switch itself. • 0–9—J-EX4200 switch in a Virtual Chassis configuration. The value corresponds to the switch’s member ID. • 0–7—J-EX8208 switch. The slot is a line card slot. • 0–15—J-EX8216 switch. The slot is a line card slot. The remaining statements are explained separately. Required Privilege Level Related Documentation 312 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Setting the Mode on an SFP+ Uplink Module (CLI Procedure) on page 921 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 Chapter 21: Configuration Statements for Power Management n-plus-n Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation n-plus-n; [edit chassis psu redundancy] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Configure N+N power supply redundancy for power management on a J-EX8200 switch. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Power Supply Redundancy (CLI Procedure) on page 307 power-budget-priority Syntax Hierarchy Level Release Information Description Default Options power-budget-priority priority; [edit chassis fpc slot] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Assign a power priority to the specified line card slot on a J-EX8200 switch. All line card slots are initially assigned the lowest priority. priority—Assigned power priority for the slot, with 0 being the highest priority. Range: 0 through 7 for a J-EX8208 switch; 0 through 15 for a J-EX8216 switch Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 313 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS psu Syntax Hierarchy Level Release Information Description psu { redundancy { n-plus-n; } } [edit chassis] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Configure N+N power supply redundancy for power management on a J-EX8200 switch. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Power Supply Redundancy (CLI Procedure) on page 307 redundancy Syntax Hierarchy Level Release Information Description redundancy { n-plus-n; } [edit chassis psu] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Configure N+N power supply redundancy for power management on a J-EX8200 switch. The remaining statement is explained separately. Default Required Privilege Level Related Documentation 314 N+1 power supply redundancy is configured by default. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Power Supply Redundancy (CLI Procedure) on page 307 CHAPTER 22 Operational Mode Commands for Power Management 315 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis power-budget-statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show chassis power-budget-statistics Command introduced in Junos OS Release 10.2 for J-EX Series switches. Display the power budget of a J-EX8200 switch. view • Verifying Power Configuration and Use on page 309 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 • Configuring Power Supply Redundancy (CLI Procedure) on page 307 show chassis power-budget-statistics on page 317 Table 44 on page 316 lists the output fields for the show chassis power-budget-statistics command. Output fields are listed in the approximate order in which they appear. Table 44: show chassis power-budget-statistics Output Fields Field Name Field Description PSU n (supply type) Number of watts supplied by the power supply. All installed power supplies, whether currently operating or not, are listed. Power supplied by all Online PSUs Total number of watts supplied by all currently operating power supplies. Power Redundancy Configuration Configured power redundancy setting, either N+1 or N+N. Power Reserved for the Chassis Power reserved for the chassis: • For a J-EX8208 switch: 1600 W in an N+1 configuration; 1200 W in an N+N configuration • For a J-EX8216 switch: 2400 W in an N+1 configuration; 1800 W in an N+N configuration The power reserved for the chassis includes the maximum power requirements for the fan tray and Switch Fabric and Routing Engine (SRE), Routing Engine (RE), and Switch Fabric (SF) modules in both base and redundant configurations. FPC n (card type) Number of watts required by the line card in slot n and the power priority assigned to the slot. Actual Power Used Power budgeted for all the components in the switch. This equal to the power reserved for the chassis plus the power requirements of all online line cards. Because the amount budgeted is based on maximum power requirements, the real power consumption of the switch is likely to be less than this figure. 316 Chapter 22: Operational Mode Commands for Power Management Table 44: show chassis power-budget-statistics Output Fields (continued) Field Name Field Description Power Available (Redundant case) Unused power available to the switch in the power budget, excluding redundant power. If power is insufficient to meet the N+1 or N+N redundancy requirements, this value is 0. Total Power Available Unused power available to the switch in the power budget, including redundant power. show chassis power-budget-statistics user@switch> show chassis power-budget-statistics PSU 0 (EX8200-AC2K) : PSU 1 (EX8200-AC2K) : PSU 2 (EX8200-AC2K) : Total Power supplied by all Online PSUs : Power Redundancy Configuration : Power Reserved for the Chassis : FPC 6 (EX8200-8XS ) : Actual Power Used : Power Available (Redundant case) : Total Power Available : 2000 2000 2000 6000 N+N 1600 450 2050 1950 3950 W W W W W W W W W Priority: 7 317 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 318 PART 7 Junos OS for J-EX Series Switches Configuration Management • Configuration Management Overview on page 321 • Managing Junos OS Configuration on page 331 • Verifying Configuration on page 349 • Configuration Statements for Configuration Management on page 351 • Operational Mode Commands for Configuration Management on page 359 319 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 320 CHAPTER 23 Configuration Management Overview • Configuration Files—Overview on page 321 • J-EX Series Switches Default Configuration on page 325 Configuration Files—Overview • Understanding Configuration Files for J-EX Series Switches on page 321 • Configuration Files Terms on page 322 • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Understanding Autoinstallation of Configuration Files on J-EX Series Switches on page 323 Understanding Configuration Files for J-EX Series Switches A configuration file stores the complete configuration of a switch. The current configuration of a switch is called the active configuration. You can alter this current configuration and you can also return to a previous configuration or to a rescue configuration. For more information, see “Configuration Files Terms” on page 322. Junos OS saves the 50 most recently committed configuration files on the switch so that you can return to a previous configuration. The configuration files are named: • juniper.conf.gz—The current active configuration. • juniper.conf.1.gz to juniper.conf.49.gz—Rollback configurations. To make changes to the configuration file, you have to work in the configuration mode in the CLI or use the configuration tools in the J-Web interface. When making changes to a configuration file, you are viewing and changing the candidate configuration file. The candidate configuration allows you to make configuration changes without causing operational changes to the active configuration or causing potential damage to your current network operations. Once you commit the changes made to the candidate configuration, the system updates the active configuration. Related Documentation • Managing Configuration Files Through the Configuration History (J-Web Procedure) on page 338 • Uploading a Configuration File (CLI Procedure) on page 336 • Uploading a Configuration File (J-Web Procedure) on page 337 321 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Loading a Previous Configuration File (CLI Procedure) on page 340 • Reverting to the Rescue Configuration for the J-EX Series Switch on page 343 • Configuration Files Terms on page 322 Configuration Files Terms Table 45 on page 322 lists the various configuration file terms used for J-EX Series switches and their definitions. Table 45: Configuration File Terms Term Definition active configuration The current committed configuration of a switch. candidate configuration A working copy of the configuration that allows users to make configurational changes without causing any operational changes until this copy is committed. configuration group Group of configuration statements that can be inherited by the rest of the configuration. commit a configuration Have the candidate configuration checked for proper syntax, activated, and marked as the current configuration file running on the switching platform. configuration hierarchy The Junos OS configuration consists of a hierarchy of statements. There are two types of statements: container statements, which contain other statements, and leaf statements, which do not contain other statements. All the container and leaf statements together form the configuration hierarchy. default configuration The default configuration contains the initial values set for each configuration parameter when a switch is shipped. rescue configuration Well-known configuration that recovers a switch from a configuration that denies management access. You set a current committed configuration to be the rescue configuration through the J-Web interface or CLI. roll back a configuration Return to a previously committed configuration. Related Documentation 322 • J-EX4200 Default Configuration on page 325 • J-EX8200 Switch Default Configuration on page 329 • Loading a Previous Configuration File (CLI Procedure) on page 340 • Managing Configuration Files Through the Configuration History (J-Web Procedure) on page 338 • Reverting to the Rescue Configuration for the J-EX Series Switch on page 343 • Understanding Configuration Files for J-EX Series Switches on page 321 Chapter 23: Configuration Management Overview Understanding Automatic Refreshing of Scripts on J-EX Series Switches You can automatically refresh commit, event, and op scripts using operational mode commands on J-EX Series switches. The commands are: • request system scripts refresh-from commit • request system scripts refresh-from event • request system scripts refresh-from op The existing Junos OS command-line interface (CLI) refresh and refresh-from configuration mode statements have been extended to work with Junos XML management protocol and NETCONF XML management protocol sessions. Related Documentation • Understanding Autoinstallation of Configuration Files on J-EX Series Switches on page 323 • CLI User Interface Overview on page 127 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guideat http://www.juniper.net/techpubs/software/junos/ Understanding Autoinstallation of Configuration Files on J-EX Series Switches Autoinstallation is the automatic configuration of a device over the network from a pre-existing configuration file that you create and store on a configuration server—typically a Trivial File Transfer Protocol (TFTP) server. You can use autoinstallation to automatically configure new devices and to deploy multiple devices from a central location in the network. Autoinstallation takes place automatically when you connect an Ethernet port on a new switch to the network and power on the switch. You can also explicitly enable autoinstallation on J-EX Series Switches in your network to implement autoinstallation when they are powered on. To configure autointallation, you specify a configuration server, an autoinstallation interface, and a protocol for IP address acquisition. This topic describes: • Typical Uses for Autoinstallation on page 323 • Autoinstallation Configuration Files and IP Addresses on page 324 • Typical Autoinstallation Process on a New Switch on page 324 Typical Uses for Autoinstallation • To deploy and update multiple devices from a central location in the network. • To configure a new device—Autoinstallation takes place when you power on a device that has only the factory default configuration (boot) file. 323 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • To update a device—Autoinstallation takes place when a device that has been manually configured for autoinstallation is powered on. Autoinstallation Configuration Files and IP Addresses For the autoinstallation process to work, you must store one or more host-specific or default configuration files on a configuration server in the network and have a service available—typically Dynamic Host Configuration Protocol (DHCP)—to assign an IP address to the switch. You can set up the following configuration files for autoinstallation on the switch: • network.conf—Default configuration file for autoinstallation, in which you specify IP addresses and associated hostnames for devices on the network. • switch.conf—Default configuration file for autoinstallation with a minimum configuration sufficient for you to telnet to the device and configure it manually. • hostname.conf—Host-specific configuration file for autoinstallation on a device that contains all the configuration information necessary for the switch. In the filename, hostname is replaced with the hostname assigned to the switch. If the server with the autoinstallation configuration file is not on the same LAN segment as the new device, or if a specific device is required by the network, you must configure an intermediate device directly attached to the new switch, through which the new switch can send TFTP, boot protocol (BOOTP), and Domain Name System (DNS) requests. In this case, you specify the IP address of the intermediate device as the location to receive TFTP requests for autoinstallation. Typical Autoinstallation Process on a New Switch When a J-EX Series switch is powered on for the first time, it performs the following autoinstallation tasks: 1. The new switch sends out DHCP or BOOTP requests on each connected interface simultaneously to obtain an IP address. If a DHCP server responds to these requests, it provides the switch with some or all of the following information: • An IP address and subnet mask for the autoinstallation interface. • The location of the (typically) TFTP server, Hypertext Transfer Protocol (HTTP) server, or FTP server on which the configuration file is stored. • The name of the configuration file to be requested from the TFTP server. • The IP address or hostname of the TFTP server. If the DHCP server provides the server’s hostname, a DNS server must be available on the network to resolve the name to an IP address. • 324 The IP address of an intermediate device if the configuration server is on a different LAN segment from the new switch. Chapter 23: Configuration Management Overview 2. After the new switch acquires an IP address, the autoinstallation process on the switch attempts to download a configuration file in the following ways: a. If the DHCP server specifies the host-specific configuration file hostname.conf, the switch uses that filename in the TFTP server request. The autoinstallation process on the new switch makes three unicast TFTP requests for hostname.conf. If these attempts fail, the switch broadcasts three requests to any available TFTP server for the file. b. If the new switch does not locate a hostname.conf file, the autoinstallation process sends three unicast TFTP requests for a network.conf file that contains the switch’s hostname-to-IP-address mapping information. If these attempts fail, the switch broadcasts three requests to any available TFTP server for the file. c. If the switch fails to find a network.conf file that contains a hostname entry for the switch, the autoinstallation process sends out a DNS request and attempts to resolve the new switch's IP address to a hostname. d. If the new switch determines its hostname, it sends a TFTP request for the hostname.conf file. e. If the new switch is unable to map its IP address to a hostname, it sends TFTP requests for the default configuration file switch.conf. The TFTP request procedure is the same as for the network.conf file. 3. After the new switch locates a configuration file on a TFTP server, the autoinstallation process downloads the file, installs the file on the switch, and commits the configuration. Related Documentation • Configuring Autoinstallation of Configuration Files (CLI Procedure) on page 345 • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • Configuration Files Terms on page 322 J-EX Series Switches Default Configuration • J-EX4200 Default Configuration on page 325 • J-EX8200 Switch Default Configuration on page 329 J-EX4200 Default Configuration Each J-EX Series switch is programmed with a factory default configuration that contains the values set for each configuration parameter when a switch is shipped. The default configuration file sets values for system parameters such as syslog and commit; configures Power over Ethernet (PoE), storm control, and Ethernet switching on all interfaces; and enables the LLDP and RSTP protocols. When you commit changes to the configuration, a new configuration file is created that becomes the active configuration. You can always revert to the factory default 325 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS configuration. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. The following factory default configuration file is for a J-EX4200 switch with 24 ports (for models that have more ports, this default configuration file has more interfaces): NOTE: In this example, ge-0/0/0 through ge-0/0/23 are the network interface ports. Optional uplink modules provide four 1-gigabit SFP transceivers (ge-0/1/0 through ge-0/1/3). Although you can install only one uplink module, the interfaces for both are shown below. system { syslog { user * { any emergency; } file messages { any notice; authorization info; } file interactive-commands { interactive-commands any; } } commit { factory-settings { reset-chassis-lcd-menu; reset-virtual-chassis-configuration; } } } interfaces { ge-0/0/0 { unit 0 { family ethernet-switching; } } ge-0/0/1 { unit 0 { family ethernet-switching; } } ge-0/0/2 { unit 0 { family ethernet-switching; } } ge-0/0/3 { unit 0 { family ethernet-switching; } } ge-0/0/4 { 326 Chapter 23: Configuration Management Overview unit 0 { family ethernet-switching; } } ge-0/0/5 { unit 0 { family ethernet-switching; } } ge-0/0/6 { unit 0 { family ethernet-switching; } } ge-0/0/7 { unit 0 { family ethernet-switching; } } ge-0/0/8 { unit 0 { family ethernet-switching; } } ge-0/0/9 { unit 0 { family ethernet-switching; } } ge-0/0/10 { unit 0 { family ethernet-switching; } } ge-0/0/11 { unit 0 { family ethernet-switching; } } ge-0/0/12 { unit 0 { family ethernet-switching; } } ge-0/0/13 { unit 0 { family ethernet-switching; } } ge-0/0/14 { unit 0 { family ethernet-switching; } } ge-0/0/15 { unit 0 { 327 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS family ethernet-switching; } } ge-0/0/16 { unit 0 { family ethernet-switching; } } ge-0/0/17 { unit 0 { family ethernet-switching; } } ge-0/0/18 { unit 0 { family ethernet-switching; } } ge-0/0/19 { unit 0 { family ethernet-switching; } } ge-0/0/20 { unit 0 { family ethernet-switching; } } ge-0/0/21 { unit 0 { family ethernet-switching; } } ge-0/0/22 { unit 0 { family ethernet-switching; } } ge-0/0/23 { unit 0 { family ethernet-switching; } } ge-0/1/0 { unit 0 { family ethernet-switching; } } ge-0/1/1 { unit 0 { family ethernet-switching; } } ge-0/1/2 { unit 0 { family ethernet-switching; 328 Chapter 23: Configuration Management Overview } } ge-0/1/3 { unit 0 { family ethernet-switching; } } } protocols { igmp-snooping{ vlan all; } lldp { interface all; } lldp-med { interface all; } rstp; } ethernet-switching-options { storm-control { interface all; } } poe { interface all; } Related Documentation • Reverting to the Default Factory Configuration for the J-EX Series Switch on page 341 • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • Understanding Configuration Files for J-EX Series Switches on page 321 • J-EX Series Switches Interfaces Overview on page 863 J-EX8200 Switch Default Configuration Each J-EX8200 switch is programmed with a factory default configuration that contains the values set for each configuration parameter when a switch is shipped. The default configuration file sets values for system parameters such as the ARP aging timer, the system log, and file messages, while also enabling the LLDP protocol, the RSTP protocol, IGMP snooping, and storm control. When you commit changes to the configuration, a new configuration file is created that becomes the active configuration. You can always revert to the factory default configuration. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. This topic shows the factory default configuration file of a J-EX8200 switch: system { arp { 329 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS aging-timer 5 } } syslog { user * { any emergency; } file messages { any notice; authorization info; } file interactive-commands { interactive-commands any; } } commit { factory-settings { reset-chassis-lcd-menu; } } } protocols { igmp-snooping { vlan all; } lldp { interface all; } rstp; } ethernet-switching-options { storm-control { interface all; } } Related Documentation 330 • Configuration Files Terms on page 322 • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • Understanding Configuration Files for J-EX Series Switches on page 321 • J-EX8208 Switch Hardware Overview on page 27 • J-EX8216 Switch Hardware Overview on page 30 CHAPTER 24 Managing Junos OS Configuration • Using the Configuration Tools in J-Web on page 331 • Managing Junos OS Configuration on page 335 Using the Configuration Tools in J-Web • Using the CLI Viewer in the J-Web Interface to View Configuration Text on page 331 • Using the CLI Editor in the J-Web Interface to Edit Configuration Text on page 331 • Using the Point and Click CLI Tool in the J-Web Interface to Edit Configuration Text on page 332 • Using the Commit Options to Commit Configuration Changes (J-Web Procedure) on page 334 Using the CLI Viewer in the J-Web Interface to View Configuration Text To view the entire configuration file contents in text format, select Configure>CLI Tools >CLI Viewer. The main pane displays the configuration in text format. Each level in the hierarchy is indented to indicate each statement's relative position in the hierarchy. Each level is generally set off with braces, with an open brace ({) at the beginning of each hierarchy level and a closing brace (}) at the end. If the statement at a hierarchy level is empty, the braces are not displayed. Each leaf statement ends with a semicolon (;), as does the last statement in the hierarchy. This indented representation is used when the configuration is displayed or saved as an ASCII file. However, when you load an ASCII configuration file, the format of the file is not so strict. The braces and semicolons are required, but the indention and use of new lines are not required in ASCII configuration files. Related Documentation • Understanding J-Web Configuration Tools on page 131 Using the CLI Editor in the J-Web Interface to Edit Configuration Text Use the CLI Editor to edit configuration if you know the Junos OS CLI or prefer a command interface. To edit the entire configuration in text format: 331 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS CAUTION: We recommend that you use this method to edit and commit the configuration only if you have experience editing configurations through the CLI. 1. Select Configure>CLI Tools>CLI Editor. The main pane displays the configuration in a text editor. 2. Navigate to the hierarchy level you want to edit. You can edit the candidate configuration using standard text editor operations—insert lines (by using the Enter key), delete lines, and modify, copy, and paste text. 3. Click Commit to load and commit the configuration. The switching platform checks the configuration for the correct syntax before committing it. Related Documentation • CLI User Interface Overview on page 127 • Understanding J-Web Configuration Tools on page 131 Using the Point and Click CLI Tool in the J-Web Interface to Edit Configuration Text To edit the configuration on a series of pages of clickable options that steps you through the hierarchy, select Configure>CLI Tools>Point&Click CLI. The side pane displays the top level of the configured hierarchy, and the main pane displays configured hierarchy options and the Icon Legend. To expand or hide the hierarchy of all the statements in the side pane, click Expand all or Hide all. To expand or hide an individual statement in the hierarchy, click the expand (+) or collapse (–) icon to the left of the statement. TIP: Only those statements included in the committed configuration are displayed in the hierarchy. The configuration information in the main pane consists of configuration options that correspond to configuration statements. Configuration options that contain subordinate statements are identified by the term Nested. To include, edit, or delete statements in the candidate configuration, click one of the links described in Table 46 on page 332. Then specify configuration information by typing in a field, selecting a value from a list, or clicking a check box (toggle). Table 46: J-Web Edit Point & Click Configuration Links Link Function Add new entry Displays fields and lists for a statement identifier, allowing you to add a new identifier to a statement. 332 Chapter 24: Managing Junos OS Configuration Table 46: J-Web Edit Point & Click Configuration Links (continued) Link Function Configure Displays information for a configuration option that has not been configured, allowing you to include a statement. Delete Deletes the corresponding statement or identifier from the configuration. All subordinate statements and identifiers contained within a deleted statement are also discarded. Edit Displays information for a configuration option that has already been configured, allowing you to edit a statement. Identifier Displays fields and lists for an existing statement identifier, allowing you to edit the identifier. As you navigate through the configuration, the hierarchy level is displayed at the top of the main pane. You can click a statement or identifier in the hierarchy to display the corresponding configuration options in the main pane. The main pane includes icons that display information about statements and identifiers when you place your cursor over them. Table 47 on page 333 describes these icons. Table 47: J-Web Edit Point & Click Configuration Icons Icon Function C Displays a comment about a statement. I Indicates that a statement is inactive. M Indicates that a statement has been added or modified but has not been committed. * Indicates that the statement or identifier is required in the configuration. ? Provides online help information. After typing or selecting your configuration edits, click a button in the main pane (described in Table 48 on page 333) to apply your changes or cancel them, refresh the display, or discard parts of the candidate configuration. An updated configuration does not take effect until you commit it. Table 48: J-Web Edit Point & Click Configuration Buttons Button Function Refresh Updates the display with any changes to the configuration made by other users. Commit Verifies edits and applies them to the current configuration file running on the switch. Discard Removes edits applied to or deletes existing statements or identifiers from the candidate configuration. 333 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • CLI User Interface Overview on page 127 • Understanding J-Web Configuration Tools on page 131 Using the Commit Options to Commit Configuration Changes (J-Web Procedure) You can use the single-commit feature to commit all outstanding configuration changes in the J-Web interface on J-EX Series switches simultaneously. This helps in reducing the time J-Web takes for committing configurations because when changes are committed at every step, rollback configurations pile up. For example, suppose you want to delete a firewall filter and add a new one. With immediate commits, you would need to commit your changes twice for this action. Using single commit, you can decrease the number of commits to one, thus saving time for working on other configurations. When you edit a configuration, you work on a copy of the current configuration, which is your candidate configuration. The changes you make to the candidate configuration are visible through the user interface immediately, allowing other users to edit those configurations, but they do not take effect on the switch until you commit the changes. When you commit the configuration, the candidate file is checked for proper syntax, activated, and marked as the current, operational software configuration file. If multiple users are editing the configuration when you commit the candidate configuration, changes made by all users take effect. You can configure the commit options to either commit all configuration changes together or commit each configuration change immediately using the J-Web Commit Preference page. 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 of such a page is the Interface Page (Configure > Interface). To configure the commit options on a J-EX Series switch using the J-Web interface: 1. Select Commit Options. NOTE: All action links except Preference are disabled unless you edit, add, or delete a configuration. 2. Choose an action. See Table 49 on page 335 for details on the actions. 3. Configure the commit options by selecting Preference. See Table 50 on page 335 for details on preference options. 334 Chapter 24: Managing Junos OS Configuration Table 49: Commit Options Menu Item Function Your Action Commit Commits the candidate configuration of the current user session, along with changes from other user sessions. 1. Select Commit Options > Commit. Changes are committed after the system validates your configuration. A window displays that the configuration was successfully committed or that the commit failed. 2. Click OK. Click Details to view the commit log. Compare Displays the XML log of pending uncommitted configurations on the device. 1. Select Commit Options > Compare. The XML log of pending configurations on the devices are displayed similar to the CLI interface, in a “human-readable” form. 2. Click Close. Discard Preference Discards the candidate configuration of your current session, along with changes from other user sessions. 1. Indicates your choice of committing all global configurations together or committing each configuration change immediately. 1. Select Commit Options > Discard. 2. Click OK to confirm the discard action. Your changes are discarded after the system validates your configuration. Select Commit Options > Preference. The Commit Preference page is displayed. 2. Configure the commit options by selecting your preference. See Table 50 on page 335 for details on preference options. Table 50: Commit Preference Options Option Function Validate and commit configuration changes Sets the system to validate and force an immediate commit on every screen after every configuration change. Validate configuration changes Loads all the configuration changes for an accumulated single commit. If there are errors in loading the configuration, the errors are logged. This is the default mode. Once you select this option, you need to select Commit Options > Commit to commit your changes. Related Documentation • J-Web User Interface for J-EX Series Switches Overview on page 129 • J-EX Series Switch Software Features Overview on page 3 Managing Junos OS Configuration • Uploading a Configuration File (CLI Procedure) on page 336 • Uploading a Configuration File (J-Web Procedure) on page 337 335 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Managing Configuration Files Through the Configuration History (J-Web Procedure) on page 338 • Loading a Previous Configuration File (CLI Procedure) on page 340 • Reverting to the Default Factory Configuration for the J-EX Series Switch on page 341 • Reverting to the Rescue Configuration for the J-EX Series Switch on page 343 • Setting or Deleting the Rescue Configuration (CLI Procedure) on page 344 • Setting or Deleting the Rescue Configuration (J-Web Procedure) on page 345 • Configuring Autoinstallation of Configuration Files (CLI Procedure) on page 345 Uploading a Configuration File (CLI Procedure) You can create a configuration file on your local system, copy the file to the J-EX Series switch and then load the file into the CLI. After you have loaded the configuration file, you can commit it to activate the configuration on the switch. You can also edit the configuration interactively using the CLI and commit it at a later time. To upload a configuration file from your local system: 1. Create the configuration file using a text editor such as Notepad, making sure that the syntax of the configuration file is correct. For more information about testing the syntax of a configuration file see Junos OS System Basics and Services Command Reference at http://www.juniper.net/techpubs/software/junos/. 2. In the configuration text file, use an option to perform the required action when the file is loaded. Table 51 on page 336 lists and describes some options for the load command. Table 51: Options for the load command Options Description merge Combines the current active configuration and the configuration in filename or the one that you type at the terminal. A merge operation is useful when you are adding a new section to an existing configuration. If the active configuration and the incoming configuration contain conflicting statements, the statements in the incoming configuration override those in the active configuration. override Discards the current candidate configuration and loads the configuration in filename or the one that you type at the terminal. When you use the override option and commit the configuration, all system processes reparse the configuration. You can use the override option at any level of the hierarchy. replace Searches for the replace tags, deletes the existing statements of the same name, if any, and replaces them with the incoming configuration. If there is no existing statement of the same name, the replace operation adds the statements marked with the replace tag to the active configuration. NOTE: For this operation to work, you must include replace tags in the text file or in the configuration you type at the terminal. 3. Press Ctrl+A to select all the text in the configuration file. 4. Press Ctrl+C to copy the contents of the configuration text file to the Clipboard. 336 Chapter 24: Managing Junos OS Configuration 5. Log in to the switch using your username and password. 6. To enter configuration mode: user@switch> configure You will see this output, with the hash or pound mark indicating configuration mode. Entering configuration mode [edit] user@switch# 7. Load the configuration file: [edit] user@switch# load merge terminal 8. At the cursor, paste the contents of the Clipboard using the mouse and the Paste icon: [edit] user@switch# load merge terminal [Type ^D at a new line to end input] >Cursor is here. Paste the contents of the clipboard here< 9. Press Enter. 10. Press Ctrl+D to set the end-of-file marker. To view results of the configuration steps before committing the configuration, type the show command at the user prompt. To commit these changes to the active configuration, type the commit command at the user prompt.You can also edit the configuration interactively using the CLI and commit it at a later time. Related Documentation • Uploading a Configuration File (J-Web Procedure) on page 337 • Understanding Configuration Files for J-EX Series Switches on page 321 Uploading a Configuration File (J-Web Procedure) You can create a configuration file on your local system, copy the file to the J-EX Series switch and then load the file into the CLI. After you have loaded the configuration file, you can commit it to activate the configuration on the switch. You can also edit the configuration interactively using the CLI and commit it at a later time. To upload a configuration file from your local system: 1. Select Maintain > Config Management > Upload. The main pane displays the File to Upload box. 2. Specify the name of the file to upload using one of the following methods: • Type the absolute path and filename in the File to Upload box. • Click Browse to navigate to the file. 3. Click Upload and Commit to upload and commit the configuration. 337 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS The switch checks the configuration for the correct syntax before committing it. Related Documentation • Uploading a Configuration File (CLI Procedure) on page 336 • Understanding J-Web Configuration Tools on page 131 • Understanding Configuration Files for J-EX Series Switches on page 321 Managing Configuration Files Through the Configuration History (J-Web Procedure) Use the Configuration History function to manage configuration files. 1. Displaying Configuration History on page 338 2. Displaying Users Editing the Configuration on page 339 3. Comparing Configuration Files with the J-Web Interface on page 339 4. Downloading a Configuration File with the J-Web Interface on page 340 5. Loading a Previous Configuration File with the J-Web Interface on page 340 Displaying Configuration History To manage configuration files with the J-Web interface, select Maintain > Config Management >History. The main pane displays History — Database Information page. Table 52 on page 338 summarizes the contents of the display. The configuration history display allows you to: • View a configuration. • Compare two configurations. • Download a configuration file to your local system. • Roll back the configuration to any of the previous versions stored on the switch. Table 52: J-Web Configuration History Summary Field Description Number Version of the configuration file. Date/Time Date and time the configuration was committed. User Name of the user who committed the configuration. Client Method by which the configuration was committed: • cli—A user entered a Junos OS CLI command. • junoscript—A Junos XML protocol client performed the operation. Commit operations performed by users through the J-Web interface are identified in this way. Comment 338 • snmp—An SNMP set request started the operation. • other—Another method was used to commit the configuration. Comment. Chapter 24: Managing Junos OS Configuration Table 52: J-Web Configuration History Summary (continued) Field Description Log Message Method used to edit the configuration: Action • Imported via paste— Configuration was edited and loaded with the Configure>CLI Tools>Edit Configuration Text option. • Imported upload [filename]—Configuration was uploaded with the Configure>CLI Tools>Point Click Editor option. • Modified via J–Web Configure — Configuration was modified with the J-Web Configure menu. • Rolled back via user-interface— Configuration was rolled back to a previous version through the user interface specified by user-interface, which can be Web Interface or CLI. Action to perform with the configuration file. The action can be Download or Rollback. Displaying Users Editing the Configuration To display a list of users editing the switching platform configuration, select Config Management >History. The list is displayed as Database Information in the main pane. Table 53 on page 339 summarizes the Database Information display. Table 53: J-Web Configuration Database Information Summary Field Description User Name Name of user editing the configuration. Start Time Time of day the user logged in to the switch. Idle Time Elapsed time since the user issued a configuration command from the CLI. Terminal Terminal on which the user is logged in. PID Process identifier assigned to the user by the switching platform. Edit Flags Designates a private or exclusive edit. Edit Path Level of the configuration hierarchy that the user is editing. Comparing Configuration Files with the J-Web Interface To compare any two of the past 50 committed configuration files: 1. Select Config Management >History. A list of the current and the previous 49 configurations is displayed as Configuration History in the main pane. 2. Select the check boxes to the left of the two configuration versions you want to compare. 3. Click Compare. The main pane displays the differences between the two configuration files at each hierarchy level as follows: 339 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Lines that have changed are highlighted side by side in green. • Lines that exist only in the more recent configuration file are displayed in red on the left. • Lines that exist only in the older configuration file are displayed in blue on the right. Downloading a Configuration File with the J-Web Interface To download a configuration file from the switch to your local system: 1. Select Config Management >History. A list of current and previous 49 configurations is displayed as Configuration History in the main pane. 2. In the Action column, click Download for the version of the configuration you want to download. 3. Select the options your Web browser provides that allow you to save the configuration file to a target directory on your local system. The file is saved as an ASCII file. Loading a Previous Configuration File with the J-Web Interface To load (roll back) and commit a previous configuration file stored on the switching platform: 1. Select Config Management >History. A list of current and previous 49 configurations is displayed as Configuration History in the main pane. 2. In the Action column, click Rollback for the version of the configuration you want to load. The main pane displays the results of the rollback operation. NOTE: When you click Rollback, the switch loads and commits the selected configuration. This behavior is different from the switch's behavior that occurs after you enter the rollback configuration mode command from the CLI. In the latter case, the configuration is loaded but not committed. Related Documentation • Loading a Previous Configuration File (CLI Procedure) on page 340 • Understanding Configuration Files for J-EX Series Switches on page 321 • Understanding J-Web Configuration Tools on page 131 Loading a Previous Configuration File (CLI Procedure) You can return to a previously committed configuration file if you need to revert to a previous configuration. The J-EX Series switch saves the last 50 committed configurations, including the rollback number, date, time, and name of the user who issued the commit configuration command. 340 Chapter 24: Managing Junos OS Configuration Syntax rollback Options • none— Return to the most recently saved configuration. • number—Configuration to return to. • Range: 0 through 49. The most recently saved configuration is number 0, and the oldest saved configuration is number 49. • Default: 0 To return to a configuration prior to the most recently committed one: 1. Specify the rollback number (here, 1 is entered and the configuration returns to the previously committed configuation): [edit] user@switch# rollback 1 load complete 2. Activate the configuration you have loaded: [edit] user@switch# commit Related Documentation • Managing Configuration Files Through the Configuration History (J-Web Procedure) on page 338 • Configuration Files Terms on page 322 • For more information on rollback, see the Junos OS CLI User Guide at http://www.juniper.net/techpubs/software/junos/ . Reverting to the Default Factory Configuration for the J-EX Series Switch If for any reason the current active configuration fails, you can revert to the default factory configuration. You can also roll back to a previous configuration, as described in “Loading a Previous Configuration File (CLI Procedure)” on page 340, or revert to the rescue configuration, as described in “Reverting to the Rescue Configuration for the J-EX Series Switch” on page 343. The default factory configuration contains the basic configuration settings. This is the first configuration of the switch and it is loaded when the switch is first installed and powered on. 341 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS You can revert to the default factory configuration by using the Menu button to the right of the LCD on the front panel of the switch or by using the load factory default configuration command. • Reverting to the Default Factory Configuration by Using the LCD Panel on page 342 • Reverting to the Default Factory Configuration by Using the Load Factory Default Command on page 342 Reverting to the Default Factory Configuration by Using the LCD Panel To set the switch to the default factory configuration, use the LCD panel and buttons on the front panel of the switch as shown in Figure 5 on page 342. If the switch model does not have an LCD panel, use the CLI command described in the following section. Use the LCD panel to revert to the default factory configuration if you want to run EZsetup. When you use the CLI to revert to the default factory configuration, the configuration for the root password is retained and you cannot run EZSetup. Figure 5: J-EX Series Switch LCD Panel NOTE: If you want to convert a J-EX4200 switch from a member of a multimember Virtual Chassis configuration to a standalone switch, first disconnect the cables connected to the Virtual Chassis ports (VCPs). See Disconnecting a Virtual Chassis Cable from a J-EX4200 Switch. The Menu button procedure deletes all modified configuration parameters, including Virtual Chassis parameters such as member ID, mastership priority, and setting of VCP uplinks. 1. Press the Menu button until you see MAINTENANCE MENU on the panel. 2. Press the Enter button. 3. Press Menu until you see FACTORY DEFAULT. 4. Press Enter. The display says RESTORE DEFAULT? 5. Press Enter. The screen flashes FACTORY DEFAULT IN PROGRESS and returns to the idle menu. Reverting to the Default Factory Configuration by Using the Load Factory Default Command The load factory default command is a standard Junos OS configuration command. This configuration command replaces the current active configuration with the default factory configuration. 342 Chapter 24: Managing Junos OS Configuration Use the LCD panel to revert to the default factory configuration if you want to run EZsetup. When you use the CLI to revert to the default factory configuration, the configuration for the root password is retained and you cannot run EZSetup. NOTE: The load factory default command by itself is not supported on J-EX4200 switches configured in a Virtual Chassis with multiple members. In a multimember Virtual Chassis configuration, you can revert to the default factory configuration while retaining the Virtual Chassis parameters (member ID, mastership priority, or settings of VCP uplinks) using the following procedure: 1. [edit] user@switch# load factory default 2. [edit] user@switch# delete system commit factory-settings 3. [edit] user@switch# commit 4. Check the member ID and mastership priority with the show virtual-chassis status command and check to see whether there are remaining settings for uplink VCPs by using the show virtual-chassis vc-port command. Related Documentation • Configuring a Virtual Chassis (CLI Procedure) on page 781 • J-EX4200 Default Configuration on page 325 • J-EX8200 Switch Default Configuration on page 329 • Understanding Configuration Files for J-EX Series Switches on page 321 • For more information about the load factory default command see the Junos OS CLI User Guide at http://www.juniper.net/techpubs/software/junos/. Reverting to the Rescue Configuration for the J-EX Series Switch If someone inadvertently commits a configuration that denies management access to a J-EX Series switch and the console port is not accessible, you can overwrite the invalid configuration and replace it with the rescue configuration by using the LCD panel on the switch. The rescue configuration is a previously committed, valid configuration. You can also revert to the default factory configuration, as described in “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. Before you begin to revert to the rescue configuration: • Ensure that you have physical access to the switch. • A rescue configuration for the switch must have been previously set. 343 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To revert the switch to the rescue configuration: 1. At the LCD panel on the switch, press Menu until you see MAINTENANCE MENU. 2. Press Enter. 3. Press Menu until you see Load Rescue. 4. Press Enter. 5. When Commit Rescue is displayed, press Enter. The LCD panel displays the message Commit Rescue in Progress. When the reversion is complete, it displays the idle menu. NOTE: If there is no rescue configuration saved on the switch, the message Commit rescue failed is displayed. Related Documentation • Setting or Deleting the Rescue Configuration (CLI Procedure) on page 344 • Setting or Deleting the Rescue Configuration (J-Web Procedure) on page 345 • LCD Panel in J-EX4200 Switches • LCD Panel in a J-EX8200 Switch • Configuration Files Terms on page 322 Setting or Deleting the Rescue Configuration (CLI Procedure) A rescue configuration is a well-known configuration that recovers a switch from a configuration that denies management access. You set a current committed configuration to be the rescue configuration through the J-Web interface or CLI. If someone inadvertently commits a configuration that denies management access to a J-EX Series switch and the console port is not accessible, you can overwrite the invalid configuration and replace it with the rescue configuration by using the LCD panel on the switch. The rescue configuration is a previously committed, valid configuration. We recommend that the rescue configuration include the IP address (accessible from the network) for the management port. To set the current active configuration as the rescue configuration: user@switch> request system configuration rescue save To delete an existing rescue configuration: user@switch> request system configuration rescue delete Related Documentation 344 • Setting or Deleting the Rescue Configuration (J-Web Procedure) on page 345 • Reverting to the Rescue Configuration for the J-EX Series Switch on page 343 • Loading a Previous Configuration File (CLI Procedure) on page 340 Chapter 24: Managing Junos OS Configuration • Configuration Files Terms on page 322 • For information on show system configuration rescue, see the Junos OS System Basics and Services Command Reference at http://www.juniper.net/techpubs/software/junos/ . Setting or Deleting the Rescue Configuration (J-Web Procedure) A rescue configuration is a well-known configuration that recovers a switch from a configuration that denies management access. You set a current committed configuration to be the rescue configuration through the J-Web interface or CLI. If someone inadvertently commits a configuration that denies management access to a J-EX Series switch and the console port is not accessible, you can overwrite the invalid configuration and replace it with the rescue configuration by using the LCD panel on the switch. The rescue configuration is a previously committed, valid configuration. We recommend that the rescue configuration include the IP address (accessible from the network) for the management port. To view, set, or delete the rescue configuration using the J-Web interface, select Maintain > Config Management >Rescue. On the Rescue page, you can perform the following tasks: Related Documentation • View the current rescue configuration—Click View rescue configuration. • Set the current running configuration as the rescue configuration—Click Set rescue configuration. • Delete the current rescue configuration—Click Delete rescue configuration. • Setting or Deleting the Rescue Configuration (CLI Procedure) on page 344 • Reverting to the Rescue Configuration for the J-EX Series Switch on page 343 • Configuration Files Terms on page 322 Configuring Autoinstallation of Configuration Files (CLI Procedure) Autoinstallation is the automatic configuration of a device over the network from a pre-existing configuration file that you create and store on a configuration server—typically a Trivial File Transfer Protocol (TFTP) server. You can use autoinstallation to automatically configure new devices and to deploy multiple devices from a central location in the network. No configuration is required on a new switch (a switch that has the factory default configuration file), because it is an automated process. However, to specify autoinstallation to run when you power on a switch already installed in your network, you can enable it by specifying one or more interfaces, protocols, and configuration servers to be used for autoinstallation. Before you explicitly enable and configure autoinstallation on the switch, perform these tasks as needed for your network’s configuration: 345 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Have a service available—typically Dynamic Host Configuration Protocol (DHCP)—to assign an IP address to the switch • Configure a DHCP server on your network to meet your network requirements. You can configure a J-EX Series switch to operate as a DHCP server. For more information, see “Configuring DHCP Services (J-Web Procedure)” on page 447. • Create one of the following configuration files, and store it on a TFTP server (or HTTP server or FTP server) in the network: • A host-specific file with the name hostname.conf for each switch undergoing autoinstallation. Replace hostname with the name of a switch. The hostname.conf file typically contains all the configuration information necessary for the switch with this hostname. • A default configuration file named switch.conf with the minimum configuration necessary to enable you to telnet into the new switch for further configuration. • Physically attach the switch to the network using a Gigabit Ethernet port. • If you configure the DHCP server to provide only the TFTP server hostname, add an IP address-to-hostname mapping entry for the TFTP server to the DNS database file on the Domain Name System (DNS) server in the network. • If the new switch is not on the same network segment as the DHCP server (or other device providing IP address resolution), configure an existing device as an intermediate device to receive TFTP and DNS requests and forward them to the TFTP server and the DNS server. You must configure the LAN or serial interface on the intermediate device with the IP addresses of the hosts providing TFTP and DNS services. Connect this interface to the new switch. • If you are using hostname.conf files for autoinstallation, you must also complete the following tasks: • Configure the DHCP server to provide a hostname.conf filename to each new switch. Each switch uses its hostname.conf filename to request a configuration file from the TFTP server. Copy the necessary hostname.conf configuration files to the TFTP server. • Create a default configuration file named network.conf, and copy it to the TFTP server. This file contains IP-address-to-hostname mapping entries. If the DHCP server does not send a hostname.conf filename to a new switch, the switch uses network.conf to resolve its hostname based on its IP address. Alternatively, you can add the IP-address-to-hostname mapping entry for the new switch to a DNS database file. The switch uses the hostname to request a hostname.conf file from the TFTP server. To configure autoinstallation: 1. Specify the URL address of one or more servers from which to obtain configuration files. [edit system] user@switch# set autoinstallation configuration-servers tftp://tftpconfig.sp.com 346 Chapter 24: Managing Junos OS Configuration NOTE: You can also use an FTP address, for example, ftp://user:password@sftpconfig.sp.com. 2. Configure one or more Ethernet interfaces to perform autoinstallation and one or two procurement protocols for each interface. The switch uses the protocols to send a request for an IP address for the interface: [edit system] user@switch# set autoinstallation interfaces ge-0/0/0 bootp Related Documentation • Verifying Autoinstallation Status on a J-EX Series Switch on page 349 • Understanding Autoinstallation of Configuration Files on J-EX Series Switches on page 323 • DHCP Services for J-EX Series Switches Overview on page 445 347 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 348 CHAPTER 25 Verifying Configuration • Verifying Autoinstallation Status on a J-EX Series Switch on page 349 Verifying Autoinstallation Status on a J-EX Series Switch Purpose Action Sample Output Meaning Related Documentation Display the status of the autoinstallation feature on a J-EX Series switch. From the CLI, enter the show system autoinstallation status command. user@switch> show system autoinstallation status Autoinstallation status: Master state: Active Last committed file: None Configuration server of last committed file: 10.25.100.1 Interface: Name: ge-0/0/0 State: Configuration Acquisition Acquired: Address: 192.168.124.75 Hostname: host-ge-000 Hostname source: DNS Configuration filename: switch-ge-000.conf Configuration filename server: 10.25.100.3 Address acquisition: Protocol: DHCP Client Acquired address: None Protocol: RARP Client Acquired address: None Interface: Name: ge-0/0/1 State: None Address acquisition: Protocol: DHCP Client Acquired address: None Protocol: RARP Client Acquired address: None The output shows the settings configured for autoinstallation. Verify that the values displayed are correct for the switch when it is deployed on the network. • Configuring Autoinstallation of Configuration Files (CLI Procedure) on page 345 349 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 350 CHAPTER 26 Configuration Statements for Configuration Management archival Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation archival { configuration { archive-sites { ftp://username:@:/; scp://:@:/; } transfer-interval interval; transfer-on-commit; } } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure copying of the currently active configuration to an archive site. The remaining statements are explained separately. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Using Junos OS to Configure a Router or Switch to Transfer Its Configuration to an Archive Site 351 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS archive-sites (Configuration File) Syntax Hierarchy Level Release Information Description archive-sites { file:///; ftp://username@host:url-path password password; http://username@host:url-path password password; scp://username@host:url-path password password; } [edit system archival configuration] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify where to transfer the current configuration files. When specifying a URL in a Junos OS statement using an IPv6 host address, you must enclose the entire URL in quotation marks (" ") and enclose the IPv6 host address in brackets ([ ]). For example, "scp://username<:password>@[ipv6-host-address]<:port>/url-path" If you specify more than one archive site, the router or switch attempts to transfer the configuration files to the first archive site in the list, moving to the next only if the transfer fails. The format for the destination filename is router-name_juniper.conf[.gz]_YYYYMMDD_HHMMSS. NOTE: The time included in the destination filename is always in Coordinated Universal Time (UTC) regardless of whether the time on the router or switch is configured as UTC or the local time zone. The default time zone on the router or switch is UTC. Required Privilege Level Related Documentation 352 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Using Junos OS to Configure a Router or Switch to Transfer Its Configuration to an Archive Site • configuration on page 355 • transfer-on-commit on page 358 Chapter 26: Configuration Statements for Configuration Management autoinstallation Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation autoinstallation { configuration-servers { url; } interfaces { interface-name { bootp; rarp; } } } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Download a configuration file automatically from an FTP, Hypertext Transfer Protocol (HTTP), or Trivial FTP (TFTP) server. When you power on a router or switch configured for autoinstallation, it requests an IP address from a Dynamic Host Configuration Protocol (DHCP) server. Once the router or switch has an address, it sends a request to a configuration server and downloads and installs a configuration. The remaining statements are explained separately. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 • configuration-servers on page 356 • idle-timeout on page 418 353 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS commit synchronize Syntax Hierarchy Level Release Information Description commit synchronize; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For devices with multiple Routing Engines only. Configure a commit command to automatically result in a commit synchronize command. The Routing Engine on which you execute the commit command (the requesting Routing Engine) copies and loads its candidate configuration to the other (the responding) Routing Engines. All Routing Engines then perform a syntax check on the candidate configuration file being committed. If no errors are found, the configuration is activated and becomes the current operational configuration on all Routing Engines. Accounting of events and operations on a backup Routing Engine is not supported on accounting servers such as TACACS+ or RADIUS. Logging of accounting events is supported only for events and operations on a master Routing Engine. Required Privilege Level Related Documentation 354 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring Multiple Routing Engines to Synchronize Committed Configurations Automatically Chapter 26: Configuration Statements for Configuration Management configuration Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation configuration { transfer-interval interval; transfer-on-commit; archive-sites { file:///; ftp://:@:/ password password; http://username@host:url-path password password; scp://username@host:url-path password password; } } [edit system archival] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to transfer its currently active configuration by means of FTP periodically or after each commit. The remaining statements are explained separately. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Using Junos OS to Configure a Router or Switch to Transfer Its Configuration to an Archive Site • archive on page 560 • transfer-interval on page 358 • transfer-on-commit on page 358 355 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS configuration-servers Syntax Hierarchy Level Release Information Description configuration-servers { url; } [edit system autoinstallation] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only, configure the URL address of a server from which to obtain configuration files. Examples of URLs: tftp://hostname/path/filename ftp://username:prompt@ftp.hostname.net/filename / Required Privilege Level Related Documentation 356 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 • autoinstallation on page 353 • idle-timeout on page 418 Chapter 26: Configuration Statements for Configuration Management interfaces Syntax Hierarchy Level Release Information Description Options interfaces { interface-name { bootp; rarp; slarp; } } [edit system autoinstallation] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Configure the interface on which to perform autoinstallation. A request for an IP address is sent from the interface. Specify the IP address procurement protocol. bootp—Send requests over serial interfaces with Frame Relay. rarp—Send requests over Ethernet interfaces. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 • J Series Services Router Basic LAN and WAN Access Configuration Guide • autoinstallation on page 353 357 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS transfer-interval (Configuration) Syntax Hierarchy Level Release Information Description Options transfer-interval interval; [edit system archival configuration] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the switch to periodically transfer its currently active configuration to an archive site. interval—Interval at which to transfer the current configuration to an archive site. Range: 15 through 2880 minutes Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • archive on page 560 • configuration on page 355 • transfer-on-commit on page 358 transfer-on-commit Syntax Hierarchy Level Release Information Description transfer-on-commit; [edit system archival configuration] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the switch to transfer its currently active configuration to an archive site each time you commit a candidate configuration. NOTE: When specifying a URL in a Junos OS statement using an IPv6 host address, you must enclose the entire URL in quotation marks (“ ”) and enclose the IPv6 host address in brackets ([ ]). For example, “ftp://username<:password>@[ipv6-host-address]<:port>/url-path” Required Privilege Level Related Documentation 358 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • archive on page 560 • configuration on page 355 • transfer-interval on page 358 CHAPTER 27 Operational Mode Commands for Configuration Management 359 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear log Syntax Release Information Description Options clear log filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Remove contents of a log file. filename—Name of the specific log file to truncate. all—(Optional) Truncate the specified log file and delete all archived versions of it. Required Privilege Level Related Documentation List of Sample Output Output Fields clear log clear • show log on page 657 clear log on page 360 See file list for an explanation of output fields. The following sample commands list log file information, clear the contents of a log file, and then display the updated log file information: user@host> file list lcc0-re0:/var/log/sampled detail lcc0-re0: --------------------------------------------------------------------------rw-r----- 1 root wheel 26450 Jun 23 18:47 /var/log/sampled total 1 user@host> clear log lcc0-re0:sampled lcc0-re0: -------------------------------------------------------------------------user@host> file list lcc0-re0:/var/log/sampled detail lcc0-re0: --------------------------------------------------------------------------rw-r----- 1 root wheel 57 Sep 15 03:44 /var/log/sampled total 1 360 Chapter 27: Operational Mode Commands for Configuration Management clear system commit Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields clear system commit Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear any pending commit operation. This command has no options. maintenance (or the actual user who scheduled the commit) • show system commit on page 381 clear system commit on page 361 clear system commit (None Pending) on page 361 clear system commit (User Does Not Have Required Privilege Level) on page 361 When you enter this command, you are provided feedback on the status of your request. clear system commit user@host> clear system commit Pending commit cleared. clear system commit (None Pending) user@host> clear system commit No commit scheduled. clear system commit (User Does Not Have Required Privilege Level) user@host> clear system commit error: Permission denied 361 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file archive Syntax Release Information Description Options file archive destination destination source source Command introduced before Junos OS Release 10.2 for J-EX Series switches. Archive, and optionally compress, one or multiple local system files as a single file, locally or at a remote location. destination destination—Destination of the archived file or files. Specify the destination as a URL or filename. The Junos OS adds one of the following suffixes if the destination filename does not already have it: • For archived files—The suffix .tar • For archived and compressed files—The suffix .tgz source source—Source of the original file or files. Specify the source as a URL or filename. compress—(Optional) Compress the archived file with the GNU zip (gzip) compression utility. The compressed files have the suffix .tgz. Required Privilege Level List of Sample Output Output Fields file archive (Multiple Files) maintenance file archive (Multiple Files) on page 362 file archive (Single File) on page 362 file archive (with Compression) on page 363 When you enter this command, you are provided feedback on the status of your request. The following sample command archives all message files in the local directory /var/log/messages as the single file messages-archive.tar in the same directory: user@host> file archive source /var/log/messages* destination /var/log/messages-archive.tar /usr/bin/tar: Removing leading / from absolute path names in the archive. user@host> file archive (Single File) The following sample command archives one message file in the local directory /var/log/messages as the single file messages-archive.tar in the same directory: user@host> file archive source /var/log/messages destination /var/log/messages-archive.tar /usr/bin/tar: Removing leading / from absolute path names in the archive. user@host 362 Chapter 27: Operational Mode Commands for Configuration Management file archive (with Compression) The following sample command archives and compresses all message files in the local directory /var/log/messages as the single file messages-archive.tgz in the same directory: user@host> file archive compress source /var/log/messages* destination /var/log/messages-archive.tgz /usr/bin/tar: Removing leading / from absolute path names in the archive. user@host> 363 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file checksum md5 Syntax Release Information Description Options file checksum md5 filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Calculate the Message Digest 5 (MD5) checksum of a file. pathname—(Optional) Path to a filename. filename—Name of a local file for which to calculate the MD5 checksum. Required Privilege Level Related Documentation List of Sample Output Output Fields file checksum md5 364 maintenance • Configuring Checksum Hashes for a Commit Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Event Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Op Script in the Junos OS Configuration and Diagnostic Automation Guide • Executing an Op Script from a Remote Site in the Junos OS Configuration and Diagnostic Automation Guide • file checksum sha-256 on page 366 • file checksum sha1 on page 365 • op on page 207 file checksum md5 on page 364 When you enter this command, you are provided feedback on the status of your request. user@host> file checksum md5 jbundle-5.3R2.4-export-signed.tgz MD5 (jbundle-5.3R2.4-export-signed.tgz) = 2a3b69e43f9bd4893729cc16f505a0f5 Chapter 27: Operational Mode Commands for Configuration Management file checksum sha1 Syntax Release Information Description Options file checksum sha1 filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Calculate the Secure Hash Algorithm (SHA-1) checksum of a file. pathname—(Optional) Path to a filename. filename—Name of a local file for which to calculate the SHA-1 checksum. Required Privilege Level Related Documentation List of Sample Output Output Fields file checksum sha1 maintenance • Configuring Checksum Hashes for a Commit Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Event Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Op Script in the Junos OS Configuration and Diagnostic Automation Guide • Executing an Op Script from a Remote Site in the Junos OS Configuration and Diagnostic Automation Guide • file checksum md5 on page 364 • file checksum sha-256 on page 366 • op on page 207 file checksum sha1 on page 365 When you enter this command, you are provided feedback on the status of your request. user@host> file checksum sha1 /var/db/scripts/opscript.slax SHA1 (/var/db/scripts/commitscript.slax) = ba9e47120c7ce55cff29afd73eacd370e162c676 365 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file checksum sha-256 Syntax file checksum sha-256 filename Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Calculate the Secure Hash Algorithm 2 family (SHA-256) checksum of a file. Options pathname—(Optional) Path to a filename. filename—Name of a local file for which to calculate the SHA-256 checksum. Required Privilege Level Related Documentation List of Sample Output Output Fields file checksum sha-256 maintenance • Configuring Checksum Hashes for a Commit Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Event Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Op Script in the Junos OS Configuration and Diagnostic Automation Guide • Executing an Op Script from a Remote Site in the Junos OS Configuration and Diagnostic Automation Guide • file checksum md5 on page 364 • file checksum sha1 on page 365 • op on page 207 file checksum sha-256 on page 366 When you enter this command, you are provided feedback on the status of your request. user@host> file checksum sha-256 /var/db/scripts/commitscript.slax SHA256 (/var/db/scripts/commitscript.slax) = 94c2b061fb55399e15babd2529453815601a602b5c98e5c12ed929c9d343dd71 366 Chapter 27: Operational Mode Commands for Configuration Management file compare Syntax Release Information Description file compare (files filename filename) < context | unified> Command introduced before Junos OS Release 10.2 for J-EX Series switches. Compare two local files and describe the differences between them in default, context, or unified output styles: • Default—In the first line of output, c means lines were changed between the two files, d means lines were deleted between the two files, and a means lines were added between the two files. The numbers preceding this alphabetical marker represent the first file, and the lines after the alphabetical marker represent the second file. A left angle bracket (<) in front of output lines refers to the first file. A right angle bracket (>) in front of output lines refers to the second file. • Context—Display is divided into two parts. The first part is the first file; the second part is the second file. Output lines preceded by an exclamation point (!) have changed. Additions are marked with a plus sign (+), and deletions are marked with a minus sign (-). • Unified—Display is preceded by the line number from the first and the second file (xx,xxx,x). Before the line number, additions to the file are marked with a plus sign (+), and deletions to the file are marked with a minus sign (-). The body of the output contains the affected lines. Changes are viewed as additions plus deletions. Options files filename—Names of two local files to compare. context—(Optional) Display output in context format. ignore-white-space—(Optional) Ignore changes in amount of white space. unified—(Optional) Display output in unified format. Required Privilege Level List of Sample Output Output Fields none file compare files on page 368 file compare files context on page 368 file compare files unified on page 368 file compare files unified ignore-white-space on page 369 When you enter this command, you are provided feedback on the status of your request. 367 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 368 file compare files user@host> file compare files /tmp/one /tmp/two 100c100 < full-name "File 1"; --> full-name "File 2"; 102c102 < class foo; # 'foo' is not defined --> class super-user; file compare files context user@host> file compare files /tmp/one /tmp/two context *** /tmp/one Wed Dec 3 17:12:50 2003 --- /tmp/two Wed Dec 3 09:13:14 2003 *************** *** 97,104 **** } } user bill { ! full-name "Bill Smith"; ! class foo; # 'foo' is not defined authentication { encrypted-password SECRET; } --- 97,105 ---} } user bill { ! full-name "Bill Smith"; ! uid 1089; ! class super-user; authentication { encrypted-password SECRET; } file compare files unified user@host> file compare files /tmp/one /tmp/two unified --- /tmp/one Wed Dec 3 17:12:50 2003 +++ /tmp/two Wed Dec 3 09:13:14 2003 @@ -97,8 +97,9 @@ } } user bill { full-name "Bill Smith"; class foo; # 'foo' is not defined + full-name "Bill Smith"; + uid 1089; + class super-user; authentication { encrypted-passwordSECRET; } Chapter 27: Operational Mode Commands for Configuration Management file compare files unified ignore-white-space user@host> file compare files /tmp/one /tmp/two unified ignore-white-space --- /tmp/one Wed Dec 3 09:13:10 2003 +++ /tmp/two Wed Dec 3 09:13:14 2003 @@ -99,7 +99,7 @@ user bill { full-name "Bill Smith"; uid 1089; class foo; # 'foo' is not defined + class super-user; authentication { encrypted-password ; # SECRET-DATA } 369 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file copy Syntax Release Information Description Options file copy source destination Command introduced before Junos OS Release 10.2 for J-EX Series switches. Copy files from one place to another on the local router or switch or between the local router or switch and a remote system. source—Source of the original file. Specify this as a URL or filename. destination—Destination of the copied file. Specify this as a URL or filename. If you are copying a file to the current directory (your home directory on the local router or switch) and are not renaming the file, specify the destination with a period (.). source-address address—(Optional) Source IP host address. This option is useful for specifying the source address of a secure copy (scp) file transfer. Required Privilege Level List of Sample Output Output Fields file copy (A File from the Router to a PC) maintenance file copy (A File from the Router to a PC) on page 370 file copy (A Configuration File Between Routing Engines) on page 370 file copy (A Log File Between Routing Engines) on page 370 When you enter this command, you are provided feedback on the status of your request. user@host> file copy /var/tmp/rpd.core.4 berry:/c/junipero/tmp ...transferring.file...... | file copy (A Configuration File Between Routing Engines) file copy (A Log File Between Routing Engines) 370 0 KB | 0.3 kB/s | ETA: 00:00:00 | 100% The following sample command copies a configuration file from Routing Engine 0 to Routing Engine 1: user@host> file copy /config/juniper.conf re1:/var/tmp/copied-juniper.conf The following sample command copies a log file from Routing Engine 0 to Routing Engine 1: user@host> file copy lcc0-re0:/var/log/chassisd lcc0-re1:/var/tmp Chapter 27: Operational Mode Commands for Configuration Management file delete Syntax Release Information Description Options file delete filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Delete a file on the local router or switch. filename—Name of the file to delete. For a routing matrix, include chassis information in the filename if the file to be deleted is not local to the Routing Engine from which the command is issued. purge—(Optional) Overwrite regular files before deleting them. Required Privilege Level List of Sample Output Output Fields file delete maintenance file delete on page 371 file delete (Routing Matrix) on page 371 When you enter this command, you are provided feedback on the status of your request. user@host> file list /var/tmp dcd.core rpd.core snmpd.core user@host> file delete /var/tmp/snmpd.core user@host> file list /var/tmp dcd.core rpd.core file delete (Routing Matrix) user@host> file list lcc0-re0:/var/tmp dcd.core rpd.core snmpd.core user@host> file delete lcc0-re0:/var/tmp/snmpd.core user@host> file list /var/tmp dcd.core rpd.core 371 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file list Syntax Release Information Description Options file list Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a list of files on the local router or switch. none—Display a list of all files for the current directory. detail | recursive—(Optional) Display detailed output or descend recursively through the directory hierarchy, respectively. filename—(Optional) Display a list of files. For a routing matrix, the filename must include the chassis information. Additional Information Required Privilege Level List of Sample Output Output Fields file list 372 The default directory is the home directory of the user logged into the router or switch. To view available directories, enter a space and then a backslash (/) after the file list command. To view files within a specific directory, include a backslash followed by the directory and, optionally, subdirectory name after the file list command. maintenance file list on page 372 When you enter this command, you are provided feedback on the status of your request. user@host> file list /var/tmp dcd.core rpd.core snmpd.core Chapter 27: Operational Mode Commands for Configuration Management file rename Syntax Release Information Description Options file rename source destination Command introduced before Junos OS Release 10.2 for J-EX Series switches. Rename a file on the local router or switch. destination—New name for the file. source—Original name of the file. For a routing matrix, the filename must include the chassis information. Required Privilege Level List of Sample Output Output Fields file rename maintenance file rename on page 373 When you enter this command, you are provided feedback on the status of your request. The following example lists the files in /var/tmp, renames one of the files, and then displays the list of files again to reveal the newly named file. user@host> file list /var/tmp dcd.core rpd.core snmpd.core user@host> file rename /var/tmp/dcd.core /var/tmp/dcd.core.990413 user@host> file list /var/tmp dcd.core.990413 rpd.core snmpd.core 373 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 374 Chapter 27: Operational Mode Commands for Configuration Management file show Syntax Release Information Description Options file show filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the contents of a file. filename—Name of a file. For a routing matrix, the filename must include the chassis information. encoding base64—(Optional) Encode file contents. Required Privilege Level List of Sample Output Output Fields file show maintenance file show on page 375 When you enter this command, you are provided feedback on the status of your request. user@host> file show /var/log/messages Apr 13 21:00:08 romney /kernel: so-1/1/2: loopback suspected; going to standby. Apr 13 21:00:40 romney /kernel: so-1/1/2: loopback suspected; going to standby. Apr 13 21:02:48 romney last message repeated 4 times Apr 13 21:07:04 romney last message repeated 8 times Apr 13 21:07:13 romney /kernel: so-1/1/0: Clearing SONET alarm(s) RDI-P Apr 13 21:07:29 romney /kernel: so-1/1/0: Asserting SONET alarm(s) RDI-P ... 375 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request system configuration rescue delete Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields request system configuration rescue delete 376 request system configuration rescue delete Command introduced before Junos OS Release 10.2 for J-EX Series switches. Delete an existing rescue configuration. This command has no options. maintenance • request system configuration rescue save on page 377 • request system software rollback on page 113 • show system commit on page 381 request system configuration rescue delete on page 376 This command produces no output. user@host> request system configuration rescue delete Chapter 27: Operational Mode Commands for Configuration Management request system configuration rescue save Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields request system configuration rescue save request system configuration rescue save Command introduced before Junos OS Release 10.2 for J-EX Series switches. Save the most recently committed configuration as the rescue configuration so that you can return to it at any time by using the rollback command. This command has no options. maintenance • request system software delete on page 111 • request system software rollback on page 113 • show system commit on page 381 request system configuration rescue save on page 377 This command produces no output. user@host> request system configuration rescue save 377 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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: 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from commit file config.txt url http://host1.juniper.net on page 378 request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> 378 Chapter 27: Operational Mode Commands for Configuration Management 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: 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from event file config.txt url http://host1.juniper.net on page 379 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> 379 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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: op 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from op file config.txt url http://host1.juniper.net on page 380 request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> 380 Chapter 27: Operational Mode Commands for Configuration Management show system commit Syntax show system commit Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the pending commit operation (if any) and the commit history. Options This command has no options. Required Privilege Level view Related Documentation • List of Sample Output clear system commit on page 361 show system commit on page 382 show system commit (At a Particular Time) on page 382 show system commit (At the Next Reboot) on page 382 show system commit (Rollback Pending) on page 382 Output Fields Table 54 on page 381 describes the output fields for the show system commit command. Output fields are listed in the approximate order in which they appear. Table 54: show system commit Output Fields Field Name Field Description Commit History Displays the last 50 commit operations listed, most recent to first. The identifier rescue designates a configuration created for recovery using the request system configuration rescue save command. Timestamp Date and time of the commit operation. User name User who executed the commit operation Commit method Method used to execute the commit operation: • cli—CLI interactive user performed the commit operation. • junoscript—Junos XML protocol client performed the commit operation. • synchronize—The commit synchronize command was performed on the other Routing Engine. • snmp—An SNMP SET request caused the commit operation. • button—A button on the router or switch was pressed to commit a rescue configuration for recovery. • autoinstall—A configuration obtained through autoinstallation was committed. • other—A method other than those identified was used to perform the commit operation. 381 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system commit user@host> show system commit 0 2003-07-28 19:14:04 PDT by root via other 1 2003-07-25 22:01:36 PDT by regress via cli 2 2003-07-25 22:01:32 PDT by regress via cli 3 2003-07-25 21:30:13 PDT by root via button 4 2003-07-25 13:46:48 PDT by regress via cli 5 2003-07-25 05:33:21 PDT by root via autoinstall ... rescue 2002-05-10 15:32:03 PDT by root via other show system commit (At a Particular Time) user@host> show system commit commit requested by root via cli at Tue May show system commit (At the Next Reboot) user@host> show system commit commit requested by root via cli at reboot show system commit (Rollback Pending) user@host> show system commit 0 2005-01-05 15:00:37 PST by root via cli commit confirmed, rollback in 3mins 382 7 15:59:00 2002 Chapter 27: Operational Mode Commands for Configuration Management show system configuration archival Syntax Release Information Description Options Required Privilege Level show system configuration archival Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display directory and number of files queued for archival transfer. This command has no options. maintenance List of Sample Output show system configuration archival on page 383 show system configuration archival user@host> show system configuration archival /var/transfer/config/: total 8 383 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system configuration rescue Syntax Release Information Description Options Required Privilege Level List of Sample Output show system configuration rescue 384 show system configuration rescue Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a rescue configuration, if one exists. This command has no options. maintenance show system configuration rescue on page 384 user@host> show system configuration rescue version "7.3"; groups { global { system { host-name router1; domain-name customer.net; domain-search [ customer.net ]; backup-router 192.168.124.254; name-server { 172.17.28.11; 172.17.28.101; 172.17.28.100; 172.17.28.10; } login { user regress { uid 928; class ; shell csh; authentication { encrypted-password "$1$kPU..$w.4FGRAGanJ8U4Yq6sbj7."; ## SECRET-DATA } } } services { ftp; rlogin; rsh; telnet; } } } .... Chapter 27: Operational Mode Commands for Configuration Management show system rollback Syntax Release Information Description Options show system rollback number Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the contents of a previously committed configuration, or the differences between two previously committed configurations. number—Number of a configuration to view. The output displays the configuration. The range of values is 0 through 49. compare number —(Optional) Number of another previously committed (rollback) configuration to compare to rollback number. The output displays the differences between the two configurations. The range of values is 0 through 49. Required Privilege Level view List of Sample Output show system rollback compare on page 385 show system rollback compare user@host> show system rollback 3 compare 1 [edit] + interfaces { + ge-1/1/1 { + unit 0 { + family inet { + filter { + input mf_plp; + } + address 14.1.1.1/30; + } + } + } + ge-1/2/1 { + unit 0 { + family inet { + filter { + input mf_plp; + } + address 13.1.1.1/30; + } + } + } + ge-1/3/0 { + unit 0 { + family inet { + filter { + input mf_plp; + } + address 12.1.1.1/30; + } + } 385 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS + +} 386 } Chapter 27: Operational Mode Commands for Configuration Management test configuration Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields test configuration test configuration filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Verify that the syntax of a configuration file is correct. If the configuration contains any errors, a message is displayed to indicate the line number and column number in which the error was found. filename—Name of the configuration file. view test configuration on page 387 When you enter this command, you are provided feedback on the status of your request. user@host> test configuration terminal [Type ^D to end input] system { host-name bluesky; paris-23; login; } terminal:3:(8) syntax error: paris [edit system] 'paris-23;' syntax error terminal:4:(11) statement must contain additional statements: ; [edit system login] 'login ;' statement must contain additional statements configuration syntax failed 387 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 388 PART 8 User and Access Management on J-EX Series Switches • User and Access Management on J-EX Series Switches Overview on page 391 • User Access Management Configuration on page 395 • Monitoring Users on page 401 • Troubleshooting User Access Management on page 405 • Configuration Statements for User and Access Management on page 409 • Operational Mode Commands for User and Access Management on page 433 389 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 390 CHAPTER 28 User and Access Management on J-EX Series Switches Overview • J-EX Series Switch Software Features Overview on page 391 • Understanding Software Infrastructure and Processes on page 392 J-EX Series Switch Software Features Overview The following tables list the J-EX Series Switches software features and the Junos OS Release in which they were introduced: Related Documentation • Table 4 on page 4—Access Control Features • Table 5 on page 4—Administration Features • Table 6 on page 4—Class-of-Service (CoS) Features • Table 7 on page 5—High Availability and Resiliency Features • Table 8 on page 6—Interfaces Features • Table 9 on page 7—IP Address Management Features • Table 10 on page 7—IPv6 Features • Table 11 on page 7—Layer 2 Network Protocols Features • Table 12 on page 8—Layer 3 Protocols Features • Table 13 on page 9—MPLS Features • Table 14 on page 10—Multicast Features • Table 15 on page 10—Network Management and Monitoring Features • Table 16 on page 11—Port Security Features • Table 17 on page 12—System Management Features • High Availability Features for J-EX Series Switches Overview on page 18 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 14 • J-EX4200 Switches Hardware Overview on page 25 391 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • J-EX8208 Switch Hardware Overview on page 27 • J-EX8216 Switch Hardware Overview on page 30 Understanding Software Infrastructure and Processes Each switch runs the Junos OS for J-EX Series Switches on its general-purpose processors. The 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 392 • Junos OS Processes on page 392 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. • 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. 392 Chapter 28: User and Access Management on J-EX Series Switches Overview Table 55 on page 393 describes the primary Junos OS processes. Table 55: 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 Related Documentation Defines how routing protocols such as RIP, OSPF, and BGP operate on the device, including selecting routes and maintaining forwarding tables. • For more information about processes, see the Junos OS Network Operations Guide at http://www.juniper.net/techpubs/software/junos/. • For more information about basic system parameters, supported protocols, and software processes, see Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. 393 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 394 CHAPTER 29 User Access Management Configuration • Configuring Management Access for the J-EX Series Switch (J-Web Procedure) on page 395 • Generating SSL Certificates to Be Used for Secure Web Access on page 398 • Configuring MS-CHAPv2 to Provide Password-Change Support (CLI Procedure) on page 399 Configuring Management Access for the J-EX Series Switch (J-Web Procedure) You can manage a J-EX Series switch remotely through the J-Web interface. To communicate with the switch, the J-Web interface uses Hypertext Transfer Protocol (HTTP). HTTP allows easy Web access but no encryption. The data that is transmitted between the Web browser and the switch by means of HTTP is vulnerable to interception and attack. To enable secure Web access the switch supports HTTP over Secure Sockets Layer (HTTPS). You can enable HTTP or HTTPS access on specific interfaces and ports as needed. Navigate to the Secure Access Configuration page by selecting Configure > System Properties > Management Access. On this page, you can enable HTTP and HTTPS access on interfaces for managing the J-EX Series switch through the J-Web interface. You can also install SSL certificates and enable Junos XML management protocol over SSL with the Secure Access page. 1. Click Edit to modify the configuration. Enter information into the Management Access Configuration page as described in Table 56 on page 396. 2. To verify that Web access is enabled correctly, connect to the switch using the appropriate method: • For HTTP access—In your Web browser, type http://URL or http://IP address. • For HTTPS access—In your Web browser, type https://URL or https://IP address. • For SSL Junos XML management protocol access—To use this option, you must have a Junos XML management protocol client such as Junos Scope. For information about how to log into Junos Scope, see the Junos Scope Software User Guide. 395 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 334 for details about all commit options. Table 56: Secure Management Access Configuration Summary Field Function Your Action Management Access tab Management Port IP/Management Port IPv6 Specifies the management port IP address. The software supports both IPv4 ( displayed as IP) and IPv6 address. NOTE: IPv6 is not supported on EX 4500 switches. To specify an IPv4 address: 1. Select the check box IPv4 address. 2. Type an IP address—for example: 10.10.10.10. 3. Enter the subnet mask or address prefix. For example, 24 bits represents 255.255.255.0. 4. Click OK. To specify an IPv6 address: 1. Select the check box IPv6 address. 2. Type an IP address—for example:2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. 4. Click OK. Default Gateway Defines a default gateway through which to direct packets addressed to networks that are not explicitly listed in the bridge table constructed by the switch. For IPv4 address type a 32-bit IP address, in dotted decimal notation. Type a 128-bit IP address for IPv6 address type. Loopback address Specifies the IP address of the loopback interface. Type an IP address. Subnet Mask Specifies the subnet mask for the loopback interface. Enter the subnet mask or address prefix. Services Specifies services to be enabled: telnet and SSH. Select to enable the required services. Enable Junos XML management protocol over Clear Text Enables clear text access to the Junos XML management protocol XML scripting API. To enable clear text access, select the Enable Junos XML management protocol over Clear Text check box. Enable Junos XML protocol over SSL Enables secure SSL access to the Junos XML management protocol XML scripting API. To enable SSL access, select the Enable Junos XML management protocol over SSL check box. Services tab 396 Chapter 29: User Access Management Configuration Table 56: Secure Management Access Configuration Summary (continued) Field Function Your Action Junos XML management protocol Certificate Specifies SSL certificates to be used for encryption. To enable an SSL certificate, select a certificate from the Junos XML management protocol SSL Certificate list—for example, new. This field is available only after you create at least one SSL certificate. Enable HTTP Enables HTTP access on interfaces. To enable HTTP access, select the Enable HTTP access check box. Select and clear interfaces by clicking the direction arrows: • Enable HTTPS Enables HTTPS access on interfaces. To enable HTTP access on an interface, add the interface to the HTTP Interfaces list. You can either select all interfaces or specific interfaces. To enable HTTPS access, select the Enable HTTPS access check box. Select and deselect interfaces by clicking the direction arrows: • To enable HTTPS access on an interface, add the interface to the HTTPS Interfaces list. You can either select all interfaces or specific interfaces. NOTE: Specify the certificate to be used for HTTPS access. Certificates tab Certificates Displays digital certificates required for SSL access to the switch. To add a certificate: 1. Allows you to add and delete SSL certificates. Have a general SSL certificate available. See Generating SSL Certificates for more information. 2. Click Add. The Add a Local Certificate page opens. 3. Type a name in the Certificate Name box—for example, new. 4. Open the certificate file and copy its contents. 5. Paste the generated certificate and RSA private key in the Certificate box. To edit a certificate, select it and click Edit. To delete a certificate, select it and click Delete. Related Documentation • Security Features for J-EX Series Switches Overview on page 16 397 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Understanding J-Web User Interface Sessions on page 133 Generating SSL Certificates to Be Used for Secure Web Access You can set up secure Web access for a J-EX Series switch. To enable secure Web access, you must generate a digital Secure Sockets Layer (SSL) certificate and then enable HTTPS access on the switch. To generate an SSL certificate: 1. Enter the following openssl command in your SSH command-line interface on a BSD or Linux system on which openssl is installed. The openssl command generates a self-signed SSL certificate in the privacy-enhanced mail (PEM) format. It writes the certificate and an unencrypted 1024-bit RSA private key to the specified file. % openssl req –x509 –nodes –newkey rsa:1024 –keyout filename.pem -out filename.pem where filename is the name of a file in which you want the SSL certificate to be written—for example, my-certificate. 2. When prompted, type the appropriate information in the identification form. For example, type US for the country name. 3. Display the contents of the file that you created. cat my-certificate.pem You can use the J-Web Configuration page to install the SSL certificate on the switch. To do this, copy the file containing the certificate from the BSD or Linux system to the switch. Then open the file, copy its contents, and paste them into the Certificate box on the J-Web Secure Access Configuration page. You can also use the following CLI statement to install the SSL certificate on the switch: [edit] user@switch# set security certificates local my-signed-cert load-key-file my-certificate.pem Related Documentation 398 • Configuring Management Access for the J-EX Series Switch (J-Web Procedure) on page 395 • Security Features for J-EX Series Switches Overview on page 16 Chapter 29: User Access Management Configuration Configuring MS-CHAPv2 to Provide Password-Change Support (CLI Procedure) Junos OS for J-EX Series switches enables you to configure the Microsoft Corporation implementation of the Challenge Handshake Authentication Protocol version 2 (MS-CHAPv2) on the switch to provide password-change support. Configuring MS-CHAPv2 on the switch provides users accessing a switch the option of changing the password when the password expires, is reset, or is configured to be changed at next login. See RFC 2433 at , Microsoft PPP CHAP Extensions, for information about MS-CHAP. Before you configure MS-CHAPv2 to provide password-change support, ensure that you have: • Configured RADIUS server authentication. Configure users on the authentication server and set the first-tried option in the authentication order to radius. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. To configure MS-CHAPv2, specify the following: [edit system radius-options] user@switch# set password-protocol mschap-v2 You must have the required access permission on the switch in order to change your password. Related Documentation • Managing Users (J-Web Procedure) on page 401 • For more about configuring user access, see the Junos OS Access Privilege Configuration Guide at http://www.juniper.net/techpubs/software/junos/. 399 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 400 CHAPTER 30 Monitoring Users • Managing Users (J-Web Procedure) on page 401 Managing Users (J-Web Procedure) You can use the Users Configuration page for user information to add new users to a J-EX Series switch. For each account, you define a login name and password for the user and specify a login class for access privileges. To configure users: 1. Select Configure > System Properties > User Management. The User Management page displays details of users, the authentication order, the RADIUS servers and TACACS servers present. 2. Click Edit. 3. Click any of the following options on the Users tab: • Add—Select this option to add a user. Enter details as described in Table 57 on page 402. • Edit—Select this option to edit an existing user's details. Enter details as described in Table 57 on page 402. • Delete—Select this option to delete a user. 4. Click an option on the Authentication Methods and Order tab: • Authentication Order—Drag and drop the authentication type from the Available Methods section to the Selected Methods. Click the up or down buttons to modify the authentication order. • RADIUS server—Click one: • Add—Select this option to add an authentication server. Enter details as described in Table 58 on page 403. • Edit—Select this option to modify the authentication server details. Enter details as described in Table 58 on page 403. • Delete—Select this option to delete an authentication server from the list. 401 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • TACACS server—Click one: • Add—Select this option to add an authentication server. Enter details as described in Table 58 on page 403. • Edit—Select this option to modify the authentication server details. Enter details as described in Table 58 on page 403. • Delete—Select this option to delete an authentication server from the list. 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 334 for details about all commit options. Table 57: User Management Configuration Page Summary Field Function Your Action Username (required) Specifies the name that identifies the user. Type the username. It must be unique within the switching platform. Do not include spaces, colons, or commas in the username. User Id Specifies the user identification. Type the user’s ID. Full Name Specifies the user's full name. Type the user's full name. If the full name contains spaces, enclose it in quotation marks. Do not include colons or commas. Login Class (required) Defines the user's access privilege. Select the user's login class from the list: User Information • operator • read-only • super-user/superuser • unauthorized This list also includes any user-defined login classes. Password Confirm Password 402 Specifies the login password for this user. Verifies the login password for this user. Type the login password for this user. The login password must meet these criteria: • The password must be at least 6 characters long. • It can include alphabetic, numeric, and special characters, but not control characters. • It must contain at least one change of case or character class. Retype the login password for this user. Chapter 30: Monitoring Users Table 58: Add an Authentication Server Field Function Your Action IP Address Specifies the IP address of the server. Type the server’s 32-bit IP address, in dotted decimal notation. Password Specifies the password of the server. Type the password of the server. Confirm Password Verifies that the password of the server is entered correctly. Retype the password of the server. Server Port Specifies the port with which the server is associated. Type the port number. Source Address Specifies the source address of the server. Type the server’s 32-bit IP address, in dotted decimal notation. Retry Attempts Specifies the number of login retries allowed after a login failure. Type the number. NOTE: Only 1 retry is permitted for a TACACS server. Time out Related Documentation Specifies the time interval to wait before the connection to the server is closed. • Type the interval in seconds. Configuring Management Access for the J-EX Series Switch (J-Web Procedure) on page 395 403 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 404 CHAPTER 31 Troubleshooting User Access Management • Troubleshooting Loss of the Root Password on page 405 Troubleshooting Loss of the Root Password Problem If you forget the root password for the switch, you can use the password recovery procedure to reset the root password. NOTE: You need physical access to the switch to recover the root password. Solution To recover the root password: 1. Power off your switch by unplugging the power cord or turning off the power at the wall switch. 2. Insert one end of the Ethernet cable into the serial port on the management device and connect the other end to the console port on the back of the switch. See Figure 6 on page 405 Figure 6: Connecting to the Console Port on the J-EX Series Switch 3. On the management device, start your asynchronous terminal emulation application (such as Microsoft Windows Hyperterminal) and select the appropriate COM port to use (for example, COM1). 405 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 4. Configure the port settings as follows: • Bits per second: 9600 • Data bits: 8 • Parity: None • Stop bits: 1 • Flow control: None 5. Power on your switch by plugging in the power cord or turning on the power at the wall switch. 6. When the following prompt appears, press the Spacebar to access the switch's bootstrap loader command prompt: Hit [Enter] to boot immediately, or space bar for command prompt. Booting [kernel] in 1 second... 7. At the following prompt, type boot -s to start up the system in single-user mode: loader> boot -s 8. At the following prompt, type recovery to start the root password recovery procedure: Enter full path name of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery A series of messages describe consistency checks, mounting of filesystems, and initialization and checkout of management services. Then the CLI prompt appears. 9. Enter configuration mode in the CLI: user@switch> configure 10. Set the root password. For example: user@switch# set system root-authentication plain-text-password 11. At the following prompt, enter the new root password. For example: New password: juniper1 Retype new password: 12. At the second prompt, reenter the new root password. 13. If you are finished configuring the network, commit the configuration. root@switch# commit commit complete 14. Exit configuration mode in the CLI. root@switch# exit 15. Exit operational mode in the CLI. root@switch> exit 16. At the prompt, enter y to reboot the switch. Reboot the system? [y/n] y 406 Chapter 31: Troubleshooting User Access Management Related Documentation • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 • For information about configuring an encrypted root password, configuring SSH keys to authenticate root logins, and configuring special requirements for plain-text passwords, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. 407 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 408 CHAPTER 32 Configuration Statements for User and Access Management allow-commands Syntax Hierarchy Level Release Information Description allow-commands "regular-expression"; [edit system login class class-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the operational mode commands that members of a login class can use. Default If you omit this statement and the deny-commands statement, users can issue only those commands for which they have access privileges through the permissions statement. Options regular-expression—Extended (modern) regular expression as defined in POSIX 1003.2. If the regular expression contains any spaces, operators, or wildcard characters, enclose it in quotation marks. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Specifying Access Privileges for Junos OS Operational Mode Commands • deny-commands on page 415 • user on page 432 409 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS allow-configuration Syntax Hierarchy Level Release Information Description allow-configuration "regular-expression"; [edit system login class class-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the configuration mode commands that members of a login class can use. Default If you omit this statement and the deny-configuration statement, users can issue only those commands for which they have access privileges through the permissions statement. Options regular-expression—Extended (modern) regular expression as defined in POSIX 1003.2. If the regular expression contains any spaces, operators, or wildcard characters, enclose it in quotation marks. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Specifying Access Privileges for Junos OS Configuration Mode Commands • Regular Expressions for Allowing and Denying Junos OS Configuration Mode Commands • deny-commands on page 415 • user on page 432 announcement Syntax Hierarchy Level Release Information announcement text; [edit system login] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure a system login announcement. This announcement appears after a user logs in. Options text—Text of the announcement. If the text contains any spaces, enclose it in quotation marks. Required Privilege Level Related Documentation 410 system—To view this statement in the configuration. system-control—To add this statement to the configuration • Configuring the Junos OS to Display a System Login Announcement • message on page 421 Chapter 32: Configuration Statements for User and Access Management authentication (Login) Syntax Hierarchy Level Release Information Description Options authentication { (encrypted-password "password" | plain-text-password); ssh-dsa "public-key"; ssh-rsa "public-key"; } [edit system login user username] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Authentication methods that a user can use to log in to the router or switch. You can assign multiple authentication methods to a single user. encrypted-password "password"—Message Digest 5 (MD5) or other encrypted authentication. Specify the MD5 or other password. You can specify only one encrypted password for each user. You cannot configure a blank password for encrypted-password using blank quotation marks (" "). You must configure a password whose number of characters range from 1 through 128 characters and enclose the password in quotation marks. plain-text-password—Plain-text password. The command-line interface (CLI) prompts you for the password and then encrypts it. ssh-dsa "public-key"—SSH version 2 authentication. Specify the SSH public key. You can specify one or more public keys for each user. ssh-rsa "public-key"—SSH version 1 and SSH version 2 authentication. Specify the SSH public key. You can specify one or more public keys for each user. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Junos OS User Accounts • root-authentication on page 426 411 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-order Syntax Hierarchy Level Release Information authentication-order [ authentication-methods ]; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the order in which the software tries different user authentication methods when attempting to authenticate a user. For each login attempt, the software tries the authentication methods in order, starting with the first one, until the password matches. Default If you do not include the authentication-order statement, users are verified based on their configured passwords. Options authentication-methods—One or more authentication methods, listed in the order in which they should be tried. The method can be one or more of the following: • password—Use the password configured for the user with the authentication statement at the [edit system login user] hierarchy level. Required Privilege Level Related Documentation 412 • radius—Use RADIUS authentication services. • tacplus—Use TACACS+ authentication services. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS Authentication Order for RADIUS, TACACS+, and Local Password Authentication • authentication on page 411 Chapter 32: Configuration Statements for User and Access Management change-type Syntax Hierarchy Level Release Information Description Options change-type (character-sets | set-transitions); [edit system login password] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set requirements for using character sets in plain-text passwords. When you combine this statement with the minimum-changes statement, you can check for the total number of character sets included in the password or for the total number of character-set changes in the password. Newly created passwords must meet these requirements. Specify one of the following: • character-sets—The number of character sets in the password. Valid character sets include uppercase letters, lowercase letters, numbers, punctuation, and other special characters. • Required Privilege Level Related Documentation set-transitions—The number of transitions between character sets. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Special Requirements for Junos OS Plain-Text Passwords • minimum-changes on page 422 class (Assigning a Class to an Individual User) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation class class-name; [edit system login user username] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a user’s login class. You must configure one class for each user. class-name—One of the classes defined at the [edit system login class] hierarchy level. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Junos OS User Accounts 413 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS class (Defining Login Classes) Syntax Hierarchy Level Release Information Description Options class class-name { allow-commands "regular-expression"; allow-configuration "regular-expression"; deny-commands "regular-expression"; deny-configuration "regular-expression"; idle-timeout minutes; permissions [ permissions ]; } [edit system login] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a login class. class-name—A name you choose for the login class. The remaining statements are explained separately. Required Privilege Level Related Documentation 414 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Defining Junos OS Login Classes • user on page 432 Chapter 32: Configuration Statements for User and Access Management deny-commands Syntax Hierarchy Level Release Information Description deny-commands "regular-expression"; [edit system login class] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the operational mode commands that the user is denied permission to issue even though the permissions set with the permissions statement would allow it. Default If you omit this statement and the allow-commands statement, users can issue only those commands for which they have access privileges through the permissions statement. Options regular-expression—Extended (modern) regular expression as defined in POSIX 1003.2. If the regular expression contains any spaces, operators, or wildcard characters, enclose it in quotation marks. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Specifying Access Privileges for Junos OS Operational Mode Commands • allow-commands on page 409 • user on page 432 415 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS deny-configuration Syntax Hierarchy Level Release Information Description deny-configuration "regular-expression"; [edit system login class] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the configuration mode commands that the user is denied permission to issue even though the permissions set with the permissions statement would allow it. Default If you omit this statement and the allow-configuration statement, users can issue only those commands for which they have access privileges through the permissions statement. Options regular-expression—Extended (modern) regular expression as defined in POSIX 1003.2. If the regular expression contains any spaces, operators, or wildcard characters, enclose it in quotation marks. Required Privilege Level Related Documentation 416 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Specifying Access Privileges for Junos OS Operational Mode Commands • allow-configuration on page 410 • user on page 432 Chapter 32: Configuration Statements for User and Access Management format Syntax Hierarchy Level Release Information Description format (des | md5 | sha1); [edit system login password] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the authentication algorithm for plain-text passwords. Default For the Junos OS, the default encryption format is md5. For Junos-FIPS software, the default encryption format is sha1. Options The hash algorithm that authenticates the password can be one of three algorithms: Required Privilege Level Related Documentation • des—Has a block size of 8 bytes; its key size is 48 bits long. • md5—Produces a 128-bit digest. • sha1—Produces a 160-bit digest. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Special Requirements for Junos OS Plain-Text Passwords full-name Syntax Hierarchy Level Release Information Description Options full-name complete-name; [edit system login user] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the complete name of a user. complete-name—Full name of the user. If the name contains spaces, enclose it in quotation marks. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Junos OS User Accounts 417 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS idle-timeout Syntax Hierarchy Level Release Information idle-timeout minutes; [edit system login class class-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description For a login class, configure the maximum time that a session can be idle before the user is logged off the router or switch. The session times out after remaining at the CLI operational mode prompt for the specified time. Default If you omit this statement, a user is never forced off the system after extended idle times. Options minutes—Maximum idle time. Range: 0 through 100,000 minutes Required Privilege Level Related Documentation 418 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Timeout Value for Idle Login Sessions • user on page 432 Chapter 32: Configuration Statements for User and Access Management login Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation login { announcement text; class class-name { allow-commands "regular-expression"; allow-configuration "regular-expression"; deny-commands "regular-expression"; deny-configuration "regular-expression"; idle-timeout minutes; login-tip; permissions [ permissions ]; } message text; password { change-type (set-transitions | character-set); format (md5 | sha1 | des); maximum-length length; minimum-changes number; minimum-length length; } retry-options { backoff-threshold number; backoff-factor seconds; minimum-time seconds; tries-before-disconnect number; } user username { full-name complete-name; uid uid-value; class class-name; authentication authentication; (encrypted-password "password" | plain-text-password); ssh-rsa "public-key"; ssh-dsa "public-key"; } } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure user access to the router or switch. The remaining statements are explained separately. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Defining Junos OS Login Classes 419 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS login-alarms Syntax Hierarchy Level Release Information Description Required Privilege Level login-alarms; [edit system login class admin] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Show system alarms automatically when an admin user logs on to the router. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. login-tip Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 420 login-tip; [edit system login class class-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable CLI tips at login. Disabled. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring CLI Tips Chapter 32: Configuration Statements for User and Access Management maximum-length Syntax Hierarchy Level Release Information Description Default Options maximum-length length; [edit system login passwords] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the maximum number of characters allowed in plain-text passwords. Newly created passwords must meet this requirement. For Junos-FIPS software, the maximum number of characters for plain-text passwords is 20. For Junos OS, no maximum is set. length—The maximum number of characters the password can include. Range: 1 to 64 characters Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Special Requirements for Junos OS Plain-Text Passwords message Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation message text; [edit system login] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a system login message. This message appears before a user logs in. text—Text of the message. system—To view this statement in the configuration. system-control—To add this statement to the configuration • Configuring the Junos OS to Display a System Login Message • announcement on page 410 421 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS minimum-changes Syntax Hierarchy Level Release Information Description minimum-changes number; [edit system login passwords] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the minimum number of character sets (or character set changes) required in plain-text passwords. Newly created passwords must meet this requirement. This statement is used in combination with the change-type statement. If the change-type is character-sets, then the number of character sets included in the password is checked against the specified minimum. If change-type is set-transitions, then the number of character set changes in the password is checked against the specified minimum. Default For Junos OS, the minimum number of changes is 1. For Junos-FIPS Software, the minimum number of changes is 3. Options number—The minimum number of character sets (or character set changes) required for the password. Required Privilege Level Related Documentation 422 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Special Requirements for Junos OS Plain-Text Passwords • change-type on page 413 Chapter 32: Configuration Statements for User and Access Management minimum-length Syntax Hierarchy Level Release Information Description Default Options minimum-length length; [edit system login passwords] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the minimum number of characters required in plain-text passwords. Newly created passwords must meet this requirement. For Junos OS, the minimum number of characters for plain-text passwords is six. For Junos-FIPS software, the minimum number of characters for plain-text passwords is 10. length—The minimum number of characters the password must include. Range: 6 to 20 characters Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Special Requirements for Junos OS Plain-Text Passwords • maximum-length on page 421 password (Login) Syntax Hierarchy Level Release Information Description password { change-type (set-transitions | character-set); format (md5 | sha1 | des); maximum-length length; minimum-changes number; minimum-length length; } [edit system login] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure special requirements such as character length and encryption format for plain-text passwords. Newly created passwords must meet these requirements. 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. • Special Requirements for Junos OS Plain-Text Passwords • maximum-length on page 421 423 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS permissions Syntax Hierarchy Level Release Information Description Options permissions [ permissions ]; [edit system login class] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the login access privileges to be provided on the router or switch. permissions—Privilege type. For a list of permission flag types, see Junos OS Access Privilege Levels Overview. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Access Privilege Levels • user on page 432 radius-options Syntax Hierarchy Level Release Information Description Options radius-options { attributes { nas-ip-address ip-address; } password-protocol mschap-v2; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS options for the NAS-IP address for outgoing RADIUS packets and password protocol used in RADIUS packets. ip-address—IP address of the network access server (NAS) that requests user authentication. mschap-v2—Protocol MS-CHAPv2, used for password authentication and password changing. Required Privilege Level Related Documentation 424 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication Chapter 32: Configuration Statements for User and Access Management retry-options Syntax Hierarchy Level Release Information Description Options retry-options { backoff-threshold number; backoff-factor seconds; maximum-time seconds; minimum-time seconds; tries-before-disconnect number; } [edit system login] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Maximum number of times a user can attempt to enter a password while logging in through SSH or Telnet before being disconnected. backoff-threshold number—Threshold for the number of failed login attempts before the user experiences a delay when attempting to reenter a password. Use the backoff-factor option to specify the length of delay, in seconds. Range: 1 through 3 Default: 2 backoff-factor seconds—Length of delay after each failed login attempt. The length of delay increases by this value for each subsequent login attempt after the value specified in the backoff-threshold option. Range: 5 through 10 Default: 5 maximum-time seconds—Maximum length of time that the connection remains open for the user to enter a username and password to log in. If the user remains idle and does not enter a username and password within the configured maximum-time, the connection is closed. Range: 20 through 300 Default: 120 minimum-time seconds—Minimum length of time that the connection remains open while the user is attempting to enter a password to log in. Range: 20 through 60 Default: 20 tries-before-disconnect number—Maximum number of times a user is allowed to attempt to enter a password to log in through SSH or Telnet. Range: 1 through 10 Default: 10 Required Privilege Level admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. 425 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Limiting the Number of User Login Attempts for SSH and Telnet Sessions • rate-limit on page 487 root-authentication Syntax Hierarchy Level Release Information root-authentication { (encrypted-password "password" | plain-text-password); ssh-dsa "public-key"; ssh-rsa "public-key"; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the authentication methods for the root-level user, whose username is root. Options encrypted-password "password"— MD5 or other encrypted authentication. Specify the MD5 or other password. You can specify only one encrypted password. You cannot configure a blank password for encrypted-password using blank quotation marks (" "). You must configure a password whose number of characters range from 1 through 128 characters and enclose the password in quotation marks. plain-text-password—Plain-text password. The CLI prompts you for the password and then encrypts it. The CLI displays the encrypted version, and the software places the encrypted version in its user database. You can specify only one plain-text password. ssh-dsa "public-key"—SSH version 2 authentication. Specify the DSA (SSH version 2) public key. You can specify one or more public keys. ssh-rsa "public-key"—SSH version 1 authentication. Specify the RSA (SSH version 1 and SSH version 2) public key. You can specify one or more public keys. Required Privilege Level Related Documentation 426 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Root Password • authentication on page 411 Chapter 32: Configuration Statements for User and Access Management root-login Syntax Hierarchy Level Release Information Description Default Options root-login (allow | deny | deny-password); [edit system services ssh] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Control user access through SSH. Allow user access through SSH. allow—Allow users to log in to the router or switch as root through SSH. deny—Disable users from logging in to the router or switch as root through SSH. deny-password—Allow users to log in to the router or switch as root through SSH when the authentication method (for example, RSA authentication) does not require a password. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring SSH Service for Remote Access to the Router or Switch • Configuring SSH Service for Remote Access to the Router or Switch 427 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS tacplus-options Syntax Hierarchy Level Release Information Description Options tacplus-options { service-name service-name; (no-cmd-attribute-value | exclude-cmd-attribute); } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure TACACS+ options for authentication and accounting. service-name service-name—The name of the authentication service used when configuring multiple TACACS+ servers to use the same authentication service. Default: junos-exec no-cmd-attribute-value—Set the cmd attribute value to an empty string in the TACACS+ accounting start and stop requests to enable logging of accounting records in the correct log file on a TACACS+ server. exclude-cmd-attribute—Exclude the cmd attribute value completely from start and stop accounting records to enable logging of accounting records in the correct log file on a TACACS+ server. Required Privilege Level Related Documentation 428 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring TACACS+ Authentication • Configuring TACACS+ System Accounting • Junos OS Authentication Order for RADIUS, TACACS+, and Password Authentication Chapter 32: Configuration Statements for User and Access Management tacplus-server Syntax Hierarchy Level Release Information Description Options tacplus-server server-address { secret password; single-connection; source-address source-address; timeout seconds; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the TACACS+ server. server-address—Address of the TACACS+ authentication server. 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 TACACS+ Authentication 429 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions (Address-Assignment Pool) Syntax Hierarchy Level Release Information Description Options traceoptions { file filename { files number; size maximum-file-size; match regex; ; } flag address-assignment; flag all; flag configuration; flag framework; flag ldap; flag local-authentication; flag radius; } [edit system processes general-authentication-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure tracing options. 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. 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 also must specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: 430 • address-assignment—All address-assignment events • all—All tracing operations • configuration—Configuration events • framework—Authentication framework events • ldap—LDAP authentication events • local-authentication—Local authentication events • radius—RADIUS authentication events Chapter 32: Configuration Statements for User and Access Management match regex—(Optional) Refine the output to include lines that contain the regular expression. no-world-readable—(Optional) Restrict access to the originator of the trace operation only. size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). 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. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Tracing Address-Assignment Pool Processes • Configuring Address-Assignment Pools uid Syntax Hierarchy Level Release Information Description Options uid uid-value; [edit system login user] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a user identifier for a login account. uid-value—Number associated with the login account. This value must be unique on the router or switch. Range: 100 through 64000 Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Junos OS User Accounts 431 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user (Access) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 432 user username { authentication { class class-name; (encrypted-password "password" | plain-text-password); full-name complete-name; ssh-dsa "public-key"; ssh-rsa "public-key"; uid uid-value; } } [edit system login] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure access permission for individual users. The remaining statements are explained separately. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Junos OS User Accounts • class on page 413 CHAPTER 33 Operational Mode Commands for User and Access Management 433 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request message Syntax Release Information Description Options request message all message "text" request message message "text" (terminal terminal-name | user user-name) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a message on the screens of all users who are logged in to the router or switch or on specific screens. all—Display a message on the terminal of all users who are currently logged in. message "text"—Message to display. terminal terminal-name—Name of the terminal on which to display the message. user user-name—Name of the user to whom to direct the message. Required Privilege Level List of Sample Output Output Fields request message message 434 maintenance request message message on page 434 When you enter this command, you are provided feedback on the status of your request. user@host> request message message "Maintenance window in 10 minutes" user maria Message from user@host on ttyp0 at 20:27 ... Maintenance window in 10 minutes EOF Chapter 33: Operational Mode Commands for User and Access Management show subscribers Syntax show subscribers
Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. client-type, mac-address, subscriber-state, extensive, and summary options introduced in Junos OS Release 10.2. count option usage with other options introduced in Junos OS Release 10.2 Description Options Display information for active subscribers. address—(Optional) Display subscribers whose IP address matches the specified address. client-type—(Optional) Display subscribers whose client type matches the specified client type (DHCP, L2TP, PPP, PPPOE, or VLAN). count—(Optional) Display the count of total subscribers and active subscribers for any specified option. You can use the count option alone or with the address, client-type, interface, logical-system, mac-address, profile-name, routing-instance, stacked-vlan-id, subscriber-state, and vlan-id options. interface—(Optional) Display subscribers whose interface matches the specified interface. logical system—(Optional) Display subscribers whose logical system matches the specified logical system. mac-address—(Optional) Display subscribers whose MAC address matches the specified MAC address. profile name—(Optional) Display subscribers whose dynamic profile matches the specified profile name. routing instance—(Optional) Display subscribers whose routing instance matches the specified routing instance. subscriber-state—(Optional) Display subscribers whose subscriber state matches the specified subscriber state (ACTIVE, CONFIGURED, INIT, TERMINATED, or TERMINATING). vlan-id—(Optional) Display subscribers whose VLAN ID matches the specified VLAN ID. 435 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS stacked-vlan-id—(Optional) Display subscribers whose stacked VLAN ID matches the specified stacked VLAN ID. detail | terse | extensive—(Optional) Display the specified level of output. summary—(Optional) Display summary output. NOTE: Due to display limitations, logical system and routing instance output values are truncated when necessary. Required Privilege Level List of Sample Output Output Fields view show subscribers on page 438 show subscribers detail (IPv4) on page 438 show subscribers detail (IPv6) on page 438 show subscribers logical-system on page 439 show subscribers count on page 439 show subscribers routing-instance inst1 count on page 439 show subscribers vlan-id on page 439 show subscribers vlan-id detail on page 439 show subscribers stacked-vlan-id detail on page 439 show subscribers stacked-vlan-id vlan-id detail (Combined Output) on page 439 show subscribers stacked-vlan-id vlan-id interface detail (Combined Output for a Specific Interface) on page 440 show subscribers client-type dhcp detail on page 440 show subscribers extensive on page 440 show subscribers summary on page 440 show subscribers summary all on page 441 show subscribers terse on page 441 Table 59 on page 436 lists the output fields for the show subscribers command. Output fields are listed in the approximate order in which they appear. Table 59: show subscribers Output Fields Field Name Field Description User Name Name of subscriber. Type Subscriber client type (DHCP, VLAN, PPP, PPPOE, or L2TP). IP Address Subscriber IPv4 address. IP Netmask Subscriber IP netmask. IPv6 Address Subscriber IPv6 address. IPv6 Prefix Subscriber IPv6 prefix. 436 Chapter 33: Operational Mode Commands for User and Access Management Table 59: show subscribers Output Fields (continued) Field Name Field Description IPv6 Prefix Length Length of the subscriber IPv6 prefix. Logical System Logical system associated with the subscriber. Routing Instance Routing instance associated with the subscriber. Interface Interface associated with the subscriber. The router displays subscribers whose interface matches or begins with the specified interface. Interface Type Whether the subscriber interface is static or dynamic. Dynamic Profile Name Dynamic profile used for the subscriber. MAC Address MAC address associated with the subscriber. State Current state of the subscriber session (Init, Configured, Active, Terminating, Terminated). VLAN Id VLAN ID associated with the subscriber in the form tpid.vlan-id. Stacked VLAN Id Stacked VLAN ID associated with the subscriber in the form tpid.vlan-id. RADIUS Accounting ID RADIUS accounting ID associated with the subscriber. Agent Circuit ID Option 82 agent circuit ID associated with the subscriber. Agent Remote ID Option 82 agent remote ID associated with the subscriber. DHCP Relay IP Address IP address used by the DHCP relay agent. Login Time Date and time at which the subscriber logged in. Session ID ID number for a subscriber service session. Service Sessions Number of service sessions (that is, a service activated using RADIUS CoA) associated with the subscribers. Service Session Name Service session profile name. IPv4 Input Filter Name Name assigned to the IPv4 input filter (client or service session). IPv4 Output Filter Name Name assigned to the IPv4 output filter (client or service session). IPv6 Input Filter Name Name assigned to the IPv6 input filter (client or service session). IPv6 Output Filter Name Name assigned to the IPv6 output filter (client or service session). IFL Input Filter Name Name assigned to the logical interface input filter (client or service session). 437 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 59: show subscribers Output Fields (continued) Field Name Field Description IFL Output Filter Name Name assigned to the logical interface output filter (client or service session). Subscribers by State Number of subscribers summarized by state. The summary information includes the following: • Init—Number of subscriber currently in the initialization state. • Configured—Number of configured subscribers. • Active—Number of active subscribers. • Terminating—Number of subscribers currently terminating. • Terminated—Number of terminated subscribers. Summary information includes subscriber counts per state and the total number of subscribers. Subscribers by Client Type Number of subscribers summarized by client type. Client types can include DHCP, VLAN, PPP, PPPOE, and L2TP. Summary information includes subscriber counts per client type and the total number of subscribers. Subscribers by LS:RI Number of subscribers summarized by logical system:routing instance (LS:RI) combination. Summary information includes subscriber counts per LS:RI and the total number of subscribers. show subscribers 438 user@host> show subscribers Interface IP Address/VLAN ID ge-1/3/0.1073741824 100 demux0.1073741824 100.0.0.10 demux0.1073741825 101.0.0.3 demux0.1073741826 102.0.0.3 show subscribers detail (IPv4) user@host> show subscribers detail Type: DHCP IP Address: 100.20.9.7 IP Netmask: 255.255.0.0 Logical System: default Routing Instance: default Interface: demux0.1073744127 Interface type: Dynamic Dynamic Profile Name: dhcp-demux-prof MAC Address: 00:10:95:00:00:98 State: Active Radius Accounting ID: jnpr :2304 Login Time: 2009-08-25 14:43:52 PDT Service Sessions: 2 show subscribers detail (IPv6) user@host> show subscribers detail Type: DHCP IPv6 Address: 1080:0:0:0:8:800:200C:417A Ipv6 Prefix: fec0:1:1:1::/128 Logical System: default1 Routing Instance: default Interface: demux0.1073744127 Interface type: Dynamic Dynamic Profile Name: dhcp-demux-prof MAC Address: 00:10:95:00:00:98 State: Active User Name LS:RI default:default WHOLESALER-CLIENT default:default RETAILER1-CLIENT test1:retailer1 RETAILER2-CLIENT test1:retailer2 Chapter 33: Operational Mode Commands for User and Access Management Radius Accounting ID: jnpr :2304 Login Time: 2009-08-25 14:43:52 PDT Service Sessions: 2 show subscribers logical-system user@host> show subscribers logical-system test1 terse Interface IP Address/VLAN ID User Name LS:RI demux0.1073741825 101.0.0.3 RETAILER1-CLIENT test1:retailer1 demux0.1073741826 102.0.0.3 RETAILER2-CLIENT test1:retailer2 show subscribers count user@host> show subscribers count Total Subscribers: 188, Active Subscribers: 188 show subscribers routing-instance inst1 count user@host> show subscribers routing-instance inst1 count Total Subscribers: 188, Active Subscribers: 183 show subscribers vlan-id user@host> show subscribers vlan-id 100 Interface IP Address ge-1/0/0.1073741824 ge-1/2/0.1073741825 show subscribers vlan-id detail user@host> show subscribers vlan-id 100 detail Type: VLAN Interface: ge-1/0/0.1073741824 Interface type: Dynamic Dynamic Profile Name: vlan-prof-tpid State: Active VLAN Id: 100 Login Time: 2009-03-11 06:48:54 PDT User Name Type: VLAN Interface: ge-1/2/0.1073741825 Interface type: Dynamic Dynamic Profile Name: vlan-prof-tpid State: Active VLAN Id: 100 Login Time: 2009-03-11 06:48:54 PDT show subscribers stacked-vlan-id detail user@host> show subscribers stacked-vlan-id 101 detail Type: VLAN Interface: ge-1/2/0.1073741824 Interface type: Dynamic Dynamic Profile Name: svlan-prof State: Active Stacked VLAN Id: 0x8100.101 VLAN Id: 0x8100.100 Login Time: 2009-03-27 11:57:19 PDT show subscribers stacked-vlan-id vlan-id detail (Combined Output) user@host> show subscribers stacked-vlan-id 101 vlan-id 100 detail Type: VLAN Interface: ge-1/2/0.1073741824 Interface type: Dynamic Dynamic Profile Name: svlan-prof State: Active Stacked VLAN Id: 0x8100.101 VLAN Id: 0x8100.100 Login Time: 2009-03-27 11:57:19 PDT 439 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show subscribers stacked-vlan-id vlan-id interface detail (Combined Output for a Specific Interface) user@host> show subscribers stacked-vlan-id 101 vlan-id 100 interface ge-1/2/0.* detail Type: VLAN Interface: ge-1/2/0.1073741824 Interface type: Dynamic Dynamic Profile Name: svlan-prof State: Active Stacked VLAN Id: 0x8100.101 VLAN Id: 0x8100.100 Login Time: 2009-03-27 11:57:19 PDT show subscribers client-type dhcp detail user@host> show subscribers client-type dhcp detail Type: DHCP IP Address: 100.20.9.7 IP Netmask: 255.255.0.0 Logical System: default Routing Instance: default Interface: demux0.1073744127 Interface type: Dynamic Dynamic Profile Name: dhcp-demux-prof MAC Address: 00:10:95:00:00:98 State: Active Radius Accounting ID: jnpr :2304 Login Time: 2009-08-25 14:43:52 PDT Type: DHCP IP Address: 100.20.10.7 IP Netmask: 255.255.0.0 Logical System: default Routing Instance: default Interface: demux0.1073744383 Interface type: Dynamic Dynamic Profile Name: dhcp-demux-prof MAC Address: 00:10:94:00:01:f3 State: Active Radius Accounting ID: jnpr :2560 Login Time: 2009-08-25 14:43:56 PDT show subscribers extensive user@host> show subscribers extensive Type: DHCP IPv6 Prefix: 2001::40:0:0:0/74 IPv6 Prefix Length: 64 Logical System: default Routing Instance: default Interface: demux0.1073741825 Interface type: Dynamic Dynamic Profile Name: dhcp-demux-prof State: Active Radius Accounting ID: jnpr :2 Agent Circuit ID: abc Remote Circuit ID: xyz Login Time: 2010-03-31 14:27:19 PDT Service Sessions: 1 IPv6 Input Filter Name: demux0-inet6-in Session ID: 213 Service Session Name: service-profile IPv6 Input Filter Name: dfwd1-demux.1073741825-in show subscribers summary user@host> show subscribers summary Subscribers by State 440 Chapter 33: Operational Mode Commands for User and Access Management Init 3 Configured Active 183 Terminating Terminated 2 2 TOTAL 1 191 Subscribers by Client Type DHCP 107 PPP 76 VLAN 8 TOTAL show subscribers summary all 191 user@host> show subscribers summary all Subscribers by State Init 3 Configured 2 Active 183 Terminating 2 Terminated 1 TOTAL 191 Subscribers by Client Type DHCP 107 PPP 76 VLAN 8 TOTAL 191 Subscribers by LS:RI default:default 1 default:ri1 28 default:ri2 16 ls1:default 22 ls1:riA 38 ls1:riB 44 logsysX:routinstY 42 TOTAL show subscribers terse 191 user@host> show subscribers summary terse Interface IP Address/VLAN ID ge-1/3/0.1073741824 100 demux0.1073741824 100.0.0.10 demux0.1073741825 101.0.0.3 demux0.1073741826 102.0.0.3 User Name LS:RI default:default WHOLESALER-CLIENT default:default RETAILER1-CLIENT test1:retailer1 RETAILER2-CLIENT test1:retailer2 441 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 442 PART 9 Junos OS for J-EX Series Switches System Services • System Services Overview on page 445 • System Services Configuration on page 447 • Monitoring System Services on page 451 • Configuration Statements for System Services on page 455 • Operational Mode Commands for System Services on page 509 443 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 444 CHAPTER 34 System Services Overview • DHCP Overview on page 445 • DHCP Services for J-EX Series Switches Overview on page 445 • DHCP/BOOTP Relay for J-EX Series Switches Overview on page 446 DHCP Overview DHCP Services for J-EX Series Switches Overview A Dynamic Host Configuration Protocol (DHCP) server can automatically allocate IP addresses and also deliver configuration settings to client hosts on a subnet. DHCP is particularly useful for managing a pool of IP addresses among hosts. An IP address can be leased to a host for a limited period of time, allowing the DHCP server to share a limited number of IP addresses among a group of hosts that do not need permanent IP addresses. DHCP, through the use of the automatic software download feature, can also be used to install software packages on J-EX Series Switches. 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 82. To configure DHCP access service for a J-EX Series switch, you can use either the Junos OS command-line interface (CLI) or the J-Web user interface. For detailed information about configuring DHCP services, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. The configuration for DHCP service on the J-EX Series switch includes the dhcp statement at the [edit system services] hierarchy level. You can monitor DHCP services for the switch by using either operational-mode CLI commands or the J-Web interface. 445 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • For information about configuring DHCP services with the CLI, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. • Configuring DHCP Services (J-Web Procedure) on page 447 • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 • Monitoring DHCP Services on page 451 DHCP/BOOTP Relay for J-EX Series Switches Overview You can configure the J-EX Series Switch to act as a Dynamic Host Configuration Protocol (DHCP) or Bootstrap Protocol (BOOTP) relay agent. This means that a locally attached host can issue a DHCP or BOOTP request as a broadcast message. If the switch sees this broadcast message, it relays the message to a specified DHCP or BOOTP server. You should configure the switch to be a DHCP/BOOTP relay agent if you have locally attached hosts and a distant DHCP or BOOTP server. For detailed information about configuring a DHCP/BOOTP relay agent, see the Junos OS Policy Framework Configuration Guide at http://www.juniper.net/techpubs/software/junos/. You can configure a J-EX Series Switch to use the gateway IP address (giaddr) as the source IP address of the switch for relayed DHCP packets when the switch is used as the DHCP relay agent. For information on configuring this option, see the source-address-giaddr configuration statement. NOTE: Because DHCP/BOOTP messages are broadcast and are not directed to a specific server, switch, or router, J-EX Series switches cannot function as both a DHCP server and a DHCP/BOOTP relay agent at the same time. The Junos OS generates a commit error if both options are configured at the same time, and the commit will not succeed until one of the options is removed. Related Documentation 446 • For information about configuring the switch as a DHCP/BOOTP relay agent, see the Junos OS Policy Framework Configuration Guide at http://www.juniper.net/techpubs/software/junos/. • DHCP Services for J-EX Series Switches Overview on page 445 CHAPTER 35 System Services Configuration • Configuring DHCP Services (J-Web Procedure) on page 447 • Configuring a DHCP SIP Server (CLI Procedure) on page 450 Configuring DHCP Services (J-Web Procedure) Use the J-Web DHCP Configuration pages to configure DHCP pools for subnets and static bindings for DHCP clients on a J-EX Series switch. If DHCP pools or static bindings are already configured, use the Configure Global DHCP Parameters Configuration page to add settings for these pools and static bindings. Settings that have been previously configured for DHCP pools or static bindings are not overridden when you use the Configure Global DHCP Parameters Configuration page. To configure the DHCP server: 1. Select Configure > Services > DHCP. 2. Access a DHCP Configuration page: • To configure a DHCP pool for a subnet, click Add in the DHCP Pools box. • To configure a static binding for a DHCP client, click Add in the DHCP Static Binding box. • To globally configure settings for existing DHCP pools and static bindings, click Configure Global DHCP Parameters. 3. Enter information into the DHCP Configuration pages as described in Table 60 on page 448. 4. To apply the configuration, click Apply. 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 334 for details about all commit options. 447 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 60: DHCP Server Configuration Pages Summary Field Function Your Action DHCP Subnet (required) Specifies the subnet on which DHCP is configured. Type an IP address prefix. Address Range (Low) (required) Specifies the lowest address in the IP address pool range. Type an IP address that is part of the subnet specified in DHCP Subnet. Address Range (High) (required) Specifies the highest address in the IP address pool range. Type an IP address that is part of the subnet specified in DHCP Subnet. This address must be greater than the address specified in Address Range (Low). Exclude Addresses Specifies addresses to exclude from the IP address pool. • To add an excluded address, type the address next to the Add button, and click Add. • To delete an excluded address, select the address in the Exclude Addresses box, and click Delete. DHCP Pool Information Lease Time Maximum Lease Time (Seconds) Specifies the maximum length of time a client can hold a lease. (Dynamic BOOTP lease lengths can exceed this maximum time.) Type a number from 60 through 4,294,967,295 (seconds). You can also type infinite to specify a lease that never expires. Default Lease Time (Seconds) Specifies the length of time a client can hold a lease for clients that do not request a specific lease length. Type a number from 60 through 2,147,483,647 (seconds). You can also type infinite to specify a lease that never expires. Server Identifier Specifies the IP address of the DHCP server reported to a client. Type the IP address of the server. If you do not specify a server identifier, the primary address of the interface on which the DHCP exchange occurs is used. Domain Name Specifies the domain name that clients must use to resolve hostnames. Type the name of the domain. Domain Search Specifies the order—from top to bottom—in which clients must append domain names when resolving hostnames using DNS. • To add a domain name, type the name next to the Add button, and click Add. • To delete a domain name, select the name in the Domain Search box, and click Delete. Defines a list of DNS servers the client can use, in the specified order—from top to bottom. • To add a DNS server, type an IP address next to the Add button, and click Add. • To remove a DNS server, select the IP address in the DNS Name Servers box, and click Delete. Server Information DNS Name Servers 448 Chapter 35: System Services Configuration Table 60: DHCP Server Configuration Pages Summary (continued) Field Function Your Action Gateway Routers Defines a list of relay agents on the subnet, in the specified order—from top to bottom. • To add a relay agent, type an IP address next to the Add button, and click Add. • To remove a relay agent, select the IP address in the Gateway Routers box, and click Delete. • To add a NetBIOS name server, type an IP address next to the Add button, and click Add. • To remove a NetBIOS name server, select the IP address in the WINS Servers box, and click Delete. WINS Servers Defines a list of NetBIOS name servers, in the specified order—from top to bottom. Boot Options Boot File Specifies the path and filename of the initial boot file to be used by the client. Type a path and filename. Boot Server Specifies the TFTP server that provides the initial boot file to the client. Type the IP address or hostname of the TFTP server. DHCP Static Binding Information DHCP MAC Address (required) Specifies the MAC address of the client to be permanently assigned a static IP address. Type the hexadecimal MAC address of the client. Fixed IP Addresses (required) Defines a list of IP addresses permanently assigned to the client. A static binding must have at least one fixed address assigned to it, but multiple addresses are also allowed. • To add an IP address, type it next to the Add button, and click Add. • To remove an IP address, select it in the Fixed IP Addresses box, and click Delete. Host Name Specifies the name of the client used in DHCP messages exchanged between the server and the client. The name must be unique to the client within the subnet on which the client resides. Type a client hostname. Client Identifier Specifies the name of the client used by the DHCP server to index its database of address bindings. The name must be unique to the client within the subnet on which the client resides. Type a client identifier in string form. Hexadecimal Client Identifier Specifies the name of the client, in hexadecimal form, used by the DHCP server to index its database of address bindings. The name must be unique to the client within the subnet on which the client resides. Type a client identifier in hexadecimal form. Related Documentation • DHCP Services for J-EX Series Switches Overview on page 445 • Monitoring DHCP Services on page 451 449 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring a DHCP SIP Server (CLI Procedure) You can use the sip-server statement on the J-EX Series switch to configure option 120 on a DHCP server. The DHCP server sends configured option values—Session Initiation Protocol (SIP) server addresses or names—to DHCP clients when they request them. Previously, you were only allowed to specify a SIP server by address using [edit system services dhcp option 120]. You specify either an IPv4 address or a fully qualified domain name to be used by SIP clients to locate a SIP server. You cannot specify both an address and name in the same statement. To configure a SIP server using the address option: [edit system services dhcp] user@switch# set sip-server address For example, to configure one address: [edit system services dhcp] user@switch set sip-server 172.168.0.11 To configure a SIP server using the name option: [edit system services dhcp] user@switch# set sip-server name For example, to configure a name: [edit system services dhcp] user@switch set sip-server abc.example.com Related Documentation • DHCP Services for J-EX Series Switches Overview on page 445 • Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 450 CHAPTER 36 Monitoring System Services • Monitoring DHCP Services on page 451 Monitoring DHCP Services Purpose Action A switch or router can operate as a DHCP server. Use the monitoring functionality to view information about dynamic and static DHCP leases, conflicts, pools, and statistics. To monitor the DHCP server in the J-Web interface, select Monitor > Services > DHCP. To monitor the DHCP server in the CLI, enter the following CLI commands: Meaning • show system services dhcp binding • show system services dhcp conflict • show system services dhcp pool • show system services dhcp statistics • show system services dhcp relay-statistics • show system services dhcp global • show system services dhcp client Table 61 on page 452 summarizes the output fields in DHCP displays in the J-Web interface. 451 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 61: Summary of DHCP Output Fields Field Values Additional Information Global tab Name Value This column displays the following information: • Boot lease length • Domain Name • Name servers • Server identifier • Domain search • Gateway routers • WINS server • Boot file • Boot server • Default lease time • Minimum lease time • Maximum lease time Displays the value for each of the parameters in the Name column. Bindings tab Allocated Address List of IP addresses the DHCP server has assigned to clients. MAC Address Corresponding media access control (MAC) address of the client. Binding Type Type of binding assigned to the client: dynamic or static. Lease Expires Date and time the lease expires, or never for leases that do not expire. Pools tab Pool Name Subnet on which the IP address pool is defined. Low Address Lowest address in the IP address pool. High Address Highest address in the IP address pool. Excluded Addresses Addresses excluded from the address pool. Clients tab 452 DHCP servers can assign a dynamic binding from a pool of IP addresses or a static binding to one or more specific IP addresses. Chapter 36: Monitoring System Services Table 61: Summary of DHCP Output Fields (continued) Field Values Interface Name Name of the logical interface. Hardware Address Vendor identification. Status State of the client binding. Address Obtained IP address obtained from the DHCP server. Update Server Indicates whether server update is enabled. Lease Obtained Date and time the lease was obtained. Lease Expires Date and time the lease expires. Renew Reacquires an IP address from the server for the interface. When you click this option, the command sends a discover message if the client state is INIT and a renew request message if the client state is BOUND. For all other states it performs no action. Release Clears other resources received earlier from the server, and reinitializes the client state to INIT for the particular interface. Additional Information Conflicts tab Detection Time Date and time the client detected the conflict. Detection Method How the conflict was detected. Only client-detected conflicts are displayed. Address IP address where the conflict occurs. The addresses in the conflicts list remain excluded until you use the clear system services dhcp conflict command to manually clear the list. DHCP Statistics Relay Statistics tab Packet Counters Displays the number of packet counters. Dropped Packet Counters Graphically displays the number of dropped packet counters. 453 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 61: Summary of DHCP Output Fields (continued) Field Values Additional Information Statistics tab Packets dropped Total number of packets dropped and the number of packets dropped due to a particular condition. Messages received Number of BOOTREQUEST, DHCPDECLINE, DHCPDISCOVER, DHCPINFORM, DHCPRELEASE, and DHCPREQUEST messages sent from DHCP clients and received by the DHCP server. Messages sent Number of BOOTREPLY, DHCPACK, DHCPOFFER, and DHCPNAK messages sent from the DHCP server to DHCP clients. Related Documentation 454 • Configuring DHCP Services (J-Web Procedure) on page 447 • DHCP Services for J-EX Series Switches Overview on page 445 CHAPTER 37 Configuration Statements for System Services boot-file Syntax Hierarchy Level Release Information Description Options boot-file filename; [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Set the boot file advertised to DHCP clients. After the client receives an IP address and the boot file location from the DHCP server, the client uses the boot image stored in the boot file to complete DHCP setup. filename—The location of the boot file on the boot server. The filename can include a pathname. 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, Switch, or Interface to Act as a DHCP Server on J Series Services Routers and J-EX Series Switches • boot-server on page 456 455 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS boot-server (DHCP) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 456 boot-server address; [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Configure the name of the boot server advertised to DHCP clients. The client uses a boot file located on the boot server to complete DHCP setup. address—Address of a boot server. You must specify an IPv4 address, not a hostname. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • boot-file on page 455 Chapter 37: Configuration Statements for System Services bootp Syntax Hierarchy Level Release Information Description bootp { client-response-ttl number; description text-description; interface interface-group { client-response-ttl number; description text-description; maximum-hop-count number; minimum-wait-time seconds; no-listen; server address { ; } } maximum-hop-count number; minimum-wait-time seconds; server address { ; } } [edit forwarding-options helpers] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configures a router, switch, or interface to act as a Dynamic Host Configuration Protocol (DHCP) or bootstrap protocol (BOOTP) relay agent. DHCP relaying is disabled. Options Required Privilege Level Related Documentation The remaining statements are explained separately. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 457 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ca-name Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation ca-name ca-identity; [edit security certificates certification-authority] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Specify the certificate authority (CA) identity to use in the certificate request. ca-identity—CA identity to use in the certificate request. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Digital Certificates for an ES PIC cache-size Syntax Hierarchy Level Release Information Description Options cache-size bytes; [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Configure the cache size for digital certificates. bytes—Cache size for digital certificates. Range: 64 through 4,294,967,295 Default: 2 megabytes (MB) NOTE: We recommend that you limit your cache size to 4 MB. Required Privilege Level Related Documentation 458 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration • Configuring Digital Certificates for an ES PIC Chapter 37: Configuration Statements for System Services cache-timeout-negative Syntax Hierarchy Level Release Information Description Options cache-timeout-negative seconds; [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Configure a negative cache for digital certificates. seconds—Negative time to cache digital certificates, in seconds. Range: 10 through 4,294,967,295 Default: 20 CAUTION: Configuring a large negative cache value can lead to a denial-of-service attack. Required Privilege Level admin—To view this statement in the configuration. admin-control—To add this statement to the configuration 459 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS certificates Syntax Hierarchy Level Release Information Description certificates { cache-size bytes; cache-timeout-negative seconds; certification-authority ca-profile-name { ca-name ca-identity; crl file-name; encoding (binary | pem); enrollment-url url-name; file certificate-filename; ldap-url url-name; } enrollment-retry attempts; local certificate-name { certificate-key-string; load-key-file URL-or-path; } maximum-certificates number; path-length certificate-path-length; } [edit security] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface J-EX Series switches) Configure the digital certificates for IPsec. The remaining statements are explained separately. Required Privilege Level 460 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. Chapter 37: Configuration Statements for System Services certification-authority Syntax Hierarchy Level Release Information Description certification-authority ca-profile-name { ca-name ca-identity; crl file-name; encoding (binary | pem); enrollment-url url-name; file certificate-filename; ldap-url url-name; } [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Configure a certificate authority profile name. The remaining statements are explained separately. Required Privilege Level admin—To view this statement in the configuration. admin-control—To add this statement to the configuration client-identifier Syntax Hierarchy Level Release Information client-identifier (ascii client-id | hexadecimal client-id); [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description For J-EX Series switches only. Configure the client’s unique identifier. This identifier is used by the DHCP server to index its database of address bindings. Either a client identifier or the client’s MAC address is required to uniquely identify the client on the network. Options client-id—A name or number that uniquely identifies the client on the network. The client identifier can be an ASCII string or hexadecimal digits. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. 461 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS connection-limit Syntax Hierarchy Level Release Information Description Options connection-limit limit; [edit system services finger], [edit system services ftp], [edit system services ssh], [edit system services telnet], [edit system services xnm-clear-text], [edit system services xnm-ssl] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the maximum number of established connections for each type of system service (finger, ftp, ssh, telnet, xnm-clear-text, or xnm-ssl) for each IP protocol, such as IPv6 and IPv4. limit—(Optional) Maximum number of established connections. Range: 1 through 250 Default: 75 Required Privilege Level Related Documentation 462 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring clear-text or SSL Service for Junos XML Management Protocol Client Applications • Configuring DTCP-over-SSH Service for the Flow-Tap Application • Configuring Finger Service for Remote Access to the Router • Configuring FTP Service for Remote Access to the Router or Switch • Configuring SSH Service for Remote Access to the Router or Switch • Configuring Telnet Service for Remote Access to a Router Chapter 37: Configuration Statements for System Services crl (Encryption Interface) Syntax Hierarchy Level Release Information Description Options Required Privilege Level crl file-name; [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Configure the certificate revocation list (CRL). A CRL is a time-stamped list identifying revoked certificates, which is signed by a CA and made available to the participating IPsec peers on a regular periodic basis. file-name—Specify the file from which to read the CRL. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration default-lease-time Syntax Hierarchy Level Release Information Description Options default-lease-time seconds; [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Specify the length of time in seconds that a client holds the lease for an IP address assigned by a DHCP server. This setting is used if a lease time is not requested by the client. seconds—Number of seconds the lease can be held. Default: 86400 (1day) Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • maximum-lease-time on page 479 463 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS description Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 464 description text-description; [edit forwarding-options helpers bootp], [edit forwarding-options helpers bootpinterface interface-group], [edit forwarding-options helpers domain], [edit forwarding-options helpers domain interface interface-name], [edit forwarding-options helpers tftp], [edit forwarding-options helpers tftpinterface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Describe a BOOTP, DHCP, Domain Name System (DNS), or Trivial File Transfer Protocol (TFTP) service, or an interface that is configured for the service. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding • Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents Chapter 37: Configuration Statements for System Services dhcp Syntax Hierarchy Level Release Information Description dhcp { boot-file filename; boot-server (address | hostname); default-lease-time seconds; domain-name domain-name; domain-search [domain-list]; maximum-lease-time seconds; name-server { address; } option { [ (id-number option-type option-value) | (id-number array option-type option-value) ]; } pool address/prefix-length { address-range { low address; high address; } exclude-address { address; } } router { address; } static-binding mac-address { fixed-address { address; } host hostname; client-identifier (ascii client-id | hexadecimal client-id); } server-identifier address; wins-server { address; } } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Configure a router, switch, or interface as a DHCP server. A DHCP server can allocate network addresses and deliver configuration information to client hosts on a TCP/IP network. The remaining statements are explained separately. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. 465 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • System Management Configuration Statements domain Syntax Hierarchy Level Release Information Description domain { description text-description; interface interface-name { broadcast; description text-description; no-listen; server address ; } server address ; } [edit forwarding-options helpers] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable DNS request packet forwarding. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding domain-name (DHCP) Syntax Hierarchy Level Release Information Description Options 466 domain-name domain-name; [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches only. Configure the name of the domain in which clients search for a DHCP server host. This is the default domain name that is appended to hostnames that are not fully qualified. domain-name—Name of the domain. Chapter 37: Configuration Statements for System Services domain-search Syntax Hierarchy Level Release Information Description Options domain-search [ domain-list ]; [edit system], [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a list of domains to be searched. domain-list—A list of domain names to search. The list can contain up to six domain names, with a total of up to 256 characters. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Domains to Search When a Router or Switch Is Included in Multiple Domains encoding Syntax Hierarchy Level Release Information Description Options encoding (binary | pem); [edit security ike policy ike-peer-address], [edit security certificates certification-authority ca-profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Specify the file format used for the local-certificate and local-key-pair statements. binary—Binary file format. pem—Privacy-enhanced mail (PEM), an ASCII base 64 encoded format. Default: binary Required Privilege Level admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. 467 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS enrollment-retry Syntax Hierarchy Level Release Information Description Options enrollment-retry attempts; [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Specify how many times a router or switch can resend a digital certificate request. attempts—Number of enrollment retries. Range: 0 through 100 Default: 0 Required Privilege Level admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. enrollment-url Syntax Hierarchy Level Release Information Description Options Required Privilege Level 468 enrollment-url url-name; [edit security certificates certification-authority ca-profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Specify where your router or switch sends Simple Certificate Enrollment Protocol-based (SCEP-based) certificate enrollment requests (certificate authority URL). url-name—Certificate authority URL. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. Chapter 37: Configuration Statements for System Services file Syntax Hierarchy Level Release Information Description Options Required Privilege Level file certificate-filename; [edit security certificates certification-authority ca-profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Specify the file from which to read the digital certificate. certificate-filename—File from which to read the digital certificate. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. ftp Syntax Hierarchy Level Release Information Description Options Required Privilege Level ftp { connection-limit limit; rate-limit limit; } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Allow FTP requests from remote systems to the local router or switch. The remaining statements are explained separately. system—To view this statement in the configuration. system-control—To add this statement to the configuration. 469 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS helpers Syntax 470 helpers { bootp { client-response-ttl number; description text-description; interface interface-group { client-response-ttl number; description text-description; maximum-hop-count number; minimum-wait-time seconds; no-listen; server address { ; } } maximum-hop-count number; minimum-wait-time seconds; server address { ; } } domain { description text-description; interface interface-name { broadcast; description text-description; no-listen; server address ; } server address ; } port port-number { description text-description; interface interface-name { broadcast; description text-description; no-listen; server address ; } server address ; } tftp { description text-description; interface interface-name { broadcast; description text-description; no-listen; Chapter 37: Configuration Statements for System Services server address ; } server address ; } traceoptions { file filename ; flag flag; level level; no-remote-trace level; } } Hierarchy Level Release Information Description [edit forwarding-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable TFTP or DNS request packet forwarding, or configure the router, switch, or interface to act as a DHCP/BOOTP relay agent. Use only one server address per interface or global configuration. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding 471 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS http Syntax Hierarchy Level Release Information Description Options http { interfaces [ interface-names ]; port port; } [edit system services web-management] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the port and interfaces for HTTP service, which is unencrypted. interfaces [ interface-names ]—Name of one or more interfaces on which to allow the HTTP service. By default, HTTP access is allowed through built-in Fast Ethernet or Gigabit Ethernet interfaces only. The remaining statement is explained separately. Required Privilege Level Related Documentation 472 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring Management Access for the J-EX Series Switch (J-Web Procedure) on page 395 • J-Web Interface User Guide • https on page 473 • port on page 486 • web-management on page 506 Chapter 37: Configuration Statements for System Services https Syntax Hierarchy Level Release Information Description Options https { interfaces [ interface-names ]; local-certificate name; port port; } [edit system services web-management] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the secure version of HTTP (HTTPS) service, which is encrypted. interfaces [ interface-names]—Name of one or more interfaces on which to allow the HTTPS service. By default, HTTPS access is allowed through any ingress interface, but HTTP access is allowed through built-in Fast Ethernet or Gigabit Ethernet interfaces only. local-certificate name—Name of the X.509 certificate for a Secure Sockets Layer (SSL) connection. An SSL connection is configured at the [edit security certificates local] hierarchy. 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 Management Access for the J-EX Series Switch (J-Web Procedure) on page 395 • J-Web Interface User Guide • http on page 472 • port on page 486 • web-management on page 506 473 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface (BOOTP) Syntax Hierarchy Level Release Information Description Options interface interface-group { client-response-ttl number; description text-description; maximum-hop-count number; minimum-wait-time seconds; no-listen; server address { ; } } [edit forwarding-options helpers bootp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the interface for a DHCP and BOOTP relay agent. interface-group—Sets a logical interface or group of logical interfaces with a specific DHCP relay configuration. The remaining statements are explained separately. Required Privilege Level Related Documentation 474 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 Chapter 37: Configuration Statements for System Services interface (DNS and TFTP Packet Forwarding or Relay Agent) Syntax Hierarchy Level Release Information Description Options interface interface-name { broadcast; description text-description; no-listen; server address ; } [edit forwarding-options helpers domain], [edit forwarding-options helpers tftp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the interface for monitoring and forwarding DNS or TFTP requests. interface-name—Name of the interface. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding ldap-url Syntax Hierarchy Level Release Information Description Options Required Privilege Level ; [edit security certificates certification-authority ca-profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches ) (Optional) Specify the Lightweight Directory Access Protocol (LDAP) URL for digital certificates. url-name—Name of the LDAP URL. system—To view this statement in the configuration. system-control—To add this statement to the configuration. 475 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS load-key-file Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 476 load-key-file; [edit system root-authentication], [edit system login user username authentication] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Load RSA (SSH version 1 and SSH version 2) and DSA (SSH version 2) public keys from a file. The file is a URL containing one or more SSH keys. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Root Password • Configuring Junos OS User Accounts Chapter 37: Configuration Statements for System Services local Syntax Hierarchy Level Release Information Description Options local certificate-name { certificate-key-string; load-key-file URL-or-path; } [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Import a paired X.509 private key and authentication certificate, to enable Junos XML management protocol client applications to establish Secure Sockets Layer (SSL) connections to the router or switch. certificate-key-string—String of alphanumeric characters that constitute the private key and certificate. certificate-name—Name that uniquely identifies the certificate. load-key-file URL-or-path—File that contains the private key and certificate. It can be one of two types of values: Required Privilege Level Related Documentation • Pathname of a file on the local disk (assuming you have already used another method to copy the certificate file to the router’s or switch’s local disk) • URL to the certificate file location (for instance, on the computer where the Junos XML management protocol client application runs) system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Importing SSL Certificates for Junos XML Management Protocol Support 477 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS local-certificate Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation local-certificate; [edit system services service-deployment], [edit system services web-management https], [edit system services xnm-ssl] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Import or reference an SSL certificate. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring clear-text or SSL Service for Junos XML Management Protocol Client Applications • Generating SSL Certificates to Be Used for Secure Web Access on page 398 • Importing SSL Certificates for Junos XML Management Protocol Support maximum-certificates Syntax Hierarchy Level Release Information Description Options maximum-certificates number; [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches ) Configure the maximum number of peer digital certificates to be cached. number—Maximum number of peer digital certificates to be cached. Range: 64 through 4,294,967,295 peer certificates Default: 1024 peer certificates Required Privilege Level 478 system—To view this statement in the configuration. system-control—To add this statement to the configuration. Chapter 37: Configuration Statements for System Services maximum-hop-count Syntax Hierarchy Level Release Information Description Options maximum-hop-count number; [edit forwarding-options helpers bootp], [edit forwarding-options helpers bootpinterface interface-group] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the maximum number of hops allowed. number—Maximum number of hops. Default: 4 hops Required Privilege Level interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. maximum-lease-time Syntax Hierarchy Level Release Information Description maximum-lease-time seconds; [edit system services dhcp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches. Specify the maximum length of time in seconds for which a client can request and hold a lease on a DHCP server. An exception is that the dynamic BOOTP lease length can exceed the maximum lease length specified. Options Required Privilege Level Related Documentation seconds—The maximum number of seconds the lease can be held. system—To view this statement in the configuration. system-control—To add this statement to the configuration • default-lease-time on page 463 479 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS minimum-wait-time Syntax Hierarchy Level Release Information Description Options minimum-wait-time seconds; [edit forwarding-options helpers bootp], [edit forwarding-options helpers bootpinterface interface-group] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the minimum time allowed. seconds—Minimum time. Default: 0 seconds Required Privilege Level interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. name-server Syntax Hierarchy Level Release Information Description Options name-server { address; } [edit system], [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure one or more Domain Name System (DNS) name servers. address—Address of the name server. To configure multiple name servers, include multiple address options. Required Privilege Level Related Documentation 480 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring a DNS Name Server for Resolving a Hostname into Addresses Chapter 37: Configuration Statements for System Services no-listen Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-listen; [edit forwarding-options helpers bootp interfaceinterface-group], [edit forwarding-options helpers domain interface interface-name], [edit forwarding-options helpers tftp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable recognition of DNS requests or stop packets from being forwarded on a logical interface, a group of logical interfaces, a router, or a switch. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding 481 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS outbound-ssh Syntax Hierarchy Level Release Information [edit system services] outbound-ssh { client client-id { address { port port-number; retry number; timeout seconds; } device-id device-id; keep-alive { retry number; timeout seconds; } reconnect-strategy (in-order | sticky); secret password; services netconf; } traceoptions { file filename ; flag flag; no-remote-trace; } } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure a router or switch running the Junos OS behind a firewall to communicate with client management applications on the other side of the firewall. Default To configure transmission of the router’s or switch’s device ID to the application, include the device-id statement at the [edit system services] hierarchy level. Options client-id—Identifies the outbound-ssh configuration stanza on the router or switch. Each outbound-ssh stanza represents a single outbound SSH connection. This attribute is not sent to the client. device-id—Identifies the router or switch to the client during the initiation sequence. keep-alive—(Optional) When configured, specifies that the router or switch send keepalive messages to the management server. To configure the keepalive message, you must set both the timeout and retry attributes. reconnect-strategy—(Optional) Specify the method the router or switch uses to reestablish a disconnected outbound SSH connection. Two methods are available: • in-order—Specify that the router or switch first attempt to establish an outbound SSH session based on the management server address list. The router or switch attempts 482 Chapter 37: Configuration Statements for System Services to establish a session with the first server on the list. If this connection is not available, the router or switch attempts to establish a session with the next server, and so on down the list until a connection is established. • sticky—Specify that the router or switch first attempt to reconnect to the management server that it was last connected to. If the connection is unavailable, it attempts to establish a connection with the next client on the list and so forth until a connection is made. retry—Number of keepalive messages the router or switch sends without receiving a response from the client before the current SSH connection is disconnected. The default is three messages. secret—(Optional) Router’s or switch’s public SSH host key. If added to the outbound-ssh statement, during the initialization of the outbound SSH service, the router or switch passes its public key to the management server. This is the recommended method of maintaining a current copy of the router’s or switch’s public key. timeout—Length of time that the Junos OS server waits for data before sending a keep alive signal. The default is 15 seconds. When reconnecting to a client, the router or switch attempts to reconnect to the client based on the retry and timeout values for each client listed. address—Hostname or the IPv4 address of the NSM application server. You can list multiple clients by adding each client’s IP address or hostname along with the following connection parameters: • port—Outbound SSH port for the client. The default is port 22. • retry—Number of times the router or switch attempts to establish an outbound SSH connection before giving up. The default is three tries. • timeout—Length of time that the router or switch attempts to establish an outbound SSH connection before giving up. The default is fifteen seconds. filename—(Optional) By default, the filename of the log file used to record the trace options is the name of the traced process (for example, mib2d or snmpd). Use this option to override the default value. files—(Optional) Maximum number of trace files generated. By default, the maximum number of trace files is 10. Use this option to override the default value. When a trace file reaches its maximum size, the system archives the file and starts a new file. The system archives trace files by appending a number to the filename in sequential order from 1 to the maximum value (specified by the default value or the options value set here). Once the maximum value is reached, the numbering sequence is restarted at 1, overwriting the older file. size—(Optional) Maximum size of the trace file in kilobytes (KB). Once the maximum file size is reached, the system archives the file. The default value is 1000 KB. Use this option to override the default value. 483 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS match—(Optional) When used, the system only adds lines to the trace file that match the regular expression specified. For example, if the match value is set to =error, the system only records lines to the trace file that include the string error. services—Services available for the session. Currently, NETCONF is the only service available. world-readable | no-world-readable—(Optional) Whether the files are accessible by the originator of the trace operation only or by any user. By default, log files are only accessible by the user that started the trace operation (no-world-readable). all | configuration | connectivity—(Optional) Type of tracing operation to perform. all—Log all events. configuration—Log all events pertaining to the configuration of the router or switch. connectivity—Log all events pertaining to the establishment of a connection between the client server and the router or switch. no-remote-trace—(Optional) Disable remote tracing. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Outbound SSH Service • System Management Configuration Statements path-length Syntax Hierarchy Level Release Information Description Options path-length certificate-path-length; [edit security certificates] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Configure the digital certificate path length. certificate-path-length—Digital certificate path length. Range: 2 through 15 certificates Default: 15 certificates Required Privilege Level 484 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. Chapter 37: Configuration Statements for System Services pool Syntax pool address/prefix-length { address-range { low address; high address; } exclude-address { address; } } Hierarchy Level [edit system services dhcp] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description For J-EX Series switches . Configure a pool of IP addresses for DHCP clients on a subnet. When a client joins the network, the DHCP server dynamically allocates an IP address from this pool. Options address-range—Lowest and highest IP addresses in the pool that are available for dynamic address assignment. If no range is specified, the pool will use all available addresses within the subnet specified. (Broadcast addresses, interface addresses, and excluded addresses are not available.) exclude-address—Addresses within the range that are not used for dynamic address assignment. You can exclude one or more addresses within the range. The remaining statements are explained separately. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. 485 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS port (HTTP/HTTPS) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation port port-number; [edit system services web-management] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the port on which the HTTP or HTTPS service is connected. port-number—The TCP port number on which the specified service listens. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Table 56 on page 396 • J-Web Interface User Guide • http on page 472 • https on page 473 • web-management on page 506 port (SRC Server) Syntax Hierarchy Level Release Information Description Options port port-number; [edit system services service-deployment servers server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the port number on which to contact the SRC server. port-number—(Optional) The TCP port number for the SRC server. Default: 3333 Required Privilege Level Related Documentation 486 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Work with SRC Software Chapter 37: Configuration Statements for System Services protocol-version Syntax Hierarchy Level Release Information Description Options protocol-version version; [edit system services ssh] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the secure shell (SSH) protocol version. version—SSH protocol version Values: v1, u2, or [ v1 v2 ] Default: [v1 v2] Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring SSH Service for Remote Access to the Router or Switch rate-limit Syntax Hierarchy Level Release Information Description Options rate-limit limit; [edit system services finger], [edit system services ftp], [edit system services ssh], [edit system services telnet], [edit system services xnm-clear-text], [edit system services xnm-ssl] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Maximum number of connection attempts on an access service. rate-limit limit—(Optional) Maximum number of connection attempts allowed per minute. Range: 1 through 250 Default: 150 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring clear-text or SSL Service for Junos XML Management Protocol Client Applications 487 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS server (DHCP and BOOTP Relay Agent) Syntax Hierarchy Level Release Information Description Options server address { ; } [edit forwarding-options helpers bootp], [edit forwarding-options helpers bootp interface interface-group] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to act as a DHCP and BOOTP relay agent. • address—One or more addresses of the server. • logical-system logical-system-name—(Optional) Logical system of the server. • routing-instance [ routing-instance-names ]—(Optional) Routing instance name or names that belong to the DHCP or BOOTP relay agent. Required Privilege Level Related Documentation 488 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents Chapter 37: Configuration Statements for System Services server (DNS and TFTP Service) Syntax Hierarchy Level Release Information Description Options server address ; [edit forwarding-options helpers domain], [edit forwarding-options helpers domain interface interface-name], [edit forwarding-options helpers tftp], [edit forwarding-options helpers tftp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the DNS or TFTP server for forwarding DNS or TFTP requests. Only one server can be specified for each interface. address—Address of the server. logical-system logical-system-name—(Optional) Logical system of the server. routing-instance [ routing-instance-names ]—(Optional) Set the routing instance name or names that belong to the DNS server or TFTP server. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding 489 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS server-identifier Syntax Hierarchy Level Release Information Description server-identifier address; [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches . Configure a server identifier. The identifier can be used to identify a DHCP server in a DHCP message. It can also be used as a destination address from clients to servers (for example, when the boot file is set, but not the boot server). Servers include the server identifier in DHCPOFFER messages so that clients can distinguish between multiple lease offers. Clients include the server identifier in DHCPREQUEST messages to select a lease and indicate which offer is accepted from multiple lease offers. Also, clients can use the server identifier to send unicast request messages to specific DHCP servers to renew a current lease. This address must be a manually assigned, static IP address. The server cannot send a request and receive an IP address from itself or another DHCP server. Default If no server identifier is set, the DHCP server sets the server identifier based on the primary interface address used by the server to receive a client request. For example, if the client sends a DHCP request and the server receives it on fe-0/0/0 and the primary interface address is 1.1.1.1, then the server identifier is set to 1.1.1.1. Options address—IPv4 address of the server. This address must be accessible by all clients served within a specified range of addresses (based on an address pool or static binding). Required Privilege Level 490 system—To view this statement in the configuration. system-control—To add this statement to the configuration. Chapter 37: Configuration Statements for System Services servers Syntax Hierarchy Level Release Information Description Options servers server-address { port port-number; } [edit system services service-deployment] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an IPv4 address for the Session and Resource Control (SRC) server. server-address—The TCP port number. Default: 3333 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 Work with SRC Software service-deployment Syntax Hierarchy Level Release Information Description service-deployment { servers server-address { port port-number; } source-address source-address; } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable Junos OS to work with the Session and Resource Control (SRC) software. 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 Work with SRC Software 491 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS services Syntax 492 services { dhcp { dhcp_services; } finger { ; ; } ftp { ; ; } ssh { protocol-version [v1 v2]; ; ; root-login (allow | deny | deny-password); } service-deployment { servers server-address { port-number port-number; } source-address source-address; } telnet { ; ; } web-management { http { interfaces [ interface-names ]; port port; } https { interfaces [ interface-names ]; local-certificate name; port port; } session { idle-timeout [ minutes ]; session-limit [ session-limit ]; } } xnm-clear-text { ; ; } xnm-ssl { ; ; } Chapter 37: Configuration Statements for System Services } Hierarchy Level Release Information Description [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch so that users on remote systems can access the local router or switch through the DHCP server, finger, rlogin, SSH, telnet, Web management, Junos XML management protocol clear-text, Junos XML management protocol SSL, and network utilities or enable Junos OS to work with the Session and Resource Control (SRC) software. 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 clear-text or SSL Service for Junos XML Management Protocol Client Applications • Configuring Junos OS to Work with SRC Software 493 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS session Syntax Hierarchy Level Release Information Description Options session { idle-timeout [ minutes ]; session-limit [ session-limit ]; } [edit system services web-management] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure limits for the number of minutes a session can be idle before it times out, and configure the number of simultaneous J-Web user login sessions. idle-timeout minutes—Configure the number of minutes a session can be idle before it times out. Range: 1 through 1440 Default: 1440 session-limit session-limit—Configure the maximum number of simultaneous J-Web user login sessions. Range: 1 through 1024 Default: Unlimited Required Privilege Level Related Documentation 494 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • J-Web Interface User Guide Chapter 37: Configuration Statements for System Services sip-server Syntax Hierarchy Level Release Information sip-server [address | name]; [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure Session Initiation Protocol (SIP) server addresses or names for DHCP servers. Options address—IPv4 address of the SIP server. To configure multiple SIP servers, include multiple address options. This address must be accessible by all clients served within a specified range of addresses (based on an address pool or static binding). name—Fully qualified domain name of the SIP server. To configure multiple SIP servers, include multiple name options. This domain name must be accessible by all clients served within a specified range of addresses (based on an address pool or static binding). Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring a DHCP SIP Server on page 450 source-address (SRC Software) Syntax Hierarchy Level Release Information Description Options source-address source-address; [edit system services service-deployment] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the Junos OS to work with the Session and Resource Control (SRC) software. source-address— Local IPv4 address to be used as source address for traffic to the SRC server. The source address restricts traffic within the out-of-band network. 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 Work with SRC Software 495 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS source-address-giaddr Syntax Hierarchy Level Release Information Description source-address-giaddr; [edit forwarding-options helpers bootp], [edit forwarding-options helpers bootp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the gateway IP address (giaddr) as the source IP address of the switch for relayed DHCP packets when the switch is used as the DHCP relay agent. When this statement is entered in the [edit forwarding-options helpers bootp] hierarchy, the gateway IP address is configured as the source IP address of the switch for relayed DHCP packets exiting all interfaces on the switch. When this statement is entered in the [edit forwarding-options helpers bootp interface interface-name] hierarchy, the gateway IP address is configured as the source IP address of the switch for relayed DHCP packets exiting the specified interface of the switch. The IP address of the interface that the DHCP packet exits on the switch acting as a DHCP relay agent is used as the source IP address for relayed DHCP packets by default. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • DHCP/BOOTP Relay for J-EX Series Switches Overview on page 446 ssh Syntax Hierarchy Level Release Information Description ssh { protocol-version [v1 v2]; ; ; root-login (allow | deny | deny-password); } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Allow SSH requests from remote systems to the local router or switch. The remaining statements are explained separately. Required Privilege Level Related Documentation 496 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring SSH Service for Remote Access to the Router or Switch Chapter 37: Configuration Statements for System Services static-binding Syntax Hierarchy Level Release Information Description Options static-binding mac-address { client-identifier (ascii client-id | hexadecimal client-id); fixed-address { address; } host client-hostname; } [edit system services dhcp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches . Set static bindings for DHCP clients. A static binding is a mapping between a fixed IP address and the client’s MAC address or client identifier. mac-address—The MAC address of the client. This is a hardware address that uniquely identifies a client on the network. fixed-address address—Fixed IP address assigned to the client. Typically a client has one address assigned, but you can assign more. host client-hostname—Hostname of the client requesting the DHCP server. The name can include the local domain name. Otherwise, the name is resolved based on the domain-name statement. client-identifier (ascii client-id | hexadecimal client-id)—Used by the DHCP server to index the database of address bindings. The client identifier is an ASCII string or hexadecimal number and can include a type-value pair as specified in RFC 1700, Assigned Numbers. Either a client identifier or the client’s MAC address must be configured to uniquely identify the client on the network. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. 497 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS telnet Syntax Hierarchy Level Release Information Description telnet { connection-limit limit; rate-limit limit; } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Allow Telnet connections from remote systems to the local router or switch. The remaining statements are explained separately. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. tftp Syntax Hierarchy Level Release Information Description tftp { description text-description; interface interface-name { broadcast; description text-description; no-listen; server address ; } server address ; } [edit forwarding-options helpers] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable TFTP request packet forwarding. The remaining statements are explained separately. Required Privilege Level Related Documentation 498 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring DNS and TFTP Packet Forwarding Chapter 37: Configuration Statements for System Services traceoptions Syntax Hierarchy Level traceoptions { file filename ; flag all; flag database; flag general; flag ike; flag parse; flag policy-manager; flag routing-socket; flag timer; } [edit security], [edit services ipsec-vpn] Trace options can be configured at either the [edit security] or the [edit services ipsec-vpn] hierarchy level, but not at both levels. Release Information Description Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure security trace options. To specify more than one trace option, include multiple flag statements. Trace option output is recorded in the /var/log/kmd file. Options files number—(Optional) Maximum number of trace files. When a trace file (for example, kmd) reaches its maximum size, it is renamed kmd.0, then kmd.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. Range: 2 through 1000 files Default: 0 files size size—(Optional) Maximum size of each trace file, in kilobytes (KB). When a trace file (for example, kmd) reaches this size, it is renamed, kmd.0, then kmd.1 and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten. Default: 1024 KB flag—Trace operation to perform. To specify more than one trace operation, include multiple flag statements. • all—Trace all security events. • database—Trace database events. • general—Trace general events. • ike—Trace IKE module processing. 499 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation 500 • parse—Trace configuration processing. • policy-manager—Trace policy manager processing. • routing-socket—Trace routing socket messages. • timer—Trace internal timer events. admin—To view the configuration. admin-control—To add this statement to the configuration. • Configuring Tracing Operations for Security Services Chapter 37: Configuration Statements for System Services traceoptions (DHCP Server) Syntax Hierarchy Level Release Information Description Options traceoptions { file filename ; flag flag; } [edit system services dhcp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for DHCP processes for J-EX Series switches. 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. 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 also must specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—All tracing operations • binding—Trace binding operations • config—Log reading of configuration • conflict—Trace user-detected conflicts for IP addresses • event—Trace important events • ifdb—Trace interface database operations • io— Trace I/O operations • lease—Trace lease operations • main—Trace main loop operations • misc— Trace miscellaneous operations • packet—Trace DHCP packets • options—Trace DHCP options • pool—Trace address pool operations 501 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • protocol—Trace protocol operations • rtsock—Trace routing socket operations • scope—Trace scope operations • signal—Trace DHCP signal operations • trace—All tracing operations • ui—Trace user interface operations match regex—(Optional) Refine the output to include lines that contain the regular expression. • all—All tracing operations • binding—Trace binding operations • config— Log reading of configuration • conflict—Trace user-detected conflicts for IP addresses • event—Trace important events • ifdb— Trace interface database operations • io—Trace I/O operations • lease—Trace lease operations • main—Trace main loop operations • match regex— Refine the output to include lines that contain the regular expression. • misc—Trace miscellaneous operations • packet—Trace DHCP packets • options—Trace DHCP options • pool—Trace address pool operations • protocol—Trace protocol operations • rtsock—Trace routing socket operations • scope—Trace scope operations • signal—Trace DHCP signal operations • trace—All tracing operations • ui—Trace user interface operations no-world-readable—(Optional) Disable unrestricted file access. 502 Chapter 37: Configuration Statements for System Services 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. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring Tracing Operations for DHCP Processes • System Management Configuration Statements 503 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions (DNS and TFTP Packet Forwarding) Syntax Hierarchy Level Release Information Description Default Options traceoptions { file filename ; flag flag; level level; ; } [edit forwarding-options helpers] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure tracing operations for BOOTP, DNS and TFTP packet forwarding. If you do not include this statement, no tracing operations are performed. file filename—Name of the file to receive the output of the tracing operation. Enclose the name in quotation marks (" "). All files are placed in a file named fud in the directory /var/log. If you include the file statement, you must specify a filename. 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 also must specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: 504 • address—Trace address management events • all—Trace all events • bootp—Trace BOOTP or DHCP services events • config—Trace configuration events • domain—Trace DNS service events • ifdb—Trace interface database operations • io—Trace I/O operations • main—Trace main loop events • port—Trace arbitrary protocol events • rtsock—Trace routing socket operations Chapter 37: Configuration Statements for System Services • tftp—Trace TFTP service events • trace—Trace tracing operations • ui—Trace user interface operations • util—Trace miscellaneous utility operations match regular-expression—(Optional) Refine the output to include lines that contain the regular expression. no-remote-trace—(Optional) Disable remote tracing globally or for a specific tracing operation. no-world-readable—(Optional) Restrict file access to the owner. 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 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: 0 bytes through 4,294,967,295 KB Default: 128 KB world-readable—(Optional) Enable unrestricted file access. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Tracing BOOTP, DNS, and TFTP Forwarding Operations 505 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS web-management Syntax Hierarchy Level Release Information Description web-management { http { interfaces [ interface-names ]; port port; } https { interfaces [ interface-names ]; local-certificate name; port port; } } [edit system services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure settings for HTTP or HTTPS access. HTTP access allows management of the router or switch using the browser-based J-Web graphical user interface. HTTPS access allows secure management of the router or switch using the J-Web interface. With HTTPS access, communication between the router or switch Web server and your browser is encrypted. The remaining statements are explained separately. Required Privilege Level Related Documentation 506 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Table 56 on page 396 • J-Web Interface User Guide • http on page 472 • https on page 473 • port on page 486 Chapter 37: Configuration Statements for System Services wins-server Syntax Hierarchy Level Release Information wins-server { address; } [edit system services dhcp], [edit system services dhcp pool], [edit system services dhcp static-binding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description For J-EX Series switches . Specify one or more NetBIOS Name Servers. When a DHCP client is added to the network and assigned an IP address, the NetBIOS Name Server manages the Windows Internet Name Service (WINS) database that matches IP addresses (such as 192.168.1.3) to Windows NetBIOS names (such as \\Marketing ). List servers in order of preference. Options address—IPv4 address of the NetBIOS Name Server running WINS. To configure multiple servers, include multiple address options. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. 507 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 508 CHAPTER 38 Operational Mode Commands for System Services 509 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear system services dhcp binding Syntax Release Information Description Options clear system services dhcp binding
Command introduced before Junos OS Release 10.2 for J-EX Series switches. (J-EX Series switches) Remove obsolete IP address bindings on a Dynamic Host Configuration Protocol (DHCP) server and return them to the IP address pool. address—(Optional) Remove a specific IP address binding and return it to the address pool. Required Privilege Level Related Documentation List of Sample Output Output Fields clear system services dhcp binding 510 view and system • show system services dhcp binding on page 517 clear system services dhcp binding on page 510 When you enter this command, you are provided feedback on the status of your request. user@host> clear system services dhcp binding Chapter 38: Operational Mode Commands for System Services clear system services dhcp conflict Syntax Release Information Description Options clear system services dhcp conflict
Command introduced before Junos OS Release 10.2 for J-EX Series switches. ( J-EX Series switches ) Remove IP addresses from the Dynamic Host Configuration Protocol (DHCP) server conflict list and return them to the IP address pool. address—(Optional) Remove a specific IP address from the conflict list and return it to the address pool. Required Privilege Level Related Documentation List of Sample Output Output Fields clear system services dhcp conflict view and system • show system services dhcp conflict on page 519 clear system services dhcp conflict on page 511 When you enter this command, you are provided feedback on the status of your request. user@host> clear system services dhcp conflict 511 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear system services dhcp statistics Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields clear system services dhcp statistics 512 clear system services dhcp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. ( J-EX Series switches ) Clear Dynamic Host Configuration Protocol (DHCP) server statistics. This command has no options. view and system • show system services dhcp statistics on page 524 clear system services dhcp statistics on page 512 When you enter this command, you are provided feedback on the status of your request. user@host> clear system services dhcp statistics Chapter 38: Operational Mode Commands for System Services request ipsec switch Syntax Release Information Description Options request ipsec switch (interface | security-associations ) Command introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches ) Manually switch from the primary to the backup encryption services interface, or switch from the primary to the backup IP Security (IPsec) tunnel. interface —Switch to the backup encryption interface. security-associations —Switch to the backup tunnel. Required Privilege Level Related Documentation List of Sample Output Output Fields request ipsec switch view • show ipsec redundancy request ipsec switch on page 513 When you enter this command, you are provided feedback on the status of your request. user@host> request ipsec switch security-associations sa-private 513 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request security certificate (signed) Syntax Release Information Description Options request security certificate enroll filename filename subject subject alternative-subject alternative-subject certification-authority certification-authority encoding (binary | pem) key-file key-file domain-name domain-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches ) Obtain a signed certificate from a certificate authority (CA). The signed certificate validates the CA and the owner of the certificate. The results are saved in a specified file to the /var/etc/ikecert directory. filename filename—File that stores the certificate. subject subject—Distinguished name (dn), which consists of a set of components—for example, an organization (o), an organization unit (ou), a country (c), and a locality (l). alternative-subject alternative-subject—Tunnel source address. certification-authority certification-authority—Name of the certificate authority profile in the configuration. encoding (binary | pem)—File format used for the certificate. The format can be a binary file or privacy-enhanced mail (PEM), an ASCII base64-encoded format. The default format is binary. key-file key-file—File containing a local private key. domain-name domain-name—Fully qualified domain name. Required Privilege Level List of Sample Output 514 maintenance request security certificate (signed) on page 514 Output Fields When you enter this command, you are provided feedback on the status of your request. request security certificate (signed) user@host> request security certificate enroll filename host.crt subject c=uk,o=london alternative-subject 10.50.1.4 certification-authority verisign key-file host-1.prv domain-name host.juniper.net CA name: juniper.net CA file: ca_verisign local pub/private key pair: host.prv subject: c=uk,o=london domain name: host.juniper.net alternative subject: 10.50.1.4 Encoding: binary Certificate enrollment has started. To view the status of your enrollment, check the key management process (kmd) log file at /var/log/kmd. <-------------- Chapter 38: Operational Mode Commands for System Services request security key-pair Syntax Release Information Description Options request security key-pair filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches) Generate a public and private key pair for a digital certificate. filename—Name of a file in which to store the key pair. size key-size—(Optional) Key size, in bits. The key size can be 512, 1024, or 2048. The default value is 1024. type—(Optional) Algorithm used to encrypt the key: Required Privilege Level List of Sample Output Output Fields request security key-pair • rsa—RSA algorithm. This is the default. • dsa—Digital signature algorithm with Secure Hash Algorithm (SHA). maintenance request security key-pair on page 515 When you enter this command, you are provided feedback on the status of your request. user@host> request security key-pair security-key-file 515 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request security certificate (unsigned) Syntax Release Information Description Options request security certificate enroll filename filename ca-file ca-file ca-name ca-name encoding (binary | perm) url url Command introduced before Junos OS Release 10.2 for J-EX Series switches. (Encryption interface on J-EX Series switches ) Obtain a certificate from a certificate authority (CA). The results are saved in a specified file to the /var/etc/ikecert directory. filename filename—File that stores the public key certificate. ca-file ca-file—Name of the certificate authority profile in the configuration. ca-name ca-name—Name of the certificate authority. encoding (binary | pem)—File format used for the certificate. The format can be a binary file or privacy-enhanced mail (PEM), an ASCII base64-encoded format. The default value is binary. url url—Certificate authority URL. Required Privilege Level List of Sample Output maintenance request security certificate (unsigned) on page 516 Output Fields When you enter this command, you are provided feedback on the status of your request. request security certificate (unsigned) user@host> request security certificate enroll filename ca_verisign ca-file verisign ca-name juniper.net urlxyzcompany URL http:///cgi-bin/pkiclient.exe CA name: juniper.net CA file: verisign Encoding: binary Certificate enrollment has started. To view the status of your enrollment, check the key management process (kmd) log file at /var/log/kmd. <-------------- 516 Chapter 38: Operational Mode Commands for System Services show system services dhcp binding Syntax Release Information Description Options show system services dhcp binding
Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Dynamic Host Configuration Protocol (DHCP) server client binding information. none—Display brief information about all active client bindings. detail—(Optional) Display detailed information about all active client bindings. address—(Optional) Display detailed client binding information for the specified IP address only. Required Privilege Level Related Documentation List of Sample Output Output Fields view and system • clear system services dhcp binding on page 510 show system services dhcp binding on page 518 show system services dhcp binding address on page 518 show system services dhcp binding address detail on page 518 Table 62 on page 517 describes the output fields for the show system services dhcp binding command. Output fields are listed in the approximate order in which they appear. Table 62: show system services dhcp binding Output Fields Field Name Field Description Level of Output Allocated address List of IP addresses the DHCP server has assigned to clients. All levels MAC address Corresponding media access control (MAC) hardware address of the client. All levels Client identifier (address option only) Client's unique identifier (represented by an ASCII string or hexadecimal digits). This identifier is used by the DHCP server to index its database of address bindings. All levels Binding Type Type of binding assigned to the client. DHCP servers can assign a dynamic binding from a pool of IP addresses or a static binding to one or more specific IP addresses. All levels Lease Expires at Time the lease expires or never for leases that do not expire. All levels Lease Obtained at (address option only) Time the client obtained the lease from the DHCP server. detail State Status of the binding. Bindings can be active or expired. detail 517 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 62: show system services dhcp binding Output Fields (continued) Field Name Field Description Level of Output Pool Address pool that contains the IP address assigned to the client. detail Request received on Interface on which the DHCP message exchange occurs. The IP address pool is configured based on the interface's IP address. If a relay agent is used, its IP address is also displayed. detail DHCP options User-defined options created for the DHCP server. If no options have been defined, this field is blank. detail show system services dhcp binding user@host> show system services dhcp binding Allocated address 192.168.1.2 192.168.1.3 show system services dhcp binding address MAC address 00:a0:12:00:12:ab 00:a0:12:00:13:02 Binding Type static dynamic Lease expires at never 2004-05-03 13:01:42 PDT user@host> show system services dhcp binding 192.168.1.3 DHCP binding information: Allocated address: 192.168.1.3 Mac address: 00:a0:12:00:12:ab Client identifier 61 63 65 64 2d 30 30 3a 61 30 3a 31 32 3a 30 30aced-00:a0:12:00 3a 31 33 3a 30 32:13:02 Lease information: Binding Type dynamic Obtained at 2004-05-02 13:01:42 PDT Expires at 2004-05-03 13:01:42 PDT show system services dhcp binding address detail user@host> show system services dhcp binding 192.168.1.3 detail DHCP binding information: Allocated address 192.168.1.3 MAC address 00:a0:12:00:12:ab Pool 192.168.1.0/24 Request received on fe-0/0/0, relayed by 192.168.4.254 Lease information: Type Obtained at Expires at State active DHCP 2004-05-02 13:01:42 PDT 2004-05-03 13:01:42 PDT DHCP options: Name: name-server, Value: { 6.6.6.6, 6.6.6.7 } Name: domain-name, Value: mydomain.tld Code: 19, Type: flag, Value: off Code: 40, Type: string, Value: domain.tld Code: 32, Type: ip-address, Value: 3.3.3.33 518 Chapter 38: Operational Mode Commands for System Services show system services dhcp conflict Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show system services dhcp conflict Command introduced before Junos OS Release 10.2 for J-EX Series switches. (J-EX Series switches) Display Dynamic Host Configuration Protocol (DHCP) client-detected conflicts for IP addresses. When a conflict is detected, the DHCP server removes the address from the address pool. This command has no options. view and system • clear system services dhcp conflict on page 511 show system services dhcp conflict on page 519 Table 63 on page 519 describes the output fields for the show system services dhcp conflict command. Output fields are listed in the approximate order in which they appear. Table 63: show system services dhcp conflict Output Fields show system services dhcp conflict Field Name Field Description Detection time Date and time the client detected the conflict. Detection method How the conflict was detected. Address IP address where the conflict occurs. The addresses in the conflicts list remain excluded from the pool until you use a clear system services dhcp conflict command to manually clear the list. user@host> show system services dhcp conflict Detection time 2004-08-03 19:04:00 PDT 2004-08-04 04:23:12 PDT 2004-08-05 21:06:44 PDT Detection method ARP Ping Client Address 3.3.3.5 4.4.4.8 3.3.3.10 519 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system services dhcp global Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show system services dhcp global Command introduced before Junos OS Release 10.2 for J-EX Series switches. ( J-EX Series switches ) Display Dynamic Host Configuration Protocol (DHCP) global configuration options. Global options apply to all scopes and clients served by the DHCP server. Global options are overridden if specified otherwise in scope or client options. Scope options apply to specific subnets or ranges of addresses. Client options apply to specific clients. This command has no options. view and system show system services dhcp global on page 521 Table 64 on page 520 describes the output fields for the show system services dhcp global command. Output fields are listed in the approximate order in which they appear. Table 64: show system services dhcp global Output Fields 520 Field Name Field Description BOOTP lease length Length of lease time assigned to BOOTP clients. Default lease time Lease time assigned to clients that do not request a specific lease time. Minimum lease time Minimum time a client retains an IP address lease on the server. Maximum lease time Maximum time a client can retain an IP address lease on the server. DHCP options User-defined options created for the DHCP server. If no options have been defined, this field is blank. Chapter 38: Operational Mode Commands for System Services show system services dhcp global user@host> show system services dhcp global Global settings: BOOTP lease length infinite DHCP lease times: Default lease time Minimum lease time Maximum lease time 1 hour 2 hours infinite DHCP options: Name: name-server, Value: { 6.6.6.6, 6.6.6.7 } Name: domain-name, Value: mydomain.tld Code: 19, Type: flag, Value: off Code: 40, Type: string, Value: domain.tld Code: 32, Type: ip-address, Value: 3.3.3.33 521 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system services dhcp pool Syntax Release Information Description Options show system services dhcp pool Command introduced before Junos OS Release 10.2 for J-EX Series switches. ( J-EX Series switches) Display Dynamic Host Configuration Protocol (DHCP) server IP address pools. none—Display brief information about all IP address pools. detail—(Optional) Display detailed information. subnet-address—(Optional) Display information for the specified subnet address. Required Privilege Level List of Sample Output Output Fields view and system show system services dhcp pool on page 523 show system services dhcp pool subnet-address on page 523 show system services dhcp pool subnet-address detail on page 523 Table 65 on page 522 describes the output fields for the show system services dhcp pool command. Output fields are listed in the approximate order in which they appear. Table 65: show system services dhcp pool Output Fields Field Name Field Description Level of Output Pool name Subnet on which the IP address pool is defined. None specified Low address Lowest address in the IP address pool. None specified High address Highest address in the IP address pool. None specified Excluded addresses Addresses excluded from the address pool. None specified Subnet (subnet-address option only) Subnet to which the specified address pool belongs. None specified Address range (subnet-address option only) Range of IP addresses in the address pool. None specified Addresses assigned Number of IP addresses in the pool that are assigned to DHCP clients and the total number of IP addresses in the pool. detail Active Number of assigned IP addresses in the pool that are active. detail Excluded Number of assigned IP addresses in the pool that are excluded. detail Default lease time Lease time assigned to clients that do not request a specific lease time. detail 522 Chapter 38: Operational Mode Commands for System Services Table 65: show system services dhcp pool Output Fields (continued) Field Name Field Description Level of Output Minimum lease time Minimum time a client can retain an IP address lease on the server. detail Maximum lease time Maximum time a client can retain an IP address lease on the server. detail DHCP options User-defined options created for the DHCP server. If no options have been defined, this field is blank. detail show system services dhcp pool user@host> show system services dhcp pool Pool name 3.3.3.0/24 Low address 3.3.3.2 High address 3.3.3.254 Excluded addresses 3.3.3.1 show system services dhcp pool subnet-address user@host> show system services dhcp pool 3.3.3.0/24 show system services dhcp pool subnet-address detail user@host> show system services dhcp pool 3.3.3.0/24 detail Pool information: Subnet Address range Addresses assigned Pool information: Subnet Address range Addresses assigned Active: 1, Excluded: 1 DHCP lease times: Default lease time Minimum lease time Maximum lease time 3.3.3.0/24 3.3.3.2 - 3.3.3.254 2/253 3.3.3.0/24 3.3.3.2 - 3.3.3.254 2/253 1 hour 2 hours infinite DHCP options: Name: name-server, Value: { 6.6.6.6, 6.6.6.7 } Name: domain-name, Value: mydomain.tld Name: router, Value: { 3.3.3.1 } Name: server-identifier, Value: 3.3.3.1 Code: 19, Type: flag, Value: off Code: 40, Type: string, Value: domain.tld Code: 32, Type: ip-address, Value: 3.3.3.333.3.3.254 3.3.3.1 523 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system services dhcp statistics Syntax show system services dhcp statistics Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description (J-EX Series switches) Display Dynamic Host Configuration Protocol (DHCP) server statistics. Options This command has no options. Required Privilege Level view and system Related Documentation • List of Sample Output clear system services dhcp statistics on page 512 show system services dhcp statistics on page 525 Output Fields Table 66 on page 524 describes the output fields for the show system services dhcp statistics command. Output fields are listed in the approximate order in which they appear. Table 66: show system services dhcp statistics Output Fields Field Name Field Description Default lease time Lease time assigned to clients that do not request a specific lease time. Minimum lease time Minimum time a client can retain an IP address lease on the server. Maximum lease time Maximum time a client can retain an IP address lease on the server. Packets dropped Total number of packets dropped and number of packets dropped because of: 524 • Invalid hardware address • Invalid opcode • Invalid server address • No available address • No interface match • No routing instance match • No valid local addresses • Packet too short • Read error • Send error Chapter 38: Operational Mode Commands for System Services Table 66: show system services dhcp statistics Output Fields (continued) Field Name Field Description Messages received Number of the following message types sent from DHCP clients and received by the DHCP server: Messages sent show system services dhcp statistics • BOOTREQUEST • DHCPDECLINE • DHCPDISCOVER • DHCPINFORM • DHCPRELEASE • DHCPREQUEST Number of the following message types sent from the DHCP server to DHCP clients: • BOOTREPLY • DHCPACK • DHCPOFFER • DHCPNAK user@host> show system services dhcp statistics DHCP lease times: Default lease time Minimum lease time Maximum lease time 1 hour 2 hours infinite Packets dropped: Total Bad hardware address Bad opcode Invalid server address No available addresses No interface match No routing instance match No valid local address Packet too short Read error Send error 0 0 0 0 0 0 0 0 0 0 0 Messages received: BOOTREQUEST DHCPDECLINE DHCPDISCOVER DHCPINFORM DHCPRELEASE DHCPREQUEST 0 0 0 0 0 0 Messages sent: BOOTREPLY DHCPACK DHCPOFFER DHCPNAK 0 0 0 0 525 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system services service-deployment Syntax Release Information Description Options Required Privilege Level show system services service-deployment Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about a Session and Resource Control (SRC) client. This command has no options. view and system List of Sample Output show system services service-deployment on page 526 show system services service-deployment user@host> show system services service-deployment Connected to 192.4.4.4 port 10288 since 2004-05-03 11:04:34 PDT Keepalive settings: Interval 15 seconds Keepalives sent: 750 Notifications sent: 0 Last update from peer: 00:00:06 ago 526 Chapter 38: Operational Mode Commands for System Services ssh Syntax ssh host Syntax (J-EX Series Switch) ssh host Release Information Description Command introduced before Junos OS Release 10.2 for J-EX Series switches. Use the SSH program to open a connection between a local router or switch and a remote system and execute commands on the remote system. You can issue the ssh command from the Junos OS CLI to log in to a remote system or from a remote system to log in to the local router or switch. When executing this command, you include one or more CLI commands by enclosing them in quotation marks and separating the commands with semicolons: ssh address 'cli-command1 ; cli-command2 ' Options host—Name or address of the remote system. bypass-routing—(Optional) Bypass the normal routing tables and send ping requests directly to a system on an attached network. If the system is not on a directly attached network, an error is returned. Use this option to ping a local system through an interface that has no route through it. inet | inet6—(Optional) Create an IPv4 or IPv6 connection, respectively. interface interface-name—(Optional) Interface name for the SSH session. (This option does not work when default-address-selection is configured at the [edit system] hierarchy level, because this configuration uses the loopback interface as the source address for all locally generated IP packets.) logical-system logical-system-name—(Optional) Name of a particular logical system for the SSH attempt. routing-instance routing-instance-name—(Optional) Name of the routing instance for the SSH attempt. source address—(Optional) Source address of the SSH connection. 527 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS v1 | v2—(Optional) Use SSH version 1 or 2, respectively, when connecting to a remote host. Additional Information To configure an SSH (version 1) key for your user account, include the authentication ssh-rsa statement at the [edit system login user user-name] hierarchy level. To configure an SSH (version 2) key for your user account, include the authentication dsa-rsa statement at the [edit system login user user-name] hierarchy level. For details, see the Junos OS System Basics Configuration Guide. You can limit the number of times a user can attempt to enter a password while logging in through SSH. To specify the number of times a user can attempt to enter a password to log in through SSH, include the retry-options statement at the [edit system login] hierarchy level. For details, see the Junos OS System Basics Configuration Guide. Required Privilege Level List of Sample Output Output Fields ssh network ssh on page 528 When you enter this command, you are provided feedback on the status of your request. user@host> ssh cree Host key not found from the list of known hosts. Are you sure you want to continue connecting (yes/no)? yes Host ?cree' added to the list of known hosts. boojun@cree's password: Last login: Sun Jun 21 10:43:42 1998 from junos-router % ... 528 Chapter 38: Operational Mode Commands for System Services telnet Syntax telnet host <8bit> Syntax (J-EX Series Switch) telnet host <8bit> Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Open a telnet session to a remote system. Type Ctrl+] to escape from the telnet session to the telnet command level, and then type quit to exit from telnet. host—Name or address of the remote system. 8bit—(Optional) Use an 8-bit data path. bypass-routing—(Optional) Bypass the normal routing tables and send ping requests directly to a system on an attached network. If the system is not on a directly attached network, an error is returned. Use this option to ping a local system through an interface that has no route through it. inet | inet6—(Optional) Open an IPv4 or IPv6 session, respectively. interface interface-name—(Optional) Interface name for the telnet session. (This option does not work when default-address-selection is configured at the [edit system] hierarchy level, because this configuration uses the loopback interface as the source address for all locally generated IP packets.) logical-system logical-system-name—(Optional) Name of a particular logical system for the telnet attempt. no-resolve—(Optional) Do not attempt to determine the hostname that corresponds to the IP address. port port-number—(Optional) Port number or service name on the remote system. 529 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS routing-instance routing-instance-name—(Optional) Name of the routing instance for the telnet attempt. source source-address—(Optional) Source address of the telnet connection. Additional Information Required Privilege Level List of Sample Output Output Fields telnet 530 You can limit the number of times a user can attempt to enter a password while logging in through telnet. To specify the number of times a user can attempt to enter a password to log in through telnet, include the retry-options statement at the [edit system login] hierarchy level. For details, see the Junos OS System Basics Configuration Guide. network telnet on page 530 When you enter this command, you are provided feedback on the status of your request. user@host> telnet 192.154.1.254 Trying 192.154.169.254... Connected to level5.company.net. Escape character is '^]'. ttypa login: PART 10 Junos OS for J-EX Series Switches System Monitoring • System Monitoring Overview on page 533 • Administering and Monitoring System Functions on page 541 • Configuration Statements for System Monitoring on page 559 • Operational Mode Commands for System Monitoring on page 611 531 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 532 CHAPTER 39 System Monitoring Overview • Understanding Alarm Types and Severity Levels on J-EX Series Switches on page 533 • Dashboard for J-EX Series Switches on page 534 Understanding Alarm Types and Severity Levels on J-EX Series Switches Before monitoring alarms on the switch, become familiar with the terms defined in Table 67 on page 533. Table 67: Alarm Terms Term Definition alarm Signal alerting you to conditions that might prevent normal operation. On a switch, the alarm signal is the yellow ALARM LED lit on the front of the chassis. alarm condition Failure event that triggers an alarm. alarm severity Seriousness of the alarm. The level of severity can be either major (red) or minor (yellow). chassis alarm Predefined alarm triggered by a physical condition on the switch such as a power supply failure, excessive component temperature, or media failure. system alarm Predefined alarm triggered by a missing rescue configuration or failure to install a license for a licensed software feature. Alarm Types The switch supports these alarms: • Chassis alarms indicate a failure on the switch or one of its components. Chassis alarms are preset and cannot be modified. • System alarms indicate a missing rescue configuration. System alarms are preset and cannot be modified, although you can configure them to appear automatically in the J-Web interface display or CLI display. Alarm Severity Levels 533 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Alarms on a J-EX Series Switches have two severity levels: • Major (red)—Indicates a critical situation on the switch that has resulted from one of the following conditions. A red alarm condition requires immediate action. • One or more hardware components have failed. • One or more hardware components have exceeded temperature thresholds. • An alarm condition configured on an interface has triggered a critical warning. NOTE: When you connect power to a J-EX4200 switch, the Alarm (ALM) LED lights red to indicate that the network link is disconnected. This behavior is normal. Plugging an active Ethernet cable into the management (MGMT) port on the switch completes the network link and turns off the ALM LED. Connecting the switch to a dedicated management console instead of a network does not affect the ALM LED. The LED remains red until the switch is connected to a network. • Minor (yellow or amber)—Indicates a noncritical condition on the switch that, if left unchecked, might cause an interruption in service or degradation in performance. A yellow alarm condition requires monitoring or maintenance. A missing rescue configuration generates a yellow system alarm. To set the rescue configuration, see “Setting or Deleting the Rescue Configuration (CLI Procedure)” on page 344. Related Documentation • Checking Active Alarms with the J-Web Interface on page 544 • Dashboard for J-EX Series Switches on page 534 Dashboard for J-EX Series Switches When you log in to the J-Web user interface, the dashboard for the J-EX Series switch appears. Use the dashboard to view system information. The dashboard comprises four panels and a graphical chassis viewer. You can click Preferences to choose which panels are to be displayed and set the refresh interval for chassis viewer information. Click OK to save your preference changes and return to the dashboard or click Cancel to return to the dashboard without saving changes. NOTE: You can drag and drop the various panels to different locations in the J-Web window. 534 Chapter 39: System Monitoring Overview This topic describes: • System Information Panel on page 535 • Health Status Panel on page 535 • Capacity Utilization Panel on page 536 • Alarms Panel on page 536 • Chassis Viewer on page 537 System Information Panel Table 68: System Information Field Description System name Indicates the local name of the J-EX Series switch. Device model Indicates the model of the J-EX Series switch. NOTE: For a J-EX8208 switch or a J-EX8216 switch, the Device model information changes with respect to the selected line card, the Switch Fabric and Routing Engine (SRE) module in a J-EX8208 switch, or the Routing Engine (RE) module in a J-EX8216 switch. Inventory details Indicates the following: • For J-EX4200 switches not configured as Virtual Chassis, the value in Inventory is always 1 FPC. FPC is a legacy term for a slot in a large router chassis; here, it simply refers to the single switch. • For a J-EX4200 switch configured as a Virtual Chassis, the value in Inventory is displayed as 1–10 FPC, with the number corresponding to the number of member switches. • For a J-EX8208 switch, the values in Inventory are displayed as 1–3 CB and 0–8 FPC. Control board (CB) refers to SRE and SF modules. FPC refers to line cards. • For a J-EX8216 switch, the values in Inventory are displayed as 1-2 CB and 0-16 FPC. Control board (CB) refers to RE modules. FPC refers to line cards. Junos image Indicates the version of the Junos OS image. Boot image Indicates the version of the boot image that is used. Device uptime Indicates the time since the last reboot. Last configured time Indicates the time when the switch was last configured. Health Status Panel Table 69: Health Status Field Description J-EX4200 Switches Memory util. Indicates the memory used in the Routing Engine. In a Virtual Chassis configuration, the memory utilization value of the master Routing Engine is displayed. Flash Indicates the usage and capacity of internal flash memory and any external USB flash drive. 535 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 69: Health Status (continued) Field Description Temp. Indicates the chassis temperature status. Temperatures in the dashboard are listed in Celsius and the corresponding Fahrenheit values. CPU load Indicates the average CPU usage over 15 minutes. Fan status Indicates the fan status of the switch. The possible values are OK, Failed, and Absent. J-EX8208 Switches Memory util. Indicates the memory used in the Routing Engine. If there are two Routing Engines, the memory utilization value of the master is displayed. CPU load Indicates the average CPU usage over 15 minutes. Flash Indicates the usage and capacity of internal flash memory and any external USB flash drive. J-EX8216 Switches Memory util. Indicates the memory used in the Routing Engine. If there are two Routing Engines, the memory utilization value of the master is displayed. CPU load Indicates the average CPU usage over 15 minutes. Flash Indicates the usage and capacity of internal flash memory and any external USB flash drive. Capacity Utilization Panel Table 70: Capacity Utilization Field Description Number of active ports Indicates the number of active ports in the switch. Total number of ports Indicates the number of ports in the switch. Used-up MAC-Table entries Indicates the number of MAC-Table entries. Supported MAC-Table entries Indicates the maximum number of MAC-Table entries permitted. Number of VLANs configured Indicates the number of configured VLANs. Number of VLANs supported Indicates the maximum number of VLANs that are supported. Alarms Panel Displays information about the last five alarms raised in the system. For example, if there are 5 major alarms, then details for all 5 major alarms are displayed. If there are 4 major alarms and 3 minor alarms, then details of the 4 major alarms and 1 minor alarm are displayed. Major alarms are displayed in red and minor alarms are displayed in yellow. 536 Chapter 39: System Monitoring Overview NOTE: When you connect power to a J-EX4200 switch, the Alarm (ALM) LED lights red to indicate that the network link is disconnected. This behavior is normal. Plugging an active Ethernet cable into the management (MGMT) port on the switch completes the network link and turns off the ALM LED. Connecting the switch to a dedicated management console instead of a network does not affect the ALM LED. The LED remains red until the switch is connected to a network. Chassis Viewer You can click the Rear View button to see the back of the chassis image. Click Front View to see the front of the image. In a Virtual Chassis configuration, the Rear View button is disabled if the switch is not selected. • Table 71 on page 537—Describes the chassis viewer for J-EX4200 switches. • Table 72 on page 538—Describes the chassis viewer for J-EX8208 switches. • Table 73 on page 540—Describes the chassis viewer for J-EX8216 switches. Table 71: Chassis Viewer for J-EX4200 Switches Field Description Front View Interface status In the image, the colors listed below denote the interface status: • Green—Interface is up and operational. • Yellow—Interface is up but is nonoperational. • Gray—Interface is down and nonoperational. Hover the mouse pointer over the interface (port) to view more information. For a Virtual Chassis configuration, select the switch to view the interface status. If an SFP+ uplink module is installed in the switch, hover the mouse pointer over the port icon to display whether the module is configured to operate in 1G mode or 10G mode. If the module is configured to operate in 1G mode, the tool tip information is displayed for all 4 ports. If the module is configured to operate in 10G mode, the tool tip information is displayed only for 2 ports. For SFP and SFP+ ports, the interfaces appear dimmed if no transceiver is inserted. The chassis viewer displays “Transceiver not plugged-in” when you hover the mouse pointer over the port icon. LCD panel LCD panel configured for the LEDs on the ports. Hover the mouse pointer over the icon to view the current character display. Rear View of the J-EX4200 Switch Fan tray Hover the mouse pointer over the fan tray icon to display Name, Status, and Description information. For a Virtual Chassis, the status of the fans of the selected member switch is displayed. 537 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 71: Chassis Viewer for J-EX4200 Switches (continued) Field Description Virtual Chassis port Displayed only when switches are configured as a Virtual Chassis. The colors listed below denote the Virtual Chassis port (VCP) status: USB port • Green—VCP is up and operational. • Yellow—VCP is up but is nonoperational. • Gray—VCP is down and nonoperational. Indicates the USB port for the switch. NOTE: We recommend you use USB flash drives purchased from Dell for your J-EX Series switch. Management (me0) port The management port is used to connect the switch to a management device for out-of-band management. Console port The console port is used to connect the switch to a management console or to a console server. (You might do this for initial switch configuration.) Power supplies Hover the mouse pointer over the power supply icons to display Name, Status, and Description information. Table 72: Chassis Viewer for J-EX8208 Switches Field Description Front View Interface status In the image, click any line card, SRE module, or SF module to view the front view of the selected component. The colors listed below denote the interface status: • Green—Interface is up and operational. • Yellow—Interface is up but is nonoperational. • Gray—Interface is down and nonoperational. Hover the mouse pointer over the interface (port) to view more information. You can view status for the following ports on the SRE module: • USB port—Indicates the USB port for the switch. NOTE: We recommend you use USB flash drives purchased from Dell for your J-EX Series switch. • Auxiliary port—This port is not enabled on the switch. It is reserved for future use. • Management (me0) port—The management port is used to connect the switch to a management device for out-of-band management. • Console port—The console port is used to connect the switch to a management console or to a console server. (You might do this for initial switch configuration.) Because the SF module has no ports, no status information is displayed. 538 Chapter 39: System Monitoring Overview Table 72: Chassis Viewer for J-EX8208 Switches (continued) Field Description Slot numbers Slots on the switch are labeled, from the top of the switch down: • 0–3 (line cards) • SRE0, SF, SRE1 (SRE and SF modules) • 4–7 (line cards) Temperature The active slots contain a gray temperature icon. Hover the mouse pointer over the icon to display temperature information for the slot. Fan status Hover the mouse pointer over the fan tray icon to display Name, Status, and Description information. Power supplies Hover the mouse pointer over the power supply icons to display Name, Status, and Description information. LCD panel LCD panel configured for the LEDs on the ports. Hover the mouse pointer over the icon to view the current character display. Rear View The J-EX8208 switch does not have any components on the rear of the chassis. 539 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 73: Chassis Viewer for J-EX8216 Switches Field Description Front View Interface status In the image, click any line card or RE module to view the front view of the selected component. The colors listed below denote the interface status: • Green—Interface is up and operational. • Yellow—Interface is up but is nonoperational. • Gray—Interface is down and nonoperational. Hover the mouse pointer over the interface (port) to view more information. You can view status for the following ports on the RE module: • USB port—Indicates the USB port for the switch. NOTE: We recommend you use USB flash drives purchased from Dell for your J-EX Series switch. Slot numbers • Auxiliary port—This port is not enabled on the switch. It is reserved for future use. • Management (me0) port—The management port is used to connect the switch to a management device for out-of-band management. • Console port—The console port is used to connect the switch to a management console or to a console server. (You might do this for initial switch configuration.) Slots on the switch are labeled, from the top of the switch down: • RE0 (RE module) • RE1 (RE module) • 0–15 (line cards) Temperature The active slots contain a gray temperature icon. Hover the mouse pointer over the icon to display temperature information for the slot. Fan status Hover the mouse pointer over the fan tray icon to display consolidated fan information. Power supplies Hover the mouse pointer over the power supply icons to display Name, Status, and Description information. LCD panel LCD panel configured for the LEDs on the ports. Hover the mouse pointer over the icon to view the current character display. Rear View SF modules Related Documentation 540 Hover the mouse pointer over the SF module icons in their respective slots to display information. Slots are numbered SF7–SF0, from left to right. • J-Web User Interface for J-EX Series Switches Overview on page 129 • Checking Active Alarms with the J-Web Interface on page 544 • J-EX4200 Switches Hardware Overview on page 25 • J-EX8208 Switch Hardware Overview on page 27 • J-EX8216 Switch Hardware Overview on page 30 CHAPTER 40 Administering and Monitoring System Functions • Monitoring System Log Messages on page 541 • Checking Active Alarms with the J-Web Interface on page 544 • Monitoring Chassis Alarms for a J-EX8200 Switch on page 545 • Monitoring Switch Control Traffic on page 548 • Monitoring System Properties on page 550 • Monitoring Chassis Information on page 552 • Monitoring System Process Information on page 554 • Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure) on page 555 Monitoring System Log Messages Purpose Action Use the monitoring functionality to filter and view system log messages for J-EX Series switches. To view events in the J-Web interface, select Monitor > Events and Alarms > View Events. Apply a filter or a combination of filters to view messages. You can use filters to display relevant events. Table 74 on page 541 describes the different filters, their functions, and the associated actions. To view events in the CLI, enter the following command: show log Table 74: Filtering System Log Messages Field Function Your Action System Log File Specifies the name of a system log file for which you want to display the recorded events. To specify events recorded in a particular file, select the system log filename from the list—for example, messages. Lists the names of all the system log files that you configure. By default, a log file, messages, is included in the /var/log/ directory. Select Include archived files to include archived files in the search. 541 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 74: Filtering System Log Messages (continued) Field Function Your Action Process Specifies the name of the process generating the events you want to display. To specify events generated by a process, type the name of the process. To view all the processes running on your system, enter the CLI command show system processes. For example, type mgd to list all messages generated by the management process. For more information about processes, see the Junos OS Installation and Upgrade Guide at http://www.juniper.net/techpubs/software/junos/. Date From Specifies the time period in which the events you want displayed are generated. To Displays a calendar that allows you to select the year, month, day, and time. It also allows you to select the local time. By default, the messages generated in the last hour are displayed. End Time shows the current time and Start Time shows the time one hour before End Time. Event ID Specifies the event ID for which you want to display the messages. To specify the time period: • Click the Calendar icon and select the year, month, and date—for example, 02/10/2007. • Click the Calendar icon and select the year, month, and date—for example, 02/10/2007. • Click to select the time in hours, minutes, and seconds. To specify events with a specific ID, type the partial or complete ID—for example, TFTPD_AF_ERR. Allows you to type part of the ID and completes the remainder automatically. An event ID, also known as a system log message code, uniquely identifies a system log message. It begins with a prefix that indicates the generating software process or library. Description Specifies text from the description of events that you want to display. Allows you to use regular expressions to match text from the event description. Search To specify events with a specific description, type a text string from the description with regular expression. NOTE: Regular expression matching is case-sensitive. For example, type ^Initial* to display all messages with lines beginning with the term Initial. Applies the specified filter and displays the matching messages. To apply the filter and display messages, click Search. Meaning Table 75 on page 543 describes the Event Summary fields. NOTE: By default, the View Events page in the J-Web interface displays the most recent 25 events, with severity levels highlighted in different colors. After you specify the filters, Event Summary displays the events matching the specified filters. Click the First, Next, Prev, and Last links to navigate through messages. 542 Chapter 40: Administering and Monitoring System Functions Table 75: Viewing System Log Messages Field Function Additional Information Process Displays the name and ID of the process that generated the system log message. The information displayed in this field is different for messages generated on the local Routing Engine than for messages generated on another Routing Engine (on a system with two Routing Engines installed and operational). Messages from the other Routing Engine also include the identifiers re0 and re1 to identify the Routing Engine. Severity Severity level of a message is indicated by different colors. A severity level indicates how seriously the triggering event affects switch functions. When you configure a location for logging a facility, you also specify a severity level for the facility. Only messages from the facility that are rated at that level or higher are logged to the specified file. Event ID • Unknown—Gray—Indicates no severity level is specified. • Debug/Info/Notice—Green—Indicates conditions that are not errors but are of interest or might warrant special handling. • Warning—Yellow—Indicates conditions that warrant monitoring. • Error—Blue—Indicates standard error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels. • Critical—Pink—Indicates critical conditions, such as hard-drive errors. • Alert—Orange—Indicates conditions that require immediate correction, such as a corrupted system database. • Emergency—Red—Indicates system panic or other conditions that cause the switch to stop functioning. Displays a code that uniquely identifies the message. The prefix on each code identifies the message source, and the rest of the code indicates the specific event or error. The event ID begins with a prefix that indicates the generating software process. Some processes on a switch do not use codes. This field might be blank in a message generated from such a process. An event can belong to one of the following type categories: Event Description Displays a more detailed explanation of the message. Time Displays the time at which the message was logged. Related Documentation • Error—Indicates an error or failure condition that might require corrective action. • Event—Indicates a condition or occurrence that does not generally require corrective action. • Checking Active Alarms with the J-Web Interface on page 544 • Understanding Alarm Types and Severity Levels on J-EX Series Switches on page 533 543 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Checking Active Alarms with the J-Web Interface Purpose Use the monitoring functionality to view alarm information for the J-EX Series switches including alarm type, alarm severity, and a brief description for each active alarm on the switching platform. Action To view the active alarms: 1. Select Monitor> Events and Alarms > View Alarms in the J-Web interface. 2. Select an alarm filter based on alarm type, severity, description, and date range. 3. Click Go. All the alarms matching the filter are displayed. NOTE: When the switch is reset, the active alarms are displayed. Meaning Table 76 on page 544 lists the alarm output fields. Table 76: Summary of Key Alarm Output Fields Field Values Type Category of the alarm: • Chassis—Indicates an alarm condition on the chassis (typically an environmental alarm such as one related to temperature). NOTE: When you connect power to a J-EX4200 switch, the Alarm (ALM) LED lights red to indicate that the network link is disconnected. This behavior is normal. Plugging an active Ethernet cable into the management (MGMT) port on the switch completes the network link and turns off the ALM LED. Connecting the switch to a dedicated management console instead of a network does not affect the ALM LED. The LED remains red until the switch is connected to a network. • System—Indicates an alarm condition in the system. Severity Alarm severity—either major (red) or minor (yellow). Description Brief synopsis of the alarm. Time Date and time when the failure was detected. Related Documentation 544 • Monitoring System Log Messages on page 541 • Dashboard for J-EX Series Switches on page 534 • Understanding Alarm Types and Severity Levels on J-EX Series Switches on page 533 Chapter 40: Administering and Monitoring System Functions Monitoring Chassis Alarms for a J-EX8200 Switch Purpose This document provides information on chassis alarm conditions, and how you should respond when a certain chassis alarm is seen on your switch. Various conditions related to the chassis components trigger yellow and red alarms. You cannot configure these conditions. See “Understanding Alarm Types and Severity Levels on J-EX Series Switches” on page 533. Action You can monitor chassis alarms by watching the ALM chassis status LED and using the LCD panel to gather information about the alarm. See Chassis Status LEDs in a J-EX8200 Switch and LCD Panel in a J-EX8200 Switch. To display switch chassis alarms in the CLI, use the following command user@host> show chassis alarms The command output displays the number of alarms currently active, the time when the alarm began, the severity level, and an alarm description. Note the date and time of an alarm so that you can correlate it with error messages in the messages system log file. You can also monitor chassis alarms using the J-Web interface. See “Checking Active Alarms with the J-Web Interface” on page 544. Table 77 on page 545 lists some of the chassis alarms that a J-EX8200 switch can generate. Table 77: Chassis Alarms for J-EX8200 Switches Component Alarm Condition Remedy Severity Additional Information Fan tray The fan tray has been removed from the chassis. Install the fan tray. Yellow/Red The switch will eventually get too hot to operate if a fan tray is removed. Temperature alarms will follow. This alarm is expected during fan tray removal and installation. Fan tray One or more fans in a fan tray is spinning below the required speed. Replace the fan tray. Red Individual fans cannot be replaced; you must replace the fan tray. Fan tray The fan tray’s internal connection to the switch is not functioning properly. Remove and reinsert the fan tray. Red The switch will eventually get too hot to operate if a fan tray is not operating. Temperature alarms will follow. If removing and reinserting the fan tray does not resolve the problem, reboot the switch. 545 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 77: Chassis Alarms for J-EX8200 Switches (continued) Power supply A power supply slot that contained a power supply at bootup is now empty. Install a power supply in the empty power supply slot. Yellow You can ignore this alarm in cases in which a power supply slot can remain empty. You will not see this alarm if the switch is booted with an empty power supply slot. This alarm is expected during power supply removal and installation. This alarm can be triggered by a line card insertion. The alarm condition corrects itself when seen for this reason. Power supply A power supply has failed due to an input or output failure, or due to temperature issues. Replace the failed power supply. Red Power supply A power supply’s internal connection to the switch is not operating properly. Remove and reinsert the power supply. Red The chassis warm temperature threshold has been exceeded and fan speeds have increased. Adjust room temperature downward, if possible. Temperature If removing and reinserting the power supply does not resolve the problem, reboot the switch. Ensure airflow through the switch is unobstructed. Yellow The chassis is warm and should be cooled down. The switch is still functioning normally. To monitor temperature: user@switch> show chassis environment To monitor temperature thresholds: user@switch> show chassis temperature-thresholds 546 Chapter 40: Administering and Monitoring System Functions Table 77: Chassis Alarms for J-EX8200 Switches (continued) Temperature The chassis high temperature threshold has been exceeded and the fans are operating at full speed. Adjust room temperature downward, if possible. Red Ensure airflow through the switch is unobstructed. The chassis is hot and should be cooled down. The switch might still function normally but is close to shutting down if it hasn’t already. To monitor temperature: user@switch> show chassis environment To monitor temperature thresholds: user@switch> show chassis temperature-thresholds Temperature Temperature The chassis warm temperature threshold has been exceeded, and one or more fans are not operating properly. The operating fans are running at full speed. The chassis high temperature threshold has been exceeded, and one or more fans is not operating properly. The operating fans are running at full speed. Replace the fan tray that has the faulty fan or fans. Yellow The chassis is warm and should be cooled down. The switch is still functioning normally. Adjust room temperature downward, if possible. To monitor temperature: Ensure airflow through the switch is unobstructed. To monitor temperature user@switch> thresholds: show chassis Replace the fan tray that has the faulty fan or fans. user@switch> show chassis environment temperature-thresholds Red Adjust room temperature downward, if possible. The chassis is hot and should be cooled down. The switch might still function normally but is close to shutting down if it hasn’t already. To monitor temperature: user@switch> Ensure airflow through the switch is unobstructed. show chassis environment To monitor temperature thresholds: user@switch> show chassis temperature-thresholds Temperature The temperature sensor on a hardware component has failed. Replace the hardware component. Yellow Routing Engine (RE), Switch Fabric and Routing Engine (SRE), or Switch Fabric (SF) module The RE, SRE, or SF module has failed. The RE, SRE, or SF module must be replaced. Red 547 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 77: Chassis Alarms for J-EX8200 Switches (continued) Link Status The link to the network is down. Related Documentation Check network connectivity. Red or Yellow The network link is disabled by default, so you might see this alarm before you connect the switch to the network. • Checking Active Alarms with the J-Web Interface on page 544 • Chassis Status LEDs in a J-EX8200 Switch Monitoring Switch Control Traffic Purpose Use the packet capture feature when you need to quickly capture and analyze switch control traffic on a switch. The packet capture feature allows you to capture traffic destined for or originating from the Routing Engine. Action To use the packet capture feature in the J-Web interface, select Troubleshoot>Packet Capture. To use the packet capture feature in the CLI, enter the following CLI command: monitor traffic Meaning You can use the packet capture feature to compose expressions with various matching criteria to specify the packets that you want to capture. You can decode and view the captured packets in the J-Web interface as they are captured. The packet capture feature does not capture transient traffic. Table 78: Packet Capture Field Summary Field Function Your Action Interface Specifies the interface on which the packets are captured. If you select default, packets on the Ethernet management port 0, are captured. From the list, select an interface—for example, ge-0/0/0. Detail level Specifies the extent of details to be displayed for the packet headers. From the list, select Detail. Packets 548 • Brief—Displays the minimum packet header information. This is the default. • Detail—Displays packet header information in moderate detail. • Extensive—Displays the maximum packet header information. Specifies the number of packets to be captured. Values range from 1 to 1000. Default is 10. Packet capture stops capturing packets after this number is reached. From the list, select the number of packets to be captured—for example, 10. Chapter 40: Administering and Monitoring System Functions Table 78: Packet Capture Field Summary (continued) Field Function Your Action Addresses Specifies the addresses to be matched for capturing the packets using a combination of the following parameters: Select address-matching criteria. For example: • Direction—Matches the packet headers for IP address, hostname, or network address of the source, destination or both. 1. Type—Specifies if packet headers are matched for host address or network address. 3. In the Address box, type 10.1.40.48. • From the Direction list, select source. 2. From the Type list, select host. 4. Click Add. You can add multiple entries to refine the match criteria for addresses. Protocols Matches the protocol for which packets are captured. You can choose to capture TCP, UDP, or ICMP packets or a combination of TCP, UDP, and ICMP packets. From the list, select a protocol—for example, tcp. Ports Matches packet headers containing the specified source or destination TCP or UDP port number or port name. Select a direction and a port. For example: • From the Type list, select src. • In the Port box, type 23. Advanced Options Absolute TCP Sequence Specifies that absolute TCP sequence numbers are to be displayed for the packet headers. To display absolute TCP sequence numbers in the packet headers, select this check box. Layer 2 Headers Specifies that link-layer packet headers are to be displayed. To include link-layer packet headers while capturing packets, select this check box. Non-Promiscuous Specifies not to place the interface in promiscuous mode, so that the interface reads only packets addressed to it. In promiscuous mode, the interface reads every packet that reaches it. To read all packets that reach the interface, select this check box. Display Hex Specifies that packet headers, except link-layer headers, are to be displayed in hexadecimal format. To display the packet headers in hexadecimal format, select this check box. Display ASCII and Hex Specifies that packet headers are to be displayed in hexadecimal and ASCII format. To display the packet headers in ASCII and hexadecimal formats, select this check box. Header Expression Specifies the match condition for the packets to be captured. The match conditions you specify for Addresses, Protocols, and Ports are displayed in expression format in this field. You can enter match conditions directly in this field in expression format or modify the expression composed from the match conditions you specified for Addresses, Protocols, and Ports. If you change the match conditions specified for Addresses, Protocols, and Ports again, packet capture overwrites your changes with the new match conditions. Packet Size Specifies the number of bytes to be displayed for each packet. If a packet header exceeds this size, the display is truncated for the packet header. The default value is 96 bytes. Type the number of bytes you want to capture for each packet header—for example, 256. 549 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 78: Packet Capture Field Summary (continued) Field Function Your Action Don't Resolve Addresses Specifies that IP addresses are not to be resolved into hostnames in the packet headers displayed. To prevent packet capture from resolving IP addresses to hostnames, select this check box. No Timestamp Suppresses the display of packet header timestamps. To stop displaying timestamps in the captured packet headers, select this check box. Write Packet Capture File Writes the captured packets to a file in PCAP format in /var/tmp. The files are named with the prefix jweb-pcap and the extension .pcap. If you select this option, the decoded packet headers are not displayed on the packet capture page. To decode and display the packet headers on the J-Web page, clear this check box. Related Documentation • Using the CLI Terminal on page 135 Monitoring System Properties Purpose Use the monitoring functionality to view system properties such as the name and IP address of the switch and resource usage. Action To monitor system properties in the J-Web interface, select Monitor > System View > System Information. To monitor system properties in the CLI, enter the following commands: Meaning • show system uptime • show system users • show system storage Table 79 on page 550 summarizes key output fields in the system properties display. Table 79: Summary of Key System Properties Output Fields Field Values Additional Information General Information Serial Number Serial number for the switch. Junos OS Version Version of Junos OS active on the switch, including whether the software is for domestic or export use. Hostname The name of switch. IP Address The IP address of the switch. 550 Export software is for use outside of the U.S. and Canada. Chapter 40: Administering and Monitoring System Functions Table 79: Summary of Key System Properties Output Fields (continued) Field Values Loopback Address The loopback address. Domain Name Server The address of the domain name server. Time Zone The time zone on the switch. Additional Information Time Current Time Current system time, in Coordinated Universal Time (UTC). System Booted Time Date and time when the switch was last booted and how long it has been running. Protocol Started Time Date and time when the switching protocols were last started and how long they have been running. Last Configured Time Date and time when a configuration was last committed. This field also shows the name of the user who issued the last commit command, through either the J-Web interface or the CLI. Load Average The CPU load average for 1, 5, and 15 minutes. Storage Media Internal Flash Memory Memory usage details of internal flash. External Flash Memory Usage details of external flash memory. Logged in Users Details User Username of any user logged in to the switching platform. Terminal Terminal through which the user is logged in. From System from which the user has logged in. A hyphen indicates that the user is logged in through the console. Login Time Time when the user logged in. This is the LOGIN@ field in show system users command output. 551 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 79: Summary of Key System Properties Output Fields (continued) Field Values Idle Time How long the user has been idle. Related Documentation Additional Information • Monitoring System Process Information on page 554 • Understanding J-Web User Interface Sessions on page 133 Monitoring Chassis Information Purpose Action Use the monitoring functionality to view chassis properties such as general switch information, temperature and fan status, and resource information for the J-EX Series switch. To view chassis properties in the J-Web interface, select Monitor > System View > Chassis Information. To view chassis properties in the CLI, enter the following commands: Meaning • show chassis environment • show chassis fpc • show chassis hardware Table 80 on page 552 gives information about the key output fields for chassis information. NOTE: For a J-EX4200 standalone switch, FPC refers to the switch itself. In a Virtual Chassis configuration, FPC refers to the member switch. In a J-EX8200 switch, FPC refers to the line card. Table 80: Summary of the Key Output Fields for Chassis Information Field Values Routing Engine Details Select the Master tab to view details about the master Routing Engine or select Backup to view details about the backup Routing Engine. 552 Chapter 40: Administering and Monitoring System Functions Table 80: Summary of the Key Output Fields for Chassis Information (continued) Field Values Name/Value This table displays the following details of the master Routing Engine: • Routing engine module • Model • Version • Part number • Serial number • Memory utilization • Temperature • Start time • CPU load average for 1, 5, and 15 minutes Power and Fan Tray Details Power Select the Power tab to view details of the power supplies. Name/Value Displays the status and model number of each power supply. Fan Select the Fan tab to view details about the fans. Name/Value Displays the status of each fan in the corresponding FPC. Chassis Component Details Select component Select an FPC to view General, Temperature, Resource, and Sub-component details. General Select the General tab to view the general information about the chassis components. Name/Value Displays general information: • Version—Revision level. Supply the version number when reporting hardware problems to customer support. • Part Number • Serial Number—Supply the serial number when contacting customer support about the switch chassis. • Description—Brief text description. Temperature Select the Temperature tab to view the temperature details of the components in the selected FPC. Name/Value Displays the temperature details of the sensors present in the selected FPC. Resource Select the Resource tab to view the resource details of the selected FPC. 553 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 80: Summary of the Key Output Fields for Chassis Information (continued) Field Values Name/Value Displays resource details: • State: • Dead—Held in reset because of errors. • Diag—The FPC is running diagnostics. • Dormant—Held in reset. • Empty—No FPC is present. • Online—The FPC is online and running. • Probed—Probe is complete. The FPC is awaiting restart of the Packet Forwarding Engine (PFE). • Related Documentation Probe-wait—The FPC is waiting for the probe operation to start. • Total CPU DRAM—Total DRAM, in megabytes, available to the FPC. • Start time—Date and time the switch was last rebooted. • Monitoring System Process Information on page 554 • Monitoring System Properties on page 550 • Dashboard for J-EX Series Switches on page 534 Monitoring System Process Information Purpose Action Use the monitoring functionality to view the processes running on the switch. To view the software processes running on the switch in the J-Web interface, select Monitor>System View>Process Details. To view the software processes running on the switch in the CLI, enter the following command. show system processes Meaning Table 81 on page 555 summarizes the output fields in the system process information display. The display includes the total CPU load and total memory utilization. 554 Chapter 40: Administering and Monitoring System Functions Table 81: Summary of System Process Information Output Fields Field Values PID Identifier of the process. Name Owner of the process. State Current state of the process. CPU Load Percentage of the CPU that is being used by the process. Memory Utilization Amount of memory that is being used by the process. Start Time Time of day when the process started. Related Documentation • Monitoring System Properties on page 550 • For more information about show system properties command, see show system uptime on page 842 Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure) You can use the J-Web interface to rotate log files and delete unnecessary log, temporary, and crash files on the switching platform. 1. Cleaning Up Files on page 555 2. Downloading Files on page 556 3. Deleting Files on page 556 Cleaning Up Files If you are running low on storage space, use the file cleanup procedure to quickly identify files to delete. The file cleanup procedure performs the following tasks: • Rotates log files—Archives the current log files, and creates fresh log files. • Deletes log files in /var/log—Deletes files that are not currently being written to. • Deletes temporary files in /var/tmp—Deletes files that have not been accessed within two days. • Deletes all crash files in /var/crash—Deletes core files that the switch has written during an error. To rotate log files and delete unnecessary files with the J-Web interface: 1. Select Maintain>Files. 555 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2. In the Clean Up Files section, click Clean Up Files. The switching platform rotates log files and identifies files that can be safely deleted. The J-Web interface displays the files that you can delete and the amount of space that will be freed on the file system. 3. Click one: • To delete the files and return to the Files page, click OK. • To cancel your entries and return to the list of files in the directory, click Cancel. Downloading Files You can use the J-Web interface to download a copy of an individual log, temporary, or crash file from the switching platform. When you download a file, it is not deleted from the file system. To download files with the J-Web interface: 1. In the J-Web interface, select Maintain>Files. 2. In the Download and Delete Files section, click one: • Log Files—Log files in the /var/log directory on the switch. • Temporary Files—Lists the temporary files in the /var/tmp directory on the switching platform. • Jailed Temporary Files (Install, Session, etc)—Lists the files in the /var/jail/tmp directory on the switching platform. • Crash (Core) Files—Lists the core files in the /var/crash directory on the switching platform. The J-Web interface displays the files located in the directory. 3. Select the files that you want to download and click Download. 4. Choose a location for the saved file. The file is saved as a text file, with a .txt file extension. Deleting Files You can use the J-Web interface to delete an individual log, temporary, and crash file from the switching platform. When you delete the file, it is permanently removed from the file system. CAUTION: If you are unsure whether to delete a file from the switching platform, we recommend using the Clean Up Files tool described in Cleaning Up Files. This tool determines which files can be safely deleted from the file system. 556 Chapter 40: Administering and Monitoring System Functions To delete files with the J-Web interface: 1. Select Maintain>Files. 2. In the Download and Delete Files section, click one: • Log Files—Lists the log files in the /var/log directory on the switching platform. • Temporary Files—Lists the temporary files in the /var/tmp directory on the switching platform. • Jailed Temporary Files (Install, Session, etc)—Lists the files in the /var/jail/tmp directory on the switching platform. • Crash (Core) Files—Lists the core files in the /var/crash directory on the switching platform. The J-Web interface displays the files in the directory. 3. Select the box next to each file you plan to delete. 4. Click Delete. The J-Web interface displays the files you can delete and the amount of space that will be freed on the file system. 5. Click one of the following buttons on the confirmation page: • To delete the files and return to the Files page, click OK. • To cancel your entries and return to the list of files in the directory, click Cancel. 557 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 558 CHAPTER 41 Configuration Statements for System Monitoring 559 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS archive (All System Log Files) Syntax Hierarchy Level Release Information Description Options archive ; [edit system syslog] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure archiving properties for all system log files. files number—Maximum number of archived log files to retain. When the Junos OS logging utility has written a defined maximum amount of data to a log file logfile, it closes the file, compresses it, and renames it to logfile.0.gz (the amount of data is determined by the size statement at this hierarchy level). The utility then opens and writes to a new file called logfile. When the new file reaches the maximum size, the logfile.0.gz file is renamed to logfile.1.gz, and the new file is closed, compressed, and renamed logfile.0.gz. By default, the logging facility creates up to ten archive files in this manner. Once the maximum number of archive files exists, each time the active log file reaches the maximum size, the contents of the oldest archive file are lost (overwritten by the next oldest file). Range: 1 through 1000 Default: 10 files size size—Maximum amount of data that the Junos OS logging utility writes to a log file logfile before archiving it (closing it, compressing it, and changing its name to logfile.0.gz). The utility then opens and writes to a new file called logfile. Syntax: xk to specify the number of kilobytes, xm for the number of megabytes, or xg for the number of gigabytes Range: 64 KB through 1 GB world-readable | no-world-readable—Grant all users permission to read archived log files, or restrict the permission only to the root user and users who have the Junos OS maintenance permission. Default: no-world-readable Required Privilege Level Related Documentation 560 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Specifying Log File Size, Number, and Archiving Properties Chapter 41: Configuration Statements for System Monitoring archive-sites Syntax Hierarchy Level Release Information Description Options archive-sites { url ; } [edit event-options destinations destination-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify an archive site to which files are transferred. If you specify more than one archive site, the router or switch attempts to transfer to the first archive site in the list, moving to the next site only if the transfer fails. url—The archive destination specified as Hypertext Transfer Protocol (HTTP) URL, FTP URL, or secure copy (scp)-style remote file specification. URLs of the type file:// are not supported; however, local router or switch directories are supported (for example, /var/tmp/). password password—A plain-text password for login into the archive site. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Defining Destinations for File Archiving by Event Policies arguments Syntax Hierarchy Level Release Information Description Options arguments { argument-name argument-value; } [edit event-options policy policy-name then event-script filename] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define command-line arguments for an event script that is invoked from an event policy. argument-name—Name of the argument. argument-value—Value of the argument. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Executing Event Scripts in an Event Policy 561 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS attributes-match Syntax Hierarchy Level Release Information Description attributes-match { event1.attribute-name equals event2.attribute-name; event.attribute-name matches regular-expression; event1.attribute-name starts-with event2.attribute-name; } [edit event-options policy policy-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Execute the policy only if the attributes of two events are correlated or if the attribute of one event matches a regular expression. If the attributes-match statement includes the equals or starts-with options, or if it includes a matches option that includes a clause for an event that is not specified at the [edit event-options policy policy-name events] hierarchy level, you must include one or more within statements in the same policy configuration. The statements are explained separately. Required Privilege Level Related Documentation 562 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using Correlated Events to Trigger an Event Policy • within on page 608 Chapter 41: Configuration Statements for System Monitoring commands Syntax Hierarchy Level Release Information Description Options commands { "command"; } [edit event-options policy policy-name then execute-commands] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify an operational mode command to be issued on receipt of an event. command—Command to be issued. Enclose each command in quotation marks (“ ”). The event process (eventd) issues the commands in the order in which they appear in the configuration. You can include variables in commands. The eventd process replaces each variable with values contained in the event that triggers the policy. You can use command variables of the following forms: • {$$.attribute-name}—The double dollar sign ($$) notation represents the event that is triggering a policy. When combined with an attribute name, the command variable is replaced by the value of the attribute name of the triggering event. • {$event.attribute-name}—The dollar sign with the event name ($event) notation represents the most recent event that matches the specified event. The variable is replaced by the value of the attribute name of the most recent event that matches event. • {$*.attribute-name}—The dollar sign with the asterisk ($*) notation represents the most recent event that matches any of the correlating events. The variable is replaced by the value of the attribute name of the most recent event that matches any of the events specified in the policy configuration. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Execute Operational Mode Commands • Representing the Correlating Event in an Event Policy 563 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS console (System Logging) Syntax Hierarchy Level Release Information Description Options console { facility severity; } [edit system syslog] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the logging of system messages to the system console. facility—Class of messages to log. To specify multiple classes, include multiple facility severity statements. For a list of the facilities, see Junos OS System Logging Facilities and Message Severity Levels. severity—Severity of the messages that belong to the facility specified by the paired facility name. Messages with severities the specified level and higher are logged. For a list of the severities, see Junos OS System Logging Facilities and Message Severity Levels. Required Privilege Level Related Documentation 564 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Directing System Log Messages to the Console • Junos OS System Log Messages Reference Chapter 41: Configuration Statements for System Monitoring destination Syntax Hierarchy Level Release Information Description Options destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } [edit event-options policy policy-name then event-script filename], [edit event-options policy policy-name then execute-commands] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Assign a location to which to upload command or script output for the specified policy. destination-name—Name of a destination defined in the destinations statement at the [edit event-options] hierarchy level. The remaining statements are explained separately. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Execute Operational Mode Commands • Executing Event Scripts in an Event Policy • destinations on page 566 565 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS destinations Syntax Hierarchy Level Release Information Description Options destinations { destination-name { archive-sites { url ; } transfer-delay seconds; } } [edit event-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define one or more destinations, each with a unique name and other attributes. You can use the destination as a storage location for command output and for various files, such as system log files and core files. destination-name—Name of a destination. The remaining statements are explained separately. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Defining Destinations for File Archiving by Event Policies equals Syntax Hierarchy Level Release Information Description Options event1.attribute-name equals event2.attribute-name; [edit event-options policy policy-name attributes-match] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Execute the policy only if the specified attribute of event1 equals the specified attribute of event2. event1.attribute-name—Attribute of one event. event2.attribute-name—Attribute of another event. Required Privilege Level Related Documentation 566 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using Correlated Events to Trigger an Event Policy Chapter 41: Configuration Statements for System Monitoring event-options Syntax event-options { destinations { destination-name { archive-sites { url ; } transfer-delay seconds; } } event-script { file filename { checksum (md5 | sha-256 | sha1) hash; refresh; refresh-from url; remote-execution { remote-hostname { passphrase user-password; username user-login; } } source url; } refresh; refresh-from url; traceoptions { file ; flag flag; no-remote-trace; } } generate-event event-name { time-interval seconds; time-of-day hh:mm:ss; } policy policy-name { attributes-match { event1.attribute-name equals event2.attribute-name; event.attribute-name matches regular-expression; event1.attribute-name starts-with event2.attribute-name; } events [ events ]; within seconds not events [ events ]; then { event-script filename { arguments { argument-name argument-value; } output-filename filename; destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } 567 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } execute-commands { commands { "command"; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } ignore; raise-trap; upload filename (filename | committed) destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; user-name username; } } } traceoptions { file filename ; flag flag; } } Hierarchy Level Release Information Description [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure event policies. The statements are explained separately. Required Privilege Level 568 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. Chapter 41: Configuration Statements for System Monitoring events (Associating Events with a Policy) Syntax Hierarchy Level Release Information events [ events ]; [edit event-options policy policy-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Create a list of events that trigger this policy. If one or more of the listed events occurs, the policy is executed. Options [ events ]—List of events. Events can be internally generated, or they can be generated by Junos OS processes. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using Correlated Events to Trigger an Event Policy events (Correlating Events with Each Other) Syntax Hierarchy Level Release Information events [ events ]; [edit event-options policy policy-name within seconds] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Create a list of events that must occur within a specified time interval for the policy to be triggered. Options [ events ]—List of events. Events can be internally generated, or they can be generated by Junos OS processes. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using Correlated Events to Trigger an Event Policy 569 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS event-script Syntax Hierarchy Level Release Information Description event-script { file filename { checksum (md5 | sha-256 | sha1) hash; refresh; refresh-from url; remote-execution { remote-hostname { passphrase user-password; username user-login; } } source url; } refresh; refresh-from url; traceoptions { file ; flag flag; no-remote-trace; } } [edit event-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Junos OS event scripts, configure scripting mechanisms. The statements are explained separately. Required Privilege Level Related Documentation 570 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Implementing Event Scripts Chapter 41: Configuration Statements for System Monitoring event-script Syntax Hierarchy Level Release Information Description event-script filename { arguments { argument-name argument-value; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } [edit event-options policy policy-name then] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On receipt of an event, specify operational mode commands to be issued, the format of the command output, and a name and destination for the output file. The statements are explained separately. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Executing Event Scripts in an Event Policy 571 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS execute-commands Syntax Hierarchy Level Release Information Description execute-commands { commands { "command"; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } [edit event-options policy policy-name then] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On receipt of an event, specify operational mode commands to be issued, the format of the command output, and a name and destination for the output file. The statements are explained separately. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Execute Operational Mode Commands explicit-priority Syntax Hierarchy Level Release Information Description explicit-priority; [edit system syslog file filename], [edit system syslog host] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Record the priority (facility and severity level) in each standard-format system log message directed to a file or remote destination. When the structured-data statement is also included at the [edit system syslog file filename] hierarchy level, this statement is ignored for the file. Required Privilege Level Related Documentation 572 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Including Priority Information in System Log Messages • Junos OS System Log Messages Reference • structured-data on page 590 Chapter 41: Configuration Statements for System Monitoring facility-override Syntax Hierarchy Level Release Information Description Options facility-override facility; [edit system syslog host] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Substitute an alternate facility for the default facilities used when messages are directed to a remote destination. facility—Alternate facility to substitute for the default facilities. For a list of the possible facilities, see Junos OS System Log Alternate Facilities for Remote Logging. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Changing the Alternative Facility Name for Remote System Log Messages • Junos OS System Log Messages Reference 573 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file Syntax Hierarchy Level Release Information Description Options file filename { checksum (md5 | sha-256 | sha1) hash; refresh; refresh-from url; remote-execution { remote-hostname { passphrase user-password; username user-login; } } source url; } [edit event-options event-script] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Junos OS event scripts, enable an event script that is located in the /var/db/scripts/event directory. filename—The name of an Extensible Stylesheet Language Transformations (XSLT) or Stylesheet Language Alternative Syntax (SLAX) file containing an event script. The statements are explained separately. Required Privilege Level Related Documentation 574 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Enabling an Event Script Chapter 41: Configuration Statements for System Monitoring file (System Logging) Syntax Hierarchy Level Release Information Description Options file filename { facility severity; archive { files number; size size; (no-world-readable | world-readable); } explicit-priority; match "regular-expression"; structured-data { brief; } } [edit system syslog] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the logging of system messages to a file. facility—Class of messages to log. To specify multiple classes, include multiple facility severity statements. For a list of the facilities, see Junos OS System Logging Facilities and Message Severity Levels. file filename—File in the /var/log directory in which to log messages from the specified facility. To log messages to more than one file, include more than one file statement. severity—Severity of the messages that belong to the facility specified by the paired facility name. Messages with severities the specified level and higher are logged. For a list of the severities, see Junos OS System Logging Facilities and Message Severity Levels. 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. • Directing System Log Messages to a Log File • Junos OS System Log Messages Reference 575 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS files Syntax Hierarchy Level Release Information Description Options files number; [edit system syslog archive], [edit system syslog file filename archive] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the maximum number of archived log files to retain. When the Junos OS logging utility has written a defined maximum amount of data to a log file logfile, it closes the file, compresses it, and renames it to logfile.0.gz (for information about the maximum file size, see size). The utility then opens and writes to a new file called logfile. When the new file reaches the maximum size, the logfile.0.gz file is renamed to logfile.1.gz, and the new file is closed, compressed, and renamed logfile.0.gz. By default, the logging facility creates up to ten archive files in this manner. Once the maximum number of archive files exists, each time the active log file reaches the maximum size, the contents of the oldest archive file are lost (overwritten by the next oldest file). number—Maximum number of archived files. Range: 1 through 1000 Default: 10 files Required Privilege Level Related Documentation 576 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Specifying Log File Size, Number, and Archiving Properties • Junos OS System Log Messages Reference • size on page 588 Chapter 41: Configuration Statements for System Monitoring generate-event Syntax Hierarchy Level Release Information Description Options generate-event event-name { time-interval seconds; time-of-day hh:mm:ss; } [edit event-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Generate an internal event, based on a time interval or the time of day. event-name—Name of an internally generated event. The statements are explained separately. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Generating Internal Events to Trigger Event Policies 577 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS host Syntax host (hostname | other-routing-engine) { facility severity; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; } J-EX Series Switches host (hostname | other-routing-engine | scc-master) { facility severity; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; } TX Matrix Plus Router host (hostname | other-routing-engine | sfc0-master) { facility severity; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; } Hierarchy Level Release Information Description Options [edit system syslog] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the logging of system messages to a remote destination. facility—Class of messages to log. To specify multiple classes, include multiple facility severity statements. For a list of the facilities, see Junos OS System Logging Facilities and Message Severity Levels. hostname—IPv4 address, IPv6 address, or fully qualified hostname of the remote machine to which to direct messages. To direct messages to multiple remote machines, include a host statement for each one. other-routing-engine—Direct messages to the other Routing Engine on a router or switch with two Routing Engines installed and operational. severity—Severity of the messages that belong to the facility specified by the paired facility name. Messages with severities the specified level and higher are logged. For a list of the severities, see Junos OS System Logging Facilities and Message Severity Levels. The remaining statements are explained separately. Required Privilege Level 578 system—To view this statement in the configuration. system-control—To add this statement to the configuration. Chapter 41: Configuration Statements for System Monitoring Related Documentation • Directing System Log Messages to a Remote Machine or the Other Routing Engine • Junos OS System Log Messages Reference ignore Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation ignore; [edit event-options policy policy-name then] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a policy that ignores particular events. If one or more of the listed events occur, a system log message for the event is not generated, and no further policies associated with this event are processed. If you include the ignore statement in a policy configuration, you cannot configure any other actions in the policy. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring Event Policies to Ignore an Event interface (Accounting or Sampling) Syntax Hierarchy Level Release Information Description Options interface interface-name { engine-id number; engine-type number; source-address address; } [edit forwarding-options accounting name output], [edit forwarding-optionssamplingoutput] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the output interface for monitored traffic. interface-name—Name of the interface. The remaining statements are explained separately. Usage Guidelines Required Privilege Level See Configuring Discard Accounting or Configuring Traffic Sampling. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. 579 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS log-prefix Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation log-prefix string; [edit system syslog host] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Include a text string in each message directed to a remote destination. string—Text string to include in each message. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Adding a Text String to System Log Messages • Junos OS System Log Messages Reference match Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 580 match "regular-expression"; [edit system syslog file filename], [edit system syslog host hostname | other-routing-engine| scc-master)], [edit system syslog user (username | *)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a text string that must (or must not) appear in a message for the message to be logged to a destination. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Using Regular Expressions to Refine the Set of Logged Messages Chapter 41: Configuration Statements for System Monitoring not Syntax Hierarchy Level Release Information Description Options not events [ events ]; [edit event-options policy policy-name within seconds] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Create a list of events that must not occur within the specified time interval for the policy to be triggered. [ events ]—List of events. Events can be internally generated, or they can be generated by Junos OS processes. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using Correlated Events to Trigger an Event Policy output-filename Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation output-filename filename; [edit event-options policy policy-name then event-script filename], [edit event-options policy policy-name then execute-commands] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Assign a filename to which to write command or script output for the specified commands or script. For op scripts, this statement is optional. filename—Name of a file in which to write command or script output. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Execute Operational Mode Commands • Executing Event Scripts in an Event Policy 581 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS output-format Syntax Hierarchy Level Release Information Description Options output-format (text | xml); [edit event-options policy policy-name then event-script filename], [edit event-options policy policy-name then execute-commands] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the format (ASCII text or XML) for the output of the specified commands or script. text—Formatted ASCII text. xml—Junos Extensible Markup Language (XML) tags. Default: xml at the [edit event-options policy policy-name then execute-commands] hierarchy level and text at the [edit event-options policy policy-name then event-script filename] hierarchy level. Required Privilege Level Related Documentation 582 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Execute Operational Mode Commands • Executing Event Scripts in an Event Policy Chapter 41: Configuration Statements for System Monitoring policy Syntax policy policy-name { attributes-match { event1.attribute-name equals event2.attribute-name; event.attribute-name matches regular-expression; event1.attribute-name starts-with event2.attribute-name; } events [ events ]; then { ... the then subhierarchy appears at the end of the [edit event-options policy policy-name] hierarchy level ... } within seconds { events [ events ]; not events [ events ]; trigger (on | after | until) event-count; } then { event-script filename { arguments { argument-name argument-value; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } execute-commands { commands { "command"; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } ignore; raise-trap; upload filename (filename | committed) destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; user-name username; } } } 583 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Hierarchy Level Release Information Description [edit event-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define an event policy to be processed by the eventd process. If you configure a policy, the events and then statements are mandatory. You can configure multiple policies to be processed for an event. The policies are executed in the order in which they appear in the configuration. If you configure more than one policy for an event, and if one of the policies is to ignore the event, no policies that follow the ignore statement are executed. Default Options If you do not configure a policy for an event, the event is recorded in the system log. policy-name—Name of an event policy. The statements are explained separately. Required Privilege Level maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. raise-trap Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 584 raise-trap; [edit event-options policy policy-name then] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a policy that raises an SNMP trap in response to an event. If one or more of the listed events occur, the system log message for the event is converted into a trap. This enables an agent to notify a trap-based network management system (NMS) of significant events. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring Event Policies to Raise SNMP Traps Chapter 41: Configuration Statements for System Monitoring refresh Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation refresh; [edit event-options event-script], [edit event-options event-script file filename] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Junos OS event scripts, overwrite the local copy of all enabled event scripts or a single enabled script located in the /var/db/scripts/event directory with the copy located at the source URL, specified in the source statement at the same hierarchy level. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Updating an Event Script from the Master Source • refresh-from on page 585 • source on page 589 refresh-from Syntax Hierarchy Level Release Information refresh-from url; [edit event-options event-script], [edit event-options event-script file filename] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description For Junos OS event scripts, overwrite the local copy of all enabled event scripts or a single enabled script located in the /var/db/scripts/event directory with the copy located at a URL other than the URL specified in the source statement. Options url—Source specified as a Hypertext Transfer Protocol (HTTP) URL, FTP URL, or secure copy (scp)-style remote file specification. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Updating an Event Script from an Alternate Location • refresh on page 585 • source on page 589 585 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS remote-execution Syntax Hierarchy Level Release Information Description Options remote-execution { remote-hostname { passphrase user-password; username user-login; } } [edit event-options event-script file filename] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Junos OS event scripts, enable event scripts to invoke RPCs on a local or remote host. passphrase user-password—User’s password for the remote host. remote-hostname—Name of the remote host with which the event script will communicate. username username—User’s login name for the remote host. Required Privilege Level Related Documentation 586 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using RPCs and Operational Mode Commands in Event Scripts Chapter 41: Configuration Statements for System Monitoring retry-count Syntax Hierarchy Level Release Information Description Default Options retry-count number retry-interval seconds; [edit event-options policy policy-name then event-script filename destination destination-name], [edit event-options policy policy-name then execute-commands destination destination-name], [edit event-options policy policy-name then upload filename (filename | committed) destination destination-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an event policy to retry a file upload operation if the first attempt fails. If you do not include this statement, the file upload operation is attempted one time only. number—Number of retries. retry-interval seconds—Length of time to wait between retries. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Retry the File Upload Action 587 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS size Syntax Hierarchy Level Release Information Description Options size size; [edit system syslog archive], [edit system syslog file filename archive] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the maximum amount of data that the Junos OS logging utility writes to a log file logfile before archiving it (closing it, compressing it, and changing its name to logfile.0.gz). The utility then opens and writes to a new file called logfile. For information about the number of archive files that the utility creates in this way, see files. size—Maximum size of each system log file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). Syntax: xk to specify the number of kilobytes, xm for the number of megabytes, or xg for the number of gigabytes Range: 64 KB through 1 GB Default: 1 MB for MX Series routers Required Privilege Level Related Documentation 588 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Specifying Log File Size, Number, and Archiving Properties • Junos OS System Log Messages Reference • files on page 576 Chapter 41: Configuration Statements for System Monitoring source Syntax Hierarchy Level Release Information Description Options source url; [edit event-options event-script file filename] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Junos OS event scripts, specify the location of the source file for an enabled script located in the /var/db/scripts/event directory. When you include the refresh statement at the same hierarchy level, the local copy is overwritten by the version stored at the specified URL. url—Master source file for an event script specified as an HTTP URL, FTP URL, or scp-style remote file specification. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • refresh on page 585 • refresh-from on page 585 • Specifying a Master Source for an Event Script 589 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS structured-data Syntax Hierarchy Level Release Information Description structured-data { brief; } [edit system syslog file filename] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Write system log messages to the log file in structured-data format, which complies with Internet draft draft-ietf-syslog-protocol-23, The syslog Protocol (http://tools.ietf.org/html/draft-ietf-syslog-protocol-23). NOTE: When this statement is included, other statements that specify the format for messages written to the file are ignored (the explicit-priority statement at the [edit system syslog file filename] hierarchy level and the time-format statement at the [edit system syslog] hierarchy level). Required Privilege Level Related Documentation 590 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Logging Messages in Structured-Data Format • Junos OS System Log Messages Reference • explicit-priority on page 572 • time-format on page 594 Chapter 41: Configuration Statements for System Monitoring syslog Syntax Hierarchy Level Release Information Description syslog { archive { files number; size maximum-file-size; start-time "YYYY-MM-DD.hh:mm"; transfer-interval minutes; (world-readable | no-world-readable); } console { facility severity; } file filename { facility severity; explicit-priority; match "regular-expression"; archive { files number; size maximum-file-size; start-time "YYYY-MM-DD.hh:mm"; transfer-interval minutes; (world-readable | no-world-readable); } structured-data { brief; } } host (hostname | other-routing-engine | scc-master) { facility severity; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; } source-address source-address; time-format (millisecond | year | year millisecond); user (username | *) { facility severity; match "regular-expression"; } } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the types of system log messages to log to files, a remote destination, user terminals, or the system console. The remaining statements are explained separately. 591 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation 592 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Junos OS System Log Configuration Overview • Junos OS System Log Messages Reference Chapter 41: Configuration Statements for System Monitoring then Syntax Hierarchy Level Release Information Description then { event-script filename { arguments { argument-name argument-value; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } execute-commands { commands { "command"; } destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; } output-filename filename; output-format (text | xml); user-name username; } ignore; raise-trap; upload filename (filename | committed) destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; user-name username; } } [edit event-options policy policy-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define actions to take if an event occurs. For each policy, you can configure multiple actions. The statements are explained separately. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Configuring an Event Policy to Upload Files • Configuring an Event Policy to Execute Operational Mode Commands • Executing Event Scripts in an Event Policy 593 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring Event Policies to Ignore an Event • Configuring Event Policies to Raise SNMP Traps time-format Syntax Hierarchy Level Release Information Description time-format (year | millisecond | year millisecond); [edit system syslog] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Include the year, the millisecond, or both, in the timestamp on every standard-format system log message. The additional information is included for messages directed to each destination configured by a file, console, or user statement at the [edit system syslog] hierarchy level, but not to destinations configured by a host statement. By default, the timestamp specifies the month, date, hour, minute, and second when the message was logged—for example, Aug 21 12:36:30. NOTE: When the structured-data statement is included at the [edit system syslog file filename] hierarchy level, this statement is ignored for the file. Options millisecond—Include the millisecond in the timestamp. year—Include the year in the timestamp. Required Privilege Level Related Documentation 594 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Including the Year or Millisecond in Timestamps • Junos OS System Log Messages Reference • structured-data on page 590 Chapter 41: Configuration Statements for System Monitoring time-interval Syntax Hierarchy Level Release Information Description Options time-interval seconds; [edit event-options generate-event event-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a frequency at which to generate a particular event. seconds—Time interval between internally generated events. Range: 60 through 604,800 seconds Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Generating Internal Events to Trigger Event Policies time-of-day Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation time-of-day hh:mm:ss; [edit event-options generate-event event-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a time of day at which to generate a particular event. hh:mm:ss—Time of day at which to generate an event. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Generating Internal Events to Trigger Event Policies 595 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS time-zone Syntax Hierarchy Level Release Information Description Default Options time-zone (GMT hour-offset | time-zone); [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the local time zone. To have the time zone change take effect for all processes running on the router or switch, you must reboot the router or switch. UTC GMT hour-offset—Set the time zone relative to UTC time. Range: –14 through +12 Default: 0 time-zone—Specify the time zone as UTC, which is the default time zone, or as a string such as PDT (Pacific Daylight Time), or use one of the following continents and major cities: Africa/Abidjan, Africa/Accra, Africa/Addis_Ababa, Africa/Algiers, Africa/Asmera, Africa/Bamako, Africa/Bangui, Africa/Banjul, Africa/Bissau, Africa/Blantyre, Africa/Brazzaville, Africa/Bujumbura, Africa/Cairo, Africa/Casablanca, Africa/Ceuta, Africa/Conakry, Africa/Dakar, Africa/Dar_es_Salaam, Africa/Djibouti, Africa/Douala, Africa/El_Aaiun, Africa/Freetown, Africa/Gaborone, Africa/Harare, Africa/Johannesburg, Africa/Kampala, Africa/Khartoum, Africa/Kigali, Africa/Kinshasa, Africa/Lagos, Africa/Libreville, Africa/Lome, Africa/Luanda, Africa/Lubumbashi, Africa/Lusaka, Africa/Malabo, Africa/Maputo, Africa/Maseru, Africa/Mbabane, Africa/Mogadishu, Africa/Monrovia, Africa/Nairobi, Africa/Ndjamena, Africa/Niamey, Africa/Nouakchott, Africa/Ouagadougou, Africa/Porto-Novo, Africa/Sao_Tome, Africa/Timbuktu, Africa/Tripoli, Africa/Tunis, Africa/Windhoek America/Adak, America/Anchorage, America/Anguilla, America/Antigua, America/Aruba, America/Asuncion, America/Barbados, America/Belize, America/Bogota, America/Boise, America/Buenos_Aires, America/Caracas, America/Catamarca, America/Cayenne, America/Cayman, America/Chicago, America/Cordoba, America/Costa_Rica, America/Cuiaba, America/Curacao, America/Dawson, America/Dawson_Creek, America/Denver, America/Detroit, America/Dominica, America/Edmonton, America/El_Salvador, America/Ensenada, America/Fortaleza, America/Glace_Bay, America/Godthab, America/Goose_Bay, America/Grand_Turk, America/Grenada, America/Guadeloupe, America/Guatemala, America/Guayaquil, America/Guyana, America/Halifax, America/Havana, America/Indiana/Knox, America/Indiana/Marengo, America/Indiana/Vevay, America/Indianapolis, America/Inuvik, America/Iqaluit, America/Jamaica, America/Jujuy, America/Juneau, America/La_Paz, America/Lima, America/Los_Angeles, America/Louisville, America/Maceio, America/Managua, America/Manaus, America/Martinique, America/Mazatlan, America/Mendoza, America/Menominee, America/Mexico_City, America/Miquelon, America/Montevideo, America/Montreal, America/Montserrat, America/Nassau, America/New_York, America/Nipigon, America/Nome, America/Noronha, America/Panama, America/Pangnirtung, America/Paramaribo, America/Phoenix, America/Port-au-Prince, America/Port_of_Spain, America/Porto_Acre, America/Puerto_Rico, America/Rainy_River, America/Rankin_Inlet, America/Regina, America/Rosario, America/Santiago, 596 Chapter 41: Configuration Statements for System Monitoring America/Santo_Domingo, America/Sao_Paulo, America/Scoresbysund, America/Shiprock, America/St_Johns, America/St_Kitts, America/St_Lucia, America/St_Thomas, America/St_Vincent, America/Swift_Current, America/Tegucigalpa, America/Thule, America/Thunder_Bay, America/Tijuana, America/Tortola, America/Vancouver, America/Whitehorse, America/Winnipeg, America/Yakutat, America/Yellowknife Antarctica/Casey, Antarctica/DumontDUrville, Antarctica/Mawson, Antarctica/McMurdo, Antarctica/Palmer, Antarctica/South_Pole Arctic/Longyearbyen Asia/Aden, Asia/Alma-Ata, Asia/Amman, Asia/Anadyr, Asia/Aqtau, Asia/Aqtobe, Asia/Ashkhabad, Asia/Baghdad, Asia/Bahrain, Asia/Baku, Asia/Bangkok, Asia/Beirut, Asia/Bishkek, Asia/Brunei, Asia/Calcutta, Asia/Chungking, Asia/Colombo, Asia/Dacca, Asia/Damascus, Asia/Dubai, Asia/Dushanbe, Asia/Gaza, Asia/Harbin, Asia/Hong_Kong, Asia/Irkutsk, Asia/Ishigaki, Asia/Jakarta, Asia/Jayapura, Asia/Jerusalem, Asia/Kabul, Asia/Kamchatka, Asia/Karachi, Asia/Kashgar, Asia/Katmandu, Asia/Krasnoyarsk, Asia/Kuala_Lumpur, Asia/Kuching, Asia/Kuwait, Asia/Macao, Asia/Magadan, Asia/Manila, Asia/Muscat, Asia/Nicosia, Asia/Novosibirsk, Asia/Omsk, Asia/Phnom_Penh, Asia/Pyongyang, Asia/Qatar, Asia/Rangoon, Asia/Riyadh, Asia/Saigon, Asia/Seoul, Asia/Shanghai, Asia/Singapore, Asia/Taipei, Asia/Tashkent, Asia/Tbilisi, Asia/Tehran, Asia/Thimbu, Asia/Tokyo, Asia/Ujung_Pandang, Asia/Ulan_Bator, Asia/Urumqi, Asia/Vientiane, Asia/Vladivostok, Asia/Yakutsk, Asia/Yekaterinburg, Asia/Yerevan Atlantic/Azores, Atlantic/Bermuda, Atlantic/Canary, Atlantic/Cape_Verde, Atlantic/Faeroe, Atlantic/Jan_Mayen, Atlantic/Madeira, Atlantic/Reykjavik, Atlantic/South_Georgia, Atlantic/St_Helena, Atlantic/Stanley Australia/Adelaide, Australia/Brisbane, Australia/Broken_Hill, Australia/Darwin, Australia/Hobart, Australia/Lindeman, Australia/Lord_Howe, Australia/Melbourne, Australia/Perth, Australia/Sydney Europe/Amsterdam, Europe/Andorra, Europe/Athens, Europe/Belfast, Europe/Belgrade, Europe/Berlin, Europe/Bratislava, Europe/Brussels, Europe/Bucharest, Europe/Budapest, Europe/Chisinau, Europe/Copenhagen, Europe/Dublin, Europe/Gibraltar, Europe/Helsinki, Europe/Istanbul, Europe/Kaliningrad, Europe/Kiev, Europe/Lisbon, Europe/Ljubljana, Europe/London, Europe/Luxembourg, Europe/Madrid, Europe/Malta, Europe/Minsk, Europe/Monaco, Europe/Moscow, Europe/Oslo, Europe/Paris, Europe/Prague, Europe/Riga, Europe/Rome, Europe/Samara, Europe/San_Marino, Europe/Sarajevo, Europe/Simferopol, Europe/Skopje, Europe/Sofia, Europe/Stockholm, Europe/Tallinn, Europe/Tirane, Europe/Vaduz, Europe/Vatican, Europe/Vienna, Europe/Vilnius, Europe/Warsaw, Europe/Zagreb, Europe/Zurich Indian/Antananarivo, Indian/Chagos, Indian/Christmas, Indian/Cocos, Indian/Comoro, Indian/Kerguelen, Indian/Mahe, Indian/Maldives, Indian/Mauritius, Indian/Mayotte, Indian/Reunion Pacific/Apia, Pacific/Auckland, Pacific/Chatham, Pacific/Easter, Pacific/Efate, Pacific/Enderbury, Pacific/Fakaofo, Pacific/Fiji, Pacific/Funafuti, Pacific/Galapagos, Pacific/Gambier, Pacific/Guadalcanal, Pacific/Guam, Pacific/Honolulu, Pacific/Johnston, Pacific/Kiritimati, Pacific/Kosrae, Pacific/Kwajalein, Pacific/Majuro, Pacific/Marquesas, Pacific/Midway, Pacific/Nauru, Pacific/Niue, Pacific/Norfolk, Pacific/Noumea, Pacific/Pago_Pago, Pacific/Palau, Pacific/Pitcairn, Pacific/Ponape, Pacific/Port_Moresby, Pacific/Rarotonga, Pacific/Saipan, Pacific/Tahiti, Pacific/Tarawa, Pacific/Tongatapu, Pacific/Truk, Pacific/Wake, Pacific/Wallis, Pacific/Yap Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Modifying the Default Time Zone for a Router or Switch Running Junos OS • System Management Configuration Statements 597 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions Syntax Hierarchy Level Release Information Description traceoptions { file ; flag flag; no-remote-trace; } [edit event-options event-script] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for event scripts. Default If you do not include this statement, no event script–specific tracing operations are performed. Options filename—Name of the file to receive the output of the tracing operation. All files are placed in the directory /var/log. By default, event script process tracing output is placed in the file escript.log. If you include the file statement, you must specify a filename. To retain the default, you can specify escript.log as the filename. files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed and compressed to trace-file.0.gz, then trace-file.1.gz, 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 also must specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 10 files flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—Log all operations • events—Log important events • input—Log event script input data • offline—Generate data for offline development • output—Log event script output data • rpc—Log event script RPCs • xslt—Log the XSLT library no-world-readable—Restrict file access to owner. This is the default. 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 598 Chapter 41: Configuration Statements for System Monitoring and compressed to trace-file.0.gz. When trace-file again reaches its maximum size, trace-file.0.gz is renamed trace-file.1.gz and trace-file is renamed and compressed to trace-file.0.gz. 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 a 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—Enable unrestricted file access. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Tracing Event Script Processing 599 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions Syntax Hierarchy Level Release Information Description traceoptions { file ; flag flag; no-remote-trace; } [edit event-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for event policies. Default If you do not include this statement, no event-policy-specific tracing operations are performed. Options filename—Name of the file to receive the output of the tracing operation. All files are placed in the directory /var/log. By default, commit script process tracing output is placed in the file eventd. If you include the file statement, you must specify a filename. To retain the default, you can specify eventd as the filename. files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed and compressed to trace-file.0.gz, then trace-file.1.gz, 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 also must specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 3 files flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—Log all operations • configuration—Log reading of configuration at the [edit event-options] hierarchy level • events—Log eventd processing • database—Log events involving storage and retrieval in events database • server—Log communication with processes that are generating events • timer-events—Log internally generated events match regular-expression—(Optional) Refine the output to include lines that contain the regular expression. no-world-readable—Restrict file access to owner. This is the default. 600 Chapter 41: Configuration Statements for System Monitoring 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 and compressed to trace-file.0.gz. When the trace-file again reaches its maximum size, trace-file.0.gz is renamed trace-file.1.gz and trace-file is renamed and compressed to trace-file.0.gz. 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. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Tracing Event Policy Processing 601 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions (Commit and Op Scripts) Syntax Hierarchy Level Release Information Description Default Options traceoptions { file ; flag flag; no-remote-trace; } [edit system scripts commit], [edit system scripts op] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for commit or op scripts. If you do not include this statement, no script-specific tracing operations are performed. filename—Name of the file to receive the output of the tracing operation. All files are placed in the directory /var/log. By default, commit script process tracing output is placed in the file cscript.log and op script process tracing is placed in the file op-script.log. If you include the file statement, you must specify a filename. To retain the default, you can specify cscript.log or op-script.log as the filename. files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed and compressed to trace-file.0.gz, then trace-file.1.gz, 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 also must specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 10 files flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—Log all operations • events—Log important events • input—Log script input data • offline—Generate data for offline development • output—Log script output data • rpc—Log script RPCs • xslt—Log the XSLT library no-world-readable—Restrict file access to owner. This is the default. 602 Chapter 41: Configuration Statements for System Monitoring 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 and compressed to trace-file.0.gz. When trace-file again reaches its maximum size, trace-file.0.gz is renamed trace-file.1.gz and trace-file is renamed and compressed to trace-file.0.gz. 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 a 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—Enable unrestricted file access. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Tracing Commit Script Processing • Tracing Op Script Processing 603 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS transfer-delay Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation 604 transfer-delay seconds; [edit event-options destinations destination-name], [edit event-options policy policy-name then event-script filename destination destination-name], [edit event-options policy policy-name then execute-commands destination destination-name], [edit event-options policy policy-name then upload filename (filename | committed) destination destination-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a delay before transferring files. This allows the files to be completely generated before the upload starts. If you configure a transfer delay at the [edit event-options destination destination-name] hierarchy level and at one of the [edit event-options policy policy-name then ...] hierarchy levels, the resulting delay is the sum of the two delays. If you do not include this statement, there is no transfer delay. seconds—Duration of the delay before files are uploaded. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Defining Destinations for File Archiving by Event Policies • Configuring the Delay Before Files Are Uploaded by an Event Policy Chapter 41: Configuration Statements for System Monitoring trigger Syntax Hierarchy Level Release Information Description trigger (on | after | until) event-count; [edit event-options policy policy-name within seconds] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an event policy to be triggered if an event or set of events occurs event-count times within a specified time period. Default If you do not include this statement, the policy is executed on receipt of the first configured event. Options after event-count—The policy is executed when the number of matching events received equals event-count + 1. on event-count—The policy is executed when the number of matching events received equals event-count. until event-count—The policy is executed each time a matching event is received and stops being executed when the number of matching events received equals event-count. Required Privilege Level Related Documentation maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Triggering an Event Policy Based on Event Count 605 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS upload Syntax Hierarchy Level Release Information Description Options upload filename (filename | committed) destination destination-name { retry-count count retry-interval seconds; transfer-delay seconds; user-name username; } [edit event-options policy policy-name then] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On receipt of an event, upload the committed configuration file to a destination. destination destination-name—Name of the destination for the uploaded file. It must be defined in the destinations statement at the [edit event-options] hierarchy level. filename (filename | committed)—Name of the file to upload. Specify either the word committed to upload the most recently committed configuration file, or the filename of another file. The remaining statements are explained separately. Required Privilege Level Related Documentation 606 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • destinations on page 566 • Configuring an Event Policy to Upload Files Chapter 41: Configuration Statements for System Monitoring user (System Logging) Syntax Hierarchy Level Release Information Description Options user (username | *) { facility severity; match "regular-expression"; } [edit system syslog] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the logging of system messages to user terminals. * (the asterisk)—Log messages to the terminal sessions of all users who are currently logged in. facility—Class of messages to log. To specify multiple classes, include multiple facility severity statements. For a list of the facilities, see Junos OS System Logging Facilities and Message Severity Levels. severity—Severity of the messages that belong to the facility specified by the paired facility name. Messages with severities the specified level and higher are logged. For a list of the severities, see Junos OS System Logging Facilities and Message Severity Levels. username—Junos OS login name of the user whose terminal session is to receive system log messages. To log messages to more than one user’s terminal session, include more than one user statement. The remaining statement is explained separately. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Directing System Log Messages to a User Terminal. • Junos OS System Logging Facilities and Message Severity Levels • Junos OS System Log Messages Reference 607 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user-name Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation user-name username; [edit event-options policy policy-name then event-script filename], [edit event-options policy policy-name then execute-commands], [edit event-options policy policy-name then upload filename (filename | committed) destination destination-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate a user with an action in an event policy. The event policy action is executed under the privileges of the associated user. If you do not associate a user with an action, the action is executed as user root. username—A username that is configured at the [edit system login] hierarchy level. maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Changing the User Privilege Level for an Event Policy Action within Syntax Hierarchy Level Release Information Description within seconds { events [ events ]; not events [ events ]; trigger (after | on | until) event-count; } [edit event-options policy policy-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Create a list of events that must (or must not) occur within a specified time interval for the policy to be triggered. The statements are explained separately. Options seconds—Interval between events. Range: 60 through 604,800 seconds Required Privilege Level Related Documentation 608 maintenance—To view this statement in the configuration. maintenance-control—To add this statement to the configuration. • Using Correlated Events to Trigger an Event Policy Chapter 41: Configuration Statements for System Monitoring world-readable Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation world-readable | no-world-readable; [edit system syslog archive], [edit system syslog file filename archive] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Grant all users permission to read log files, or restrict the permission only to the root user and users who have the Junos OS maintenance permission. no-world-readable system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Specifying Log File Size, Number, and Archiving Properties • Junos OS System Log Messages Reference 609 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 610 CHAPTER 42 Operational Mode Commands for System Monitoring 611 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear log Syntax Release Information Description Options clear log filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Remove contents of a log file. filename—Name of the specific log file to truncate. all—(Optional) Truncate the specified log file and delete all archived versions of it. Required Privilege Level Related Documentation List of Sample Output Output Fields clear log clear • show log on page 657 clear log on page 612 See file list for an explanation of output fields. The following sample commands list log file information, clear the contents of a log file, and then display the updated log file information: user@host> file list lcc0-re0:/var/log/sampled detail lcc0-re0: --------------------------------------------------------------------------rw-r----- 1 root wheel 26450 Jun 23 18:47 /var/log/sampled total 1 user@host> clear log lcc0-re0:sampled lcc0-re0: -------------------------------------------------------------------------user@host> file list lcc0-re0:/var/log/sampled detail lcc0-re0: --------------------------------------------------------------------------rw-r----- 1 root wheel 57 Sep 15 03:44 /var/log/sampled total 1 612 Chapter 42: Operational Mode Commands for System Monitoring file archive Syntax Release Information Description Options file archive destination destination source source Command introduced before Junos OS Release 10.2 for J-EX Series switches. Archive, and optionally compress, one or multiple local system files as a single file, locally or at a remote location. destination destination—Destination of the archived file or files. Specify the destination as a URL or filename. The Junos OS adds one of the following suffixes if the destination filename does not already have it: • For archived files—The suffix .tar • For archived and compressed files—The suffix .tgz source source—Source of the original file or files. Specify the source as a URL or filename. compress—(Optional) Compress the archived file with the GNU zip (gzip) compression utility. The compressed files have the suffix .tgz. Required Privilege Level List of Sample Output Output Fields file archive (Multiple Files) maintenance file archive (Multiple Files) on page 613 file archive (Single File) on page 613 file archive (with Compression) on page 614 When you enter this command, you are provided feedback on the status of your request. The following sample command archives all message files in the local directory /var/log/messages as the single file messages-archive.tar in the same directory: user@host> file archive source /var/log/messages* destination /var/log/messages-archive.tar /usr/bin/tar: Removing leading / from absolute path names in the archive. user@host> file archive (Single File) The following sample command archives one message file in the local directory /var/log/messages as the single file messages-archive.tar in the same directory: user@host> file archive source /var/log/messages destination /var/log/messages-archive.tar /usr/bin/tar: Removing leading / from absolute path names in the archive. user@host 613 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file archive (with Compression) The following sample command archives and compresses all message files in the local directory /var/log/messages as the single file messages-archive.tgz in the same directory: user@host> file archive compress source /var/log/messages* destination /var/log/messages-archive.tgz /usr/bin/tar: Removing leading / from absolute path names in the archive. user@host> 614 Chapter 42: Operational Mode Commands for System Monitoring file checksum md5 Syntax Release Information Description Options file checksum md5 filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Calculate the Message Digest 5 (MD5) checksum of a file. pathname—(Optional) Path to a filename. filename—Name of a local file for which to calculate the MD5 checksum. Required Privilege Level Related Documentation List of Sample Output Output Fields file checksum md5 maintenance • Configuring Checksum Hashes for a Commit Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Event Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Op Script in the Junos OS Configuration and Diagnostic Automation Guide • Executing an Op Script from a Remote Site in the JUNO Configuration and Diagnostic Automation Guide • file checksum sha-256 on page 366 • file checksum sha1 on page 365 • op on page 207 file checksum md5 on page 615 When you enter this command, you are provided feedback on the status of your request. user@host> file checksum md5 jbundle-5.3R2.4-export-signed.tgz MD5 (jbundle-5.3R2.4-export-signed.tgz) = 2a3b69e43f9bd4893729cc16f505a0f5 615 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file checksum sha1 Syntax Release Information Description Options file checksum sha1 filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Calculate the Secure Hash Algorithm (SHA-1) checksum of a file. pathname—(Optional) Path to a filename. filename—Name of a local file for which to calculate the SHA-1 checksum. Required Privilege Level Related Documentation List of Sample Output Output Fields file checksum sha1 maintenance • Configuring Checksum Hashes for a Commit Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Event Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Op Script in the Junos OS Configuration and Diagnostic Automation Guide • Executing an Op Script from a Remote Site in the Junos OS Configuration and Diagnostic Automation Guide • file checksum md5 on page 364 • file checksum sha-256 on page 366 • op on page 207 file checksum sha1 on page 616 When you enter this command, you are provided feedback on the status of your request. user@host> file checksum sha1 /var/db/scripts/opscript.slax SHA1 (/var/db/scripts/commitscript.slax) = ba9e47120c7ce55cff29afd73eacd370e162c676 616 Chapter 42: Operational Mode Commands for System Monitoring file checksum sha-256 Syntax file checksum sha-256 filename Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Calculate the Secure Hash Algorithm 2 family (SHA-256) checksum of a file. Options pathname—(Optional) Path to a filename. filename—Name of a local file for which to calculate the SHA-256 checksum. Required Privilege Level Related Documentation List of Sample Output Output Fields file checksum sha-256 maintenance • Configuring Checksum Hashes for a Commit Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Event Script in the Junos OS Configuration and Diagnostic Automation Guide • Configuring Checksum Hashes for an Op Script in the Junos OS Configuration and Diagnostic Automation Guide • Executing an Op Script from a Remote Site in the Junos OS Configuration and Diagnostic Automation Guide • file checksum md5 on page 364 • file checksum sha1 on page 365 • op on page 207 file checksum sha-256 on page 617 When you enter this command, you are provided feedback on the status of your request. user@host> file checksum sha-256 /var/db/scripts/commitscript.slax SHA256 (/var/db/scripts/commitscript.slax) = 94c2b061fb55399e15babd2529453815601a602b5c98e5c12ed929c9d343dd71 617 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file compare Syntax Release Information Description file compare (files filename filename) < context | unified> Command introduced before Junos OS Release 10.2 for J-EX Series switches. Compare two local files and describe the differences between them in default, context, or unified output styles: • Default—In the first line of output, c means lines were changed between the two files, d means lines were deleted between the two files, and a means lines were added between the two files. The numbers preceding this alphabetical marker represent the first file, and the lines after the alphabetical marker represent the second file. A left angle bracket (<) in front of output lines refers to the first file. A right angle bracket (>) in front of output lines refers to the second file. • Context—Display is divided into two parts. The first part is the first file; the second part is the second file. Output lines preceded by an exclamation point (!) have changed. Additions are marked with a plus sign (+), and deletions are marked with a minus sign (-). • Unified—Display is preceded by the line number from the first and the second file (xx,xxx,x). Before the line number, additions to the file are marked with a plus sign (+), and deletions to the file are marked with a minus sign (-). The body of the output contains the affected lines. Changes are viewed as additions plus deletions. Options files filename—Names of two local files to compare. context—(Optional) Display output in context format. ignore-white-space—(Optional) Ignore changes in amount of white space. unified—(Optional) Display output in unified format. Required Privilege Level List of Sample Output Output Fields 618 none file compare files on page 619 file compare files context on page 619 file compare files unified on page 619 file compare files unified ignore-white-space on page 620 When you enter this command, you are provided feedback on the status of your request. Chapter 42: Operational Mode Commands for System Monitoring file compare files user@host> file compare files /tmp/one /tmp/two 100c100 < full-name "File 1"; --> full-name "File 2"; 102c102 < class foo; # 'foo' is not defined --> class super-user; file compare files context user@host> file compare files /tmp/one /tmp/two context *** /tmp/one Wed Dec 3 17:12:50 2003 --- /tmp/two Wed Dec 3 09:13:14 2003 *************** *** 97,104 **** } } user bill { ! full-name "Bill Smith"; ! class foo; # 'foo' is not defined authentication { encrypted-password SECRET; } --- 97,105 ---} } user bill { ! full-name "Bill Smith"; ! uid 1089; ! class super-user; authentication { encrypted-password SECRET; } file compare files unified user@host> file compare files /tmp/one /tmp/two unified --- /tmp/one Wed Dec 3 17:12:50 2003 +++ /tmp/two Wed Dec 3 09:13:14 2003 @@ -97,8 +97,9 @@ } } user bill { full-name "Bill Smith"; class foo; # 'foo' is not defined + full-name "Bill Smith"; + uid 1089; + class super-user; authentication { encrypted-passwordSECRET; } 619 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file compare files unified ignore-white-space 620 user@host> file compare files /tmp/one /tmp/two unified ignore-white-space --- /tmp/one Wed Dec 3 09:13:10 2003 +++ /tmp/two Wed Dec 3 09:13:14 2003 @@ -99,7 +99,7 @@ user bill { full-name "Bill Smith"; uid 1089; class foo; # 'foo' is not defined + class super-user; authentication { encrypted-password ; # SECRET-DATA } Chapter 42: Operational Mode Commands for System Monitoring file copy Syntax Release Information Description Options file copy source destination Command introduced before Junos OS Release 10.2 for J-EX Series switches. Copy files from one place to another on the local router or switch or between the local router or switch and a remote system. source—Source of the original file. Specify this as a URL or filename. destination—Destination of the copied file. Specify this as a URL or filename. If you are copying a file to the current directory (your home directory on the local router or switch) and are not renaming the file, specify the destination with a period (.). source-address address—(Optional) Source IP host address. This option is useful for specifying the source address of a secure copy (scp) file transfer. Required Privilege Level List of Sample Output Output Fields file copy (A File from the Router to a PC) maintenance file copy (A File from the Router to a PC) on page 621 file copy (A Configuration File Between Routing Engines) on page 621 file copy (A Log File Between Routing Engines) on page 621 When you enter this command, you are provided feedback on the status of your request. user@host> file copy /var/tmp/rpd.core.4 berry:/c/junipero/tmp ...transferring.file...... | file copy (A Configuration File Between Routing Engines) file copy (A Log File Between Routing Engines) 0 KB | 0.3 kB/s | ETA: 00:00:00 | 100% The following sample command copies a configuration file from Routing Engine 0 to Routing Engine 1: user@host> file copy /config/juniper.conf re1:/var/tmp/copied-juniper.conf The following sample command copies a log file from Routing Engine 0 to Routing Engine 1: user@host> file copy lcc0-re0:/var/log/chassisd lcc0-re1:/var/tmp 621 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file delete Syntax Release Information Description Options file delete filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Delete a file on the local router or switch. filename—Name of the file to delete. For a routing matrix, include chassis information in the filename if the file to be deleted is not local to the Routing Engine from which the command is issued. purge—(Optional) Overwrite regular files before deleting them. Required Privilege Level List of Sample Output Output Fields file delete maintenance file delete on page 622 When you enter this command, you are provided feedback on the status of your request. user@host> file list /var/tmp dcd.core rpd.core snmpd.core user@host> file delete /var/tmp/snmpd.core user@host> file list /var/tmp dcd.core rpd.core 622 Chapter 42: Operational Mode Commands for System Monitoring file list Syntax Release Information Description Options file list Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a list of files on the local router or switch. none—Display a list of all files for the current directory. detail | recursive—(Optional) Display detailed output or descend recursively through the directory hierarchy, respectively. filename—(Optional) Display a list of files. For a routing matrix, the filename must include the chassis information. Additional Information Required Privilege Level List of Sample Output Output Fields file list The default directory is the home directory of the user logged into the router or switch. To view available directories, enter a space and then a backslash (/) after the file list command. To view files within a specific directory, include a backslash followed by the directory and, optionally, subdirectory name after the file list command. maintenance file list on page 623 When you enter this command, you are provided feedback on the status of your request. user@host> file list /var/tmp dcd.core rpd.core snmpd.core 623 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS file rename Syntax Release Information Description Options file rename source destination Command introduced before Junos OS Release 10.2 for J-EX Series switches. Rename a file on the local router or switch. destination—New name for the file. source—Original name of the file. For a routing matrix, the filename must include the chassis information. Required Privilege Level List of Sample Output Output Fields file rename maintenance file rename on page 624 When you enter this command, you are provided feedback on the status of your request. The following example lists the files in /var/tmp, renames one of the files, and then displays the list of files again to reveal the newly named file. user@host> file list /var/tmp dcd.core rpd.core snmpd.core user@host> file rename /var/tmp/dcd.core /var/tmp/dcd.core.990413 user@host> file list /var/tmp dcd.core.990413 rpd.core snmpd.core 624 Chapter 42: Operational Mode Commands for System Monitoring file show Syntax Release Information Description Options file show filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the contents of a file. filename—Name of a file. For a routing matrix, the filename must include the chassis information. encoding base64—(Optional) Encode file contents. Required Privilege Level List of Sample Output Output Fields file show maintenance file show on page 625 When you enter this command, you are provided feedback on the status of your request. user@host> file show /var/log/messages Apr 13 21:00:08 romney /kernel: so-1/1/2: loopback suspected; going to standby. Apr 13 21:00:40 romney /kernel: so-1/1/2: loopback suspected; going to standby. Apr 13 21:02:48 romney last message repeated 4 times Apr 13 21:07:04 romney last message repeated 8 times Apr 13 21:07:13 romney /kernel: so-1/1/0: Clearing SONET alarm(s) RDI-P Apr 13 21:07:29 romney /kernel: so-1/1/0: Asserting SONET alarm(s) RDI-P ... 625 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS monitor list Syntax Release Information Description Options Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields monitor list Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the status of monitored log and trace files. This command has no options. Log files are generated by the routing protocol process or by system logging. The log files generated by system logging are configured with the syslog statement at the [edit system] hierarchy level and the options statement at the [edit routing-options] hierarchy level. The trace files generated by the routing protocol process are those configured with traceoptions statements at the [edit routing-options], [edit interfaces], and [edit protocols protocol] hierarchy levels. trace • monitor start on page 627 • monitor stop on page 628 monitor list on page 626 Table 82 on page 626 describes the output fields for the monitor list command. Output fields are listed in the approximate order in which they appear. Table 82: monitor list Output Fields monitor list 626 Field Name Field Description monitor start Indicates the file is being monitored. "filename" Name of the file that is being monitored. Last changed Date and time at which the file was last modified. user@host> monitor list monitor start "vrrpd" (Last changed Dec 03:11:06 20) monitor start "cli-commands" (Last changed Nov 07:3) Chapter 42: Operational Mode Commands for System Monitoring monitor start Syntax Release Information Description Options Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields monitor start filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Start displaying the system log or trace file and additional entries being added to those files. filename—Specific log or trace file. Log files are generated by the routing protocol process or by system logging. The log files generated by system logging are configured with the syslog statement at the [edit system] hierarchy level and the options statement at the [edit routing-options] hierarchy level. The trace files generated by the routing protocol process are configured with traceoptions statements at the [edit routing-options], [edit interfaces], and [edit protocols protocol] hierarchy levels. trace • monitor list on page 626 • monitor stop on page 628 monitor start on page 627 Table 83 on page 627 describes the output fields for the monitor start command. Output fields are listed in the approximate order in which they appear. Table 83: monitor start Output Fields monitor start Field Name Field Description ***filename *** Name of the file from which entries are being displayed. This line is displayed initially and when the command switches between log files. Date and time Timestamp for the log entry. user@host> monitor start system-log *** system-log*** Jul 20 15:07:34 hang sshd[5845]: Jul 20 15:07:35 hang sshd[5845]: Jul 20 15:07:35 hang sshd[5845]: Jul 20 15:07:37 hang sshd[5845]: Jul 20 15:07:37 hang sshd[5845]: Jul 20 15:07:37 hang sshd[5845]: log: log: log: log: log: log: Generating 768 bit RSA key. RSA key generation complete. Connection from 204.69.248.180 port 912 RSA authentication for root accepted. ROOT LOGIN as 'root' from trip.jcmax.com Closing connection to 204.69.248.180 627 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS monitor stop Syntax Release Information Description Options Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields monitor stop 628 monitor stop filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Stop displaying the system log or trace file. filename—Specific log or trace file. Log files are generated by the routing protocol process or by system logging. The log files generated by system logging are those configured with the syslog statement at the [edit system] hierarchy level and the options statement at the [edit routing-options] hierarchy level. The trace files generated by the routing protocol process are those configured with traceoptions statements at the [edit routing-options], [edit interfaces], and [edit protocols protocol] hierarchy levels. trace • monitor list on page 626 • monitor start on page 627 monitor stop on page 628 This command produces no output. user@host> monitor stop Chapter 42: Operational Mode Commands for System Monitoring request system configuration rescue delete Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields request system configuration rescue delete request system configuration rescue delete Command introduced before Junos OS Release 10.2 for J-EX Series switches. Delete an existing rescue configuration. This command has no options. maintenance • request system configuration rescue save on page 377 • request system software rollback on page 113 • show system commit on page 381 request system configuration rescue delete on page 629 This command produces no output. user@host> request system configuration rescue delete 629 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request system configuration rescue save Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields request system configuration rescue save 630 request system configuration rescue save Command introduced before Junos OS Release 10.2 for J-EX Series switches. Save the most recently committed configuration as the rescue configuration so that you can return to it at any time by using the rollback command. This command has no options. maintenance • request system software delete on page 111 • request system software rollback on page 113 • show system commit on page 381 request system configuration rescue save on page 630 This command produces no output. user@host> request system configuration rescue save Chapter 42: Operational Mode Commands for System Monitoring 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: 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from commit file config.txt url http://host1.juniper.net on page 631 request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> 631 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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: 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from event file config.txt url http://host1.juniper.net on page 632 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> 632 Chapter 42: Operational Mode Commands for System Monitoring 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: op 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 maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 323 • Junos OS Junos XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS NETCONF XML Management Protocol Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output request system scripts refresh-from op file config.txt url http://host1.juniper.net on page 633 request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> 633 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis alarms Syntax Release Information Description Options show chassis alarms Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the conditions that have been configured to trigger alarms. none—Display information about the conditions that have been configured to trigger alarms. Additional Information Required Privilege Level List of Sample Output Output Fields You cannot clear the alarms for chassis components. Instead, you must remedy the cause of the alarm. When a chassis alarm is lit, it indicates that you are running the router or switch in a manner that we do not recommend. view show chassis alarms (Alarms Active) on page 634 show chassis alarms (No Alarms Active) on page 634 show chassis alarms (Backup Routing Engine) on page 634 Table 84 on page 634 lists the output fields for the show chassis alarms command. Output fields are listed in the approximate order in which they appear. Table 84: show chassis alarms Output Fields Field Name Field Description Alarm time Date and time the alarm was first recorded. Class Severity class for this alarm: Minor or Major. Description Information about the alarm. show chassis alarms (Alarms Active) user@host> show chassis alarms 3 alarms are currently active Alarm time Class Description 2000-02-07 10:12:22 UTC Major fxp0: ethernet link down 2000-02-07 10:11:54 UTC Minor YELLOW ALARM - PEM 1 Removed 2000-02-07 10:11:03 UTC Minor YELLOW ALARM - Lower Fan Tray Removed show chassis alarms (No Alarms Active) user@host> show chassis alarms No alarms are currently active show chassis alarms (Backup Routing Engine) user@host> show chassis alarms 2 alarms are currently active Alarm time Class 2005-04-07 10:12:22 PDT Minor 2005-04-07 10:11:54 PDT Major 634 Description Host 1 Boot from alternate media Host 1 compact-flash missing in Boot List Chapter 42: Operational Mode Commands for System Monitoring show chassis environment Syntax Release Information Description Options show chassis environment Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display environmental information about the router or switch chassis, including the temperature and information about the fans, power supplies, and Routing Engine. none—Display environmental information about the router or switch chassis. For information about the remaining options, see the Related Topics. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show chassis environment cb • show chassis environment cip • show chassis environment fpc on page 637 • show chassis environment fpm • show chassis environment mcs • show chassis environment pcg • show chassis environment pem • show chassis environment routing-engine on page 638 show chassis environment (J-EX8208 Switch) on page 636 Table 85 on page 635 lists the output fields for the show chassis environment command. Output fields are listed in the approximate order in which they appear. Table 85: show chassis environment Output Fields Field Name Field Description Class Item, Status, Measurement Power Information about each power supply. Status can be OK, Testing (during initial power-on), Check, Failed, or Absent. Temp Temperature of air flowing through the chassis. Measurement indicates degrees in Celsius (C) and Fahrenheit (F). Fan Information about the fans. Status can be OK, Testing (during initial power-on), Failed, or Absent. Measurement indicates if fans are spinning at normal or high speed. Misc Information about other components of the chassis. 635 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis environment (J-EX8208 Switch) 636 user@switch> show chassis environment Class Item Power PSU 0 PSU 1 PSU 2 PSU 3 PSU 4 PSU 5 Temp CB 0 Intake CB 0 Exhaust CB 1 Intake CB 1 Exhaust CB 2 Intake CB 2 Exhaust Fans Fan 1 Fan 2 Fan 3 Fan 4 Fan 5 Fan 6 Fan 7 Fan 8 Fan 9 Fan 10 Fan 11 Fan 12 Status OK OK OK Check Check Check OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Measurement 20 degrees C / 68 degrees 24 degrees C / 75 degrees 19 degrees C / 66 degrees 23 degrees C / 73 degrees 19 degrees C / 66 degrees 23 degrees C / 73 degrees Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Spinning at normal speed Chapter 42: Operational Mode Commands for System Monitoring show chassis environment fpc Syntax show chassis environment fpc Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description (J-EX Series switches) Display environmental information about Flexible PIC Concentrators (FPCs). Options none—Display environmental information about all FPCs. slot—(Optional) Display environmental information about an individual FPC: user@host> show chassis environment fpc 1 lcc 1 user@host> show chassis environment fpc 9 • • Required Privilege Level J-EX Series switches: • J-EX4200 standalone switches—Replace slot with 0. • J-EX4200 switches in a Virtual Chassis configuration—Replace slot with a value from 0 through 9 (switch’s member ID). • J-EX8208 switches—Replace slot with a value from 0 through 7 (line card). • J-EX8216 switches—Replace slot with a value from 0 through 15 (line card). view Output Fields Table 86 on page 637 lists the output fields for the show chassis environment fpc command. Output fields are listed in the approximate order in which they appear. Table 86: show chassis environment fpc Output Fields Field Name Field Description State Status of the FPC: • Unknown—FPC is not detected by the router. • Empty—No FPC is present. • Present—FPC is detected by the chassis daemon but is either not supported by the current version of the Junos OS, or the FPC is coming up but not yet online. • Ready—FPC is in intermediate or transition state. • Announce online—Intermediate state during which the FPC is coming up but not yet online, and the chassis manager acknowledges the chassisd FPC online initiative. Power • Online—FPC is online and running. • Offline—FPC is powered down. • Diagnostics—FPC is set to operate in diagnostics mode. Information about the voltage supplied to the FPC. The left column displays the required power, in volts. The right column displays the measured power, in millivolts. 637 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis environment routing-engine Syntax Release Information Description Options show chassis environment routing-engine Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Routing Engine environmental status information. none—Display environmental information about all Routing Engines. slot—(Optional) Display environmental information about an individual Routing Engine. . On J-EX4200 standalone switches, replace slot with 0. On J-EX4200 switches in a Virtual Chassis configuration and on J-EX8208 and J-EX8216 switches, replace slot with 0 or 1. Required Privilege Level List of Sample Output Output Fields view show chassis environment routing-engine (Nonredundant) on page 638 show chassis environment routing-engine (Redundant) on page 638 Table 87 on page 638 lists the output fields for the show chassis environment routing-engine command. Output fields are listed in the approximate order in which they appear. Table 87: show chassis environment routing-engine Output Fields Field Name Field Description Routing engine slot status Number of the Routing Engine slot: 0 or 1. State Status of the Routing Engine: Temperature show chassis environment routing-engine (Nonredundant) show chassis environment routing-engine (Redundant) 638 • Online Master—MCS is online, operating as Master. • Online Standby—MCS is online, operating as Standby. Temperature of the air flowing past the Routing Engine. user@host> show chassis environment routing-engine Routing Engine 0 status: State Online Master Temperature 27 degrees C / 80 degrees user@host> show chassis environment routing-engine Route Engine 0 status: State: Online Master Temperature: 26 degrees C / 78 degrees F Route Engine 1 status: State: Online Standby Temperature: 26 degrees C / 78 degrees F Chapter 42: Operational Mode Commands for System Monitoring show chassis fpc Syntax Release Information Description Options show chassis fpc > | > Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display status information about the installed Flexible PIC Concentrators (FPCs) and PICs. none—Display status information for all FPCs. detail—(Optional) Display detailed status information for all FPCs or for the FPC in the specified slot (see fpc-slot). fpc-slot—(Optional) FPC slot number: • J-EX Series switches: • J-EX4200 standalone switches—Replace fpc-slot with 0. • J-EX4200 switches in a Virtual Chassis configuration—Replace fpc-slot with a value from 0 through 9 (switch’s member ID). • J-EX8208 switches—Replace fpc-slot with a value from 0 through 7 (line card). • J-EX8216 switches—Replace fpc-slot with a value from 0 through 15 (line card). pic-status—(Optional) Display status information for all PICs or for the PIC in the specified slot (see fpc-slot). Required Privilege Level Related Documentation List of Sample Output Output Fields view • request chassis fpc show chassis fpc (Hardware Not Supported) on page 641 show chassis fpc detail (Hardware Not Supported) on page 641 show chassis fpc pic-status on page 641 Table 88 on page 640 lists the output fields for theshow chassis fpc command. Output fields are listed in the approximate order in which they appear. 639 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 88: show chassis fpc Output Fields Field Name Field Description Level of Output Slot or Slot State Slot number and state. The state can be one of the following conditions: all levels • Dead—Held in reset because of errors. • Diag—Slot is being ignored while the FPC is running diagnostics. • Dormant—Held in reset. • Empty—No FPC is present. • Online—FPC is online and running. • Present—FPC is detected by the chassis daemon but is either not supported by the current version of Junos OS or inserted in the wrong slot. The output also states either Hardware Not Supported or Hardware Not In Right Slot. FPC is coming up but not yet online. • Probed—Probe is complete; awaiting restart of the Packet Forwarding Engine (PFE). • Probe-wait—Waiting to be probed. Logical slot Slot number. all levels Temp (C) or Temperature Temperature of the air passing by the FPC, in degrees Celsius or in both Celsius and Fahrenheit. all levels Total CPU Utilization (%) Total percentage of CPU being used by the FPC's processor. all levels Interrupt CPU Utilization (%) Of the total CPU being used by the FPC's processor, the percentage being used for interrupts. none specified Memory DRAM (MB) Total DRAM, in megabytes, available to the FPC's processor. none specified Heap Utilization (%) Percentage of heap space (dynamic memory) being used by the FPC's processor. If this number exceeds 80 percent, there may be a software problem (memory leak). none specified Buffer Utilization (%) Percentage of buffer space being used by the FPC's processor for buffering internal messages. none specified Total CPU DRAM Amount of DRAM available to the FPC's CPU. detail Total RLDRAM Amount of reduced latency dynamic random access memory (RLDRAM) available to the FPC CPU. detail Total DDR DRAM Amount of double data rate dynamic random access memory (DDR DRAM) available to the FPC CPU. detail Total SRAM Amount of static RAM (SRAM) used by the FPC's CPU. detail Total SDRAM Total amount of memory used for storing packets and notifications. detail 640 Chapter 42: Operational Mode Commands for System Monitoring Table 88: show chassis fpc Output Fields (continued) Field Name Field Description Level of Output I/O Manager ASICs information I/O Manager version number, manufacturer, and part number. detail Start time Time when the Routing Engine detected that the FPC was running. detail Uptime How long the Routing Engine has been connected to the FPC and, therefore, how long the FPC has been up and running. detail PIC type (pic-status output only) Type of PIC. none specified show chassis fpc (Hardware Not Supported) show chassis fpc detail (Hardware Not Supported) show chassis fpc pic-status user@host> show chassis fpc show chassis fpc Temp CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt DRAM (MB) Heap Buffer 0 Online -------------------- CPU less FPC -------------------1 Present ------ Hardware Not In Right Slot -----2 Online 0 0 0 0 0 3 Present ------ Hardware Not Supported -----4 Empty 5 Empty 6 Online 0 0 0 0 0 user@host> show chassis fpc detail Slot 0 information: State Total CPU DRAM Start time Uptime Slot 1 information: State Reason Slot 2 information: State Total CPU DRAM Start time Uptime Slot 3 information: State Reason Total CPU DRAM Slot 6 information: State Total CPU DRAM Start time Uptime Online ---- CPU less FPC ---2006-07-07 03:21:00 UTC 27 minutes, 51 seconds Present --- Hardware Not In Right Slot --Online 32 MB 2006-07-07 03:20:59 UTC 27 minutes, 52 seconds Present --- Hardware Not Supported --0 MB Online 32 MB 2006-07-07 03:21:01 UTC 27 minutes, 50 seconds user@host> show chassis fpc pic-status Slot 0 Online PIC 1 1x OC-12 ATM, MM PIC 2 1x OC-12 ATM, MM PIC 3 1x OC-12 ATM, MM Slot 1 Online 641 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS PIC 0 1x OC-48 SONET, SMIR Slot 2 Online PIC 0 1x OC-192 SONET, SMSR 642 Chapter 42: Operational Mode Commands for System Monitoring show chassis hardware Syntax show chassis hardware Syntax (J-EX4200 Switch) show chassis hardware Release Information Description Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a list of all Flexible PIC Concentrators (FPCs) and PICs installed in the router or switch chassis, including the hardware version level and serial number. In J-EX Series switch command output, FPC refers to the following: Options • On J-EX4200 standalone switches—Refers to the switch; fpc-number is always 0. • On J-EX4200 switches in a Virtual Chassis configuration—Refers to the member of a Virtual Chassis; FPC number equals the member ID, from 0 through 9. • On J-EX8208 and J-EX8216 switches—Refers to a line card; FPC number equals the slot number for the line card. none—Display information about hardware. clei-models—(Optional) Display Common Language Equipment Identifier (CLEI) bar code and model number for orderable field-replaceable units (FRUs). detail—(Optional) Include RAM and disk information in output. extensive—(Optional) Display ID EEPROM information. models—(Optional) Display model numbers and part numbers for orderable FRUs and, for components that use ID EEPROM format v2, the CLEI code. Required Privilege Level List of Sample Output Output Fields view show chassis hardware (J-EX8216 Switch) on page 644 show chassis hardware clei-models (J-EX8216 Switch) on page 645 Table 89 on page 644 lists the output fields for the show chassis hardware command. Output fields are listed in the approximate order in which they appear. 643 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 89: show chassis hardware Output Fields Field Name Field Description Level of Output Item Chassis—Information about the chassis, Routing Engine (SRE and RE modules in J-EX8200 switches), power supplies, fan trays, and LCD panel. Also displays information about Flexible PIC Concentrators (FPCs) and associated Physical Interface Cards (PICs). Information about the backplane, midplane, and SIBs (SF modules) is displayed for J-EX8200 switches. See J-EX Series Switches Hardware and CLI Terminology Mapping. All levels Version Revision level of the chassis component. All levels Part number Part number of the chassis component. All levels Serial number Serial number of the chassis component. The serial number of the backplane is also the serial number of the chassis. Use this serial number when you need to contact Dell Support (see “Requesting Technical Support” on page lxxi) about the chassis. All levels Assb ID or Assembly ID (extensive output only) Identification number that describes the FRU hardware. All levels FRU model number (clei-models, extensive, and models keyword only) Model number of FRU hardware component. none specified CLEI code (clei-models and extensivekeyword only) Common Language Equipment Identifier code. This value is displayed only for hardware components that use ID EEPROM format v2. This value is not displayed for components that use ID EEPROM format v1. none specified EEPROM Version ID EEPROM version used by hardware component: 0x01 (version 1) or 0x02 (version 2). extensive Description Brief description of the hardware item: All levels • Type of power supply. • Type of PIC. If the PIC type is not supported on the current software release, the output states Hardware Not Supported • Type of FPC: FPC Type 1, FPC Type 2, FPC Type 3, FPC Type 4 , or FPC Type OC192, . A brief description of the FPC. • MPC M 16x 10GE—16-port 10-Gigabit Module Port Concentrator that supports SFP+ optical transceivers. (Not on J-EX Series switches.) • For hosts, the Routing Engine type. • For small form-factor pluggable transceiver (SFP) modules, the type of fiber: LX, SX, LH, or T. • LCD description for J-EX Series switches. show chassis hardware (J-EX8216 Switch) 644 user@host> show chassis hardware Hardware inventory: Item Version Part number Chassis REV 06 Midplane REV 06 710-016845 Serial number CY0109260072 BA0909160167 Description DELL J-EX8216 EX8216-MP Chapter 42: Operational Mode Commands for System Monitoring CB 0 Routing Engine CB 1 Routing Engine FPC 5 CPU PIC 0 Base-X SIB 0 SIB 1 SIB 2 SIB 3 SIB 4 SIB 5 SIB 6 SIB 7 PSU 0 PSU 1 PSU 2 PSU 3 PSU 4 PSU 5 Top Fan Tray FTC 0 FTC 1 Bottom Fan Tray FTC 0 FTC 1 LCD 0 show chassis hardware clei-models (J-EX8216 Switch) REV 0 REV 1 REV REV 22 710-020771 BUILTIN 710-020771 BUILTIN 710-020683 710-020598 BUILTIN AX0109197708 BUILTIN AX0109197755 BUILTIN BC0109228159 BF0109197545 BUILTIN EX8216-RE320 RE-EX8216 EX8216-RE320 RE-EX8216 EX8200-48F EX8200-CPU 48x 100 Base-FX/1000 REV REV REV REV REV REV REV REV REV REV REV REV REV REV 10 10 10 10 10 10 10 10 01 01 01 01 01 01 710-021613 710-021613 710-021613 710-021613 710-021613 710-021613 710-021613 710-021613 740-030762 740-030762 740-030762 740-030762 740-030762 740-030762 AY0109207864 AY0109207808 AY0109207917 AY0109207831 AY0109207811 AY0109207881 AY0109207837 AY0109207819 BG0709251730 BG0709251728 BG0709251743 BG0709251741 BG0709251729 BG0709251737 EX8216-SF320 EX8216-SF320 EX8216-SF320 EX8216-SF320 EX8216-SF320 EX8216-SF320 EX8216-SF320 EX8216-SF320 EX8200-AC2K EX8200-AC2K EX8200-AC2K EX8200-AC2K EX8200-AC2K EX8200-AC2K REV 1 REV 1 760-030533 760-030533 CX1209110149 CX1209110149 EX8216-FT EX8216-FT REV 1 REV 1 REV 04 760-030533 760-030533 710-025742 CX1209110121 CX1209110121 CE0109020194 EX8216-FT EX8216-FT EX8200 LCD 22 20 13 user@host> show chassis hardware clei-models Hardware inventory: Item Version Part number CLEI code Midplane REV 08 710-016845 PSU 0 REV 05 740-023002 COUPAEAEAA PSU 1 REV 05 740-023002 COUPAEAEAA PSU 2 REV 05 740-023002 COUPAEAEAA PSU 3 REV 05 740-023002 COUPAEAEAA PSU 4 REV 05 740-023002 COUPAEAEAA PSU 5 REV 05 740-023002 COUPAEAEAA Top Fan Tray Bottom Fan Tray FRU model number EX8200-PWR-AC3KR EX8200-PWR-AC3KR EX8200-PWR-AC3KR EX8200-PWR-AC3KR EX8200-PWR-AC3KR EX8200-PWR-AC3KR 645 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis led Syntax Release Information Description Options show chassis led > Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the status and colors of the chassis LEDs on the front of the switch. A major alarm (red) indicates a critical error condition that requires immediate action. A minor alarm (yellow) indicates a noncritical condition that requires monitoring or maintenance. A minor alarm that is left unchecked might cause interruption in service or performance degradation. none—Display the status of the chassis status LEDs (for J-EX4200 switches configured as a Virtual Chassis, display the information for all Virtual Chassis members). fpc-slot —(Optional) Display the information as follows: Required Privilege Level Related Documentation Output Fields • For the standalone J-EX4200 switch (fpc-slot-number equals 0) • For all J-EX4200 switches in a Virtual Chassis (fpc-slot with no fpc-slot-number value specified) • For a specific Virtual Chassis member (fpc-slot-number equals member ID value) • For the line card in the specified slot on a J-EX8200 switch (fpc-slot-number equals slot number) view • Chassis Status LEDs in J-EX4200 Switches • Chassis Status LEDs in a J-EX8200 Switch Table 90 on page 646 lists the output fields for the show chassis led command. Output fields are listed in the approximate order in which they appear. Table 90: show chassis led Output Fields Field Name Field Description Front panel contents for slot FPC slot number of the switch whose content is being displayed. The number is always 0, except for J-EX4200 switches in a Virtual Chassis, where it is the member ID value. Front panel contents (EX8200 switches) 646 On J-EX8200 switches, no slot number is displayed. Chapter 42: Operational Mode Commands for System Monitoring Table 90: show chassis led Output Fields (continued) Field Name Field Description Alarms LED Displays status of the ALM LED: System LED Master LED • Off—No alarm has been configured. • Green—No alarm has been triggered. • Red—Major alarm. • Yellow—Minor alarm Displays status of the SYS LED: • Off—Switch is powered off. • Green—Switch is operating normally. • Yellow—Switch is booting. Displays status of the MST LED (on J-EX4200, and J-EX8200 switches): • Green—On a J-EX4200 Virtual Chassis switch, indicates the switch is the master in the Virtual Chassis configuration. On other switches, indicates that the Routing Engine is operational. • Off • On a J-EX4200 Virtual Chassis switch, indicates that this switch is not the master in the Virtual Chassis configuration. • On standalone J-EX4200, and J-EX8200 switches, indicates that the Routing Engine is not operational. Interface Names of the interfaces on the switch. LED (ADM/SPD/DPX/POE) State of the currently selected port parameter of the Status LED for the interface. The Status LED port parameters are: NOTE: J-EX8200 switches do not have the POE port parameter. show chassis led • ADM—Administrative • SPD—Speed • DPX—Duplex • POE—Power over Ethernet user@switch> show chassis led Front panel contents for slot: 0 --------------------------------LEDs status: Alarms LED: Off System LED: Green Master LED: Green Interface LED(ADM/SPD/DPX/POE) ------------------------------------ge-0/0/0 Off ge-0/0/1 Full Duplex ge-0/0/2 Full Duplex ge-0/0/3 Off ge-0/0/4 Off 647 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/5 ge-0/0/6 ge-0/0/7 ge-0/0/8 ge-0/0/9 ge-0/0/10 ge-0/0/11 ge-0/0/12 ge-0/0/13 ge-0/0/14 ge-0/0/15 ge-0/0/16 ge-0/0/17 ge-0/0/18 ge-0/0/19 ge-0/0/20 ge-0/0/21 ge-0/0/22 ge-0/0/23 ge-0/0/24 ge-0/0/25 ge-0/0/26 ge-0/0/27 ge-0/0/28 ge-0/0/29 show chassis led fpc-slot 0 648 Full Full Full Full Full Full Full Full Full Full Full Full Full Full Full Full Full Off Off Full Full Off Off Full Full Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex Duplex user@switch> show chassis led fpc-slot 0 Front panel contents for slot: 0 --------------------------------LEDs status: Alarms LED: Red System LED: Green Master LED: Green Interface LED(ADM/SPD/DPX/POE) ------------------------------------ge-0/0/0 Off ge-0/0/1 Off ge-0/0/2 Off ge-0/0/3 Off ge-0/0/4 Off ge-0/0/5 Off ge-0/0/6 Off ge-0/0/7 Off ge-0/0/8 Off ge-0/0/9 Off ge-0/0/10 Off ge-0/0/11 Off ge-0/0/12 Off ge-0/0/13 Off ge-0/0/14 Off ge-0/0/15 Off ge-0/0/16 Off ge-0/0/17 Off ge-0/0/18 Off ge-0/0/19 Off ge-0/0/20 Off ge-0/0/21 Off ge-0/0/22 Off ge-0/0/23 Off Chapter 42: Operational Mode Commands for System Monitoring show chassis location Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show chassis location Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the physical location of the chassis. This command can only be used on the master Routing Engine. none—Display all information about the physical location of the chassis. view show chassis location on page 649 show chassis location on page 649 Table 91 on page 649 lists the output fields for the show chassis location command. Output fields are listed in the approximate order in which they appear. Table 91: show chassis location Output Fields Field Name Field Description country-code Country code information. postal-code Postal code information. Building Building information. Floor Floor information. Global FPC Global FPC number. The FPC slot number, when all FPC slots in the Routing Matrix are considered. The range of values is 0 through 31. LCC Line-card chassis number. Local FPC Local FPC number. show chassis location user@host> show chassis location country-code: US postal-code: 94404 Building: Building 2, Floor: 2 show chassis location user@host> show chassis location country-code: US postal-code: 94404 Building: Building 2, Floor: 2 649 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show chassis pic Syntax Release Information Description Options show chassis pic fpc-slot slot-number pic-slot slot-number Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display status information about the PIC installed in the specified Flexible PIC Concentrator (FPC) and PIC slot. fpc-slot slot-number—Display information about the PIC in this particular FPC slot: • J-EX Series switches: • J-EX4200 standalone switches—Replace slot-number with 0. • J-EX4200 switches in a Virtual Chassis configuration—Replace slot-number with a value from 0 through 9 (switch’s member ID). • J-EX8208 switches—Replace slot-number with a value from 0 through 7 (line card). • J-EX8216 switches—Replace slot-number with a value from 0 through 15 (line card). pic-slot slot-number—Display information about the PIC in this particular PIC slot. For routers, replace slot-number with a value from 0 through 3. For J-EX4200 switches, replace slot-number with 0 for built-in network interfaces and 1 for interfaces on uplink modules. For J-EX8208 and J-EX8216 switches, replace slot-number with 0. Required Privilege Level Related Documentation List of Sample Output Output Fields view • request chassis pic on page 209 show chassis pic fpc-slot pic-slot on page 651 show chassis pic fpc-slot pic-slot (PIC Offline) on page 651 show chassis pic fpc-slot pic-slot (FPC Offline) on page 652 show chassis pic fpc-slot pic-slot (FPC Not Present) on page 652 show chassis pic fpc-slot pic-slot (PIC Not Present) on page 652 Table 92 on page 650 lists the output fields for the show chassis pic command. Output fields are listed in the approximate order in which they appear. Table 92: show chassis pic Output Fields 650 Field Name Field Description Type PIC type. ASIC type Type of ASIC on the PIC. Chapter 42: Operational Mode Commands for System Monitoring Table 92: show chassis pic Output Fields (continued) Field Name Field Description State Status of the PIC. State is displayed only when a PIC is in the slot. • Online— PIC is online and running. • Offline—PIC is powered down. PIC version PIC hardware version. Uptime How long the PIC has been online. Package (MultiServices PICs only) Services package supported: Layer-2 or Layer-3. PIC Port Information Port-level information for the PIC. Port Number Port number for the PIC. Cable Type Type of cable connected to the port: LH, LX, or SX PIC Port Information (MX960 Router Bidirectional Optics) Port-level information for the PIC. • Port—Port number • Cable type—Type of small form-factor pluggable (SFP) optical transceiver installed. Uplink interfaces display -U. Down link interfaces display -D. • Fiber type—Type of fiber. SM is single-mode. • Xcvr vendor—Transceiver vendor name. • Xcvr vendor part number—Transceiver vendor part number. • • BX10-10-km bidirectional optics. • BX40-40-km bidirectional optics. • SFP-LX-40-km SFP optics. Wavelength—Wavelength of the transmitted signal. Uplinks are always 1310 nm. Downlinks are either 1490 nm or 1550 nm. show chassis pic fpc-slot pic-slot user@host> show chassis pic fpc-slot 2 pic-slot 0 PIC fpc slot 2 pic slot 0 information: Type 10x 1GE(LAN), 1000 BASE ASIC type H chip State Online PIC version 1.1 Uptime 1 day, 50 minutes, 58 seconds PIC Port Information: Port Cable Number Type 0 GIGE 1000LX 6 GIGE 1000LX show chassis pic fpc-slot pic-slot (PIC Offline) user@host> show chassis pic fpc-slot 1 pic-slot 0 651 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS PIC fpc slot 1 pic slot 0 information: State Offline 652 show chassis pic fpc-slot pic-slot (FPC Offline) user@host> show chassis pic fpc-slot 1 pic-slot 0 FPC 1 is not online show chassis pic fpc-slot pic-slot (FPC Not Present) user@host> show chassis pic fpc-slot 4 pic-slot 0 FPC slot 4 is empty show chassis pic fpc-slot pic-slot (PIC Not Present) user@host> show chassis pic fpc-slot 5 pic-slot 2 FPC 5, PIC 2 is empty Chapter 42: Operational Mode Commands for System Monitoring show chassis routing-engine Syntax show chassis routing-engine Syntax (J-EX Series Switch) show chassis routing-engine Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the status of the Routing Engine. none—Display information about one or more Routing Engines. bios—(Optional) Display the basic input/output system (BIOS) firmware version. slot—(Systems with multiple Routing Engines) (Optional) Display information for an individual Routing Engine. Replace slot with 0 or 1. Required Privilege Level Related Documentation Output Fields view • request chassis routing-engine master on page 210 Table 93 on page 653 lists the output fields for theshow chassis routing-engine command. Output fields are listed in the approximate order in which they appear. Table 93: show chassis routing-engine Output Fields Field Name Field Description Slot (Systems with multiple Routing Engines) Slot number. Current state (Systems with multiple Routing Engines) Current state of the Routing Engine: Master, Backup, or Disabled. Election priority (Systems with multiple Routing Engines) Election priority for the Routing Engine: Master or Backup. Temperature Temperature of the air flowing past the Routing Engine. DRAM Total DRAM available to the Routing Engine's processor. Memory utilization Percentage of Routing Engine memory being used. 653 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 93: show chassis routing-engine Output Fields (continued) Field Name Field Description CPU utilization Information about the Routing Engine's CPU utilization: • User—Percentage of CPU time being used by user processes. • Background—Percentage of CPU time being used by background processes. • Kernel—Percentage of CPU time being used by kernel processes. • Interrupt—Percentage of CPU time being used by interrupts. • Idle—Percentage of CPU time that is idle. Model Routing Engine model number. Serial ID (Systems with multiple Routing Engines) Identification number of the Routing Engine in this slot. Start time Time at which the Routing Engine started running. Uptime How long the Routing Engine has been running. Last reboot reason Reason for last reboot, including: • power cycle/failure—Reboot due to the switching off of the power button behind the Routing Engine, not the power button on the chassis. • watchdog—Reboot due to a hardware watchdog. • power-button hard power off—Reboot due to pressing of the power button. • misc hardware reason—Reboot due to miscellaneous hardware reasons. • thermal shutdown—Reboot due to the router reaching a critical temperature point at which it is unsafe to continue operations. Load averages 654 • hard disk failure—Reboot due to a hard disk failure. • reset from debugger—Reboot due to reset from the debugger. • chassis control reset—Reboot due to a chassis control reset. • bios auto recovery reset—Reboot due to a BIOS auto-recovery reset. • could not be determined—Reboot due to an undetermined reason. • Router rebooted after a normal shutdown—Reboot due to a normal shutdown. Routing Engine load averages for the last 1, 5, and 15 minutes. Chapter 42: Operational Mode Commands for System Monitoring show chassis temperature-thresholds Syntax show chassis temperature-thresholds Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display chassis temperature threshold settings, in degrees Celsius. Required Privilege Level view List of Sample Output show chassis temperature-thresholds on page 655 Output Fields Table 94 on page 655 lists the output fields for the show chassis temperature-thresholds command. Output fields are listed in the approximate order in which they appear. Table 94: show chassis temperature-thresholds Output Fields Field name Field Description Item Chassis component. If per FRU per slot thresholds are configured, the components about which information is displayed include the chassis, the Routing Engines, FPCs, and FEBs. If per FRU per slot thresholds are not configured, the components about which information is displayed include the chassis and the Routing Engines. Fan speed Temperature threshold settings, in degrees Celsius, for the fans to operate at normal and high speeds. • Normal—The fans operate at normal speed if the component is at or below this temperature and all the fans are present and functioning normally. • High—The fans operate at high speed if the component has exceeded this temperature or a fan has failed or is missing. An alarm is not triggered until the temperature exceeds the threshold settings for a yellow alarm or a red alarm. Yellow alarm Temperature threshold settings, in degrees Celsius, that trigger a yellow alarm. • Normal—The temperature that must be exceeded on the component to trigger a yellow alarm when the fans are running at full speed. • Bad fan—The temperature that must be exceeded on the component to trigger a yellow alarm when one or more fans have failed or are missing. Red alarm Temperature threshold settings, in degrees Celsius, that trigger a red alarm. • Normal—The temperature that must be exceeded on the component to trigger a red alarm when the fans are running at full speed. • Bad fan—The temperature that must be exceeded on the component to trigger a red alarm when one or more fans have failed or are missing. show chassis temperature-thresholds user@host> show chassis temperature-thresholds Fan speed Yellow alarm Item Normal High Normal Bad fan Chassis default 48 54 65 55 Routing Engine 0 70 80 95 95 Routing Engine 1 70 80 95 95 Red alarm Normal Bad fan 75 65 110 110 110 110 655 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS FPC FPC FPC FPC FPC FPC FPC FPC FPC FPC FPC FPC 656 0 1 2 3 4 5 6 7 8 9 10 11 55 55 55 55 55 55 55 55 55 55 55 55 60 60 60 60 60 60 60 60 60 60 60 60 75 75 75 75 75 75 75 75 75 75 75 75 65 65 65 65 65 65 65 65 65 65 65 65 90 90 90 90 90 90 90 90 90 90 90 90 80 80 80 80 80 80 80 80 80 80 80 80 Chapter 42: Operational Mode Commands for System Monitoring show log Syntax Release Information Description Options show log > Command introduced before Junos OS Release 10.2 for J-EX Series switches. List log files, display log file contents, or display information about users who have logged in to the router or switch. none—List all log files. filename—(Optional) Display the log messages in the specified log file. user —(Optional) Display logging information about users who have recently logged in to the router or switch. If you include username, display logging information about the specified user. Required Privilege Level List of Sample Output show log show log filename trace show log on page 657 show log filename on page 657 show log user on page 658 user@host> show log total 57518 -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-rw-r-- 1 root bin bin bin bin bin bin bin bin bin bin bin bin bin 211663 999947 999994 238815 1049098 1061095 1052026 1056309 1056371 1056301 1056350 1048876 19656 Oct Oct Oct Oct Oct Oct Oct Sep Sep Sep Sep Sep Oct 1 1 1 1 1 1 1 30 30 30 30 30 1 19:44 19:41 17:48 19:44 18:00 12:13 06:08 18:21 14:36 10:50 07:04 03:21 19:37 dcd dcd.0 dcd.1 rpd rpd.0 rpd.1 rpd.2 rpd.3 rpd.4 rpd.5 rpd.6 rpd.7 wtmp user@host> show log rpd Oct 1 18:00:18 trace_on: Tracing to ?/var/log/rpd? started Oct 1 18:00:18 EVENT ds-5/2/0.0 index 24 show log user darius mg2546 darius mg2529 darius mg2518 root mg1575 root ttyp2 jun.site.per alex ttyp1 192.168.1.2 Thu Oct 1 19:37 still logged in Thu Oct 1 19:08 - 19:36 (00:28) Thu Oct 1 18:53 - 18:58 (00:04) Wed Sep 30 18:39 - 18:41 (00:02) Wed Sep 30 18:39 - 18:41 (00:02) Wed Sep 30 01:03 - 01:22 (00:19) Chapter 42: Operational Mode Commands for System Monitoring show pfe next-hop Syntax Release Information Description Options show pfe next-hop Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Packet Forwarding Engine next-hop information. none—Display all Packet Forwarding Engine next-hop information. interface interface-name—(Optional) Display the Packet Forwarding Engine next-hop interface. Required Privilege Level List of Sample Output admin show pfe next-hop on page 660 659 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pfe next-hop 660 user@host> show pfe next-hop Nexthop Info: ID Type Interface ----- -------- ------------4 Mcast 5 Bcast 7 Discard 8 MDiscard 9 Reject 13 Local 14 Resolve fxp0.0 17 Local 18 Unicast fxp0.0 21 Local 22 Unicast at-0/1/0.0 ... Protocol --------IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 Encap -----------Unspecified Unspecified ATM SNAP Next Hop Addr --------------0.0.0.0 192.168.4.60 127.0.0.1 192.168.4.254 11.1.0.1 11.1.0.2 MTU ----0 0 0 0 0 0 0 0 0 0 4482 Chapter 42: Operational Mode Commands for System Monitoring show pfe route Syntax Syntax (J-EX Series Switch) Release Information Description show pfe route < | >> show pfe route < |
>> Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the routes in the Packet Forwarding Engine forwarding table. The Packet Forwarding Engine forwards packets between input and output interfaces. NOTE: The Routing Engine maintains a master copy of the forwarding table. It copies the forwarding table to the Packet Forwarding Engine, which is the part of the router or switch responsible for forwarding packets. To display the routes in the Routing Engine forwarding table, use the show route forwarding table command. For more information, see the Junos OS Routing Protocols and Policies Command Reference. Options none—Display all Packet Forwarding Engine forwarding table information. inet6—(Optional) Display Packet Forwarding Engine IPv6 routes. ip—(Optional) Display Packet Forwarding Engine IPv4 routes. iso —(Optional) Display ISO version routing tables. mpls—(Optional) Display Packet Forwarding Engine Multiprotocol Label Switching (MPLS) information. prefix prefix—(Optional) IPv4 or IPv6 prefix for which to show table entries. summary—(Optional) Display summary of Packet Forwarding Engine information. table —(Optional) Display table information. Optionally, specify the table name, index, or prefix. Required Privilege Level List of Sample Output show pfe route ip admin show pfe route ip on page 661 show pfe route iso on page 662 user@host> show pfe route ip IPv4 Route Table 0, default.0, 0x0: 661 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Destination --------------------------------default 127.0.0.1 172.16/12 192.168.0/18 192.168.40/22 192.168.64/18 192.168.64/21 192.168.71.249 192.168.220.0/30 192.168.220.0 224.0.0.1 255.255.255.255 NH IP Addr Type NH ID Interface --------------- -------- ----- --------Discard 8 127.0.0.1 Local 256 192.168.71.254 Unicast 68 fxp0.0 192.168.71.254 Unicast 68 fxp0.0 192.168.71.254 Unicast 68 fxp0.0 192.168.71.254 Unicast 68 fxp0.0 Resolve 67 fxp0.0 192.168.71.249 Local 66 Resolve 303 fe-0/0/0.0 192.168.220.0 Receive 301 fe-0/0/0.0 Mcast 5 Bcast 6 ... show pfe route iso user@host# show pfe route iso CLNS Route Table 0, CLNP.0, 0x0: Destination Type NH ID Interface ---------------------------------------- -------- ----- --------default Reject 60 47.0005.80ff.f800.0000.0108.0001.0102.5508.2159/152 Local 514 49.0001.00a0.c96b.c491/72 Local 536 662 Chapter 42: Operational Mode Commands for System Monitoring show pfe statistics ip Syntax show pfe statistics ip Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display IPv4 Packet Forwarding Engine statistics. Options none—Display all IPv4 Packet Forward Engine statistics. icmp—(Optional) Display Packet Forwarding Engine IP ICMP statistics. options—(Optional) Display Packet Forwarding Engine IP options statistics. Required Privilege Level admin List of Sample Output show pfe statistics ip icmp on page 664 show pfe statistics ip options on page 665 Output Fields Table 95 on page 663 lists the output fields for the show pfe statistics ip command. Output fields are listed in the approximate order in which they appear. Table 95: show pfe statistics ip Output Fields Field Name Field Description ICMP Statistics ICMP statistics, including the following: • requests—Number of ICMP notifications sent to the PFE. If a throttler is configured, the number of notifications might not reflect all requests made. (See the throttled icmps field description.) • network unreachables—When route lookups fail, ICMP packets are sent to the source. These packets are ICMP TypeDestination Unreachable (3) and ICMP Code=Network Unreachable (0). • ttl expired—Number of notifications processed as a result of time-to-live (TTL) expiration packets. • ttl captured—Number of TTL expired packets sent by PFE interfaces to the Routing Engine. • redirects—Number of ICMP errors sent with Type=Redirect (5). • mtu exceeded—Number of ICMP errors sent with Type=Source Quench (4). • icmp/option handoffs—Number of packets that the PFE hardware requests the PFE software to process. 663 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 95: show pfe statistics ip Output Fields (continued) Field Name Field Description ICMP errors ICMP errors, including the following: • unknown unreachables—Unknown code (greater than 16) found for an unknown unreachable type ICMP error. • unsupported ICMP type—Any ICMP type other than UNREACH, REDIRECT, TIME_EXCEED, and PARAM_PROB. • unprocessed redirects—When trying to find the neighbor to send redirects to, the PFE could not find the next-hop information. • invalid ICMP type—Any ICMP type other than UNREACH, REDIRECT, TIME_EXCEED, and PARAM_PROB. • invalid protocol—An incorrect protocol was detected by the ICMP processor. • bad input interface if1—The PFE software cannot map the interface index supplied by the chips to a proper data structure in the microkernel. • throttled icmps—Number of requests dropped because of rate limiting by the PFE. • runts—Number of packets for which the IP header length is less than the minimum length that is supported. ICMP Discards ICMP discard statistics, including the following: • multicasts—ICMP packets are not sent for link-layer multicast packets. These are counted as invalid source addresses (not a unicast address or all zeros). • bad source addresses—ICMP packets were received from an invalid source address (not a unicast address or all zeros). • bad dest addresses—ICMP packets were sent to an invalid destination address (not a unicast address or all zeros). • IP fragments—ICMP responses are sent only for the first fragments. The rest do not receive a response. This is the count for ICMP requests that receive no response. • show pfe statistics ip icmp 664 ICMP errors—Number of ICMP error packets. user@host> show pfe statistics ip icmp ICMP Statistics: 0 requests 0 network unreachables 0 ttl expired 0 ttl captured 0 redirects 0 mtu exceeded 0 icmp/option handoffs ICMP Errors: 0 unknown unreachables 0 unsupported ICMP type 0 unprocessed redirects 0 invalid ICMP type 0 invalid protocol 0 bad input interface 0 throttled icmps 0 runts ICMP Discards: 0 multicasts 0 bad source addresses 0 bad dest addresses 0 IP fragments Chapter 42: Operational Mode Commands for System Monitoring 0 ICMP errors show pfe statistics ip options user@host> show pfe statistics ip options IP Option Values: LSRR/SSRR forwarding enabled IP Option Statistics: 0 loose source routes 0 strict source routes 0 record routes 889382 router alerts 0 other options IP Option Errors: 0 runts 2 bad versions 0 runt header lengths 0 giant header lengths 0 null frames 0 bad option lengths 0 duplicate options 0 bad option pointers 0 source route frames dropped 188 frames queued 1126 frames dropped 665 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pfe statistics ip6 Syntax show pfe statistics ip6 Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display Packet Forwarding Engine IPv6 statistics. Options none—Display all Packet Forwarding Engine IPv6 statistics. icmp—(Optional) Display Packet Forwarding Engine IP ICMP statistics. Required Privilege Level admin List of Sample Output show pfe statistics ip6 icmp on page 667 show pfe statistics ip6 lcc on page 668 Output Fields Table 96 on page 666 lists the output fields for the show pfe statistics ip6 command. Output fields are listed in the approximate order in which they appear. Table 96: show pfe statistics ip6 Output Fields Field Name Field Description ICMP6 Statistics ICMP6 statistics, including the following: • requests—Number of ICMP notifications sent to the PFE. If a throttler is configured, the number of notifications might not reflect all requests made. (See the throttled icmps field description.) • network unreachables—When route lookups fail, ICMP packets are sent to the source. These packets are ICMP Type= Destination Unreachable (3) and ICMP Code= Network Unreachable (0). • ttl expired—Number of notifications processed as a result of time-to-live (TTL) expiration packets. • ttl captured—Number of TTL expired packets sent by PFE interfaces to the Routing Engine. • redirects—Number of ICMP errors sent with Type=Redirect (5). • mtu exceeded—Number of ICMP errors sent with Type=Source Quench (4). • icmp/option handoffs—Number of packets that the PFE hardware requests the PFE software to process. 666 Chapter 42: Operational Mode Commands for System Monitoring Table 96: show pfe statistics ip6 Output Fields (continued) Field Name Field Description ICMP6 errors ICMP6 errors, including the following: • unknown unreachables—Unknown code (greater than 16) found for an unknown unreachable type ICMP error. • unsupported ICMP type—Any ICMP type other than UNREACH, REDIRECT, TIME_EXCEED, and PARAM_PROB. • unprocessed redirects—When trying to find the neighbor to send redirects to, the PFE could not find the next-hop information. • invalid ICMP type—Any ICMP type other than UNREACH, REDIRECT, TIME_EXCEED, and PARAM_PROB. • invalid protocol—An incorrect protocol was detected by the ICMP processor. • bad input interface if1—The PFE software cannot map the interface index supplied by the chips to a proper data structure in the microkernel. • throttled icmps—Number of requests dropped because of rate limiting by the PFE. • runts—Number of packets for which the IP header length is less than the minimum length that is supported. ICMP6 Discards ICMP6 discard statistics, including the following: • multicasts—ICMP packets are not sent for link-layer multicast packets. These are counted as invalid source addresses (not a unicast address or all zeros). • bad source addresses—ICMP packets were received from an invalid source address (not a unicast address or all zeros). • bad dest addresses—ICMP packets were sent to an invalid destination address (not a unicast address or all zeros). • IP fragments—ICMP responses are sent only for the first fragments. The rest do not receive a response. This is the count for ICMP requests that receive no response. • show pfe statistics ip6 icmp ICMP errors—Number of ICMP error packets. user@host> show pfe statistics ip6 icmp ICMP6 Statistics: 0 requests 0 network unreachables 0 ttl expired 0 ttl captured 0 redirects 0 mtu exceeded 0 icmp/option handoffs ICMP6 Errors: 0 unknown unreachables 0 unsupported ICMP type 0 unprocessed redirects 0 invalid ICMP type 0 invalid protocol 0 bad input interface 0 throttled icmps 0 runts ICMP6 Discards: 0 multicasts 0 bad source addresses 0 bad dest addresses 667 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 0 IP fragments 0 ICMP errors show pfe statistics ip6 lcc user@host> show pfe statistics ip6 lcc 0 fpc 0 sfc0-re0: -------------------------------------------------------------------------ICMP Statistics: 0 requests 0 network unreachables 0 ttl expired 0 ttl captured 0 redirects 0 mtu exceeded 0 icmp/option handoffs ICMP Errors: 0 0 0 0 0 0 0 0 unknown unreachables unsupported ICMP type unprocessed redirects invalid ICMP type invalid protocol bad input interface throttled icmps runts ICMP Discards: 0 multicasts 0 bad source addresses 0 bad dest addresses 0 IP fragments 0 ICMP errors 668 Chapter 42: Operational Mode Commands for System Monitoring show pfe terse Syntax Release Information Description Options Required Privilege Level show pfe terse Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Packet Forwarding Engine status information. none—Display brief information about the Packet Forwarding Engine. admin 669 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system alarms Syntax Release Information Description Options Additional Information Required Privilege Level List of Sample Output show system alarms 670 show system alarms Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display active system alarms. This command has no options. System alarms are preset. They include a configuration alarm that appears when no rescue configuration alarm is set and a license alarm that appears when a software feature is configured and no valid license is configured for the feature. For more information about system alarms, see the Junos OS System Basics Configuration Guide. admin show system alarms on page 670 user@host> show system alarms 2 alarms currently active Alarm time 2005-02-24 17:29:34 UTC license 2005-02-24 17:29:34 UTC Class Minor Description IPsec VPN tunneling usage requires a Minor Rescue configuration is not sent Chapter 42: Operational Mode Commands for System Monitoring show system audit Syntax Syntax (J-EX Series Switch) Release Information Description Options show system audit show system audit Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the state and checksum values for file systems. none—Display the state and checksum values for all file systems. all-members—(J-EX4200 switches only) (Optional) Display file system MD5 hash and permissions information on all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Display file system MD5 hash and permissions information on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display file system MD5 hash and permissions information on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. root-only—(Optional) Check only the root (/) file system. Additional Information To redirect the output to a file, issue the following command: ssh router-name 'show system audit root-only' > output-file If you save the output of the show system audit root-only command to a file, you can compare it to subsequent output from the command to determine whether anything has changed. Required Privilege Level List of Sample Output show system audit root-only admin show system audit root-only on page 671 user@host> show system audit root-only # user: root # machine: my-host # tree: / date: Fri Feb 11 21:21:46 2000 # . /set type=file uid=0 gid=0 mode=0755 nlink=1 . type=dir nlink=23 size=1024 time=950252640.0 .cshrc uid=3 gid=7 mode=0644 size=177 time=939182975.0 \ md5digest=f414e06fea6bd646244b98e13d6e6226 .kernel.jkernel.backup \ 671 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mode=0744 size=1934552 time=944688902.0 \ md5digest=2c343cf0bd9fea8f04f78604feed7aa4 .profile uid=3 gid=7 mode=0644 nlink=2 size=173 time=939182975.0 \ md5digest=55a1e3c6c67789c9d3a1cce1ea39f670 COPYRIGHT uid=3 gid=7 mode=0444 size=3425 time=939182975.0 \ md5digest=7df8bc77dcee71382ea73eb0ec6a9243 boot.config mode=0644 size=3 time=945902618.0 \ md5digest=93d722493ed38477338a1405d7dcbb40 boot.help uid=3 gid=7 mode=0444 size=411 time=939182876.0 \ md5digest=9b7126385734bcae753f4179ab59d8e5 compat type=link mode=0777 size=11 time=915149058.0 \ link=/usr/compat kernel mode=0444 size=1947607 time=950230892.0 \ md5digest=1a2a8aff2fec678a918ba0d6bf063980 kernel.avr uid=1112 size=1947642 time=950252597.0 \ md5digest=82e1637682d58ec28964dfee7fccb62e kernel.config \ mode=0644 size=0 time=915149058.0 \ md5digest=d41d8cd98f00b204e9800998ecf8427e sys type=link mode=0777 size=11 time=915149029.0 \ link=usr/src/sys 672 Chapter 42: Operational Mode Commands for System Monitoring show system buffers Syntax Syntax (J-EX Series Switch) Release Information Description Options show system buffers show system buffers Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the buffer pool that the Routing Engine uses for local traffic. Local traffic is the routing and management traffic that is exchanged between the Routing Engine and the Packet Forwarding Engine within the router or switch, as well as the routing and management traffic from IP (that is, from OSPF, BGP, SNMP, ping operations, and so on). none—Show all buffer statistics. all-members—(J-EX4200 switches only) (Optional) Show buffer statistics for on all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Show buffer statistics for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Show buffer statistics for 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 A special type of memory buffer called a cluster is 2 KB in size. For more information, see The Design and Implementation of the 4.4BSD Operation System by McKusic, Bostic, Karels, and Quarterman. view show system buffers on page 674 Table 97 on page 674 describes the output fields for the show system buffers command. Output fields are listed in the approximate order in which they appear. 673 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 97: show system buffers Output Fields Field Name Field Description mbufs in use Memory buffers (mbufs) are 128-byte buffers that are used for various purposes inside the kernel. Each memory buffer has a type, and the output itemizes the amount allocated for each type. Types with no memory buffers allocated are not displayed. mbufs allocated to packet headers Number of memory buffers currently holding packet headers mbufs allocated to control blocks Number of memory buffers currently holding state for sockets. mbufs allocated to send data Number of memory buffers currently holding socket send data. mbufs allocated to pfe refill data Number of memory buffers currently holding Packet Forwarding Engine refill data. mbufs allocated to fxp data Number of memory buffers currently holding fxp data. mbufs allocated to socket names and addresses Number of memory buffers currently holding addresses for sockets. mbuf clusters in use Allocation statistics for mbuf clusters. allocated to network Total amount of memory in use by the networking and interprocess communication (IPC) code. requests for memory denied Number of times a memory allocation request within the IPC and networking code failed. requests for memory delayed Number of times a memory allocation request within the IPC and networking code was postponed. calls to protoocl drain routines Number of times a memory allocation request within the IPC and networking code triggered a memory reclamation attempt. show system buffers 674 user@host> show system buffers 853 mbufs in use: 2 mbufs allocated to packet headers 37 mbufs allocated to protocol control blocks 28 mbufs allocated to socket names and addresses 2 mbufs allocated to socket send data 400 mbufs allocated to pfe refill data 384 mbufs allocated to fxp data 784/944 mbuf clusters in use 1994 Kbytes allocated to network (83% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Chapter 42: Operational Mode Commands for System Monitoring show system connections Syntax Syntax (J-EX Series Switch) Release Information Description Options show system connections show system connections Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the active IP sockets on the Routing Engine. Use this command to verify which servers are active on a system and what connections are currently in progress. none—Display information about all active IP sockets on the Routing Engine. extensive—(Optional) Display exhaustive system process information, which, for TCP connections, includes the TCP control block. This option is useful for debugging TCP connections. all-members—(J-EX4200 switches only) (Optional) Display system connection activity for all members of the Virtual Chassis configuration. inet | inet6—(Optional) Display IPv4 connections or IPv6 connections, respectively. local—(J-EX4200 switches only) (Optional) Display system connection activity for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display system connection activity for the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. show-routing-instances—(Optional) Display routing instances. Required Privilege Level List of Sample Output Output Fields view show system connections on page 676 show system connections extensive on page 677 show system connections show-routing-instances on page 677 Table 98 on page 676 describes the output fields for the show system connections command. Output fields are listed in the approximate order in which they appear. 675 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 98: show system connections Output Fields Field Name Field Description Proto Protocol of the socket: IP, TCP, or UDP for IPv4 or IPv6. Recv-Q Number of input packets received by the protocol and waiting to be processed by the application. Send-Q Number of output packets sent by the application and waiting to be processed by the protocol. Local Address Local address and port of the socket, separated by a period. An asterisk (*) indicates that the bound address is the wildcard address. Server sockets typically have the wildcard address and a well-known port bound to them. Foreign Address Foreign address and port of the socket, separated by a period. An asterisk (*) indicates that the address or port is a wildcard. Routing Instance (Displayed Routing instances associated with active IP sockets on the Routing Engine. only when the show-routing-instance option is used. (state) show system connections 676 For TCP, the protocol state of the socket. user@host> show system connections Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address tcp 0 2 192.168.4.16.513 208.197.169.254.894 tcp 0 0 192.168.4.16.513 208.197.169.195.945 tcp 0 0 *.23 *.* tcp 0 0 *.22 *.* tcp 0 0 *.513 *.* tcp00 *.514 *.* LISTEN tcp 0 0*.21 *.* LISTEN tcp00 *.79 *.* LISTEN tcp 00 *.1023 *.* LISTEN tcp 00 *.111 *.* LISTEN udp00192.168.4.16.1634 208.197.169.249.2049 udp00192.168.4.16.1627 208.197.169.254.2049 udp00192.168.4.16.1371 208.197.169.195.2049 udp00*.* *.* udp00*.9999 *.* udp00 *.161 *.* udp00192.168.4.16.1039 192.168.4.16.1023 udp00192.168.4.16.1038 192.168.4.16.1023 udp 00 192.168.4.16.1037 192.168.4.16.1023 udp00192.168.4.16.1036 192.168.4.16.1023 udp00*.1022 *.* udp00*.1023 *.* udp00*.111 *.* udp00*.* *.* (state) ESTABLISHED ESTABLISHED LISTEN LISTEN LISTEN Chapter 42: Operational Mode Commands for System Monitoring show system connections extensive user@host> show system connections extensive Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 2 192.168.4.16.513 208.197.169.254.894 ESTABLISHED iss: 3972677059 sndup: 3972693435 sndcc: 10 snduna: 3972693435 sndnxt: 3972693437 sndwnd: 17376 sndmax: 3972693437 sndcwnd: 65535 sndssthresh: 1073725440 irs: 484187869 rcvup: 484188060 rcvcc: 98357 rcvnxt: 484188070 rcvadv: 484205446 rcvwnd: 17376 rtt: 1 srtt: 7 rttv: 5 rxtcur: 120 rxtshift: 0 rtseq: 1103707591 rttmin: 2 duration: 5011 mss: 1448 flags: REQ_SCALE RCVD_SCALE REQ_TSTMP RCVD_TSTMP RCVD_CC [0x41e0] tcp 0 0 192.168.4.16.513 208.197.169.195.945 ESTABLISHED iss: 1057609890 sndup: 1057790796 sndcc: 2 snduna: 1057790810 sndnxt: 1057790810 sndwnd: 17376 sndmax: 1057790810 sndcwnd: 39096 sndssthresh: 1073725440 irs: 3551947312 rcvup: 3551947422 rcvcc: 0 rcvnxt: 3551947422 rcvadv: 3551964798 rcvwnd: 17376 rtt: 0 srtt: 17 rttv: 11 rxtcur: 300 rxtshift: 0 rtseq: 0 rttmin: 2 duration: 125814 mss: 1448 flags: REQ_SCALE RCVD_SCALE REQ_TSTMP RCVD_TSTMP [0x1e0] udp0 0192.168.4.16.1634208.197.169.249.2049 udp0 0192.168.4.16.1627208.197.169.254.2049 udp0 0192.168.4.16.1371208.197.169.195.2049 udp 0 0*.* *.* udp0 0*.9999*.* udp 0 0*.161*.* udp0 0192.168.4.16.1039192.168.4.16.1023 udp0 0192.168.4.16.1038192.168.4.16.1023 udp0 0192.168.4.16.1037192.168.4.16.1023 udp0 0192.168.4.16.1036192.168.4.16.1023 udp0 0*.1022*.* udp 0 0*.1023 *.* udp0 0 *.111*.* udp0 0*.**.* show system connections show-routing-instances user@host> show system connections show-routing-instances Active Internet connections (including servers) (including routing-instances) Proto Recv-Q Send-Q Local Address Foreign Address Routing Instance (state) tcp4 0 0 192.168.69.204.23 172.17.28.19.4267 default ESTABLISHED tcp4 0 0 192.168.69.204.58540 10.209.7.138.23 default ESTABLISHED tcp4 0 0 192.168.69.204.23 172.17.28.19.1098 default ESTABLISHED tcp4 0 0 192.168.7.1.57668 192.168.9.1.179 default ESTABLISHED tcp4 0 0 192.168.7.1.179 192.168.8.1.49209 default ESTABLISHED tcp4 0 0 128.0.0.1.6234 128.0.3.17.1024 __juniper_private1__ ESTABLISHED tcp4 0 0 128.0.0.4.9000 128.0.0.4.59103 __juniper_private1__ ESTABLISHED tcp4 0 0 128.0.0.4.59103 128.0.0.4.9000 __juniper_private1__ ESTABLISHED tcp4 0 0 *.32012 *.* __juniper_private1__ LISTEN tcp4 0 0 *.9000 *.* 677 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS __juniper_private1__ tcp4 0 0 __juniper_private2__ tcp46 0 0 LISTEN tcp4 0 0 LISTEN tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private2__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private2__ tcp4 0 0 __juniper_private1__ tcp4 0 0 __juniper_private1__ tcp4 0 0 LISTEN 678 LISTEN *.33007 LISTEN *.179 *.* default *.179 *.* default *.6154 LISTEN *.6153 LISTEN *.7000 LISTEN *.6152 LISTEN *.6156 LISTEN *.33005 LISTEN *.31343 LISTEN *.31341 LISTEN *.32003 LISTEN *.666 LISTEN *.38 LISTEN *.3221 *.* *.* *.* *.* *.* *.* *.* *.* *.* *.* *.* *.* *.* default Chapter 42: Operational Mode Commands for System Monitoring show system core-dumps Syntax show system core-dumps Syntax (J-EX Series Switch show system core-dumps Release Information Description Command introduced before Junos OS Release 10.2 for J-EX Series switches. Show core files on all routers or switches running the Junos OS. You can use the show system core-dumps command to show a list of system core files created when the router or switch has failed. This command can be useful for diagnostic purposes. Each list item includes the file permissions, number of links, owner, group, size, modification date, and path/filename. You can use the option core-filename and its options core-file-info, brief, and detail to display more information about the specified core-dump files. Options none—Display a list of all existing core-dump files. all-members—(J-EX4200 switches only) (Optional) Display system core files on all members of the Virtual Chassis configuration. brief—(Optional) View details of binary. core-file-info—(Optional) Display the stack trace of a core file. core-filename—(Optional) Name of a specific core file to display. detail—(Optional) View stack trace with details of binary. local—(J-EX4200 switches only) (Optional) Display system core files on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display system core files 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 core-dumps on page 680 show system core-dumps on page 680 679 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output Fields Table 99 on page 680 describes the output fields for the show system core-dumps command. Output fields are listed in the approximate order in which they appear. Table 99: show system core-dumps Output Fields show system core-dumps Field Name Field Description Permissions Read/write permissions for the file named. Links Number of links to the file. Owner Name of the file owner. Group Name of the group with file access. File size File size in bytes. Modified Last file modification date and time. Path/filename File path where the file resides and the filename. This example shows the command output if core files exist. user@host> -rw-------rw-rw----rw-r--r-- show system core-dumps 680 show system core-dumps 1 root wheel 268369920 Jun 18 17:59 /var/crash/vmcore.0 1 root field 3371008 Jun 18 17:53 /var/tmp/rpd.core.0 1 root wheel 27775914 Jun 18 17:59 /var/crash/kernel.0 This example shows the command output if core files do not exist. user@host> show system core-dumps /var/crash/*core*: No such file or directory /var/tmp/*core*: No such file or directory /var/crash/kernel.*: No such file or directory Chapter 42: Operational Mode Commands for System Monitoring show system directory-usage Syntax show system directory-usage Syntax (J-EX Series Switch) show system directory-usage Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display directory usage information. none—Display all directory usage information. all-members—(J-EX4200 switches only) (Optional) Display directory information for all members of the Virtual Chassis configuration. depth number—(Optional) Depth of the directory to traverse. This option is useful when you want to limit the output shown for a large file system. local—(J-EX4200 switches only) (Optional) Display directory information for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display directory information for the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. path—(Optional) Path or root directory to traverse. Required Privilege Level Output Fields view Table 100 on page 681 describes the output fields for the show system directory-usage command. Output fields are listed in the approximate order in which they appear. Table 100: show system directory-usage Output Fields Field Name Field Description bytes Number of bytes used by files in a directory. directory-name Name of the directory. 681 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system processes Syntax show system processes Syntax (J-EX Series Switch) show system processes Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about software processes that are running on the router or switch and that have controlling terminals. none—Display standard information about system processes. all-members—(J-EX4200 switches only) (Optional) Display standard system process information for all members of the Virtual Chassis configuration. brief | detail | extensive | summary—(Optional) Display the specified level of detail. health (pid process-identifer | process-name process-name)—(Optional) Display process health information. local—(J-EX4200 switches only) (Optional) Display standard system process information for the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display standard system process information for the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. providers—(Optional) Display provider processes. resource-limits (brief | detail) process-name—(Optional) Display process resource limits. wide—(Optional) Display process information that might be wider than 80 columns. Required Privilege Level List of Sample Output 682 view show system processes on page 685 show system processes brief on page 685 show system processes detail on page 685 Chapter 42: Operational Mode Commands for System Monitoring show system processes extensive on page 686 show system processes summary on page 687 Output Fields Table 101 on page 683 describes the output fields for the show system processes command. Output fields are listed in the approximate order in which they appear. Table 101: show system processes Output Fields Field Name Field Description Level of Output last PID Last process identifier assigned to the process. brief extensive summary load averages Three load averages followed by the current time. brief extensive summary processes Number of existing processes and the number of processes in each state (sleeping, running, starting, zombies, and stopped). brief extensive summary Mem Information about physical and virtual memory allocation. brief extensive summary Swap Information about physical and virtual memory allocation. brief extensive summary PID Process identifier. detail extensive summary TT Control terminal name. none detail 683 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 101: show system processes Output Fields (continued) Field Name Field Description Level of Output STAT Symbolic process state. The state is given by a sequence of letters. The first letter indicates the run state of the process: none detail • D—In disk or other short-term, uninterruptible wait • I—Idle (sleeping longer than about 20 seconds) • R—Runnable • S—Sleeping for less than 20 seconds • T—Stopped • Z—Dead (zombie) • + —The process is in the foreground process group of its control terminal. • < —The process has raised CPU scheduling priority. • > —The process has specified a soft limit on memory requirements and is currently exceeding that limit; such a process is not swapped. • A—The process requested random page replacement. • E—The process is trying to exit. • L—The process has pages locked in core. • N—The process has reduced CPU scheduling priority. • S—The process requested first-in, first-out (FIFO) page replacement. • s—The process is a session leader. • V—The process is temporarily suspended. • W—The process is swapped out. • X—The process is being traced or debugged. UID User identifier. detail USERNAME Process owner. extensive summary PPID Parent process identifier. detail CPU (D)—Short-term CPU usage. detail extensive summary (E and S)—Raw (unweighted) CPU usage. The value of this field is used to sort the processes in the output. RSS Resident set size. detail WCHAN Symbolic name of the wait channel. detail STARTED Local time when the process started running. detail PRI Current priority of the process. A lower number indicates a higher priority. detail extensive summary NI or NICE UNIX "niceness" value. A lower number indicates a higher priority. detail extensive summary SIZE Total size of the process (text, data, and stack), in kilobytes. extensive summary 684 Chapter 42: Operational Mode Commands for System Monitoring Table 101: show system processes Output Fields (continued) Field Name Field Description Level of Output RES Current amount of resident memory, in kilobytes. extensive summary STATE Current state of the process (for example, sleep, wait, run, idle, zombie, or stop). extensive summary TIME (S)—Number of system and user CPU seconds that the process has used. detail extensive summary (None, D, and E)—Total amount of time that the command has been running. WCPU Weighted CPU usage. extensive summary COMMAND Command that is currently running. detail extensive summary show system processes show system processes brief user@host> show system processes PID TT STAT TIME COMMAND 0 ?? DLs 0:00.70 (swapper) 1 ?? Is 0:00.35 /sbin/init -2 ?? DL 0:00.00 (pagedaemon) 3 ?? DL 0:00.00 (vmdaemon) 4 ?? DL 0:42.37 (update) 5 ?? DL 0:00.00 (if_jnx) 80 ?? Ss 0:14.66 syslogd -s 96 ?? Is 0:00.01 portmap 128 ?? Is 0:02.70 cron 173 ?? Is 0:02.24 /usr/local/sbin/sshd (sshd1) 189 ?? S 0:03.80 /sbin/watchdog -t180 190 ?? I 0:00.03 /usr/sbin/tnetd -N 191 ?? S 2:24.76 /sbin/ifd -N 192 ?? S< 0:55.44 /usr/sbin/xntpd -N 195 ?? S 0:53.11 /usr/sbin/snmpd -N 196 ?? S 1:15.73 /usr/sbin/mib2d -N 198 ?? I 0:00.75 /usr/sbin/inetd -N 2677 ?? I 0:00.01 /usr/sbin/mgd -N 2712 ?? Ss 0:00.24 rlogind 2735 ?? R 0:00.00 /bin/ps -ax 1985 p0- S 0:07.41 ./rpd -N 2713 p0 Is 0:00.24 -tcsh (tcsh) 2726 p0 S+ 0:00.07 cli user@host> show system processes brief last pid: 543; load averages: 0.00, 37 processes: 1 running, 36 sleeping 0.00, 0.00 18:29:47 Mem: 25M Active, 3976K Inact, 19M Wired, 8346K Buf, 202M Free Swap: 528M Total, 64K Used, 528M Free show system processes detail user@host> show system processes detail PID UID PPID CPU PRI NI RSS WCHAN STARTED TT STAT 3151 1049 3129 2 28 0 672 1:13PM p0 R+ 1 0 0 0 10 0 376 wait 1:51PM ?? Is 2 0 0 0 -18 0 12 psleep 1:51PM ?? DL 3 0 0 0 28 0 12 psleep 1:51PM ?? DL 4 0 0 0 28 0 12 update 1:51PM ?? DL TIME COMMAND 0:00.00 ps -ax -r 0:00.29 /sbin/ini 0:00.00 (pagedae 0:00.00 (vmdaemo 0:07.15 (update) 685 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 5 27 81 119 134 151 183 206 207 208 210 211 215 219 220 221 222 735 736 1380 3019 3122 3128 3129 0 show system processes extensive 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1049 0 0 0 2 0 12 pfesel 1:51PM 1 0 10 0 17936 mfsidl 1:51PM 1 0 2 0 496 select 1:52PM 1 0 2 0 492 select 1:52PM 1 0 2 0 580 select 1:52PM 1 0 18 0 532 pause 1:52PM 1 0 2 0 420 select 1:52PM 1 0 18 0 72 pause 1:52PM 1 0 2 0 520 select 1:52PM 1 0 2 0 536 select 1:52PM 1 255 2 -12 740 select 1:52PM 1 0 2 0 376 select 1:52PM 1 0 2 0 548 select 1:52PM 1 0 3 0 540 ttyin 1:52PM 1 0 3 0 540 ttyin 1:52PM 1 0 3 0 540 ttyin 1:52PM 1 0 3 0 540 ttyin 1:52PM 1 0 2 0 468 select 2:47PM 1 0 2 0 212 select 2:47PM 1 0 3 0 888 ttyin 7:32PM 207 0 2 0 636 select 10:49AM 1380 0 2 0 1764 select 12:33PM 215 0 2 0 580 select 12:45PM 3128 0 18 0 944 pause 12:45PM 0 0 -18 0 0 sched 1:51PM user@host> show system processes extensive last pid: 544; load averages: 0.00, 37 processes: 1 running, 36 sleeping 0.00, ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? v0 v1 v2 v3 ?? ?? d0 ?? d0 ?? p0 ?? 0.00 IL Is Ss Is S Is Ss S I S S< S I Is+ Is+ Is+ Is+ S S Is+ Ss S Ss Ss DLs 0:02.90 0:00.46 0:31.21 0:00.00 0:02.95 0:00.34 0:00.07 0:00.51 0:00.16 0:08.21 0:05.83 0:00.03 0:00.50 0:00.02 0:00.01 0:00.01 0:00.01 0:19.14 0:14.13 0:00.46 0:02.93 0:00.77 0:00.12 0:00.14 0:00.10 18:30:33 Mem: 25M Active, 3968K Inact, 19M Wired, 8346K Buf, 202M Free Swap: 528M Total, 64K Used, 528M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU 544 root 30 0 604K 768K RUN 0:00 0.00% 0.00% 3 root 28 0 0K 12K psleep 0:00 0.00% 0.00% 4 root 28 0 0K 12K update 0:03 0.00% 0.00% 528 aviva 18 0 660K 948K pause 0:00 0.00% 0.00% 204 root 18 0 300K 544K pause 0:00 0.00% 0.00% 131 root 18 0 332K 532K pause 0:00 0.00% 0.00% 186 root 18 0 196K 68K pause 0:00 0.00% 0.00% 27 root 10 0 512M 16288K mfsidl 0:00 0.00% 0.00% 1 root 10 0 620K 344K wait 0:00 0.00% 0.00% 304 root 3 0 884K 900K ttyin 0:00 0.00% 0.00% 200 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% 203 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% 202 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% 201 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% 194 root 2 0 2248K 1640K select 0:11 0.00% 0.00% 205 root 2 0 964K 800K select 0:12 0.00% 0.00% 189 root 2 -12 352K 740K select 0:03 0.00% 0.00% 114 root 2 0 296K 612K select 0:00 0.00% 0.00% 188 root 2 0 780K 600K select 0:00 0.00% 0.00% 527 root 2 0 176K 580K select 0:00 0.00% 0.00% 195 root 2 0 212K 552K select 0:00 0.00% 0.00% 187 root 2 0 192K 532K select 0:00 0.00% 0.00% 83 root 2 0 188K 520K select 0:00 0.00% 0.00% 538 root 2 0 1324K 516K select 0:00 0.00% 0.00% 99 daemon 2 0 176K 492K select 0:00 0.00% 0.00% 163 root 2 0 572K 420K select 0:00 0.00% 0.00% 192 root 2 0 560K 400K select 0:10 0.00% 0.00% 191 root 2 0 1284K 376K select 0:00 0.00% 0.00% 686 (if_pfe) mfs /dev/ syslogd portmap amd -p -a cron /usr/loca /sbin/wat /usr/sbin /sbin/dcd /usr/sbin /usr/sbin /usr/sbin /usr/libe /usr/libe /usr/libe /usr/libe /usr/sbin /usr/sbin bash tnp.chass ./rpd -N rlogind -tcsh (tc (swapper COMMAND top vmdaemon update tcsh csh cron watchdog mount_mfs init bash getty getty getty getty rpd tnp.chassisd xntpd amd dcd rlogind inetd tnetd syslogd mgd portmap nsrexecd snmpd mgd Chapter 42: Operational Mode Commands for System Monitoring 537 193 5 2 0 show system processes summary aviva root root root root 2 2 2 -18 -18 0 0 0 0 0 636K 312K 0K 0K 0K 364K 204K 12K 12K 0K select select pfesel psleep sched user@host> show system processes summary last pid: 543; load averages: 0.00, 37 processes: 1 running, 36 sleeping 0:00 0:07 0:00 0:00 0:00 0.00, 0.00% 0.00% 0.00% 0.00% 0.00% 0.00 0.00% 0.00% 0.00% 0.00% 0.00% cli mib2d if_pfe pagedaemon swapper 18:29:47 Mem: 25M Active, 3976K Inact, 19M Wired, 8346K Buf, 202M Free Swap: 528M Total, 64K Used, 528M Free PID USERNAME PRI NICE SIZE 527 root 2 0 176K 543 root 30 0 604K RES STATE 580K select 768K RUN TIME 0:00 0:00 WCPU 0.04% 0.00% CPU COMMAND 0.04% rlogind 0.00% top 687 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 688 PART 11 Virtual Chassis • Virtual Chassis—Overview, Components, and Configurations on page 691 • Virtual Chassis—Configuration Examples on page 717 • Configuring Virtual Chassis on page 781 • Verifying Virtual Chassis Configuration on page 803 • Troubleshooting Virtual Chassis on page 815 • Configuration Statements for Virtual Chassis on page 817 • Operational Mode Commands for Virtual Chassis on page 835 689 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 690 CHAPTER 43 Virtual Chassis—Overview, Components, and Configurations • Virtual Chassis Overview on page 691 • Understanding Virtual Chassis Components on page 694 • Understanding How the Master in a Virtual Chassis Configuration Is Elected on page 698 • Understanding Software Upgrade in a Virtual Chassis Configuration on page 698 • Understanding Global Management of a Virtual Chassis Configuration on page 699 • Understanding Nonvolatile Storage in a Virtual Chassis Configuration on page 702 • Understanding the High-Speed Interconnection of the Virtual Chassis Members on page 702 • Understanding Virtual Chassis Configurations and Link Aggregation on page 702 • Understanding Virtual Chassis Configuration on page 704 • Understanding Virtual Chassis J-EX4200 Switch Version Compatibility on page 705 • Understanding Fast Failover in a Virtual Chassis Configuration on page 706 • Understanding Split and Merge in a Virtual Chassis Configuration on page 712 • Understanding Automatic Software Update on Virtual Chassis Member Switches on page 715 Virtual Chassis Overview The Dell PowerConnect J-Series J-EX4200 Ethernet Switch is the basis for the Virtual Chassis flexible, scaling switch solution. You can connect individual J-EX4200 switches together to form one unit and manage the unit as a single chassis, called a Virtual Chassis. Up to ten J-EX4200 switches can be interconnected, providing up to a total of 480 access ports. The available bandwidth increases as you include more members within the Virtual Chassis configuration. See “Understanding the High-Speed Interconnection of the Virtual Chassis Members” on page 702. This topic describes: • Basic Configuration of a Virtual Chassis with Master and Backup Switches on page 692 • Expanding Configurations—Within a Single Wiring Closet and Across Wiring Closets on page 692 691 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Global Management of Member Switches in a Virtual Chassis on page 693 • High Availability Through Redundant Routing Engines on page 693 • Adaptability as an Access Switch or Distribution Switch on page 693 Basic Configuration of a Virtual Chassis with Master and Backup Switches To take advantage of the Virtual Chassis configuration’s higher bandwidth capacity and software redundancy features, you need to interconnect at least two J-EX4200 switches in a Virtual Chassis configuration. You can start with a default configuration, composed of two J-EX4200 member switches interconnected through the dedicated 64-Gbps Virtual Chassis ports (VCPs) on their rear panels. These ports do not have to be configured. They are operational as soon as the member switches are powered on. See “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717 for additional information. Expanding Configurations—Within a Single Wiring Closet and Across Wiring Closets As your needs grow, you can easily expand the Virtual Chassis configuration to include more member switches. Within a single wiring closet, simply add member switches by cabling together the dedicated VCPs. For more information about expanding Virtual Chassis configurations within a single wiring closet, see “Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet” on page 722 and “Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration” on page 727. You can also expand a Virtual Chassis configuration beyond a single wiring closet. Interconnect switches located in multiple wiring closets or in multiple data center racks by installing the optional SFP or SFP+ uplink modules and connecting the uplink module ports or by connecting the 1-gigabit network interfaces in a J-EX4200-24F switch. The small form-factor pluggable (SFP) uplink module provides four ports for 1-gigabit transceivers. The SFP+ uplink module provides two ports for 10-gigabit SFP+ transceivers or four ports for 1-gigabit SFP transceivers. To use SFP and SFP+ uplink module ports or J-EX4200-24F network interfaces for interconnecting member switches, you must first explicitly configure them as Virtual Chassis ports (VCPs). This procedure includes configuring these ports of a standalone J-EX4200 switch as VCPs prior to interconnecting the new member switch with the existing Virtual Chassis configuration. See “Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets” on page 733 for detailed information. When you are creating a Virtual Chassis configuration with multiple members, you might want to deterministically control the role and member ID assigned to each member switch. You can do this by creating a preprovisioned configuration. See “Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File” on page 752 for more information. You can add switches to a preprovisioned configuration by using the autoprovisioning feature to automatically configure the uplink module ports as VCPs on the switches being added. See “Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure)” on page 786 for detailed information. 692 Chapter 43: Virtual Chassis—Overview, Components, and Configurations Global Management of Member Switches in a Virtual Chassis The interconnected member switches in a Virtual Chassis configuration operate as a single network entity. You run EZSetup only once to specify the identification parameters for the master, and these parameters implicitly apply to all members of the Virtual Chassis configuration. You can view the Virtual Chassis configuration as a single device in the J-Web user interface and apply various device management functions to all members of the Virtual Chassis configuration. The serial console port and dedicated out-of-band management port that are on the rear panel of the individual switches have global virtual counterparts when the switches are interconnected in a Virtual Chassis configuration. A virtual console allows you to connect to the master by connecting a terminal directly to the console port of any member switch. A virtual management Ethernet (VME) interface allows you to remotely manage the Virtual Chassis configuration by connecting to the out-of-band management port of any member switch through a single IP address. See “Understanding Global Management of a Virtual Chassis Configuration” on page 699. High Availability Through Redundant Routing Engines A Virtual Chassis configuration has a master and a backup, each of which has a Routing Engine. These redundant Routing Engines handle all routing protocol processes and control the Virtual Chassis configuration. See “High Availability Features for J-EX Series Switches Overview” on page 18 for further information on redundant Routing Engines and additional high availability features. Adaptability as an Access Switch or Distribution Switch A Virtual Chassis configuration supports a variety of user environments, because it can be composed of different models of J-EX4200 switches, with either 24 or 48 access ports, and with these having either full (24 or 48 ports) or partial (8 ports) Power over Ethernet (PoE) port capabilities. You can select different switch models to support various functions. For example, you might set up one Virtual Chassis access switch configuration composed of the full PoE models to support users sitting in cubicles equipped with PCs and VoIP phones. You could set up another Virtual Chassis configuration with partial PoE models to support the company's internal servers and configure one more Virtual Chassis configuration with partial PoE models to support the company's external servers. Alternatively, the Virtual Chassis configuration can be used as a distribution switch. For this type of deployment, you might select the J-EX4200-24F model to connect the distribution switch to multiple access switches located in different buildings on the campus. Related Documentation • Understanding Virtual Chassis Components on page 694 • Understanding How the Master in a Virtual Chassis Configuration Is Elected on page 698 • Understanding Virtual Chassis J-EX4200 Switch Version Compatibility on page 705 • Understanding Virtual Chassis Configurations and Link Aggregation on page 702 • Understanding Virtual Chassis Configuration on page 704 • J-EX4200 Switch Models on page 26 693 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Virtual Chassis Components A Virtual Chassis configuration allows you to interconnect two to ten J-EX4200 Ethernet Switches and run them as a single network entity. While it is true that you need at least two interconnected switches to take advantage of Virtual Chassis features, it is also true that any individual J-EX4200 switch has some Virtual Chassis components. This topic covers: • Virtual Chassis Ports (VCPs) on page 694 • Master Role on page 694 • Backup Role on page 695 • Linecard Role on page 695 • Member Switch and Member ID on page 696 • Mastership Priority on page 696 • Virtual Chassis Identifier (VCID) on page 697 Virtual Chassis Ports (VCPs) There are two dedicated Virtual Chassis ports (VCPs) on the rear panel of the J-EX4200 switch that are used exclusively to interconnect J-EX4200 switches in a Virtual Chassis configuration. The interfaces for these dedicated ports are operational by default when the ports are properly cabled. For an example of two J-EX4200 switches interconnected with their dedicated VCPs, see “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717. In addition, you can interconnect the switch with another J-EX4200 switch across a wider distance by installing an optional SFP or SFP+ uplink module in a J-EX4200 switch or by using the network interfaces in a J-EX4200-24F switch. To do this using uplink module ports, you need to install one uplink module in at least one J-EX4200 switch at each end of the link. You must set the uplink module ports or the J-EX4200-24F network interfaces to function as VCPs in order for the interconnected switches to be recognized as members of the same Virtual Chassis configuration. This procedure includes setting the uplink module ports or J-EX4200-24F network ports of a standalone J-EX4200 switch as VCPs prior to interconnecting the new member switch with the existing Virtual Chassis configuration. For an example of J-EX4200 switches interconnected with the uplink ports functioning as VCPs, see “Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets” on page 733. You can display the status of both the dedicated VCP interfaces and the uplink ports configured as VCP interfaces with the show virtual-chassis vc-port command. Master Role The member that functions in the master role: 694 • Manages the member switches. • Runs the Junos OS for J-EX Series Switches in a master role. Chapter 43: Virtual Chassis—Overview, Components, and Configurations • Runs the chassis management processes and control protocols. • Represents all the member switches interconnected within the Virtual Chassis configuration. (The hostname and other properties that you assign to this switch during setup apply to all members of the Virtual Chassis configuration.) When a J-EX4200 switch is powered on as a standalone switch, it is considered the master member. In a multimember Virtual Chassis configuration, one member functions as the master and a second member functions as the backup: • In a preprovisioned configuration, one of the two members assigned as routing-engine functions as the master member. The selection of which member assigned as routing-engine functions as master and which as backup is determined by the software based on the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. • In a configuration that is not preprovisioned, the selection of the master and backup is determined by the mastership priority value and secondary factors in the master election algorithm. Backup Role The member that functions in the backup role: • Maintains a state of readiness to take over the master role if the master fails. • Runs the Junos OS for J-EX Series switches in a backup role. • Synchronizes with the master in terms of protocol states, forwarding tables, and so forth, so that it is prepared to preserve routing information and maintain network connectivity without disruption in case the master is unavailable. You must have at least two member switches in a Virtual Chassis configuration in order to have a backup member. • In a preprovisioned configuration, one of the two members assigned as routing-engine functions in the backup role. The selection of which member assigned as routing-engine functions as master and which as backup is determined by the software based on the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. • In a configuration that is not preprovisioned, the selection of the master and backup is determined by the mastership priority value and secondary factors in the master election algorithm. Linecard Role A member that functions in the linecard role: • Runs only a subset of the Junos OS for J-EX Series switches. • Does not run the chassis control protocols. • Can detect certain error conditions (such as an unplugged cable) on any interfaces that have been configured on it through the master. 695 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS A Virtual Chassis configuration must have at least three members in order to include a linecard member. • In a preprovisioned configuration, you can explicitly configure a member with the role of linecard, which makes it ineligible for functioning as a master or backup. • In a configuration that is not preprovisioned, the members that are not selected as master or backup function as linecard members of the Virtual Chassis configuration. The selection of the master and backup is determined by the mastership priority value and secondary factors in the master election algorithm. Member Switch and Member ID Each physically discrete J-EX4200 switch is a potential member of a Virtual Chassis configuration. When a J-EX4200 switch is powered on, it receives a member ID that is displayed on the front-panel LCD. If the switch is powered on as a standalone switch, its member ID is always 0. When the switch is interconnected with other J-EX4200 switches in a Virtual Chassis configuration, its member ID (0 through 9) is assigned by the master based on various factors, such as the order in which the switch was added to the Virtual Chassis configuration. As each switch is added and powered on, it receives the next available (unused) member ID. If the Virtual Chassis configuration previously included a member switch and that member was physically disconnected or removed from the Virtual Chassis configuration, its member ID is not available for assignment as part of the standard sequential assignment by the master. For example, you might have a Virtual Chassis configuration composed of member 0, member 2, and member 3, because member 1 was removed. When you add another member switch and power it on, the master assigns it as member 4. However, you can use the request virtual-chassis renumber command to explicitly change the member ID of the new member switch to use member ID 1. The member ID distinguishes the member switches from one another. You use the member ID: • To assign a mastership priority value to a member switch • To configure interfaces for a member switch • To apply some operational commands to a member switch • To display status or characteristics of a member switch Mastership Priority In a configuration that is not preprovisioned, you can designate the role (master, backup, or linecard) that a member switch performs within the Virtual Chassis configuration by configuring its mastership priority (from 1 to 255). The mastership priority value is the factor with the highest precedence for selecting the master of the Virtual Chassis configuration. The default value for mastership priority is 128. When a J-EX4200 switch is powered on, it receives the default mastership priority value. Because it is the only member of the Virtual Chassis configuration, it is also the master. When you interconnect a standalone 696 Chapter 43: Virtual Chassis—Overview, Components, and Configurations switch to an existing Virtual Chassis configuration (which implicitly includes its own master), we recommend that you explicitly configure the mastership priority of the members that you want to function as the master and backup. We recommend that you specify the same mastership priority value for both the master and backup members. NOTE: Configuring the same mastership priority value for both the master and backup helps to ensure a smooth transition from master to backup in case the master becomes unavailable. It prevents the old master from preempting control from the backup in situations where the backup has taken control of the Virtual Chassis configuration due to the original master being unavailable. We also recommend that you configure the highest possible mastership priority value (255) for those two members, because that guarantees that these two members continue to function as the master and backup when other members are added to the Virtual Chassis configuration. Any other members of the Virtual Chassis configuration (members with lower mastership priority) are considered linecard members. In a preprovisioned configuration, the mastership priority value is assigned by the software, based on the specified role. Virtual Chassis Identifier (VCID) All members of a Virtual Chassis configuration share one Virtual Chassis identifier (VCID). This identifier is derived from internal parameters. When you are monitoring a Virtual Chassis configuration, the VCID is displayed in the user interface. Related Documentation • Virtual Chassis Overview on page 691 • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Command Forwarding Usage with a Virtual Chassis Configuration on page 803 697 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding How the Master in a Virtual Chassis Configuration Is Elected All switches that are interconnected in a Virtual Chassis configuration are member switches of that Virtual Chassis. Each Virtual Chassis configuration has one member that functions as the master and controls the Virtual Chassis configuration. When a Virtual Chassis configuration boots, the Junos OS for J-EX Series Switches automatically runs a master election algorithm to determine which member switch takes the role of master. The algorithm that the software uses to determine the master is as follows: 1. Choose the member with the highest user-configured mastership priority (255 is the highest possible value). 2. Choose the member that was master the last time the Virtual Chassis configuration booted. 3. Choose the member that has been included in the Virtual Chassis configuration for the longest period of time. (For this to be a deciding factor, there has to be a minimum time lapse of one minute between the power-ons of the individual interconnected member switches.) 4. Choose the member with the lowest MAC address. The variations among switch models, such as whether the switch has 48 or 24 ports, do not impact the master election algorithm. To ensure that a specific member is elected as the master: 1. Power on only the switch that you want to configure as master of the Virtual Chassis configuration. 2. Configure the mastership priority of that member to have the highest possible value (255). 3. Continue to configure other members through the master member, as desired. 4. Power on the other members. Related Documentation • Virtual Chassis Overview on page 691 • Understanding Virtual Chassis Components on page 694 • Understanding Virtual Chassis Configuration on page 704 Understanding Software Upgrade in a Virtual Chassis Configuration A Virtual Chassis configuration can be composed of multiple J-EX4200 Ethernet Switches and each member switch is running Junos OS packages. For ease of management, the Virtual Chassis configuration provides flexible methods to upgrade software releases. A new software release can be upgraded to the entire Virtual Chassis configuration or to a particular member in the Virtual Chassis configuration through a CLI or J-Web command. 698 Chapter 43: Virtual Chassis—Overview, Components, and Configurations A user can add software packages to either a single member of the Virtual Chassis configuration or to all members of the Virtual Chassis configuration at the same time. Related Documentation • Virtual Chassis Overview on page 691 • Understanding Virtual Chassis Components on page 694 • Understanding Automatic Software Update on Virtual Chassis Member Switches on page 715 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 Understanding Global Management of a Virtual Chassis Configuration A Virtual Chassis configuration is composed of multiple J-EX4200 Ethernet Switches, so it has multiple console ports and multiple out-of-band management Ethernet ports located on the rear panels of the switches. You can connect a PC or laptop directly to a console port of any member switch to set up and configure the Virtual Chassis. When you connect to the console port of any member switch, the console session is redirected to the master switch, as shown in Figure 7 on page 700. 699 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 7: Console Session Redirection If the master becomes unavailable, the console session is disconnected from the old master and a new session is established with the newly elected master. An out-of-band management Ethernet port is often referred to simply as a management Ethernet port. It uses a dedicated management channel for device maintenance and allows a system administrator to monitor and manage the switch by remote control. The Virtual Chassis configuration can be managed remotely through SSH or Telnet using a global management interface called the virtual management Ethernet (VME) interface. VME is a logical interface representing any and all of the out-of-band management ports on the member switches. When you connect to the Virtual Chassis configuration using the VME IP address, the connection is redirected to the master member as shown in Figure 8 on page 701. 700 Chapter 43: Virtual Chassis—Overview, Components, and Configurations Figure 8: Management Ethernet Port Redirection to VME If the master management Ethernet link is unavailable, the session is redirected through the backup management Ethernet link. If there is no active management Ethernet link on the backup, the VME interface chooses a management Ethernet link on one of the linecard members, selecting the linecard member with the lowest member ID as its first choice. You can configure an IP address for the VME global management interface at any time. You can perform remote configuration and administration of all members of the Virtual Chassis configuration through the VME interface. Related Documentation • Understanding Virtual Chassis Components on page 694 • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 701 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) on page 797 Understanding Nonvolatile Storage in a Virtual Chassis Configuration The J-EX4200 Ethernet Switch stores Junos OS system files in internal flash memory. In a Virtual Chassis configuration, both the master and the backup switch store the configuration information for all the member switches. • Nonvolatile Memory Features on page 702 Nonvolatile Memory Features The Junos OS for J-EX Series Switches optimizes the way the Virtual Chassis stores its configuration if a member switch or the Virtual Chassis configuration is shut down improperly: Related Documentation • If the master is not available, the backup switch takes on the role of the master and its internal flash memory takes over as the alternate location for maintaining nonvolatile configuration memory. • If a member switch is taken offline for repair, the master stores the configuration of the member switch. • Command Forwarding Usage with a Virtual Chassis Configuration on page 803 • Monitoring System Properties on page 550 Understanding the High-Speed Interconnection of the Virtual Chassis Members Two high-speed Virtual Chassis ports (VCPs) on the rear panel of the Virtual Chassis member switches enable the members to be interconnected and operate as a single, powerful switch. Each VCP interface is 32 Gbps bidirectional. When VCP interfaces are used to form a ring topology, each segment provides 64 Gbps bidirectional bandwidth. Because the VCP links act as point-to-point links, multiple segments of the ring can be used simultaneously. This allows the Virtual Chassis configuration bandwidth to scale as you interconnect more members within the ring topology. Related Documentation • Understanding Virtual Chassis Components on page 694 • Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches Understanding Virtual Chassis Configurations and Link Aggregation You can combine physical Ethernet ports belonging to different member switches of a Virtual Chassis configuration 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 702 Chapter 43: Virtual Chassis—Overview, Components, and Configurations load-balancing traffic across all available links. If one of the links fails, the system automatically load-balances traffic across all remaining links. You can select up to four uplink module ports or SFP network ports on a J-EX4200-24F switch that have been configured as Virtual Chassis ports (VCPs) to form a LAG. When you set uplink module ports or SFP network ports on Virtual Chassis member switches as uplink VCPs, connect at least two of those uplink VCPs on one member to at least two uplink VCPs on another member, and configure those uplink VCPs to operate at the same link speed, the uplink VCPs automatically form a LAG and each LAG is assigned a positive-integer identifier called a trunk ID. A LAG over uplink VCPs provides higher overall bandwidth for forwarding traffic between the member switches connected by the uplink VCPs, faster management communications, and greater redundancy of operations among the members than would be available without the LAG. All J-EX4200 Ethernet Switches have two dedicated VCPs. A LAG over uplink VCPs provides an additional Virtual Chassis link throughput of 20 Gbps for the J-EX4200-24T and J-EX4200-48T models and additional throughput of 28 Gbps for the J-EX4200-24F model. Up to eight Virtual Chassis LAGs can be created per member. See “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792 for information about configuring uplink module ports and SFP network ports on J-EX4200-24F switches as uplink VCPs. To verify that the LAG has been created, view the output of the command show virtual-chassis vc-port. NOTE: The interfaces that are included within a bundle or LAG are sometimes referred to as member interfaces. Do not confuse this term with member switches, which refers to J-EX4200 switches that are interconnected as a Virtual Chassis. It is possible to create a LAG that is composed of member interfaces that are located in different member switches of a Virtual Chassis. Related Documentation • Virtual Chassis Overview on page 691 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring Link Aggregation Groups Using Uplink Virtual Chassis Ports on page 769 703 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Virtual Chassis Configuration You configure and manage almost all aspects of a Virtual Chassis configuration through the master of the Virtual Chassis. However, you can also configure Virtual Chassis parameters when a J-EX4200 Ethernet Switch is a standalone switch not interconnected with other members. A J-EX4200 switch has some innate characteristics of a Virtual Chassis by default. A standalone J-EX4200 switch is assigned member ID 0 and is the master of itself. Therefore, you can edit its Virtual Chassis configuration. When the standalone switch is interconnected with an existing Virtual Chassis configuration, the Virtual Chassis configuration statements and any uplink Virtual Chassis port (VCP) settings that you previously specified on the standalone switch remain part of its configuration. A switch is not recognized as a member of a Virtual Chassis until it is interconnected with the master or interconnected with an existing member of the Virtual Chassis. When a switch is located too far away to be interconnected through dedicated VCPs, you can specify an uplink module port or a J-EX4200-24F network interface as a VCP by using the request virtual-chassis vc-port command. You must issue the request virtual-chassis vc-port command on the switch you are adding to the Virtual Chassis as well as on the existing member switch that you will connect to the new member. Because the to-be-added switch is not yet a member, the master switch will not recognize that added switch unless the latter has an uplink VCP. A link aggregation group (LAG) will be formed automatically when the new switch is added to the configuration if more than one such link with the same speed is detected between uplink VCPs on the new member and an existing member. See “Understanding Virtual Chassis Configurations and Link Aggregation” on page 702. When an uplink module port or a J-EX4200-24F network interface is set as a VCP, it cannot be used for any additional purpose. If you want to use the uplink module port or J-EX4200-24F network interface for another purpose, you can delete the VCP setting by using the request virtual-chassis vc-port command. You can execute this command directly on the member whose uplink VCP setting you want to delete or through the master of the Virtual Chassis configuration. CAUTION: Deleting a VCP in a Virtual Chassis chain configuration can cause the Virtual Chassis configuration to split. For more information, see “Understanding Split and Merge in a Virtual Chassis Configuration” on page 712. You can create a preprovisioned configuration. This type of configuration allows you to deterministically control the member ID and role assigned to a member switch by associating the switch with its serial number. For an example of a preprovisioned configuration, see “Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File” on page 752. 704 Chapter 43: Virtual Chassis—Overview, Components, and Configurations NOTE: If a J-EX4200 switch is interconnected with other switches in a Virtual Chassis configuration, each individual switch that is included as a member of the configuration is identified with a member ID. The member ID functions as an FPC slot number. When you are configuring interfaces for a Virtual Chassis configuration, you specify the appropriate member ID (0 through 9) as the slot element of the interface name. The default factory settings for a Virtual Chassis configuration include FPC 0 as a member of the default VLAN because FPC 0 is configured as part of the ethernet-switching family. In order to include FPC 1 through FPC 9 in the default VLAN, add the ethernet-switching family to the configurations for those interfaces. Related Documentation • Understanding Virtual Chassis Components on page 694 • Understanding How the Master in a Virtual Chassis Configuration Is Elected on page 698 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • request virtual-chassis vc-port on page 840 Understanding Virtual Chassis J-EX4200 Switch Version Compatibility For J-EX4200 Ethernet Switches to be interconnected as a Virtual Chassis configuration, the switches must be running the same software versions. The master checks the hardware version, the Junos OS version, and other component versions running in a switch that is physically interconnected to its Virtual Chassis port (VCP). Different hardware models can be members of the same Virtual Chassis configuration. However, the master will not assign a member ID to a switch that is running a different software version. A switch that is running a different version of software will not be allowed to join the Virtual Chassis configuration. Related Documentation • Understanding Virtual Chassis Components on page 694 • Understanding Software Upgrade in a Virtual Chassis Configuration on page 698 • Understanding Software Installation on J-EX Series Switches on page 61 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 70 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 75 705 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Fast Failover in a Virtual Chassis Configuration The Virtual Chassis fast failover feature is a hardware-assisted failover mechanism that automatically reroutes traffic and reduces traffic loss in the event of a link failure or switch failure. If a link between two members fails, traffic flow between those members must be rerouted quickly so that there is minimal traffic loss. Fast failover is effective only for Virtual Chassis members configured in ring topologies using identical port types. This topic describes the following: • Supported Topologies for Fast Failover on page 706 • How Fast Failover Works on page 706 • Effects of Topology Changes on a Fast Failover Configuration on page 711 Supported Topologies for Fast Failover For fast failover to be effective, the Virtual Chassis members must be configured in a ring topology. The ring topology can be formed by using either dedicated Virtual Chassis ports (VCPs) or user-configured uplink module VCPs. Fast failover is supported only in a ring topology that uses identical port types, for example, either a topology that uses all dedicated VCPs or one that uses all uplink module VCPs. Fast failover is not supported in a ring topology that includes both dedicated VCPs and uplink module VCPs. Fast failover is supported, however, in a Virtual Chassis configuration that consists of multiple rings. How Fast Failover Works When fast failover is activated, each VCP is automatically configured with a backup port of the same type (dedicated VCP or SFP uplink VCP). If a VCP fails, its backup port is used to send traffic. These backup ports act as standby ports and are not meant for load-balancing purposes. Fast Failover in a Ring Topology using Dedicated VCPs When fast failover is activated in a ring topology that uses dedicated VCPs, each VCP is automatically configured with a backup port of the same type. If a VCP fails, its backup port is used to send traffic. Figure 9 on page 707 shows normal traffic flow in a ring topology using dedicated VCPs. 706 Chapter 43: Virtual Chassis—Overview, Components, and Configurations Figure 9: Normal Traffic Flow in a Ring Topology Using Dedicated VCPs Figure 10 on page 708 shows traffic redirected by fast failover. 707 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 10: Traffic Redirected by Fast Failover After Dedicated VCP Link Failure When the failed link is restored, the Virtual Chassis reconfigures the topology to the topology's original state. Fast Failover in a Ring Topology Using Uplink Module VCPs In a ring topology that uses uplink module VCPs, each uplink module VCP is automatically configured with a backup uplink module VCP. If an uplink module VCP fails, its backup port is used to send traffic. Figure 11 on page 709 shows normal traffic flow in a ring topology using SFP uplink module VCPs. NOTE: In order to use SFP uplink module ports as VCPs, you must configure them to be VCPs using the request virtual-chassis vc-port command. Once configured, they will be converted into VCPs. For example xe-0/1/0 will become vcp-255/1/0 after you configure it to be a VCP. 708 Chapter 43: Virtual Chassis—Overview, Components, and Configurations Figure 11: Normal Traffic Flow in a Ring Topology Using SFP Uplink Module VCPs Figure 12 on page 710 shows traffic redirected by fast failover. 709 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 12: Traffic Redirected by Fast Failover After SFP Uplink Module VCP Link Failure In a ring topology that uses SFP uplink module VCPs, there are four ports per module. Consecutive pair of ports are automatically configured as backup ports for each other. For example, if a Virtual Chassis member has an SFP uplink module installed, uplink module VCPs ge-0/1/0 and ge-0/1/1 are automatically configured as the backup port for the other port in the pair. Similarly, ports ge-0/1/2 and ge-0/1/3 are automatically configured as the backup port for the other port in the pair. Fast Failover in a Virtual Chassis Configuration Using Multiple Ring Topologies Fast failover is supported in a Virtual Chassis configuration with a multiple-ring topology, as shown in Figure 13 on page 711. 710 Chapter 43: Virtual Chassis—Overview, Components, and Configurations Figure 13: Traffic Redirected by Fast Failover After VCP Link Failures in a Topology with Multiple Rings In this scenario, the Virtual Chassis configuration has three rings: two rings that use dedicated VCPs and one ring that uses SFP uplink module VCPs. Fast failover works independently on each ring. Each dedicated VCP in a ring is backed up by another dedicated VCP. Similarly, each SFP uplink module VCP is backed up by another SFP uplink module VCP. Fast failover does not support a ring topology consisting of a mix of dedicated VCPs and uplink module VCPs. Effects of Topology Changes on a Fast Failover Configuration Once the fast failover feature has been activated, topology changes to the Virtual Chassis configuration do not affect the fast failover configuration. In the event of a link or switch failure, fast failover functions normally. 711 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Understanding Virtual Chassis Configuration on page 704 • Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Intermember Link Fails on page 763 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 Understanding Split and Merge in a Virtual Chassis Configuration In a Virtual Chassis configuration, two or more J-EX4200 Ethernet Switches are connected together to form a unit that is managed as a single chassis. If there is a disruption to the Virtual Chassis configuration due to member switches failing or being removed from the configuration, the Virtual Chassis configuration splits into two separate Virtual Chassis. This situation could cause disruptions in the network if the two separate configurations share common resources, such as global IP addresses. The split and merge feature provides a method to prevent the separate Virtual Chassis configurations from adversely affecting the network and also allows the two parts to merge back into a single Virtual Chassis configuration. NOTE: If a Virtual Chassis configuration splits into separate parts, we recommend that you resolve the problem that caused the Virtual Chassis configuration to split as soon as possible. You can also use this feature to merge two active but separate Virtual Chassis that have not previously been part of the same configuration into one Virtual Chassis configuration. NOTE: The split and merge feature is enabled by default on J-EX4200 switches. You can disable the split and merge feature by using the set virtual-chassis no-split-detection command. This topic describes: • What Happens When a Virtual Chassis Configuration Splits on page 712 • Merging Virtual Chassis Configurations on page 713 What Happens When a Virtual Chassis Configuration Splits When a Virtual Chassis configuration splits into two separate Virtual Chassis configurations, the individual member switches detect this topology change and run the master election algorithm to select a new master for each of the two Virtual Chassis configurations. The new masters then determine whether their Virtual Chassis configuration remains active. One of the configurations remains active based on the following: • 712 It contains both the stable master and the stable backup (that is, the master and backup from the original Virtual Chassis configuration before the split). Chapter 43: Virtual Chassis—Overview, Components, and Configurations • It contains the stable master and the configuration is greater than half the Virtual Chassis size. • It contains the stable backup and is at least half the Virtual Chassis size. Due to the rules given in the second and third list items, if the Virtual Chassis configuration splits into two equal parts and the stable master and stable backup are in different parts, then the part that contains the stable backup will become active. NOTE: The number of members in the Virtual Chassis configuration includes all member switches connected to date minus the number whose Virtual Chassis member IDs have been recycled. Therefore, the size of the Virtual Chassis configuration increases when a new member switch is detected and decreases when a member switch's ID is recycled (that is, made available for reassignment). These rules ensure that only one of the two separate Virtual Chassis configurations created by the split remains active. The member switches in the inactive Virtual Chassis configuration remain in a linecard role. For the inactive members to become active again, one of the following things must happen: • The problem that caused the original Virtual Chassis configuration to split is resolved, allowing the two Virtual Chassis configurations to merge. • You load the factory default configuration on the inactive members, which causes the inactive members to function as standalone switches or become part of a different Virtual Chassis configuration. NOTE: When you remove a member switch from a Virtual Chassis configuration, you should recycle the member ID using the request virtual-chassis recycle command. Merging Virtual Chassis Configurations There are two scenarios in which separate Virtual Chassis merge: • A Virtual Chassis configuration that had split into two is now merging back into a single configuration because the problem that had caused it to split has been resolved. • You want to merge two Virtual Chassis that had not previously been configured together. Every Virtual Chassis configuration has a unique ID that is automatically assigned when the Virtual Chassis configuration is formed. You can also explicitly assign a Virtual Chassis ID using the set virtual-chassis id command. A Virtual Chassis ID that you assign takes precedence over automatically assigned Virtual Chassis IDs. When you reconnect the separate Virtual Chassis configurations or connect them for the first time, the members determine whether or not the separate Virtual Chassis 713 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS configurations can merge. The members use the following rules to determine whether a merge is possible: • If the Virtual Chassis configurations have the same Virtual Chassis ID, then the configurations can merge. If the two Virtual Chassis were formed as the result of a split, they will have the same Virtual Chassis ID. • If the Virtual Chassis IDs are different, then the two configurations can merge only if both are active (inactive configurations cannot merge, ensuring that members removed from one Virtual Chassis configuration do not become members of another Virtual Chassis configuration). If the configurations to merge are both active and one of them has a user-configured Virtual Chassis ID, this ID becomes the ID of the merged Virtual Chassis. If neither Virtual Chassis has a user-configured Virtual Chassis ID, then the Virtual Chassis ID of the configuration with the highest mastership priority becomes the ID of the merged Virtual Chassis. The resulting merged Virtual Chassis configuration will be active. When you connect two Virtual Chassis configurations, the following events occur: 1. Connecting the two split Virtual Chassis configurations triggers the shortest-path-first (SPF) algorithm. The SPF algorithm computes the network topology and then triggers the master election algorithm. The master election algorithm waits for the members to synchronize the topology information before running. 2. The master election algorithm merges the Virtual Chassis IDs of all the members. 3. Each member runs the master election algorithm to select a master and a backup from among all members with the same Virtual Chassis IDs. For more information, see “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. 4. The master determines whether the Virtual Chassis configuration is active or inactive. (See “What Happens When a Virtual Chassis Configuration Splits” on page 712.) 5. If the Virtual Chassis configuration is active, the master assigns roles to all members. If the Virtual Chassis configuration is inactive, the master assigns all members the role of linecard. 6. When the other members receive their role from the master, they change their role to backup or linecard. They also use the active or inactive state information sent by the master to set their own state to active or inactive and to construct the Virtual Chassis member list from the information sent by the master. 7. If the Virtual Chassis state is active, the master waits for messages from the members indicating that they have changed their roles to the assigned roles, and then the master changes its own role to master. 714 Chapter 43: Virtual Chassis—Overview, Components, and Configurations NOTE: When you merge two Virtual Chassis that had not previously been part of the same Virtual Chassis configuration, any configuration settings (such as the settings for Telnet/FTP services, GRES, fast failover, VLANs, and so on) that exist on the new master will become the configuration settings for all members of the new Virtual Chassis, overwriting any other configuration settings. Related Documentation • Understanding Virtual Chassis Configuration on page 704 • Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge on page 767 • Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge (CLI Procedure) on page 800 • Disabling Split and Merge in a Virtual Chassis Configuration (CLI Procedure) on page 799 Understanding Automatic Software Update on Virtual Chassis Member Switches The automatic software update feature automatically updates the Junos OS version on prospective member switches as they are added to a Virtual Chassis configuration of J-EX4200 Ethernet Switches so the new member switch immediately joins the Virtual Chassis configuration and is put in the active state. For a standalone J-EX4200 switch to join an existing Virtual Chassis configuration, it must be running the same version of Junos OS that is running on the Virtual Chassis master. When the master in a Virtual Chassis configuration detects that a new switch has been added to the configuration, it checks the software version on the new switch. If the software version on the new switch is not the same as the version running on the master, the master keeps the new switch in the inactive state. If you have not enabled the automatic software update feature, you will have to manually install the correct software version on each prospective member switch as it is added to the Virtual Chassis configuration. Related Documentation • Understanding Software Upgrade in a Virtual Chassis Configuration on page 698 • Example: Configuring Automatic Software Update on Virtual Chassis Member Switches on page 777 • Configuring Automatic Software Update on Virtual Chassis Member Switches (CLI Procedure) on page 800 715 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 716 CHAPTER 44 Virtual Chassis—Configuration Examples • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Intermember Link Fails on page 763 • Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge on page 767 • Example: Configuring Link Aggregation Groups Using Uplink Virtual Chassis Ports on page 769 • Example: Configuring Automatic Software Update on Virtual Chassis Member Switches on page 777 Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet A Virtual Chassis configuration is a scalable switch. You can provide secure, redundant network accessibility with a basic two-member Virtual Chassis configuration and later expand the Virtual Chassis configuration to provide additional access ports as your office grows. 717 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to configure a Virtual Chassis with a master and backup in a single wiring closet: • Requirements on page 718 • Overview and Topology on page 718 • Configuration on page 720 • Verification on page 720 • Troubleshooting the Virtual Chassis on page 721 Requirements This example uses the following hardware and software components: • One J-EX4200-48T switch • One J-EX4200-24T switch • One uplink module Before you begin, be sure you have: 1. Rack-mounted the switches. See Mounting a J-EX4200 Switch on Two Posts in a Rack or Cabinet or Mounting a J-EX4200 Switch on Four Posts in a Rack or Cabinet or Mounting a J-EX4200 Switch on a Desk or Other Level Surface. 2. Installed the uplink module. See Installing an Uplink Module in a J-EX4200 Switch. 3. Cabled the switches. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch. Overview and Topology A Virtual Chassis configuration allows you to accommodate the networking needs of a growing office. The default configuration of a two-member Virtual Chassis includes a master and a backup switch. In addition to providing more access ports than a single J-EX4200 switch can provide, a Virtual Chassis configuration provides high availability through redundancy. This example shows a Virtual Chassis configuration composed of two J-EX4200 switches. One of the switches has an uplink module with ports that can be configured to connect to a distribution switch or customer edge (CE) router or that can be configured as Virtual Chassis ports (VCPs) to interconnect with a member switch that is located too far for the dedicated VCP cabling. (The network interfaces on J-EX4200-24F switches can also be configured as VCPs.) For information on configuring the uplink ports as trunk ports to a distribution switch, see “Configuring Gigabit Ethernet Interfaces (CLI Procedure)” on page 919. For an example of configuring uplink ports as VCPs, see “Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets” on page 733. By default, after you interconnect the switches with the dedicated VCPs and power on the switches, the VCPs are operational. The mastership priorities and member IDs are assigned by the software. The software elects a master based on several criteria, including how long a member switch has belonged to the Virtual Chassis configuration. For additional details, see “Understanding How the Master in a Virtual Chassis Configuration 718 Chapter 44: Virtual Chassis—Configuration Examples Is Elected” on page 698. Therefore, we recommend that you start by powering on only one member switch, the one that you want to function as the master. NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis. The Virtual Chassis configuration provides networking access for 50 onsite workers, who are sitting within range of a single wiring closet. The workers all use personal computers and VoIP phones. As the office grows, you can add more J-EX4200 switches to meet increased needs for access ports. The topology for this example consists of two switches, one of which contains an uplink module: • One J-EX4200-48T switch (SWA-0) with 48 access ports, all of which support PoE • One J-EX4200-24T switch (SWA-1) with 24 access ports, including eight ports that support PoE • One uplink module, with two 10-Gigabit Ethernet ports, is installed in SWA-1. Table 102 on page 719 shows the default configuration settings for the two-member Virtual Chassis. Table 102: Components of the Basic Virtual Chassis Access Switch Topology Member Switch Hardware Member ID Role and Priority SWA-0 J-EX4200-48T switch 0 Master: mastership priority 128 SWA-1 J-EX4200-24T switch 1 Backup: mastership priority 128 Figure 14 on page 719 shows that SWA-0 and SWA-1 are interconnected with their dedicated VCPs on the rear panel. The LCD on the front displays the Member ID and Role. SWA-0 also includes an uplink module. Its uplink ports can be used to connect to a distribution switch. Figure 14: Basic Virtual Chassis with Master and Backup 719 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuration Configure a Virtual Chassis with a default master and backup in a single wiring closet: Step-by-Step Procedure To configure a Virtual Chassis with master and backup: 1. Make sure the VCPs on the rear panel of the member switches are properly cabled. See Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches. 2. Power on SWA-0 (the member switch that you want to function as the master). 3. Check the front-panel LCD to confirm that the switch has powered on correctly. 4. Run the EZ Setup program on SWA-0, specifying the identification parameters. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. 5. Configure SWA-0 with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis configuration, if desired. [edit] user@SWA-0# set interfaces vme unit 0 family inet address /ip-address/mask/ 6. Power on SWA-1. Verification To confirm that the Virtual Chassis configuration is operational, perform these tasks: • Verifying That the Mastership Priority Is Assigned Appropriately on page 720 • Verifying That the VCPs Are Operational on page 721 Verifying That the Mastership Priority Is Assigned Appropriately Purpose Action Verify that the master, which has been selected by default, is the member switch that you want to function in that role. 1. Check the front-panel LCD to confirm that the switch has powered on correctly and that a member ID has been assigned. 2. List the member switches of the Virtual Chassis configuration. user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0019.e250.47a0 Member ID 0 (FPC 0) Status Prsnt Mastership Serial No Model priority AK0207360276 ex4200-48t 128 Role Master* 1 (FPC 1) Prsnt AK0207360281 ex4200-24t Backup Member ID for next new member: 2 (FPC 2) 720 128 Neighbor List ID Interface 1 vcp-0 1 vcp-1 0 vcp-0 0 vcp-1 Chapter 44: Virtual Chassis—Configuration Examples Meaning The show virtual-chassis status command lists the member switches interconnected in a Virtual Chassis configuration with the member IDs that have been assigned by the master, the mastership priority values, and the roles. It also displays the neighbor members with which each member is interconnected. The output shows that SWA-0, member 0, has been assigned default mastership priority 128. Because SWA-0 is the first member to be powered on, it has the most seniority and is therefore assigned the role of master. SWA-1 is powered on after member 0, so it is assigned the role of backup. The member IDs are displayed on the front panel of the switches. Check and confirm whether the default assignment is satisfactory. Verifying That the VCPs Are Operational Purpose Action Verify that the dedicated Virtual Chassis ports interconnecting the switches are operational. Display the Virtual Chassis ports of all the members: user@SWA-0> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up 32000 1 vcp-1 vcp-1 Dedicated Up 32000 1 vcp-0 fpc1: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up 32000 1 vcp-0 vcp-1 Dedicated Up 32000 1 vcp-1 Meaning The show virtual-chassis vc-port command lists the interfaces that are enabled for the member switches of the Virtual Chassis configuration and shows the status of the interfaces. The output in this example shows that two of the VCPs are operational and two VCPs are not. A single cable has been used to interconnect vcp-0 of member ID 0 and vcp-0 of member ID 1. That interconnection is sufficient for the switch to be operational. However, we recommend that you connect the second set of VCPs for redundancy. Troubleshooting the Virtual Chassis To troubleshoot the configuration of a Virtual Chassis, perform these tasks: Troubleshooting the Assignment of Roles Problem The master and backup roles are not assigned to the member switches that you want to function in these roles. Solution Modify the mastership priority values. 721 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To quickly modify the mastership priority of SWA-1 (member ID 1), copy the following command and paste it into the switch terminal window: [edit virtual-chassis] user@SWA-1# set member 1 mastership-priority 255 Troubleshooting the VCPs Problem The VCPs are down. Solution 1. Check to make sure that you have cabled the appropriate ports. 2. Check to make sure that the cables are seated properly. You should generally cable and interconnect both of the VCPs on the member switches, for redundancy and high availability. Related Documentation • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet A Virtual Chassis configuration is a scalable switch composed of multiple interconnected J-EX4200 switches. Up to ten J-EX4200 switches can be interconnected as a Virtual Chassis configuration. This example describes how to configure an expanding Virtual Chassis within a single wiring closet: • Requirements on page 722 • Overview and Topology on page 723 • Configuration on page 724 • Verification on page 725 • Troubleshooting on page 726 Requirements This example uses the following hardware and software components: 722 • One J-EX4200-48T switch • Two J-EX4200-24T switches • One uplink module Chapter 44: Virtual Chassis—Configuration Examples Before you begin, be sure you have: • Confirmed that the existing Virtual Chassis configuration is operating correctly. See “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717. Overview and Topology A Virtual Chassis configuration can be expanded without disrupting the site's network connectivity. This example describes adding a member switch to an existing Virtual Chassis configuration to provide additional access ports for connecting more PCs and VoIP phones at this location. You can continue to expand the Virtual Chassis configuration with additional members in the same wiring closet, using the same procedure. If you want to expand the Virtual Chassis configuration to include member switches in another wiring closet, see “Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets” on page 733. If you want to retain the roles of the existing master and backup switches, explicitly configure the mastership priority of these switches, specifying the highest possible value (255) for both the master and the backup. During expansion, the existing Virtual Chassis configuration can remain powered on and connected to the network. Before powering up the new switch, interconnect it to the other the switches using the dedicated VCPs on the rear panel. Do not run the EZ Setup program on the added member switch. This example shows an existing Virtual Chassis configuration composed of two J-EX4200 switches. The Virtual Chassis configuration is being expanded to include a J-EX4200-24T switch as a linecard member. The topology for this example consists of: • One J-EX4200-48T switch (SWA-0) with 48 access ports, 8 of which support Power over Ethernet (PoE) • Two J-EX4200-24T switch (SWA-1 and SWA-2) each with 24 access ports, including 8 ports that support PoE • One uplink module with two 10-gigabit ports is installed in the J-EX4200-48T switch. These ports can be configured as trunk ports to connect to a distribution switch or customer edge (CE) router or as Virtual Chassis ports (VCPs) to interconnect with a member switch that is located too far for dedicated VCP cabling. (The uplink module ports on the SFP and SFP+ uplink modules and the SFP network interfaces on the J-EX4200-24F switches can also be used for these purposes.) For information on configuring the uplink ports as trunk ports to a distribution switch, see “Configuring Gigabit Ethernet Interfaces (CLI Procedure)” on page 919 or “Configuring Gigabit Ethernet Interfaces (J-Web Procedure)” on page 909. For information on configuring uplink ports as Virtual Chassis ports, see “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792. Table 103 on page 724 shows the configuration settings for the expanded Virtual Chassis. 723 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 103: Components of the Expanded Virtual Chassis Access Switch Member Switch Hardware Member ID Role in Virtual Chassis SWA-0 J-EX4200-48T switch 0 master; mastership priority 255 SWA-1 J-EX4200-24T switch 1 backup; mastership priority 255 SWA-2 J-EX4200-24T switch 2 linecard; mastership priority 128 Figure 15 on page 724 shows that the three member switches ( SWA-0, SWA-1 and SWA-2) are interconnected with their dedicated VCPs on the rear panel. The LCD on the front displays the member ID and role. SWA-0 also includes an uplink module. Its uplink ports can be used to connect to a distribution switch. Figure 15: Expanded Virtual Chassis in Single Wiring Closet Configuration To expand a Virtual Chassis configuration to include additional member switches within a single wiring closet, perform these tasks: NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis configuration. CLI Quick Configuration To maintain the master and backup roles of the existing members and ensure that the new member switch functions in a linecard role, copy the following commands and paste them into the terminal window: [edit] user@SWA-0# set virtual-chassis member 0 mastership-priority 255 user@SWA-1# set virtual-chassis member 1 mastership-priority 255 724 Chapter 44: Virtual Chassis—Configuration Examples Step-by-Step Procedure To ensure that the existing member switches retain their current roles and to add another member switch in a linecard role: 1. Configure the mastership priority of SWA-0 (member 0) to be the highest possible value, thereby ensuring that it functions as the master of the expanded Virtual Chassis configuration. [edit virtual-chassis] user@SWA-0# set member 0 mastership-priority 255 2. Configure the mastership priority of SWA-1 (member 1) to be the highest possible value. This setting is recommended for high availability and smooth transition of mastership in case the original master becomes unavailable. [edit virtual-chassis] user@SWA-1# set member 1 mastership-priority 255 3. Interconnect the unpowered SWA-2 with SWA-0 and SWA-1 using the dedicated VCPs on the rear panel. See Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches for additional information. 4. Power on SWA-2. You do not need to configure or run EZ Setup on SWA-2. The identification parameters that were set up for the master apply implicitly to all members of the Virtual Chassis configuration. SWA-2 functions in a linecard role, since SWA-0 and SWA-1 have been configured to the highest mastership priority values. Verification To verify that the new switch has been added as a linecard and that its VCPs are operational, perform these tasks: • Verifying That the New Switch Has Been Added as a Linecard on page 725 • Verifying That the VCPs Are Operational on page 726 Verifying That the New Switch Has Been Added as a Linecard Purpose Action Verify that SWA-2 has been added in a linecard role to the Virtual Chassis configuration. Use the show virtual-chassis status command to list the member switches with their member IDs, mastership priority values, and assigned roles. user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0000.e255.00e0 Mastership Priority Role Neighbor List ID Interface Member ID Status Serial No Model 0 (FPC 0) Prsnt abc123 ex4200-48t 255 Master* 1 vcp-0 2 vcp-1 1 (FPC 1) Prsnt def456 ex4200-24t 255 Backup 2 vcp-0 0 vcp-1 725 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2 (FPC 2) Meaning Prsnt abd231 ex4200-24tp 128 Linecard 0 vcp-0 1 vcp-1 The show virtual-chassis status command lists the member switches of the Virtual Chassis configuration with the member IDs and mastership priority values. It also displays the neighbor members with which each member is interconnected. This output shows that SWA-2 has been assigned member ID 2 and has the default mastership priority value 128. Because the mastership priority is lower than the mastership priority of the other members, SWA-2 functions in the linecard role. You can continue to add more member switches, following the same procedure. It is possible to have multiple members in linecard roles with the same mastership priority value. Verifying That the VCPs Are Operational Purpose Action Verify that the dedicated VCPs interconnecting the member switches are operational. List the VCP interfaces on the Virtual Chassis configuration. user@SWA-0>show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc1: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc2: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up Meaning The show virtual-chassis vc-port all-members command lists all the interfaces for the Virtual Chassis configuration. In this case, no VCP uplinks have been configured. However, the VCP interfaces are automatically configured and enabled when you interconnect member switches using the dedicated Virtual Chassis ports. There are two dedicated VCPs on the rear panel of each J-EX4200 switch. It is recommended that you interconnect the member switches using both VCPs for redundancy. The VCP interfaces are identified simply as vcp-0 and vcp-1. The fpc number is the same as the member ID. Troubleshooting To troubleshoot the configuration of an expanded Virtual Chassis, perform these tasks: 726 Chapter 44: Virtual Chassis—Configuration Examples Troubleshooting Mastership Priority Problem You want to designate a different member as the master. Solution Change the mastership priority value or values of the switches, designating the highest mastership priority value for the switch that you want to be master. 1. Lower the mastership priority of the existing master (member 0). [edit virtual-chassis] user@SWA-0# set member 0 mastership-priority 1 2. Set the mastership priority of the member that you want to be the master to the highest possible value (255): [edit virtual-chassis] user@SWA-2# set member 2 mastership-priority 255 Troubleshooting Nonoperational VCPs Problem The VCP interface shows a status of down. Solution Check the cable to make sure that it is properly and securely connected to the VCPs. Related Documentation • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration You can configure a multimember Virtual Chassis access switch in a single wiring closet without setting any parameters—by simply cabling the switches together, using the dedicated Virtual Chassis ports (VCPs). You do not need to modify the default configuration to enable these ports. They are operational by default. The Virtual Chassis configuration automatically assigns the master, backup, and linecard roles, based on the sequence in which the switches are powered on and other factors in the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. TIP: We recommend that you explicitly configure the mastership priority of the switches to ensure that the switches continue to perform the desired roles when additional switches are added or other changes occur. However, it is possible to use the default configuration described in this example. 727 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to configure a multimember Virtual Chassis in a single wiring closet, using the default role assignments: • Requirements on page 728 • Overview and Topology on page 728 • Configuration on page 729 • Verification on page 730 • Troubleshooting on page 732 Requirements This example uses the following hardware and software components: • Two J-EX4200-48T switches • Four J-EX4200-24T switches Overview and Topology A Virtual Chassis configuration is easily expandable. This example shows a Virtual Chassis configuration composed of six J-EX4200 switches. It provides networking access for 180 onsite workers, who are sitting within range of a single wiring closet. The six combined switches are identified by a single host name and managed through a global management IP address. To set up a multimember Virtual Chassis configuration within a single wiring closet, you need to run the EZ Setup program only once. Connect to the master and run EZ Setup to specify its identification, time zone, and network properties. When additional switches are connected through the Virtual Chassis ports (VCPs), they automatically receive the same properties that were specified for the master. The topology for this example (see Figure 16 on page 729) consists of six switches: • Two J-EX4200-48T switches (SWA-0 and SWA-1) with 48 access ports, 8 of which support Power over Ethernet (PoE) • Four J-EX4200-24T switches (SWA-2, SWA-3, SWA-4, and SWA-5) with 24 access ports, 8 of which support PoE Figure 16 on page 729 shows that all the member switches are interconnected with the dedicated VCPs on the rear panel. The LCD on the front displays the member ID and role. 728 Chapter 44: Virtual Chassis—Configuration Examples Figure 16: Default Configuration of Multimember Virtual Chassis in a Single Wiring Closet Configuration Configure a multimember Virtual Chassis access switch in a single wiring closet using the factory defaults: CLI Quick Configuration By default, after you interconnect the switches with the dedicated VCPs and power on the switches, the VCPs are operational. The mastership priorities and member IDs are assigned by the software. To determine which switch has been selected as the master, check the LCD on the front panel. It should be the first switch that you power on. The backup should be the second switch that you power on. The other switches are all linecards. Wait at least one minute after powering on the master, before continuing to power on the other switches. Step-by-Step Procedure To configure a multimember Virtual Chassis with default role assignments: 1. Make sure the dedicated VCPs on the rear panel are properly cabled. See Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches for additional information. 2. Power on the switch that you want to function as the master (SWA-0). This examples uses one of the larger switches (J-EX4200-48T) as the master. 3. Check the front panel LCD to confirm that the switch has powered on correctly and that a member ID has been assigned. 4. Run the EZ Setup program on SWA-0, the master, specifying the identification parameters. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. 729 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 5. Configure SWA-0 with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis configuration, if desired. [edit] user@SWA-0# set interfaces vme unit 0 family inet address /ip-address/mask/ 6. After a lapse of at least one minute, power on SWA-1. This example uses the second J-EX4200-48T switch as the backup. 7. Check the front panel LCD to confirm that the switch has powered on correctly and that a member ID has been assigned. 8. Power on SWA-2, and check the front panels to make sure that the switch is operating correctly. 9. Continue to power on the member switches one by one, checking the front panels as you proceed. Verification To confirm that the configuration is working properly, perform these tasks: • Verifying the Member IDs and Roles of the Member Switches on page 730 • Verifying That the VCPs Are Operational on page 731 Verifying the Member IDs and Roles of the Member Switches Purpose Action Verify that all the interconnected member switches are included within the Virtual Chassis configuration and that their roles are assigned appropriately. Display the members of the Virtual Chassis configuration: user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0000.e255.00e0 730 Mastership Priority Role Neighbor List ID Interface Member ID Status Serial No Model 0 (FPC 0) Prsnt abc123 ex4200-48t 128 Master* 1 vcp-0 5 vcp-1 1 (FPC 1) Prsnt def123 ex4200-48p 128 Backup 2 vcp-0 0 vcp-1 2 (FPC 2) Prsnt abd231 ex4200-24t 128 Linecard 3 vcp-0 1 vcp-1 3 (FPC 3) Prsnt cab123 ex4200-24t 128 Linecard 4 vcp-0 2 vcp-1 4 (FPC 4) Prsnt fed456 ex4200-24t 128 Linecard 5 vcp-0 3 vcp-1 5 (FPC 5) Prsnt jkl231 ex4200-24t 128 Linecard 0 vcp-0 4 vcp-1 Chapter 44: Virtual Chassis—Configuration Examples Meaning The show virtual-chassis status command lists the member switches of the Virtual Chassis configuration with the member IDs and mastership priority values. It also displays the neighbor members with which each member is interconnected. The fpc number is the same as the member ID. Verifying That the VCPs Are Operational Purpose Action Verify that the dedicated VCPs interconnecting the member switches are operational. Display the Virtual Chassis interfaces. user@SWA-0> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc1: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc2: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc3: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc4: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc5: Interface or PIC / Port Type Status 731 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vcp-0 vcp-1 Meaning Dedicated Dedicated Up Up The show virtual-chassis vc-port all-members command lists the Virtual Chassis interfaces that are enabled for the member switches of the Virtual Chassis configuration and shows the status of the interfaces. In this case, no VCP uplinks have been configured. However, the VCP interfaces are automatically configured and enabled when you interconnect member switches using the dedicated VCPs. There are two dedicated VCPs on the rear panel of each J-EX4200 switch. The dedicated VCP interfaces are identified simply as vcp-0 and vcp-1. They do not use the standard interface address (in which the member ID is represented by the first digit). The output in this example shows that all interfaces are operational. The fpc number is the same as the member ID. Troubleshooting To troubleshoot the configuration of a multimember Virtual Chassis in a single wiring closet, perform these tasks: Troubleshooting Mastership Priority Problem You want to explicitly designate one member as the master and another as backup. Solution Change the mastership priority value of the member that you want to function as master, designating the highest mastership priority value that member. NOTE: These configuration changes are made through the current master, SWA-0. 1. Configure mastership priority of member 0 to be the highest possible value. [edit virtual-chassis] user@SWA-0# set member 0 mastership-priority 255 2. Set the mastership priority of another member that you want to function as the backup member as the same value: [edit virtual-chassis] user@SWA-0# set member 2 mastership-priority 255 Troubleshooting Nonoperational VCPs Problem The VCP interface shows a status of down. Solution Check the cable to make sure that it is properly and securely connected to the VCPs. Related Documentation 732 • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 Chapter 44: Virtual Chassis—Configuration Examples • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets A Virtual Chassis configuration is a very adaptable access switch solution. You can install member switches in different wiring closets, interconnecting the member switches by cabling and configuring uplink module ports and SFP network ports on J-EX4200-24F switches as Virtual Chassis ports (VCPs). This example shows how to use uplink VCPs to connect Virtual Chassis members that are located too far apart to be connected using the dedicated VCPs. Uplink VCPs can also be used to connect Virtual Chassis members to form link aggregation groups (LAGs). For the latter usage, see “Example: Configuring Link Aggregation Groups Using Uplink Virtual Chassis Ports” on page 769. NOTE: You can also configure the SFP networks ports on J-EX4200-24F switches as VCPs to connect Virtual Chassis member switches across wiring closets and to form LAGs. This example describes how to configure a Virtual Chassis access switch interconnected across wiring closets: • Requirements on page 733 • Overview and Topology on page 734 • Configuration on page 736 • Verification on page 738 • Troubleshooting on page 740 Requirements This example uses the following hardware and software components: • Four J-EX4200 switches • Four uplink modules 733 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Before you interconnect the members of the Virtual Chassis configuration across wiring closets, be sure you have: 1. Installed an uplink module in each member switch. See Installing an Uplink Module in a J-EX4200 Switch. 2. Powered on, connected, and run the EZSetup program on SWA-0 (see Table 104 on page 735 for switch names used in this example). See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. 3. Configured SWA-0 with the virtual management Ethernet (VME) interface for remote, out-of-band management of the Virtual Chassis configuration, if desired. See “Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure)” on page 797. 4. Interconnected SWA-0 and SWA-1 using the dedicated VCPs on the rear panel. SWA-1 must not be powered on at this time. 5. Interconnected SWA-2 and SWA-3 using the dedicated VCPs on the rear panel. SWA-2 and SWA-3 must not be powered on at this time. Overview and Topology In this example, four J-EX4200 switches will be interconnected in a Virtual Chassis configuration. Two of these (SWA-0 and SWA-1) are located in wiring closet A and the two other (SWA-2 and SWA-3) are located in wiring closet B. For ease of monitoring and manageability, we want to interconnect all four switches as members of a Virtual Chassis configuration. Prior to configuring the Virtual Chassis, we installed uplink modules in each of the member switches. In this example, uplink modules are installed in all four members so that there are redundant VCP connections across the wiring closets. If you want to expand this configuration to include more members within these wiring closets, you do not need to add any more uplink modules. Simply use the dedicated VCPs on the rear panel. The redundancy of uplink VCPs provided in this example is sufficient. We have interconnected the switches in wiring closet A and also interconnected the ones in wiring closet B using the dedicated VCPs. The interfaces for the dedicated VCPs are operational by default. They do not need to be configured. However, the Virtual Chassis cables that interconnect the dedicated VCPs of member switches within a single wiring closet are not long enough to connect member switches across wiring closets. Instead, we will use the fiber-optic cable connections in the uplink modules to interconnect the member switches in wiring closet A to the member switches in wiring closet B. You only need to interconnect one member switch in wiring closet A to one in wiring closet B to form the Virtual Chassis configuration. However, for redundancy, this example connects uplink module ports from the two member switches in wiring closet A to the two member switches in wiring closet B. We will specify the highest mastership priority value (255) for SWA-0 to make it the master before we power on SWA-1. Because SWA-0 and SWA-1 are interconnected with 734 Chapter 44: Virtual Chassis—Configuration Examples the dedicated VCPs, the master detects that SWA-1 is a member of its Virtual Chassis configuration and assigns it a member ID. We configure SWA-2 in wiring closet B without running EZSetup by directly connecting to the console port. If you wish, you can run EZSetup and specify identification parameters. Later, when you interconnect SWA-2 with SWA-0, the master of the Virtual Chassis configuration, the master overwrites any conflicting parameters. We will use SWA-2 as the backup of the Virtual Chassis configuration. If a problem occurs in wiring closet A, SWA-2 would take control of the Virtual Chassis configuration and maintain the network connections. We will configure the same mastership priority value for SWA-2 (255) that we configured for the master. Because we power on SWA-0 before we power on SWA-2, SWA-0 has additional prioritization properties that allow it to retain mastership of the Virtual Chassis configuration. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. We recommend setting identical mastership priority values for the master and backup members for high availability and smooth transition of mastership in case the original master becomes unavailable. (Setting identical mastership priority values for the master and backup members prevents the previous master from pre-empting the master role from the new master when the previous master comes back online.) After we have configured SWA-2 and set one of its uplink module ports as an uplink VCP, we will interconnect its uplink VCP with an uplink VCP on SWA-0. Finally, we will power on SWA-3. Because SWA-3 is interconnected with SWA-2 using the dedicated VCPs on the rear panel, the master will detect that SWA-3 is part of the expanded Virtual Chassis configuration and assign it member ID 3. For redundancy, we will configure an uplink VCP on SWA-3 through the master and interconnect that uplink VCP with an uplink VCP on SWA-1. Table 104 on page 735 shows the Virtual Chassis configuration settings for a Virtual Chassis composed of member switches in different wiring closets. Table 104: Components of a Virtual Chassis Interconnected Across Multiple Wiring Closets Switch Member ID Role and Priority Location SWA-0 0 master; mastership priority 255 Wiring closet A SWA-1 1 linecard; mastership priority 128 Wiring closet A SWA-2 2 backup; mastership priority 255 Wiring closet B SWA-3 3 linecard; mastership priority 128 Wiring closet B Figure 17 on page 736 shows the different types of interconnections used for this Virtual Chassis configuration. The rear view shows the member switches within each wiring 735 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS closet interconnected to each other using the dedicated VCPs. The front view shows the uplink VCPs interconnected across the wiring closets. Figure 17: Virtual Chassis Interconnected Across Wiring Closets Configuration To configure the Virtual Chassis across multiple wiring closets, perform these tasks: Step-by-Step Procedure To configure a Virtual Chassis across multiple wiring closets: 1. Configure the mastership priority of SWA-0 (member 0) to be the highest possible value (255), thereby ensuring that it functions as the master of the expanded Virtual Chassis configuration: [edit virtual-chassis] user@SWA-0# set member 0 mastership-priority 255 2. Prepare the members in wiring closet A for interconnecting with the member switches in wiring closet B by setting uplink VCPs for member 0 and member 1: user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 member 1 NOTE: • For redundancy, this example configures an uplink VCP in both SWA-0 and SWA-1. • 3. 736 This example omits the specification of the member member-id option in configuring an uplink VCP for SWA-0 (and, later, for SWA-2). The command applies by default to the switch where it is executed. Prepare SWA-2 in wiring closet B for interconnecting with the Virtual Chassis configuration by configuring its mastership priority to be the highest possible value (255). Its member ID is currently 0, because it is not yet interconnected with the Chapter 44: Virtual Chassis—Configuration Examples other members of the Virtual Chassis configuration. It is operating as a standalone switch. Its member ID will change when it is interconnected. [edit virtual-chassis] user@SWA-2# set member 0 mastership-priority 255 NOTE: SWA-2 is configured with the same mastership priority value that we configured for SWA-0. However, the longer uptime of SWA-0 ensures that, once the interconnection is made, SWA-0 functions as the master and SWA-2 functions as the backup. 4. Specify one uplink module port in SWA-2 as an uplink VCP. Its member ID is 0, because it is not yet interconnected with the other members of the Virtual Chassis configuration. NOTE: The setting of the uplink VCP remains intact when SWA-2 reboots and joins the Virtual Chassis configuration as member 2. user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 0 5. Physically interconnect SWA-0 and SWA-2 across wiring closets using their uplink VCPs. Although SWA-0 and SWA-2 have the same mastership priority value (255), SWA-0 was powered on first and thus has longer uptime. This results in SWA-0 retaining mastership while SWA-2 reboots and joins the now expanded Virtual Chassis configuration as the backup, with member ID 2. 6. Power on SWA-3. It joins the expanded Virtual Chassis configuration as member 3. NOTE: Member ID 3 is assigned to SWA-3 is 3, because SWA-3 was powered on after members 0, 1, and 2. 7. Because SWA-3 is now interconnected as a member of the Virtual Chassis configuration, you can specify a redundant uplink VCP on SWA-3 through the master of the Virtual Chassis configuration: user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 member 3 8. Physically interconnect SWA-3 and SWA-1 across wiring closets using their uplink VCPs. Both SWA-1 and SWA-3 have the default mastership priority value (128) and function in a linecard role. NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis. Results Display the results of the configuration on SWA-0: 737 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit] user@SWA-0# show virtual-chassis member 0 { mastership-priority 255; } member 1 { mastership-priority 128; } member 2 { mastership-priority 255; } member 3 { mastership-priority 128; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying the Member IDs and Roles of the Member Switches on page 738 • Verifying that the Dedicated VCPs and Uplink VCPs Are Operational on page 739 Verifying the Member IDs and Roles of the Member Switches Purpose Action Verify that all the interconnected member switches are included within the Virtual Chassis configuration and that their roles are assigned appropriately. Display the members of the Virtual Chassis configuration: user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0000.e255.00e0 Mastership Priority Role Neighbor List ID Interface Member ID Status Serial No Model 0 (FPC 0) Prsnt abc123 ex4200-48t 255 Master* 1 vcp-0 2 vcp-1 2 vcp-255/1/0 1 (FPC 1) Prsnt def456 ex4200-24t 128 Linecard 0 vcp-0 0 vcp-1 3 vcp–255/1/0 2 (FPC 2) Prsnt ghi789 ex4200-48t 255 Backup 3 vcp-0 3 vcp-1 0 vcp-255/1/0 3 (FPC 3) Meaning 738 Prsnt jkl012 ex4200-24t 128 Linecard 2 vcp-0 2 vcp-1 3 vcp–255/1/0 The show virtual-chassis status command lists the member switches interconnected as a Virtual Chassis configuration with the member IDs that have been assigned by the Chapter 44: Virtual Chassis—Configuration Examples master, the mastership priority values, and the roles. It also displays the neighbor members with which each member is interconnected. Verifying that the Dedicated VCPs and Uplink VCPs Are Operational Purpose Action Verify that the dedicated VCPs interconnecting member switches in wiring closet A and the uplink VCPs interconnecting the member switches between wiring closets are operational. Display the Virtual Chassis interfaces: user@SWA-0> show virtual-chassis status all-members fpc0: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 vcp-1 Dedicated 2 Up 32000 1 vcp-0 1/0 Auto-Configured —1 Up 1000 2 vcp-255/1/0 fpc1: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 0 vcp-0 vcp-1 Dedicated 2 Up 32000 0 vcp-1 1/0 Auto-Configured —1 Up 1000 3 vcp-255/1/0 fpc2: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 3 vcp-0 vcp-1 Dedicated 2 Up 32000 1/0 Auto-Configured —1 Up 1000 0 vcp-255/1/0 fpc3: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 2 vcp-0 vcp-1 Dedicated 2 Up 32000 2 vcp-1 1/0 Auto-Configured —1 Up 1000 1 vcp-255/1/0 Meaning The dedicated VCPs are displayed as vcp-0 and vcp-1. The interface on the switch that has been set as an uplink VCP is displayed as 1/0. The member interface names of uplink VCPs are of the form vcp-255/pic/port—for example, vcp-255/1/0. In that name, vcp-255 indicates that the interface is an uplink VCP, 1 is the uplink PIC number, and 0 is the uplink port number. The fpc number is the same as the member ID. The Trunk ID is a positive 739 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS number ID assigned to the LAG formed by the Virtual Chassis. If no LAG is formed, the value is –1. Troubleshooting To troubleshoot a Virtual Chassis configuration that is interconnected across wiring closets, perform these tasks: Troubleshooting Nonoperational VCPs Problem A uplink VCP shows a status of down. Solution • Check the cable to make sure that it is properly and securely connected to the ports. • If the VCP is an uplink module port, make sure that it has been explicitly set as an uplink VCP. • If the VCP is an uplink module port, make sure that you have specified the options (pic-slot, port, and member) correctly. • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 Related Documentation Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch J-EX Series switches allow you to combine multiple Ethernet links into one logical interface for higher bandwidth and redundancy. The ports that are combined in this manner are referred to as a link aggregation group (LAG) or bundle. The number of Ethernet links you can combine into a LAG depends on your J-EX Series switch model. See “Understanding Aggregated Ethernet Interfaces and LACP” on page 867 for more information. This example describes how to configure uplink LAGs to connect a Virtual Chassis access switch to a Virtual Chassis distribution switch: 740 • Requirements on page 741 • Overview and Topology on page 741 • Configuration on page 743 • Verification on page 745 • Troubleshooting on page 746 Chapter 44: Virtual Chassis—Configuration Examples Requirements This example uses the following software and hardware components: • Two J-EX4200-48T switches • Two J-EX4200-24F switches • Four uplink modules Before you configure the LAGs, be sure you have: • Configured the Virtual Chassis switches. See “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717. • Configured the uplink ports on the switches as trunk ports. See “Configuring Gigabit Ethernet Interfaces (CLI Procedure)” on page 919. Overview and Topology For maximum speed and resiliency, you can combine uplinks between an access switch and a distribution switch into LAGs. Using LAGs can be particularly effective when connecting a multimember Virtual Chassis access switch to a multimember Virtual Chassis distribution switch. The Virtual Chassis access switch in this example is composed of two member switches. Each member switch has an uplink module with two 10-Gigabit Ethernet ports. These ports are configured as trunk ports, connecting the access switch with the distribution switch. Configuring the uplinks as LAGs has the following advantages: • Link Aggregation Control Protocol (LACP) can optionally be configured for link negotiation. • It doubles the speed of each uplink from 10 Gbps to 20 Gbps. • If one physical port is lost for any reason (a cable is unplugged or a switch port fails, or one member switch is unavailable), the logical port transparently continues to function over the remaining physical port. The topology used in this example consists of one Virtual Chassis access switch and one Virtual Chassis distribution switch. The access switch is composed of two J-EX4200-48T switches (SWA-0 and SWA-1), interconnected to each other with their Virtual Chassis ports (VCPs) as member switches of Host-A. The distribution switch is composed of two J-EX4200-24F switches (SWD-0 and SWD-1), interconnected with their VCPs as member switches of Host-D. Each member of the access switch has an uplink module installed. Each uplink module has two ports. The uplinks are configured to act as trunk ports, connecting the access switch with the distribution switch. One uplink port from SWA-0 and one uplink port from SWA-1 are combined as LAG ae0 to SWD-0. This link is used for one VLAN. The remaining uplink ports from SWA-0 and from SWA-1 are combined as a second LAG connection (ae1) to SWD-1. LAG ae1 is used for another VLAN. 741 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: If the remote end of the LAG link is a security device, LACP might not be supported because security devices require a deterministic configuration. In this case, do not configure LACP. All links in the LAG are permanently operational unless the switch detects a link failure within the Ethernet physical layer or data link layers. Figure 18: Topology for LAGs Connecting a Virtual Chassis Access Switch to a Virtual Chassis Distribution Switch Table 105 on page 743 details the topology used in this configuration example. 742 Chapter 44: Virtual Chassis—Configuration Examples Table 105: Components of the Topology for Connecting Virtual Chassis Access Switches to a Virtual Chassis Distribution Switch Switch SWA-0 Hostname and VCID Base Hardware Uplink Module Member ID Trunk Port Host-A Access switch J-EX4200-48T switch One uplink module 0 ge-0/1/0 to SWD-0 ge-0/1/1 to SWD-1 VCID 1 SWA-1 Host-A Access switch J-EX4200-48T switch One uplink module 1 ge-1/1/0 to SWD-0 ge-1/1/1 to SWD-1 VCID 1 SWD-0 Host-D Distribution switch J-EX4200 L-24F switch One uplink module 0 ge-0/1/0 to SWA-0 ge-0/1/1 to SWA-1 VCID 4 SWD-1 Host-D Distribution switch J-EX4200 L-24F switch One uplink module 1 ge-1/1/0 to SWA-0 xge-1/1/1 to SWA-1 VCID 4 Configuration To configure two uplink LAGs from the Virtual Chassis access switch to the Virtual Chassis distribution switch: CLI Quick Configuration To quickly configure aggregated Ethernet high-speed uplinks between a Virtual Chassis access switch and a Virtual Chassis distribution switch, copy the following commands and paste them into the switch terminal window: [edit] set chassis aggregated-devices ethernet device-count 2 set interfaces ae0 aggregated-ether-options minimum-links 2 set interfaces ae0 aggregated-ether-options link-speed 10g set interfaces ae1 aggregated-ether-options minimum-links 2 set interfaces ae1 aggregated-ether-options link-speed 10g set interfaces ae0 unit 0 family inet address 192.0.2.0/25 set interfaces ae1 unit 1 family inet address 192.0.2.128/25 set interfaces ge-0/1/0 ether-options 802.ad ae0 set interfaces ge-1/1/0 ether-options 802.ad ae0 set interfaces ge-0/1/1 ether-options 802.ad ae1 set interfaces ge-1/1/1 ether-options 802.ad ae1 Step-by-Step Procedure To configure aggregated Ethernet high-speed uplinks between a Virtual Chassis access switch and a Virtual Chassis distribution switch: 1. Specify the number of LAGs to be created on the chassis: [edit chassis] user@Host-A# set aggregated-devices ethernet device-count 2 2. Specify the number of links that need to be present for the ae0 LAG interface to be up: 743 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit interfaces] user@Host-A# set ae0 aggregated-ether-options minimum-links 2 3. Specify the number of links that need to be present for the ae1 LAG interface to be up: [edit interfaces] user@Host-A# set ae1 aggregated-ether-options minimum-links 2 4. Specify the media speed of the ae0 link: [edit interfaces] user@Host-A# set ae0 aggregated-ether-options link-speed 10g 5. Specify the media speed of the ae1 link: [edit interfaces] user@Host-A# set ae1 aggregated-ether-options link-speed 10g 6. Specify the interface ID of the uplinks to be included in LAG ae0: [edit interfaces] user@Host-A# set ge-0/1/0 ether-options 802.ad ae0 user@Host-A# set ge-1/1/0 ether-options 802.ad ae0 7. Specify the interface ID of the uplinks to be included in LAG ae1: [edit interfaces] user@Host-A# set ge-0/1/1 ether-options 802.ad ae1 user@Host-A# set ge1/1/1 ether-options 802.ad ae1 8. Specify that LAG ae0 belongs to the subnet for the employee broadcast domain: [edit interfaces] user@Host-A# set ae0 unit 0 family inet address 192.0.2.0/25 9. Specify that LAG ae1 belongs to the subnet for the guest broadcast domain: [edit interfaces] user@Host-A# set ae1 unit 1 family inet address 192.0.2.128/25 Results Display the results of the configuration: [edit] chassis { aggregated-devices { ethernet { device-count 2; } } } interfaces { ae0 { aggregated-ether-options { link-speed 10g; minimum-links 2; } unit 0 { family inet { address 192.0.2.0/25; 744 Chapter 44: Virtual Chassis—Configuration Examples } } } ae1 { aggregated-ether-options { link-speed 10g; minimum-links 2; } unit 0 { family inet { address 192.0.2.128/25; } } ge–0/1/0 { ether-options { 802.ad ae0; } } ge–1/1/0 { ether-options { 802.ad ae0; } } ge–0/1/1 { ether-options { 802.ad ae1; } } gxe–1/1/1 { ether-options { 802.ad ae1; } } } Verification To verify that switching is operational and two LAGs have been created, perform these tasks: • Verifying That LAG ae0 Has Been Created on page 745 • Verifying That LAG ae1 Has Been Created on page 746 Verifying That LAG ae0 Has Been Created Purpose Action Verify that LAG ae0 has been created on the switch. show interfaces ae0 terse Interface ae0 ae0.0 Admin up up Link Proto up up inet Local Remote 10.10.10.2/24 745 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning The output confirms that the ae0 link is up and shows the family and IP address assigned to this link. Verifying That LAG ae1 Has Been Created Purpose Action Verify that LAG ae1 has been created on the switch show interfaces ae1 terse Interface ae1 ae1.0 Meaning Admin Link Proto up down up down inet Local Remote The output shows that the ae1 link is down. Troubleshooting Troubleshooting a LAG That Is Down Problem The show interfaces terse command shows that the LAG is down: Solution Check the following: Related Documentation • Verify that there is no configuration mismatch. • Verify that all member ports are up. • Verify that a LAG is part of family ethernet switching (Layer 2 LAG) or family inet (Layer 3 LAG). • Verify that the LAG member is connected to the correct LAG at the other end. • Verify that the LAG members belong to the same switch (or the same Virtual Chassis). • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Example: Connecting an Access Switch to a Distribution Switch on page 1078. • Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches • Installing an Uplink Module in a J-EX4200 Switch Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch J-EX Series switches allow you to combine multiple Ethernet links into one logical interface for higher bandwidth and redundancy. The ports that are combined in this manner are referred to as a link aggregation group (LAG) or bundle. The number of Ethernet links you can combine into a LAG depends on your J-EX Series switch model. See “Understanding Aggregated Ethernet Interfaces and LACP” on page 867 for more 746 Chapter 44: Virtual Chassis—Configuration Examples information. J-EX Series switches allow you to further enhance these links by configuring Link Aggregation Control Protocol (LACP). This example describes how to overlay LACP on the LAG configurations that were created in “Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch” on page 740: • Requirements on page 747 • Overview and Topology on page 747 • Configuring LACP for the LAGs on the Virtual Chassis Access Switch on page 748 • Configuring LACP for the LAGs on the Virtual Chassis Distribution Switch on page 748 • Verification on page 749 • Troubleshooting on page 750 Requirements This example uses the following software and hardware components: • Two J-EX4200-48T switches • Two J-EX4200-24F switches • Four J-EX Series uplink modules Before you configure LACP, be sure you have: • Set up the Virtual Chassis switches. See “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717. • Configured the uplink ports on the switches as trunk ports. See “Configuring Gigabit Ethernet Interfaces (CLI Procedure)” on page 919. • Configured the LAGs. See “Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch” on page 740 Overview and Topology This example assumes that you are already familiar with the Example: Configuring Aggregated Ethernet High-Speed Uplinks between Virtual Chassis Access Switch and Virtual Chassis Distribution Switch. The topology in this example is exactly the same as the topology in that other example. This example shows how to use LACP to enhance the LAG functionality. LACP exchanges are made between actors (the transmitting link) and partners (the receiving link). The LACP mode can be either active or passive. NOTE: If the actor and partner are both in passive mode, they do not exchange LACP packets, which results in the aggregated Ethernet links not coming up. By default, LACP is in passive mode. To initiate transmission of LACP packets and responses to LACP packets, you must enable LACP in active mode. 747 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS By default, the actor and partner send LACP packets every second. You can configure the interval at which the interfaces send LACP packets by including the periodic statement at the [edit interfaces interface-name aggregated-ether-options lacp] hierarchy level. The interval can be fast (every second) or slow (every 30 seconds). Configuring LACP for the LAGs on the Virtual Chassis Access Switch To configure LACP for the access switch LAGs, perform these tasks: CLI Quick Configuration To quickly configure LACP for the access switch LAGs, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ae0 aggregated-ether-options lacp active periodic fast set interfaces ae1 aggregated-ether-options lacp active periodic fast Step-by-Step Procedure To configure LACP for Host-A LAGs ae0 and ae1: 1. Specify the aggregated Ethernet options for both bundles: [edit interfaces] user@Host-A#set ae0 aggregated-ether-options lacp active periodic fast user@Host-A#set ae1 aggregated-ether-options lacp active periodic fast Results Display the results of the configuration: [edit interfaces] user@Host-A# show ae0 { aggregated-ether-options { lacp { active; periodic fast; } } } ae1 { aggregated-ether-options { lacp { active; periodic fast; } } } Configuring LACP for the LAGs on the Virtual Chassis Distribution Switch To configure LACP for the two uplink LAGs from the Virtual Chassis access switch to the Virtual Chassis distribution switch, perform these tasks: CLI Quick Configuration To quickly configure LACP for the distribution switch LAGs, copy the following commands and paste them into the switch terminal window: [edit interfaces] set ae0 aggregated-ether-options lacp passive periodic fast set ae1 aggregated-ether-options lacp passive periodic fast 748 Chapter 44: Virtual Chassis—Configuration Examples Step-by-Step Procedure To configure LACP for Host D LAGs ae0 and ae1: 1. Specify the aggregated Ethernet options for both bundles: [edit interfaces] user@Host-D#set ae0 aggregated-ether-options lacp passive periodic fast user@Host-D#set ae1 aggregated-ether-options lacp passive periodic fast Results Display the results of the configuration: [edit interfaces] user@Host-D# show ae0 { aggregated-ether-options { lacp { passive; periodic fast; } } } ae1 { aggregated-ether-options { lacp { passive periodic fast; } } } Verification To verify that LACP packets are being exchanged, perform these tasks: • Verifying the LACP Settings on page 749 • Verifying That the LACP Packets Are Being Exchanged on page 750 Verifying the LACP Settings Purpose Action Verify that LACP has been set up correctly. Use the show lacp interfaces interface-name command to check that LACP has been enabled as active on one end. user@Host-A> show lacp interfaces xe-0/1/0 Aggregated interface: ae0 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity ge-0/1/0 Actor No Yes No No No Yes Fast Active ge-0/1/0 Partner No Yes No No No Yes Fast Passive LACP protocol: ge-0/1/0 Receive State Defaulted Transmit State Mux State Fast periodic Detached 749 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning The output indicates that LACP has been set up correctly and is active at one end. Verifying That the LACP Packets Are Being Exchanged Purpose Action Verify that LACP packets are being exchanged. Use the show interfaces aex statistics command to display LACP information. user@Host-A> show interfaces ae0 statistics Physical interface: ae0, Enabled, Physical link is Down Interface index: 153, SNMP ifIndex: 30 Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Minimum links needed: 1, Minimum bandwidth needed: 0 Device flags : Present Running Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Current address: 02:19:e2:50:45:e0, Hardware address: 02:19:e2:50:45:e0 Last flapped : Never Statistics last cleared: Never Input packets : 0 Output packets: 0 Input errors: 0, Output errors: 0 Logical interface ae0.0 (Index 71) (SNMP ifIndex 34) Flags: Hardware-Down Device-Down SNMP-Traps Encapsulation: ENET2 Statistics Packets pps Bytes bps Bundle: Input : 0 0 0 0 Output: 0 0 0 0 Protocol inet Flags: None Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255 Meaning The output here shows that the link is down and that no PDUs are being exchanged. Troubleshooting These are some tips for troubleshooting: Troubleshooting a Nonworking LACP Link 750 Problem The LACP link is not working. Solution Check the following: • Remove the LACP configuration and verify whether the static LAG is up. • Verify that LACP is configured at both ends. Chapter 44: Virtual Chassis—Configuration Examples Related Documentation • Verify that LACP is not passive at both ends. • Verify whether LACP protocol data units (PDUs) are being exchanged by running the monitor traffic-interface lag-member detail command. • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches • Installing an Uplink Module in a J-EX4200 Switch 751 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File You can deterministically control both the role and the member ID assigned to each member switch in a Virtual Chassis configuration by creating a preprovisioned configuration file. A preprovisioned configuration file links the serial number of each J-EX4200 switch in the configuration to a specified member ID and role. The serial number must be specified in the configuration file for the member to be recognized as part of the Virtual Chassis configuration. You must select two members that you want to make eligible for election as master of the Virtual Chassis configuration. When you list these two members in the preprovisioned configuration file, you designate both members as routing-engine. One will function as the master of the Virtual Chassis configuration and the other will function as the backup. You designate additional members, which are not eligible for election as master, has having the linecard role in the preprovisioned configuration file. NOTE: When you use a preprovisioned configuration, you cannot modify the mastership priority or member ID of member switches through the user interfaces. NOTE: After you have created a preprovisioned Virtual Chassis configuration, you can use the autoprovisioning feature to add member switches to that configuration. See “Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure)” on page 786. This example describes how to configure a Virtual Chassis across multiple wiring closets using a preprovisioned configuration file: • Requirements on page 752 • Overview and Topology on page 753 • Configuration on page 757 • Verification on page 760 • Troubleshooting on page 763 Requirements This example uses the following hardware and software components: 752 • Five J-EX4200-48T switches • Five J-EX4200-24T switches • Four uplink modules Chapter 44: Virtual Chassis—Configuration Examples Before you create the preprovisioned configuration of the Virtual Chassis and interconnect the members across the wiring closets, be sure you have: 1. Made a list of the serial numbers of all the switches to be connected as a Virtual Chassis configuration. 2. Noted the desired role (routing-engine or linecard) of each switch. If you configure the member with a routing-engine role, it is eligible to function as a master or backup. If you configure the member with a linecard role , it is not eligible to become a master or backup. 3. Installed an uplink module in each of the member switches that will be interconnected across wiring closets. See Installing an Uplink Module in a J-EX4200 Switch. 4. Interconnected the member switches within each wiring closet using the dedicated VCPs on the rear panel of switches. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch. 5. Powered on the switch that you plan to use as the master switch (SWA-0). 6. Run the EZSetup program on SWA-0, specifying the identification parameters. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 for details. SWA-0 is going to be configured in the example to function as the master of the Virtual Chassis configuration. Thus, the properties that you specify for SWA-0 will apply to the entire Virtual Chassis configuration, including all the member switches that you specify in the preprovisioned configuration file. 7. Configured SWA-0 with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis configuration, if desired. [edit] user@SWA-0# set interfaces vme unit 0 family inet address /ip-address/mask/ Overview and Topology In this example, five J-EX4200 switches (SWA-0 through SWA-4) are interconnected with their dedicated VCPs in wiring closet A and five J-EX4200 switches (SWA-5 through SWA-9) are interconnected with their dedicated VCPs in wiring closet B. SWA-0 (in wiring closet A) is going to be the master of the Virtual Chassis configuration. This example shows how to create a preprovisioned configuration file on SWA-0 for all member switches that will be interconnected in the Virtual Chassis configuration. The preprovisioned configuration file includes member IDs for the members in wiring closet A and for the members in wiring closet B. SWA-5 (in wiring closet B) is going to be the backup of the Virtual Chassis configuration. Both SWA-0 and SWA-5 are specified in the preprovisioned configuration file with the role of routing-engine. All other members are specified with the role of linecard. If all member switches could be interconnected with their dedicated VCPs, you could simply power on the switches after saving and committing the preprovisioned configuration file. The master detects the connection of the members through the 753 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dedicated VCPs and applies the parameters specified in the preprovisioned configuration file. However, the Virtual Chassis cables that interconnect the VCPs of member switches within a single wiring closet are not long enough to connect member switches across wiring closets. Instead, you can configure the uplink module ports and the SFP networks ports on J-EX4200-24F switches as VCPs to interconnect the member switches in wiring closet A to the member switch in wiring closet B. For redundancy, this example connects uplink VCPs from two member switches in wiring closet A (SWA–0 and SWA–2) to two member switches (SWA-5 and SWA-7) in wiring closet B. NOTE: You can use interfaces on SFP and SFP+ uplink modules and the SFP network ports on J-EX4200-24F switches as VCPs. When an uplink module port or SFP network port is set as a VCP, it cannot be used for any other purpose. The SFP uplink module has four 1-Gbps ports; the SFP+ uplink module has four 1-Gbps or two 10-Gbps ports. The uplink module ports that are not set as VCPs can be configured as trunk ports to connect to a distribution switch. Because this particular preprovisioned configuration is for a Virtual Chassis that is interconnected across wiring closets, we will bring up the Virtual Chassis configuration in stages. First, we power on SWA-0 (without powering on any other switches) and create the preprovisioned configuration file. Then we power on the remaining switches in wiring closet A. If we check the status of the Virtual Chassis configuration at this point by using the show virtual-chassis status command, it will display only member 0 through member 4. The members that have not yet been interconnected will not be listed. Next power on SWA-5 without powering on the remaining switches (SWA-6 through SWA-9) in wiring closet B. Bring up SWA-5 as a standalone switch and set one of its uplinks as a VCP prior to interconnecting it with the Virtual Chassis configuration in wiring closet A. Without this setting, SWA-5 cannot be detected as a member switch by the master of the Virtual Chassis configuration. You can set the uplink VCP of SWA–5 without running the EZSetup program by directly connecting to the console port. If you wish, you can run the EZSetup program and specify identification parameters. When you interconnect SWA-5 with the master of the Virtual Chassis configuration, the master overwrites any conflicting parameters. After setting the VCP in SWA-5, connect this VCP with the VCP of SWA-0 in wiring closet A. SWA-5 (serial number pqr678) is specified as a routing-engine in the preprovisioned configuration file. This example uses SWA-5 as the backup of the Virtual Chassis configuration. If a problem occurred in wiring closet A, SWA-5 would take control of the Virtual Chassis configuration and maintain the network connections. Specify both SWA-0 and SWA-5 as routing-engine. Because SWA-0 is powered on prior to SWA-5, it has additional prioritization properties that cause it to be elected as master of the Virtual Chassis configuration. 754 Chapter 44: Virtual Chassis—Configuration Examples After being physically interconnected with SWA-0, SWA-5 reboots and comes up as member 5 and as the backup of the Virtual Chassis configuration. Power on the remaining switches (SWA-6 through SWA-9) in wiring closet B. The master can now detect that all members are present. Finally, for redundancy, configure an additional VCP on SWA-7 through the master. The topology for this example consists of: • Three J-EX4200-48T switches (SWA-0 , SWA-2, and SWA-4) in wiring closet A. • Two J-EX4200-48T switches (SWA-5 and SWA-9) in wiring closet B. • Two J-EX4200-24T switches (SWA-1 and SWA-3) in wiring closet A. • Three J-EX4200-24T switches (SWA-6, SWA-7, and SWA-8) in wiring closet B. • Four uplink modules. Two are installed in wiring closet A and two are installed in wiring closet B. Table 106 on page 755 shows the Virtual Chassis configuration settings for a preprovisioned Virtual Chassis composed of member switches in different wiring closets. Table 106: Components of a Preprovisioned Virtual Chassis Interconnected Across Multiple Wiring Closets Switch Serial number Member ID Role Uplink Module Ports SWA-0 abc123 0 routing-engine ge-0/1/0 SWA-1 def456 1 linecard SWA-2 ghi789 2 linecard SWA-3 jkl012 3 SWA-4 mno345 SWA-5 pqr678 Hardware Location J-EX4200-48T and uplink module Wiring closet A J-EX4200-24T Wiring closet A J-EX4200-48T and uplink module Wiring closet A linecard J-EX4200-24T Wiring closet A 4 linecard J-EX4200-48T Wiring closet A 5 routing-engine J-EX4200-48T and uplink module Wiring closet B J-EX4200-24T Wiring closet B ge-2/1/0 ge-0/1/0 NOTE: The member ID of SWA-5 is 0 at the time that its uplink module port is configured as a VCP. SWA-6 stu901 6 linecard 755 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 106: Components of a Preprovisioned Virtual Chassis Interconnected Across Multiple Wiring Closets (continued) Switch Serial number Member ID Role Uplink Module Ports SWA-7 vwx234 7 linecard ge-7/1/0 SWA-8 yza567 8 SWA-9 bcd890 9 Hardware Location J-EX4200-24T and uplink module Wiring closet B linecard J-EX4200-24T Wiring closet B linecard J-EX4200-48T Wiring closet B Figure 19 on page 757 shows the different types of interconnections used for this Virtual Chassis configuration. The rear view shows that the member switches within each wiring closet are interconnected to each other using the dedicated VCPs. The front view shows that the uplink module ports that have been set as VCPs and interconnected across the wiring closets. The uplink module ports that are not set as VCPs can be configured as trunk ports to connect to a distribution switch. NOTE: The interconnections shown in Figure 19 on page 757 are the same as they would be for a configuration that was not preprovisioned across wiring closets. 756 Chapter 44: Virtual Chassis—Configuration Examples Figure 19: Maximum Size Virtual Chassis Interconnected Across Wiring Closets Configuration To configure the Virtual Chassis across multiple wiring closets using a preprovisioned configuration: NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis configuration. 757 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To create a preprovisioned configuration for the Virtual Chassis: 1. Specify the preprovisioned configuration mode: [edit virtual-chassis] user@SWA–0# set preprovisioned 2. Specify all the members that will be included in the Virtual Chassis configuration, listing each switch's serial number with the desired member ID and the desired role: [edit virtual-chassis] user@SWA–0# set member 0 serial-number abc123 role routing-engine user@SWA–0# set member 1 serial-number def456 role linecard user@SWA–0# set member 2 serial-number ghi789 role linecard user@SWA–0# set member 3 serial-number jkl012 role linecard user@SWA–0# set member 4 serial-number mno345 role linecard user@SWA–0# set member 5 serial-number pqr678 role routing-engine user@SWA–0# set member 6 serial-number stu901 role linecard user@SWA–0# set member 7 serial-number vwx234 role linecard user@SWA-0# set member 8 serial-number yza567 role linecard user@SWA–0# set member 9 serial-number bcd890 role linecard 3. Power on the member switches in wiring closet A. 4. Prepare the members in wiring closet A for interconnecting with the member switches in wiring closet B by setting uplink VCPs for member 0 and member 2: user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 0 member 2 NOTE: • For redundancy, this example sets an uplink VCP in both SWA-0 and SWA-2. • This example omits the specification of the member 0 in setting the uplink for SWA-0. The command applies by default to the switch where it is executed. 5. Power on SWA-5 and connect to it. This switch comes up as member ID 0 and functions as master of itself. Although SWA-5 is listed in the preprovisioned configuration file, it is not a present member of the Virtual Chassis configuration that has been powered on thus far. In order for the master to detect SWA-5 as a connected member, you must first set an uplink VCP on SWA-5 and interconnect that VCP with the uplink VCP of SWA-0. 6. Set the first uplink of SWA-5 to function as a VCP. Because SWA-5 has been powered on as a separate switch and is still operating independently at this point, its member ID is 0. user@SWA-5> request virtual-chassis vc-port set pic-slot 1 port 0 758 Chapter 44: Virtual Chassis—Configuration Examples NOTE: This example omits the specification of the member 0 in configuring the uplink for SWA-5 (at this point the member ID of SWA-5 is still 0). The command applies by default to the switch where it is executed. 7. Power off SWA-5 and connect the fiber cable from SWA-5 uplink VCP ge-0/1/0 to the uplink VCP ge-0/1/0 on SWA-0. 8. Power on SWA-5. 9. Now that SWA-5 has been brought up as member 5 of the Virtual Chassis configuration, power on the remaining switches (SWA-6 through SWA-9) in wiring closet B. They are interconnected with SWA-5 using the dedicated VCPs on the rear panel and are therefore detected by the master as interconnected members. If you check the status of the Virtual Chassis configuration at this point, all the members that were specified in the preprovisioned configuration file should be displayed as present. Additional configuration for member switches can now be done through the master switch. 10. Set one uplink module port of SWA-7 to function as a VCP: user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 member 7 Results Display the results of the configuration on SWA-0: [edit] user@SWA-0# show virtual-chassis { member 0 { role routing-engine; serial-number abc123; } member 1 { role linecard; serial-number def456; } member 2 { role linecard; serial-number ghi789; } member 3 { role linecard; serial-number jkl012; } member 4 { role linecard; serial-number mno345; } member 5 { role routing-engine; serial-number pqr678; } 759 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS member 6 { role linecard; serial-number stu901; } member 7 { role linecard; serial-number vwx234; } member 8 { role linecard; serial-number yza567; } member 9 { role linecard; serial-number bcd890; } preprovisioned; } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying the Member IDs and Roles of the Member Switches on page 760 • Verifying That the Dedicated VCPs and Uplink VCPs Are Operational on page 761 Verifying the Member IDs and Roles of the Member Switches Purpose Action Verify that the member IDs and roles are all set as expected. Display the members of the Virtual Chassis configuration: user@SWA-0> show virtual-chassis status Preprovisioned Virtual Chassis Virtual Chassis ID: 0000.e255.0000 760 Mastership Priority Role Member ID Status Serial No Model 0 (FPC 0) Prsnt abc123 ex4200-48t 129 1 (FPC 1) Prsnt def456 ex4200-24t 2 (FPC 2) Prsnt ghi789 3 (FPC 3) Prsnt 4 (FPC 4) 5 FPC 5) Neighbor List ID Interface Master* 1 4 5 vcp-0 vcp-1 1/0 0 Linecard 2 0 vcp-0 vcp—1 ex4200-48t 0 Linecard 3 1 7 vcp-0 vcp-1 1/0 jkl012 ex4200-24t 0 Linecard 4 2 vcp-0 vcp-1 Prsnt mno345 ex4200-48t 0 Linecard 0 3 vcp-0 vcp-1 Prsnt pqr678 ex4200-48t 129 Backup 6 9 vcp-0 vcp-1 Chapter 44: Virtual Chassis—Configuration Examples Meaning 0 1/0 6 (FPC 6) Prsnt stu901 ex4200-24t 0 Linecard 7 5 vcp-0 vcp-1 7 (FPC 7) Prsnt vwx234 ex4200-24t 0 Linecard 8 6 2 vcp-0 vcp-1 1/0 8 (FPC 8) Prsnt yza567 ex4200-24t 0 Linecard 9 7 vcp-0 vcp-1 9 (FPC 9) Prsnt bc7890 ex4200-48t 0 Linecard 5 8 vcp-0 vcp-1 The output shows that all members listed in the preprovisioned configuration file are connected to the Virtual Chassis configuration. It confirms that SWA-0 (member 0) is functioning as the master of the Virtual Chassis configuration, which was the intention of the configuration procedure. The other switch configured with the routing-engine role (SWA-5) is functioning as the backup. The Neighbor List displays the interconnections of the member VCPs. Verifying That the Dedicated VCPs and Uplink VCPs Are Operational Purpose Action Verify that the dedicated VCPs interconnecting the member switches within each wiring closet and the uplink module VCPs interconnecting the member switches across wiring closets are operational. Display the Virtual Chassis interfaces: user@SWA-0> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up fpc1: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc2: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up 761 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS fpc3: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc4: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc5: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up fpc6: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc7: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up fpc8: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc9: -------------------------------------------------------------------------Interface Type Status Speed Neighbor or (mbps) ID Interface PIC / Port vcp-0 Dedicated Up 762 Chapter 44: Virtual Chassis—Configuration Examples vcp-1 Meaning Dedicated Up The dedicated VCPs interconnecting the member switches within wiring closets are displayed as vcp-0 and vcp-1. The uplink module VCPs interconnecting member switches (members 0, 2, 5, and 7) across wiring closets are displayed as 1/0 and 1/1 and identified as Configured. Troubleshooting To troubleshoot a preprovisioned Virtual Chassis configuration that is interconnected across wiring closets, perform these tasks: Troubleshooting Nonoperational VCPs Problem A VCP shows a status of down. Solution Check the cable to make sure that it is properly and securely connected to the ports. Related Documentation • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Intermember Link Fails The Virtual Chassis fast failover feature is a hardware-assisted failover mechanism that automatically reroutes traffic and reduces traffic loss in the event of a link or switch failure. If a link between two members fails, traffic flow between those members must be rerouted quickly so that there is minimal traffic loss. Fast failover is enabled by default on all dedicated Virtual Chassis ports (VCPs). This example describes how to configure fast failover on uplink module VCPs in a Virtual Chassis configuration: • Requirements on page 764 • Overview and Topology on page 764 • Configuration on page 765 • Verification on page 766 763 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example uses the following hardware and software components: • Six J-EX4200-24T switches • Four SFP uplink modules Before you begin configuring fast failover, be sure you have: 1. Mounted the switches. See Mounting a J-EX4200 Switch on Two Posts in a Rack or Cabinet, Mounting a J-EX4200 Switch on a Desk or Other Level Surface, or Mounting a J-EX4200 Switch on a Wall. 2. Cabled the switches in a multiple-ring topology to create the Virtual Chassis configuration. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch and “Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets” on page 733. See Figure 20 on page 765 for an illustration of a multiple-ring topology. Overview and Topology In a Virtual Chassis configuration, fast failover automatically reroutes traffic and reduces traffic loss in the event of a link failure or a member switch failure. By default, fast failover is enabled on all dedicated Virtual Chassis ports (VCPs). If you configure uplink module ports as VCPs, you must manually configure fast failover on these ports. For fast failover to be effective, the Virtual Chassis members must be configured in a ring topology. The ring topology can be formed by using either dedicated Virtual Chassis ports (VCPs) or user-configured uplink module VCPs. Fast failover is supported only in a ring topology that uses identical port types, for example, either a topology that uses all dedicated VCPs or one that uses all uplink module VCPs. Fast failover is not supported in a ring topology that includes both dedicated VCPs and uplink module VCPs. Fast failover is supported, however, in a Virtual Chassis configuration that consists of multiple rings. Figure 20 on page 765 shows an example of a multiple-ring topology. 764 Chapter 44: Virtual Chassis—Configuration Examples Figure 20: Traffic Redirected by Fast Failover After VCP Link Failures in a Topology with Multiple Rings This example shows how to enable fast failover on uplink module VCPs. The topology for this example consists of six switches: • Six J-EX4200-24T switches, four of which have an SFP uplink module installed (switches 1, 3, 4, and 6) Configuration To configure the fast failover feature on uplink module VCPs: CLI Quick Configuration To configure fast failover on all SFP uplink module VCPs, copy the following command and paste it into the terminal window on switch 1: 765 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit] set virtual-chassis fast-failover ge Step-by-Step Procedure To configure fast failover on SFP uplink module VCPs: 1. Enable fast failover on all SFP uplink module VCPs in the Virtual Chassis configuration: [edit] user@switch1# set virtual-chassis fast-failover ge NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis. Results Check the results of the configuration: [edit virtual-chassis] user@switch1# show fast-failover { ge; } Verification To confirm that fast failover is enabled on SFP uplink module VCPs in the Virtual Chassis configuration, perform these tasks: • Verifying That Fast Failover Is Enabled on page 766 Verifying That Fast Failover Is Enabled Purpose Action Verify that fast failover has been enabled in a Virtual Chassis configuration. 1. Issue the show virtual-chassis fast-failover command. 2. Check to see that fast failover is enabled. user@switch1> show virtual-chassis fast-failover Fast failover on dedicated VCP ports: Enabled Fast failover on XE uplink VCP ports: Disabled Fast failover on GE uplink VCP ports: Enabled Meaning Related Documentation 766 Fast failover is enabled on all dedicated VCPs and SFP uplink module VCPs in the Virtual Chassis configuration. • Configuring Fast Failover in a Virtual Chassis Configuration on page 798 • Disabling Fast Failover in a Virtual Chassis Configuration on page 799 Chapter 44: Virtual Chassis—Configuration Examples • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge You can explicitly assign a Virtual Chassis ID so that, when two Virtual Chassis configurations merge, the ID that you assigned takes precedence over the automatically assigned Virtual Chassis IDs and becomes the ID of the newly merged Virtual Chassis configuration. This example describes how to assign the Virtual Chassis ID in a Virtual Chassis configuration: • Requirements on page 767 • Overview and Topology on page 767 • Configuration on page 768 • Verification on page 768 Requirements This example uses the following hardware and software components: • Two J-EX4200-48T switches • Two J-EX4200-24T switches Before you begin, be sure you have: Installed the switches. See Mounting a J-EX4200 Switch on Two Posts in a Rack or Cabinet, Mounting a J-EX4200 Switch on a Desk or Other Level Surface, or Mounting a J-EX4200 Switch on a Wall. 1. 2. Cabled the switches to create the Virtual Chassis configuration. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch. Overview and Topology Every Virtual Chassis configuration has a unique ID that is automatically assigned when the Virtual Chassis configuration is formed. You can also configure a Virtual Chassis ID using the set virtual-chassis id command. When two Virtual Chassis merge, the Virtual Chassis ID that you assigned takes precedence over the automatically assigned Virtual Chassis IDs and becomes the ID for the newly merged Virtual Chassis configuration. The topology for this example consists of four switches: • Two J-EX4200-24T switches • Two J-EX4200-48T switches 767 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS The switches are connected as a four-member Virtual Chassis configuration and are identified as switch-A, switch-B, switch-C, and switch-D. The master is switch-A. Configuration Assign the Virtual Chassis ID in a Virtual Chassis configuration: CLI Quick Configuration To assign a Virtual Chassis ID so that, when two Virtual Chassis configurations merge, the ID that you assigned takes precedence over the automatically assigned Virtual Chassis IDs and becomes the ID of the newly merged Virtual Chassis configuration, copy the following command and paste it into the terminal window: [edit] set virtual-chassis id 9622.6ac8.5345 Step-by-Step Procedure To assign the Virtual Chassis ID in a Virtual Chassis configuration: 1. Assign the Virtual Chassis ID: [edit] user@switch-A# set virtual-chassis id 9622.6ac8.5345 NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis configuration. Verification To verify that the Virtual Chassis ID has been assigned as you intended, perform these tasks: • Verifying That the Virtual Chassis ID Is Assigned on page 768 Verifying That the Virtual Chassis ID Is Assigned Purpose Action Verify that the Virtual Chassis ID has been assigned in a Virtual Chassis configuration. 1. Issue the show configuration virtual-chassis id command. 2. Check to see that the Virtual Chassis ID number is listed. user@switch-A> show configuration virtual-chassis id id 9622.6ac8.5345; Meaning Related Documentation 768 The Virtual Chassis ID has been assigned as 9622.6ac8.5345. • Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge (CLI Procedure) on page 800 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 Chapter 44: Virtual Chassis—Configuration Examples Example: Configuring Link Aggregation Groups Using Uplink Virtual Chassis Ports You can form link aggregation groups (LAGs) between Virtual Chassis member switches in different wiring closets using uplink Virtual Chassis ports (VCPs) and, on J-EX4200-24F switches, network VCPs. LAGs balance traffic across the member links, increase the uplink bandwidth, and provide increased availability. To form LAGs using uplink or network VCPs, you configure the uplink module interfaces or network interfaces on the member switches as VCPs and connect the VCPs using fiber-optic cables. For the LAGs to form, the uplink or network VCPs on each member switch that will form a LAG must operate at the same link speed and you must interconnect at least two uplink or network VCPs on each of those members. You can connect uplink or network VCPs operating at different link speeds, but they will not form a LAG. NOTE: The LAGs formed by VCPs are different from LAGs formed by Virtual Chassis network interfaces. For more information on LAGs formed by network interfaces, see “Understanding Virtual Chassis Configurations and Link Aggregation” on page 702. This example shows how to configure uplink module interfaces and network interfaces as VCPs on multiple member switches of a Virtual Chassis configuration and then connect them to form LAGs: • Requirements on page 769 • Overview and Topology on page 770 • Configuration on page 771 • Verification on page 774 • Troubleshooting on page 777 Requirements This example uses the following hardware and software components: • Five J-EX4200 switches, one of which is a J-EX4200-24F model • Four uplink modules 769 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Before you configure the uplink module interfaces and network interfaces on Virtual Chassis member switches as VCPs and interconnect the members to form a LAG, be sure you have: 1. Installed the uplink modules in the SWA-0, SWA-1, SWA-2, and SWA-3 switches. See Installing an Uplink Module in a J-EX4200 Switch. 2. Powered on SWA-0, connected it to the network, and run the EZSetup program. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. 3. Configured SWA-0 with the virtual management Ethernet (VME) interface for remote, out-of-band management of the Virtual Chassis configuration, if desired. See “Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure)” on page 797. 4. Ensured that SWA-1 is not powered on and then interconnected SWA-0 and SWA-1 using the dedicated VCPs on the rear panel. NOTE: The interfaces for the dedicated VCPs are operational by default. They do not need to be configured. 5. Ensured that SWA-2, SWA-3, and SWA-4 are not powered on. They are not connected in any way, so when initially powered up they will be standalone switches. Overview and Topology In this example, five J-EX4200 switches will be interconnected to form LAGs for ease of monitoring and manageability. Two of these switches (SWA-0 and SWA-1) are located in wiring closet A and the three others (SWA-2, SWA-3, and SWA-4) are located in wiring closet B. SWA-0 will form one LAG with SWA-2 and another LAG with SWA-4, and SWA-1 will form a LAG with SWA-3. We will use fiber-optic cables connected to the uplink and network VCPs to interconnect the member switches in wiring closet A to the member switches in wiring closet B. We will specify the highest mastership priority value (255) for SWA-0 to make it the master before we power on SWA-1. Because SWA-0 and SWA-1 are interconnected with the dedicated VCPs, the master detects that SWA-1 is a member of its Virtual Chassis configuration and assigns it a member ID. We will use SWA-2 as the backup of the Virtual Chassis configuration. We will configure the same mastership priority value for SWA-2 (255) that we configured for the master. Because we power on SWA-0 before we power on SWA-2, SWA-0 retains mastership of the Virtual Chassis configuration. NOTE: We recommend setting identical mastership priority values for the master and backup members for high availability and smooth transition of mastership in case the original master becomes unavailable. 770 Chapter 44: Virtual Chassis—Configuration Examples We will configure the uplink module interfaces on three of the switches as uplink VCPs. On the J-EX4200-24F switch we will configure two of the network interfaces as VCPs. We will interconnect two of the uplink VCPs on SWA-0 with two of the uplink VCPs on SWA-2. Similarly, we will interconnect the two uplink VCPs on SWA-1 with the two uplink VCPs on SWA-3. Finally, we will connect the two remaining uplink VCPs on SWA-0 with two network VCPs on SWA-4. As a result, three LAGs will be automatically formed. Figure 21 on page 771 shows the interconnections used to form LAGs using uplink VCPs and the network VCPs after the procedure below has been completed. Figure 21: Virtual Chassis Interconnected Across Wiring Closets to Form LAGs Configuration To configure the Virtual Chassis uplink module interfaces and network interfaces as uplink VCPs and interconnect them between two wiring closets to form LAGs, perform these tasks: 771 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure a Virtual Chassis across multiple wiring closets and interconnect them to form LAGs: 1. Configure the mastership priority of SWA-0 (member 0) to be the highest possible value (255), thereby ensuring that it functions as the master of the expanded Virtual Chassis configuration: [edit virtual-chassis] user@SWA-0# set member 0 mastership-priority 255 2. Power on SWA-1. 3. Prepare the members in wiring closet A for interconnecting with the member switches in wiring closet B by setting all the uplink module interfaces on SWA-0 and two of the uplink module interfaces on SWA-1 as uplink VCPs: user@SWA-0> user@SWA-0> user@SWA-0> user@SWA-0> user@SWA-0> user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 request virtual-chassis vc-port set pic-slot 1 port 1 request virtual-chassis vc-port set pic-slot 1 port 2 request virtual-chassis vc-port set pic-slot 1 port 3 request virtual-chassis vc-port set pic-slot 1 port 0 member 1 request virtual-chassis vc-port set pic-slot 1 port 1 member 1 NOTE: This example omits the specification of the member member-id option in configuring the uplink VCPs for SWA-0 (and, later, for SWA-2). The command applies by default to the switch where it is executed. 4. Power on SWA-2. 5. If SWA-2 was previously configured, revert to the factory default configuration. 6. Prepare SWA-2 in wiring closet B by configuring its mastership priority to be the highest possible value (255). Its member ID is currently 0, because it is not yet interconnected with the other members of the Virtual Chassis configuration. It is operating as a standalone switch. Its member ID will change when it is interconnected. [edit virtual-chassis] user@SWA-2# set member 0 mastership-priority 255 NOTE: SWA-2 is configured with the same mastership priority value that we configured for SWA-0. However, the longer uptime of SWA-0 ensures that, once the interconnection is made, SWA-0 functions as the master and SWA-2 functions as the backup. 7. 772 Specify two of the SFP uplink module interfaces in SWA-2 as uplink VCPs. The member IDs are 0, because they are not yet interconnected with the other members of the Virtual Chassis configuration: Chapter 44: Virtual Chassis—Configuration Examples NOTE: The setting of the uplink VCPs remain intact when SWA-2 reboots and joins the Virtual Chassis configuration as member 2. user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 0 user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 1 8. Power down SWA-2. 9. Physically interconnect SWA-0 and SWA-2 across wiring closets using two of the uplink VCPs on each switch. 10. Power on SWA-2. SWA-2 joins the Virtual Chassis configuration and a LAG is automatically formed between SWA-0 and SWA-2. In addition, although SWA-0 and SWA-2 have the same mastership priority value (255), SWA-0 was powered on first and thus has longer uptime. This results in SWA-0 retaining mastership while SWA-2 reboots and joins the now expanded Virtual Chassis configuration as the backup, with member ID 2. 11. Power on SWA-3. 12. If SWA-3 was previously configured, revert to the factory default configuration. 13. Specify both uplink module interfaces in SWA-3 as uplink VCPs: user@SWA-3> request virtual-chassis vc-port set pic-slot 1 port 0 user@SWA-3> request virtual-chassis vc-port set pic-slot 1 port 1 14. Power down SWA-3. 15. Physically interconnect SWA-3 with SWA-2 using their dedicated VCPs. 16. Physically interconnect SWA-1 and SWA-3 across wiring closets using their uplink VCPs. 17. Power on SWA-3. It joins the Virtual Chassis configuration as member 3. NOTE: Member ID 3 is assigned to SWA-3 because SWA-3 was powered on after members 0, 1, and 2. A LAG is automatically formed between SWA-1 and SWA-3. In addition, both SWA-1 and SWA-3 have the default mastership priority value (128) and function in a linecard role. 18. Power on SWA-4. 19. If SWA-4 was previously configured, revert to the factory default configuration. 20. Configure two of the network interfaces on SWA-4 as uplink VCPs: user@SWA-4> request virtual-chassis vc-port set pic-slot 0 port 20 user@SWA-4> request virtual-chassis vc-port set pic-slot 0 port 21 21. Power down SWA-4. 773 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Results 22. Physically interconnect SWA-4 and SWA-0 across wiring closets using the network VCPs on SWA-4 and the two remaining SFP uplink VCPs on SWA-0. 23. Power on SWA-4. A LAG is automatically formed between SWA-4 and SWA-0. In addition, SWA-4 joins the Virtual Chassis configuration in the linecard role. Display the results of the configuration on SWA-0: user@SWA-0> show configuration virtual-chassis member 0 { mastership-priority 255; } member 1 { mastership-priority 128; } member 2 { mastership-priority 255; } member 3 { mastership-priority 128; } member 4 { mastership-priority 128; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying the Member IDs and Roles of the Member Switches on page 774 • Verifying That the VCPs Are Operational on page 775 Verifying the Member IDs and Roles of the Member Switches Purpose Action Verify that all the interconnected member switches are included within the Virtual Chassis configuration and that their roles are assigned appropriately. Display the members of the Virtual Chassis configuration: user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0000.e255.00e0 774 Mastership Priority Role Neighbor List ID Interface Member ID Status Serial No Model 0 (FPC 0) Prsnt abc123 ex4200-48t 255 Master* 1 1 2 2 4 4 1 (FPC 1) Prsnt def456 ex4200-24t 128 Linecard 0 vcp-0 0 vcp-1 vcp-0 vcp-1 vcp-255/1/0 vcp-255/1/1 vcp-255/0/20 vcp-255/0/21 Chapter 44: Virtual Chassis—Configuration Examples 3 vcp–255/1/0 3 vcp–255/1/1 Meaning 2 (FPC 2) Prsnt ghi789 ex4200-48t 255 Backup 3 3 0 0 vcp-0 vcp-1 vcp-255/1/0 vcp-255/1/1 3 (FPC 3) Prsnt jkl012 ex4200-24t 128 Linecard 2 2 1 1 vcp-0 vcp-1 vcp–255/1/0 vcp–255/1/1 4 (FPC 4) Prsnt mno345 ex4200-24f 128 Linecard 0 vcp-255/1/2 0 vcp-255/1/3 The show virtual-chassis status command lists the member switches interconnected in a Virtual Chassis configuration with the member IDs that have been assigned by the master, the mastership priority values, and the roles. It also displays the neighbor members with which each member is interconnected by the dedicated VCPs, by uplink VCPs, and by network VCPs. Verifying That the VCPs Are Operational Purpose Action Verify that the dedicated VCPs interconnecting member switches in wiring closets A and B and the uplink and network VCPs interconnecting the member switches between wiring closets are operational. Display the Virtual Chassis interfaces: user@SWA-0> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 1 vcp-0 vcp-1 Dedicated 2 Up 32000 1 vcp-1 1/0 Configured 3 Up 1000 2 vcp-255/1/0 1/1 Configured 3 Up 1000 2 vcp-255/1/1 1/2 Configured 4 Up 1000 4 vcp-255/0/20 1/3 Configured 4 Up 1000 4 vcp-255/0/21 fpc1: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 0 vcp-0 vcp-1 Dedicated 2 Up 32000 0 vcp-1 1/0 Configured 3 Up 10000 3 vcp-255/1/0 1/1 Configured 3 Up 10000 3 vcp-255/1/1 fpc2: -------------------------------------------------------------------------- 775 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Interface or PIC / Port vcp-0 vcp-1 1/0 1/1 1/2 1/3 Type Dedicated Dedicated Configured Configured Trunk ID 1 2 3 3 —1 —1 Status Speed (mbps) Neighbor ID Interface Up Up Up Up Down Down 32000 32000 1000 1000 1000 1000 3 3 0 0 vcp-0 vcp-1 vcp-255/1/0 vcp-255/1/1 fpc3: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 2 vcp-0 vcp-1 Dedicated 2 Up 32000 2 vcp-1 1/0 Configured 3 Up 10000 1 vcp-255/1/0 1/1 Configured 3 Up 10000 1 vcp-255/1/1 fpc4: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Down 32000 vcp-1 Dedicated 2 Down 32000 0/20 Configured 3 Up 1000 0 vcp-255/1/2 0/21 Configured 3 Up 1000 0 vcp-255/1/3 Meaning The dedicated VCPs are displayed as vcp-0 and vcp-1. The uplink module interfaces that have been set as uplink VCPs are displayed as 1/0, 1/1, 1/2, and 1/3. The network interfaces that have been set as VCPs are displayed as 0/20 and 0/21. The neighbor interface names of uplink and network VCPs are of the form vcp-255/pic/port—for example, vcp-255/1/0. In that name, vcp-255 indicates that the interface is a VCP, 1 is the uplink PIC number, and 0 is the port number. The fpc number is the same as the member ID. The trunk ID is a positive number ID assigned to the LAG formed by the Virtual Chassis. If no LAG is formed, the value is –1. NOTE: Each switch assigns the trunk IDs to its local interfaces. As a result, the pair of interfaces that form one end of a LAG on one switch will have the same trunk ID, and the pair of interfaces that form the other end of the LAG will have the same trunk ID, but the trunk IDs on either end of the LAG might be different. For example, in Figure 21 on page 771, the uplink VCPs 1/2 and 1/3 on SWA-0 form a LAG with the network VCPs 0/20 and 0/21 on SWA-4. Uplink VCPs 1/2 and 1/3 on SWA-0 both have trunk ID 4, while network VCPs 0/20 and 0/21 on SWA-4 both have trunk ID 3. The trunk IDs are different between the switches because SWA-0 assigns the trunk IDs for its local uplink VCPs and SWA-4 assigns the trunk IDs for its local VCPs. 776 Chapter 44: Virtual Chassis—Configuration Examples Troubleshooting To troubleshoot a Virtual Chassis configuration that is interconnected across wiring closets, perform this task: Troubleshooting Nonoperational VCPs Problem An uplink VCP shows a status of down. Solution • Check the cable to make sure that it is properly and securely connected to the interfaces. • If the VCP is an uplink module interface, make sure that it has been explicitly set as an uplink VCP. • If the VCP is an uplink module interface, make sure that you have specified the options (pic-slot, port, and member) correctly. • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Reverting to the Default Factory Configuration for the J-EX Series Switch on page 341 Related Documentation Example: Configuring Automatic Software Update on Virtual Chassis Member Switches The automatic software update feature automatically updates the Junos OS version on prospective member switches as they are added to a Virtual Chassis configuration of J-EX4200 Ethernet Switches so the new member switch immediately joins the Virtual Chassis configuration and is put in the active state. If the software version on the new switch is not the same as the version running on the master, the master keeps the new switch in the inactive state. If you have not enabled the automatic software update feature, you will have to manually install the correct software version on each prospective member switch as it is added to the Virtual Chassis configuration. This example describes how to configure the Virtual Chassis automatic software update feature: • Requirements on page 778 • Overview and Topology on page 778 • Configuration on page 778 • Verification on page 779 777 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example uses the following hardware and software components: • Three J-EX4200 switches Before you begin, be sure you have: Ensured that two member switches are running the same version of the Junos OS for J-EX Series switches so that they can form the initial Virtual Chassis configuration. 1. 2. Cabled and powered on those two switches to create the Virtual Chassis configuration. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch. 3. Ensured that you know the name or the URL of the software package to be used by the automatic software update feature. Overview and Topology For a standalone J-EX4200 switch to join an existing Virtual Chassis configuration, it must be running the same version of the Junos OS that is running on the Virtual Chassis master. If the software version on the new switch is not the same as the version running on the master, the master keeps the new switch in the inactive state. The topology for this example consists of three J-EX Series switches. Two of the switches are connected in a Virtual Chassis configuration and are therefore running the same version of the Junos OS for J-EX Series switches. The third switch is a standalone switch that is running a different software version than the Virtual Chassis member switches. In this example, we will enable the automatic software update feature on the Virtual Chassis configuration and then add the third switch to the configuration. The master will detect the presence of the new switch, check the software version running on the new switch, and, because it is not the same version currently running on the master, will update the software version on the new switch and reboot the switch so that it can join the Virtual Chassis configuration and immediately be put in the active state. Configuration To configure automatic software update, perform this task: Step-by-Step Procedure To configure automatic software update: 1. Enable automatic software update and configure the path to the software package: [edit] user@switch# set virtual-chassis auto-sw-update package-name /var/tmp/jinstall-ex-4200-10.2R1.1-domestic-signed.tgz 2. Results Connect and power on the new switch to be added to the existing Virtual Chassis configuration. Check the results of the configuration: [edit virtual-chassis] 778 Chapter 44: Virtual Chassis—Configuration Examples user@switch# show auto-sw-update { package-name /var/tmp/jinstall-ex-4200-10.2R1.1-domestic-signed.tgz; } Verification To verify that the software version on the new switch has been updated and that the switch has joined the Virtual Chassis configuration, perform this task: • Verifying That the Software Version Is Updated on page 779 Verifying That the Software Version Is Updated Purpose Verify that the new switch has joined the Virtual Chassis configuration. NOTE: If the software version on the new switch had not been updated successfully, the master would not allow the switch to join the Virtual Chassis configuration. Action 1. Issue the show virtual-chassis status command. 2. Check to see that the new member switch has been added. user@switch> show virtual-chassis status Virtual Chassis ID: 0019.e250.47a0 Meaning Related Documentation Member ID 0 (FPC 0) Status Prsnt Mastership Serial No Model priority AK0207360276 ex4200-24t 255 Role Master* 1 (FPC 1) Prsnt AK0207360281 ex4200-24t 255 Backup 2 (FPC 2) Prsnt AJ0207391130 ex4200-48t 128 Linecard Neighbor List ID Interface 1 vcp-1 2 vcp-0 2 vcp-1 0 vcp-0 0 vcp-1 1 vcp-0 Because in the initial two-member Virtual Chassis configuration member 0 was the master and member 1 was the backup, the output shows that the new switch has been assigned member ID 2 and has been given the Linecard role. The Status field shows that member 2 is Prsnt, which means that it is in the active state. • Configuring Automatic Software Update on Virtual Chassis Member Switches (CLI Procedure) on page 800 • Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) on page 786 779 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 780 CHAPTER 45 Configuring Virtual Chassis • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) on page 786 • Configuring Mastership of the Virtual Chassis (CLI Procedure) on page 790 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Setting an Uplink Module Port or a J-EX4200-24F Network Port as a Virtual Chassis Port Using the LCD Panel on page 795 • Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) on page 797 • Configuring the Timer for the Backup Member to Start Using Its Own MAC Address, as Master of Virtual Chassis (CLI Procedure) on page 797 • Configuring Fast Failover in a Virtual Chassis Configuration on page 798 • Disabling Fast Failover in a Virtual Chassis Configuration on page 799 • Disabling Split and Merge in a Virtual Chassis Configuration (CLI Procedure) on page 799 • Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge (CLI Procedure) on page 800 • Configuring Automatic Software Update on Virtual Chassis Member Switches (CLI Procedure) on page 800 • Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure) on page 801 Configuring a Virtual Chassis (CLI Procedure) To take advantage of the scalability features of J-EX4200 switches, you can configure a Virtual Chassis that includes up to 10 member switches. You can interconnect the member switches using the dedicated Virtual Chassis ports (VCPs) on the back of the switch. You do not have to configure the interface for the dedicated VCPs. If you want to interconnect member switches that are located in different racks or wiring closets, interconnect them using uplinks configured as VCP interfaces. See “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792. 781 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: A multimember Virtual Chassis configuration has two Routing Engines, one in the master and the other in the backup. Therefore, we recommend that you always use commit synchronize rather than simply commit to save configuration changes made for a Virtual Chassis. This ensures that the configuration changes are saved in both Routing Engines. A Virtual Chassis can be configured with either: • preprovisioned configuration—Allows you to deterministically control the member ID and role assigned to a member switch by tying it to its serial number. • nonprovisioned configuration—The master sequentially assigns a member ID to other member switches. The role is determined by the mastership priority value and other factors in the master election algorithm. • Configuring a Virtual Chassis with a Preprovisioned Configuration File on page 782 • Configuring a Virtual Chassis with a Nonprovisioned Configuration File on page 783 Configuring a Virtual Chassis with a Preprovisioned Configuration File To configure a Virtual Chassis using a preprovisioned configuration: 1. Make a list of the serial numbers of all the switches to be connected in a Virtual Chassis configuration. 2. Note the desired role (routing-engine or linecard) of each switch. If you configure the member with a routing-engine role, it is eligible to function as a master or backup. If you configure the member with a linecard role, it is not eligible to become a master or backup. 3. Interconnect the member switches using the dedicated VCPs on the rear panel of switches. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch. NOTE: Arrange the switches in sequence, either from top to bottom or from bottom to top (0–9). 4. Power on only the switch that you plan to use as the master switch (SWA-0). Do not power on the other switches at this time. 5. Run the EZ Setup program on SWA-0, specifying the identification parameters. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 for details. NOTE: The properties that you specify for SWA-0 apply to the entire Virtual Chassis configuration, including all the member listed in the preprovisioned configuration file. 782 Chapter 45: Configuring Virtual Chassis 6. Configure SWA-0 with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis configuration, if desired. [edit] user@SWA-0# set interfaces vme unit 0 family inet address /ip-address/mask/ 7. Specify the preprovisioned configuration mode: [edit virtual-chassis] user@SWA–0# set preprovisioned 8. Specify all the members that you want to included in the Virtual Chassis configuration, listing each switch’s serial number with the desired member ID and the desired role: [edit virtual-chassis] user@SWA–0# set member 0 serial-number abc123 role routing-engine user@SWA–0# set member 1 serial-number def456 role linecard user@SWA–0# set member 2 serial-number ghi789 role linecard user@SWA–0# set member 3 serial-number jkl012 role linecard user@SWA–0# set member 4 serial-number mno345 role linecard user@SWA–0# set member 5 serial-number pqr678 role routing-engine user@SWA–0# set member 6 serial-number stu901 role linecard user@SWA–0# set member 7 serial-number vwx234 role linecard user@SWA-0# set member 8 serial-number yza567 role linecard user@SWA–0# set member 9 serial-number bcd890 role linecard 9. Power on the member switches. NOTE: You cannot modify the mastership-priority when you are using a preprovisioned configuration. The mastership priority values are generated automatically and controlled by the role that is assigned to the member switch in the configuration file. The two routing engines are assigned the same mastership priority value. However, the member that was powered on first has higher prioritization according to the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. Configuring a Virtual Chassis with a Nonprovisioned Configuration File To configure the Virtual Chassis using a nonprovisioned configuration: 1. Interconnect the member switches using the dedicated VCPs on the rear panel of switches. See Connecting a Virtual Chassis Cable to a J-EX4200 Switch. NOTE: Arrange the switches in sequence, either from top to bottom or from bottom to top (0–9). 2. Power on only the switch that you plan to use as the master switch (SWA-0). Do not power on the other switches at this time. 3. Run the EZ Setup program on SWA-0, specifying the identification parameters. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 for details. 783 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: The properties that you specify for SWA-0 apply to the entire Virtual Chassis configuration, including all the members interconnected through VCPs.. 4. Configure SWA-0 with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis configuration, if desired. [edit] user@SWA-0# set interfaces vme unit 0 family inet address /ip-address/mask/ 5. Configure mastership priority for the master, backup, and other members, if desired: [edit virtual-chassis] user@SWA–0# set member 0 mastership-priority 255 user@SWA–0# set member 5 mastership-priority 255 6. Power on the member switches in sequential order, one by one. NOTE: If you do not edit the Virtual Chassis configuration file, a nonprovisioned configuration is generated by default. The mastership priority value for each member switch is 128. The master role is selected by default. You can change the role that is performed by the members by modifying the mastership-priority. See “Configuring Mastership of the Virtual Chassis (CLI Procedure)” on page 790. We recommend that you specify the same mastership priority value for the desired master and backup members. We have assigned the highest possible mastership priority to two members. However, the member that was powered on first has higher prioritization according to the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. We have allowed the other members to use the default mastership priority, which qualifies them to function in the role of linecard. NOTE: If you want to change the member ID that the master has assigned to a member switch, use the request virtual-chassis renumber command. Related Documentation • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Configuring Mastership of the Virtual Chassis (CLI Procedure) on page 790 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 Configuring a Virtual Chassis (J-Web Procedure) To take advantage of the scalability features of J-EX4200 switches, you can configure a Virtual Chassis that includes up to 10 member switches. You can interconnect the 784 Chapter 45: Configuring Virtual Chassis member switches using the dedicated Virtual Chassis ports (VCPs) on the back of the switch. You do not have to configure the interface for the dedicated VCPs. If you want to interconnect member switches that are located in different racks or wiring closets, interconnect them using uplinks configured as VCP interfaces. See “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792. To configure a Virtual Chassis for J-EX Series switches using the J-Web interface: 1. Select Configure > Virtual Chassis. 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 334 for details about all commit options. 2. The properties you can configure are displayed. The first section of the Virtual Chassis Configuration page displays the Virtual Chassis member configuration. the display includes a list of member switches, their member IDs, and the mastership priority. The second section displays the operational status of the Virtual Chassis configuration, member details, and the dedicated and configured Virtual Chassis ports (VCPs). 3. Enter information into the page as described in Table 107 on page 785. 4. Click one: • Add—To add a member's configuration to the Virtual Chassis configuration, click Add. • Edit—To modify an existing member's configuration, click Edit. • Delete—To delete the configuration of a member, click Delete. 5. To configure an uplink as a VCP, select the member in the Virtual Chassis members list and select Action > Select Uplink Port as VCP. Select the port from the list. 6. To delete an uplink VCP from a member, select the member in the Virtual Chassis members list and select Action > Delete Uplink Port as VCP. Table 107: Virtual Chassis Configuration Fields Field Function Your Action Member ID Specifies the identifier for the member switch. The master switch assigns member IDs. Select an identifier from the list. Select an ID from 0 through 9. Priority Specifies the mastership priority to be assigned to the member. Select a number from 1 through 255, with 255 being the highest priority (128 is the default). Member Details 785 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 107: Virtual Chassis Configuration Fields (continued) Field Function Your Action Disable Management VLAN If you want to reserve an individual member's management Ethernet port for local troubleshooting, you can remove that port from being part of the Virtual Management Ethernet (VME). Click to disable management VLAN on the port. Refresh Refreshes the operational status of Virtual Chassis members. Click to refresh the operational status. Related Documentation • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches • Virtual Chassis Overview on page 691 Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) You can add one or more J-EX4200 switches to an existing Virtual Chassis configuration. Up to ten J-EX4200 switches can be included within a Virtual Chassis configuration. You can add the new switches to either type—nonprovisioned or preprovisioned—of Virtual Chassis configuration. See “Configuring a Virtual Chassis (CLI Procedure)” on page 781 for descriptions of these types. To add a switch to an existing Virtual Chassis configuration, use the procedure that matches what you need to accomplish: • Adding a New Switch to an Existing Virtual Chassis Configuration Within the Same Wiring Closet on page 786 • Adding a New Switch from a Different Wiring Closet to an Existing Virtual Chassis Configuration on page 787 • Adding a New Switch to an Existing Preprovisioned Virtual Chassis Configuration Using Autoprovisioning on page 789 Adding a New Switch to an Existing Virtual Chassis Configuration Within the Same Wiring Closet Before you begin, be sure you have: 786 • Mounted the new switch in a rack. • Confirmed that the new switch is powered off. Chapter 45: Configuring Virtual Chassis • If you are expanding a preprovisioned configuration, made a note of the serial number (on the back of the switch). You will need to edit the Virtual Chassis configuration to include the serial number of the new member switch. • If you are expanding a preprovisioned configuration, edited the existing Virtual Chassis configuration to include the serial number of the new member switch. You can specify the role of the new member switch when you add its serial number in the Virtual Chassis configuration file. The parameters specified in the master Virtual Chassis configuration file are applied after the new member switch has been interconnected to an existing member switch. NOTE: After you have created a preprovisioned Virtual Chassis configuration, you can use the autoprovisioning feature to add member switches to that configuration. To add a new member switch to an existing Virtual Chassis configuration within the same wiring closet: 1. If the new member switch has been previously configured, revert that switch’s configuration to the factory defaults. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. 2. Interconnect the unpowered new switch to at least one member of the existing Virtual Chassis configuration using the dedicated Virtual Chassis ports (VCPs). 3. Power on the new switch. 4. Confirm that the new member switch is now included within the Virtual Chassis configuration by checking the front-panel display for the member ID. It should display a member ID that is higher than 0 (1 through 9), because there is already at least one member of the Virtual Chassis configuration. NOTE: If you are using a preprovisioned configuration, the member ID is automatically assigned to the member’s serial number in the configuration file. Adding a New Switch from a Different Wiring Closet to an Existing Virtual Chassis Configuration To add a new switch from a different wiring closet to an existing Virtual Chassis configuration, you must use a long cable to connect the new member switch across wiring closets. You can use a port on an SFP or SFP+ uplink module, or an SFP network port on a J-EX4200-24F switch, and a fiber-optic cable for this purpose. Before you begin, be sure you have: • Installed the uplink modules needed for the Virtual Chassis configuration. • Mounted the new switch in a rack. 787 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • If the new member switch has been previously configured, reverted its configuration to the factory defaults. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. • Powered on the new member switch as a standalone switch and configured its uplink module ports as VCPs. Otherwise, it cannot be recognized as a member switch by the master. • If you are expanding a preprovisioned configuration, made a note of the serial number (on the back of the switch). You will need to edit the Virtual Chassis configuration to include the serial number of the new member switch. • If you are expanding a preprovisioned configuration, edited the existing Virtual Chassis configuration to include the serial number of the new member switch. You can specify the role of the new member switch when you add its serial number in the Virtual Chassis configuration file. The parameters specified in the master Virtual Chassis configuration file are applied after the new member switch has been interconnected with its uplink VCP to an existing member switch. • Confirmed that the new, currently standalone switch is powered off. • Prepared an existing member switch for interconnecting with the new switch through an uplink module port by configuring an uplink module port as a VCP on the existing member switch. NOTE: After you have created a preprovisioned Virtual Chassis configuration, you can use the autoprovisioning feature to add member switches to that configuration. To add a new member switch that is going to be interconnected with the existing Virtual Chassis configuration across wiring closets: 1. Power on the new switch. 2. Connect a laptop or terminal to the console port of the switch, or use EZSetup on the standalone switch to specify temporary identification parameters. (When you interconnect the new member switch with the existing Virtual Chassis configuration, the master will overwrite and disable any specified parameters that conflict with the Virtual Chassis parameters or assigned member configuration.) 3. Use the CLI or the J-Web interface to set the uplink module ports as VCPs. NOTE: If you are using a nonprovisioned configuration, you might configure the new member switch with a mastership priority value that is less than that of the existing member switches. Doing so ensures that the new member switch will function in a linecard role when it is included within the Virtual Chassis configuration. 4. Power off the new switch. 788 Chapter 45: Configuring Virtual Chassis 5. Interconnect the new member switch to at least one member of the existing Virtual Chassis configuration using the uplink module ports on each of the switches that have been configured as VCPs. 6. Power on the new member switch. 7. Confirm that the new member switch is now included within the Virtual Chassis configuration by checking the front-panel display for the member ID. It should display a member ID that is higher than 0 (1 through 9), because there is already at least one member of the Virtual Chassis configuration. NOTE: If you are using a preprovisioned configuration, the member ID is automatically assigned to the member's serial number in the configuration file. Adding a New Switch to an Existing Preprovisioned Virtual Chassis Configuration Using Autoprovisioning Before you begin, be sure you have: • Installed the uplink modules needed for the Virtual Chassis configuration. • Mounted the new switch in a rack. • Ensured that the preprovisioned Virtual Chassis configuration has an active master. For more information, see “Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File” on page 752. • On the master, configured the Link Level Discovery Protocol (LLDP) on the uplink module ports that will be used as VCPs. LLDP is configured by default but might have been disabled. To configure LLDP, see “Configuring LLDP (CLI Procedure)” on page 2344 or “Configuring LLDP (J-Web Procedure)” on page 2345. • Ensured that the new member switch has the factory-default configuration. If the new member switch has been previously configured, revert its configuration to the factory defaults. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. • Made a note of the serial number (on the back of the switch). You will need to edit the Virtual Chassis configuration to include the serial number of the new member switch. • Edited the existing Virtual Chassis preprovisioned configuration to include the serial number of the new member switch. You can specify the role of the new member switch when you add its serial number to the Virtual Chassis configuration file. The parameters specified in the master Virtual Chassis configuration file are applied to the new member switch after it has been interconnected through its uplink VCP to an existing member switch. • Prepared an existing member switch to interconnect with the new switch through an uplink module port by configuring an uplink module port as a VCP on the existing member switch. 789 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Ensured that the operational modes of the uplink modules on the existing member switch and the new member switch match. • Confirmed that the new member switch is powered off. • Interconnected the existing switch with the new switch using the appropriate cable. If these conditions are not met, autoprovisioning will not work and you will need to manually configure uplink module ports on the switch to be added to the configuration to be VCPs. For more information, see “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792. To add a switch to an existing preprovisioned Virtual Chassis configuration using the autoprovisioning feature: 1. Power on the new member switch. 2. Confirm that the new member switch is now included in the Virtual Chassis configuration by checking the front-panel display for the member ID. It should display a member ID in the range from 0 through 9 because there was already at least one member of the Virtual Chassis configuration. The member ID is automatically assigned to the new member switch's serial number in the configuration file. Related Documentation • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Example: Configuring Automatic Software Update on Virtual Chassis Member Switches on page 777 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 • Reverting to the Default Factory Configuration for the J-EX Series Switch on page 341 Configuring Mastership of the Virtual Chassis (CLI Procedure) You can designate the role (master, backup, or linecard) that a member switch performs within a Virtual Chassis configuration whether or not you are using a preprovisioned configuration. 790 Chapter 45: Configuring Virtual Chassis NOTE: A multimember Virtual Chassis configuration has two Routing Engines, one in the master and the other in the backup. Therefore, we recommend that you always use commit synchronize rather than simply commit to save configuration changes made for a Virtual Chassis. This ensures that the configuration changes are saved in both Routing Engines. This topic describes: • Configuring Mastership Using a Preprovisioned Configuration File on page 791 • Configuring Mastership Using a Configuration File That Is Not Preprovisioned on page 792 Configuring Mastership Using a Preprovisioned Configuration File To configure mastership using a preprovisioned configuration: 1. Note the serial numbers of the switches that you want to function in the master role and backup role. 2. Power on only the switch (SWA-0) that you want to function in the master role. 3. Edit the configuration to specify the preprovisioned configuration mode: [edit virtual-chassis] user@SWA-0# set preprovisioned 4. List the serial numbers of the member switches that you want to function as master and backup, specifying their role as routing-engine: [edit] user@SWA-0# set virtual-chassis member 0 serial-number abc123 role routing-engine user@SWA-0# set virtual-chassis member 2 serial-number def456 role routing-engine NOTE: You cannot directly modify the mastership priority value when you are using a preprovisioned configuration. The mastership priority values are generated automatically and controlled by the role that is assigned to the member switch in the configuration file. The two members assigned the routing-engine role are assigned the same mastership priority value (128). However, the member that was powered on first has higher prioritization according to the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. Only two members can be specified with the routing-engine role. 5. List the serial numbers of any other member switches that you want to include in the Virtual Chassis configuration. You may also specify their role as linecard, if desired. 791 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Mastership Using a Configuration File That Is Not Preprovisioned To configure mastership of the Virtual Chassis through a configuration that is not preprovisioned: 1. Power on only the switch that you want to function in the master role (SWA-0). 2. Configure the highest possible mastership priority value (255) for the member that you want to function in the master role: [edit virtual-chassis] user@SWA-0# set member 0 mastership-priority 255 3. Configure the same mastership priority value (continue to edit the Virtual Chassis configuration on the master) for the member that you want to be the backup (SWA-1): [edit virtual-chassis] user@SWA-0# set member 1 mastership-priority 255 NOTE: We recommend that the master and backup have the same mastership priority value to prevent the master and backup status from switching back and forth between master and backup members in failover conditions. 4. Use the default mastership priority value (128) for the remaining member switches or configure the mastership priority to a value that is lower than the value specified for members functioning in the master and backup roles. Related Documentation • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual Chassis Member on page 807 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Virtual Chassis Configuration on page 704 Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) You can interconnect J-EX4200 switches that are beyond the reach of the Virtual Chassis cables as members of a Virtual Chassis configuration by installing the optional SFP or SFP+ uplink module and connecting the uplink ports. You can also use the SFP network ports on a J-EX4200-24F for this purpose. To use the uplink ports or SFP network ports for interconnecting member switches, you must explicitly set the uplink ports as VCPs. 792 Chapter 45: Configuring Virtual Chassis NOTE: When an uplink port is set as a VCP interface, it cannot be used for any other purpose. You can set one port as a VCP interface and configure the other port in trunk mode as an uplink to a distribution switch. Before you set an uplink port as a VCP: 1. Install the uplink module in the member switches that you want to interconnect. 2. Power on and connect to the switch that you plan to designate as the master of the Virtual Chassis configuration. NOTE: Do not power on the other switches at this point. 3. Run EZSetup on the switch that you are configuring to be the master. Follow the prompts to specify the hostname and other identification, time zone, and network properties. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. The properties that you specify for the master apply to the entire Virtual Chassis configuration, including all the member switches that you later interconnect with the master. 4. If you want to configure and manage the Virtual Chassis configuration remotely, specify the VME global management interface. You can configure the VME global management interface when you are setting up the master or you can do it after completing the other configuration steps for the Virtual Chassis. See “Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure)” on page 797. 5. Configure mastership of the Virtual Chassis using either the nonprovisioned or preprovisioned configuration. See “Configuring Mastership of the Virtual Chassis (CLI Procedure)” on page 790 for details. NOTE: A multimember Virtual Chassis configuration has two Routing Engines, one in the master and the other in the backup. Therefore, we recommend that you always use commit synchronize rather than simply commit to save configuration changes made for a Virtual Chassis configuration. This ensures that the configuration changes are saved in both Routing Engines. To interconnect a Virtual Chassis configuration across longer distances, such as wiring closets, you need to: • Prepare the existing Virtual Chassis configuration for interconnecting with a potential member switch that is beyond the reach of a Virtual Chassis cable by setting at least one uplink VCP on an existing member of Virtual Chassis configuration. • Prepare the potential member switch for interconnecting with the existing Virtual Chassis configuration by setting at least one uplink VCP on the standalone switch. 793 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: We recommend that you set two uplink VCPs within each wiring closet for redundancy. This topic describes: 1. Setting an Uplink VCP Between Two Member Switches on page 794 2. Setting an Uplink VCP on a Standalone Switch on page 794 Setting an Uplink VCP Between Two Member Switches Set an uplink port of a Virtual Chassis member as a VCP by executing the operational command request virtual-chassis vc-port. NOTE: If you use the SFP+ uplink module, you must configure all member switches to support either 1-gigabit SFP transceivers or 10-gigabit SFP+ transceivers. See “Setting the Mode on an SFP+ Uplink Module (CLI Procedure)” on page 921. To set the uplink ports for the local member switch (for example, member 0) and for a different member switch (for example, member 1) to function as VCPs: 1. Set one uplink port of member 0 as a VCP interface. You do not need to specify the member member-id option, because the command applies by default on the member where it is executed. user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 2. Set one uplink port of member 1 as a VCP interface. user@SWA-0>request virtual-chassis vc-port set pic-slot 1 port 0 member 1 This example includes the member member-id option, because it is executed on a different member switch than the local member switch. Setting an Uplink VCP on a Standalone Switch To set an uplink VCP on a standalone switch, first power on the switch. You must set an uplink port on the standalone switch as a VCP prior to physically interconnecting the switch with the existing Virtual Chassis configuration. Otherwise, the master cannot detect that the switch is a member of the Virtual Chassis configuration. To set one uplink VCP on the potential member (SWA-2), which is currently operating as a standalone switch: 1. Power on the standalone switch. 2. Set one uplink port as a VCP interface. You do not need to specify the member member-id option, because the command applies by default on the member where it is executed. user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 0 794 Chapter 45: Configuring Virtual Chassis NOTE: If you do specify the member member-id option, use member ID 0. Because the switch is not yet interconnected with the other members of the Virtual Chassis configuration, its current member ID is 0. Its member ID will change when it is interconnected with the Virtual Chassis configuration. It does not impact the functioning of the uplink VCP that its VCP interface is set with 0 as the member ID. The VCP interface has significance only on the local switch. 3. After you have set the uplink VCP on the standalone switch, physically interconnect its uplink port with the VCP uplink ports of the members in the existing Virtual Chassis configuration. 4. The new member switch reboots and joins the now expanded Virtual Chassis configuration with a different member ID. NOTE: The setting for the new member switch's uplink VCP remains intact and is not affected by the change of member ID. 5. If you have additional members in the second wiring closet, set a redundant VCP uplink on another member switch by issuing the request virtual-chassis vc-port command. Related Documentation • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 Setting an Uplink Module Port or a J-EX4200-24F Network Port as a Virtual Chassis Port Using the LCD Panel You can interconnect J-EX4200 switches that are beyond the reach of the Virtual Chassis cables as members of a Virtual Chassis configuration by installing the optional SFP or SFP+ uplink module and connecting the uplink module ports. You can also use the network ports on J-EX4200-24F switches to interconnect Virtual Chassis member switches. To use the uplink module ports or the J-EX4200-24F network ports for interconnecting member switches, you must explicitly set the ports as VCPs. This topic describes how to set the uplink module ports and the J-EX4200-24F network ports as VCPs using the LCD panel on the front of J-EX4200 switches. In this procedure, we show how to configure uplink module port ge-0/1/2 as a VCP. 795 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To set an uplink module port as a VCP using the LCD panel: 1. Press Menu until you see MAINTENANCE MENU. 2. Press Menu until you see REQUEST VC PORT. 3. Press Enter. You will see SET VC PORT?. 4. Press Enter. You will see SET FPC 0?. 5. Press Enter. You will see SET PIC 0?. 6. Press Menu until you see SET PIC 1?. 7. Press Enter. You will see SET PORT 0?. 8. Press Menu until you see SET PORT 2?. 9. Press Enter. You will see CONFIGURING .... 10. Once the configuration has been accepted, press Enter to return to the MAINTENANCE menu. You can also use the LCD panel to delete a VCP, thus resetting the port to an uplink module port or a J-EX4200-24F network port. To reset vcp-0/1/2 to an uplink module port using the LCD panel: 1. Press Menu until you see MAINTENANCE MENU. 2. Press Menu until you see REQUEST VC PORT. 3. Press Enter. You will see SET VC PORT?. 4. Press Menu. You will see DELETE VC PORT?. 5. Press Enter. You will see DELETE FPC 0?. 6. Press Enter. You will see DELETE PIC 0?. 7. Press Menu until you see DELETE PIC 1?. 8. Press Enter. You will see DELETE PORT 0?. 9. Press Menu until you see DELETE PORT 2?. 10. Press Enter. You will see CONFIGURING .... 11. Once the configuration has been accepted, press Enter to return to the MAINTENANCE menu. Related Documentation 796 • LCD Panel in J-EX4200 Switches • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Understanding Interface Naming Conventions on J-EX Series Switches on page 865 Chapter 45: Configuring Virtual Chassis Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) If you want to configure and manage a Virtual Chassis remotely through SSH or Telnet, configure the virtual management Ethernet (VME) interface on the master of the Virtual Chassis. You can configure and manage all members of the Virtual Chassis through this single global interface. 1. Power on the switch that you want to function as the master. 2. Check the front-panel LCD to confirm that the switch has powered on correctly. 3. Run the EZ Setup program on the switch, specifying the identification parameters. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. To configure the VME: [edit] user@SWA-0# set interfaces vme unit 0 family inet address /ip-address/mask/ Related Documentation • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Understanding Global Management of a Virtual Chassis Configuration on page 699 Configuring the Timer for the Backup Member to Start Using Its Own MAC Address, as Master of Virtual Chassis (CLI Procedure) When a backup member takes control of a Virtual Chassis configuration because of a reset or other temporary failure, the backup uses the MAC address of the old master. This helps to ensure a smooth transition of mastership with no disruption to network connectivity. The MAC persistence timer is used in situations when the master is no longer a member of the Virtual Chassis configuration, because it has been physically disconnected or removed. If the old master does not rejoin the Virtual Chassis configuration before the timer elapses, the new master starts using its own MAC address. The default timer value is 10 minutes. There are no minimum or maximum limits. Before you begin configuring the timer, ensure that you have at least two member switches in the Virtual Chassis configuration. To configure or modify the MAC persistence timer, use the following command: [edit virtual-chassis] user@switch# set mac-persistence-timer 30 This command modifies the MAC persistence timer value to specify a timer value of 30 minutes rather than the default timer value of 10 minutes. 797 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Virtual Chassis Components on page 694 Configuring Fast Failover in a Virtual Chassis Configuration The Virtual Chassis fast failover feature is a hardware-assisted failover mechanism that automatically reroutes traffic and reduces traffic loss in the event of a link or switch failure. If a link between two members fails, traffic flow between those members must be rerouted quickly so that there is minimal traffic loss. While fast failover is enabled by default on dedicated Virtual Chassis ports (VCPs), you must manually enable fast failover on uplink module ports that have been configured as VCPs. Before you begin configuring fast failover, ensure that the dedicated VCPs or uplink module VCPs are connected in a ring topology. • To reenable the fast failover feature on all dedicated VCPs in a ring: [edit] user@switch# delete virtual-chassis fast-failover vcp disable • To configure the fast failover feature on all SFP uplink module VCPs in a ring: [edit] user@switch# set virtual-chassis fast-failover ge Related Documentation 798 • Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Inter-Member Link Fails on page 763 • Disabling Fast Failover in a Virtual Chassis Configuration on page 799 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Fast Failover in a Virtual Chassis Configuration on page 706 Chapter 45: Configuring Virtual Chassis Disabling Fast Failover in a Virtual Chassis Configuration While fast failover is enabled by default on dedicated Virtual Chassis ports (VCPs), you can manually disable fast failover on dedicated VCPs using the set virtual-chassis fast-failover vcp disable command. • To disable the fast failover feature on all dedicated VCPs in a ring: [edit] user@switch# set virtual-chassis fast-failover vcp disable • To disable the fast failover feature on all SFP uplink module VCPs in a ring: [edit] user@switch# delete virtual-chassis fast-failover ge Related Documentation • Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Inter-Member Link Fails on page 763 • Configuring Fast Failover in a Virtual Chassis Configuration on page 798 • Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure) on page 792 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Fast Failover in a Virtual Chassis Configuration on page 706 Disabling Split and Merge in a Virtual Chassis Configuration (CLI Procedure) The split and merge feature is enabled by default on J-EX4200 switches in a Virtual Chassis configuration. You can disable the split and merge feature using the set virtual-chassis no-split-detection command. If you disable the split and merge feature and the Virtual Chassis configuration splits, both parts of the split Virtual Chassis configuration remain active. In a preprovisioned Virtual Chassis configuration, if both of the Routing Engines end up in the same Virtual Chassis configuration after a split, the other split Virtual Chassis configuration remains inactive. If the Routing Engines end up in different parts of the split Virtual Chassis configuration and the rest of the member switches are configured as having linecard roles, then a backup Routing Engine might not be selected for either part. To disable the split and merge feature in a Virtual Chassis configuration: [edit] user@switch# set virtual-chassis no-split-detection Related Documentation • Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge on page 767 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 799 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Understanding Split and Merge in a Virtual Chassis Configuration on page 712 • Understanding Virtual Chassis Configuration on page 704 Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge (CLI Procedure) Every Virtual Chassis configuration has a unique ID that is automatically assigned when the Virtual Chassis configuration is formed. You can also explicitly assign a Virtual Chassis ID using the set virtual-chassis id command. When two Virtual Chassis configurations attempt to merge, the Virtual Chassis ID that you assigned takes precedence over the automatically assigned Virtual Chassis IDs and becomes the ID for the newly merged Virtual Chassis configuration. To configure the Virtual Chassis ID: [edit] user@switch# set virtual-chassis id id Related Documentation • Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge on page 767 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Split and Merge in a Virtual Chassis Configuration on page 712 • Understanding Virtual Chassis Configuration on page 704 Configuring Automatic Software Update on Virtual Chassis Member Switches (CLI Procedure) The automatic software update feature allows you to automatically update the software version on prospective member switches as they are added so that they can join a Virtual Chassis configuration. Before you begin, ensure that you know the name or the URL of the software package to be used by the automatic software update feature. To configure the automatic software update feature: [edit] user@switch# set virtual-chassis auto-sw-update package-name package-name If the software package is located on a local directory on the switch, use the following format for package-name: /pathname/package-name If the software package is to be downloaded and installed from a remote location, use one of the following formats: ftp://hostname/pathname/package-name 800 Chapter 45: Configuring Virtual Chassis ftp://username:prompt@ftp.hostname.net/package-name http://hostname/pathname/package-name Related Documentation • Example: Configuring Automatic Software Update on Virtual Chassis Member Switches on page 777 • Understanding Automatic Software Update on Virtual Chassis Member Switches on page 715 Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure) In a Virtual Chassis configuration, one member switch is assigned the master role and has the master Rouing Engine. Another member switch is assigned the backup role and has the backup Routing Engine. Graceful Routing Engine switchover (GRES) enables the master and backup Routing Engines in a Virtual Chassis configuration to switch from the master to backup without interruption to packet forwarding. When you configure graceful Routing Engine switchover, the backup Routing Engine automatically synchronizes with the master Routing Engine to preserve kernel state information and the forwarding state. To set up a Virtual Chassis configuration to use graceful Routing Engine switchover (GRES): 1. Set up a minimum of two J-EX4200 switches in a Virtual Chassis configuration with mastership priority of 255: [edit] user@switch# set virtual-chassis member 0 mastership-priority 255 [edit] user@switch# set virtual-chassis member 1 mastership-priority 255 2. Set up graceful Routing Engine switchover: [edit] user@switch# set chassis redundancy graceful-switchover Commit the configuration. Related Documentation • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • High Availability Features for J-EX Series Switches Overview on page 18 • Understanding Virtual Chassis Configuration on page 704 • For more information about graceful Routing Engine switchover, see the Junos OS High Availability Configuration Guide at http://www.juniper.net/techpubs/software/junos/index.html. 801 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 802 CHAPTER 46 Verifying Virtual Chassis Configuration • Command Forwarding Usage with a Virtual Chassis Configuration on page 803 • Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual Chassis Member on page 807 • Verifying That the Virtual Chassis Ports Are Operational on page 808 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 • Verifying That Graceful Routing Engine Switchover Is Working in the Virtual Chassis Configuration on page 813 Command Forwarding Usage with a Virtual Chassis Configuration Some CLI commands can be run either on all members or on a specific member of a Virtual Chassis configuration. This functionality is referred to as command forwarding. For example, to collect information about your system prior to contacting Dell Support (see “Requesting Technical Support” on page lxxi), use the command request support information all-members to gather data for all the member switches. If you want to gather this data only for a particular member switch, use the command request support information member member-id . Table 108 on page 804 provides a list of commands that can be run either on all members of the Virtual Chassis configuration or on a specific member switch. 803 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 108: Commands That Can be Run on All or Specific Members of the Virtual Chassis Configuration Commands Available for Command Forwarding request support information Purpose all-members member-member-id Use this command when you contact Dell Support about your component problem. This command is the equivalent of using the following CLI commands: Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. • show version • show chassis firmware • show chassis hardware • show chassis environment • show interfaces extensive (for each configured interface) • show configuration (excluding any SECRET-DATA) • show system virtual-memory request system partition hard-disk Set up the hard disk for partitioning. After this command is issued, the hard disk is partitioned the next time the system is rebooted. When the hard disk is partitioned, the contents of /altroot and /altconfig are saved and restored. All other data on the hard disk is at risk of being lost. Partitions the hard disk on all members of the Virtual Chassis configuration. Partitions the hard disk on the specified member switch. request system reboot Reboot the Junos OS for J-EX Series switches after a software upgrade and occasionally to recover from an error condition. Reboots all members of the Virtual Chassis configuration. Reboots the specified member switch. request system snapshot Back up the currently running and active file system. Backs up the file systems on all members of the Virtual Chassis configuration. Backs up the file system on the specified member switch. request system storage cleanup Free storage space on the switch by rotating log files and proposing a list of files for deletion. User input is required for file deletion. Runs cleanup on all members of the Virtual Chassis configuration. Runs cleanup on the specified member switch. show log user Display users who are viewing the system log. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. 804 Chapter 46: Verifying Virtual Chassis Configuration Table 108: Commands That Can be Run on All or Specific Members of the Virtual Chassis Configuration (continued) Commands Available for Command Forwarding Purpose all-members member-member-id show system alarms Display active system alarms. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system audit Display the state and checksum values for file systems. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system boot-messages Display initial messages generated by the system kernel upon startup. These messages are the contents of /var/run/dmesg.boot. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system core-dumps Display a core file generated by an internal Junos OS process. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system directory-usage Display directory usage information. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system reboot Display pending system reboots or halts. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system snapshot Display information about the backup software that is located in the /altroot and /altconfig file systems. To back up software, use the request system snapshot command. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system software Display the Junos OS extensions loaded on your switch. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system statistics Display systemwide protocol-related statistics. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system storage Display statistics about the amount of free disk space in the switch's file systems. Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. 805 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 108: Commands That Can be Run on All or Specific Members of the Virtual Chassis Configuration (continued) Commands Available for Command Forwarding Purpose all-members member-member-id show system uptime Display the current time and information about how long the switch, the switch software, and any existing protocols have been running Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. show system users Show all users who are currently logged in. Shows all users who are currently logged in to any members of the Virtual Chassis configuration. Shows all users who are currently logged in to the specified member switch. show system virtual-memory Display the usage of the Junos OS kernel memory, listed first by size of allocation and then by type of usage. Use show system virtual-memory for troubleshooting with Dell Support (see “Requesting Technical Support” on page lxxi). Displays information for all members of the Virtual Chassis configuration. Displays information for the specified member switch. Table 109 on page 806 shows a list of commands that are relevant only to the master. Do not use the options all-members or member-member-id with these commands. Table 109: Commands Relevant Only to the Master Commands Relevant Only to the Master Purpose set date Set the data and time. show system buffers Display information about the buffer pool that the Routing Engine uses for local traffic. Local traffic is the routing and management traffic that is exchanged between the Routing Engine and the Packet Forwarding Engine within the switch, as well as the routing and management traffic from IP (that is, from OSPF, BGP, SNMP, ping operations, and so on). show system connections Display information about the active IP sockets on the Routing Engine. Use this command to verify which servers are active on a system and which connections are currently in progress. show system processes Display information about software processes that are running on the switch and that have controlling terminals. Related Documentation 806 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Understanding Virtual Chassis Components on page 694 Chapter 46: Verifying Virtual Chassis Configuration • Junos OS System Basics and Services Command Reference at http://www.juniper.net/techpubs/software/junos/ Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual Chassis Member Purpose You can designate the role that a member performs within a Virtual Chassis configuration or you can allow the role to be assigned by default. You can designate the member ID that is assigned to a specific switch by creating a permanent association between the switch’s serial number and a member ID, using a preprovisioned configuration. Or you can let the member ID be assigned by the master, based on the sequence in which the member switch is powered on and on which member IDs are currently available. The role and member ID of the member switch are displayed on the front-panel LCD. Each member switch can be cabled to one or two other member switches, using either the dedicated Virtual Chassis ports (VCPs) on the rear panel, an uplink module port that has been configured as a VCP, or an SFP network port on a J-EX4200-24F switch that has been configured as a VCP. The members that are cabled together are considered neighbor members. Action To display the role and member ID assignments using the CLI, use the show virtual-chassis status command: user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0000.e255.00e0 Meaning Mastership Priority Role Neighbor List ID, Interface Member ID Status Serial No Model 0 (FPC 0) Prsnt abc123 ex4200-48t 255 Master* 1 vcp-0 2 vcp-1 1 (FPC 1) Prsnt def456 ex4200-24t 255 Backup 2 vcp-0 0 vcp-1 2 (FPC 2) Prsnt abd231 ex4200-24t 128 Linecard 0 vcp-0 1 vcp-1 This output verifies that three J-EX4200 switches have been interconnected as a Virtual Chassis configuration using their dedicated VCPs . The display shows which of the VCPs is connected to which neighbor. The first port (vcp-0) of member 0 is connected to member 1 and the second port of member 0 (vcp-1) is connected to member 2. The FPC slots for J-EX Series switches are the same as the member IDs. The Mastership Priority values indicate that the master and backup members have been explicitly configured, because they are not using the default value (128). Related Documentation • Configuring Mastership of the Virtual Chassis (CLI Procedure) on page 790 • Configuring a Virtual Chassis (CLI Procedure) on page 781 807 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Example: Expanding a Virtual Chassis Configuration in a Single Wiring Closet on page 722 • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 Verifying That the Virtual Chassis Ports Are Operational Purpose Use the show virtual-chassis vc-port command to display the status of Virtual Chassis ports (VCPs). NOTE: The interfaces for VCPs are not displayed when you issue the show interfaces ge- command. Action Display the VCPs: user@SWA-0> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 1 vcp-0 vcp-1 Dedicated 2 Up 32000 1 vcp-1 1/0 Configured 3 Up 1000 2 vcp-255/1/0 1/1 Configured 3 Up 1000 2 vcp-255/1/1 1/2 Configured 4 Up 1000 4 vcp-255/0/20 1/3 Configured 4 Up 1000 4 vcp-255/0/21 fpc1: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 0 vcp-0 vcp-1 Dedicated 2 Up 32000 0 vcp-1 1/0 Configured 3 Up 10000 3 vcp-255/1/0 1/1 Configured 3 Up 10000 3 vcp-255/1/1 fpc2: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 3 vcp-0 vcp-1 Dedicated 2 Up 32000 3 vcp-1 1/0 Configured 3 Up 1000 0 vcp-255/1/0 1/1 Configured 3 Up 1000 0 vcp-255/1/1 1/2 —1 Down 1000 1/3 —1 Down 1000 808 Chapter 46: Verifying Virtual Chassis Configuration fpc3: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 2 vcp-0 vcp-1 Dedicated 2 Up 32000 2 vcp-1 1/0 Configured 3 Up 10000 1 vcp-255/1/0 1/1 Configured 3 Up 10000 1 vcp-255/1/1 fpc4: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Down 32000 vcp-1 Dedicated 2 Down 32000 0/20 Configured 3 Up 1000 0 vcp-255/1/2 0/21 Configured 3 Up 1000 0 vcp-255/1/3 Meaning Related Documentation The dedicated VCPs are displayed as vcp-0 and vcp-1. The uplink module interfaces that have been set as uplink VCPs are displayed as 1/0, 1/1, 1/2, and 1/3. The J-EX4200-24F network interfaces that have been set as VCPs are displayed as 0/20 and 0/21. The neighbor interface names of uplink and network VCPs are of the form vcp-255/pic/port—for example, vcp-255/1/0. In that name, vcp-255 indicates that the interface is a VCP, 1 is the uplink PIC number, and 0 is the port number. The fpc number is the same as the member ID. The trunk ID is a positive number ID assigned to the LAG formed by the Virtual Chassis. If no LAG is formed, the value is –1. • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 Monitoring Virtual Chassis Configuration Status and Statistics Purpose Action Use the monitoring functionality to view the following information about Virtual Chassis members and ports: • Member details and how members are connected with each other. • Traffic statistics for Virtual Chassis ports of the selected members. • Details of the Virtual Chassis port packet counters. To view Virtual Chassis monitoring details in the J-Web interface, select Monitor > Virtual Chassis. To view member details for all members in the CLI, enter the following command: 809 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show virtual-chassis status To view Virtual Chassis port traffic statistics for a specific member in the CLI, enter the following command: show virtual-chassis vc-port statistics member member-id To view the path a packet takes when going from a source interface to a destination interface in a Virtual Chassis configuration using the CLI, enter the following command: show virtual-chassis vc-path Meaning In the J-Web interface the top half of the screen displays details of the Virtual Chassis configuration, such as: • Member • Role • Interface • Type • Speed • Neighboring Member ID • Link Status • Error count Click the Stop button to stop fetching values from the switch, and click the Start button to start plotting data again from the point where it was stopped. To view a graph of the statistics for the selected Virtual Chassis port of the member, click Show Graph. Refresh Interval (sec)—Displays the time interval you have set for page refresh. Click Clear Statistics to clear the monitoring statistics for the selected member switch. You can specify the interval at which the member details and statistics must be refreshed. The bottom half of the screen displays a chart of the Virtual Chassis statistics, and the port packet counters. For details about the output from CLI commands, see show virtual-chassis status and show virtual-chassis vc-port statistics. Related Documentation 810 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 Chapter 46: Verifying Virtual Chassis Configuration • Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual Chassis Member on page 807 Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) You can replace a member switch of a Virtual Chassis configuration without disrupting network service for the other members. You can retain the existing configuration of the member switch and apply it to a new member switch, or you can free up the member ID and make it available for assignment to a new member switch. To replace a member switch, use the procedure that matches what you need to accomplish: • Remove, Repair, and Reinstall the Same Switch on page 811 • Remove a Member Switch, Replace with a Different Switch, and Reapply the Old Configuration on page 812 • Remove a Member Switch and Make Its Member ID Available for Reassignment to a Different Switch on page 812 Remove, Repair, and Reinstall the Same Switch If you need to repair a member switch, you can remove it from the Virtual Chassis configuration without disrupting network service for the other members. The master stores the configuration of the member ID so that it can be reapplied when the member switch (with the same base MAC address) is reconnected. 1. Power off and disconnect the member switch to be repaired. 2. Repair, as necessary. 3. Reconnect and power on the member switch. 811 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Remove a Member Switch, Replace with a Different Switch, and Reapply the Old Configuration If you are unable to repair a member switch, you can replace it with a different member switch and retain the old configuration. The master stores the configuration of the member that was removed. When you connect a different member switch, the master assigns a new member ID. But the old configuration is still stored under the previous member ID of the previous member switch. NOTE: If you have used a preprovisioned configuration, use the replace command to change the serial number in the Virtual Chassis configuration file. Substitute the serial number of the replacement member switch (on the back of the switch) for the serial number of the member switch that was removed. 1. Power off and disconnect the member switch to be replaced. 2. If the replacement member switch has been previously configured, revert that switch’s configuration to the factory defaults. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. 3. Connect and power on the replacement member switch. 4. Note the member ID displayed on the front panel. 5. Issue the request virtual-chassis renumber command from the Virtual Chassis master to change the member switch’s current member ID to the member ID that belonged to the member switch that was removed from the Virtual Chassis configuration). Remove a Member Switch and Make Its Member ID Available for Reassignment to a Different Switch When you remove a member switch from the Virtual Chassis configuration, the master keeps its member ID on reserve. To make that member switch’s member ID available for reassignment, issue the request virtual-chassis recycle command from the Virtual Chassis master. NOTE: When you add or delete members in a Virtual Chassis configuration, internal routing changes might cause temporary traffic loss for a few seconds. Related Documentation 812 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) on page 786 Chapter 46: Verifying Virtual Chassis Configuration Verifying That Graceful Routing Engine Switchover Is Working in the Virtual Chassis Configuration Purpose Action Verify that graceful Routing Engine switchover (GRES) is working in the Virtual Chassis configuration. On the master switch, verify the member ID of the backup Routing Engine: {master:0} user@switch> show virtual-chassis status Virtual Chassis ID: 5efa.4b7a.aae6 Member ID 0 (FPC 0) 1 (FPC 1) Status Prsnt Prsnt Mastership Serial No Model priority BM0208105281 ex4200-24t 255 BP0208192350 ex4200-48t 255 Role Master* Backup Neighbor List ID Interface 1 vcp-0 0 vcp-0 Member ID for next new member: 2 (FPC 2) Connect to the backup Routing Engine: {master:0} user@switch> request session member 1 {backup:1} user@switch> Verify that the backup Routing Engine is ready for switchover on member ID 1: {backup:1} user@switch> show system switchover Graceful switchover: On Configuration database: Ready Kernel database: Ready Peer state: Steady State Switch the current backup Routing Engine to master Routing Engine: NOTE: You must wait a minimum of 2 minutes between Routing Engine failovers for the Routing Engines to synchronize. {backup:1} user@switch> request chassis routing-engine master acquire Verify that the master and backup Routing Engines have switched roles: NOTE: Member ID 1 is now the master, and member ID 0 is now the backup. {master:1} user@switch> show virtual-chassis status Virtual Chassis ID: 5efa.4b7a.aae6 813 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Member ID 0 (FPC 0) 1 (FPC 1) Status Prsnt Prsnt Mastership Serial No Model priority BM0208105281 ex4200-24t 255 BP0208192350 ex4200-48t 255 Role Backup Master* Neighbor List ID Interface 1 vcp-0 0 vcp-0 Member ID for next new member: 2 (FPC 2) Meaning Related Documentation 814 With graceful Routing Engine switchover enabled, when you initiated a switchover from the backup Routing Engine, the backup Routing Engine became the master and the master Routing Engine became the backup. • Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure) on page 801 CHAPTER 47 Troubleshooting Virtual Chassis • Troubleshooting a Virtual Chassis Configuration on page 815 Troubleshooting a Virtual Chassis Configuration • Clear Virtual Chassis NotPrsnt Status and Make Member ID Available for Reassignment on page 815 • Load Factory Default Does Not Commit on a Multimember Virtual Chassis on page 815 • Member ID Persists When a Member Switch Is Disconnected From a Virtual Chassis on page 815 Clear Virtual Chassis NotPrsnt Status and Make Member ID Available for Reassignment Problem You disconnected a J-EX4200 from the Virtual Chassis configuration, but the disconnected switch’s member ID is still displayed in the status output. You cannot reassign that member ID to another switch. Solution When you disconnect a member of a Virtual Chassis configuration, the master retains the member ID and member configuration in its configuration database. The show virtual-chassis status command continues to display the member ID of the disconnected member with a status of NotPrsnt. If want to permanently disconnect the member switch, you can free up the member ID by using the request virtual-chassis recycle command. This will also clear the status of that member. Load Factory Default Does Not Commit on a Multimember Virtual Chassis Problem The load factory default command fails on a multimember Virtual Chassis configuration. Solution The load factory default command is not supported on a multimember Virtual Chassis configuration. For information on how to revert to factory default settings, see “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 341. Member ID Persists When a Member Switch Is Disconnected From a Virtual Chassis Problem Gigabit Ethernet interfaces retain their previous slot numbers when a member switch is disconnected from the Virtual Chassis configuration. 815 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Solution If a switch had been previously connected as a member of a Virtual Chassis configuration, it retains the member ID that it was assigned as a member of that configuration even after it is disconnected and operating as a standalone switch. The interfaces that were configured while the switch was a member of the Virtual Chassis configuration retain the old member ID as the first digit of the interface name. For example, if the switch was previously member 1, its interfaces are named ge-1/0/0 and so on. To change the switch’s member ID, so that its member ID is 0, and to rename the switch’s interfaces accordingly, enter the following operational-mode commands: 1. To change the member ID to 0: user@switch> request virtual-chassis renumber member-id 1 new-member-id 0 2. To rename the interfaces to match the new member ID: user@switch# replace pattern ge-1/ with ge-0/ Related Documentation 816 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • For more information about the replace command, see Junos OS CLI User Guide at http://www.juniper.net/techpubs/software/junos/ . CHAPTER 48 Configuration Statements for Virtual Chassis • [edit virtual-chassis] Configuration Statement Hierarchy on page 817 [edit virtual-chassis] Configuration Statement Hierarchy virtual-chassis { auto-sw-update { package-name-edit-virtual-chassis.xml package-name; } fast-failover (ge | vcp disable | xe); id id; mac-persistence-timer seconds; member member-id { mastership-priority number; no-management-vlan; serial-number; role; } no-split-detection; preprovisioned; traceoptions { file filename ; flag flag ; } } Related Documentation • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Virtual Chassis Overview on page 691 817 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS auto-sw-update Syntax Hierarchy Level Release Information Description auto-sw-update { package-name package-name; } [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the automatic software update feature for Virtual Chassis configurations. The remaining statement is explained separately. Default Required Privilege Level Related Documentation 818 The automatic software update feature is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Automatic Software Update on Virtual Chassis Member Switches on page 777 • Configuring Automatic Software Update on Virtual Chassis Member Switches (CLI Procedure) on page 800 Chapter 48: Configuration Statements for Virtual Chassis fast-failover Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation fast-failover (ge | vcp disable | xe); [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the fast failover feature on all SFP uplink module Virtual Chassis ports (VCPs) or disable the fast failover feature on all dedicated VCPs in a ring topology. Fast failover is enabled on dedicated VCPs; it is not enabled on uplink module VCPs. • ge—Enable fast failover on all Gigabit Ethernet uplink module VCPs in the ring. • vcp disable—Disable fast failover on all dedicated VCPs in the ring. • xe—Enable fast failover on all 10-Gigabit Ethernet uplink module VCPs in the ring. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Inter-Member Link Fails on page 763 • Configuring Fast Failover in a Virtual Chassis Configuration on page 798 • Disabling Fast Failover in a Virtual Chassis Configuration on page 799 819 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS graceful-switchover Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation graceful-switchover; [edit chassis redundancy] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For switches with more than one Routing Engine, including those in a Virtual Chassis, configure the master Routing Engine to switch over gracefully to a backup Routing Engine without interruption to packet forwarding. Graceful Routing Engine switchover (GRES) is disabled. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Nonstop Active Routing on J-EX Series Switches • Configuring Graceful Routing Engine Switchover in a J-EX4200 Virtual Chassis (CLI Procedure) on page 801 • Configuring Nonstop Active Routing on J-EX Series Switches (CLI Procedure) • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 71 id Syntax Hierarchy Level Release Information Description Options id id; [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the alphanumeric string that identifies a Virtual Chassis configuration. id—ID of the Virtual Chassis configuration, which uses the ISO family address format—for example, 9622.6ac8.5345. Required Privilege Level Related Documentation 820 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge on page 767 • Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge (CLI Procedure) on page 800 • Understanding Split and Merge in a Virtual Chassis Configuration on page 712 Chapter 48: Configuration Statements for Virtual Chassis mac-persistence-timer Syntax Hierarchy Level Release Information Description mac-persistence-timer minutes; [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. If the master is physically disconnected or removed from the Virtual Chassis configuration, the MAC persistence timer determines how long the backup (new master) continues to use the address of the old master. When the MAC persistence timer expires, the backup (new master) begins to use its own MAC address. There are no minimum or maximum timer limits. Default Required Privilege Level Related Documentation 10 minutes routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Timer for the Backup Member to Start Using Its Own MAC Address, as Master of Virtual Chassis (CLI Procedure) on page 797 • Understanding Virtual Chassis Components on page 694 821 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mastership-priority Syntax Hierarchy Level Release Information Description mastership-priority number ; [edit virtual-chassis member member-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. The mastership priority value is the most important factor in determining the role of the J-EX4200 member switch within the Virtual Chassis configuration. Other factors (see “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698) also affect the election of the master. The mastership priority value takes the highest precedence in the master election algorithm. The member switch with highest mastership priority becomes the master of the Virtual Chassis configuration. Toggling back and forth between master and backup status in failover conditions is undesirable, so we recommend that you assign the same mastership priority value to both the master and the backup. Secondary factors in the master election algorithm determine which of these two members (that is, the two members that are assigned the highest mastership priority value) functions as the master of the Virtual Chassis configuration. Default Options 128 number—Mastership priority value. Range: 1 through 255 Required Privilege Level Related Documentation 822 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets on page 733 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Virtual Chassis Components on page 694 Chapter 48: Configuration Statements for Virtual Chassis member Syntax Hierarchy Level member member-id { mastership-priority number; no-management-vlan; serial-number; role; } [edit virtual-chassis] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure a J-EX4200 switch as a member of a Virtual Chassis configuration. Default Options When a J-EX4200 is powered on as a standalone switch (not interconnected through its Virtual Chassis ports with other J-EX4200 switches), its default member ID is 0. member-id—Identifies a specific member switch of a Virtual Chassis configuration. Range: 0 through 9 The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Virtual Chassis Components on page 694 823 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-management-vlan Syntax Hierarchy Level Release Information Description no-management-vlan; [edit virtual-chassis member member-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Remove the specified member’s out-of-band management port from the Virtual Management Ethernet (VME) global management VLAN of the Virtual Chassis configuration. For a member that is functioning in a linecard role, you can use this configuration to reserve the member's management Ethernet port for local troubleshooting: virtual-chassis { member 2 { no-management-vlan; } } You cannot configure the IP address for a local management Ethernet port using the CLI or the J-Web interface. To do this, you need to use the shell ifconfig command. Required Privilege Level Related Documentation 824 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up a Multimember Virtual Chassis Access Switch with a Default Configuration on page 727 • Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) on page 797 • Understanding Global Management of a Virtual Chassis Configuration on page 699 Chapter 48: Configuration Statements for Virtual Chassis no-split-detection Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-split-detection; [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the split and merge feature in a Virtual Chassis configuration. The split and merge feature is enabled by default on J-EX4200 switches. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge on page 767 • Disabling Split and Merge in a Virtual Chassis Configuration (CLI Procedure) on page 799 • Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge (CLI Procedure) on page 800 • Understanding Split and Merge in a Virtual Chassis Configuration on page 712 825 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS package-name Syntax Hierarchy Level Release Information Description Default Options package-name package-name; [edit virtual-chassis auto-sw-update] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the software package name or location of the software package to be used by the automatic software update feature for Virtual Chassis configurations. No package name is specified. package-name—Name of the software package or the URL to the software package to be used. • If the software package is located on a local directory on the switch, use the following format for package-name: /pathname/package-name • If the software package is to be downloaded and installed from a remote location, use one of the following formats: ftp://hostname/pathname/package-name ftp://username:prompt@ftp.hostname.net/package-name http://hostname/pathname/package-name Required Privilege Level Related Documentation 826 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Automatic Software Update on Virtual Chassis Member Switches on page 777 • Configuring Automatic Software Update on Virtual Chassis Member Switches (CLI Procedure) on page 800 Chapter 48: Configuration Statements for Virtual Chassis preprovisioned Syntax Hierarchy Level Release Information Description preprovisioned; [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the preprovisioned configuration mode for a Virtual Chassis configuration. When preprovisioned configuration mode is enabled, you cannot use the CLI or the J-Web interface to change the mastership priority or member ID of member switches. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) on page 786 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 • Understanding Virtual Chassis Configuration on page 704 827 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS redundancy (Graceful Switchover) Syntax Hierarchy Level Release Information Description redundancy { graceful-switchover; } [edit chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX4200 switches configured as a Virtual Chassis and for J-EX8200 switches with more than one Routing Engine, enable redundant Routing Engines. The remaining statement is explained separately. Default Required Privilege Level Related Documentation 828 Redundancy is enabled for the Routing Engines. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Graceful Routing Engine Switchover in a J-EX4200 Virtual Chassis (CLI Procedure) on page 801 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 71 Chapter 48: Configuration Statements for Virtual Chassis role Syntax Hierarchy Level Release Information Description Options role (routing-engine | line-card); [edit virtual-chassis preprovisioned member member-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. In a preprovisioned Virtual Chassis configuration, specify the role to be performed by each J-EX4200 member switch. Associate the role permanently with the member’s serial number. routing-engine—Enables the member eligible to function as a master or backup of the Virtual Chassis configuration. The master manages all the members of the Virtual Chassis configuration and runs the chassis management processes and control protocols. The backup synchronizes with the master in terms of protocol states, forwarding tables, and so forth, so that it is prepared to preserve routing information and maintain network connectivity without disruption in case the master is unavailable. Specify two and only two members as routing-engine. The software determines which of the two members assigned the routing-engine role functions as master, based on the master election algorithm. See “Understanding How the Master in a Virtual Chassis Configuration Is Elected” on page 698. line-card—Enables the member to be eligible to function only in the linecard role. Any member of the Virtual Chassis configuration other than the master or backup functions in the linecard role and runs only a subset of the Junos OS for J-EX Series switches. A member functioning in the linecard role does not run the chassis control protocols. A Virtual Chassis configuration must have at least three members in order to include a member that functions in the linecard role. When you use a preprovisioned configuration, you cannot modify the mastership priority or member ID of member switches through the user interfaces. The mastership priority value is generated by the software, based on the assigned role: • A member configured as routing-engine is assigned the mastership priority 129. • A member configured as line-card is assigned the mastership priority 0. • A member listed in the preprovisioned configuration without an explicitly specified role is assigned the mastership priority 128. The configured role specifications are permanent. If both routing-engine members should fail, a line-card member cannot take over as master of the Virtual Chassis configuration. You must delete the preprovisioned configuration in order to change the specified roles. It is possible to explicitly configure two members as routing-engine and to configure additional switches as members of the preprovisioned Virtual Chassis by specifying only their serial numbers. If you do not explicitly configure the role of the additional 829 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS members, they function in a linecard role by default. In that case, a member that is functioning in a linecard role can take over mastership if the members functioning as master and backup (routing-engine role) both fail. Required Privilege Level Related Documentation 830 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) on page 786 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 • Understanding Virtual Chassis Configuration on page 704 Chapter 48: Configuration Statements for Virtual Chassis serial-number Syntax Hierarchy Level Release Information Description Options serial-number serial-number; [edit virtual-chassis preprovisioned member member-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. In a preprovisioned Virtual Chassis configuration, specify the serial number of each J-EX4200 member switch to be included in the Virtual Chassis configuration. If you do not include the serial number within the Virtual Chassis configuration, the switch cannot be recognized as a member of a preprovisioned configuration. serial-number—The switch’s permanent serial number, which is located on the back of the switch. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File on page 752 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure) on page 786 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 • Understanding Virtual Chassis Configuration on page 704 831 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions Syntax Hierarchy Level Release Information Description Default Options traceoptions { file filename ; flag flag ; } [edit virtual-chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for the Virtual Chassis configuration. Tracing operations are disabled. detail—(Optional) Generate detailed trace information for a flag. disable—(Optional) Disable a flag. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. 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 also must specify a maximum file size with the size option. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—All tracing operations. TIP: The all flag displays a subset of logs that are useful in debugging most issues. For more detailed information, use all detail. • auto-configuration—Trace Virtual Chassis ports (VCPs) that have been automatically configured. 832 • csn—Trace Virtual Chassis complete sequence number (CSN) packets. • error—Trace Virtual Chassis errored packets. • hello—Trace Virtual Chassis hello packets. • krt—Trace Virtual Chassis KRT events. • lsp—Trace Virtual Chassis link-state packets. Chapter 48: Configuration Statements for Virtual Chassis • lsp-generation—Trace Virtual Chassis link-state packet generation. • me—Trace Virtual Chassis ME events. • normal—Trace normal events. • packets—Trace Virtual Chassis packets. • parse—Trace reading of the configuration. • psn—Trace partial sequence number (PSN) packets. • route—Trace Virtual Chassis routing information. • spf—Trace Virtual Chassis SPF events. • state—Trace Virtual Chassis state transitions. • task—Trace Virtual Chassis task operations. no-stamp—(Optional) Do not place a timestamp on any trace file. no-world-readable—(Optional) Restrict file access to the user who created the file. receive—(Optional) Trace received packets. replace—(Optional) Replace a trace file rather than appending information to it. send—(Optional) Trace transmitted packets. 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 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 also must specify a maximum file size with the files option. 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. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual Chassis Member on page 807 • Verifying That the Virtual Chassis Ports Are Operational on page 808 • Troubleshooting a Virtual Chassis Configuration on page 815 833 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS virtual-chassis Syntax Hierarchy Level Release Information Description virtual-chassis { auto-sw-upgrade { package-name-edit-virtual-chassis.xml package-name; } fast-failover (ge | vcp disable | xe); id id; mac-persistence-timer seconds; member member-id { mastership-priority number; no-management-vlan; serial-number; role; } no-split-detection; preprovisioned; traceoptions { file filename ; flag flag ; } } [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Virtual Chassis information on a J-EX4200 switch. The remaining statements are explained separately. Default Required Privilege Level Related Documentation 834 A standalone J-EX4200 switch is a Virtual Chassis by default. It has a default member ID of 0, a default mastership priority of 128, and a default role as master. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Configuring a Virtual Chassis (CLI Procedure) on page 781 • Configuring a Virtual Chassis (J-Web Procedure) on page 784 • Understanding Virtual Chassis Components on page 694 CHAPTER 49 Operational Mode Commands for Virtual Chassis 835 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear virtual-chassis vc-port statistics Syntax Release Information Description Options clear virtual-chassis vc-port statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear—reset to zero (0)—the traffic statistics counters on Virtual Chassis ports (VCPs). none—Clear traffic statistics for the VCPs of all members of a Virtual Chassis configuration. all-members—(Optional) Clear traffic statistics for the VCPs of all members of a Virtual Chassis configuration. interface-name—(Optional) Name of the VCP interface to be cleared of its traffic statistics. Specify either vcp-0 or vcp-1. local—(Optional) Clear VCP traffic statistics from only the switch on which this command is entered. member member-id—(Optional) Clear VCP traffic statistics from only the specified member of a Virtual Chassis configuration. Required Privilege Level Related Documentation List of Sample Output clear virtual-chassis vc-port statistics clear • show virtual-chassis vc-port statistics on page 854 • show virtual-chassis vc-port on page 851 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Understanding Virtual Chassis Components on page 694 clear virtual-chassis vc-port statistics on page 836 clear virtual-chassis vc-port statistics member 3 on page 836 user@SWA-0> clear virtual-chassis vc-port statistics fpc0: -------------------------------------------------------------------------Statistics cleared {master:0} clear virtual-chassis vc-port statistics member 3 836 user@SWA-0> clear virtual-chassis vc-port statistics member 3 Cleared statistics on member 3 Chapter 49: Operational Mode Commands for Virtual Chassis request session member Syntax Release Information Description Options request session member member-id Command introduced before Junos OS Release 10.2 for J-EX Series switches. Starts a session with the specified member of a Virtual Chassis configuration. member-id—Select the specific member of the Virtual Chassis configuration with which you want to establish a session. Required Privilege Level Related Documentation maintenance • member on page 823 • Understanding Virtual Chassis Components on page 694 837 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request virtual-chassis recycle Syntax Release Information Description request virtual-chassis recycle member-id member-id Command introduced before Junos OS Release 10.2 for J-EX Series switches. Make a previously used member ID available for reassignment. When you remove a member switch from the Virtual Chassis configuration, the master reserves that member ID. To make the member ID available for reassignment, you must use this command. NOTE: You can run this command from the Virtual Chassis master only. Options member-id member-id—Specify the member id that you want to make available for reassignment to a different member switch. Required Privilege Level Related Documentation system-control • request virtual-chassis renumber on page 839 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 List of Sample Output request virtual-chassis recycle member-id 3 on page 838 request virtual-chassis recycle member-id 3 user@host> request virtual-chassis recycle member-id 3 838 Chapter 49: Operational Mode Commands for Virtual Chassis request virtual-chassis renumber Syntax Release Information Description request virtual-chassis renumber member-id old-member-id new-member-id new-member-id Command introduced before Junos OS Release 10.2 for J-EX Series switches. Renumber a member of a Virtual Chassis configuration. NOTE: You can run this command from the Virtual Chassis master only. Options member-id old-member-id—Specify the ID of the member that you wish to renumber. new-member-id new-member-id—Specify an unassigned member ID (from 0 through 9). Required Privilege Level Related Documentation system-control • request virtual-chassis recycle on page 838 • Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on page 811 List of Sample Output request virtual-chassis renumber member-id 5 new-member-id 4 on page 839 request virtual-chassis renumber member-id 5 new-member-id 4 user@SWA-0> request virtual-chassis renumber member-id 5 new-member-id 4 839 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request virtual-chassis vc-port Syntax Release Information Description Options request virtual-chassis vc-port set | delete pic-slot pic-slot port port-number Command introduced before Junos OS Release 10.2 for J-EX Series switches. Enable or disable an uplink module port (on an SFP or SFP+ uplink module) or an SFP network port on a J-EX4200-24F switch as a Virtual Chassis port (VCP). pic-slot pic-slot—Number of the PIC slot for the uplink module port or SFP network port on a J-EX4200-24F switch. Specify 1 to represent the uplink module PIC on the J-EX Series switch. Specify 0 to represent the SFP network port on a J-EX4200-24F switch. port port-number—Number of the uplink module port (0 or 1) or SFP network port on a J-EX4200-24F switch (0 to 23) that is to be enabled or disabled as a VCP. member member-id—(Optional) Enable or disable the specified VCP on the specified member of the Virtual Chassis configuration. Additional Information Required Privilege Level Related Documentation If you omit member member-id, this command defaults to enabling or disabling the uplink VCP or SFP network port configured as a VCP on the switch where the command is issued. system-control • request virtual-chassis vc-port on page 841 (dedicated port) • show virtual-chassis vc-port on page 851 • show virtual-chassis vc-port statistics on page 854 • clear virtual-chassis vc-port statistics on page 836 • Understanding Virtual Chassis Components on page 694 List of Sample Output request virtual-chassis vc-port set pic-slot 1 port 0 on page 840 request virtual-chassis vc-port set pic-slot 1 port 1 member 3 on page 840 request virtual-chassis vc-port delete pic-slot 1 port 1 member 3 on page 840 request virtual-chassis vc-port set pic-slot 1 port 0 user@host>request virtual-chassis vc-port set pic-slot 1 port 0 request virtual-chassis vc-port set pic-slot 1 port 1 member 3 user@host>request virtual-chassis vc-port set pic-slot 1 port 1 member 3 request virtual-chassis vc-port delete pic-slot 1 port 1 member 3 user@host>request virtual-chassis vc-port delete pic-slot 1 port 1 member 3 840 To check the results of this command, use the show virtual-chassis vc-port command. To check the results of this command, use the show virtual-chassis vc-port command. To check the results of this command, use the show virtual-chassis vc-port command. Chapter 49: Operational Mode Commands for Virtual Chassis request virtual-chassis vc-port Syntax Release Information request virtual-chassis vc-port set interface vcp-interface-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Disable or enable a Virtual Chassis port (VCP) for a dedicated VCP on the rear panel of the Virtual Chassis. Options interface vcp-interface-name —Name of the interface to enable or disable. Specify either vcp-0 or vcp-1. member member-id —(Optional) Enable or disable the specified VCP on the specified member of the Virtual Chassis configuration. disable —(Optional) Disable the specified VCP. If you omit this keyword, the command enables the dedicated VCP. Additional Information Required Privilege Level Related Documentation If you omit member member-id, this command defaults to disabling or enabling the dedicated VCP on the switch where the command is issued. The dedicated VCPs are enabled in the factory default configuration. system-control • request virtual-chassis vc-port on page 840 • show virtual-chassis vc-port on page 851 • show virtual-chassis vc-port statistics on page 854 • clear virtual-chassis vc-port statistics on page 836 • Understanding Virtual Chassis Components on page 694 List of Sample Output request virtual-chassis vc-port set interface vcp-0 disable on page 841 request virtual-chassis vc-port set interface vcp-0 member 3 disable on page 841 request virtual-chassis vc-port set interface vcp-0 disable user@host> request virtual-chassis vc-port set interface vcp-0 disable request virtual-chassis vc-port set interface vcp-0 member 3 disable user@host> request virtual-chassis vc-port set interface vcp-0 member 3 disable To check the results of this command, use the show virtual-chassis vc-port command. To check the results of this command, use the show virtual-chassis vc-port command. 841 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system uptime Syntax Release Information Description Options show system uptime (all-members | member member-id) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the current time and information about how long the Virtual Chassis, Virtual Chassis software, and routing protocols have been running. all-members—Display the current time and information about how long the Virtual Chassis, Virtual Chassis software, and routing protocols have been running for all the member switches of the Virtual Chassis configuration. member member-id—Display the current time and information about how long the Virtual Chassis, Virtual Chassis software, and routing protocols have been running for the specific member of the Virtual Chassis configuration. Required Privilege Level Related Documentation List of Sample Output Output Fields view • virtual-chassis on page 834 • Monitoring System Properties on page 550 • For more information about show system uptime, see the Junos OS System Basics Services and Command Reference at http://www.juniper.net/techpubs/software/junos/. show system uptime member 0 on page 843 Table 110 on page 842 lists the output fields for the show system uptime command. Output fields are listed in the approximate order in which they appear. Table 110: show system uptime Output Fields Field Name Field Description Current time Current system time in UTC. System booted Date and time when the switch was last booted and how long it has been running. Protocols started Date and time when the routing protocols were last started and how long they have been running. Last configured Date and time when a configuration was last committed. Also shows the name of the user who issued the last commit command. Time and up Current time, in the local time zone, and how long the switch has been operational. Users Number of users logged into the switch. 842 Chapter 49: Operational Mode Commands for Virtual Chassis Table 110: show system uptime Output Fields (continued) Field Name Field Description Load averages Load averages for the last 1 minute, 5 minutes, and 15 minutes. show system uptime member 0 user@host>show system uptime member 0 fpc0: -----------------------------------------------------------------------Current time: 2008-02-06 05:24:20 UTC System booted: 2008-01-31 08:26:54 UTC (5d 20:57 ago) Protocols started: 2008-01-31 08:27:56 UTC (5d 20:56 ago) Last configured: 2008-02-05 03:26:43 UTC (1d 01:57 ago) by root 5:24AM up 5 days, 20:57, 1 user, load averages: 0.14, 0.06, 0.01 843 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show virtual-chassis active topology Syntax Release Information Description Options show virtual-chassis active-topology <(all-members | member member-id)> Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the active topology of the Virtual Chassis configuration with reachability information. none—Display the active topology of the member switch where the command is issued. all-members—Display the active topology of all members of the Virtual Chassis configuration. member member-id—Display the active topology of a specified member of the Virtual Chassis configuration. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Understanding Virtual Chassis Configuration on page 704 show virtual-chassis active-topology on page 844 Table 111 on page 844 lists the output fields for the show virtual-chassis active-topology command. Output fields are listed in the approximate order in which they appear. Table 111: show virtual-chassis active-topology Output Fields Field Name Field Description Destination ID Specifies the member ID of the destination. Next-hop Specifies the member ID and VCP of the next-hop to which packets for the destination ID are forwarded. show virtual-chassis active-topology 844 user@SWA-0> show virtual-chassis active-topology 1 1(vcp-1) 2 1(vcp-1) 3 1(vcp-1) 4 1(vcp-1) Chapter 49: Operational Mode Commands for Virtual Chassis 5 8(vcp-0) 6 8(vcp-0) 7 8(vcp-0) 8 8(vcp-0) 1(vcp-1) 845 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show virtual-chassis fast-failover Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show virtual-chassis fast-failover Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the fast failover feature in a Virtual Chassis configuration. view • Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a Virtual Chassis Member Switch or Inter-Member Link Fails on page 763 • Configuring Fast Failover in a Virtual Chassis Configuration on page 798 • Disabling Fast Failover in a Virtual Chassis Configuration on page 799 • Understanding Fast Failover in a Virtual Chassis Configuration on page 706 show virtual-chassis fast-failover on page 846 Table 112 on page 846 lists the output fields for the show virtual-chassis fast-failover command. Output fields are listed in the approximate order in which they appear. Table 112: show virtual-chassis fast-failover Output Fields Field Name Field Description Fast failover on dedicated VCP ports Indicates fast failover status on dedicated VCPs. Fast failover on XE uplink VCP ports Indicates fast failover status on XFP uplink module VCPs. (Not supported on Dell PowerConnect J-EX Series Switches.) Fast failover on GE uplink VCP ports Indicates fast failover status on SFP uplink module VCPs. show virtual-chassis fast-failover 846 user@switch1> Fast failover Fast failover Fast failover show virtual-chassis fast-failover on dedicated VCP ports: Enabled on XE uplink VCP ports: Disabled on GE uplink VCP ports: Enabled Chapter 49: Operational Mode Commands for Virtual Chassis show virtual-chassis status Syntax Release Information Description Options Required Privilege Level Related Documentation Output Fields show virtual-chassis status Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about all the members of the Virtual Chassis configuration. none—Display all information for all member switches of the Virtual Chassis configuration. view • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Understanding Virtual Chassis Configuration on page 704 Table 113 on page 847 lists the output fields for the show virtual-chassis status command. Output fields are listed in the approximate order in which they appear. Table 113: show virtual-chassis status Output Fields Field Name Field Description Virtual Chassis ID Assigned ID that applies to the entire Virtual Chassis configuration. Member ID Assigned member ID and FPC slot (from 0 through 9). Status For a nonprovisioned configuration: • Prsnt for a member that is currently connected to the Virtual Chassis configuration • NotPrsnt for a member ID that has been assigned but is not currently connected For a preprovisioned configuration: • Prsnt for a member that is specified in the preprovisioned configuration file and is currently connected to the Virtual Chassis configuration. • Unprvsnd for a member that is interconnected with the Virtual Chassis configuration, but is not specified in the preprovisioned configuration file. Serial No Serial number of the member switch. Model Model number of the member switch. Mastership Priority Mastership priority value of the member switch. Role Role of the member switch. Neighbor List Member ID of the neighbor member to which this member’s VCP interface is connected. 847 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show virtual-chassis status user@SWA-0> show virtual-chassis status Virtual Chassis ID: 0019.e250.47a0 Member ID 0 (FPC 0) Status Prsnt Mastership Serial No Model priority AK0207360276 ex4200-24t 249 Role Master* 1 (FPC 1) Prsnt AK0207360281 ex4200-24t 248 Backup 2 (FPC 2) Prsnt AJ0207391130 ex4200-48t 247 Linecard 3 (FPC 3) Prsnt AK0207360280 ex4200-24t 246 Linecard 4 (FPC 4) Prsnt AJ0207391113 ex4200-48t 245 Linecard 5 (FPC 5) Prsnt BP0207452204 ex4200-48t 244 Linecard 6 (FPC 6) Prsnt BP0207452222 ex4200-48t 243 Linecard 7 (FPC 7) Prsnt BR0207432028 ex4200-24f 242 Linecard 8 (FPC 8) Prsnt BR0207431996 ex4200-24f 241 Linecard Member ID for next new member: 9 (FPC 9) 848 Neighbor List ID Interface 8 vcp-0 1 vcp-1 0 vcp-0 2 vcp-1 1 vcp-0 3 vcp-1 2 vcp-0 4 vcp-1 3 vcp-0 5 vcp-1 4 vcp-0 6 vcp-1 5 vcp-0 7 vcp-1 6 vcp-0 8 vcp-1 7 vcp-0 0 vcp-1 Chapter 49: Operational Mode Commands for Virtual Chassis show virtual-chassis vc-path Syntax Release Information Description Options show virtual-chassis vc-path source-interface interface-name destination-interface interface-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Show the path a packet takes when going from a source interface to a destination interface in a Virtual Chassis configuration. source-interface interface-name —Name of the interface from which the packet originates destination-interface interface-name —Name of the interface to which the packet is delivered Required Privilege Level Related Documentation List of Sample Output Output Fields view • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Understanding Virtual Chassis Configuration on page 704 show virtual-chassis vc-path source-interface destination-interface on page 849 Table 114 on page 849 lists the output fields for the show virtual-chassis vc-path command. Output fields are listed in the approximate order in which they appear. Table 114: show virtual-chassis vc-path Output Fields Field Name Field Description Hop The number of hops between the source and destination interfaces. Member The Virtual Chassis ID of the member switch that contains the Packet Forwarding Engine for each intermediate hop. PFE-Device The number of the Packet Forwarding Engine in each Virtual Chassis member through which a packet passes. Each Packet Forwarding Engine is the next hop of the preceding Packet Forwarding Engine. Interface The name of the interface through which the Packet Forwarding Engines are connected. The interface for the first hop is always the source interface and the interface for the last hop is always the destination interface. For intermediate hops, the Interface field denotes the Packet Forwarding Engines through which the packet passes on its way to the next hop. show virtual-chassis vc-path source-interface destination-interface user@switch> show virtual-chassis vc-path source-interface ge-0/0/0 destination-interface ge-1/0/1 vc-path from ge-0/0/0 to ge-1/0/1 Hop Member PFE-Device Interface 0 0 1 ge-0/0/0 1 0 0 internal-1/24 849 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2 3 850 1 1 3 4 vcp-0 ge-1/0/1 Chapter 49: Operational Mode Commands for Virtual Chassis show virtual-chassis vc-port Syntax Release Information Description Options show virtual-chassis vc-port <(all-members | member member-id)> Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the status of the Virtual Chassis ports (VCPs), including both the dedicated VCPs and the uplink module ports configured as VCPs. none—Display the operational status of all the VCPs of the member switch where the command is issued. all-members—(Optional) Display the operational status of all the VCPs on all members of the Virtual Chassis configuration. member member-id—(Optional) Display the operational status of all the VCPs for the specified member of the Virtual Chassis configuration. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show virtual-chassis vc-port statistics on page 854 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 • Understanding Virtual Chassis Configuration on page 704 show virtual-chassis vc-port on page 852 show virtual-chassis vc-port all-members on page 852 Table 115 on page 851 lists the output fields for the show virtual-chassis vc-port command. Output fields are listed in the approximate order in which they appear. Table 115: show virtual-chassis vc-port Output Fields Field Name Field Description fpcnumber The FPC number is the same as the member ID. Interface or PIC/Port VCP interface name. Unlike network interface names, a VCP interface name does not include a slot number (member ID). • The dedicated VCPs are vcp-0 and vcp-1. • The uplink module ports set as VCPs are named 1/0 and 1/1, representing the PIC number and the port number. 851 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 115: show virtual-chassis vc-port Output Fields (continued) Field Name Field Description Type Type of VCP: • Dedicated (on the rear panel) • Configured (uplink module port configured as a VCP) • Auto-Configured (uplink module port autoconfigured as a VCP) See “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792 for information about configuring VCPs. Trunk ID A positive-number ID assigned to a LAG formed by the Virtual Chassis. The trunk ID value is –1 if no trunk is formed. A LAG between uplink VCPs requires that the link speed be the same on connected interfaces and that at least two VCPs on one member be connected to at least two VCPs on the other member. Dedicated VCP LAGs are assigned trunk IDs 1 and 2. Trunk IDs for LAGs formed with uplink VCPs therefore have values of 3 or greater. The trunk ID value changes if the link-adjacency state between LAG members changes; trunk membership is then allocated or deallocated. Status Interface status: down or up. Speed (mbps) Speed of the interface in megabits per second. Neighbor ID/Interface The Virtual Chassis member ID and interface of a VCP on a member switch that is connected to the interface or PIC/Port field in the same row as this interface. show virtual-chassis vc-port user@switch> show virtual-chassis vc-port fpc0: -------------------------------------------------------------------------– Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 1 vcp-1 vcp-1 Dedicated 2 Up 32000 0 vcp-0 1/0 Auto-Configured 3 Up 1000 2 vcp-255/1/0 1/0 Auto-Configured 3 Up 1000 2 vcp-255/1/1 show virtual-chassis vc-port all-members user@switch> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 1 vcp-1 vcp-1 Dedicated 2 Up 32000 0 vcp-0 1/0 Auto-Configured 3 Up 1000 2 vcp-255/1/0 1/1 Auto-Configured 3 Up 1000 2 vcp-255/1/1 fpc1: 852 Chapter 49: Operational Mode Commands for Virtual Chassis -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 0 vcp-1 vcp-1 Dedicated 2 Up 32000 0 vcp-0 1/0 Auto-Configured —1 Up 1000 3 vcp-255/1/0 fpc2: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 3 vcp-1 vcp-1 Dedicated 2 Up 32000 3 vcp-0 1/0 Auto-Configured 3 Up 1000 0 vcp-255/1/0 1/1 Auto-Configured 3 Up 1000 0 vcp-255/1/1 fpc3: -------------------------------------------------------------------------Interface Type Trunk Status Speed Neighbor or ID (mbps) ID Interface PIC / Port vcp-0 Dedicated 1 Up 32000 2 vcp-0 vcp-1 Dedicated 2 Up 32000 2 vcp-1 1/0 Auto-Configured —1 Up 1000 1 vcp-255/1/0 853 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show virtual-chassis vc-port statistics Syntax Release Information Description Options show virtual-chassis vc-port statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the traffic statistics collected on Virtual Chassis ports (VCPs). none—Display traffic statistics for the VCPs of all members of a Virtual Chassis configuration. brief | detail | extensive—(Optional) Display the specified level of output. Using the brief option is equivalent to entering the command with no options (the default). The detail and extensive options provide identical displays. all-members—(Optional) Display traffic statistics for the VCPs of all members of a Virtual Chassis configuration. interface-name—(Optional) Name of the VCP interface for which to display traffic statistics. Specify either vcp-0 or vcp-1 or an internal port in the VCP subsystem—for example, internal-0/24. local—(Optional) Display VCP traffic statistics for only the switch on which this command is entered. member member-id—(Optional) Display VCP traffic statistics for only the specified member of a Virtual Chassis configuration. Required Privilege Level Related Documentation List of Sample Output Output Fields 854 view • clear virtual-chassis vc-port statistics on page 836 • show virtual-chassis vc-port on page 851 • Monitoring Virtual Chassis Configuration Status and Statistics on page 809 show virtual-chassis vc-port statistics on page 857 show virtual-chassis vc-port statistics brief on page 857 show virtual-chassis vc-port statistics extensive on page 857 show virtual-chassis vc-port statistics member 0 on page 858 Table 116 on page 855 lists the output fields for the show virtual-chassis vc-port statistics command. Output fields are listed in the approximate order in which they appear. Chapter 49: Operational Mode Commands for Virtual Chassis Table 116: show virtual-chassis vc-port statistics Output Fields Field Name Field Description Level of Output fpcnumber ID of the Virtual Chassis member. The FPC number is the same as the member ID. All levels Interface VCP interface name. Unlike network interface names, a VCP interface does not include a slot number (member ID). brief • The dedicated VCPs are vcp-0 and vcp-1. • Ports internal to the VCP subsystem have names corresponding to the PIC and port number. For example, 0/24 indicates internal onboard port 24, and 1/26 indicates internal uplink module port 26. Input Octets/Packets Total number of octets and packets received on the VCP interface. brief member none Output Octets/Packets Total number of octets and packets transmitted on the VCP interface. brief member none master: number Member ID of the Virtual Chassis master. All levels Port VCP for which RX (Receive) statistics,TX (Transmit) statistics, or both are reported by the VCP subsystem during a sampling interval—since the statistics counter was last cleared. detail extensive Total octets Total number of octets received and transmitted on the VCP interface. detail extensive Total packets Total number of packets received and transmitted on the VCP interface. detail extensive Unicast packets Number of unicast packets received and transmitted on the VCP interface. detail extensive Broadcast packets Number of broadcast packets received and transmitted on the VCP interface. detail extensive Multicast packets Number of multicast packets received and transmitted on the VCP interface. detail extensive MAC control frames Number of media access control (MAC) control frames received and transmitted on the VCP interface. detail extensive CRC alignment errors Number of packets received on the VCP interface that had a length—excluding framing bits, but including frame check sequence (FCS) octets—of between 64 and 1518 octets, inclusive, and had one of the following errors: detail extensive • Invalid FCS with an integral number of octets (FCS error) • Invalid FCS with a nonintegral number of octets (alignment error) Oversize packets Number of packets received on the VCP interface that were longer than 1518 octets (excluding framing bits, but including FCS octets) but were otherwise well formed. detail extensive Undersize packets Number of packets received on the VCP interface that were shorter than 64 octets (excluding framing bits but including FCS octets) and were otherwise well formed.. detail extensive 855 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 116: show virtual-chassis vc-port statistics Output Fields (continued) Field Name Field Description Level of Output Jabber packets Number of packets received on the VCP interface that were longer than 1518 octets—excluding framing bits, but including FCS octets—and that had either an FCS error or an alignment error. detail extensive NOTE: This definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5 (10Base5) and section 10.3.1.4 (10Base2). These documents define jabber as the condition in which any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms. Fragments received Number of packets received on the VCP interface that were shorter than 64 octets (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. detail extensive Fragment frames normally increment because both runts (which are normal occurrences caused by collisions) and noise hits are counted. Ifout errors Number of outbound packets received on the VCP interface that could not be transmitted because of errors. detail extensive Packet drop events Number of outbound packets received on the VCP interface that were dropped, rather than being encapsulated and sent out of the switch as fragments. The packet drop counter is incremented if a temporary shortage of packet memory causes packet fragmentation to fail. detail extensive 64 octets frames Number of packets received on the VCP interface (including invalid packets) that were 64 octets in length (excluding framing bits, but including FCS octets). detail extensive 65–127 octets frames Number of packets received on the VCP interface (including invalid packets) that were between 65 and 127 octets in length, inclusive (excluding framing bits, but including FCS octets). detail extensive 128–255 octets frames Number of packets received on the VCP interface (including invalid packets) that were between 128 and 255 octets in length, inclusive (excluding framing bits, but including FCS octets). detail extensive 256–511 octets frames Number of packets received on the VCP interface (including invalid packets) that were between 256 and 511 octets in length, inclusive (excluding framing bits, but including FCS octets). detail extensive 512–1023 octets frames Number of packets received on the VCP interface (including invalid packets) that were between 512 and 1023 octets in length, inclusive (excluding framing bits, but including FCS octets). detail extensive 1024–1518 octets frames Number of packets received on the VCP interface (including invalid packets) that were between 1024 and 1518 octets in length, inclusive (excluding framing bits, but including FCS octets). detail extensive Rate packets per second Number of packets per second received and transmitted on the VCP interface. detail extensive Rate bytes per second Number of bytes per second received and transmitted on the VCP interface. detail extensive 856 Chapter 49: Operational Mode Commands for Virtual Chassis show virtual-chassis vc-port statistics user@SWA-0> show virtual-chassis vc-port statistics fpc0: -------------------------------------------------------------------------Interface Input Octets/Packets Output Octets/Packets internal-0/24 0 / 0 0 / 0 internal-0/25 0 / 0 0 / 0 internal-1/26 0 / 0 0 / 0 internal-1/27 0 / 0 0 / 0 vcp-0 0 / 0 0 / 0 vcp-1 0 / 0 0 / 0 internal-0/26 0 / 0 0 / 0 internal-0/27 0 / 0 0 / 0 internal-1/24 0 / 0 0 / 0 internal-1/25 0 / 0 0 / 0 {master:0} show virtual-chassis vc-port statistics brief user@SWA-0> show virtual-chassis vc-port statistics brief fpc0: -------------------------------------------------------------------------Interface Input Octets/Packets Output Octets/Packets internal-0/24 0 / 0 0 / 0 internal-0/25 0 / 0 0 / 0 internal-1/26 0 / 0 0 / 0 internal-1/27 0 / 0 0 / 0 vcp-0 0 / 0 0 / 0 vcp-1 0 / 0 0 / 0 internal-0/26 0 / 0 0 / 0 internal-0/27 0 / 0 0 / 0 internal-1/24 0 / 0 0 / 0 internal-1/25 0 / 0 0 / 0 {master:0} show virtual-chassis vc-port statistics extensive user@SWA-0> show virtual-chassis vc-port statistics extensive fpc0: -------------------------------------------------------------------------- Port: internal-0/24 Total octets: Total packets: Unicast packets: Broadcast packets: Multicast packets: MAC control frames: CRC alignment errors: Oversize packets: Undersize packets: Jabber packets: Fragments received: Ifout errors: Packet drop events: 64 octets frames: 65-127 octets frames: 128-255 octets frames: 256-511 octets frames: 512-1023 octets frames: 1024-1518 octets frames: RX TX 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 857 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Rate packets per second: Rate bytes per second: 0 0 0 0 Port: vcp-0 Total octets: Total packets: Unicast packets: Broadcast packets: Multicast packets: MAC control frames: CRC alignment errors: Oversize packets: Undersize packets: Jabber packets: Fragments received: Ifout errors: Packet drop events: 64 octets frames: 65-127 octets frames: 128-255 octets frames: 256-511 octets frames: 512-1023 octets frames: 1024-1518 octets frames: Rate packets per second: Rate bytes per second: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Port: vcp-1 Total octets: Total packets: Unicast packets: Broadcast packets: Multicast packets: MAC control frames: CRC alignment errors: Oversize packets: Undersize packets: Jabber packets: Fragments received: Ifout errors: Packet drop events: 64 octets frames: 65-127 octets frames: 128-255 octets frames: 256-511 octets frames: 512-1023 octets frames: 1024-1518 octets frames: Rate packets per second: Rate bytes per second: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ... 0 0 0 0 ... {master:0} show virtual-chassis vc-port statistics member 0 858 user@SWA-0>show virtual-chassis vc-port statistics member 0 fpc0: -------------------------------------------------------------------------Interface Input Octets/Packets Output Octets/Packets internal-0/24 0 / 0 0 / 0 internal-0/25 0 / 0 0 / 0 Chapter 49: Operational Mode Commands for Virtual Chassis internal-1/26 internal-1/27 vcp-0 vcp-1 internal-0/26 internal-0/27 internal-1/24 internal-1/25 0 0 0 0 0 0 0 0 / / / / / / / / 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 / / / / / / / / 0 0 0 0 0 0 0 0 {master:0} 859 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 860 PART 12 Interfaces on J-EX Series Switches • Interfaces—Overview on page 863 • Examples: Interfaces Configuration on page 881 • Configuring Interfaces on page 909 • Verifying Interfaces on page 931 • Troubleshooting Interfaces on page 939 • Configuration Statements for Interfaces on page 943 • Operational Mode Commands for Interfaces on page 989 861 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 862 CHAPTER 50 Interfaces—Overview • J-EX Series Switches Interfaces Overview on page 863 • Understanding Interface Naming Conventions on J-EX Series Switches on page 865 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Understanding Interface Ranges on J-EX Series Switches on page 869 • Understanding Layer 3 Subinterfaces on page 871 • Understanding Unicast RPF for J-EX Series Switches on page 872 • Understanding IP Directed Broadcast for J-EX Series Switches on page 876 • High Availability Features for J-EX Series Switches Overview on page 877 J-EX Series Switches Interfaces Overview J-EX Series Switches have two types of interfaces: network interfaces and special interfaces. This topic provides brief information on these interfaces. For additional information, see the Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/. For information on interface-naming conventions on J-EX Series Switches, see “Understanding Interface Naming Conventions on J-EX Series Switches” on page 865. This topic describes: • Network Interfaces on page 863 • Special Interfaces on page 864 Network Interfaces Network interfaces connect to the network and carry network traffic. Table 117 on page 863 lists the types of network interfaces supported on J-EX Series switches. Table 117: Network Interface Types and Purposes Type Purpose Aggregated Ethernet interfaces All J-EX Series switches allow you to group Ethernet interfaces at the physical layer to form a single link layer interface, also known as a link aggregation group (LAG) or bundle. These aggregated Ethernet interfaces help to balance traffic and increase the uplink bandwidth. 863 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 117: Network Interface Types and Purposes (continued) Type Purpose LAN access interfaces Use these J-EX Series switch interfaces to connect a personal computer, laptop, file server, or printer to the network. When you power on a J-EX Series switch and use the factory-default configuration, the software automatically configures interfaces in access mode for each of the network ports. The default configuration also enables autonegotiation for both speed and link mode. Power over Ethernet (PoE) interfaces J-EX Series switches provide PoE network ports with various switch models. These ports can be used to connect voice over IP (VoIP) telephones, wireless access points, video cameras, and point-of-sale devices to safely receive power from the same access ports that are used to connect personal computers to the network. PoE interfaces are enabled by default in the factory configuration. Trunk interfaces J-EX Series access switches can be connected to a distribution switch or customer-edge (CE) switches or routers. To use a port for this type of connection, you must explicitly configure the port interface for trunk mode. The interfaces from the distribution switch or CE switch to the access switches must also be configured for trunk mode. Special Interfaces Table 118 on page 864 lists the types of special interfaces supported on J-EX Series switches. Table 118: Special Interface Types and Purposes Type Purpose Console port Each J-EX Series switch has a serial port, labeled CON or CONSOLE, for connecting tty-type terminals to the switch using standard PC-type tty cables. The console port does not have a physical address or IP address associated with it. However, it is an interface in the sense that it provides access to the switch. On J-EX4200 switches that are configured as a Virtual Chassis, you can access the master and configure all members of the Virtual Chassis through any member's console port. For more information on the console port in a Virtual Chassis, see “Understanding Global Management of a Virtual Chassis Configuration” on page 699. Loopback All J-EX Series switches have this software-only virtual interface that is always up. The loopback interface provides a stable and consistent interface and IP address on the switch. Management interface The Junos OS for J-EX Series switches automatically creates the switch's management Ethernet interface, me0. The management Ethernet interface provides an out-of-band method for connecting to the switch. To use me0 as a management port, you must configure its logical port, me0.0, with a valid IP address. You can connect to the management interface over the network using utilities such as SSH or Telnet. SNMP can use the management interface to gather statistics from the switch. (The management interface me0 is analogous to the fxp0 interfaces on routers running the Junos OS.) Routed VLAN Interface (RVI) J-EX Series switches use a Layer 3 routed VLAN interface (RVI) named vlan to route traffic from one broadcast domain to another and to perform other Layer 3 functions such as traffic engineering. These functions are typically performed by a router interface in a traditional network. The RVI functions as a logical router, eliminating the need for having both a switch and a router. The RVI (the vlan interface) must be configured as part of a broadcast domain or virtual private LAN service (VPLS) routing instance for Layer 3 traffic to be routed out of it. 864 Chapter 50: Interfaces—Overview Table 118: Special Interface Types and Purposes (continued) Type Purpose Virtual Chassis port (VCP) interfaces Each J-EX4200 switch has two dedicated Virtual Chassis ports (VCPs) on its rear panel. These ports can be used to interconnect two to ten J-EX4200 switches as a Virtual Chassis, which functions as a single network entity. See “Understanding the High-Speed Interconnection of the Virtual Chassis Members” on page 702. When you power on J-EX Series switches that are interconnected in this manner, the software automatically configures the VCP interfaces for the dedicated ports that have been interconnected. These VCP interfaces are not configurable or modifiable. You can also interconnect J-EX4200 switches across distances of up to 25 miles (40 km) by using the SFP or SFP+ uplink module ports. To do so, you must explicitly set the uplink module ports on the members you want to connect as VCPs. See “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792. When you set the uplink module ports as uplink VCPs and connect member switches through those uplink VCPs, a LAG is automatically formed when the link speed is the same on connected VCPs and at least two VCPs on one member are connected to at least two VCPs on another member. See “Understanding Virtual Chassis Configurations and Link Aggregation” on page 702. Virtual management Ethernet (VME) interface J-EX4200 switches have a VME interface. This is a logical interface that is used for Virtual Chassis configurations and allows you to manage all the members of the Virtual Chassis through the master. For more information on the VME interface, see “Understanding Global Management of a Virtual Chassis Configuration” on page 699. Related Documentation • J-EX4200 Switches Hardware Overview on page 25 • J-EX8208 Switch Hardware Overview on page 27 • J-EX8216 Switch Hardware Overview on page 30 • PoE and J-EX Series Switches Overview on page 3009 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Understanding Layer 3 Subinterfaces on page 871 Understanding Interface Naming Conventions on J-EX Series Switches J-EX Series Switches use a naming convention for defining the interfaces that is similar to that of other platforms running under the Junos OS. This topic provides brief information on the naming conventions used for interfaces on J-EX Series switches. For additional information, see the Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/. This topic describes: • Physical Part of an Interface Name on page 865 • Logical Part of an Interface Name on page 866 • Wildcard Characters in Interface Names on page 867 Physical Part of an Interface Name Interfaces in Junos OS are specified as follows: type-fpc / pic / port 865 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS J-EX Series switches apply this convention as follows: • • • • type—J-EX Series interfaces use the following media types: • ge—Gigabit Ethernet interface • xe—10 Gigabit Ethernet interface • fe—Fast Ethernet interface fpc—Flexible PIC Concentrator. J-EX Series interfaces use the following convention for the FPC number in interface names: • On J-EX4200 standalone switches, FPC refers to the switch itself. The FPC number is always 0 on these switches. • On J-EX4200 switches configured in a Virtual Chassis, the FPC number indicates the member ID of the switch within the Virtual Chassis, from 0 through 9. • On J-EX8200 switches, the FPC number indicates the slot number of the line card that contains the physical interface. pic—J-EX Series interfaces use the following convention for the PIC (Physical Interface Card) number in interface names: • On J-EX4200 switches, the PIC number is 0 for all built-in interfaces (interfaces that are not an uplink port) and 1 for uplink ports. • On J-EX8200 switches, the PIC number is always 0. port—J-EX Series interfaces use the following convention for port numbers: • On J-EX4200 switches, built-in network ports are numbered from left to right. On models that have two rows of ports, the ports on the top row start with 0 followed by the remaining even-numbered ports, and the ports on the bottom row start with 1 followed by the remaining odd-numbered ports. • Uplink ports in J-EX4200 switches are labeled from left to right, starting with 0. • On J-EX8200 switches, the network ports are numbered from left to right on each line card. On line cards that have two rows of ports, the ports on the top row start with 0 followed by the remaining even-numbered ports, and the ports on the bottom row start with 1 followed by the remaining odd-numbered ports. Logical Part of an Interface Name The logical unit part of the interface name corresponds to the logical unit number, which can be a number from 0 through 16384. In the virtual part of the name, a period (.) separates the port and logical unit numbers: type-fpc/pic/port.logical-unit-number. For example, if you issue the show ethernet-switching interfaces command on a system with a default VLAN, the resulting display shows the logical interfaces associated with the VLAN: Interface ge-0/0/0.0 866 State down VLAN members remote-analyzer Blocking unblocked Chapter 50: Interfaces—Overview ge-0/0/1.0 down ge-0/0/10.0 down default default unblocked unblocked When you configure aggregated Ethernet interfaces, you configure a logical interface that is called a bundle or a LAG. Each LAG can include up to 8 or 12 Ethernet interfaces, depending on the switch model. Wildcard Characters in Interface Names In the show interfaces and clear interfaces commands, you can use wildcard characters in the interface-name option to specify groups of interface names without having to type each name individually. You must enclose all wildcard characters except the asterisk (*) in quotation marks (" "). Related Documentation • J-EX Series Switches Interfaces Overview on page 863 • Front Panel of a J-EX4200 Switch • Slot Numbering for a J-EX8208 Switch • Slot Numbering for a J-EX8216 Switch Understanding Aggregated Ethernet Interfaces and LACP IEEE 802.3ad link aggregation enables you to group Ethernet interfaces to form a single link layer interface, also known as a link aggregation group (LAG) or bundle. Aggregating multiple links between physical interfaces creates a single logical point-to-point trunk link or a LAG. The LAG balances traffic across the member links within an aggregated Ethernet bundle and effectively increases the uplink bandwidth. Another advantage of link aggregation is increased availability, because the LAG is composed of multiple member links. If one member link fails, the LAG continues to carry traffic over the remaining links. Link Aggregation Control Protocol (LACP), a component of IEEE 802.3ad, provides additional functionality for LAGs. This topic describes: • Link Aggregation Group (LAG) on page 867 • Link Aggregation Control Protocol (LACP) on page 868 Link Aggregation Group (LAG) You configure a LAG by specifying the link number as a physical device and then associating a set of interfaces (ports) with the link. All the interfaces must have the same speed and be in full-duplex mode. The Junos OS for J-EX Series Switches assigns a unique ID and port priority to each interface. The ID and priority are not configurable. The number of interfaces that can be grouped into a LAG and the total number of LAGs supported on a switch varies according to switch model. Table 119 on page 868 lists the J-EX Series switches and the maximum number of interfaces per LAG and maximum number of LAGs they support. 867 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 119: Maximum Interfaces per LAG and Maximum LAGs per Switch Switch Model Maximum Interfaces per LAG Maximum LAGs J-EX4200 8 64 J-EX8200 12 255 When configuring LAGs, consider the following guidelines: • The LAG must be configured on both sides of the link. • The interfaces on either side of the link must be set to the same speed. • You can configure and apply firewall filters on a LAG. • LACP can optionally be configured for link negotiation. You can combine physical Ethernet ports belonging to different member switches of a Virtual Chassis configuration to form a LAG. See “Understanding Virtual Chassis Configurations and Link Aggregation” on page 702. NOTE: The interfaces that are included within a bundle or LAG are sometimes referred to as member interfaces. Do not confuse this term with member switches, which refers to J-EX4200 Ethernet Switches that are interconnected as a Virtual Chassis. It is possible to create a LAG that is composed of member interfaces that are located in different member switches of a Virtual Chassis. A LAG creates a single logical point-to-point connection. A typical deployment for a LAG would be to aggregate trunk links between an access switch and a distribution switch or customer edge (CE) router. Link Aggregation Control Protocol (LACP) When LACP is configured, it detects misconfigurations on the local end or the remote end of the link. About enabling LACP: • When LACP is not enabled, a local LAG might attempt to transmit packets to a remote single interface, which causes the communication to fail. • When LACP is enabled, a local LAG cannot transmit packets unless a LAG with LACP is also configured on the remote end of the link. By default, Ethernet links do not exchange protocol data units (PDUs), which contain information about the state of the link. You can configure Ethernet links to actively transmit PDUs, or you can configure the links to passively transmit them, sending out LACP PDUs only when they receive them from another link. The transmitting link is known as the actor and the receiving link is known as the partner. 868 Chapter 50: Interfaces—Overview In a scenario where a dual-homed server is deployed with a switch, the network interface cards form a LAG with the switch. During a server upgrade, the server may not be able to exchange LACP PDUs. In such a situation you can configure an interface to be in the UP state even if no PDUs are exchanged. Use the force-up statement to configure an interface when the peer has limited LACP capability. The interface selects the associated LAG by default, whether the switch and peer are both in active or passive mode. When there are no received PDUs, the partner is considered to be working in the passive mode. Therefore, LACP PDU transmissions are controlled by the transmitting link. If the remote end of the LAG link is a security device, LACP might not be supported because security devices require a deterministic configuration. In this case, do not configure LACP. All links in the LAG are permanently operational unless the switch detects a link failure within the Ethernet physical layer or data link layers. Related Documentation • Understanding Virtual Chassis Configurations and Link Aggregation on page 702 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ Understanding Interface Ranges on J-EX Series Switches You can use the interface ranges to group interfaces of the same type that share a common configuration profile. This helps reduce the time and effort in configuring interfaces on J-EX Series switches. The configurations common to all the interfaces can be included in the interface range definition. The interface range definition contains the name of the interface range defined, the names of the individual member interfaces that do not fall in a series of interfaces, a range of interfaces defined in the member range, and the configuration statements common to all the interfaces. An interface range defined with member ranges and individual members but without any common configurations, is also a valid definition. NOTE: The interface range definition is supported only for Gigabit, 10-Gigabit, and Fast Ethernet interfaces. The common configurations defined in the interface range will be overridden by the local configuration. The defined interface ranges can be used at places where the interface node is used in the following configuration hierarchies: 869 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 870 • ethernet-switching-options analyzer name input egress interface • ethernet-switching-options analyzer name input ingress interface • ethernet-switching-options analyzer output interface • ethernet-switching-options bpdu-block interface • ethernet-switching-options interfaces • ethernet-switching-options redundant-trunk-group group-name interface • ethernet-switching-options secure-access-port interface • ethernet-switching-options voip interface • poe interface • protocols dot1x authentication interface • protocols gvrp interface • protocols igmp interface • protocols igmp-snooping vlan vlan-name interface • protocols isis interface • protocols link-management peer lmp-control-channel interface • protocols link-management te-link name interface • protocols lldp interface • protocols lldp-med interface • protocols mpls interface • protocols mstp interface • protocols mstp msti-id interface • protocols mstp msti-id vlan vlan-id interface • protocols oam ethernet link-fault-management interface • protocols ospf area • protocols pim interface • protocols rip group group-name neighbor • protocols ripng group group-name neighbor • protocols router-advertisement interface • protocols router-discovery interface • protocols rsvp interface • protocols sflow interfaces • protocols stp interface Chapter 50: Interfaces—Overview Related Documentation • protocols vstp vlan vlan-id interface • vlans vlan-name interface • J-EX Series Switches Interfaces Overview on page 863 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ • interface-range on page 962 Understanding Layer 3 Subinterfaces A Layer 3 subinterface is a logical division of a physical interface that operates at the network level and therefore can receive and forward 802.1Q VLAN tags. You can use Layer 3 subinterfaces to route traffic among multiple VLANs along a single trunk line that connects a J-EX Series Switch to a Layer 2 switch. Only one physical connection is required between the switches. This topology is often called a “router on a stick” or a “one-armed router” when the Layer 3 device is a router. To create Layer 3 subinterfaces on a J-EX Series switch, you enable VLAN tagging, partition the physical interface into logical partitions, and bind the VLAN ID to the logical interface. You can partition one physical interface into up to 4094 different subinterfaces, one for each VLAN. We recommend that you use the VLAN ID as the subinterface number when you configure the subinterface. The Junos OS reserves VLAN IDs 0 and 4095. VLAN tagging places the VLAN ID in the frame header, allowing each physical interface to handle multiple VLANs. When you configure multiple VLANs on an interface, you must also enable tagging on that interface. Junos OS on J-EX Series switches supports a subset of the 802.1Q standard for receiving and forwarding routed or bridged Ethernet frames with single VLAN tags and running Virtual Router Redundancy Protocol (VRRP) over 802.1Q-tagged interfaces. Double-tagging is not supported. Related Documentation • J-EX Series Switches Interfaces Overview on page 863 • Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch on page 893 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 871 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Unicast RPF for J-EX Series Switches Unicast reverse-path forwarding (RPF) helps protect the switch against denial-of-service (DoS) and distributed denial-of-service (DDoS) attacks by verifying the unicast source address of each packet that arrives on an ingress interface where unicast RPF is enabled. It also helps ensure that traffic arriving on ingress interfaces comes from a network source that the receiving interface can reach. When you enable unicast RPF, the switch forwards a packet only if the receiving interface is the best return path to the packet's unicast source address. This is known as strict mode unicast RPF. NOTE: On J-EX4200 Ethernet Switches, the switch applies unicast RPF globally to all interfaces when unicast RPF is configured on any interface. For additional information, see “Limitations of the Unicast RPF Implementation on J-EX4200 Switches” on page 875. This topic covers: • Unicast RPF for J-EX Series Switches Overview on page 872 • Unicast RPF Implementation for J-EX Series Switches on page 873 • When to Enable Unicast RPF on page 873 • When Not to Enable Unicast RPF on page 874 • Limitations of the Unicast RPF Implementation on J-EX4200 Switches on page 875 Unicast RPF for J-EX Series Switches Overview Unicast RPF functions as an ingress filter that reduces the forwarding of IP packets that might be spoofing an address. By default, unicast RPF is disabled on the switch interfaces. The type of unicast RPF provided on the switches—that is, strict mode unicast RPF is especially useful on untrusted interfaces. An untrusted interface is an interface where untrusted users or processes can place packets on the network segment. The switch supports only the active paths method of determining the best return path back to a unicast source address. The active paths method looks up the best reverse path entry in the forwarding table. It does not consider alternate routes specified using routing-protocol-specific methods when determining the best return path. If the forwarding table lists the receiving interface as the interface to use to forward the packet back to its unicast source, it is the best return path interface. Strict mode unicast RPF recognizes only one best return path to a unicast source address. Use strict mode unicast RPF only on symmetrically routed interfaces. (For information about symmetrically routed interfaces, see “When to Enable Unicast RPF” on page 873.) For more information about strict unicast RPF, see RFC 3704, Ingress Filtering for Multihomed Networks at http://www.ietf.org/rfc/rfc3704.txt. 872 Chapter 50: Interfaces—Overview Unicast RPF Implementation for J-EX Series Switches This section includes: • Unicast RPF Packet Filtering on page 873 • Bootstrap Protocol (BOOTP) and DHCP Requests on page 873 • Default Route Handling on page 873 Unicast RPF Packet Filtering When you enable unicast RPF on the switch, the switch handles traffic in the following manner: • If the switch receives a packet on the interface that is the best return path to the unicast source address of that packet, the switch forwards the packet. • If the best return path from the switch to the packet's unicast source address is not the receiving interface, the switch discards the packet. • If the switch receives a packet that has a source IP address that does not have a routing entry in the forwarding table, the switch discards the packet. Bootstrap Protocol (BOOTP) and DHCP Requests Bootstrap protocol (BOOTP) and DHCP request packets are sent with a broadcast MAC address and therefore the switch does not perform unicast RPF checks on them. The switch forwards all BOOTP packets and DHCP request packets without performing unicast RPF checks. Default Route Handling If the best return path to the source is the default route (0.0.0.0) and the default route points to reject, the switch discards all unicast RPF packets. If the default route points to a valid network interface, the switch performs a normal unicast RPF check on the packets. When to Enable Unicast RPF Enable unicast RPF when you want to ensure that traffic arriving on a network interface comes from a source that resides on a network that that interface can reach. You can enable unicast RPF on untrusted interfaces to filter spoofed packets. For example, a common application for unicast RPF is to help defend an enterprise network from DoS/DDoS attacks coming from the Internet. Enable unicast RPF only on symmetrically routed interfaces. A symmetrically routed interface uses the same route in both directions between the source and the destination, as shown in Figure 22 on page 874. Symmetrical routing means that if an interface receives a packet, the switch uses the same interface to send a reply to the packet source (the receiving interface matches the forwarding-table entry for the best return path to the source). 873 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 22: Symmetrically Routed Interfaces Enabling unicast RPF on asymmetrically routed interfaces (where different interfaces receive a packet and reply to its source) results in packets from legitimate sources being filtered (discarded) because the best return path is not the same interface that received the packet. The following switch interfaces are most likely to be symmetrically routed and thus are candidates for unicast RPF enabling: • The service provider edge to a customer • The customer edge to a service provider • A single access point out of the network (usually on the network perimeter) • A terminal network that has only one link NOTE: Because unicast RPF is enabled globally on J-EX4200 switches, ensure that all interfaces are symmetrically routed before you enable unicast RPF on those switches. Enabling unicast RPF on asymmetrically routed interfaces results in packets from legitimate sources being filtered. TIP: Enabling unicast RPF as close as possible to the traffic source stops spoofed traffic before it can proliferate or reach interfaces that do not have unicast RPF enabled. When Not to Enable Unicast RPF Typically, you will not enable unicast RPF if: • Switch interfaces are multihomed. • Switch interfaces are trusted interfaces. • BGP is carrying prefixes and some of those prefixes are not advertised or are not accepted by the ISP under its policy. (The effect in this case is the same as filtering an interface by using an incomplete access list.) • Switch interfaces face the network core. Core-facing interfaces are usually asymmetrically routed. An asymmetrically routed interface uses different paths to send and receive packets between the source and the destination, as shown in Figure 23 on page 875. This means that if an interface receives a packet, that interface does not match the forwarding table 874 Chapter 50: Interfaces—Overview entry as the best return path back to the source. If the receiving interface is not the best return path to the source of a packet, unicast RPF causes the switch to discard the packet even though it comes from a valid source. Figure 23: Asymmetrically Routed Interfaces NOTE: Do not enable unicast RPF on J-EX4200 switches if any switch interfaces are asymmetrically routed, because unicast RPF is enabled globally on all interfaces of those switches. All switch interfaces must be symmetrically routed for you to enable unicast RPF without the risk of the switch discarding traffic that you want to forward. Limitations of the Unicast RPF Implementation on J-EX4200 Switches On J-EX4200 switches, the switch implements unicast RPF on a global basis. You cannot enable unicast RPF on a per-interface basis. Unicast RPF is globally disabled by default. • When you enable unicast RPF on any interface, it is automatically enabled on all switch interfaces, including link aggregation groups (LAGs) and routed VLAN interfaces (RVIs). • When you disable unicast RPF on the interface (or interfaces) on which you enabled unicast RPF, it is automatically disabled on all switch interfaces. NOTE: You must explicitly disable unicast RPF on every interface on which it was explicitly enabled or unicast RPF remains enabled on all switch interfaces. The J-EX4200 switches do not perform unicast RPF filtering on equal-cost multipath (ECMP) traffic. The unicast RPF check examines only one best return path to the packet source, but ECMP traffic employs an address block consisting of multiple paths. Using unicast RPF to filter ECMP traffic on J-EX4200 switches can result in the switch discarding packets that you want to forward because the unicast RPF filter does not examine the entire ECMP address block. Related Documentation • Example: Configuring Unicast RPF on a J-EX Series Switch on page 900 • Configuring Unicast RPF (CLI Procedure) on page 927 • Disabling Unicast RPF (CLI Procedure) on page 928 875 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding IP Directed Broadcast for J-EX Series Switches IP directed broadcast helps you implement remote administration tasks such as backups and wake-on-LAN (WOL) application tasks by sending broadcast packets targeted at the hosts in a specified destination subnet. IP directed broadcast packets traverse the network in the same way as unicast IP packets until they reach the destination subnet. When they reach the destination subnet and IP directed broadcast is enabled on the receiving switch, the switch translates (“explodes”) the IP directed broadcast packet into a broadcast that floods the packet on the target subnet. All hosts on the target subnet receive the IP directed broadcast packet. This topic covers: • IP Directed Broadcast for J-EX Series Switches Overview on page 876 • IP Directed Broadcast Implementation for J-EX Series Switches on page 876 • When to Enable IP Directed Broadcast on page 877 • When Not to Enable IP Directed Broadcast on page 877 IP Directed Broadcast for J-EX Series Switches Overview IP directed broadcast packets have a destination IP address that is a valid broadcast address for the subnet that is the target of the directed broadcast (the target subnet). The intent of an IP directed broadcast is to flood the target subnet with the broadcast packets without broadcasting to the entire network. IP directed broadcast packets cannot originate from the target subnet. When you send an IP directed broadcast packet, as it travels to the target subnet, the network forwards it in the same way as it forwards a unicast packet. When the packet reaches a switch that is directly connected to the target subnet, the switch checks to see whether IP directed broadcast is enabled on the interface that is directly connected to the target subnet: • If IP directed broadcast is enabled on that interface, the switch broadcasts the packet on that subnet by rewriting the destination IP address as the configured broadcast IP address for the subnet. The switch converts the packet to a link-layer broadcast packet that every host on the network processes. • If IP directed broadcast is disabled on the interface that is directly connected to the target subnet, the switch drops the packet. IP Directed Broadcast Implementation for J-EX Series Switches You configure IP directed broadcast on a per-subnet basis by enabling IP directed broadcast on the Layer 3 interface of the subnet’s VLAN. When the switch that is connected to that subnet receives a packet that has the subnet’s broadcast IP address as the destination address, the switch broadcasts the packet to all hosts on the subnet. By default, IP directed broadcast is disabled. 876 Chapter 50: Interfaces—Overview When to Enable IP Directed Broadcast IP directed broadcast is disabled by default. Enable IP directed broadcast when you want to perform remote management or administration services such as backups or WOL tasks on hosts in a subnet that does not have a direct connection to the Internet. Enabling IP directed broadcast on a subnet affects only the hosts within that subnet. Only packets received on the subnet’s Layer 3 interface that have the subnet’s broadcast IP address as the destination address are flooded on the subnet. When Not to Enable IP Directed Broadcast Typically, you do not enable IP directed broadcast on subnets that have direct connections to the Internet. Disabling IP directed broadcast on a subnet’s Layer 3 interface affects only that subnet. If you disable IP directed broadcast on a subnet and a packet that has the broadcast IP address of that subnet arrives at the switch, the switch drops the broadcast packet. If a subnet has a direct connection to the Internet, enabling IP directed broadcast on it increases the network’s susceptibility to denial-of-service (DoS) attacks. For example, a malicious attacker can spoof a source IP address (use a source IP address that is not the actual source of the transmission to deceive a network into identifying the attacker as a legitimate source) and send IP directed broadcasts containing Internet Control Message Protocol (ICMP) echo (ping) packets. When the hosts on the network with IP directed broadcast enabled receive the ICMP echo packets, they all send replies to the victim that has the spoofed source IP address. This creates a flood of ping replies in a DoS attack that can overwhelm the spoofed source address; this is known as a “smurf” attack. Another common DoS attack on exposed networks with IP directed broadcast enabled is a “fraggle” attack, which is similar to a smurf attack except that the malicious packet is a User Datagram Protocol (UDP) echo packet instead of an ICMP echo packet. Related Documentation • Example: Configuring IP Directed Broadcast on a J-EX Series Switch on page 904 • Configuring IP Directed Broadcast (CLI Procedure) on page 929 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 878 • Graceful Protocol Restart on page 878 • Redundant Routing Engines on page 878 • Graceful Routing Engine Switchover on page 879 • Virtual Chassis Software Upgrade and Failover Features on page 879 • Link Aggregation on page 880 877 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 J-EX Series 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 J-EX Series 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. For more information on VRRP, see “Understanding VRRP on J-EX Series Switches” on page 1425. 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 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 J-EX Series 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 Two to ten J-EX4200 switches can be interconnected to create a Virtual Chassis configuration that operates as a single network entity. Every Virtual Chassis configuration has a master and a backup. The master acts as the master Routing Engine and the backup 878 Chapter 50: Interfaces—Overview acts as the backup Routing Engine. The Routing Engine provides the following functionality: • Runs various routing protocols • Provides the forwarding table to the Packet Forwarding Engines (PFEs) in all the member switches of the Virtual Chassis configuration • Runs other management and control processes for the entire Virtual Chassis configuration The master Routing Engine, which is in the master of the Virtual Chassis configuration, runs the Junos OS in the master role. It receives and transmits routing information, builds and maintains routing tables, communicates with interfaces and Packet Forwarding Engine components of the member switches, and has full control over the Virtual Chassis configuration. The backup Routing Engine, which is in the backup of the Virtual Chassis configuration, runs the Junos OS in the backup role. It 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. Graceful Routing Engine Switchover You can configure graceful Routing Engine switchover (GRES) in a Virtual Chassis configuration, allowing the configuration to switch from the master Routing Engine in the master to the backup Routing Engine in the backup with minimal interruption to network communications. When you configure GRES, 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 boot up 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 with the new master Routing Engine. The interruption to the traffic is minimal. Virtual Chassis Software Upgrade and Failover Features J-EX4200 switches provide these features for increased resiliency in Virtual Chassis configurations: • Virtual Chassis atomic software upgrade—When you upgrade software in a Virtual Chassis configuration, the upgrade will either succeed or fail on all member switches, preventing the situation in which only some of the Virtual Chassis member switches are upgraded. 879 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Virtual Chassis fast failover—A hardware-assisted failover mechanism that automatically reroutes traffic and reduces traffic loss in the event of a link failure. • Virtual Chassis split and merge—If there is a disruption to the Virtual Chassis configuration due to member switches failing or being removed from the configuration, the Virtual Chassis configuration splits into two separate Virtual Chassis. 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. You can select up to eight Ethernet interfaces and include them within a LAG. In a J-EX4200 Virtual Chassis configuration, the interfaces that form a LAG can be on different members of the Virtual Chassis. See “Understanding Virtual Chassis Configurations and Link Aggregation” on page 702. Related Documentation 880 • For more information on high availability features, see the Junos OS High Availability Configuration Guide at http://www.juniper.net/techpubs/software/junos/. • Virtual Chassis Overview on page 691 • Understanding Virtual Chassis Components on page 694 • Understanding Virtual Chassis Configurations and Link Aggregation on page 702 • Understanding VRRP on J-EX Series Switches on page 1425 CHAPTER 51 Examples: Interfaces Configuration • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 881 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 887 • Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch on page 893 • Example: Configuring Unicast RPF on a J-EX Series Switch on page 900 • Example: Configuring IP Directed Broadcast on a J-EX Series Switch on page 904 Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch J-EX Series switches allow you to combine multiple Ethernet links into one logical interface for higher bandwidth and redundancy. The ports that are combined in this manner are referred to as a link aggregation group (LAG) or bundle. The number of Ethernet links you can combine into a LAG depends on your J-EX Series switch model. See “Understanding Aggregated Ethernet Interfaces and LACP” on page 867 for more information. This example describes how to configure uplink LAGs to connect a Virtual Chassis access switch to a Virtual Chassis distribution switch: • Requirements on page 881 • Overview and Topology on page 882 • Configuration on page 884 • Verification on page 886 • Troubleshooting on page 887 Requirements This example uses the following software and hardware components: • Two J-EX4200-48T switches • Two J-EX4200-24F switches • Four uplink modules 881 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Before you configure the LAGs, be sure you have: • Configured the Virtual Chassis switches. See “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717. • Configured the uplink ports on the switches as trunk ports. See “Configuring Gigabit Ethernet Interfaces (CLI Procedure)” on page 919. Overview and Topology For maximum speed and resiliency, you can combine uplinks between an access switch and a distribution switch into LAGs. Using LAGs can be particularly effective when connecting a multimember Virtual Chassis access switch to a multimember Virtual Chassis distribution switch. The Virtual Chassis access switch in this example is composed of two member switches. Each member switch has an uplink module with two 10-Gigabit Ethernet ports. These ports are configured as trunk ports, connecting the access switch with the distribution switch. Configuring the uplinks as LAGs has the following advantages: • Link Aggregation Control Protocol (LACP) can optionally be configured for link negotiation. • It doubles the speed of each uplink from 10 Gbps to 20 Gbps. • If one physical port is lost for any reason (a cable is unplugged or a switch port fails, or one member switch is unavailable), the logical port transparently continues to function over the remaining physical port. The topology used in this example consists of one Virtual Chassis access switch and one Virtual Chassis distribution switch. The access switch is composed of two J-EX4200-48T switches (SWA-0 and SWA-1), interconnected to each other with their Virtual Chassis ports (VCPs) as member switches of Host-A. The distribution switch is composed of two J-EX4200-24F switches (SWD-0 and SWD-1), interconnected with their VCPs as member switches of Host-D. Each member of the access switch has an uplink module installed. Each uplink module has two ports. The uplinks are configured to act as trunk ports, connecting the access switch with the distribution switch. One uplink port from SWA-0 and one uplink port from SWA-1 are combined as LAG ae0 to SWD-0. This link is used for one VLAN. The remaining uplink ports from SWA-0 and from SWA-1 are combined as a second LAG connection (ae1) to SWD-1. LAG ae1 is used for another VLAN. NOTE: If the remote end of the LAG link is a security device, LACP might not be supported because security devices require a deterministic configuration. In this case, do not configure LACP. All links in the LAG are permanently operational unless the switch detects a link failure within the Ethernet physical layer or data link layers. 882 Chapter 51: Examples: Interfaces Configuration Figure 24: Topology for LAGs Connecting a Virtual Chassis Access Switch to a Virtual Chassis Distribution Switch Table 120 on page 883 details the topology used in this configuration example. Table 120: Components of the Topology for Connecting Virtual Chassis Access Switches to a Virtual Chassis Distribution Switch Switch SWA-0 Hostname and VCID Base Hardware Uplink Module Member ID Trunk Port Host-A Access switch J-EX4200-48T switch One uplink module 0 xe-0/1/0 to SWD-0 xe-0/1/1 to SWD-1 VCID 1 SWA-1 Host-A Access switch J-EX4200-48P switch One uplink module 1 xe-2/1/0 to SWD-0 xe-2/1/1 to SWD-1 VCID 1 883 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 120: Components of the Topology for Connecting Virtual Chassis Access Switches to a Virtual Chassis Distribution Switch (continued) Switch SWD-0 Hostname and VCID Base Hardware Uplink Module Member ID Trunk Port Host-D Distribution switch J-EX4200 L-24F switch One uplink module 0 xe-0/1/0 to SWA-0 xe-0/1/1 to SWA-1 VCID 4 SWD-1 Host-D Distribution switch J-EX4200 L-24F switch One uplink module 1 xe-2/1/0 to SWA-0 xe-2/1/1 to SWA-1 VCID 4 Configuration To configure two uplink LAGs from the Virtual Chassis access switch to the Virtual Chassis distribution switch: CLI Quick Configuration To quickly configure aggregated Ethernet high-speed uplinks between a Virtual Chassis access switch and a Virtual Chassis distribution switch, copy the following commands and paste them into the switch terminal window: [edit] set chassis aggregated-devices ethernet device-count 2 set interfaces ae0 aggregated-ether-options minimum-links 2 set interfaces ae0 aggregated-ether-options link-speed 10g set interfaces ae1 aggregated-ether-options minimum-links 2 set interfaces ae1 aggregated-ether-options link-speed 10g set interfaces ae0 unit 0 family inet address 192.0.2.0/25 set interfaces ae1 unit 1 family inet address 192.0.2.128/25 set interfaces xe-0/1/0 ether-options 802.ad ae0 set interfaces xe-2/1/0 ether-options 802.ad ae0 set interfaces xe-0/1/1 ether-options 802.ad ae1 set interfaces xe-2/1/1 ether-options 802.ad ae1 Step-by-Step Procedure To configure aggregated Ethernet high-speed uplinks between a Virtual Chassis access switch and a Virtual Chassis distribution switch: 1. Specify the number of LAGs to be created on the chassis: [edit chassis] user@Host-A# set aggregated-devices ethernet device-count 2 2. Specify the number of links that need to be present for the ae0 LAG interface to be up: [edit interfaces] user@Host-A# set ae0 aggregated-ether-options minimum-links 2 3. Specify the number of links that need to be present for the ae1 LAG interface to be up: [edit interfaces] user@Host-A# set ae1 aggregated-ether-options minimum-links 2 4. 884 Specify the media speed of the ae0 link: Chapter 51: Examples: Interfaces Configuration [edit interfaces] user@Host-A# set ae0 aggregated-ether-options link-speed 10g 5. Specify the media speed of the ae1 link: [edit interfaces] user@Host-A# set ae1 aggregated-ether-options link-speed 10g 6. Specify the interface ID of the uplinks to be included in LAG ae0: [edit interfaces] user@Host-A# set xe-0/1/0 ether-options 802.ad ae0 user@Host-A# set xe-2/1/0 ether-options 802.ad ae0 7. Specify the interface ID of the uplinks to be included in LAG ae1: [edit interfaces] user@Host-A# set xe-0/1/1 ether-options 802.ad ae1 user@Host-A# set xe-2/1/1 ether-options 802.ad ae1 8. Specify that LAG ae0 belongs to the subnet for the employee broadcast domain: [edit interfaces] user@Host-A# set ae0 unit 0 family inet address 192.0.2.0/25 9. Specify that LAG ae1 belongs to the subnet for the guest broadcast domain: [edit interfaces] user@Host-A# set ae1 unit 1 family inet address 192.0.2.128/25 Results Display the results of the configuration: [edit] chassis { aggregated-devices { ethernet { device-count 2; } } } interfaces { ae0 { aggregated-ether-options { link-speed 10g; minimum-links 2; } unit 0 { family inet { address 192.0.2.0/25; } } } ae1 { aggregated-ether-options { link-speed 10g; minimum-links 2; } unit 0 { family inet { 885 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS address 192.0.2.128/25; } } xe–0/1/0 { ether-options { 802.ad ae0; } } xe–2/1/0 { ether-options { 802.ad ae0; } } xe–0/1/1 { ether-options { 802.ad ae1; } } xe–12/1/1 { ether-options { 802.ad ae1; } } } Verification To verify that switching is operational and two LAGs have been created, perform these tasks: • Verifying That LAG ae0 Has Been Created on page 886 • Verifying That LAG ae1 Has Been Created on page 886 Verifying That LAG ae0 Has Been Created Purpose Action Verify that LAG ae0 has been created on the switch. show interfaces ae0 terse Interface Admin ae0 ae0.0 Meaning up up Link Proto up up inet Action 886 Remote 10.10.10.2/24 The output confirms that the ae0 link is up and shows the family and IP address assigned to this link. Verifying That LAG ae1 Has Been Created Purpose Local Verify that LAG ae1 has been created on the switch show interfaces ae1 terse Chapter 51: Examples: Interfaces Configuration Interface ae1 ae1.0 Meaning Admin Link Proto up down up down inet Local Remote The output shows that the ae1 link is down. Troubleshooting Troubleshooting a LAG That Is Down Problem The show interfaces terse command shows that the LAG is down: Solution Check the following: Related Documentation • Verify that there is no configuration mismatch. • Verify that all member ports are up. • Verify that a LAG is part of family ethernet switching (Layer 2 LAG) or family inet (Layer 3 LAG). • Verify that the LAG member is connected to the correct LAG at the other end. • Verify that the LAG members belong to the same switch (or the same Virtual Chassis). • Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 717 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Example: Connecting an Access Switch to a Distribution Switch on page 1078. • Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches • Installing an Uplink Module in a J-EX4200 Switch Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch J-EX Series switches allow you to combine multiple Ethernet links into one logical interface for higher bandwidth and redundancy. The ports that are combined in this manner are referred to as a link aggregation group (LAG) or bundle. The number of Ethernet links you can combine into a LAG depends on your J-EX Series switch model. See “Understanding Aggregated Ethernet Interfaces and LACP” on page 867 for more information. J-EX Series switches allow you to further enhance these links by configuring Link Aggregation Control Protocol (LACP). 887 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to overlay LACP on the LAG configurations that were created in “Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch” on page 740: • Requirements on page 888 • Overview and Topology on page 888 • Configuring LACP for the LAGs on the Virtual Chassis Access Switch on page 889 • Configuring LACP for the LAGs on the Virtual Chassis Distribution Switch on page 889 • Verification on page 890 • Troubleshooting on page 891 Requirements This example uses the following software and hardware components: • Two J-EX4200-48T switches • Two J-EX4200-24F switches • Four J-EX Series uplink modules Before you configure LACP, be sure you have: • Set up the Virtual Chassis switches. See “Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet” on page 717. • Configured the uplink ports on the switches as trunk ports. See “Configuring Gigabit Ethernet Interfaces (CLI Procedure)” on page 919. • Configured the LAGs. See “Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch” on page 740 Overview and Topology This example assumes that you are already familiar with the Example: Configuring Aggregated Ethernet High-Speed Uplinks between Virtual Chassis Access Switch and Virtual Chassis Distribution Switch. The topology in this example is exactly the same as the topology in that other example. This example shows how to use LACP to enhance the LAG functionality. LACP exchanges are made between actors (the transmitting link) and partners (the receiving link). The LACP mode can be either active or passive. NOTE: If the actor and partner are both in passive mode, they do not exchange LACP packets, which results in the aggregated Ethernet links not coming up. By default, LACP is in passive mode. To initiate transmission of LACP packets and responses to LACP packets, you must enable LACP in active mode. 888 Chapter 51: Examples: Interfaces Configuration By default, the actor and partner send LACP packets every second. You can configure the interval at which the interfaces send LACP packets by including the periodic statement at the [edit interfaces interface-name aggregated-ether-options lacp] hierarchy level. The interval can be fast (every second) or slow (every 30 seconds). Configuring LACP for the LAGs on the Virtual Chassis Access Switch To configure LACP for the access switch LAGs, perform these tasks: CLI Quick Configuration To quickly configure LACP for the access switch LAGs, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ae0 aggregated-ether-options lacp active periodic fast set interfaces ae1 aggregated-ether-options lacp active periodic fast Step-by-Step Procedure To configure LACP for Host-A LAGs ae0 and ae1: 1. Specify the aggregated Ethernet options for both bundles: [edit interfaces] user@Host-A#set ae0 aggregated-ether-options lacp active periodic fast user@Host-A#set ae1 aggregated-ether-options lacp active periodic fast Results Display the results of the configuration: [edit interfaces] user@Host-A# show ae0 { aggregated-ether-options { lacp { active; periodic fast; } } } ae1 { aggregated-ether-options { lacp { active; periodic fast; } } } Configuring LACP for the LAGs on the Virtual Chassis Distribution Switch To configure LACP for the two uplink LAGs from the Virtual Chassis access switch to the Virtual Chassis distribution switch, perform these tasks: CLI Quick Configuration To quickly configure LACP for the distribution switch LAGs, copy the following commands and paste them into the switch terminal window: [edit interfaces] set ae0 aggregated-ether-options lacp passive periodic fast set ae1 aggregated-ether-options lacp passive periodic fast 889 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure LACP for Host D LAGs ae0 and ae1: 1. Specify the aggregated Ethernet options for both bundles: [edit interfaces] user@Host-D#set ae0 aggregated-ether-options lacp passive periodic fast user@Host-D#set ae1 aggregated-ether-options lacp passive periodic fast Results Display the results of the configuration: [edit interfaces] user@Host-D# show ae0 { aggregated-ether-options { lacp { passive; periodic fast; } } } ae1 { aggregated-ether-options { lacp { passive periodic fast; } } } Verification To verify that LACP packets are being exchanged, perform these tasks: • Verifying the LACP Settings on page 890 • Verifying That the LACP Packets Are Being Exchanged on page 891 Verifying the LACP Settings Purpose Action Verify that LACP has been set up correctly. Use the show lacp interfaces interface-name command to check that LACP has been enabled as active on one end. user@Host-A> show lacp interfaces xe-0/1/0 Aggregated interface: ae0 LACP state: Role Def Dist Col Syn Aggr Timeout Activity xe-0/1/0 Actor No Yes No No No Yes Fast Active xe-0/1/0 Partner No Yes No No No Yes Fast Passive LACP protocol: xe-0/1/0 890 Exp Receive State Defaulted Transmit State Mux State Fast periodic Detached Chapter 51: Examples: Interfaces Configuration Meaning The output indicates that LACP has been set up correctly and is active at one end. Verifying That the LACP Packets Are Being Exchanged Purpose Action Verify that LACP packets are being exchanged. Use the show interfaces aex statistics command to display LACP information. user@Host-A> show interfaces ae0 statistics Physical interface: ae0, Enabled, Physical link is Down Interface index: 153, SNMP ifIndex: 30 Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Minimum links needed: 1, Minimum bandwidth needed: 0 Device flags : Present Running Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Current address: 02:19:e2:50:45:e0, Hardware address: 02:19:e2:50:45:e0 Last flapped : Never Statistics last cleared: Never Input packets : 0 Output packets: 0 Input errors: 0, Output errors: 0 Logical interface ae0.0 (Index 71) (SNMP ifIndex 34) Flags: Hardware-Down Device-Down SNMP-Traps Encapsulation: ENET2 Statistics Packets pps Bytes bps Bundle: Input : 0 0 0 0 Output: 0 0 0 0 Protocol inet Flags: None Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255 Meaning The output here shows that the link is down and that no PDUs are being exchanged. Troubleshooting These are some tips for troubleshooting: Troubleshooting a Nonworking LACP Link Problem The LACP link is not working. Solution Check the following: • Remove the LACP configuration and verify whether the static LAG is up. • Verify that LACP is configured at both ends. 891 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation 892 • Verify that LACP is not passive at both ends. • Verify whether LACP protocol data units (PDUs) are being exchanged by running the monitor traffic-interface lag-member detail command. • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Virtual Chassis Cabling Configuration Examples for J-EX4200 Switches • Installing an Uplink Module in a J-EX4200 Switch Chapter 51: Examples: Interfaces Configuration Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch In a large LAN, you commonly need to partition the network into multiple VLANs. You can configure Layer 3 subinterfaces to route traffic between the VLANs. In one common topology, known as a “router on a stick” or a “one-armed router,” you connect a router to an access switch with connections to multiple VLANs. This example describes how to create Layer 3 subinterfaces on trunk interfaces of a distribution switch and access switch so that you can route traffic among multiple VLANs: • Requirements on page 893 • Overview and Topology on page 893 • Configuring the Access Switch Subinterfaces on page 894 • Configuring the Distribution Switch Subinterfaces on page 896 • Verification on page 898 Requirements This example uses the following hardware and software components: • For the distribution switch, one J-EX4200-24F switch. This model is designed to be used as a distribution switch for aggregation or collapsed core network topologies and in space-constrained data centers. It has twenty-four 1-Gigabit Ethernet fiber SFP ports and an uplink module with two 10-Gigabit Ethernet ports. • For the access switch, any Layer 2 switch that supports 802.1Q VLAN tags. Before you connect the switches, make sure you have: • Connected the two switches. • Configured the necessary VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. Overview and Topology In a large office with multiple buildings and VLANs, you commonly aggregate traffic from a number of access switches into a distribution switch. This configuration example shows a simple topology to illustrate how to connect a single Layer 2 access switch connected to multiple VLANs to a distribution switch, enabling traffic to pass between those VLANs. In the example topology, the LAN is segmented into five VLANs, all associated with interfaces on the access switch. One 1-Gigabit Ethernet port on the access switch's uplink module connects to one 1-Gigabit Ethernet port on the distribution switch. Table 121 on page 894 lists the settings for the example topology. 893 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 121: Components of the Topology for Creating Layer 3 Subinterfaces on an Access Switch and a Distribution Switch Property Settings Access switch hardware Any Layer 2 switch with multiple 1-Gigabit Ethernet ports and at least one 1-Gigabit Ethernet uplink module Distribution switch hardware J-EX4200-24F, 24 1-Gigabit Ethernet fiber SPF ports (ge-0/0/0 through ge-0/0/23); one uplink module with 10-Gigabit Ethernet ports VLAN names and tag IDs vlan1, tag 101 vlan2, tag 102 vlan3, tag 103 vlan4, tag 104 vlan5, tag 105 VLAN subnets vlan1: 1.1.1.0/24 (addresses 1.1.1.1 through 1.1.1.254) vlan2: 2.1.1.0/24 (addresses 2.1.1.1 through 2.1.1.254) vlan3: 3.1.1.0/24 (addresses 3.1.1.1 through 3.1.1.254) vlan4: 4.1.1.0/24 (addresses 4.1.1.1 through 4.1.1.254) vlan5: 5.1.1.0/24 (addresses 5.1.1.1 through 5.1.1.254) Port interfaces On the access switch: ge-0/1/0 On the distribution switch: ge-0/0/0 Configuring the Access Switch Subinterfaces CLI Quick Configuration To quickly create and configure subinterfaces on the access switch, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/1/0 vlan-tagging set interfaces ge-0/1/0 unit 0 vlan-id 101 family inet address 1.1.1.1/24 set interfaces ge-0/1/0 unit 1 vlan-id 102 family inet address 2.1.1.1/24 set interfaces ge-0/1/0 unit 2 vlan-id 103 family inet address 3.1.1.1/24 set interfaces ge-0/1/0 unit 3 vlan-id 104 family inet address 4.1.1.1/24 set interfaces ge-0/1/0 unit 4 vlan-id 105 family inet address 5.1.1.1/24 Step-by-Step Procedure To configure the subinterfaces on the access switch: 1. On the trunk interface of the access switch, enable VLAN tagging: [edit interfaces ge-0/1/0] user@access-switch# set vlan-tagging 2. Bind vlan1's VLAN ID to the logical interface: [edit interfaces ge-0/1/0] user@access-switch# set unit 0 vlan-id 101 894 Chapter 51: Examples: Interfaces Configuration Set vlan1's subinterface IP address: 3. [edit interfaces ge-0/1/0] user@access-switch# set unit 0 family inet address 1.1.1.1/24 Bind vlan2's VLAN ID to the logical interface: 4. [edit interfaces ge-0/1/0] user@access-switch# set unit 1 vlan-id 102 Set vlan2's subinterface IP address: 5. [edit interfaces ge-0/1/0] user@access-switch# set unit 1 family inet address 2.1.1.1/24 Bind vlan3's VLAN ID to the logical interface: 6. [edit interfaces ge-0/1/0] user@access-switch# set unit 2 vlan–id 103 Set vlan3's subinterface IP address: 7. [edit interfaces ge-0/1/0] user@access-switch# set unit 2 family inet address 3.1.1.1/24 Bind vlan4's VLAN ID to the logical interface: 8. [edit interfaces ge-0/1/0] user@access-switch# set unit 3 vlan-id 104 Set vlan4's subinterface IP address: 9. [edit interfaces ge-0/1/0] user@access-switch# set unit 3 family inet address 4.1.1.1/24 10. Bind vlan5's VLAN ID to the logical interface: [edit interfaces ge-0/1/0] user@access-switch# set unit 4 vlan-id 105 11. Set vlan5's subinterface IP address: [edit interfaces ge-0/1/0] user@access-switch# set unit 4 family inet address 5.1.1.1/24 Results Check the results of the configuration: user@access-switch> show configuration interfaces { ge-0/1/0 { vlan-tagging; unit 0 { vlan-id 101; family inet { address 1.1.1.1/24; } } unit 1 { vlan-id 102; family inet { address 2.1.1.1/24; 895 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } unit 2 { vlan-id 103; family inet { address 3.1.1.1/24; } } unit 3 { vlan-id 104; family inet { address 4.1.1.1/24; } } unit 4 { vlan-id 105; family inet { address 5.1.1.1/24; } } } Configuring the Distribution Switch Subinterfaces CLI Quick Configuration To quickly create and configure subinterfaces on the distribution switch, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/0/0 vlan-tagging set interfaces ge-0/0/0 unit 0 vlan-id 101 family inet address 1.1.1.2/24 set interfaces ge-0/0/0 unit 1 vlan-id 102 family inet address 2.1.1.2/24 set interfaces ge-0/0/0 unit 2 vlan-id 103 family inet address 3.1.1.2/24 set interfaces ge-0/0/0 unit 3 vlan-id 104 family inet address 4.1.1.2/24 set interfaces ge-0/0/0 unit 4 vlan-id 105 family inet address 5.1.1.2/24 Step-by-Step Procedure To configure subinterfaces on the distribution switch: 1. On the trunk interface of the distribution switch, enable VLAN tagging: [edit interfaces ge-0/0/0] user@distribution-switch# set vlan-tagging 2. Bind vlan1's VLAN ID to the logical interface: [edit interfaces ge-0/0/0] user@distribution-switch# set unit 0 vlan-id 101 3. Set vlan1's subinterface IP address: [edit interfaces ge-0/0/0] user@distribution-switch# set unit 0 family inet address 1.1.1.2/24 4. Bind vlan2's VLAN ID to the logical interface: [edit interfaces ge-0/0/0] user@distribution-switch# set unit 1 vlan-id 102 5. Set vlan2's subinterface IP address: [edit interfaces ge-0/0/0] 896 Chapter 51: Examples: Interfaces Configuration user@distribution-switch# set unit 1 family inet address 2.1.1.2/24 Bind vlan3's VLAN ID to the logical interface: 6. [edit interfaces ge-0/0/0] user@distribution-switch# set unit 2 vlan-id 103 Set vlan3's subinterface IP address: 7. [edit interfaces ge-0/0/0] user@distribution-switch# set unit 2 family inet address 3.1.1.2/24 Bind vlan4's VLAN ID to the logical interface: 8. [edit interfaces ge-0/0/0] user@distribution-switch# set unit 3 vlan-id 104 Set vlan4's subinterface IP address: 9. [edit interfaces ge-0/0/0] user@distribution-switch# set unit 3 family inet address 4.1.1.2/24 10. Bind vlan5's VLAN ID to the logical interface: [edit interfaces ge-0/0/0] user@distribution-switch# set unit 4 vlan-id 105 11. Set vlan5's subinterface IP address: [edit interfaces ge-0/0/0] user@distribution-switch# set unit 4 family inet address 5.1.1.2/24 Results user@distribution-switch> show configuration interfaces { ge-0/0/0 { vlan-tagging; unit 0 { vlan-id 101; family inet { address 1.1.1.2/24; } } unit 1 { vlan-id 102; family inet { address 2.1.1.2/24; } } unit 2 { vlan-id 103; family inet { address 3.1.1.2/24; } } unit 3 { vlan-id 104; family inet { address 4.1.1.2/24; } } 897 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit 4 { vlan-id 105; family inet { address 5.1.1.2/24; } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That Subinterfaces Were Created on page 898 • Verifying That Traffic Passes Between VLANs on page 898 Verifying That Subinterfaces Were Created Purpose Action Verify that the subinterfaces were properly created on the access switch and distribution switch. 1. Use the show interfaces command on the access switch: user@access-switch> show interfaces ge-0/1/0 terse Interface ge-0/1/0 ge-0/1/0.0 ge-0/1/0.1 ge-0/1/0.2 ge-0/1/0.3 ge-0/1/0.4 ge-0/1/0.32767 Admin up up up up up up up Link up up up up up up up Proto Local inet inet inet inet inet 1.1.1.1/24 2.1.1.1/24 3.1.1.1/24 4.1.1.1/24 5.1.1.1/24 Remote 2. Use the show interfaces command on the distribution switch: user@distribution-switch> show interfaces ge-0/0/0 terse Interface ge-0/0/0 ge-0/0/0.0 ge-0/0/0.1 ge-0/0/0.2 ge-0/0/0.3 ge-0/0/0.4 ge-0/0/0.32767 Meaning Admin up up up up up up up Link up up up up up up up Proto Local inet inet inet inet inet 1.1.1.2/24 2.1.1.2/24 3.1.1.2/24 4.1.1.2/24 5.1.1.2/24 Remote Each subinterface created is displayed as a ge-fpc/pic/port.x logical interface, where x is the unit number in the configuration. The status is listed as up, indicating the link is working. Verifying That Traffic Passes Between VLANs Purpose 898 Verify that the distribution switch is correctly routing traffic from one VLAN to another. Chapter 51: Examples: Interfaces Configuration Action Ping from the access switch to the distribution switch on each subinterface. 1. From the access switch, ping the address of the vlan1 subinterface on the distribution switch: user@access-switch> ping 1.1.1.2 count 4 PING 1.1.1.2 (1.1.1.2): 56 data bytes 64 bytes from 1.1.1.2: icmp_seq=0 ttl=64 64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.333 time=0.113 time=0.112 time=0.158 ms ms ms ms --- 1.1.1.2 ping statistics --4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.112/0.179/0.333/0.091 ms 2. From the access switch, ping the address of the vlan2 subinterface on the distribution switch: user@access-switch> ping 2.1.1.2 count 4 PING 2.1.1.2 (2.1.1.2): 56 data bytes 64 bytes from 2.1.1.2: icmp_seq=0 ttl=64 64 bytes from 2.1.1.2: icmp_seq=1 ttl=64 64 bytes from 2.1.1.2: icmp_seq=2 ttl=64 64 bytes from 2.1.1.2: icmp_seq=3 ttl=64 time=0.241 time=0.113 time=0.162 time=0.167 ms ms ms ms --- 2.1.1.2 ping statistics --4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.113/0.171/0.241/0.046 ms 3. From the access switch, ping the address of the vlan3 subinterface on the distribution switch: user@access-switch> ping 3.1.1.2 count 4 PING 3.1.1.2 (3.1.1.2): 56 data bytes 64 bytes from 3.1.1.2: icmp_seq=0 ttl=64 64 bytes from 3.1.1.2: icmp_seq=1 ttl=64 64 bytes from 3.1.1.2: icmp_seq=2 ttl=64 64 bytes from 3.1.1.2: icmp_seq=3 ttl=64 time=0.341 time=0.162 time=0.112 time=0.208 ms ms ms ms --- 3.1.1.2 ping statistics --4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.112/0.206/0.341/0.085 ms 4. From the access switch, ping the address of the vlan4 subinterface on the distribution switch: user@access-switch> ping 4.1.1.2 count 4 PING 4.1.1.2 (4.1.1.2): 56 data bytes 64 bytes from 4.1.1.2: icmp_seq=0 ttl=64 64 bytes from 4.1.1.2: icmp_seq=1 ttl=64 64 bytes from 4.1.1.2: icmp_seq=2 ttl=64 64 bytes from 4.1.1.2: icmp_seq=3 ttl=64 time=0.226 time=0.166 time=0.107 time=0.221 ms ms ms ms --- 4.1.1.2 ping statistics --- 899 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.107/0.180/0.226/0.048 ms 5. From the access switch, ping the address of the vlan5 subinterface on the distribution switch: user@access-switch> ping 5.1.1.2 count 4 PING 5.1.1.2 (5.1.1.2): 56 data bytes 64 bytes from 5.1.1.2: icmp_seq=0 ttl=64 64 bytes from 5.1.1.2: icmp_seq=1 ttl=64 64 bytes from 5.1.1.2: icmp_seq=2 ttl=64 64 bytes from 5.1.1.2: icmp_seq=3 ttl=64 time=0.224 time=0.104 time=0.102 time=0.170 ms ms ms ms --- 5.1.1.2 ping statistics --4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.102/0.150/0.224/0.051 ms Meaning Related Documentation If all the ping packets are transmitted and are received by the destination address, the subinterfaces are up and working. • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 Example: Configuring Unicast RPF on a J-EX Series Switch Unicast reverse-path forwarding (RPF) helps protect the switch against denial-of-service (DoS) and distributed denial-of-service (DDoS) attacks by verifying the unicast source address of each packet that arrives on an ingress interface where unicast RPF is enabled. This example shows how to help defend the switch ingress interfaces against denial-of-service (DoS) and distributed denial-of-service (DDoS) attacks by configuring unicast reverse-path forwarding (RPF) on a customer-edge interface to filter incoming traffic: • Requirements on page 900 • Overview and Topology on page 901 • Configuration on page 901 • Verification on page 902 Requirements This example uses the following software and hardware components: • Two J-EX8200 switches Before you begin, be sure you have: 900 • Connected the two switches by symmetrically routed interfaces. • Ensured that the interface on which you will configure unicast RPF is symmetrically routed. Chapter 51: Examples: Interfaces Configuration Overview and Topology Large amounts of unauthorized traffic such as attempts to flood a network with fake (bogus) service requests in a denial-of-service (DoS) attack can consume network resources and deny service to legitimate users. One way to help prevent DoS and distributed denial-of-service (DDoS) attacks is to verify that incoming traffic originates from legitimate network sources. Unicast RPF helps ensure that a traffic source is legitimate (authorized) by comparing the source address of each packet that arrives on an interface to the forwarding-table entry for its source address. If the switch uses the same interface that the packet arrived on to reply to the packet's source, this verifies that the packet originated from an authorized source, and the switch forwards the packet. If the switch does not use the same interface that the packet arrived on to reply to the packet's source, the packet might have originated from an unauthorized source, and the switch discards the packet. This example uses two J-EX8200 switches. On J-EX4200 switches, you cannot configure individual interfaces for unicast RPF. On J-EX4200 switches, the switch applies unicast RPF globally to all interfaces on the switch. See “Understanding Unicast RPF for J-EX Series Switches” on page 872 for more information on limitations regarding the configuration of unicast RPF on J-EX4200 switches. In this example, an enterprise network's system administrator wants to protect Switch A against potential DoS and DDoS attacks from the Internet. The administrator configures unicast RPF on interface ge-1/0/10 on Switch A. Packets arriving on interface ge-1/0/10 on Switch A from the Switch B source also use incoming interface ge-1/0/10 as the best return path to send packets back to the source. The topology of this configuration example uses two J-EX8200 switches, Switch A and Switch B, connected by symmetrically routed interfaces: • Switch A is on the edge of an enterprise network. The interface ge-1/0/10 on Switch A connects to the interface ge-1/0/5 on Switch B. • Switch B is on the edge of the service provider network that connects the enterprise network to the Internet. Configuration To enable unicast RPF, perform these tasks: CLI Quick Configuration To quickly configure unicast RPF on Switch A, copy the following command and paste it into the switch terminal window: [edit interfaces] set ge-1/0/10 unit 0 family inet rpf-check 901 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure unicast RPF on Switch A: 1. Enable unicast RPF on interface ge-1/0/10: [edit interfaces] user@switch# set ge-1/0/10 unit 0 family inet rpf-check Results Check the results: [edit interfaces] user@switch# show ge-1/0/10 { unit 0 { family inet { rpf-check; } } } Verification To confirm that the configuration is correct, perform these tasks: • Verifying That Unicast RPF Is Enabled on the Switch on page 902 Verifying That Unicast RPF Is Enabled on the Switch Purpose Action Verify that unicast RPF is enabled. Verify that unicast RPF is enabled on interface ge-1/0/10 by using the show interfaces ge-1/0/10 extensive or show interfaces ge-1/0/10 detail command. user@switch> show interfaces ge-1/0/10 extensive Physical interface: ge-1/0/10, Enabled, Physical link is Down Interface index: 139, SNMP ifIndex: 58, Generation: 140 Link-level type: Ethernet, MTU: 1514, Speed: Auto, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:19:e2:50:95:ab, Hardware address: 00:19:e2:50:95:ab Last flapped : Never Statistics last cleared: Never Traffic statistics: Input bytes : 0 0 bps Output bytes : 0 0 bps Input packets: 0 0 pps Output packets: 0 0 pps IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, 902 Chapter 51: Examples: Interfaces Configuration L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0 Output errors: Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 0 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 0 0 Active alarms : LINK Active defects : LINK MAC statistics: Receive Total octets 0 Total packets 0 Unicast packets 0 Broadcast packets 0 Multicast packets 0 CRC/Align errors 0 FIFO errors 0 MAC control frames 0 MAC pause frames 0 Oversized frames 0 Jabber frames 0 Fragment frames 0 VLAN tagged frames 0 Code violations 0 Filter statistics: Input packet count 0 Input packet rejects 0 Input DA rejects 0 Input SA rejects 0 Output packet count Output packet pad count Output packet error count CAM destination filters: 0, CAM source filters: 0 Autonegotiation information: Negotiation status: Incomplete Packet Forwarding Engine configuration: Destination slot: 1 Transmit 0 0 0 0 0 0 0 0 0 0 0 0 Logical interface ge-1/0/10.0 (Index 69) (SNMP ifIndex 59) (Generation 135) Flags: Device-Down SNMP-Traps 0x0 Encapsulation: ENET2 Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Local statistics: 903 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Protocol inet, Generation: 144, Route table: 0 Flags: uRPF Addresses, Flags: Is-Preferred Is-Primary Meaning Related Documentation 0 0 0 0 bps bps pps pps The second-to-last line of the display shows the unicast RPF flag enabled, confirming that unicast RPF is enabled on interface ge-1/0/10. • Configuring Unicast RPF (CLI Procedure) on page 927 • Disabling Unicast RPF (CLI Procedure) on page 928 Example: Configuring IP Directed Broadcast on a J-EX Series Switch IP directed broadcast provides a method of sending broadcast packets to hosts on a specified subnet without broadcasting those packets to hosts on the entire network. This example shows how to enable a subnet to receive IP directed broadcast packets so you can perform backups and other network management tasks remotely: • Requirements on page 904 • Overview and Topology on page 905 • Configuration on page 905 Requirements This example uses the following software and hardware components: • One PC • One J-EX Series switch Before you configure IP directed broadcast for a subnet: 904 • Ensure that the subnet does not have a direct connection to the Internet. • Configure routed VLAN interfaces (RVIs) for the ingress and egress VLANs on the switch. See “Configuring Routed VLAN Interfaces (CLI Procedure)” on page 1137 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. Chapter 51: Examples: Interfaces Configuration Overview and Topology You might want to perform remote administration tasks such as backups and wake-on-LAN (WOL) application tasks to manage groups of clients on a subnet. One way to do this is to send IP directed broadcast packets targeted at the hosts in a particular target subnet. The network forwards IP directed broadcast packets as if they were unicast packets. When the IP directed broadcast packet is received by a VLAN that is enabled for targeted-broadcast, the switch broadcasts the packet to all the hosts in its subnet. In this topology (see Figure 25 on page 905), a host is connected to an interface on a J-EX Series switch to manage the clients in subnet 10.1.2.1/24. When the switch receives a packet with the broadcast IP address of the target subnet as its destination address, it forwards the packet to the subnet’s Layer 3 interface and broadcasts it to all the hosts within the subnet. Figure 25: Topology for IP Directed Broadcast Table 122 on page 905 shows the settings of the components in this example. Table 122: Components of the IP Directed Broadcast Topology Property Settings Switch hardware J-EX Series switch Ingress VLAN name v0 Ingress VLAN IP address 10.1.1.1/24 Egress VLAN name v1 Egress VLAN IP address 10.1.2.1/24 Interfaces in VLAN v0 ge-0/0/3.0 Interfaces in VLAN v1 ge-0/0/0.0 and ge-0/0/1.0 Configuration To configure IP directed broadcast on a subnet to enable remote management of its hosts: 905 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS CLI Quick Configuration To quickly configure the switch to accept IP directed broadcasts targeted at subnet 10.1.2.1/24, copy the following commands and paste them into the switch’s terminal window: [edit] set interfaces ge-0/0/0.0 family ethernet-switching vlan members v1 set interfaces ge-0/0/1.0 family ethernet-switching vlan members v1 set interfaces vlan.1 family inet address 10.1.2.1/24 set interfaces ge-0/0/3.0 family ethernet-switching vlan members v0 set interfaces vlan.0 family inet address 10.1.1.1/24 set vlans v1 l3-interface vlan.1 set vlans v0 l3-interface vlan.0 set interfaces vlan.1 family inet targeted-broadcast Step-by-Step Procedure To configure the switch to accept IP directed broadcasts targeted at subnet 10.1.2.1/24: 1. Add logical interface ge-0/0/0.0 to VLAN v1: [edit interfaces] user@switch# set ge-0/0/0.0 family ethernet-switching vlan members v1 2. Add logical interface ge-0/0/1.0 to VLAN v1: [edit interfaces] user@switch# set ge-0/0/1.0 family ethernet-switching vlan members v1 3. Configure the IP address for the egress VLAN, v1: [edit interfaces] user@switch# set vlan.1 family inet address 10.1.2.1/24 4. Add logical interface ge-0/0/3.0 to VLAN v0: [edit interfaces] user@switch# set ge-0/0/3.0 family ethernet-switching vlan members v0 5. Configure the IP address for the ingress VLAN: [edit interfaces] user@switch# set vlan.0 family inet address 10.1.1.1/24 6. To route traffic between the ingress and egress VLANs, associate a Layer 3 interface with each VLAN: [edit vlans] user@switch# set v1 l3-interfacevlan.1 user@switch# set v0 l3–interface vlan.0 7. Enable the Layer 3 interface for the egress VLAN to receive IP directed broadcasts: [edit interfaces] user@switch# set vlan.1 family inet targeted-broadcast Results Check the results: user@switch# show interfaces { ge-0/0/0 { unit 0 { family ethernet-switching { vlan { 906 Chapter 51: Examples: Interfaces Configuration members v1; } } } } ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members v1; } } } } ge-0/0/3 { unit 0 { family ethernet-switching { vlan { members v0; } } } } vlan { unit 0 { family inet { targeted-broadcast; address 10.1.1.1/24; } } unit 1 { family inet { targeted-broadcast; address 10.1.2.1/24; } } } vlans { default; v0 { l3-interface vlan.0; } v1 { l3-interface vlan.1; } } Related Documentation • Configuring IP Directed Broadcast (CLI Procedure) on page 929 907 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 908 CHAPTER 52 Configuring Interfaces • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Port Role Configuration with the J-Web Interface (with CLI References) on page 915 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Setting the Mode on an SFP+ Uplink Module (CLI Procedure) on page 921 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet Interfaces (J-Web Procedure) on page 923 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Configuring Unicast RPF (CLI Procedure) on page 927 • Disabling Unicast RPF (CLI Procedure) on page 928 • Configuring IP Directed Broadcast (CLI Procedure) on page 929 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 Configuring Gigabit Ethernet Interfaces (J-Web Procedure) An Ethernet interface must be configured for optimal performance in a high-traffic network. To configure properties on a Gigabit Ethernet interface or a 10-Gigabit Ethernet interface on a J-EX Series switch: 1. Select Interfaces > Ports. The page lists Gigabit Ethernet and 10-Gigabit Ethernet interfaces and their link status. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Select the interface you want to configure. If the interface you want to configure is not listed under Ports in the top table on the page, select the FPC (the FPC is the line 909 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS card on a J-EX8200 switch or the member switch in a Virtual Chassis configuration) that includes that interface from the List Ports for FPC list. Details for the selected interface such as administrative status, link status, speed, duplex, and flow control are displayed in the bottom table on the page. NOTE: You can select multiple interfaces and modify their settings at the same time. When you do this, you cannot modify the IP address or enable or disable the administrative status of the selected interface. 3. Click Edit and select the set of options you want to configure first: • Port Role—Enables you to assign a profile for the selected interface. NOTE: When you select a particular port role, pre-configured port security parameters are set for the VLAN that the interface belongs to. For example, if you select the port role Desktop, the port security options examine-dhcp and arp-inspection are enabled on the VLAN that the interface belongs to. If there are interfaces in the VLAN that have static IP addresses, those interfaces might lose connectivity because those static IP addresses might not be present in the DHCP pool. Therefore, when you are selecting a port role, ensure that the corresponding port security settings for the VLAN are applicable to the interface. For basic information on port security features such as DHCP snooping (CLI option examine-dhcp) or dynamic ARP inspection (DAI) (CLI option arp-inspection), see “Configuring Port Security (J-Web Procedure)” on page 2627. For detailed descriptions of port security features, see “Port Security for J-EX Series Switches Overview” on page 2545. Click Details to view the configuration parameters for the selected port role. • VLAN Options—Enables you to configure VLAN options for the selected interface. • Link Options—Enables you to modify the following link options for the selected interface: • 910 • Speed • MTU • Autonegotiation • Flow Control • Duplex IP Options—Enables you to configure an IP address for the interface. Chapter 52: Configuring Interfaces 4. Configure the interface by configuring options in the selected option set. See Table 123 on page 911 for details on options. 5. Repeat Steps 3 and 4 for the remaining option sets that you want to configure for the interface. NOTE: To enable or disable the administrative status for a selected interface, click Enable Port or Disable Port. Table 123: Port Edit Options Field Function Port Role Specifies a profile (role) to assign to the interface. Your Action NOTE: Once a port role is configured on the interface, you cannot specify VLAN options or IP options. NOTE: Only the following port roles can be applied on J-EX8200 switch interfaces: Default Desktop Desktop and Phone • Default • Layer 2 uplink • Routed uplink Applies the default role. 1. The interface family is set to ethernet-switching, port mode is set to access, and RSTP is enabled. 2. Click OK. Applies the desktop role. 1. The interface family is set to ethernet-switching, port mode is set to access, RSTP is enabled with the edge and point-to-point options, and port security parameters (MAC limit =1; dynamic ARP inspection and DHCP snooping enabled) are set. 2. Click Details to view CLI commands for this role. Applies the desktop and phone role. 1. The interface family is set to ethernet-switching, port mode is set to access, port security parameters (MAC limit =1; dynamic ARP Inspection and DHCP snooping enabled) are set, and recommended CoS parameters are specified for forwarding classes, schedulers, and classifiers. See Table 124 on page 914 for more CoS information. Click Details to view CLI commands for this role. Select an existing VLAN configuration or type the name of a new VLAN configuration to be associated with the interface. 3. Click OK. Select an existing VLAN configuration or type the name of a new VLAN configuration to be associated with the interface. You can also select an existing VoIP VLAN configuration or a new VoIP VLAN configuration to be associated with the interface. NOTE: VoIP is not supported on J-EX8200 switches. 2. Click Details to view CLI commands for this role. 3. Click OK. 911 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 123: Port Edit Options (continued) Field Function Your Action Wireless Access Point Applies the wireless access point role. 1. The interface family is set to ethernet-switching, port mode is set to access, and RSTP is enabled with the edge and point-to-point options. 2. Click Details to view CLI commands for this role. Select an existing VLAN configuration or type the name of a new VLAN configuration to be associated with the interface. Type the VLAN ID for a new VLAN. 3. Click OK. Routed Uplink Applies the routed uplink role. To specify an IPv4 address: The interface family is set to inet, and recommended CoS parameters are set for schedulers and classifiers. See Table 124 on page 914 for more CoS information. 1. Select the check box IPv4 address. 2. Type an IP address—for example: 10.10.10.10. 3. Enter the subnet mask or address prefix. For example, 24 bits represents 255.255.255.0. 4. Click OK. To specify an IPv6 address: 1. Select the check box IPv6 address. 2. Type an IP address—for example: 2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. 4. Click OK. Layer 2 Uplink Applies the Layer 2 uplink role. The interface family is set to ethernet-switching, port mode is set to trunk, RSTP is enabled with the point-to-point option, and port security is set to dhcp-trusted. None 1. For this port role you can select a VLAN member and associate a native VLAN with the interface. 2. Click Details to view CLI commands for this role. 3. Click OK. Specifies that no port role is configured for the selected interface. NOTE: See “Port Role Configuration with the J-Web InterfaceCLI Reference” on page 915 for details on the CLI commands that are associated with each port role. NOTE: For a J-EX8200 switch, dynamic ARP inspection and DHCP snooping parameters are not configured. VLAN Options 912 Chapter 52: Configuring Interfaces Table 123: Port Edit Options (continued) Field Function Your Action Port Mode Specifies the mode of operation for the interface: trunk or access. If you select Trunk, you can: 1. Click Add to add a VLAN member. 2. Select the VLAN and click OK. 3. (Optional) Associate a native VLAN with the interface. If you select Access, you can: 1. Select the VLAN member to be associated with the interface. 2. (Optional) Associate a VoIP VLAN with the interface. Only a VLAN with a VLAN ID can be associated as a VoIP VLAN. NOTE: VoIP is not supported on J-EX8200 switches. Click OK. Link Options MTU (bytes) Specifies the maximum transmission unit size for the interface. Type a value from 256 through 9216. The default MTU for Gigabit Ethernet interfaces is 1514. Speed Specifies the speed for the mode. Select one of the following values: 10 Mbps, 100 Mbps, 1000 Mbps, or Auto-Negotiation. Duplex Specifies the link mode. Select one: automatic, half, or full. Description Describes the link. Enter a brief description for the link. NOTE: If the interface is part of a link aggregation group (LAG), only the option Description is enabled. Enable Auto Negotiation Enables or disables autonegotiation. Select the check box to enable autonegotiation, or clear the check box to disable it. By default, autonegotiation is enabled. Enable Flow Control Enables or disables flow control. Select the check box to enable flow control to regulate the amount of traffic sent out of the interface, or clear the check box to disable flow control and permit unrestricted traffic. Flow control is enabled by default. IP Options 913 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 123: Port Edit Options (continued) Field Function Your Action IPv4 Address Specifies an IPv4 address for the interface. 1. NOTE: If the IP address is cleared, the interface still belongs to the inet family. 2. Type an IP address—for example: 10.10.10.10. To specify an IPv4 address, select the check box IPv4 address. 3. Enter the subnet mask or address prefix. For example, 24 bits represents 255.255.255.0. 4. Click OK. IPv6 Address Specifies an IPv6 address for the interface. NOTE: If the IP address is cleared, the interface still belongs to the inet family. 1. To specify an IPv6 address, select the check box IPv6 address. 2. Type an IP address—for example: 2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. 4. Click OK. Table 124: Recommended CoS Settings for Port Roles CoS Parameter Recommended Settings Forwarding Classes There are four forwarding classes: Schedulers • voice—Queue number is set to 7. • expedited-forwarding—Queue number is set to 5. • assured-forwarding—Queue number is set to 1. • best-effort—Queue number is set to 0. The schedulers and their settings are: • Strict-priority—Transmission rate is set to 10 percent and buffer size to 5 percent. • Expedited-scheduler—Transmission rate is set to 30 percent, buffer size to 30 percent, and priority to low. • Assured-scheduler—Transmission rate is set to 25 percent, buffer size to 25 percent, and priority to low. • Best-effort scheduler—Transmission rate is set to 35 percent, buffer size to 40 percent, and priority to low. Scheduler maps When a desktop and phone, routed uplink, or layer 2 uplink role is applied on an interface, the forwarding classes and schedulers are mapped using the scheduler map. ieee-802.1 classifier Imports the default ieee-802.1 classifier configuration and sets the loss priority to low for the code point 101 for the voice forwarding class. dscp classifier Imports the default dscp classifier configuration and sets the loss priority to low for the code point 101110 for the voice forwarding class. Related Documentation 914 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Monitoring Interface Status and Traffic on page 931 Chapter 52: Configuring Interfaces • J-EX Series Switches Interfaces Overview on page 863 • Junos OS CoS for J-EX Series Switches Overview on page 2860 • Understanding Interface Naming Conventions on J-EX Series Switches on page 865 Port Role Configuration with the J-Web Interface (with CLI References) When you configure Gigabit Ethernet interface properties with the J-Web interface (Configure > Interfaces) you can optionally select pre-configured port roles for those interfaces. When you select a role from the Port Role field and apply it to a port, the J-Web interface modifies the switch configuration using CLI commands. Table 125 on page 915 lists the CLI commands applied for each port role. NOTE: If there is an existing port role configuration, it is cleared before the new port role configuration is applied. Table 125: Port Role Configuration Summary Configuration Description CLI Commands Default Port Role Set the port role to Default. set interfaces interfaceapply-macro juniper-port-profile Default Set port family to ethernet-switching. set interfaces interface unit 0 family ethernet-switching port-mode access Set port mode to access. Enable RSTP if redundant trunk groups are not configured. delete protocols rstp interface interface disable Disable RSTP if redundant trunk groups are configured. set protocols rstp interface interface disable Desktop Port Role Set the port role to desktop. set interfaces interface apply-macro juniper-port-profile Desktop Set VLAN if new VLAN is specified. set vlans vlan-id Set port family to ethernet-switching. set interfaces interface unit 0 family ethernet-switching port-mode access Set Port Mode to Access. Set VLAN if new VLAN is specified. set interfaces interface unit 0 family ethernet-switching vlan members vlan-members Set port security parameters. set ethernet-switching-options secure-access-port vlan MacTest arp-inspection Set RSTP protocol with edge option. set protocols rstp interface interface edge 915 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 125: Port Role Configuration Summary (continued) Configuration Description CLI Commands RSTP protocol is disabled if redundant trunk groups are configured. set protocols rstp interface interface disable Desktop and Phone Port Role Set the port role to desktop and phone. set interfaces interfaceapply-macro juniper-port-profile Desktop and Phone Set data VLAN if new VLAN is specified. set vlans vlan-namevlan-id vlan id Set voice VLAN if new voice VLAN is specified. Set port family to ethernet-switching. set interfaces interfaceunit 0 family ethernet-switching port-mode access Set Port Mode to access. Set data VLAN on port stanza. set interfaces interface unit 0 family ethernet-switching vlan members vlan-members Set port security parameters. set ethernet-switching-options secure-access-port vlan MacTest arp-inspection Set VOIP VLAN. set ethernet-switching-options voip interface interface.0 vlan vlan vlan name Set class of service parameters set class-of-service interfaces interfacescheduler-map juniper-port-profile-map set class-of-service interfaces interface unit 0 classifiers ieee-802.1 juniper_ieee_classifier set class-of-service interfaces interfaceunit 0 classifiers dscp juniper-dscp-classifier SCHEDULER_MAP=juniper-port-profile-map IEEE_CLASSIFIER=juniper-ieee-classifier DSCP_CLASSIFIER=juniper-dscp-classifier Set CoS Configuration Refer to Table 126 on page 918 for details. Wireless Access Point Port Role Set the port role to wireless access point. set interfaces interface apply-macro juniper-port-profile Wireless Access Point Set VLAN on VLANs stanza. set vlans vlan namevlan-id vlan-id Set port family to ethernet-ewitching set interfaces interface unit 0 family ethernet-switching port-mode access Set port mode to Access. Set VLAN on port stanza. set interfaces interface unit 0 family ethernet-switching vlan members vlan-members Set RSTP protocol with edge option. set protocols rstp interface interface edge RSTP protocol is disabled if redundant trunk groups are configured. set protocols rstp interface interface disable Routed Uplink Port Role 916 Chapter 52: Configuring Interfaces Table 125: Port Role Configuration Summary (continued) Configuration Description CLI Commands Set the port role to Routed Uplink. set interfaces interface apply-macro juniper-port-profile Routed Uplink Set port family to inet. set interfaces interfaceunit 0 family inet address ipaddress Set IP address on the port. Set class-of-service parameters SCHEDULER_MAP=juniper-port-profile-map IEEE_CLASSIFIER=juniper-ieee-classifier DSCP_CLASSIFIER=juniper-dscp-classifier Set CoS configuration set class-of-service interfaces interfacescheduler-map juniper-port-profile-map set class-of-service interfaces interface unit 0 classifiers ieee-802.1 juniper_ieee_classifier set class-of-service interfaces interfaceunit 0 classifiers dscp juniper-dscp-classifier Refer to Table 126 on page 918 for details. Layer 2 Uplink Port Role Set the port role to Layer 2 Uplink. set interfaces interface apply-macro juniper-port-profile Layer2 Uplink Set port family to ethernet-switching set interfaces interface unit 0 family ethernet-switching port-mode trunk Set port mode to trunk. Set Native VLAN name. set interfaces interface unit 0 family ethernet-switching native-vlan-id vlan-name Set the port as part of all valid VLANs; ”valid" refers to all VLANs except native VLAN and voice VLANs. set interfaces interface unit 0 family ethernet-switching vlan members vlan-members Set port security parameter. set ethernet-switching-options secure-access-port dhcp-trusted Set RSTP protocol with point-to-point option. set protocols rstp interface interface mode point-to-point Disable RSTP if redundant trunk groups are configured. set protocols rstp interface interface disable Set class-of-service parameters. set class-of-service interfaces interfacescheduler-map juniper-port-profile-map set class-of-service interfaces interface unit 0 classifiers ieee-802.1 juniper_ieee_classifier set class-of-service interfaces interfaceunit 0 classifiers dscp juniper-dscp-classifier SCHEDULER_MAP=juniper-port-profile-map IEEE_CLASSIFIER=juniper_ieee_classifier DSCP_CLASSIFIER=juniper_dscp_classifier Set CoS configuration Refer to Table 126 on page 918 for details. Table 126 on page 918 lists the CLI commands for the recommended CoS settings that are committed when the CoS configuration is set. 917 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 126: Recommended CoS Settings for Port Roles CoS Parameter CLI Command Forwarding Classes voice set class-of-service forwarding-classes class voice queue-num 7 expedited-forwarding set class-of-service forwarding-classes class expedited-forwarding queue-num 5 assured-forwarding set class-of-service forwarding-classes class assured-forwarding queue-num 1 best-effort set class-of-service forwarding-classes class best-effort queue-num 0 Schedulers strict-priority-scheduler The CLI commands are: set class-of-service schedulers strict-priority-scheduler transmit-rate percent 10 set class-of-service schedulers strict-priority-scheduler buffer-size percent 5 set class-of-service schedulers strict-priority-scheduler priority strict-high expedited-scheduler The CLI commands are: set class-of-service schedulers expedited-scheduler transmit-rate percent 30 set class-of-service schedulers expedited-scheduler buffer-size percent 30 set class-of-service schedulers expedited-scheduler priority low assured-scheduler The CLI commands are: set class-of-service schedulers assured-scheduler transmit-rate percent 25 set class-of-service schedulers strict-priority-scheduler buffer-size percent 25 set class-of-service schedulers strict-priority-scheduler priority low best-effort-scheduler The CLI commands are: set class-of-service schedulers best-effort-scheduler transmit-rate percent 35 set class-of-service schedulers best-effort-scheduler buffer-size percent 40 set class-of-service schedulers best-effort-scheduler priority low Classifiers The classifiers are: set class-of-service classifiers ieee-802.1 juniper_ieee_classifier import default forwarding-class voice loss-priority low code-points 101 set class-of-service classifiers dscp juniper_dscp_classifier import default forwarding-class voice loss-priority low code-points 101110 Related Documentation 918 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 Chapter 52: Configuring Interfaces Configuring Gigabit Ethernet Interfaces (CLI Procedure) An Ethernet interface must be configured for optimal performance in a high-traffic network. J-EX Series switches include a factory default configuration that: • Enables all the network interfaces on the switch • Sets a default port mode (access) • Sets default link settings • Specifies a logical unit (unit 0) and assigns it to family ethernet-switching (except on J-EX8200 switches) • Specifies Rapid Spanning Tree Protocol (RSTP) and Link Layer Discovery Protocol (LLDP) This topic describes: • Configuring VLAN Options and Port Mode on page 919 • Configuring the Link Settings on page 919 • Configuring the IP Options on page 920 Configuring VLAN Options and Port Mode The factory default configuration includes a default VLAN and enables interfaces for the access port mode. Access interfaces typically connect to network devices such as PCs, printers, IP telephones, and IP cameras. If you are connecting a desktop phone or wireless access point or a security camera to a Power over Ethernet (PoE) port, you can configure some parameters for the PoE interface. The PoE interfaces are enabled by default. For detailed information on PoE settings, see “Configuring PoE (CLI Procedure)” on page 3021. If you are connecting a device to other switches and to routers on the LAN, you need to assign the interface to a logical port and configure the logical port as a trunk port. See “Port Role Configuration with the J-Web Interface (with CLI References)” on page 915 for more information about port configuration. To configure a Gigabit Ethernet interface or 10-Gigabit Ethernet interface for trunk port mode: [edit] user@switch# set interfaces interface-name unit logical-unit-number family ethernet-switching port-mode trunk Configuring the Link Settings J-EX Series switches include a factory default configuration that enables interfaces with the following link settings: 919 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • All Gigabit Ethernet interfaces are set to auto-negotiation. • The speed for Gigabit Ethernet interfaces is set to auto, allowing the interface to operate at 10m, 100m or 1g. The link operates at the highest possible speed, depending on the capabilities of the remote end. • The flow control for Gigabit Ethernet interfaces and 10-Gigabit Ethernet interfaces is set to enabled. • The link mode is set to auto, allowing the interface to operate as either full duplex or half duplex. The link operates as full duplex unless this mode is not supported at the remote end. • The 10-Gigabit Ethernet interfaces default to no auto-negotiation. The default speed is 10g and the default link mode is full duplex. To configure the link settings: • Set link settings for a Gigabit Ethernet interface: [edit] user@switch# set interfaces ge-fpc/pic/port ether-options • Set link settings for a 10-Gigabit Ethernet interface: [edit] user@switch# set interfaces xe-fpc/1/port ether-options NOTE: An uplink port in a J-EX4200 switch always has a PIC value of 1. For a J-EX4200 standalone switch, fpc refers to the switch itself and is always 0. In a Virtual Chassis configuration, fpc refers to the member ID. In a J-EX8200 switch, fpc refers to the line card number. The ether-options statement allows you to modify the configuration: • 802.3ad—Specify an aggregated Ethernet bundle. See “Configuring Aggregated Ethernet Interfaces (CLI Procedure)” on page 922. • auto-negotiation—Enable or disable autonegotation of flow control, link mode, and speed. • flow-control—Enable or disable flow control. • link-mode—Specify full-duplex, half-duplex, or automatic. • speed—Specify 10m, 100m, 1g, or autonegotiation. Configuring the IP Options To specify an IP address for the logical unit using IPv4: [edit] user@switch# set interfaces interface-name unit logical-unit-number family inet address ip-address To specify an IP address for the logical unit using IPv6: 920 Chapter 52: Configuring Interfaces [edit] user@switch# set interfaces interface-name unit logical-unit-number family inet6 address ip-address NOTE: Access interfaces on J-EX4200 switches are set to family ethernet-switching by default. You might have to delete this or another user-configured family setting before changing the setting to family inet or family inet6. Related Documentation • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Monitoring Interface Status and Traffic on page 931 • show interfaces ge- on page 1005 • show interfaces xe- on page 1019 • Understanding Interface Naming Conventions on J-EX Series Switches on page 865 Setting the Mode on an SFP+ Uplink Module (CLI Procedure) SFP+ uplink modules are supported on J-EX4200 switches. You can use these uplink modules either for two SFP+ transceivers or four SFP transceivers. You configure the operating mode on the module to match the type of transceiver you want to use—that is, for SFP+ transceivers, you configure the 10-gigabit operating mode, and for SFP transceivers, you configure the 1-gigabit operating mode. By default, the SFP+ uplink module operates in the 10-gigabit mode and supports only SFP+ transceivers. If you have not changed the module from the default setting and you want to use SFP+ transceivers, you do not need to configure the operating mode. To set the operating mode of an SFP+ uplink module, change the operating mode to the appropriate mode for the transceiver type you want to use by using one of the following commands: [edit] user@switch# set chassis fpc 0 pic 1 sfpplus pic-mode 1g [edit] user@switch# set chassis fpc 0 pic 1 sfpplus pic-mode 10g The changed operating mode takes effect immediately unless a port on the SFP+ uplink module is a Virtual Chassis port (VCP). If any port on the SFP+ uplink module is a VCP, the changed operating mode does not take effect until the next reboot of the switch. NOTE: During the operating mode change, the Packet Forwarding Engine is restarted. In a Virtual Chassis configuration, this means that the Flexible PIC Concentrator connection with the master is dropped and then reconnected. You can see whether the operating mode has been changed to the new mode you configured by issuing the show chassis pic fpc-slot slot-number pic-slot 1 command. 921 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Uplink Modules in J-EX4200 Switches • Optical Interface Support in J-EX4200 Switches Configuring Aggregated Ethernet Interfaces (CLI Procedure) Use the link aggregation feature to aggregate one or more links to form a virtual link or link aggregation group (LAG). The MAC client can treat this virtual link as if it were a single link. Link aggregation increases bandwidth, provides graceful degradation as failure occurs, and increases availability. NOTE: An interface with an already configured IP address cannot form part of the aggregation group. To configure aggregated Ethernet interfaces, using the CLI: 1. Specify the number of aggregated Ethernet interfaces to be created: [edit chassis] user@switch# set aggregated-devices ethernet device-count 2 2. Specify the minimum number of links for the aggregated Ethernet interface (aex), that is, the defined bundle, to be labeled “up”: NOTE: By default only one link must be up for the bundle to be labeled “up”. [edit interfaces] user@switch# set ae0 aggregated-ether-options minimum-links 2 3. Specify the link speed for the aggregated Ethernet bundle: [edit interfaces] user@switch# set ae0 aggregated-ether-options link-speed 10g 4. Specify the members to be included within the aggregated Ethernet bundle: [edit interfaces] user@switch# set xe-0/1/0 ether-options 802.3ad ae0 user@switch# set xe-1/1/0 ether-options 802.3ad ae0 5. Specify an interface family for the aggregated Ethernet bundle: [edit interfaces] user@switch# set ae0 unit 0 family inet address 192.0.2.0/25 For information about adding LACP to a LAG, see “Configuring Aggregated Ethernet LACP (CLI Procedure)” on page 926. Related Documentation 922 • Configuring Aggregated Ethernet Interfaces (J-Web Procedure) on page 923 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 Chapter 52: Configuring Interfaces • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Verifying the Status of a LAG Interface on page 932 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 Configuring Aggregated Ethernet Interfaces (J-Web Procedure) Use the link aggregation feature to aggregate one or more Ethernet interfaces to form a virtual link or link aggregation group (LAG) on a J-EX Series switch. The MAC client can treat this virtual link as if it were a single link. Link aggregation increases bandwidth, provides graceful degradation as failure occurs, and increases availability. You can use the J-Web interface to configure aggregated Ethernet interfaces, or a LAG, on the switch. NOTE: Interfaces that are already configured with MTU, duplex, flow control, or logical interfaces are listed but are not available for aggregation. To configure an aggregated Ethernet interface (also referred to as a LAG): 1. Select Configure > Interfaces > Link Aggregation. The list of aggregated interfaces is displayed. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one of the following: • Add—Creates an aggregated Ethernet interface, or LAG. Enter information as specified in Table 127 on page 924. • Edit—Modifies a selected LAG. • Aggregation—Modifies settings for the selected LAG. Enter information as specified in Table 127 on page 924. • VLAN—Specifies VLAN options for the selected LAG. Enter information as specified in Table 128 on page 925. • IP Option—Specifies IP options for the selected LAG. Enter information as specified in Table 129 on page 925. • Delete—Deletes the selected LAG. 923 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Disable Port or Enable Port—Disables or enables the administrative status on the selected interface. • Device Count—Configures the number of aggregated logical devices available to the switch. Select the number and click OK. Table 127: Aggregated Ethernet Interface Options Field Function Your Action Aggregated Interface Specifies the name of the aggregated interface. None. The name is supplied by the software. LACP Mode Specifies the mode in which LACP packets are exchanged between the interfaces. The modes are: Select from the list. • None—Indicates that no mode is applicable. • Active—Indicates that the interface initiates transmission of LACP packets • Passive—Indicates that the interface responds only to LACP packets. Description Specifies a description for the LAG. Enter a description. Interface Specifies the interfaces in the LAG. To add interfaces to the LAG, select the interfaces and click Add. Click OK. To remove an interface from the LAG, select the interface and click Remove. NOTE: Only interfaces that are configured with the same speed can be selected together for a LAG. Enable Log 924 Specifies whether to enable generation of log entries for the LAG. Select the check box to enable log generation, or clear the check box to disable log generation. Chapter 52: Configuring Interfaces Table 128: VLAN Options Field Function Your Action Port Mode Specifies the mode of operation for the port: trunk or access. If you select Trunk, you can: 1. Click Add to add a VLAN member. 2. Select the VLAN and click OK. 3. (Optional) Associate a native VLAN ID with the port. If you select Access, you can: 1. Select the VLAN member to be associated with the port. 2. (Optional) Associate a VoIP VLAN with the interface. Only a VLAN with a VLAN ID can be associated as a VoIP VLAN. Click OK. Table 129: IP Options Field Function Your Action IPv4 Address Specifies an IPv4 address for the selected LAG. 1. Select the check box IPv4 address. 2. Type an IP address—for example, 10.10.10.10. 3. Enter the subnet mask or address prefix. For example, 24 bits represents 255.255.255.0. 4. Click OK. IPv6 Address Specifies an IPv6 address for the selected LAG. 1. Select the check box IPv6 address. 2. Type an IP address—for example, 2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. 4. Click OK. Related Documentation • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Verifying the Status of a LAG Interface on page 932 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 925 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Aggregated Ethernet LACP (CLI Procedure) For aggregated Ethernet interfaces on J-EX Series switches, you can configure the Link Aggregation Control Protocol (LACP). LACP is one method of bundling several physical interfaces to form one logical interface. You can configure aggregated Ethernet with or without LACP enabled. Before you configure LACP, be sure you have: • Configured the aggregated Ethernet bundles—also known as link aggregation groups (LAGs). See “Configuring Aggregated Ethernet Interfaces (CLI Procedure)” on page 922 When LACP is enabled, the local and remote sides of the aggregated Ethernet links exchange protocol data units (PDUs), containing information about the state of the link. You can configure Ethernet links to actively transmit PDUs, or you can configure the links to passively transmit them, sending out LACP PDUs only when they receive them from another link. One side of the link must be configured as active for the link to be up. NOTE: Do not add LACP to a LAG if the remote end of the LAG link is a security device, unless the security device supports LACP. Security devices often do not support LACP because they require a deterministic configuration. To configure LACP: 1. Enable one side of the aggregated Ethernet link as active: [edit interfaces] user@switch# set aex aggregated-ether-options lacp active 2. Specify the interval at which the interfaces send LACP packets: [edit interfaces] user@switch# set aex aggregated-ether-options lacp periodic fast Related Documentation 926 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet Interfaces (J-Web Procedure) on page 923 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Verifying the Status of a LAG Interface on page 932 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 Chapter 52: Configuring Interfaces Configuring Unicast RPF (CLI Procedure) Unicast reverse-path forwarding (RPF) can help protect your LAN from denial-of-service (DoS) and distributed denial-of-service (DDoS) attacks on untrusted interfaces. Enabling unicast RPF on the switch interfaces filters traffic with source addresses that do not use the incoming interface as the best return path back to the source. When a packet comes into an interface, if that interface is not the best return path to the source, the switch discards the packet. If the incoming interface is the best return path to the source, the switch forwards the packet. NOTE: On J-EX4200 switches, you can only enable unicast RPF globally, on all switch interfaces. You cannot enable unicast RPF on a per-interface basis. Before you begin: • On a J-EX8200 switch, ensure that the selected switch interface is symmetrically routed before you enable unicast RPF. A symmetrically routed interface is an interface that uses the same route in both directions between the source and the destination. Do not enable unicast RPF on asymmetrically routed interfaces. An asymmetrically routed interface uses different paths to send and receive packets between the source and the destination. • On a J-EX4200 switch, ensure that all switch interfaces are symmetrically routed before you enable unicast RPF on an interface. When you enable unicast RPF on any interface, it is enabled globally on all switch interfaces. Do not enable unicast RPF on asymmetrically routed interfaces. An asymmetrically routed interface uses different paths to send and receive packets between the source and the destination. To enable unicast RPF, configure it explicitly on a selected customer-edge interface: [edit interfaces] user@switch# set ge-1/0/10 unit 0 family inet rpf-check BEST PRACTICE: On J-EX4200 switches, unicast RPF is enabled globally on all switch interfaces, regardless of whether you configure it explicitly on only one interface or only on some interfaces. On J-EX4200 switches, we recommend that you enable unicast RPF explicitly on either all interfaces or only one interface. To avoid possible confusion, do not enable it on only some interfaces: • Enabling unicast RPF explicitly on only one interface makes it easier if you choose to disable it in the future because you must explicitly disable unicast RPF on every interface on which you explicitly enabled it. If you explicitly enable unicast RPF on two interfaces and you disable it on only one interface, unicast RPF is still implicitly enabled globally on the switch. The drawback to this approach is that the switch displays the flag that indicates 927 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS that unicast RPF is enabled only on interfaces on which unicast RPF is explicitly enabled, so even though unicast RPF is enabled on all interfaces, this status is not displayed. • Related Documentation Enabling unicast RPF explicitly on all interfaces makes it easier to know whether unicast RPF is enabled on the switch because every interface shows the correct status. (Only interfaces on which you explicitly enable unicast RPF display the flag that indicates that unicast RPF is enabled.) The drawback to this approach is that if you want to disable unicast RPF, you must explicitly disable it on every interface. If unicast RPF is enabled on any interface, it is implicitly enabled on all interfaces. • Example: Configuring Unicast RPF on a J-EX Series Switch on page 900 • Verifying Unicast RPF Status on page 935 • Disabling Unicast RPF (CLI Procedure) on page 928 • Troubleshooting Unicast RPF on page 941 • Understanding Unicast RPF for J-EX Series Switches on page 872 Disabling Unicast RPF (CLI Procedure) Unicast reverse-path forwarding (RPF) can help protect your LAN from denial-of-service (DoS) and distributed denial-of-service (DDoS) attacks on untrusted interfaces. Unicast RPF filters traffic with source addresses that do not use the incoming interface as the best return path back to the source. If the network configuration changes so that an interface that has unicast RPF enabled becomes a trusted interface or becomes asymmetrically routed (the interface that receives a packet is not the best return path to the packet’s source), disable unicast RPF. To disable unicast RPF on a J-EX4200 switch, you must delete it from every interface on which you explicitly configured it. If you do not disable unicast RPF on every interface on which you explicitly enabled it, it remains implicitly enabled on all interfaces. If you attempt to delete unicast RPF from an interface on which it was not explicitly enabled, the message warning: statement not found displays. If you do not disable unicast RPF on every interface on which you explicitly enabled it, unicast RPF remains implicitly enabled on all interfaces of the J-EX4200 switch. On J-EX8200 switches, the switch does not apply unicast RPF to an interface unless you explicitly enable that interface for unicast RPF. 928 Chapter 52: Configuring Interfaces To disable unicast RPF, delete its configuration from the interface: [edit interfaces] user@switch# delete ge-1/0/10 unit 0 family inet rpf-check NOTE: On J-EX4200 switches, if you do not disable unicast RPF on every interface on which you explicitly enabled it, unicast RPF remains implicitly enabled on all interfaces. Related Documentation • Example: Configuring Unicast RPF on a J-EX Series Switch on page 900 • Verifying Unicast RPF Status on page 935 • Configuring Unicast RPF (CLI Procedure) on page 927 • Understanding Unicast RPF for J-EX Series Switches on page 872 Configuring IP Directed Broadcast (CLI Procedure) You can use IP directed broadcast on a J-EX Series switch to facilitate remote network management by sending broadcast packets to hosts on a specified subnet without broadcasting to the entire network. IP directed broadcast packets are broadcast on only the target subnet. The rest of the network treats IP directed broadcast packets as unicast packets and forwards them accordingly. Before you begin to configure IP directed broadcast: • Ensure that the subnet on which you want broadcast packets using IP direct broadcast is not directly connected to the Internet. • Configure a routed VLAN interface (RVI) for the subnet that will be enabled for IP direct broadcast. See “Configuring Routed VLAN Interfaces (CLI Procedure)” on page 1137 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. NOTE: We recommend that you do not enable IP directed broadcast on subnets that have a direct connection to the Internet because of increased exposure to denial-of-service (DoS) attacks. To enable IP directed broadcast for a specified subnet: 1. Add the target subnet’s logical interfaces to the VLAN: [edit interfaces] user@switch# set ge-0/0/0.0 family ethernet-switching vlan members v1 user@switch# set ge-0/0/1.0 family ethernet-switching vlan members v1 2. Configure the Layer 3 interface on the VLAN that is the target of the IP directed broadcast packets: 929 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit interfaces] user@switch# set vlan.1 family inet address 10.1.2.1/24 3. Associate a Layer 3 interface with the VLAN: [edit vlans] user@switch# set v1 l3-interface vlan.1 4. Enable the Layer 3 interface for the VLAN to receive IP directed broadcasts: [edit interfaces] user@switch# set vlan.1 family inet targeted-broadcast Related Documentation • Example: Configuring IP Directed Broadcast on a J-EX Series Switch on page 904 • Understanding IP Directed Broadcast for J-EX Series Switches on page 876 Configuring a Layer 3 Subinterface (CLI Procedure) J-EX Series switches use Layer 3 subinterfaces to divide a physical interface into multiple logical interfaces, each corresponding to a VLAN. The switch uses the Layer 3 subinterfaces to route traffic between subnets. To configure Layer 3 subinterfaces, you enable VLAN tagging and partition one or more physical ports into multiple logical interfaces, each corresponding to a VLAN ID. Before you begin, make sure you set up your VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. To configure Layer 3 subinterfaces: 1. Enable VLAN tagging: [edit interfaces interface-name] user@switch# set vlan-tagging 2. Bind each VLAN ID to a logical interface: [edit interfaces interface-name] user@switch# set unit logical-unit-number vlan-id vlan-id-number Related Documentation 930 • Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch on page 893 • Verifying That Layer 3 Subinterfaces Are Working on page 934 • Understanding Layer 3 Subinterfaces on page 871 CHAPTER 53 Verifying Interfaces • Monitoring Interface Status and Traffic on page 931 • Verifying the Status of a LAG Interface on page 932 • Verifying That LACP Is Configured Correctly and Bundle Members Are Exchanging LACP Protocol Packets on page 933 • Verifying That Layer 3 Subinterfaces Are Working on page 934 • Verifying Unicast RPF Status on page 935 • Verifying IP Directed Broadcast Status on page 937 Monitoring Interface Status and Traffic Purpose Use the monitoring functionality to view interface status or to monitor interface bandwidth utilization and traffic statistics on the J-EX Series switches. The J-Web interface monitors interface bandwidth utilization and plots real-time charts to display input and output rates in bytes per second. In addition, the Interface monitoring page displays input and output packet counters and error counters in the form of charts. Alternatively, you can enter the show commands in the CLI to view interface status and traffic statistics. Action To view general interface information in the J-Web interface such as available interfaces, select Monitor > Interfaces. Click any interface to view details about its status. To set up interface monitoring for Virtual Chassis and J-EX8200 switches, select a member from the Port for FPC list. Details such as the admin status and link status are displayed in the table. NOTE: By default, the details of the first member in the Port for FPC drop-down list is displayed. You have the following options: • Start/Stop—Starts or stops monitoring the selected interface. • Show Graph—Displays input and output packet counters and error counters in the form of charts. Also, click on the pop-up icon to view the graph in a separate window. 931 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Details—Displays interface information such as general details, traffic statistics, I/O errors, CoS counters, and Ethernet statistics. • Refresh Interval (sec)—Displays the time interval you have set for page refresh. • Clear Statistics—Clears the statistics for the interface selected from the table. Using the CLI: Meaning • To view interface status for all the interfaces, enter show interfaces xe-. • To view status and statistics for a specific interface, enter show interfaces xe-interface-name. • To view status and traffic statistics for all interfaces, enter either show interfaces xedetail or show interfaces xe- extensive. In the J-Web interface the charts displayed are: • Bar charts—Display the input and output error counters. • Pie charts—Display the number of broadcast, unicast, and multicast packet counters. For details about output from the CLI commands, see show interfaces ge- (Gigabit Ethernet) or show interfaces xe- (10-Gigabit Ethernet). Related Documentation • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 Verifying the Status of a LAG Interface Purpose Action Verify that a LAG (ae0) has been created on the switch. show interfaces aeo terse Interface Meaning Related Documentation 932 Admin Link ae0 up up ae0.0 up up Proto inet Local Remote 10.10.10.2/24 The output confirms that the ae0 link is up and shows the family and IP address assigned to this link. • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet Interfaces (J-Web Procedure) on page 923 Chapter 53: Verifying Interfaces • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 Verifying That LACP Is Configured Correctly and Bundle Members Are Exchanging LACP Protocol Packets To verify that LACP has been set up correctly and that the bundle members are transmitting LACP protocol packets. 1. Verifying the LACP Setup on page 933 2. Verifying That the LACP Packets Are Being Exchanged on page 933 Verifying the LACP Setup Purpose Action Verify that the LACP has been set up correctly. Use the show lacp interfaces interface-name command to check that LACP has been enabled as active on one end. show lacp interfaces xe-0/1/0 show lacp interfaces xe-0/1/0 Aggregated interface: ae0 LACP state: Role Def Dist Col Syn Aggr Timeout Activity xe-0/1/0 Actor No Yes No No No Yes Fast Active xe-0/1/0 Partner No Yes No No No Yes Fast Passive LACP protocol: xe-0/1/0 Meaning Exp Receive State Defaulted Transmit State Mux State Fast periodic Detached This example shows that LACP has been configured with one side as active and the other as passive. When LACP is enabled, one side must be set as active in order for the bundled link to be up. Verifying That the LACP Packets Are Being Exchanged Purpose Action Verify that LACP packets are being exchanged between interfaces. Use the show interfaces aex statistics command to display LACP BPDU exchange information. show interfaces ae0 statistics Physical interface: ae0, Enabled, Physical link is Down Interface index: 153, SNMP ifIndex: 30 Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, Loopback: Disabled, 933 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Source filtering: Disabled, Flow control: Disabled, Minimum links needed: 1, Minimum bandwidth needed: 0 Device flags : Present Running Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Current address: 02:19:e2:50:45:e0, Hardware address: 02:19:e2:50:45:e0 Last flapped : Never Statistics last cleared: Never Input packets : 0 Output packets: 0 Input errors: 0, Output errors: 0 Logical interface ae0.0 (Index 71) (SNMP ifIndex 34) Flags: Hardware-Down Device-Down SNMP-Traps Encapsulation: ENET2 Statistics Packets pps Bytes bps Bundle: Input : 0 0 0 0 Output: 0 0 0 0 Protocol inet, Flags: None Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255 Meaning Related Documentation The output here shows that the link is down and that no PDUs are being exchanged (when there is no other traffic flowing on the link). • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Verifying the Status of a LAG Interface on page 932 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 Verifying That Layer 3 Subinterfaces Are Working Purpose Action After configuring Layer 3 subinterfaces, verify they are set up properly and transmitting data. 1. Use the show interfaces command to determine if you successfully created the subinterfaces and the links are up: user@switch> show interfaces interface-name terse Interface ge-0/0/0 ge-0/0/0.0 ge-0/0/0.1 ge-0/0/0.2 ge-0/0/0.3 ge-0/0/0.4 ge-0/0/0.32767 Admin up up up up up up up Link up up up up up up up Proto Local inet inet inet inet inet 1.1.1.1/24 2.1.1.1/24 3.1.1.1/24 4.1.1.1/24 5.1.1.1/24 Remote 2. Use the ping command from a device on one subnet to an address on another subnet to determine if packets were transmitted correctly on the subinterface VLANs: user@switch> ping ip-address 934 Chapter 53: Verifying Interfaces PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=64 time=0.157 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.238 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=0.255 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.128 ms --- 1.1.1.1 ping statistics --4 packets transmitted, 4 packets received, 0% packet loss Meaning Related Documentation The output confirms that the subinterfaces are created and the links are up. • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch on page 893 Verifying Unicast RPF Status Purpose Action Verify that unicast reverse-path forwarding (RPF) is enabled and is working on the interface. Use one of the show interfaces interface-name commands with either the extensive or detail options to verify that unicast RPF is enabled and working on the switch. The example below displays output from the show interfaces ge- extensive command. user@switch> show interfaces ge-1/0/10 extensive Physical interface: ge-1/0/10, Enabled, Physical link is Down Interface index: 139, SNMP ifIndex: 58, Generation: 140 Link-level type: Ethernet, MTU: 1514, Speed: Auto, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:19:e2:50:95:ab, Hardware address: 00:19:e2:50:95:ab Last flapped : Never Statistics last cleared: Never Traffic statistics: Input bytes : 0 0 bps Output bytes : 0 0 bps Input packets: 0 0 pps Output packets: 0 0 pps IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0 Output errors: Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 4 in use 935 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 0 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 0 0 Active alarms : LINK Active defects : LINK MAC statistics: Receive Total octets 0 Total packets 0 Unicast packets 0 Broadcast packets 0 Multicast packets 0 CRC/Align errors 0 FIFO errors 0 MAC control frames 0 MAC pause frames 0 Oversized frames 0 Jabber frames 0 Fragment frames 0 VLAN tagged frames 0 Code violations 0 Filter statistics: Input packet count 0 Input packet rejects 0 Input DA rejects 0 Input SA rejects 0 Output packet count Output packet pad count Output packet error count CAM destination filters: 0, CAM source filters: 0 Autonegotiation information: Negotiation status: Incomplete Packet Forwarding Engine configuration: Destination slot: 1 Transmit 0 0 0 0 0 0 0 0 0 0 0 0 Logical interface ge-1/0/10.0 (Index 69) (SNMP ifIndex 59) (Generation 135) Flags: Device-Down SNMP-Traps 0x0 Encapsulation: ENET2 Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Local statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Transit statistics: Input bytes : 0 0 bps Output bytes : 0 0 bps 936 Chapter 53: Verifying Interfaces Input packets: 0 Output packets: 0 IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Protocol inet, Generation: 144, Route table: 0 Flags: uRPF Addresses, Flags: Is-Preferred Is-Primary Meaning 0 pps 0 pps The show interfaces ge-1/0/10 extensive command (and the show interfaces ge-1/0/10 detail command) displays in-depth information about the interface. The Flags: output field near the bottom of the display reports the unicast RPF status. If unicast RPF has not been enabled, the uRPF flag is not displayed. On J-EX4200 switches, unicast RPF is implicitly enabled on all switch interfaces, including aggregated Ethernet interfaces (also referred to as link aggregation groups or LAGs) and routed VLAN interfaces (RVIs) when you enable unicast RPF on a single interface. However, the unicast RPF status is shown as enabled only on interfaces for which you have explicitly configured unicast RPF. Thus, the uRPF flag is not displayed on interfaces for which you have not explicitly configured unicast RPF even though unicast RPF is implicitly enabled on all interfaces on J-EX4200 switches. Related Documentation • show interfaces xe- on page 1019 • Example: Configuring Unicast RPF on a J-EX Series Switch on page 900 • Configuring Unicast RPF (CLI Procedure) on page 927 • Disabling Unicast RPF (CLI Procedure) on page 928 • Troubleshooting Unicast RPF on page 941 Verifying IP Directed Broadcast Status Purpose Action Related Documentation Verify that IP directed broadcast is enabled and is working on the subnet. Use the show vlans extensive command to verify that IP directed broadcast is enabled and working on the subnet as shown in the following example. • Configuring IP Directed Broadcast (CLI Procedure) on page 929 • Example: Configuring IP Directed Broadcast on a J-EX Series Switch on page 904 937 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 938 CHAPTER 54 Troubleshooting Interfaces • Troubleshooting Network Interfaces on J-EX4200 Switches on page 939 • Troubleshooting an Aggregated Ethernet Interface on page 940 • Troubleshooting Interface Configuration and Cable Faults on page 940 • Troubleshooting Unicast RPF on page 941 • Troubleshooting Uplink Module Installation or Replacement on J-EX4200 Switches on page 942 Troubleshooting Network Interfaces on J-EX4200 Switches This topic provides troubleshooting information for specific problems related to interfaces on J-EX4200 switches. • The interface on the port in which an SFP or SFP+ transceiver is installed in an SFP+ uplink module is down on page 939 The interface on the port in which an SFP or SFP+ transceiver is installed in an SFP+ uplink module is down Problem The interface on the port in which an SFP or SFP+ transceiver is installed in an SFP+ uplink module installed in a J-EX4200 switch is down. When you check the status with the CLI command show interfaces ge- or with the J-Web user interface, the disabled port is not listed. Cause Solution Related Documentation By default, the SFP+ uplink module operates in the 10-gigabit mode and supports only SFP+ transceivers. The operating mode for the module is incorrectly set. Either SFP+ or SFP transceivers can be installed in SFP+ uplink modules. You must configure the operating mode of the SFP+ uplink module to match the type of transceiver you want to use. For SFP+ transceivers, configure the 10-gigabit operating mode and for SFP transceivers, configure the 1-gigabit operating mode. See “Setting the Mode on an SFP+ Uplink Module (CLI Procedure)” on page 921. • Troubleshooting Uplink Module Installation or Replacement on J-EX4200 Switches on page 942 • Monitoring Interface Status and Traffic on page 931 939 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Removing a Transceiver from a J-EX Series Switch • Uplink Modules in J-EX4200 Switches • J-EX Series Switches Interfaces Overview on page 863 Troubleshooting an Aggregated Ethernet Interface Problem The show interfaces terse command shows that the LAG is down. Solution Check the following: Related Documentation • Verify that there is no configuration mismatch. • Verify that all member ports are up. • Verify that a LAG is part of family ethernet—switching (Layer 2 LAG) or family inet (Layer 3 LAG). • Verify that the LAG member is connected to the correct LAG at the other end. • Verify that the LAG members belong to the same switch (or the same Virtual Chassis). • Verifying the Status of a LAG Interface on page 932 • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 Troubleshooting Interface Configuration and Cable Faults Troubleshooting interface configuration and connectivity on the J-EX Series switch: 1. Interface Configuration or Connectivity Is Not Working on page 940 Interface Configuration or Connectivity Is Not Working Problem You encounter errors when you attempt to configure an interface on the switch, or the interface is exhibiting connectivity problems. Solution Use the port troubleshooter feature in the J-Web interface to identify and rectify port configuration and connectivity related problems. To use the J-Web interface port troubleshooter: 1. Select the option Troubleshoot from the main menu. 2. Click Troubleshoot Port. The Port Troubleshooting wizard is displayed. Click Next. 940 Chapter 54: Troubleshooting Interfaces 3. Select the ports to troubleshoot. 4. Select the test cases to be executed on the selected port. Click Next. When the selected test cases are executed, the final result and the recommended action is displayed. If there is a cable fault, the port troubleshooter displays details and the recommended action. For example, the cable must be replaced. If the port configuration needs to be modified, the port troubleshooter displays details and the recommended action. Related Documentation • Monitoring Interface Status and Traffic on page 931 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 161 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 163 Troubleshooting Unicast RPF Troubleshooting issues for unicast reverse-path forwarding (RPF) on J-EX Series switches include: 1. Legitimate Packets Are Discarded on page 941 Legitimate Packets Are Discarded Problem The switch filters valid packets from legitimate sources, which results in the switch's discarding packets that should be forwarded. Solution The interface or interfaces on which legitimate packets are discarded are asymmetrically routed interfaces. An asymmetrically routed interface uses different paths to send and receive packets between the source and the destination, so the interface that receives a packet is not the same interface the switch uses to reply to the packet's source. Unicast RPF works properly only on symmetrically routed interfaces. A symmetrically routed interface is an interface that uses the same route in both directions between the source and the destination. Unicast RPF filters packets by checking the forwarding table for the best return path to the source of an incoming packet. If the best return path uses the same interface as the interface that received the packet, the switch forwards the packet. If the best return path uses a different interface than the interface that received the packet, the switch discards the packet. 941 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: On J-EX4200 switches, unicast RPF works properly only if all switch interfaces—including aggregated Ethernet interfaces (also referred to as link aggregation groups or LAGs) and routed VLAN interfaces (RVIs)—are symmetrically routed, because unicast RPF is enabled globally on all switch interfaces. Related Documentation • Verifying Unicast RPF Status on page 935 • Understanding Unicast RPF for J-EX Series Switches on page 872 Troubleshooting Uplink Module Installation or Replacement on J-EX4200 Switches This topic provides troubleshooting information for specific problems related to uplink module ports on J-EX4200 switches. 1. Virtual Chassis port (VCP) connection does not work on page 942 Virtual Chassis port (VCP) connection does not work Problem The Virtual Chassis port (VCP) connection configured in a J-EX4200 switch does not work. A port of the uplink module is set as a VCP. Cause Solution Related Documentation 942 The uplink module installed in the switch was replaced. Set a port in the uplink module as a VCP. See “Setting an Uplink Module Port as a Virtual Chassis Port (CLI Procedure)” on page 792. • Monitoring Interface Status and Traffic on page 931 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Installing an Uplink Module in a J-EX4200 Switch • Removing a Transceiver from a J-EX Series Switch • Uplink Modules in J-EX4200 Switches • Understanding Virtual Chassis Hardware Configuration on a J-EX4200 Switch CHAPTER 55 Configuration Statements for Interfaces • [edit chassis] Configuration Statement Hierarchy on page 943 • [edit interfaces] Configuration Statement Hierarchy on page 943 [edit chassis] Configuration Statement Hierarchy chassis { aggregated-devices { ethernet { device-count number; } } auto-image-upgrade; } fpc slot { pic pic-number { sfpplus { pic-mode mode; power-budget-priority priority; } lcd-menu fpc slot-number { menu-item (menu-name | menu-option); } } psu { redundancy { n-plus-n; } } redundancy{ graceful-switchover ; } Related Documentation • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Understanding Power Management on J-EX Series Switches on page 302 [edit interfaces] Configuration Statement Hierarchy interfaces { aex { 943 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS aggregated-ether-options { (flow-control | no-flow-control); lacp mode { periodic interval; } link-speed speed; minimum-links number; } description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } fe-fpc/pic/port { description text; disable; mtu bytes; no-gratuitous-arp-request; speed speed; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } ge-fpc/pic/port { description text; disable; ether-options { 802.3ad aex { lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; speed (auto-negotiation | speed); 944 Chapter 55: Configuration Statements for Interfaces } hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } interface-range interface-range name { description text; disable; ether-options { 802.3ad aex { lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control| no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; member interface-name; member-range starting-interface name to ending-interface name; mtu bytes; unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } } lo0 { description text; disable; hold-time up milliseconds down milliseconds; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); 945 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } me0 { description text; disable; hold-time up milliseconds down milliseconds; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } vlan { description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); } } vme { description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } xe-fpc/pic/port { description text; disable; ether-options { 802.3ad aex { 946 Chapter 55: Configuration Statements for Interfaces lacp (802.3ad) { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } } Related Documentation • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) on page 797 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 947 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 802.3ad Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 802.3ad aex { lacp { force-up; } [edit interfaces interface-name ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the aggregated Ethernet logical interface number. aex—Aggregated Ethernet logical interface number. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 948 Chapter 55: Configuration Statements for Interfaces aggregated-devices Syntax Hierarchy Level Release Information Description aggregated-devices { ethernet { device-count number; } } [edit chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure properties for aggregated devices on the switch. The statements are explained separately. Default Required Privilege Level Related Documentation Disabled. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 949 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS aggregated-ether-options Syntax Hierarchy Level Release Information Description 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; } [edit interfaces (for EX Series switches) aex] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the aggregated Ethernet properties of a specific aggregated Ethernet interface. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 950 Chapter 55: Configuration Statements for Interfaces auto-negotiation Syntax Hierarchy Level Release Information Description (auto-negotiation | no-auto-negotiation); [edit interfaces interface-name ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Explicitly enable or disable autonegotiation. • auto-negotiation—Enable autonegotiation. • no-auto-negotiation—Disable autonegotiation. When autonegotiation is disabled, you must explicitly configure link mode and speed options. Default Required Privilege Level Related Documentation Autonegotiation is automatically enabled. No explicit action is taken after the autonegotiation is complete or if the negotiation fails. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 951 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS chassis Syntax Hierarchy Level Release Information Description 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 (Power Management) { n-plus-n; } } redundancy { graceful-switchover; } } [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure chassis-specific properties. The remaining statements are explained separately. Required Privilege Level Related Documentation 952 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 82 Chapter 55: Configuration Statements for Interfaces • Configuring Graceful Routing Engine Switchover in a Virtual Chassis Configuration (CLI Procedure) on page 801 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 308 • Configuring Power Supply Redundancy (CLI Procedure) on page 307 • Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/ description Syntax Hierarchy Level Release Information Description Default Options description text; [edit interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Provide a textual description of the interface or the logical unit. Any descriptive text you include is displayed in the output of the show interfaces commands and is also exposed in the ifAlias Management Information Base (MIB) object. It has no effect on the operation of the interface or the switch. No textual description is configured. text—Text to describe the interface. If the text includes spaces, enclose the entire text in straight quotation marks. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 953 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS device-count Syntax Hierarchy Level Release Information Description Default Options device-count number; [edit chassis aggregated-devices ethernet] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the number of aggregated Ethernet logical devices available to the switch. There is no default. You must configure a value. number—Maximum number of aggregated Ethernet logical interfaces on the switch. Range: 1 through 64 for J-EX4200 switches 1 through 255 for J-EX8200 switches Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 954 Chapter 55: Configuration Statements for Interfaces ether-options Syntax Hierarchy Level Release Information Description ether-options { 802.3ad aex { lacp { force-up; } } auto-negotiation; flow-control; link-mode mode; speed (speed | auto-negotiation); } [edit interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure ether-options properties for a Gigabit Ethernet interface on the J-EX Series switch. The remaining statements are explained separately. Default Required Privilege Level Related Documentation Enabled. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 955 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ethernet Syntax Hierarchy Level Release Information Description ethernet { device-count number; } [edit chassis aggregated-devices] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure properties for Ethernet aggregated devices on the switch. The remaining statement is explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/index.html 956 Chapter 55: Configuration Statements for Interfaces family (for J-EX Series switches) Syntax family ccc family ethernet-switching family inet family inet6 family ccc on page 957 family ethernet-switching on page 957 family inet on page 957 family inet6 on page 957 family iso on page 958 family mpls on page 958 family ccc; family ethernet-switching { filter input filter-name; filter output filter-name; native-vlan-id vlan-id; port-mode mode; vlan { members [ (all | names | vlan-ids) ]; } } family inet { address address { primary; vrrp-group group-id { advertise-interval milliseconds; preempt | no-preempt { hold-time seconds; } priority number; virtual-address [addresses]; virtual-link-local-address ip-address; } } filter input filter-name; filter output filter-name; primary; rpf-check; targeted-broadcast; } family inet6 { address address { primary; vrrp-inet6-group group-id { inet6-advertise-interval milliseconds; preempt | no-preempt { hold-time seconds; } priority number; virtual-inet6-address [addresses]; virtual-link-local-address ipv6–address; } } 957 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS filter input filter-name; filter output filter-name; policer input policer-name; policer output policer-name; rpf-check; } family iso family mpls Hierarchy Level Release Information Description family iso { address interface-address; } family mpls; [edit interfaces interface-name unit logical-unit-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure protocol family information for the logical interface on the switch. Most standard Junos OS configuration statements are available in Junos OS for J-EX Series switches. This topic lists standard Junos OS statements that you commonly use when configuring protocol families for interfaces on J-EX Series switches as well as statements that are used to configure protocol families only on switch interfaces. For information about additional standard Junos OS statements that you can configure on interfaces, see the Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Default Access interfaces on J-EX4200 switches are set to family ethernet-switching by default. If you are going to change the family setting for an interface, you might have to delete this default setting or any user-configured family setting before you change the setting to another family type. J-EX8200 switch interfaces do not have a default family setting. You must configure a logical interface to be able to use the physical device. 958 Chapter 55: Configuration Statements for Interfaces Options See Table 130 on page 959 for protocol families available on the switch interfaces. Different protocol families support different subsets of the interfaces types on the switch. Interface types on the switch are: • Aggregated Ethernet (ae) • Gigabit Ethernet (ge) • Interface-range configuration (interface-range) • Loopback (lo0) • Management Ethernet (me0) • Routed VLAN interface (RVI) (vlan) • Virtual management Ethernet (vme) • 10-Gigabit Ethernet (xe) If you are using an interface range, the supported protocol families are the ones supported by the interface types that compose the range. Not all interface types support all family substatements. Check your switch CLI for supported substatements for a particular protocol family configuration. Table 130: Protocol Families and Supported Interface Types Supported Interface Types Family Description ae ge lo0 me0 vlan vme xe ccc Circuit cross-connect protocol family ✓ ✓ ethernetswitching Ethernet switching protocol family ✓ ✓ inet IPv4 protocol family ✓ ✓ ✓ ✓ ✓ ✓ ✓ inet6 IPv6 protocol family ✓ ✓ ✓ ✓ ✓ ✓ ✓ iso Junos OS protocol family for IS-IS traffic ✓ ✓ ✓ ✓ ✓ ✓ ✓ mpls MPLS protocol family ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ The remaining statements are explained separately. Required Privilege Level interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. 959 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ filter Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation filter (input | output) filter-name; [edit interfaces interface-name unit logical-unit-number family ethernet-switching], [edit interfaces interface-name unit logical-unit-number family inet], [edit interfaces interface-name unit logical-unit-number family inet6] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a firewall filter to traffic entering the port or Layer 3 interface or exiting the Layer 3 interface. All incoming traffic is accepted unmodified on the port or Layer 3 interface, and all outgoing traffic is sent unmodified from the port or Layer 3 interface. filter-name—Name of a firewall filter defined in the filter statement. • input—Apply a firewall filter to traffic entering the port or Layer 3 interface. • output—Apply a firewall filter to traffic exiting the Layer 3 interface. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 960 Chapter 55: Configuration Statements for Interfaces flow-control Syntax Hierarchy Level Release Information Description (flow-control | no-flow-control); [edit interfaces interface-name ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Explicitly enable flow control, which regulates the flow of packets from the switch to the remote side of the connection, or disable it. • flow-control—Enable flow control; flow control is useful when the remote device is a Gigabit Ethernet switch. • Default Required Privilege Level Related Documentation no-flow-control—Disable flow control. Flow control enabled. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ force-up Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation force-up; [edit interfaces interface-name ether-options 802.3ad lacp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the state of the interface as UP when the peer has limited LACP capability. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 961 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface-range Syntax Hierarchy Level Release Information Description interface-range interface-range name { ether-options { 802.3ad aex ; auto-negotiation; flow-control; link-mode mode; speed ( speed | auto-negotiation) ; } hold-time up milliseconds down milliseconds; member interface-name; member-range starting-interface name to ending-interface name; mtu bytes; } [edit interfaces] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Group interfaces that share a common configuration profile. NOTE: The interface range definition is supported only for Gigabit, 10-Gigabit, and Fast Ethernet interfaces. Options interface-range-name—Name of the interface range. NOTE: You can use regular expressions and wildcards to specify the interfaces in the member-range configuration. Do not use wildcards for interface types. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Understanding Interface Ranges on J-EX Series Switches on page 869 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 962 Chapter 55: Configuration Statements for Interfaces interfaces (for J-EX Series switches) Syntax interfaces ae on page 963 interfaces ge on page 963 interfaces interface-range on page 964 interfaces lo0 on page 965 interfaces me0 on page 965 interfaces vlan on page 965 interfaces vme on page 966 interfaces xe on page 966 interfaces ae aex { aggregated-ether-options { (flow-control | no-flow-control); lacp mode { periodic interval; } link-speed speed; minimum-links number; } description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } interfaces ge ge-fpc/pic/port { description text; disable; ether-options { 802.3ad aex { lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; 963 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } interfaces interface-range 964 interface-range interface-range name { description text; disable; ether-options { 802.3ad aex { lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control| no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; member interface-name; member-range starting-interface name to ending-interface name; mtu bytes; unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } } Chapter 55: Configuration Statements for Interfaces interfaces lo0 lo0 { description text; disable; hold-time up milliseconds down milliseconds; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); } } interfaces me0 me0 { description text; disable; hold-time up milliseconds down milliseconds; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } interfaces vlan vlan { description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); } } 965 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interfaces vme vme { description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } interfaces xe xe-fpc/pic/port { description text; disable; ether-options { 802.3ad aex { lacp (802.3ad) { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } Hierarchy Level Release Information 966 [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Chapter 55: Configuration Statements for Interfaces Description Configure interfaces on J-EX Series switches. Most standard Junos OS configuration statements are available in Junos OS for J-EX Series switches. This topic lists standard Junos OS statements that you commonly use when configuring interfaces on J-EX Series switches as well as statements that are used to configure only switch interfaces; it does not list all of the possible interface configuration statements for each interface. For information about additional standard Junos OS statements that you can configure on interfaces, see the Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Options See Table 131 on page 967 for the interface types and protocol-family options supported on the switch. Different protocol families support different subsets of the interface types on the switch. See the family statement for syntax of the protocol families supported for switch interfaces. Not all interface types support all family substatements. Check your switch CLI for supported substatements for a particular protocol family configuration. Table 131: Interface Types and Their Supported Protocol Families Supported Protocol Families Interface Typ Description ccc ethernet-swtichn ig inet inet6 iso mpls ae Aggregated Ethernet interface (also referred to as a link aggregation group [LAG]) ✓ ✓ ✓ ✓ ✓ ✓ ge Gigabit Ethernet interface ✓ ✓ ✓ ✓ ✓ ✓ lo0 Loopback interface ✓ ✓ ✓ ✓ me0 Management Ethernet interface ✓ ✓ ✓ ✓ vlan Routed VLAN interface (RVI) ✓ ✓ ✓ vme Virtual management Ethernet interface ✓ ✓ ✓ ✓ xe 10-Gigabit Ethernet interface ✓ ✓ ✓ ✓ ✓ interface-range Interface-range configuration Supported protocol families are the ones supported by the interface types that compose the range. ✓ ✓ The remaining statements are explained separately. Required Privilege Level interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. 967 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) on page 797 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ lacp Syntax Hierarchy Level Release Information Description lacp mode { periodic interval; } [edit interfaces aex aggregated-ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Link Aggregation Control Protocol (LACP). Default LACP is not enabled. Options mode —LACP mode: • active—Initiate transmission of LACP packets • passive—Respond to LACP packets The remaining statement is explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Configuring Aggregated Ethernet Interfaces (J-Web Procedure) on page 923 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 968 Chapter 55: Configuration Statements for Interfaces lacp (802.3ad) Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation lacp { force-up; } [edit interfaces interface-name ether-options 802.3ad] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Link Aggregation Control Protocol (LACP) parameters for interfaces. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 969 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS link-mode Syntax Hierarchy Level Release Information Description Default Options link-mode mode; [edit interfaces interface-name ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the device’s link-connection characteristic. The automatic mode is enabled. mode —Link characteristic: • full-duplex—Connection is full duplex. • half-duplex—Connection is half duplex. • automatic—Link mode is negotiated. If no-auto-negotiation is specified in ether-options, you can select only full-duplex or half-duplex. If auto-negotiation is specified in ether-options, you can select any mode. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 970 Chapter 55: Configuration Statements for Interfaces link-speed Syntax Hierarchy Level Release Information Description Options link-speed speed; [edit interfaces aex aggregated-ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For aggregated Ethernet interfaces only, set the required link speed. speed—For aggregated Ethernet links, specify speed in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Aggregated Ethernet links on J-EX Series switches can have one of the following speed values: Required Privilege Level Related Documentation • 1g—Links are 1 Gbps. • 10g—Links are 10 Gbps. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 971 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS member Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation member interface-name; [edit interfaces interface-range interface-range-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the name of the member interface belonging to an interface range on the J-EX Series switch. interface-name—Name of the interface. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Understanding Interface Ranges on J-EX Series Switches on page 869 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 972 Chapter 55: Configuration Statements for Interfaces members Syntax Hierarchy Level Release Information Description members [ (all | names | vlan-ids) ]; [edit interfaces interface-name unit logical-unit-number family ethernet-switching vlan] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For trunk interfaces, configure the VLANs for which the interface can carry traffic. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Options all—Specifies that this trunk interface is a member of all the VLANs that are configured on this switch. When a new VLAN is configured on the switch, this trunk interface automatically becomes a member of the VLAN. NOTE: Each VLAN that is configured must have a specified VLAN ID when you attempt to commit the configuration; otherwise, the configuration commit fails. Also, all cannot be the name of a VLAN on the switch. names—Name of one or more VLANs. vlan-ids—Numeric identifier of one or more VLANs. For a series of tagged VLANs, specify a range; for example, 10-20 or 10-20 23 27-30. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • show ethernet-switching interfaces on page 997 • show vlans on page 1263 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Creating a Series of Tagged VLANs (CLI Procedure) on page 1140 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 973 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS member-range Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation member-range starting-interface-name to ending-interface-name; [edit interfaces interface-range interface-range-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the names of the first and last members of a sequence of interfaces belonging to an interface range. Range: Starting interface-name to ending interface-name—The name of the first member and the name of the last member in the interface sequence. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Understanding Interface Ranges on J-EX Series Switches on page 869 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ minimum-links Syntax Hierarchy Level Release Information Description Options minimum-links number; [edit interfaces aex aggregated-ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For an aggregated Ethernet interface, set the minimum number of links that must be up for the bundle to be labeled up. number—Number of links. Range: 1 through 8 for J-EX Series switches other than J-EX8200 switches 1 through 12 for J-EX8200 switches Default: 1 Required Privilege Level Related Documentation 974 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 Chapter 55: Configuration Statements for Interfaces mtu Syntax Hierarchy Level Release Information Description mtu bytes; [edit interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the maximum transmission unit (MTU) size for the media. Changing the media MTU size causes an interface to be deleted and added again. Keep the following points in mind if you are configuring MTU size for jumbo frames on these special types of interfaces: • For LAG interfaces—Configuring the jumbo MTU size on a link aggregation group (LAG) interface (aex) automatically configures the jumbo MTU size on the member links. • For RVIs—Jumbo frames of up to 9216 bytes are supported on the routed VLAN interface (RVI), which is named vlan. The RVI functions as a logical router. To route jumbo data packets on the RVI, you must configure the jumbo MTU size on the member physical interfaces of the RVI and not on the RVI itself (the vlan interface). However, for jumbo control packets—for example, to ping the RVI with a packet size of 6000 bytes or more—you must explicitly configure the jumbo MTU size on the interface named vlan (the RVI). CAUTION: Setting or deleting the jumbo MTU size on the RVI (the vlan interface) while the switch is transmitting packets might result in dropped packets. Default Options 1514 bytes bytes—MTU size. Range: 256 through 9216 bytes Default: 1514 bytes Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 975 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS native-vlan-id Syntax Hierarchy Level Release Information Description Options native-vlan-id vlan-id; [edit interfaces interface-name unit 0 family ethernet-switching] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the VLAN identifier to associate with untagged packets received on the interface. vlan-id—Numeric identifier of the VLAN. Range: 0 through 4095 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • show ethernet-switching interfaces on page 997 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 976 Chapter 55: Configuration Statements for Interfaces periodic Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation periodic interval; [edit interfaces aex aggregated-ether-options lacp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the interval for periodic transmission of LACP packets. fast interval —Interval at which to periodically transmit LACP packets: • fast—Transmit packets every second. This is the default. • slow—Transmit packets every 30 seconds. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 977 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS pic Syntax Hierarchy Level Release Information Description Options pic pic-number { sfpplus { pic-modemode; } } [edit chassis fpc slot] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the specified port of the SFP+ uplink module to perform in the operating mode specified by pic-mode. The port is indicated by a Physical Interface Card (PIC) number. pic-number—Number of the PIC. For uplink ports in J-EX4200 switches, the PIC number is always 1. The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Setting the Mode on an SFP+ Uplink Module (CLI Procedure) on page 921 pic-mode Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 978 pic-mode mode; [edit chassis fpc slot pic pic-number sfpplus ] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the operating mode for the specified port on the SFP+ uplink module on a J-EX4200 switch. mode—Operating mode of the SFP+ uplink module: • 1G—1-gigabit operating mode • 10G—10-gigabit operating mode interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Setting the Mode on an SFP+ Uplink Module (CLI Procedure) on page 921 Chapter 55: Configuration Statements for Interfaces port-mode Syntax Hierarchy Level Release Information Description Default Options port-mode mode; [edit interfaces interface-name unit logical-unit-number family ethernet-switching] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether an interface on the switch operates in access or trunk mode. All switch interfaces are in access mode. access—Have the interface operate in access mode. In this mode, the interface can be in a single VLAN only. Access interfaces typically connect to network devices such as PCs, printers, IP telephones, and IP cameras. trunk—Have the interface operate in trunk mode. In this mode, the interface can be in multiple VLANs and can multiplex traffic between different VLANs. Trunk interfaces typically connect to other switches and to routers on the LAN. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 979 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rpf-check Syntax Hierarchy Level Release Information Description rpf-check; [edit interfaces interface-name unit logical-unit-number family inet], [edit interfaces interface-name unit logical-unit-number family inet6] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On J-EX4200 switches, enable a reverse-path forwarding (RPF) check on unicast traffic (except ECMP packets) on all ingress interfaces. On J-EX8200 switches, enable an RPF check on unicast traffic, including ECMP packets, on the selected ingress interface. Default Required Privilege Level Related Documentation 980 Unicast RPF is disabled on all interfaces. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Unicast RPF on a J-EX Series Switch on page 900 • Configuring Unicast RPF (CLI Procedure) on page 927 • Disabling Unicast RPF (CLI Procedure) on page 928 • Understanding Unicast RPF for J-EX Series Switches on page 872 Chapter 55: Configuration Statements for Interfaces sfpplus Syntax Hierarchy Level Release Information Description sfpplus { pic-modemode; } [edit chassis fpc slot pic pic-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the operating mode for the specified port on the SFP+ uplink module on the J-EX4200 switch. The remaining statement is explained separately. Default By default, the SFP+ uplink module operates in the 10-gigabit mode and supports SFP+ transceivers. NOTE: The SFP+ uplink module provides two ports for 10-gigabit small form-factor pluggable (SFP+) transceivers when configured to operate in 10-gigabit mode or four ports for 1-gigabit small form-factor pluggable (SFP) transceivers when configured to operate in 1-gigabit mode. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Setting the Mode on an SFP+ Uplink Module (CLI Procedure) on page 921 981 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS speed Syntax Hierarchy Level Release Information Description Default Options speed (auto-negotiation | speed) ; [edit interfaces interface-name ether-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the interface’s speed. If the auto-negotiation statement at the [edit interfaces interface-name ether-options] hierarchy level is enabled, the auto-negotiation option is enabled by default. • auto-negotiation—Automatically negotiate the speed based on the speed of the other end of the link. This option is available only when the auto-negotiation statement at the [edit interfaces interface-name ether-options] hierarchy level is enabled. • speed—Specify the interface speed. If the auto-negotiation statement at the [edit interfaces interface-name ether-options] hierarchy level is disabled, you must specify a specific value. This value sets the speed that is used on the link. If the auto-negotiation statement is enabled, you might want to configure a specific speed value to advertise the desired speed to the remote end. Required Privilege Level Related Documentation • 10m—10 Mbps • 100m—100 Mbps • 1g—1 Gbps interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 982 Chapter 55: Configuration Statements for Interfaces targeted-broadcast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation targeted-broadcast; [edit interfacesge-chassis/slot/port unit logical-unit-number family inet] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable IP directed broadcast on a specified subnet. IP directed broadcast is disabled. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring IP Directed Broadcast on a J-EX Series Switch on page 904 • Configuring IP Directed Broadcast (CLI Procedure) on page 929 • Understanding IP Directed Broadcast for J-EX Series Switches on page 876 983 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit Syntax Hierarchy Level Release Information Description Options unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } [edit interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a logical interface on the physical device. You must configure a logical interface to be able to use the physical device. logical-unit-number—Number of the logical unit. Range: 0 through 16,384 The remaining statements are explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 984 Chapter 55: Configuration Statements for Interfaces vlan Syntax Hierarchy Level Release Information Description vlan { members [ (all | names | vlan-ids) ]; } [edit interfaces interface-name unit logical-unit-number family ethernet-switching] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Bind an 802.1Q VLAN tag ID to a logical interface. The remaining statement is explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • show ethernet-switching interfaces on page 997 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 985 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan-id Syntax Hierarchy Level Release Information Description vlan-id vlan-id-number; [edit interfaces interface-name unit logical-unit-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Bind an 802.1Q VLAN tag ID to a logical interface. NOTE: The VLAN tag ID cannot be configured on logical interface unit 0. The logical unit number must be 1 or higher. Options vlan-id-number—A valid VLAN identifier. Range: 1 through 4094 Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • vlan-tagging on page 987 • Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch on page 893 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 986 Chapter 55: Configuration Statements for Interfaces vlan-tagging Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation vlan-tagging; [edit interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable VLAN tagging. The switch will receive and forward single-tag frames with 802.1Q VLAN tags. VLAN tagging is disabled by default. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • vlan-id on page 986 • Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch on page 893 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 987 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 988 CHAPTER 56 Operational Mode Commands for Interfaces 989 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear ipv6 neighbors Syntax Release Information Description Options clear ipv6 neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IPv6 neighbor cache information. none—Clear all IPv6 neighbor cache information. all—(Optional) Clear all IPv6 neighbor cache information. host hostname—(Optional) Clear the information for the specified IPv6 neighbors. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ipv6 neighbors 990 view • show ipv6 neighbors on page 1031 clear ipv6 neighbors on page 990 When you enter this command, you are provided feedback on the status of your request. user@host> clear ipv6 neighbors Chapter 56: Operational Mode Commands for Interfaces monitor interface Syntax Release Information Description Options monitor interface > Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display real-time statistics about interfaces, updating the statistics every second. Check for and display common interface failures, such as loopbacks detected and increases in framing errors. none—Display real-time statistics for all interfaces. interface-name—(Optional) Display real-time statistics for the specified interface. traffic—(Optional) Display traffic data for all active interfaces. detail—(Optional) With traffic option only, display detailed output. Additional Information The output of this command shows how much each field has changed since you started the command or since you cleared the counters by using the c key. For a description of the statistical information provided in the output of this command, see the show interfaces extensive command for a particular interface type in the Junos OS Interfaces Command Reference. To control the output of the monitor interface interface-name command while it is running, use the keys listed in Table 132 on page 991. The keys are not case-sensitive. Table 132: Output Control Keys for the monitor interface interface-name Command Key Action c Clears (returns to zero) the delta counters since monitor interface was started. This does not clear the accumulative counter. To clear the accumulative counter, use the clear interfaces interval command. f Freezes the display, halting the display of updated statistics and delta counters. i Displays information about a different interface. The command prompts you for the name of a specific interface. n Displays information about the next interface. The monitor interface command displays the physical or logical interfaces in the same order as the show interfaces terse command. q or Esc Quits the command and returns to the command prompt. t Thaws the display, resuming the update of the statistics and delta counters. To control the output of the monitor interface traffic command while it is running, use the keys listed in Table 133 on page 992. The keys are not case-sensitive. 991 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 133: Output Control Keys for the monitor interface traffic Command Required Privilege Level List of Sample Output Output Fields Key Action b Displays the statistics in units of bytes and bytes per second (bps). c Clears (return to 0) the delta counters in the Current Delta column. The statistics counters are not cleared. d Displays the Current Delta column (instead of the rate column) in bps or packets per second (pps). p Displays the statistics in units of packets and packets per second (pps). q or Esc Quits the command and returns to the command prompt. r Displays the rate column (instead of the Current Delta column) in bps and pps. trace monitor interface (Physical) on page 993 monitor interface (OTN Interface) on page 994 monitor interface (Logical) on page 995 monitor interface traffic on page 995 monitor interface traffic detail on page 996 Table 134 on page 992 describes the output fields for the monitor interface command. Output fields are listed in the approximate order in which they appear. Table 134: monitor interface Output Fields Field Name Field Description Level of Output router1 Hostname of the router. All levels Seconds How long the monitor interface command has been running or how long since you last cleared the counters. All levels Time Current time (UTC). All levels Delay x/y/z Time difference between when the statistics were displayed and the actual clock time. All levels • x—Time taken for the last polling (in milliseconds). • y—Minimum time taken across all pollings (in milliseconds). • z—Maximum time taken across all pollings (in milliseconds). Interface Short description of the interface, including its name, status, and encapsulation. All levels Link State of the link: Up, Down, or Test. All levels 992 Chapter 56: Operational Mode Commands for Interfaces Table 134: monitor interface Output Fields (continued) Field Name Field Description Level of Output Current delta Cumulative number for the counter in question since the time shown in the Seconds field, which is the time since you started the command or last cleared the counters. All levels Statistics For an explanation of the interface statistics, see the description of the show interfaces extensive command for a particular interface type in the Junos OS Interfaces Command Reference. All levels Description With the traffic option, displays the interface description configured at the [edit interfaces interface-name] hierarchy level. detail monitor interface (Physical) user@host> monitor interface so-0/0/0 router1 Seconds: 19 Interface: so-0/0/0, Enabled, Link is Up Encapsulation: PPP, Keepalives, Speed: OC48 Traffic statistics: Input packets: 6045 (0 Input bytes: 6290065 (0 Output packets: 10376 (0 Output bytes: 10365540 (0 Encapsulation statistics: Input keepalives: 1901 Output keepalives: 1901 NCP state: Opened LCP state: Opened Error statistics: Input errors: 0 Input drops: 0 Input framing errors: 0 Policed discards: 0 L3 incompletes: 0 L2 channel errors: 0 L2 mismatch timeouts: 0 Carrier transitions: 1 Output errors: 0 Output drops: 0 Aged packets: 0 Active alarms : None Active defects: None SONET error counts/seconds: LOS count 1 LOF count 1 SEF count 1 ES-S 0 SES-S 0 SONET statistics: BIP-B1 458871 BIP-B2 460072 REI-L 465610 BIP-B3 458978 REI-P 458773 Time: 15:46:29 pps) bps) pps) bps) Current Delta [11] [13882] [10] [9418] [2] [2] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] 993 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Received SONET overhead: F1 : 0x00 J0 K2 : 0x00 S1 C2(cmp) : 0x00 F2 Z4 : 0x00 S1(cmp) Transmitted SONET overhead: F1 : 0x00 J0 K2 : 0x00 S1 F2 : 0x00 Z3 : : : : 0x00 0x00 0x00 0x00 K1 C2 Z3 : 0x00 : 0x00 : 0x00 : 0x01 : 0x00 : 0x00 K1 C2 Z4 : 0x00 : 0xcf : 0x00 Next='n', Quit='q' or ESC, Freeze='f', Thaw='t', Clear='c', Interface='i' monitor interface (OTN Interface) user@host> monitor interface ge-7/0/0 Interface: ge-7/0/0, Enabled, Link is Up Encapsulation: Ethernet, Speed: 10000mbps Traffic statistics: Input bytes: 0 (0 bps) Output bytes: 0 (0 bps) Input packets: 0 (0 pps) Output packets: 0 (0 pps) Error statistics: Input errors: 0 Input drops: 0 Input framing errors: 0 Policed discards: 0 L3 incompletes: 0 L2 channel errors: 0 L2 mismatch timeouts: 0 Carrier transitions: 5 Output errors: 0 Output drops: 0 Aged packets: 0 Active alarms : None Active defects: None Input MAC/Filter statistics: Unicast packets 0 Broadcast packets 0 Multicast packets 0 Oversized frames 0 Packet reject count 0 DA rejects 0 SA rejects 0 Output MAC/Filter Statistics: Unicast packets 0 Broadcast packets 0 Multicast packets 0 Packet pad count 0 Packet error count 0 OTN Link 0 OTN Alarms: OTU_BDI, OTU_TTIM, ODU_BDI OTN Defects: OTU_BDI, OTU_TTIM, ODU_BDI, ODU_TTIM OTN OC - Seconds LOS 2 LOF 9 OTN OTU - FEC Statistics Corr err ratio N/A Corr bytes 0 Uncorr words 0 OTN OTU - Counters 994 Chapter 56: Operational Mode Commands for Interfaces BIP BBE ES SES UAS OTN ODU - Counters BIP BBE ES SES UAS OTN ODU - Received Overhead monitor interface (Logical) 0 0 0 0 422 0 0 0 0 422 APSPCC 0-3: user@host> monitor interface so-1/0/0.0 host name Seconds: 16 0 Time: 15:33:39 Delay: 0/0/1 Interface: so-1/0/0.0, Enabled, Link is Down Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP Local statistics: Input bytes: 0 Output bytes: 0 Input packets: 0 Output packets: 0 Remote statistics: Input bytes: 0 (0 bps) Output bytes: 0 (0 bps) Input packets: 0 (0 pps) Output packets: 0 (0 pps) Traffic statistics: Destination address: 192.168.8.193, Local: 192.168.8.21 Current delta [0] [0] [0] [0] [0] [0] [0] [0] Next='n', Quit='q' or ESC, Freeze='f', Thaw='t', Clear='c', Interface='i' monitor interface traffic user@host> monitor interface traffic host name Seconds: 15 Interface so-1/0/0 so-1/1/0 so-1/1/1 so-1/1/2 so-1/1/3 t3-1/2/0 t3-1/2/1 t3-1/2/2 t3-1/2/3 so-2/0/0 so-2/0/1 so-2/0/2 so-2/0/3 so-2/1/0 so-2/1/1 so-2/1/2 so-2/1/3 at-2/3/0 at-2/3/1 Link Down Down Down Down Down Down Down Down Down Up Up Up Up Up Down Down Up Up Down Input packets 0 0 0 0 0 0 0 0 0 211035 192753 211020 211029 189378 0 0 0 0 0 Time: 12:31:09 (pps) (0) (0) (0) (0) (0) (0) (0) (0) (0) (1) (1) (1) (1) (1) (0) (0) (0) (0) (0) Output packets 0 0 0 0 0 0 0 0 0 36778 36782 36779 36776 36349 18747 16078 80338 0 0 (pps) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) (0) Bytes=b, Clear=c, Delta=d, Packets=p, Quit=q or ESC, Rate=r, Up=^U, Down=^D 995 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS monitor interface traffic detail user@host> monitor interface traffic detail host name Seconds: 15 Interface t1-0/1/1:0 Time: 12:31:09 Link Input packets (pps) Output packets (pps) Description Up 19769 (0) 0 (0) To-OSAKA-1 ... Bytes=b, Clear=c, Delta=d, Packets=p, Quit=q or ESC, Rate=r, Up=^U, Down=^D 996 Chapter 56: Operational Mode Commands for Interfaces show ethernet-switching interfaces Syntax Release Information Description Options show ethernet-switching interfaces Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about switched Ethernet interfaces. none—(Optional) Display brief information for Ethernet switching interfaces. brief | detail | summary—(Optional) Display the specified level of output. interface interface-name—(Optional) Display Ethernet switching information for a specific interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ethernet-switching mac-learning-log on page 1241 • show ethernet-switching table on page 1249 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 show ethernet-switching interfaces on page 998 show ethernet-switching interfaces ge-0/0/15 brief on page 999 show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) on page 999 show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) on page 999 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) on page 999 show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) on page 999 Table 135 on page 997 lists the output fields for the show ethernet-switching interfaces command. Output fields are listed in the approximate order in which they appear. Table 135: show ethernet-switching interfaces Output Fields Field Name Field Description Level of Output Interface Name of a switching interface. All levels State Interface state. Values are up and down. none, brief, detail, summary VLAN members Name of a VLAN. none, brief, detail, summary Tag Number of the 802.1Q-tag. All levels 997 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 135: show ethernet-switching interfaces Output Fields (continued) Field Name Field Description Level of Output Tagging Specifies whether the interface forwards 802.1Q-tagged or untagged traffic. All levels Blocking The forwarding state of the interface: none, brief, detail, summary • unblocked—Traffic is forwarded on the interface. • blocked—Traffic is not being forwarded on the interface. • Disabled by bpdu control—The interface is disabled due to receiving BPDUs on a protected interface. If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. • blocked by RTG—The specified redundant trunk group is disabled. • blocked by STP—The interface is disabled due to a spanning tree protocol error. • MAC limit exceeded—The interface is temporarily disabled due to a MAC limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • MAC move limit exceeded—The interface is temporarily disabled due to a MAC move limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • Storm control in effect—The interface is temporarily disabled due to a storm control error. The disabled interface is automatically restored to service when the disable timeout expires. Index The VLAN index internal to the Junos OS. detail mapping The C-VLAN to S-VLAN mapping information: detail • dot1q-tunneled—The interface maps all traffic to the S-VLAN (all-in-one bundling). • native—The interface maps untagged and priority tagged packets to the S-VLAN. • push—The interface maps packets to a firewall filter to an S-VLAN. • policy-mapped—The interface maps packets to a specifically defined S-VLAN. • integer—The interface maps packets to the specified S-VLAN. show ethernet-switching interfaces 998 user@switch> show ethernet-switching interfaces Interface State ae0.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 ge-0/0/6.0 ge-0/0/7.0 ge-0/0/13.0 ge-0/0/14.0 up up up down down down down up up ge-0/0/15.0 up VLAN members default vlan300 default default default default default default vlan100 vlan200 vlan100 vlan200 Tag 300 100 200 100 200 Tagging Blocking untagged unblocked untagged blocked by RTG (rtggroup) blocked by STP MAC limit exceeded MAC move limit exceeded Storm control in effect unblocked untagged unblocked tagged unblocked tagged unblocked tagged blocked by STP tagged blocked by STP Chapter 56: Operational Mode Commands for Interfaces ge-0/0/16.0 ge-0/0/17.0 show ethernet-switching interfaces ge-0/0/15 brief show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) down down default vlan100 100 untagged unblocked tagged Disabled by bpdu-control vlan200 200 tagged Disabled by bpdu-control user@switch> show ethernet-switching interfaces ge-0/0/15 brief Interface State VLAN members Tag Tagging Blocking ge-0/0/15.0 up vlan100 vlan200 100 200 tagged tagged blocked by STP blocked by STP user@switch> show ethernet-switching interfaces ge-0/0/2 detail Interface: ge-0/0/2.0, Index: 65, State: up, Port mode: Access VLAN membership: vlan300, 802.1Q Tag: 300, untagged, msti-id: 0, blocked by RTG(rtggroup) Number of MACs learned on IFL: 0 user@switch> show ethernet-switching interfaces ge-0/0/15 detail Interface: ge-0/0/15.0, Index: 70, State: up, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 0, blocked by STP vlan200, 802.1Q Tag: 200, tagged, msti-id: 0, blocked by STP Number of MACs learned on IFL: 0 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) user@switch> show ethernet-switching interfaces ge-0/0/17 detail show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) user@switch>show ethernet-switching interfaces ge-0/0/6.0 detail Interface: ge-0/0/6.0, Index: 73, State: up, Port mode: Access VLAN membership: map, 802.1Q Tag: 134, Mapped Tag: native, push, dot1q-tunneled, unblocked map, 802.1Q Tag: 134, Mapped Tag: 20, push, dot1q-tunneled, unblocked Interface: ge-0/0/17.0, Index: 71, State: down, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 1, Disabled by bpdu-control vlan200, 802.1Q Tag: 200, tagged, msti-id: 2, Disabled by bpdu-control Number of MACs learned on IFL: 0 999 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show interfaces diagnostics optics Syntax Release Information Description show interfaces diagnostics optics interface-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display diagnostics data and alarms for Gigabit Ethernet optical transceivers (SFP or SFP+) installed in J-EX Series switches. The information provided by this command is known as digital optical monitoring (DOM) information. Thresholds that trigger a high alarm, low alarm, high warning, or low warning are set by the transponder vendors. Generally, a high alarm or low alarm indicates that the optics module is not operating properly. This information can be used to diagnose why a transceiver is not working. Options interface-name—Name of the interface associated with the port in which the transceiver is installed: ge-fpc/pic/port or xe-fpc/pic/port. Required Privilege Level Related Documentation view • Monitoring Interface Status and Traffic on page 931 • Installing a Transceiver in a J-EX Series Switch • Removing a Transceiver from a J-EX Series Switch • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output Output Fields show interfaces diagnostics optics ge-0/1/0 (SFP Transceiver) on page 1002 show interfaces diagnostics optics xe-0/1/0 (SFP+ Transceiver) on page 1003 Table 136 on page 1000 lists the output fields for the show interfaces diagnostics optics command. Output fields are listed in the approximate order in which they appear. Table 136: show interfaces diagnostics optics Output Fields Field Name Field Description Physical interface Displays the name of the physical interface. Laser bias current Displays the magnitude of the laser bias power setting current, in milliamperes. The laser bias provides direct modulation of laser diodes and modulates currents. Laser output power Displays the laser output power, in milliwatts (mW) and decibels referred to 1.0 mW (dBm). Module temperature Displays the temperature, in Celsius and Fahrenheit. Module voltage Displays the voltage, in Volts. 1000 Chapter 56: Operational Mode Commands for Interfaces Table 136: show interfaces diagnostics optics Output Fields (continued) Field Name Field Description Receiver signal average optical power Displays the receiver signal average optical power, in milliwatts (mW) and decibels referred to 1.0 mW (dBm). Laser bias current high alarm Displays whether the laser bias power setting high alarm is On or Off. Laser bias current low alarm Displays whether the laser bias power setting low alarm is On or Off. Laser bias current high warning Displays whether the laser bias power setting high warning is On or Off. Laser bias current low warning Displays whether the laser bias power setting low warning is On or Off. Laser output power high alarm Displays whether the laser output power high alarm is On or Off. Laser output power low alarm Displays whether the laser output power low alarm is On or Off. Laser output power high warning Displays whether the laser output power high warning is On or Off. Laser output power low warning Displays whether the laser output power low warning is On or Off. Module temperature high alarm Displays whether the module temperature high alarm is On or Off. Module temperature low alarm Displays whether the module temperature low alarm is On or Off. Module temperature high warning Displays whether the module temperature high warning is On or Off. Module temperature low warning Displays whether the module temperature low warning is On or Off. Module voltage high alarm Displays whether the module voltage high alarm is On or Off. Module voltage low alarm Displays whether the module voltage low alarm is On or Off. Module voltage high warning Displays whether the module voltage high warning is On or Off. Module voltage low warning Displays whether the module voltage low warning is On or Off. Laser rx power high alarm Displays whether the receive laser power high alarm is On or Off. Laser rx power low alarm Displays whether the receive laser power low alarm is On or Off. Laser rx power high warning Displays whether the receive laser power high warning is On or Off. Laser rx power low warning Displays whether the receive laser power low warning is On or Off. Laser bias current high alarm threshold Displays the vendor-specified threshold for the laser bias current high alarm. Laser bias current low alarm threshold Displays the vendor-specified threshold for the laser bias current low alarm. 1001 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 136: show interfaces diagnostics optics Output Fields (continued) Field Name Field Description Laser bias current high warning threshold Displays the vendor-specified threshold for the laser bias current high warning. Laser bias current low warning threshold Displays the vendor-specified threshold for the laser bias current low warning. Laser output power high alarm threshold Displays the vendor-specified threshold for the laser output power high alarm. Laser output power low alarm threshold Displays the vendor-specified threshold for the laser output power low alarm. Laser output power high warning threshold Displays the vendor-specified threshold for the laser output power high warning. Laser output power low warning threshold Displays the vendor-specified threshold for the laser output power low warning. Module temperature high alarm threshold Displays the vendor-specified threshold for the module temperature high alarm. Module temperature low alarm threshold Displays the vendor-specified threshold for the module temperature low alarm. Module temperature high warning threshold Displays the vendor-specified threshold for the module temperature high warning. Module temperature low warning threshold Displays the vendor-specified threshold for the module temperature low warning. Module voltage high alarm threshold Displays the vendor-specified threshold for the module voltage high alarm. Module voltage low alarm threshold Displays the vendor-specified threshold for the module voltage low alarm. Module voltage high warning threshold Displays the vendor-specified threshold for the module voltage high warning. Module voltage low warning threshold Displays the vendor-specified threshold for the module voltage low warning. Laser rx power high alarm threshold Displays the vendor-specified threshold for the laser rx power high alarm. Laser rx power low alarm threshold Displays the vendor-specified threshold for the laser rx power low alarm. Laser rx power high warning threshold Displays the vendor-specified threshold for the laser rx power high warning. Laser rx power low warning threshold Displays the vendor-specified threshold for the laser rx power low warning. show interfaces diagnostics optics ge-0/1/0 (SFP Transceiver) 1002 user@host> show interfaces diagnostics optics ge-0/1/0 Physical interface: ge-0/1/0 Laser bias current : Laser output power : Module temperature : Module voltage : 5.444 mA 0.3130 mW / -5.04 dBm 36 degrees C / 97 degrees F 3.2120 V Chapter 56: Operational Mode Commands for Interfaces Receiver signal average optical power Laser bias current high alarm Laser bias current low alarm Laser bias current high warning Laser bias current low warning Laser output power high alarm Laser output power low alarm Laser output power high warning Laser output power low warning Module temperature high alarm Module temperature low alarm Module temperature high warning Module temperature low warning Module voltage high alarm Module voltage low alarm Module voltage high warning Module voltage low warning Laser rx power high alarm Laser rx power low alarm Laser rx power high warning Laser rx power low warning Laser bias current high alarm threshold Laser bias current low alarm threshold Laser bias current high warning threshold Laser bias current low warning threshold Laser output power high alarm threshold Laser output power low alarm threshold Laser output power high warning threshold Laser output power low warning threshold Module temperature high alarm threshold Module temperature low alarm threshold Module temperature high warning threshold Module temperature low warning threshold Module voltage high alarm threshold Module voltage low alarm threshold Module voltage high warning threshold Module voltage low warning threshold Laser rx power high alarm threshold Laser rx power low alarm threshold Laser rx power high warning threshold Laser rx power low warning threshold show interfaces diagnostics optics xe-0/1/0 (SFP+ Transceiver) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : user@host> show interfaces diagnostics optics xe-0/1/0 Physical interface: xe-0/1/0 Laser bias current : Laser output power : Module temperature : Module voltage : Receiver signal average optical power : Laser bias current high alarm : Laser bias current low alarm : Laser bias current high warning : Laser bias current low warning : Laser output power high alarm : Laser output power low alarm : Laser output power high warning : Laser output power low warning : Module temperature high alarm : Module temperature low alarm : Module temperature high warning : Module temperature low warning : 0.3840 mW / Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off 15.000 mA 1.000 mA 12.000 mA 2.000 mA 0.6300 mW / 0.0660 mW / 0.6300 mW / 0.0780 mW / 109 degrees -29 degrees 103 degrees -13 degrees 3.900 V 2.700 V 3.700 V 2.900 V 1.2589 mW / 0.0100 mW / 0.7939 mW / 0.0157 mW / -4.16 dBm -2.01 dBm -11.80 dBm -2.01 dBm -11.08 dBm C / 228 degrees F C / -20 degrees F C / 217 degrees F C / 9 degrees F 1.00 dBm -20.00 dBm -1.00 dBm -18.04 dBm 4.968 mA 0.4940 mW / -3.06 dBm 27 degrees C / 81 degrees F 3.2310 V 0.0000 Off Off Off Off Off Off Off Off Off Off Off Off 1003 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Module voltage high alarm Module voltage low alarm Module voltage high warning Module voltage low warning Laser rx power high alarm Laser rx power low alarm Laser rx power high warning Laser rx power low warning Laser bias current high alarm threshold Laser bias current low alarm threshold Laser bias current high warning threshold Laser bias current low warning threshold Laser output power high alarm threshold Laser output power low alarm threshold Laser output power high warning threshold Laser output power low warning threshold Module temperature high alarm threshold Module temperature low alarm threshold Module temperature high warning threshold Module temperature low warning threshold Module voltage high alarm threshold Module voltage low alarm threshold Module voltage high warning threshold Module voltage low warning threshold Laser rx power high alarm threshold Laser rx power low alarm threshold Laser rx power high warning threshold Laser rx power low warning threshold 1004 : : : : : : : : : : : : : : : : : : : : : : : : : : : : Off Off Off Off Off On Off On 10.500 mA 2.000 mA 9.000 mA 2.500 mA 1.4120 mW / 1.50 dBm 0.0740 mW / -11.31 dBm 0.7070 mW / -1.51 dBm 0.1860 mW / -7.30 dBm 75 degrees C / 167 degrees F -5 degrees C / 23 degrees F 70 degrees C / 158 degrees F 0 degrees C / 32 degrees F 3.630 V 2.970 V 3.465 V 3.135 V 1.5849 mW / 2.00 dBm 0.0407 mW / -13.90 dBm 0.7943 mW / -1.00 dBm 0.1023 mW / -9.90 dBm Chapter 56: Operational Mode Commands for Interfaces show interfaces geSyntax Release Information Description Options show interfaces ge-fpc/pic/port Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display status information about the specified Gigabit Ethernet interface. ge-fpc/pic/port—Display standard information about the specified Gigabit Ethernet interface. brief | detail | extensive | terse—(Optional) Display the specified level of output. descriptions—(Optional) Display interface description strings. media—(Optional) Display media-specific information about network interfaces. snmp-index snmp-index —(Optional) Display information for the specified SNMP index of the interface. statistics—(Optional) Display static interface statistics. Required Privilege Level Related Documentation view • Monitoring Interface Status and Traffic on page 931 • Troubleshooting Network Interfaces on J-EX4200 Switches on page 939 • Troubleshooting an Aggregated Ethernet Interface on page 940 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output Output Fields show interfaces ge-0/0/0 on page 1012 show interfaces ge-0/0/0 brief on page 1012 show interfaces ge-0/0/0 detail on page 1012 show interfaces ge-0/0/4 extensive on page 1013 Table 137 on page 1005 lists the output fields for the show interfaces ge- command. Output fields are listed in the approximate order in which they appear. Table 137: show interfaces ge- Output Fields Field Name Field Description Level of Output Name of the physical interface. All levels Physical Interface Physical interface 1005 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output Enabled State of the interface: Enabled or Disabled. All levels Interface index Index number of the physical interface, which reflects its initialization sequence. detail extensive none SNMP ifIndex SNMP index number for the physical interface. detail extensive none Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive Description Optional user-specified description. brief detail extensive Link-level type Encapsulation being used on the physical interface. All levels MTU Maximum transmission unit size on the physical interface. Default is 1514. All levels Speed Speed at which the interface is running. All levels Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback: Local or Remote. All levels Source filtering Source filtering status: Enabled or Disabled. All levels Flow control Flow control status: Enabled or Disabled. All levels Auto-negotiation Autonegotiation status: Enabled or Disabled. All levels Remote-fault Remote fault status: All levels • Online—Autonegotiation is manually configured as online. • Offline—Autonegotiation is manually configured as offline. Device flags Information about the physical device. All levels Interface flags Information about the interface. All levels Link flags Information about the link. All levels CoS queues Number of CoS queues configured. detail extensive none Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive Current address Configured MAC address. detail extensive none Hardware address MAC address of the hardware. detail extensive none Last flapped Date, time, and how long ago the interface went from down to up. The format is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second ago). For example, Last flapped: 2008–01–16 10:52:40 UTC (3d 22:58 ago). detail extensive none 1006 Chapter 56: Operational Mode Commands for Interfaces Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output Statistics last cleared Time when the statistics for the interface were last set to zero. detail extensive Traffic statistics Number and rate of bytes and packets received and transmitted on the physical interface. detail extensive • Input bytes—Number of bytes received on the interface. • Output bytes—Number of bytes transmitted on the interface. • Input packets—Number of packets received on the interface • Output packets—Number of packets transmitted on the interface. NOTE: The bandwidth bps counter is not enabled on the switch. Input errors Input errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious: • Errors—Sum of the incoming frame aborts and FCS errors. • Drops—Number of packets dropped by the input queue of the I/O Manager extensive ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism. • Framing errors—Number of packets received with an invalid frame checksum (FCS). • Runts—Number of frames received that are smaller than the runt threshold. • Policed discards—Number of frames that the incoming packet match code discarded because they were not recognized or not of interest. Usually, this field reports protocols that the Junos OS does not handle. • L3 incompletes—Number of incoming packets discarded because they failed Layer 3 sanity checks of the headers. For example, a frame with less than 20 bytes of available IP header is discarded. • L2 channel errors—Number of times the software did not find a valid logical interface for an incoming frame. • L2 mismatch timeouts—Number of malformed or short packets that caused the incoming packet handler to discard the frame as unreadable. • FIFO errors—Number of FIFO errors in the receive direction that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. • Resource errors—Sum of transmit drops. 1007 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output Output errors Output errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious: extensive • Carrier transitions—Number of times the interface has gone from down to up. This number does not normally increment quickly, increasing only when the cable is unplugged, the far-end system is powered down and then up, or another problem occurs. If the number of carrier transitions increments quickly (perhaps once every 10 seconds), the cable, the far-end system, or the PIC or PIM is malfunctioning. • Errors—Sum of the outgoing frame aborts and FCS errors. • Drops—Number of packets dropped by the output queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism. • Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC supports only full-duplex operation, so for Gigabit Ethernet PICs, this number should always remain 0. If it is nonzero, there is a software bug. • Aged packets—Number of packets that remained in shared packet SDRAM so long that the system automatically purged them. The value in this field should never increment. If it does, it is most likely a software bug or possibly malfunctioning hardware. • FIFO errors—Number of FIFO errors in the send direction as reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. • HS link CRC errors—Number of errors on the high-speed links between the ASICs responsible for handling the switch interfaces. • MTU errors—Number of packets whose size exceeded the MTU of the interface. • Resource errors—Sum of transmit drops. Egress queues Total number of egress queues supported on the specified interface. detail extensive Queue counters (Egress ) CoS queue number and its associated user-configured forwarding class name. detail extensive Active alarms and Active defects • Queued packets—Number of queued packets. • Transmitted packets—Number of transmitted packets. • Dropped packets—Number of packets dropped by the ASIC's RED mechanism. Ethernet-specific defects that can prevent the interface from passing packets. When a defect persists for a certain amount of time, it is promoted to an alarm. Based on the switch configuration, an alarm can ring the red or yellow alarm bell on the switch or turn on the red or yellow alarm LED on the front of the switch. These fields can contain the value None or Link. • None—There are no active defects or alarms. • Link—Interface has lost its link state, which usually means that the cable is unplugged, the far-end system has been turned off, or the PIC is malfunctioning. 1008 detail extensive none Chapter 56: Operational Mode Commands for Interfaces Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output MAC statistics Receive and Transmit statistics reported by the PIC's MAC subsystem. extensive • Total octets and total packets—Total number of octets and packets. For Gigabit Ethernet IQ PICs, the received octets count varies by interface type. • Unicast packets, Broadcast packets, and Multicast packets—Number of unicast, broadcast, and multicast packets. • CRC/Align errors—Total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). • FIFO error—Number of FIFO errors that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. • MAC control frames—Number of MAC control frames. • MAC pause frames—Number of MAC control frames with pause operational code. • Oversized frames—Number of frames that exceed 1518 octets. • Jabber frames—Number of frames that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. This definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition in which any packet exceeds 20 ms. The allowed range to detect jabber is from 20 ms to 150 ms. • Fragment frames—Total number of packets that were less than 64 octets in length (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. Fragment frames normally increment because both runts (which are normal occurrences caused by collisions) and noise hits are counted. • Code violations—Number of times an event caused the PHY to indicate “Data reception error” or “invalid data symbol error.” Filter Statistics Receive and Transmit statistics reported by the PIC's MAC address filter extensive subsystem. 1009 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output Autonegotiation information Information about link autonegotiation: extensive • Negotiation status: • Incomplete—Ethernet interface has the speed or link mode configured. • No autonegotiation—Remote Ethernet interface has the speed or link mode configured or does not perform autonegotiation. • Complete—Ethernet interface is connected to a device that performs autonegotiation and the autonegotiation process is successful. • Link partner status—OK when Ethernet interface is connected to a device that performs autonegotiation and the autonegotiation process is successful. • Link partner: • Link mode—Depending on the capability of the attached Ethernet device, either Full-duplex or Half-duplex. • Flow control—Types of flow control supported by the remote Ethernet device. For Gigabit Ethernet interfaces, types are Symmetric (link partner supports PAUSE on receive and transmit), Asymmetric (link partner supports PAUSE on transmit), and Symmetric/Asymmetric (link partner supports PAUSE on both receive and transmit or PAUSE only on receive). • Remote fault—Remote fault information from the link partner—Failure indicates a receive link error. OK indicates that the link partner is receiving. Negotiation error indicates a negotiation error. Offline indicates that the link partner is going offline. • • Link partner speed—Speed of the link partner. Local resolution—Information from the link partner: • Flow control—Types of flow control supported by the remote Ethernet device. For Gigabit Ethernet interfaces, types are Symmetric (link partner supports PAUSE on receive and transmit), Asymmetric (link partner supports PAUSE on transmit), and Symmetric/Asymmetric (link partner supports PAUSE on both receive and transmit or PAUSE only on receive). • Remote fault—Remote fault information. Link OK (no error detected on receive), Offline (local interface is offline), and Link Failure (link error detected on receive). Packet Forwarding Engine configuration Information about the configuration of the Packet Forwarding Engine: • extensive Destination slot—FPC slot number. NOTE: For a J-EX4200 standalone switch, the FPC slot number refers to the switch itself and is always 0. In a Virtual Chassis configuration, the FPC slot number refers to the member ID. In a J-EX8200 switch, the FPC slot number refers to the line card slot number. Logical Interface Logical interface Name of the logical interface. All levels Index Index number of the logical interface, which reflects its initialization sequence. detail extensive none SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none 1010 Chapter 56: Operational Mode Commands for Interfaces Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive Flags Information about the logical interface. All levels Encapsulation Encapsulation on the logical interface. All levels Protocol Protocol family. detail extensive none Traffic statistics Number and rate of bytes and packets received (input) and transmitted (output) on the specified interface. detail extensive IPv6 transit statistics If IPv6 statistics tracking is enabled, number of IPv6 bytes and packets received and transmitted on the logical interface. extensive Local statistics Number and rate of bytes and packets destined to and from the switch. extensive Transit statistics Number and rate of bytes and packets transiting the switch. extensive Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive Route Table Route table in which the logical interface address is located. For example, 0 refers to the routing table inet.0. detail extensive none Input Filters Names of any input filters applied to this interface. detail extensive Output Filters Names of any output filters applied to this interface. detail extensive Flags Information about protocol family flags. detail extensive If unicast reverse-path forwarding (RPF) is explicitly configured on the specified interface, the uRPF flag is displayed. If unicast RPF was configured on a different interface (and therefore is enabled on all switch interfaces) but was not explicitly configured on the specified interface, the uRPF flag is not displayed even though unicast RPF is enabled. protocol-family Protocol family configured on the logical interface. If the protocol is inet, the IP address of the interface is also displayed. brief Flags Information about the address flags. detail extensive none Destination IP address of the remote side of the connection. detail extensive none Local IP address of the logical interface. detail extensive none Broadcast Broadcast address of the logical interlace. detail extensive none 1011 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 137: show interfaces ge- Output Fields (continued) Field Name Field Description Level of Output Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive show interfaces ge-0/0/0 user@switch> show interfaces ge-0/0/0 Physical interface: ge-0/0/0, Enabled, Physical link is Down Interface index: 129, SNMP ifIndex: 21 Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled Remote fault: Online Device flags : Present Running Down Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:19:e2:50:3f:41, Hardware address: 00:19:e2:50:3f:41 Last flapped : 2008-01-16 11:40:53 UTC (4d 02:30 ago) Input rate : 0 bps (0 pps) Output rate : 0 bps (0 pps) Ingress rate at Packet Forwarding Engine : 0 bps (0 pps) Ingress drop rate at Packet Forwarding Engine : 0 bps (0 pps) Active alarms : None Active defects : None Logical interface ge-0/0/0.0 (Index 65) (SNMP ifIndex 22) Flags: SNMP-Traps Encapsulation: ENET2 Input packets : 0 Output packets: 0 Protocol eth-switch Flags: None show interfaces ge-0/0/0 brief user@switch> show interfaces ge-0/0/0 brief Physical interface: ge-0/0/0, Enabled, Physical link is Down Description: voice priority and tcp and icmp traffic rate-limiting filter at i ngress port Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Down Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Link flags : None Logical interface ge-0/0/0.0 Flags: Device-Down SNMP-Traps Encapsulation: ENET2 eth-switch show interfaces ge-0/0/0 detail 1012 user@switch> show interfaces ge-0/0/0 detail Physical interface: ge-0/0/0, Enabled, Physical link is Up Interface index: 193, SNMP ifIndex: 206, Generation: 196 Link-level type: Ethernet, MTU: 1514, Speed: Auto, Duplex: Auto, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None Chapter 56: Operational Mode Commands for Interfaces CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:1f:12:30:ff:40, Hardware address: 00:1f:12:30:ff:40 Last flapped : 2009-05-05 06:03:05 UTC (00:22:13 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 0 0 bps Output bytes : 0 0 bps Input packets: 0 0 pps Output packets: 0 0 pps IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 0 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 0 0 Active alarms : None Active defects : None Logical interface ge-0/0/0.0 (Index 65) (SNMP ifIndex 235) Flags: SNMP-Traps Encapsulation: ENET2 Bandwidth: 0 Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Local statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Protocol eth-switch, Generation: 146, Route table: 0 Flags: Is-Primary Input Filters: f1, Output Filters: f2,,,, show interfaces ge-0/0/4 extensive (Generation 130) 0 0 0 0 bps bps pps pps user@switch> show interfaces ge-0/0/4 extensive Physical interface: ge-0/0/4, Enabled, Physical link is Up Interface index: 165, SNMP ifIndex: 152, Generation: 168 Link-level type: Ethernet, MTU: 1514, Speed: Auto, Duplex: Auto, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None 1013 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:1f:12:33:65:44, Hardware address: 00:1f:12:33:65:44 Last flapped : 2008-09-17 11:02:25 UTC (16:32:54 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 0 0 bps Output bytes : 2989761 984 bps Input packets: 0 0 pps Output packets: 24307 1 pps IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0 Output errors: Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 0 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 24307 0 Active alarms : None Active defects : None MAC statistics: Receive Transmit Total octets 0 2989761 Total packets 0 24307 Unicast packets 0 0 Broadcast packets 0 0 Multicast packets 0 24307 CRC/Align errors 0 0 FIFO errors 0 0 MAC control frames 0 0 MAC pause frames 0 0 Oversized frames 0 Jabber frames 0 Fragment frames 0 Code violations 0 Autonegotiation information: Negotiation status: Complete Link partner: Link mode: Full-duplex, Flow control: None, Remote fault: OK, Link partner Speed: 1000 Mbps Local resolution: Flow control: None, Remote fault: Link OK Packet Forwarding Engine configuration: Destination slot: 0 Direction : Output CoS transmit queue Bandwidth Buffer Priority 1014 Chapter 56: Operational Mode Commands for Interfaces Limit 0 best-effort none 7 network-control none % 95 bps 950000000 % 95 usec NA low 5 50000000 5 NA low Logical interface ge-0/0/4.0 (Index 82) (SNMP ifIndex 184) Flags: SNMP-Traps Encapsulation: ENET2 Traffic statistics: Input bytes : 0 Output bytes : 4107883 Input packets: 0 Output packets: 24307 IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Local statistics: Input bytes : 0 Output bytes : 4107883 Input packets: 0 Output packets: 24307 Transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Protocol eth-switch, Generation: 159, Route table: 0 Flags: None Input Filters: f2, Output Filters: f1,,,, (Generation 147) 0 0 0 0 bps bps pps pps 1015 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show interfaces queue Syntax Release Information Description Options show interfaces queue Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display class-of-service (CoS) queue information for physical interfaces. none—Show detailed CoS queue statistics for all physical interfaces. both-ingress-egress—(Optional) Show both ingress and egress queue statistics. (Ingress statistics are not available for all interfaces.) egress—(Optional) Show eqress queue statistics only. forwarding-class forwarding-class—(Optional) Show queue statistics only for the specified forwarding class. ingress—(Optional) Show ingress queue statistics only. (Ingress statistics are not available for all interfaces.) interface-name interface-name—(Optional) Show queue statistics for the specified interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Monitoring Interface Status and Traffic on page 931 • Monitoring Interfaces That Have CoS Components on page 2937 • Defining CoS Schedulers (CLI Procedure) on page 2920 • Configuring CoS Traffic Classification for Ingress Queuing on 40-port SFP+ Line Cards (CLI Procedure) show interfaces queue ge-0/0/0 on page 1018 Table 138 on page 1016 lists the output fields for the show interfaces queue command. Output fields are listed in the approximate order in which they appear. Table 138: show interfaces queue Output Fields Field Name Field Description Physical Interface and Forwarding Class Information Physical interface 1016 Name of the physical interface. Chapter 56: Operational Mode Commands for Interfaces Table 138: show interfaces queue Output Fields (continued) Field Name Field Description Enabled State of the interface. Possible values are: • Administratively down, Physical link is Down—The interface is turned off, and the physical link is inoperable. • Administratively down, Physical link is Up—The interface is turned off, but the physical link is operational and can pass packets when it is enabled. • Enabled, Physical link is Down—The interface is turned on, but the physical link is inoperable and cannot pass packets. • Enabled, Physical link is Up—The interface is turned on, and the physical link is operational and can pass packets. Interface index Index number of the physical interface, which reflects its initialization sequence. SNMP ifIndex SNMP index number for the physical interface. Description User-configured interface description. Forwarding classes Number of forwarding classes supported and in use for the interface. Ingress Queues Information (not shown for all interfaces) Ingress queues Number of input queues supported and in use on the specified interface. Transmitted Transmission statistics for the queue: • Packets—Number of packets transmitted by this queue. • Bytes—Number of bytes transmitted by this queue. • Tail-dropped packets—Number of packets dropped because the queue buffers were full. PFE chassis queues For an interface on an oversubscribed line card, the number of Packet Forwarding Engine chassis queues supported and in use for the port group to which the interface belongs. The Packet Forwarding Engine chassis queue for a port group handles high priority traffic from all the interfaces in the port group. Egress Queues Information Egress queues Number of output queues supported and in use on the specified interface. Queue CoS queue number. Queued This counter is not supported on J-EX Series switches. 1017 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 138: show interfaces queue Output Fields (continued) Field Name Field Description Transmitted Number of packets and bytes transmitted by this queue. Information on transmitted packets and bytes can include: • Packets—Number of packets transmitted. • Bytes—Number of bytes transmitted. • Tail-dropped packets—Number of arriving packets dropped because output queue buffers were full. • RED-dropped packets—Number of packets dropped because of random early detection (RED). • • Low—Number of low loss priority packets dropped because of RED. • High—Number of high loss priority packets dropped because of RED. RED-dropped bytes—Number of bytes dropped because of random early detection (RED). Packet Forwarding Engine Chassis Queues show interfaces queue ge-0/0/0 1018 • Low—Number of low loss priority bytes dropped because of RED. • High—Number of high loss priority bytes dropped because of RED. For an interface on an oversubscribed line card, the number of Packet Forwarding Engine chassis queues supported and in use for the port group to which the interface belongs. The queue statistics reflect the traffic flowing on all the interfaces in the port group. user@switch> show interfaces queue ge–0/0/0 Physical interface: ge-0/0/0, Enabled, Physical link is Down Interface index: 130, SNMP ifIndex: 501 Forwarding classes: 16 supported, 4 in use Egress queues: 8 supported, 4 in use Queue: 0, Forwarding classes: best-effort Queued: Transmitted: Packets : 0 Bytes : 0 Tail-dropped packets : 0 Queue: 1, Forwarding classes: assured-forwarding Queued: Transmitted: Packets : 0 Bytes : 0 Tail-dropped packets : 0 Queue: 5, Forwarding classes: expedited-forwarding Queued: Transmitted: Packets : 0 Bytes : 0 Tail-dropped packets : 0 Queue: 7, Forwarding classes: network-control Queued: Transmitted: Packets : 0 Bytes : 0 Tail-dropped packets : 0 Chapter 56: Operational Mode Commands for Interfaces show interfaces xeSyntax show interfaces xe-fpc/pic/port Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display status information about the specified 10-Gigabit Ethernet interface. Options xe-fpc/pic/port —Display standard information about the specified 10-Gigabit Ethernet interface. brief | detail | extensive | terse—(Optional) Display the specified level of output. descriptions—(Optional) Display interface description strings. media—(Optional) Display media-specific information about network interfaces. snmp-index snmp-index —(Optional) Display information for the specified SNMP index of the interface. statistics—(Optional) Display static interface statistics. Required Privilege Level Related Documentation view • Monitoring Interface Status and Traffic on page 931 • Troubleshooting Network Interfaces on J-EX4200 Switches on page 939 • Troubleshooting an Aggregated Ethernet Interface on page 940 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output Output Fields show interfaces xe-0/1/0 on page 1026 show interfaces xe-4/1/0 on page 1027 show interfaces xe-0/1/0 brief on page 1027 show interfaces xe-4/1/0 detail on page 1027 show interfaces xe-4/1/0 extensive on page 1028 Table 139 on page 1020 lists the output fields for the show interfaces xe- command. Output fields are listed in the approximate order in which they appear. 1019 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 139: show interfaces xe- Output Fields Field Name Field Description Level of Output Physical interface Name of the physical interface. All levels Enabled State of the interface. All levels Interface index Index number of the physical interface, which reflects its initialization sequence. detail extensive none SNMP ifIndex SNMP index number for the physical interface. detail extensive none Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive Link-level type Encapsulation being used on the physical interface. All levels MTU Maximum transmission unit size on the physical interface. All levels Speed Speed at which the interface is running. All levels Duplex Duplicity of the interface. All levels BPDU Error blah blah All levels Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback: Local or Remote. All levels Source filtering Source filtering status: Enabled or Disabled. All levels Flow control Flow control status: Enabled or Disabled. All levels Device flags Information about the physical device. All levels Interface flags Information about the interface. All levels Link flags Information about the link. All levels Wavelength Configured wavelength, in nanometers (nm). All levels Frequency Frequency associated with the configured wavelength, in terahertz (THz). All levels CoS queues Number of CoS queues configured. detail extensive none Schedulers Number of CoS schedulers configured. extensive Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive Current address Configured MAC address. detail extensive none Physical Interface 1020 Chapter 56: Operational Mode Commands for Interfaces Table 139: show interfaces xe- Output Fields (continued) Field Name Field Description Level of Output Hardware address Hardware MAC address. detail extensive none Last flapped Date, time, and how long ago the interface went from down to up. The format is Last flapped: year-month-day hour::minute:second: timezone (dayd hour:minute:second ago). For example, Last flapped: 2008–01–16 10:52:40 UTC detail extensive none (3d 22:58 ago). Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified Output Rate Output rate in bps and pps. None specified Statistics last cleared Time when the statistics for the interface were last set to zero. detail extensive Traffic statistics Number and rate of bytes and packets received and transmitted on the physical interface. detail extensive • Input bytes—Number of bytes received on the interface. • Output bytes—Number of bytes transmitted on the interface. • Input packets—Number of packets received on the interface • Output packets—Number of packets transmitted on the interface. NOTE: The bandwidth bps counter is not enabled on the switch. Input errors Input errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious: • Errors—Sum of the incoming frame aborts and FCS errors. • Drops—Number of packets dropped by the input queue of the I/O Manager extensive ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism. • Framing errors—Number of packets received with an invalid frame checksum (FCS). • Runts—Number of frames received that are smaller than the runt threshold. • Policed discards—Number of frames that the incoming packet match code discarded because they were not recognized or not of interest. Usually, this field reports protocols that the Junos OS does not handle. • L3 incompletes—Number of incoming packets discarded because they failed Layer 3 sanity checks of the header. For example, a frame with less than 20 bytes of available IP header is discarded. L3 incomplete errors can be ignored if you configure the ignore-l3-incompletes statement. • L2 channel errors—Number of times the software did not find a valid logical interface for an incoming frame. • L2 mismatch timeouts—Number of malformed or short packets that caused the incoming packet handler to discard the frame as unreadable. • FIFO errors—Number of FIFO errors in the receive direction that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. • Resource errors—Sum of transmit drops. 1021 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 139: show interfaces xe- Output Fields (continued) Field Name Field Description Level of Output Output errors Output errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious: extensive • Carrier transitions—Number of times the interface has gone from down to up. This number does not normally increment quickly, increasing only when the cable is unplugged, the far-end system is powered down and then up, or another problem occurs. If the number of carrier transitions increments quickly (perhaps once every 10 seconds), the cable, the far-end system, or the PIC or PIM is malfunctioning. • Errors—Sum of the outgoing frame aborts and FCS errors. • Drops—Number of packets dropped by the output queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism. • Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC supports only full-duplex operation, so for Gigabit Ethernet PICs, this number should always remain 0. If it is nonzero, there is a software bug. • Aged packets—Number of packets that remained in shared packet SDRAM so long that the system automatically purged them. The value in this field should never increment. If it does, it is most likely a software bug or possibly malfunctioning hardware. • FIFO errors—Number of FIFO errors in the send direction as reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. • HS link CRC errors—Number of errors on the high-speed links between the ASICs responsible for handling the switch interfaces. • MTU errors—Number of packets whose size exceeded the MTU of the interface. • Resource errors—Sum of transmit drops. Ingress queues Total number of ingress queues supported on the specified interface. extensive Queue counters Statistics for the CoS low and high priority ingress queues: extensive (Ingress) • Queued packets—Number of queued packets. • Transmitted packets—Number of transmitted packets. • Dropped packets—Number of packets dropped by the ASIC's RED mechanism. Egress queues Total number of egress queues supported on the specified interface. detail extensive Queue counters Statistics for the CoS egress queues: detail extensive (Egress) PFE Egress queues 1022 • Queued packets—Number of queued packets. • Transmitted packets—Number of transmitted packets. • Dropped packets—Number of packets dropped by the ASIC's RED mechanism. Total number of Packet Forwarding Engine egress queues shared by the interfaces in a port group. Displayed for an interface on a 40–port SFP+ line card. detail extensive Chapter 56: Operational Mode Commands for Interfaces Table 139: show interfaces xe- Output Fields (continued) Field Name Field Description Level of Output Queue counters Statistics for the Packet Forwarding Engine egress queues: detail extensive (Packet Forwarding Engine Egress) • Queued packets—Number of queued packets. • Transmitted packets—Number of transmitted packets. • Dropped packets—Number of packets dropped by the ASIC's RED mechanism. Displayed for an interface on a 40–port SFP+ line card. Active alarms and Active defects Ethernet-specific defects that can prevent the interface from passing packets. When a defect persists for a certain amount of time, it is promoted to an alarm. Based on the switch configuration, an alarm can ring the red or yellow alarm bell on the switch or turn on the red or yellow alarm LED on the front of the switch. These fields can contain the value None or Link. • None—There are no active defects or alarms. • Link—Interface has lost its link state, which usually means that the cable is detail extensive none unplugged, the far-end system has been turned off, or the PIC is malfunctioning. PCS statistics Physical Coding Sublayer (PCS) fault conditions from the LAN PHY device. detail extensive MAC statistics Receive and Transmit statistics reported by the PIC's MAC subsystem. extensive • Total octets and total packets—Total number of octets and packets. For Gigabit Ethernet IQ PICs, the received octets count varies by interface type. • Unicast packets, Broadcast packets, and Multicast packets—Number of unicast, broadcast, and multicast packets. • CRC/Align errors—Total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). • FIFO error—Number of FIFO errors that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. • MAC control frames—Number of MAC control frames. • MAC pause frames—Number of MAC control frames with pause operational code. • Oversized frames—Number of frames that exceed 1518 octets. • Jabber frames—Number of frames that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. This definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition in which any packet exceeds 20 ms. The allowed range to detect jabber is from 20 ms to 150 ms. • Fragment frames—Total number of packets that were less than 64 octets in length (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. Fragment frames normally increment because both runts (which are normal occurrences caused by collisions) and noise hits are counted. • Code violations—Number of times an event caused the PHY to indicate “Data reception error” or “invalid data symbol error.” 1023 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 139: show interfaces xe- Output Fields (continued) Field Name Field Description Level of Output Filter statistics Receive and Transmit statistics reported by the PIC's MAC address filter extensive subsystem. Autonegotiation information Information about link autonegotiation: • extensive Negotiation status: • Incomplete—Ethernet interface has the speed or link mode configured. • No autonegotiation—Remote Ethernet interface has the speed or link mode configured or does not perform autonegotiation. • Complete—Ethernet interface is connected to a device that performs autonegotiation and the autonegotiation process is successful. • Link partner status—OK when Ethernet interface is connected to a device that performs autonegotiation and the autonegotiation process is successful. • Link partner: • Link mode—Depending on the capability of the attached Ethernet device, either Full-duplex or Half-duplex. • Flow control—Types of flow control supported by the remote Ethernet device. For Fast Ethernet interfaces, the type is None. For Gigabit Ethernet interfaces, types are Symmetric (link partner supports PAUSE on receive and transmit), Asymmetric (link partner supports PAUSE on transmit), and Symmetric/Asymmetric (link partner supports PAUSE on both receive and transmit or PAUSE only on receive). • Remote fault—Remote fault information from the link partner—Failure indicates a receive link error. OK indicates that the link partner is receiving. Negotiation error indicates a negotiation error. Offline indicates that the link partner is going offline. • Local resolution—Information from the link partner: • Flow control—Types of flow control supported by the remote Ethernet device. For Gigabit Ethernet interfaces, types are Symmetric (link partner supports PAUSE on receive and transmit), Asymmetric (link partner supports PAUSE on transmit), and Symmetric/Asymmetric (link partner supports PAUSE on both receive and transmit or PAUSE only on receive). • Remote fault—Remote fault information. Link OK (no error detected on receive), Offline (local interface is offline), and Link Failure (link error detected on receive). Packet Forwarding Engine configuration Information about the configuration of the Packet Forwarding Engine: • Destination slot—FPC slot number. NOTE: For a J-EX4200 standalone switch, the FPC slot number refers to the switch itself and is always 0. In a Virtual Chassis configuration, FPC slot number refers to the member ID. In a J-EX8200 switch, the FPC slot number refers to the line card slot number. 1024 extensive Chapter 56: Operational Mode Commands for Interfaces Table 139: show interfaces xe- Output Fields (continued) Field Name Field Description CoS Information Information about the CoS queue for the physical interface: • Direction—Queue direction, either Input or Output. • CoS transmit queue—Queue number and its associated user-configured Level of Output forwarding class name. • • Bandwidth—Information about bandwidth allocated to the queue: • %—Bandwidth allocated to the queue as a percentage • bps—Bandwidth allocated to the queue in bps Buffer—Information about buffer space allocated to the queue: • %—Buffer space allocated to the queue as a percentage. • usec—Buffer space allocated to the queue in microseconds. This value is nonzero only if the buffer size is configured in terms of time. • Priority—Queue priority: low or high. • Limit—Displayed if rate limiting is configured for the queue. Possible values are none and exact. If exact is configured, the queue transmits only up to the configured bandwidth, even if excess bandwidth is available. If none is configured, the queue transmits beyond the configured bandwidth if bandwidth is available. Logical Interface Logical interface Name of the logical interface. All levels Index Index number of the logical interface, which reflects its initialization sequence. detail extensive none SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none Generation Unique number for use by Dell technical support only. detail extensive Flags Information about the logical interface. All levels Encapsulation Encapsulation on the logical interface. All levels Protocol Protocol family. detail extensive none Traffic statistics Number and rate of bytes and packets received (input) and transmitted (output) on the specified interface. detail extensive IPv6 transit statistics If IPv6 statistics tracking is enabled, number of IPv6 bytes and packets received and transmitted on the logical interface. extensive Local statistics Number and rate of bytes and packets destined to and from the switch. extensive Transit statistics Number and rate of bytes and packets transiting the switch. extensive Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive 1025 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 139: show interfaces xe- Output Fields (continued) Field Name Field Description Level of Output Route Table Route table in which the logical interface address is located. For example, 0 refers to the routing table inet.0. detail extensive none Input Filters Names of any input filters applied to this interface. detail extensive Output Filters Names of any output filters applied to this interface. detail extensive Flags Information about protocol family flags. detail extensive If unicast reverse-path forwarding (RPF) is explicitly configured on the specified interface, the uRPF flag is display. If unicast RPF was configured on a different interface (and therefore is enabled on all switch interfaces) but was not explicitly configured on the specified interface, the uRPF flag is not displayed even though unicast RPF is enabled. Addresses, Flags Information about the address flags. detail extensive none protocol-family Protocol family configured on the logical interface. If the protocol is inet, the IP address of the interface is also displayed. brief Flags Information about the address flags. detail extensive none Destination IP address of the remote side of the connection. detail extensive none Local IP address of the logical interface. detail extensive none Broadcast Broadcast address of the logical interlace. detail extensive none Generation Unique number for use by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive show interfaces xe-0/1/0 1026 user@switch> show interfaces xe-0/1/0 Physical interface: xe-0/1/0, Enabled, Physical link is Up Interface index: 153, SNMP ifIndex: 69 Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Current address: 00:19:e2:50:c8:99, Hardware address: 00:19:e2:50:c8:99 Last flapped : 2008-02-25 05:28:08 UTC (00:12:49 ago) Input rate : 0 bps (0 pps) Output rate : 0 bps (0 pps) Active alarms : None Active defects : None Logical interface xe-0/1/0.0 (Index 88) (SNMP ifIndex 70) Flags: SNMP-Traps Encapsulation: ENET2 Input packets : 0 Output packets: 0 Protocol eth-switch Chapter 56: Operational Mode Commands for Interfaces Flags: None show interfaces xe-4/1/0 user@switch show interfaces xe-4/1/0 Physical interface: xe-4/1/0, Enabled, Physical link is Up Interface index: 387, SNMP ifIndex: 369 Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Duplex: Full-Duplex, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Current address: 00:23:9c:03:8e:70, Hardware address: 00:23:9c:03:8e:70 Last flapped : 2009-05-12 08:01:04 UTC (00:13:44 ago) Input rate : 36432 bps (3 pps) Output rate : 0 bps (0 pps) Active alarms : None Active defects : None Logical interface xe-4/1/0.0 (Index 66) (SNMP ifIndex 417) Flags: SNMP-Traps Encapsulation: ENET2 Input packets : 0 Output packets: 0 Protocol eth-switch Flags: None show interfaces xe-0/1/0 brief user@switch> show interfaces xe-0/1/0 brief Physical interface: xe-0/1/0, Enabled, Physical link is Up Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None Logical interface xe-0/1/0.0 Flags: SNMP-Traps Encapsulation: ENET2 eth-switch show interfaces xe-4/1/0 detail user@switch> show interfaces xe-4/1/0 detail Physical interface: xe-4/1/0, Enabled, Physical link is Up Interface index: 387, SNMP ifIndex: 369, Generation: 390 Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Duplex: Full-Duplex, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:23:9c:03:8e:70, Hardware address: 00:23:9c:03:8e:70 Last flapped : 2009-05-12 08:01:04 UTC (00:13:49 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 4945644 48576 bps Output bytes : 0 0 bps Input packets: 3258 4 pps Output packets: 0 0 pps IPv6 transit statistics: Input bytes : 0 1027 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output bytes : 0 Input packets: 0 Output packets: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 0 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 0 0 Active alarms : None Active defects : None Logical interface xe-4/1/0.0 (Index 66) (SNMP ifIndex 417) Flags: SNMP-Traps Encapsulation: ENET2 Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Local statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Protocol eth-switch, Generation: 174, Route table: 0 Flags: None Input Filters: f1, Output Filters: f2,,,, show interfaces xe-4/1/0 extensive 1028 (Generation 158) 0 0 0 0 bps bps pps pps user@switch> show interfaces xe-4/1/0 extensive Physical interface: xe-4/1/0, Enabled, Physical link is Up Interface index: 387, SNMP ifIndex: 369, Generation: 390 Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Duplex: Full-Duplex, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:23:9c:03:8e:70, Hardware address: 00:23:9c:03:8e:70 Last flapped : 2009-05-12 08:01:04 UTC (00:14:01 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 5015472 36432 bps Output bytes : 0 0 bps Input packets: 3304 3 pps Output packets: 0 0 pps IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Chapter 56: Operational Mode Commands for Interfaces Input packets: 0 Output packets: 0 Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0 Output errors: Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 0 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 0 0 Active alarms : None Active defects : None MAC statistics: Receive Total octets 5015472 Total packets 3304 Unicast packets 3304 Broadcast packets 0 Multicast packets 0 CRC/Align errors 0 FIFO errors 0 MAC control frames 0 MAC pause frames 0 Oversized frames 0 Jabber frames 0 Fragment frames 0 Code violations 0 Packet Forwarding Engine configuration: Destination slot: 4 Direction : Output CoS transmit queue Bandwidth Limit % bps 0 best-effort 95 9500000000 none 7 network-control 5 500000000 none Transmit 0 0 0 0 0 0 0 0 0 Buffer Priority % 95 usec NA low 5 NA low Logical interface xe-4/1/0.0 (Index 66) (SNMP ifIndex 417) (Generation 158) Flags: SNMP-Traps Encapsulation: ENET2 Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Local statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Transit statistics: 1029 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Protocol eth-switch, Generation: 174, Route table: 0 Flags: None Input Filters: f1, Output Filters: f2,,,, 1030 0 0 0 0 bps bps pps pps Chapter 56: Operational Mode Commands for Interfaces show ipv6 neighbors Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show ipv6 neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the IPv6 neighbor cache. This command has no options. view • clear ipv6 neighbors on page 990 show ipv6 neighbors on page 1031 show ipv6 neighbors on page 1031 Table 140 on page 1031 describes the output fields for the show ipv6 neighbors command. Output fields are listed in the approximate order in which they appear. Table 140: show ipv6 neighbors Output Fields show ipv6 neighbors show ipv6 neighbors Field Name Field Description IPv6 Address Name of the IPv6 interface. Linklayer Address Link-layer address. State State of the link: up, down, incomplete, reachable, stale, or unreachable. Exp Number of seconds until the entry expires. Rtr Whether the neighbor is a routing device: yes or no. Secure Whether this entry was created using the Secure Neighbor Discovery (SEND) protocol: yes or no. Interface Name of the interface. user@host> show ipv6 neighbors IPv6 Address Linklayer Address fe80::2a0:c9ff:fe5b:4c1e 00:a0:c9:5b:4c:1e user@host > show ipv6 neighbors IPv6 Address Linklayer Address Interface State reachable Exp 15 Rtr yes Interface fxp0.0 State Exp Rtr Secure 1031 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS fe80::14fb:5dcf:54bd:ff76 ge-3/2/0.0 1032 00:90:69:a0:a8:bc stale 1113 yes yes Chapter 56: Operational Mode Commands for Interfaces show lacp interfaces Syntax Release Information Description Options show lacp interfaces interface-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Link Aggregation Control Protocol (LACP) information about the specified aggregated Ethernet or Gigabit Ethernet interface. none—Display LACP information for all interfaces. interface-name—(Optional) Display LACP information for the specified interface: Required Privilege Level Related Documentation • Aggregated Ethernet—aex • Gigabit Ethernet—ge-fpc/pic/port view • Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 740 • Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a Virtual Chassis Access Switch and a Virtual Chassis Distribution Switch on page 746 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ List of Sample Output Output Fields show lacp interfaces (Aggregated Ethernet) on page 1036 Table 141 on page 1033 lists the output fields for the show lacp interfaces command. Output fields are listed in the approximate order in which they appear. Table 141: show lacp interfaces Output Fields Field Name Field Description Aggregated interface Aggregated Ethernet interface value. 1033 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 141: show lacp interfaces Output Fields (continued) Field Name Field Description LACP State LACP state information for each aggregated Ethernet interface: • For a child interface configured with force-up, LACP state displays FUP along with the interface name. • Role—Role played by the interface. It can be one of the following: • • Actor—Local device participating in LACP negotiation. • Partner—Remote device participating in LACP negotiation. Exp—Expired state. Yes indicates the actor or partner is in an expired state. No indicates the actor or partner is not in an expired state. • Def—Default. Yes indicates that the actor’s receive machine is using the default operational partner information, administratively configured for the partner. No indicates the operational partner information in use has been received in an LACP PDU. • Dist—Distribution of outgoing frames. No indicates distribution of outgoing frames on the link is currently disabled and is not expected to be enabled. Otherwise, the value is Yes. • Col—Collection of incoming frames. Yes indicates collection of incoming frames on the link is currently enabled and is not expected to be disabled. Otherwise, the value is No. • Syn—Synchronization. If the value is Yes, the link is considered synchronized. It has been allocated to the correct link aggregation group, the group has been associated with a compatible aggregator, and the identity of the link aggregation group is consistent with the system ID and operational key information transmitted. If the value is No, the link is not synchronized. It is currently not in the right aggregation. • Aggr—Ability of aggregation port to aggregate (Yes) or to operate only as an individual link (No). • Timeout—LACP timeout preference. Periodic transmissions of LACP PDUs occur at either a slow or fast transmission rate, depending upon the expressed LACP timeout preference (Long Timeout or Short Timeout). • Activity—Actor or partner’s port activity. Passive indicates the port’s preference for not transmitting LAC PDUs unless its partner’s control value is Active. Active indicates the port’s preference to participate in the protocol regardless of the partner’s control value. 1034 Chapter 56: Operational Mode Commands for Interfaces Table 141: show lacp interfaces Output Fields (continued) Field Name Field Description LACP Protocol LACP protocol information for each aggregated interface: • Link state (active or standby) indicated in parentheses next to the interface when link protection is configured. • Receive State—One of the following values: • Current—The state machine receives an LACP PDU and enters the Current state. • Defaulted—If no LACP PDU is received before the timer for the Current state expires a second time, the state machine enters the Defaulted state. • Expired—If no LACP PDU is received before the timer for the Current state expires once, the state machine enters the Expired state. • Initialize—When the physical connectivity of a link changes or a Begin event occurs, the state machine enters the Initialize state. • LACP Disabled—If the port is operating in half duplex, the operation of LACP is disabled on the port, forcing the state to LACP Disabled. This state is similar to the Defaulted state, except that the port is forced to operate as an individual port. • • • Port Disabled—If the port becomes inoperable and a Begin event has not occurred, the state machine enters the Port Disabled state. Transmit State—Transmit state of state machine. One of the following values: • Fast Periodic—Periodic transmissions are enabled at a fast transmission rate. • No Periodic—Periodic transmissions are disabled. • Periodic Timer—Transitory state entered when the periodic timer expires. • Slow Periodic—Periodic transmissions are enabled at a slow transmission rate. Mux State—State of the multiplexer state machine for the aggregation port. The state is one of the following values: • Attached—Multiplexer state machine initiates the process of attaching the port to the selected aggregator. • Collecting—Yes indicates that the receive function of this link is enabled with respect to its participation in an aggregation. Received frames are passed to the aggregator for collection. No indicates the receive function of this link is not enabled. • Collecting Distributing—Collecting and distributing states are merged together to form a combined state (coupled control). Because independent control is not possible, the coupled control state machine does not wait for the partner to signal that collection has started before enabling both collection and distribution. • Detached—Process of detaching the port from the aggregator is in progress. • Distributing—Yes indicates that the transmit function of this link is enabled with respect to its participation in an aggregation. Frames may be passed down from the aggregator’s distribution function for transmission. No indicates the transmit function of this link is not enabled. • LACP Statistics Waiting—Multiplexer state machine is in a holding process, awaiting an outcome. LACP statistics are returned when the extensive option is used and provides the following information: • LACP Rx—LACP received counter that increments for each normal hello. • LACP Tx—Number of LACP transmit packet errors logged. • Unknown Rx—Number of unrecognized packet errors logged. • Illegal Rx—Number of invalid packets received. 1035 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show lacp interfaces (Aggregated Ethernet) user@host> show lacp interfaces ae0 extensive Aggregated interface: ae0 LACP state: Role Exp Def Dist ge-1/0/1FUP Actor No Yes No ge-1/0/1FUP Partner No Yes No ge-1/0/2 Actor No Yes No ge-1/0/2 Partner No Yes LACP protocol: ge-1/0/1FUP distributing ge-1/0/2 distributing ge-1/0/1 (active) distributing ge-1/0/2 (standby) LACP Statistics: ge-1/0/1 ge-1/0/2 1036 Receive State CURRENT No Col Syn Aggr Timeout Activity No No Yes Fast Active No No No No No No Yes Yes Yes Fast Passive Fast Fast Active Passive Transmit State Fast periodic Mux State Collecting CURRENT Fast periodic Collecting CURRENT Fast periodic Collecting CURRENT LACP Rx 0 0 Fast periodic LACP Tx Unknown Rx 0 0 0 0 WAITING Illegal Rx 0 0 Chapter 56: Operational Mode Commands for Interfaces test interface restart-auto-negotiation Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields test interface restart-auto-negotiation test interface restart-auto-negotiation interface-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Restarts auto-negotiation on a Fast Ethernet or Gigabit Ethernet interface. interface-name—Interface name: fe-fpc/pic/port or ge-fpc/pic/port. view test interface restart-auto-negotiation on page 1037 Use the show interfaces extensive command to see the state for auto-negotiation. user@host> test interface restart-auto-negotiation fe-1/0/0 1037 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1038 PART 13 Layer 2 Bridging and VLANs • Bridging and VLANs—Overview on page 1041 • Examples: Bridging and VLAN Configuration on page 1063 • Configuring Bridging and VLANs on page 1133 • Verifying Bridging and VLAN Configuration on page 1155 • Troubleshooting Bridging and VLAN Configuration on page 1165 • Configuration Statements for Bridging and VLANs on page 1167 • Operational Mode Commands for Bridging and VLANs on page 1225 1039 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1040 CHAPTER 57 Bridging and VLANs—Overview • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Understanding Private VLANs on J-EX Series Switches on page 1047 • Understanding Virtual Routing Instances on J-EX Series Switches on page 1048 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 • Understanding Proxy ARP on EX Series Switches on page 1059 • Understanding MAC Notification on J-EX Series Switches on page 1060 Understanding Bridging and VLANs on J-EX Series Switches Network switches use Layer 2 bridging protocols to discover the topology of their LAN and to forward traffic toward destinations on the LAN. This topic explains the following concepts regarding bridging and VLANs on J-EX Series Switches: • Ethernet LANs, Transparent Bridging, and VLANs on page 1041 • How Bridging Works on page 1042 • Types of Switch Ports on page 1044 • IEEE 802.1Q Encapsulation and Tags on page 1044 • Assignment of Traffic to VLANs on page 1044 • Ethernet Switching Tables on page 1045 • Layer 2 and Layer 3 Forwarding of VLAN Traffic on page 1045 • GVRP and MVRP on page 1045 • Routed VLAN Interface on page 1046 Ethernet LANs, Transparent Bridging, and VLANs Ethernet is a data link layer technology, as defined by Layer 2 of the Open Systems Interconnection (OSI) model of communications protocols. Ethernet was first 1041 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS standardized by the IEEE in 1982, in IEEE 802.3. Ethernet is used to create LANs. The network devices, called nodes, on the LAN transmit data in bundles that are generally called frames or packets. Each node on a LAN has a unique identifier so that it can be unambiguously located on the network. Ethernet uses the Layer 2 media access control (MAC) address for this purpose. MAC addresses are hardware addresses that are programmed (“burned”) into the Ethernet processor in the node. A characteristic of Ethernet is that nodes on a LAN can transmit data frames at any time. However, the physical connecting cable between the nodes—either coaxial, copper-based (Category 5), or optical cable—can carry only a single stream of data at a time. One result of this design is that when two nodes transmit at the same time, their frames can collide on the cable and generate an error. Ethernet uses a protocol called carrier-sense multiple access with collision detection (CSMA/CD) to detect frame collisions. If a node receives a collision error message, it stops transmitting immediately and waits for a period of time before trying to send the frame again. If the node continues to detect collisions, it progressively increases the time between retransmissions in an attempt to find a time when no other data is being transmitted on the LAN. The node uses a backoff algorithm to calculate the increasing retransmission time intervals. Ethernet LANs were originally implemented for small, simple networks that carried primarily text. Over time, LANs have become larger and more complex; the type of data they carry has grown to include voice, graphics, and video; and the increased speed of Ethernet interfaces on LANs has resulted in exponential increases in traffic on the network. The IEEE 802.1D-2004 standard addresses some of the problems caused by the increase in LAN and complexity. This standard defines transparent bridging (generally called simply bridging). Bridging divides a single physical LAN (a single broadcast domain) into two or more virtual LANs, or VLANs. Each VLAN is a collection of network nodes that are grouped together to form separate broadcast domains. On an Ethernet network that is a single LAN, all traffic is forwarded to all nodes on the LAN. On VLANs, frames whose origin and destination are in the same VLAN are forwarded only within the local VLAN. Frames that are not destined for the local VLAN are the only ones forwarded to other broadcast domains. VLANs thus limit the amount of traffic flowing across the entire LAN, reducing the possible number of collisions and packet retransmissions within a VLAN and on the LAN as a whole. On an Ethernet LAN, all network nodes must be physically connected to the same network. On VLANs, the physical location of the nodes is not important, so you can group network devices in any way that makes sense for your organization, such as by department or business function, types of network nodes, or even physical location. Each VLAN is identified by a single IP subnetwork and by standardized IEEE 802.1Q encapsulation (discussed below). How Bridging Works The transparent bridging protocol allows a switch to learn information about all the nodes on the LAN, including nodes on all the different VLANs. The switch uses this information to create address-lookup tables, called Ethernet switching tables that it consults when forwarding traffic to or toward a destination on the LAN. 1042 Chapter 57: Bridging and VLANs—Overview Transparent bridging uses five mechanisms to create and maintain Ethernet switching tables on the switch: • Learning • Forwarding • Flooding • Filtering • Aging The first bridging mechanism is learning. When a switch is first connected to an Ethernet LAN or VLAN, it has no information about other nodes on the network. The switch goes through a learning process to obtain the MAC addresses of all the nodes on the network. It stores these in the Ethernet switching table. To learn MAC addresses, the switch reads all packets that it detects on the LAN or on the local VLAN, looking for MAC addresses of sending nodes. It places these addresses into its Ethernet switching table, along with two other pieces of information—the interface (or port) on which the traffic was received and the time when the address was learned. The second bridging mechanism is forwarding. Switches forward traffic, passing it from an incoming interface to an outgoing interface that leads to or toward the destination. To forward frames, the switch consults the Ethernet switching table to see whether the table contains the MAC address corresponding to the frames' destination. If the Ethernet switching table contains an entry for the desired destination address, the switch sends the traffic out the interface associated with the MAC address. The switch also consults the Ethernet switching table in the same way when transmitting frames that originate on devices connected directly to the switch. If the Ethernet switching table does not contain an entry for the desired destination address, the switch uses flooding, which is the third bridging mechanism. Flooding is how the switch learns about destinations not in its Ethernet switching table. If this table has no entry for a particular destination MAC address, the switch floods the traffic out all interfaces except the interface on which it was received. (If traffic originates on the switch, the switch floods it out all interfaces.) When the destination node receives the flooded traffic, it sends an acknowledgment packet back to the switch, allowing it to learn the MAC address of the node and to add the address to its Ethernet switching table. Filtering, the fourth bridging mechanism, is how broadcast traffic is limited to the local VLAN whenever possible. As the number of entries in the Ethernet switching table grows, the switch pieces together an increasingly complete picture of the VLAN and the larger LAN—of which nodes are in the local VLAN and which are on other network segments. The switch uses this information to filter traffic. Specifically, for traffic whose source and destination MAC addresses are in the local VLAN, filtering prevents the switch from forwarding this traffic to other network segments. Finally, the switch uses aging, the fifth bridging mechanism, to keep the entries in the Ethernet switching table current. For each MAC address in the Ethernet switching table, the switch records a timestamp of when the information about the network node was learned. Each time the switch detects traffic from a MAC address, it updates the 1043 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS timestamp. A timer on the switch periodically checks the timestamp, and if it is older than a user-configured value, the switch removes the node's MAC address from the Ethernet switching table. This aging process ensures that the switch tracks only active nodes on the network and that it is able to flush out network nodes that are no longer available. Types of Switch Ports The ports, or interfaces, on a switch operate in either access mode or trunk mode. An interface in access mode connects to a network device, such as a desktop computer, an IP telephone, a printer, a file server, or a security camera. The interface itself belongs to a single VLAN. The frames transmitted over an access interface are normal Ethernet frames. By default, when you boot a switch and use the factory-default configuration, or when you boot the switch and do not explicitly configure a port mode, all interfaces on the switch are in access mode. Trunk interfaces handle traffic for multiple VLANs, multiplexing the traffic for all those VLANs over the same physical connection. Trunk interfaces are generally used to interconnect switches to one another. IEEE 802.1Q Encapsulation and Tags To identify which VLAN traffic belongs to, all frames on an Ethernet VLAN are identified by a tag, as defined in the IEEE 802.1Q standard. These frames are tagged and are encapsulated with 802.1Q tags. For a simple network that has only a single VLAN, all traffic has the same 802.1Q tag. When an Ethernet LAN is divided into VLANs, each VLAN is identified by a unique 802.1Q tag. The tag is applied to all frames so that the network nodes receiving the frames know which VLAN the frames belong to. Trunk ports, which multiplex traffic among a number of VLANs, use the tag to determine to origin of frames and where to forward them. VLANs 0 and 4095 are reserved by the Junos OS, so you cannot use them in your network. Assignment of Traffic to VLANs You assign traffic to a particular VLAN in one of the following ways: 1044 • By interface (port) on the switch. You specify that all traffic received on a particular interface on the switch is assigned to a specific VLAN. If you use the default factory switch settings, all traffic received on an access interface is untagged. This traffic is part of a default VLAN, but it is not tagged with an 802.1Q tag. When configuring the switch, you specify which VLAN to assign the traffic to. You configure the VLAN either by using a VLAN number (called a VLAN ID) or by using a name, which the switch translates into a numeric VLAN ID. • By MAC address. You can specify that all traffic received from a specific MAC address be forwarded to a specific egress interface (next hop) on the switch. This method is administratively cumbersome to configure manually, but it can be useful when you are using automated databases to manage the switches on your network. Chapter 57: Bridging and VLANs—Overview NOTE: If a J-EX4200 Ethernet Switch is interconnected with other switches in a Virtual Chassis configuration, each individual switch that is included as a member of the configuration is identified with a member ID. The member ID functions as an FPC slot number. When you are configuring interfaces for a Virtual Chassis configuration, you specify the appropriate member ID (0 through 9) as the slot element of the interface name. The default factory settings for a Virtual Chassis configuration include FPC 0 as a member of the default VLAN because FPC 0 is configured as part of the ethernet-switching family. In order to include FPC 1 through FPC 9 in the default VLAN, add the ethernet-switching family to the configurations for those interfaces. Ethernet Switching Tables As J-EX Series switches learn the MAC addresses of the devices on local VLANs, they store them in the bridge on the switch. With each MAC address, the Ethernet switching table stores and associates the name of the interface (or port) on which the switch learned that address. The switch uses the information in this table when forwarding packets toward their destination. Layer 2 and Layer 3 Forwarding of VLAN Traffic To pass traffic within a VLAN, the switch uses Layer 2 forwarding protocols, including IEEE 802.1Q, Spanning Tree Protocol (STP), and GARP VLAN Registration Protocol (GVRP). To pass traffic between two VLANs, the switch uses standard Layer 3 routing protocols, such as static routing, OSPF, and RIP. On J-EX Series switches, the same interfaces that support Layer 2 bridging protocols also support Layer 3 routing protocols, providing multilayer switching. GVRP and MVRP The GARP VLAN Registration Protocol (GVRP) and Multiple VLAN Registration Protocol (MVRP) are used to manage dynamic VLAN registration in a LAN. GVRP is an application protocol of the Generic Attribute Registration Protocol (GARP) and is defined in the IEEE 802.1Q standard. GVRP learns VLANs on a particular 802.1Q trunk interface and adds the corresponding trunk interface to the VLAN if the advertised VLAN is preconfigured on the switch. MVRP is an application protocol of the Multiple Registration Protocol (MRP) and is defined in the IEEE 802.1ak standard. MRP and MVRP were designed by IEEE to perform the same functions as GARP and GVRP while overcoming some GARP and GVRP limitations, in particular limitations involving bandwidth usage and convergence times in large networks with large numbers of VLANs. MVRP was created by IEEE as a replacement application for GVRP. 1045 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS The VLAN registration information sent by MVRP and GVRP includes the current VLANs membership—that is, which switches are members of which VLANs—and which switch interfaces are in which VLAN. GVRP and MVRP share all VLAN information configured on a local switch. MVRP can also be used to dynamically create VLANs, which are VLANs created on one switch and propagated to other switches as part of the MVRP message exchange process. As part of ensuring that VLAN membership information is current, GVRP and MVRP remove switches and interfaces from the VLAN information when those switches and interfaces become unavailable. Pruning VLAN information has these benefits: • Limits the network VLAN configuration to active participants only, reducing network overhead. • Targets the scope of broadcast, unknown unicast, and multicast (BUM) traffic to interested devices only. Routed VLAN Interface In a traditional network, broadcast domains consist of either physical interfaces connected to a single switch or logical interfaces connected to one or more switches through VLAN configurations. Switches send traffic to hosts that are part of the same broadcast domain, but routers are needed to route traffic from one broadcast domain to another and to perform other Layer 3 functions such as traffic engineering. J-EX Series switches use a Layer 3 routed VLAN interface (RVI) named vlan to perform these routing functions, using it to route data to other Layer 3 interfaces. The RVI functions as a logical router, eliminating the need for having both a switch and a router. The RVI (the vlan interface) must be configured as part of a broadcast domain or virtual private LAN service (VPLS) routing instance for Layer 3 traffic to be routed out of it. The RVI supports IPv4, IPv6, MPLS, and IS-IS traffic. At least one Layer 2 logical interface must be operational for the RVI to be operational. You must configure a broadcast domain or VPLS routing instance for the RVI just as you would configure a VLAN on the switch. Multicast data, broadcast data, or unicast data is switched between ports within the same RVI broadcast domain or VPLS routing instance. The RVI routes data that is destined for the switch’s media access control (MAC) address. Jumbo frames of up to 9216 bytes are supported on an RVI. To route jumbo data packets on the RVI, you must configure the jumbo MTU size on the member physical interfaces of the RVI and not on the RVI itself (the vlan interface). However, for jumbo control packets—for example, to ping the RVI with a packet size of 6000 bytes or more—you must explicitly configure the jumbo MTU size on the interface named vlan (the RVI). CAUTION: Setting or deleting the jumbo MTU size on the RVI (the vlan interface) while the switch is transmitting packets might result in dropped packets. See “Configuring Routed VLAN Interfaces (CLI Procedure)” on page 1137. 1046 Chapter 57: Bridging and VLANs—Overview To learn more about configuring routing protocols and policies, see the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Related Documentation • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 Understanding Private VLANs on J-EX Series Switches The private VLAN (PVLAN) feature on J-EX Series Switches allows an administrator to split a broadcast domain into multiple isolated broadcast subdomains, essentially putting a VLAN inside a VLAN. Just like regular VLANs, PVLANs are isolated on Layer 2 and require that a Layer 3 device be used to route traffic among them. Private VLANs are useful for restricting the flow of broadcast and unknown unicast traffic and for limiting the communication between known hosts. NOTE: Configuring a voice over IP (VoIP) VLAN on PVLAN interfaces is not supported. In a private VLAN, one VLAN is designated the primary VLAN, and other VLANs are nested inside that VLAN as secondary VLANs. • Primary—A VLAN used to forward frames downstream to isolated and community VLANs. • Isolated—A secondary VLAN that receives packets only from the primary VLAN and forwards frames upstream to the primary VLAN. • Community—A secondary VLAN that transports frames among community interfaces within the same community and forwards frames upstream to the primary VLAN. Private VLANs provide IP address conservation and efficient allocation of those IP addresses. In a typical network, VLANs usually correspond to a single IP subnet. In private VLANs, the hosts in all the secondary VLANs still belong to the same IP subnet as the subnet allocated to the primary VLAN. Hosts within the secondary VLAN are numbered out of IP subnets associated with the primary VLAN, and their IP subnet masking information reflects that of the primary VLAN subnet. Any primary routed VLAN interfaces (RVIs) perform functions similar to proxy ARP to enable communication between hosts that are members of a different secondary VLAN. 1047 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: If you enable no-mac-learning on a primary VLAN, all isolated VLANs in that private VLAN inherit that setting. If you want to disable MAC address learning on any community VLANs, you must configure no-mac-learning on each of those VLANs. Related Documentation • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 • Creating a Private VLAN (CLI Procedure) on page 1143 Understanding Virtual Routing Instances on J-EX Series Switches Virtual routing instances allow administrators to divide a J-EX Series Switch into multiple independent virtual routers, each with its own routing table. Splitting a device into many virtual routing instances isolates traffic traveling across the network without requiring multiple devices to segment the network. You can use virtual routing instances to isolate customer traffic on your network and to bind customer-specific instances to customer-owned interfaces. Virtual routing and forwarding (VRF) is often used in conjunction with Layer 3 subinterfaces, allowing traffic on a single physical interface to be differentiated and associated with multiple virtual routers. Each logical Layer 3 subinterface can belong to only one routing instance. J-EX Series switches support IPv4 and IPv6 unicast and multicast VRF traffic. J-EX4200 Series Ethernet Switches support up to 252 IPv4 virtual routing instances and up to 64 IPv6 virtual routing instances. J-EX8200 Series Ethernet Switches support up to 252 IPv4 and IPv6 virtual routing instances. Related Documentation 1048 • Understanding Layer 3 Subinterfaces on page 871 • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 Chapter 57: Bridging and VLANs—Overview Understanding Redundant Trunk Links on J-EX Series Switches In a typical enterprise network comprised of distribution and access layers, a redundant trunk link provides a simple solution for network recovery when a trunk port goes down. Traffic is routed to another trunk port, keeping network convergence time to a minimum. You can configure a maximum of 16 redundant trunk groups on a standalone switch or on a Virtual Chassis. To configure a redundant trunk link, create a redundant trunk group. The redundant trunk group is configured on the access switch, and contains two links: a primary or active link, and a secondary link. If the active link fails, the secondary link automatically starts forwarding data traffic without waiting for normal STP convergence. Data traffic is forwarded only on the active link. Data Traffic on the secondary link is dropped and shown as dropped packets when you issue the operational mode command show interfaces xe- interface-name extensive. While data traffic is blocked on the secondary link, Layer 2 control traffic is still permitted. For example, an LLDP session can be run between two J-EX Series Switches on the secondary link. STP is enabled by default on J-EX Series switches to create a loop-free topology. When trunk links are placed in a redundant group, they cannot be part of an STP topology. The Junos OS for J-EX Series switches does not allow an interface to be in a redundant trunk group and in an STP topology at the same time. However, STP can continue operating in other parts of the network. For example, STP may continue operating between the distribution switches and linking them to the enterprise core. Figure 26 on page 1050 shows three switches in a basic topology for redundant trunk links. Switch 1 and Switch 2 make up the distribution layer, and Switch 3 makes up the access layer. Switch 3 is connected to the distribution layer through trunk ports ge-0/0/9.0 (Link 1) and ge-0/0/10.0 (Link 2). Link 1 and Link 2 are in a redundant trunk group called group1. Link 1 is designated as the primary link. Traffic flows between Switch 3 in the access layer and Switch 1 in the distribution layer through Link 1. While Link 1 is active, Link 2 blocks traffic. 1049 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 26: Redundant Trunk Group, Link 1 Active Figure 27 on page 1050 illustrates how the redundant trunk link topology works when the primary link goes down. Figure 27: Redundant Trunk Group, Link 2 Active 1050 Chapter 57: Bridging and VLANs—Overview Link 1 is down between Switch 3 and Switch 1. Link 2 takes over as the active link. Traffic between the access layer and the distribution layer is automatically switched to Link 2 between Switch 1 and Switch 2. Related Documentation • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • redundant-trunk-group on page 1218 Understanding Q-in-Q Tunneling on J-EX Series Switches Q-in-Q tunneling allows service providers on Ethernet access networks to extend a Layer 2 Ethernet connection between two customer sites. Using Q-in-Q tunneling, providers can also segregate or bundle customer traffic into fewer VLANs or different VLANs by adding another layer of 802.1Q tags. Q-in-Q tunneling is useful when customers have overlapping VLAN IDs, because the customer’s 802.1Q (dot1Q) VLAN tags are prepended by the service VLAN (S-VLAN) tag. The Junos OS implementation of Q-in-Q tunneling supports the IEEE 802.1ad standard. This topic describes: • How Q-in-Q Tunneling Works on page 1051 • Disabling MAC Address Learning on page 1052 • Mapping C-VLANs to S-VLANs on page 1052 • Routed VLAN Interfaces on Q-in-Q VLANs on page 1053 • Limitations for Q-in-Q Tunneling on page 1054 How Q-in-Q Tunneling Works In Q-in-Q tunneling, as a packet travels from a customer VLAN (C-VLAN) to a service provider's VLAN, a customer-specific 802.1Q tag is added to the packet. This additional tag is used to segregate traffic into service-provider-defined service VLANs (S-VLANs). The original customer 802.1Q tag of the packet remains and is transmitted transparently, passing through the service provider's network. As the packet leaves the S-VLAN in the downstream direction, the extra 802.1Q tag is removed. When Q-in-Q tunneling is enabled on J-EX Series Switches, trunk interfaces are assumed to be part of the service provider network and access interfaces are assumed to be customer facing. An access interface can receive both tagged and untagged frames in this case. An interface can be a member of multiple S-VLANs. You can map one C-VLAN to one S-VLAN (1:1) or multiple C-VLANs to one S-VLAN (N:1). Packets are double-tagged for an additional layer of segregating or bundling of C-VLANs. C-VLAN and S-VLAN tags are unique; so you can have both a C-VLAN 101 and an S-VLAN 101, for example. You can limit the set of accepted customer tags to a range of tags or to discrete values. Class-of-service (CoS) values of C-VLANs are unchanged in the downstream direction. You may, optionally, copy ingress priority and CoS settings to the S-VLAN. Using private VLANs, you can isolate users to prevent the forwarding of traffic between user interfaces even if the interfaces are on the same VLAN. 1051 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS You can use the native option to specify an S-VLAN for untagged and priority tagged packets when using many-to-one bundling and mapping a specific interface approaches to map C-VLANs to S-VLANs. Otherwise the packets are discarded. The native option is not available for all-in-one bundling because there is no need to specify untagged and priority tagged packets when all packets are mapped to the C-VLAN. See the Mapping C-VLANs to S-VLANs section of this document for information on the methods of mapping C-VLANs to S-VLANs. Firewall filters allow you to map an interface to a VLAN based on a policy. Using firewall filters to map an interface to a VLAN is useful when you want a subset of traffic from a port to be mapped to a selected VLAN instead of the designated VLAN. To configure a firewall filter to map an interface to a VLAN, the vlan option has to be configured as part of the firewall filter and the mapping policy option must be specified in the interface configuration for each logical interface using the filter. Disabling MAC Address Learning In a Q-in-Q deployment, customer packets from downstream interfaces are transported without any changes to source and destination MAC addresses. You can disable MAC address learning at both the interface level and the VLAN level. Disabling MAC address learning on an interface disables learning for all the VLANs of which that interface is a member. When you disable MAC address learning on a VLAN, MAC addresses that have already been learned are flushed. If you disable MAC address learning on an interface or a VLAN, you cannot include MAC move limiting or 802.1X authentication in that same VLAN configuration. When a routed VLAN interface (RVI) is associated with either an interface or a VLAN on which MAC address learning is disabled, the Layer 3 routes resolved on that VLAN or that interface are not resolved with the Layer 2 component. This results in routed packets flooding all the interfaces associated with the VLAN. Mapping C-VLANs to S-VLANs There are three ways to map C-VLANs to an S-VLAN: 1052 • All-in-one bundling—Use the dot1q-tunneling option to map without specifying customer VLANs. All packets from all access interfaces are mapped to the S-VLAN. • Many-to-one bundling—Use the customer-vlans option to specify which C-VLANs are mapped to the S-VLAN. • Mapping a specific interface—Use the mapping option to indicate a specific S-VLAN for a given C-VLAN. The specified C-VLAN applies to only one VLAN and not all access interfaces as in the cases of all-in-one and many-to-one bundling. Chapter 57: Bridging and VLANs—Overview If you configure multiple methods, the switch gives priority to mapping a specific interface, then to many-to-one bundling, and last to all-in-one bundling. However, you cannot have overlapping rules for the same C-VLAN under a given approach. • All-in-One Bundling on page 1053 • Many-to-One Bundling on page 1053 • Mapping a Specific Interface on page 1053 All-in-One Bundling All-in-one bundling maps all packets from all access interfaces to the S-VLAN. All-in-one bundling is configured using the dot1q-tunneling option without specifying customer VLANs. When all-in-one bundling is used, all packets leaving the C-VLAN, including untagged and priority tagged packets, enter the S-VLAN. Many-to-One Bundling Many-to-one bundling is used to specify which C-VLANs are mapped to an S-VLAN. Many-to-one bundling is configured using the customer-vlans option. Many-to-one bundling is used when you want a subset of the C-VLANs on the access switch to be part of the S-VLAN. When using many-to-one bundling, untagged and priority tagged packets can be mapped to the S-VLAN when the native option is specified along with the customer-vlans option. Mapping a Specific Interface Use the mapping a specific interface approach when you want to assign an S-VLAN to a specific C-VLAN on an interface. The mapping a specific interface configuration only applies to the configured interface, not to all access interfaces as in the cases of the all-in-one bundling and many-to-one bundling approaches. The mapping a specific interface approach is configured using the mapping option to indicate a specific S-VLAN for a given C-VLAN. The mapping a specific interface approach has two suboptions for treatment of traffic: swap and push. When traffic that is mapped to a specific interface is pushed, the packet retains its tag as it moves between the S-VLAN and C-VLAN and an additional VLAN tag is added to the packet. When traffic that is mapped to a specific interface is swapped, the incoming tag is replaced with a new VLAN tag. Using the swap option is also referred to as VLAN ID translation. It might be useful to have S-VLANs that provide service to multiple customers. Each customer will typically have its own S-VLAN plus access to one or more S-VLANs that are used by multiple customers. A specific tag on the customer side is mapped to an S-VLAN. Typically, this functionality is used to keep data from different customers separate or to provide individualized treatment of the packets on a certain interface. Routed VLAN Interfaces on Q-in-Q VLANs Routed VLAN interfaces (RVIs) are supported on Q-in-Q VLANs. 1053 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Packets arriving on an RVI that is using Q-in-Q VLANs will get routed regardless of whether the packet is single or double tagged. The outgoing routed packets contain an S-VLAN tag only when exiting a trunk interface; the packets exit the interface untagged when exiting an access interface. Limitations for Q-in-Q Tunneling Q-in-Q tunneling does not support most access port security features. There is no per-VLAN (customer) policing or per-VLAN (outgoing) shaping and limiting with Q-in-Q tunneling unless you configure these security features using firewall filters. Related Documentation • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches You can configure Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches. The primary purpose of MVRP is to manage dynamic VLAN registration in a LAN. In managing dynamic VLAN registration, MVRP also prunes VLAN information. MVRP can also be used to dynamically create VLANs in switching networks. MVRP is an application protocol of the Multiple Registration Protocol (MRP) and is defined in the IEEE 802.1ak standard. MRP and MVRP were designed by IEEE to perform the same functions as Generic Attribute Registration Protocol (GARP) and GARP VLAN Registration Protocol (GVRP) while overcoming some GARP and GVRP limitations, in particular limitations involving bandwidth usage and convergence time in large networks with large numbers of VLANs. MVRP was created by IEEE as a replacement application for GVRP. MVRP and GVRP cannot be run concurrently to share VLAN information in a switching network. This topic describes: • How MVRP Works on J-EX Series Switches on page 1054 • Basics of MVRP on J-EX Series Switches on page 1055 • MVRP Registration Modes on page 1055 • MRP Timers on page 1055 • MRP VLAN Messages on page 1056 How MVRP Works on J-EX Series Switches The VLAN registration information sent by MVRP protocol data units (PDUs) includes the current VLANs membership—that is, which switches are members of which VLANs—and which switch interfaces are in which VLAN. MVRP shares all information in the PDU with all switches participating in MVRP in the switching network. MVRP stays synchronized using these PDUs. The MVRP PDUs are sent to other switches on the network only when an MVRP state change occurs. The switches in the network 1054 Chapter 57: Bridging and VLANs—Overview participating in MVRP receive these PDUs during state changes and update their MVRP states accordingly. MVRP timers dictate when PDUs can be sent and when switches receiving MVRP PDUs can update their MVRP information. VLAN information is distributed as part of the MVRP message exchange process and can be used to dynamically create VLANs, which are VLANs created on one switch and propagated to other switches as part of the MVRP message exchange process. Dynamic VLAN creation using MVRP is enabled by default but can be disabled. As part of ensuring that VLAN membership information is current, MVRP removes switches and interfaces from the VLAN information when they become unavailable. Pruning VLAN information has these benefits: • Limits the network VLAN configuration to active participants only, reducing network overhead. • Targets the scope of broadcast, unknown unicast, and multicast (BUM) traffic to interested devices only. Basics of MVRP on J-EX Series Switches MVRP is disabled by default on all J-EX Series switches. You can configure MVRP on J-EX Series switch interfaces to participate in MVRP for the switching network. MVRP can only be enabled on trunk interfaces, and dynamic VLAN configuration through MVRP is enabled by default when MVRP is enabled. MVRP Registration Modes The MVRP registration mode defines whether an interface does or does not participate in MVRP. The following MVRP registration modes are configurable: • forbidden—The interface does not register and does not participate in MVRP. • normal—The interface accepts MVRP messages and participates in MVRP. This is the default registration mode setting. MRP Timers MVRP registration and updates are controlled by timers that are part of the MRP protocol. These timers are set on a per-interface basis and define when MVRP PDUs can be sent and when MVRP information can be updated on a switch. The following timers are used to control the operation of MVRP: • Join timer—Controls the interval for the next MVRP PDU transmit opportunity. • Leave timer—Controls the period of time that an interface on the switch waits in the Leave state before changing to the unregistered state. • LeaveAll timer—Controls the frequency with which the interface generates LeaveAll messages. 1055 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS BEST PRACTICE: Maintain default timer settings unless there is a compelling reason to change the settings. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. MRP VLAN Messages MVRP uses MRP messages to register and declare MVRP states for a switch and to inform the switching network that a switch is leaving MVRP. These messages are communicated as part of the PDU to communicate the state of a particular switch interface on the switching network to the other switches in the network. The following messages are communicated for MVRP: Related Documentation • Empty—VLAN information is not being declared and is not registered. • In—VLAN information is not being declared but is registered. • JoinEmpty—VLAN information is being declared but not registered. • JoinIn—VLAN information is being declared and is registered. • Leave—VLAN information that was previously registered is being withdrawn. • LeaveAll—All registrations will be de-registered. Participants that want to participate in MVRP will need to re-register. • New—VLAN information is new and possibly not previously registered. • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Understanding Layer 2 Protocol Tunneling on J-EX Series Switches Layer 2 protocol tunneling (L2PT) allows you to send Layer 2 protocol data units (PDUs) across a service provider network and deliver them to J-EX Series Switches that are not part of the local broadcast domain. This feature is useful when you want to run Layer 2 protocols on a network that includes switches located at remote sites that are connected across a service provider network. This topic includes: 1056 • Layer 2 Protocols Supported by L2PT on J-EX Series Switches on page 1057 • How L2PT Works on page 1057 • L2PT Basics on J-EX Series Switches on page 1058 Chapter 57: Bridging and VLANs—Overview Layer 2 Protocols Supported by L2PT on J-EX Series Switches L2PT on J-EX Series switches supports the following Layer 2 protocols: • 802.1X authentication • 802.3ah Operation, Administration, and Maintenance (OAM) link fault management (LFM) NOTE: If you enable L2PT for untagged OAM LFM packets, do not configure LFM on the corresponding access interface. • Cisco Discovery Protocol (CDP) • Ethernet local management interface (E-LMI) • GARP VLAN Registration Protocol (GVRP) • Link Aggregation Control Protocol (LACP) NOTE: If you enable L2PT for untagged LACP packets, do not configure LACP on the corresponding access interface. • Link Layer Discovery Protocol (LLDP) • Multiple MAC Registration Protocol (MMRP) • Multiple VLAN Registration Protocol (MVRP) • Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP) • VLAN Spanning Tree Protocol (VSTP) • VLAN Trunking Protocol (VTP) NOTE: CDP and VTP cannot be configured on J-EX Series switches. L2PT does, however, tunnel CDP and VTP PDUs. How L2PT Works L2PT works by encapsulating Layer 2 PDUs, tunneling them across a service provider network, and decapsulating them for delivery to their destination switches. L2PT encapsulates Layer 2 PDUs by enabling the ingress provider edge (PE) device to rewrite the PDUs’ destination media access control (MAC) addresses before forwarding them onto the service provider network. The devices in the service provider network treat these encapsulated PDUs as multicast Ethernet packets. Upon receipt of these PDUs, the egress PE devices decapsulate them by replacing the destination MAC addresses with the address of the Layer 2 protocol that is being tunneled before forwarding the PDUs to their destination switches. 1057 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS L2PT Basics on J-EX Series Switches L2PT is enabled on a per-VLAN basis. When you enable L2PT on a VLAN, all access interfaces are considered to be customer-facing interfaces, all trunk interfaces are considered to be service provider network-facing interfaces, and the specified Layer 2 protocol is disabled on the access interfaces. L2PT only acts on logical interfaces of the family ethernet-switching. NOTE: Access interfaces in an L2PT-enabled VLAN should not receive L2PT-tunneled PDUs. If an access interface does receive L2PT-tunneled PDUs, it might mean that there is a loop in the network. As a result, the interface will be shut down. L2PT is configured under the [edit vlans vlan-name dot1q-tunneling] hierarchy level, meaning Q-in-Q tunneling is (and must be) enabled. If L2PT is not enabled, Layer 2 PDUs are handled in the same way they were handled before L2PT was enabled. NOTE: If the switch receives untagged or priority-tagged Layer 2 control PDUs to be tunnelled, then you must configure the switch to map untagged and priority-tagged packets to an L2PT-enabled VLAN. For more information on assigning untagged and priority-tagged packets to VLANs, see “Understanding Q-in-Q Tunneling on J-EX Series Switches” on page 1051 and “Configuring Q-in-Q Tunneling (CLI Procedure)” on page 1144. Related Documentation 1058 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 Chapter 57: Bridging and VLANs—Overview Understanding Proxy ARP on EX Series Switches You can configure proxy Address Resolution Protocol (ARP) on your J-EX Series Ethernet switch to enable the switch to respond to ARP queries for network addresses by offering its own Ethernet media access control (MAC) address. With proxy ARP enabled, the switch captures and routes traffic to the intended destination. Proxy ARP is useful in situations where hosts are on different physical networks and you do not want to use subnet masking. Because ARP broadcasts are not propagated between hosts on different physical networks, hosts will not receive a response to their ARP request if the destination is on a different subnet. Enabling the switch to act as an ARP proxy allows the hosts to transparently communicate with each other through the switch. Proxy ARP can help hosts on a subnet reach remote subnets without your having to configure routing or a default gateway. • What Is ARP? on page 1059 • Proxy ARP Overview on page 1059 • Best Practices for Proxy ARP on J-EX Series Switches on page 1060 What Is ARP? Ethernet LANs use ARP to map Ethernet MAC addresses to IP addresses. Each device maintains a cache containing a mapping of MAC addresses to IP addresses. The switch maintains this mapping in a cache that it consults when forwarding packets to network devices. If the ARP cache does not contain an entry for the destination device, the host (the DHCP client) broadcasts an ARP request for that device's address and stores the response in the cache. Proxy ARP Overview When proxy ARP is enabled, if the switch receives an ARP request for which it has a route to the target (destination) IP address, the switch responds by sending a proxy ARP reply packet containing its own MAC address. The host that sent the ARP request then sends its packets to the switch, which forwards them to the intended host. NOTE: For security reasons, the source address in an ARP request must be on the same subnet as the interface on which the ARP request is received. You can configure proxy ARP for each interface. You can also configure proxy ARP for a VLAN by using a routed VLAN interface (RVI). J-EX Series switches support two modes of proxy ARP, restricted and unrestricted. Both modes require that the switch have an active route to the destination address of the ARP request. • Restricted—The switch responds to ARP requests in which the physical networks of the source and target are different and does not respond if the source and target IP addresses are on the same subnet. In this mode, hosts on the same subnet communicate without proxy ARP. We recommend that you use this mode on the switch. 1059 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Unrestricted—The switch responds to all ARP requests for which it has a route to the destination. This is the default mode (because it is the default mode in the Junos operating system (Junos OS) configurations other than those on the switch). We recommend using restricted mode on the switch. Best Practices for Proxy ARP on J-EX Series Switches We recommend these best practices for configuring proxy ARP on the switches: Related Documentation • Set proxy ARP to restricted mode. • Use restricted mode when configuring proxy ARP on RVIs. • If you set proxy ARP to unrestricted, disable gratuitous ARP requests on each interface enabled for proxy ARP. • Example: Configuring Proxy ARP on a J-EX Series Switch on page 2621 • Configuring Proxy ARP (CLI Procedure) on page 1153 Understanding MAC Notification on J-EX Series Switches J-EX Series Switches track clients on a network by storing Media Access Control (MAC) addresses in the Ethernet switching table on the switch. When switches learn or unlearn a MAC address, SNMP notifications can be sent to the network management system at regular intervals to record the addition or removal of the MAC address. This process is known as MAC notification. The MAC Notification MIB controls MAC notification for the network management system. For general information on the MAC Notification MIB, see the Junos OS Network Management Configuration Guide at http://www.juniper.net/techpubs/software/junos/index.html. The MAC notification interval defines how often these SNMP notifications are sent to the network management system. The MAC notification interval works by tracking all of the MAC address additions or removals on the switch over a period of time and then sending all of the tracked MAC address additions or removals to the network management server at the end of the interval. For instance, if the MAC notification interval is set to 10, all of the MAC address addition and removal SNMP notifications are sent to the network management system every 10 seconds. Enabling MAC notification allows users to monitor the addition and removal of MAC addresses from the Ethernet switching table remotely using a network management system. The advantage of setting a high MAC notification interval is that the amount of network traffic is reduced because updates are sent less frequently. The advantage of setting a low MAC notification interval is that the network management system is better synchronized with the switch. MAC notification is disabled by default. When MAC notification is enabled, the default MAC notification interval is 30 seconds. 1060 Chapter 57: Bridging and VLANs—Overview Related Documentation • Configuring MAC Notification (CLI Procedure) on page 1151 • Configuring SNMP (J-Web Procedure) on page 3309 1061 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1062 CHAPTER 58 Examples: Bridging and VLAN Configuration • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch J-EX Series switches use bridging and virtual LANs (VLANs) to connect network devices in a LAN—desktop computers, IP telephones, printers, file servers, wireless access points, and others—and to segment the LAN into smaller bridging domains. The switch's default configuration provides a quick setup of bridging and a single VLAN. This example describes how to configure basic bridging and VLANs for a J-EX Series switch: • Requirements on page 1063 • Overview and Topology on page 1064 • Configuration on page 1065 • Verification on page 1069 Requirements This example uses the following software and hardware components: 1063 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • One J-EX4200 Virtual Chassis switch Before you set up bridging and a VLAN, be sure you have: • Installed your J-EX Series switch. See Installing and Connecting a J-EX4200 Switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. Overview and Topology J-EX Series switches connect network devices in an office LAN or a data center LAN to provide sharing of common resources such as printers and file servers and to enable wireless devices to connect to the LAN through wireless access points. Without bridging and VLANs, all devices on the Ethernet LAN are in a single broadcast domain, and all the devices detect all the packets on the LAN. Bridging creates separate broadcast domains on the LAN, creating VLANs, which are independent logical networks that group together related devices into separate network segments. The grouping of devices on a VLAN is independent of where the devices are physically located in the LAN. To use a J-EX Series switch to connect network devices on a LAN, you must, at a minimum, configure bridging and VLANs. If you simply power on the switch and perform the initial switch configuration using the factory-default settings, bridging is enabled on all the switch's interfaces, all interfaces are in access mode, and all interfaces belong to a VLAN called default, which is automatically configured. When you plug access devices—such as desktop computers, Avaya IP telephones, file servers, printers, and wireless access points—into the switch, they are joined immediately into the default VLAN and the LAN is up and running. The topology used in this example consists of one J-EX4200-24T switch, which has a total of 24 ports. Eight of the ports support Power over Ethernet (PoE), which means they provide both network connectivity and electric power for the device connecting to the port. To these ports, you can plug in devices requiring PoE, such as Avaya VoIP telephones, wireless access points, and some IP cameras. (Avaya phones have a built-in hub that allows you to connect a desktop PC to the phone, so the desktop and phone in a single office require only one port on the switch.) The remaining 16 ports provide only network connectivity. You use them to connect devices that have their own power sources, such as desktop and laptop computers, printers, and servers. Table 1 details the topology used in this configuration example. Table 142: Components of the Basic Bridging Configuration Topology Property Settings Switch hardware J-EX4200-24T switch, with 24 Gigabit Ethernet ports: 8 PoE ports (ge-0/0/0 through ge-0/0/7) and 16 non-PoE ports (ge-0/0/8 through ge-0/0/23) VLAN name default Connection to wireless access point (requires PoE) ge-0/0/0 1064 Chapter 58: Examples: Bridging and VLAN Configuration Table 142: Components of the Basic Bridging Configuration Topology (continued) Property Settings Connections to Avaya IP telephone—with integrated hub, to connect phone and desktop PC to a single port (requires PoE) ge-0/0/1 through ge-0/0/7 Direct connections to desktop PCs (no PoE required) ge-0/0/8 through ge-0/0/12 Connections to file servers (no PoE required) ge-0/0/17 and ge-0/0/18 Connections to integrated printer/fax/copier machines (no PoE required) ge-0/0/19 through ge-0/0/20 Unused ports (for future expansion) ge-0/0/13 through ge-0/0/16, and ge-0/0/21 through ge-0/0/23 Configuration CLI Quick Configuration By default, after you perform the initial configuration on the J-EX4200 switch, switching is enabled on all interfaces, a VLAN named default is created, and all interfaces are placed into this VLAN. You do not need to perform any other configuration on the switch to set up bridging and VLANs. To use the switch, simply plug the Avaya IP phones into the PoE-enabled ports ge-0/0/1 through ge-0/0/7, and plug in the PCs, file servers, and printers to the non-PoE ports, ge-0/0/8 through ge-0/0/12 and ge-0/0/17 through ge-0/0/20. Step-by-Step Procedure To configure bridging and VLANs: Results 1. Make sure the switch is powered on. 2. Connect the wireless access point to switch port ge-0/0/0. 3. Connect the seven Avaya phones to switch ports ge-0/0/1 through ge-0/0/7. 4. Connect the five PCs to ports ge-0/0/8 through ge-0/0/12. 5. Connect the two file servers to ports ge-0/0/17 and ge-0/0/18. 6. Connect the two printers to ports ge-0/0/19 and ge-0/0/20. Check the results of the configuration: [edit] user@switch> show configuration ## Last commit: 2008-03-06 00:11:22 UTC by triumph version 9.0; system { root-authentication { encrypted-password "$1$urmA7AFM$x5SaGEUOdSI3u1K/iITGh1"; ## SECRET-DATA } syslog { user * { any emergency; 1065 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } file messages { any notice; authorization info; } file interactive-commands { interactive-commands any; } } commit { factory-settings { reset-chassis-lcd-menu; reset-virtual-chassis-configuration; } } } interfaces { ge-0/0/0 { unit 0 { family ethernet-switching; } } ge-0/0/1 { unit 0 { family ethernet-switching; } } ge-0/0/2 { unit 0 { family ethernet-switching; } } ge-0/0/3 { unit 0 { family ethernet-switching; } } ge-0/0/4 { unit 0 { family ethernet-switching; } } ge-0/0/5 { unit 0 { family ethernet-switching; } } ge-0/0/6 { unit 0 { family ethernet-switching; } } ge-0/0/7 { unit 0 { family ethernet-switching; } 1066 Chapter 58: Examples: Bridging and VLAN Configuration } ge-0/0/8 { unit 0 { family ethernet-switching; } } ge-0/0/9 { unit 0 { family ethernet-switching; } } ge-0/0/10 { unit 0 { family ethernet-switching; } } ge-0/0/11 { unit 0 { family ethernet-switching; } } ge-0/0/12 { unit 0 { family ethernet-switching; } } ge-0/0/13 { unit 0 { family ethernet-switching; } } ge-0/0/14 { unit 0 { family ethernet-switching; } } ge-0/0/15 { unit 0 { family ethernet-switching; } } ge-0/0/16 { unit 0 { family ethernet-switching; } } ge-0/0/17 { unit 0 { family ethernet-switching; } } ge-0/0/18 { unit 0 { family ethernet-switching; } } 1067 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/19 { unit 0 { family ethernet-switching; } } ge-0/0/20 { unit 0 { family ethernet-switching; } } ge-0/0/21 { unit 0 { family ethernet-switching; } } ge-0/0/22 { unit 0 { family ethernet-switching; } } ge-0/0/23 { unit 0 { family ethernet-switching; } } ge-0/1/0 { unit 0 { family ethernet-switching; } } xe-0/1/0 { unit 0 { family ethernet-switching; } } ge-0/1/1 { unit 0 { family ethernet-switching; } } xe-0/1/1 { unit 0 { family ethernet-switching; } } ge-0/1/2 { unit 0 { family ethernet-switching; } } ge-0/1/3 { unit 0 { family ethernet-switching; } } } 1068 Chapter 58: Examples: Bridging and VLAN Configuration protocols { lldp { interface all; } rstp; } poe { interface all; } Verification To verify that switching is operational and that a VLAN has been created, perform these tasks: • Verifying That the VLAN Has Been Created on page 1069 • Verifying That Interfaces Are Associated with the Proper VLANs on page 1069 Verifying That the VLAN Has Been Created Purpose Action Verify that the VLAN named default has been created on the switch. List all VLANs configured on the switch: user@switch> show vlans Name default Tag Interfaces ge-0/0/0.0*, ge-0/0/4.0, ge-0/0/8.0*, ge-0/0/12.0, ge-0/0/16.0, ge-0/0/20.0, ge-0/1/0.0*, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/9.0, ge-0/0/10.0, ge-0/0/11.0*, ge-0/0/13.0, ge-0/0/14.0, ge-0/0/15.0, ge-0/0/17.0, ge-0/0/18.0, ge-0/0/19.0*, ge-0/0/21.0, ge-0/0/22.0, ge-0/0/23.0, ge-0/1/1.0*, ge-0/1/2.0*, ge-0/1/3.0* mgmt me0.0* Meaning The show vlans command lists the VLANs configured on the switch. This output shows that the VLAN default has been created. Verifying That Interfaces Are Associated with the Proper VLANs Purpose Action Verify that Ethernet switching is enabled on switch interfaces and that all interfaces are included in the VLAN. List all interfaces on which switching is enabled: user@switch> show ethernet-switching interfaces Interface ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 State up down down down down VLAN members default default default default default Blocking unblocked blocked blocked blocked blocked - blocked blocked blocked blocked by by by by STP/RTG STP/RTG STP/RTG STP/RTG 1069 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/5.0 ge-0/0/6.0 ge-0/0/7.0 ge-0/0/8.0 ge-0/0/9.0 ge-0/0/10.0 ge-0/0/11.0 ge-0/0/12.0 ge-0/0/13.0 ge-0/0/14.0 ge-0/0/15.0 ge-0/0/16.0 ge-0/0/17.0 ge-0/0/18.0 ge-0/0/19.0 ge-0/0/20.0 ge-0/0/21.0 ge-0/0/22.0 ge-0/0/23.0 ge-0/1/0.0 ge-0/1/1.0 ge-0/1/2.0 ge-0/1/3.0 me0.0 Meaning Related Documentation down down down up down down up down down down down down down down up down down down down up up up up up default default default default default default default default default default default default default default default default default default default default default default default mgmt blocked blocked blocked unblocked blocked blocked unblocked blocked blocked blocked blocked blocked blocked blocked unblocked blocked blocked blocked blocked unblocked unblocked unblocked unblocked unblocked blocked by STP/RTG blocked by STP/RTG blocked by STP/RTG blocked by STP/RTG blocked by STP/RTG blocked blocked blocked blocked blocked blocked blocked by by by by by by by STP/RTG STP/RTG STP/RTG STP/RTG STP/RTG STP/RTG STP/RTG blocked blocked blocked blocked by by by by STP/RTG STP/RTG STP/RTG STP/RTG The show ethernet-switching interfaces command lists all interfaces on which switching is enabled (in the Interfaces column), along with the VLANs that are active on the interfaces (in the VLAN members column). The output in this example shows all the connected interfaces, ge-0/0/0 through ge-0/0/12 and ge-0/0/17 through ge-0/0/20 and that they are all part of VLAN default. Notice that the interfaces listed are the logical interfaces, not the physical interfaces. For example, the output shows ge-0/0/0.0 instead of ge-0/0/0. This is because the Junos OS creates VLANs on logical interfaces, not directly on physical interfaces. • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches To segment traffic on a LAN into separate broadcast domains, you create separate virtual LANs (VLANs) on a J-EX Series switch. Each VLAN is a collection of network nodes. When you use VLANs, frames whose origin and destination are in the same VLAN are forwarded only within the local VLAN, and only frames not destined for the local VLAN are forwarded to other broadcast domains. VLANs thus limit the amount of traffic flowing across the entire LAN, reducing the possible number of collisions and packet retransmissions within the LAN. 1070 Chapter 58: Examples: Bridging and VLAN Configuration This example describes how to configure bridging for a J-EX Series switch and how to create two VLANs to segment the LAN: • Requirements on page 1071 • Overview and Topology on page 1071 • Configuration on page 1072 • Verification on page 1076 Requirements This example uses the following hardware and software components: • One J-EX4200-48T Virtual Chassis switch Before you set up bridging and VLANs, be sure you have: • Installed the J-EX Series switch. See Installing and Connecting a J-EX4200 Switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. Overview and Topology J-EX Series switches connect all devices in an office or data center into a single LAN to provide sharing of common resources such as printers and file servers and to enable wireless devices to connect to the LAN through wireless access points. The default configuration creates a single VLAN, and all traffic on the switch is part of that broadcast domain. Creating separate network segments reduces the span of the broadcast domain and allows you to group related users and network resources without being limited by physical cabling or by the location of a network device in the building or on the LAN. This example shows a simple configuration to illustrate the basic steps for creating two VLANs on a single switch. One VLAN, called sales, is for the sales and marketing group, and a second, called support, is for the customer support team. The sales and support groups each have their own dedicated file servers, printers, and wireless access points. For the switch ports to be segmented across the two VLANs, each VLAN must have its own broadcast domain, identified by a unique name and tag (VLAN ID). In addition, each VLAN must be on its own distinct IP subnet. The topology for this example consists of one J-EX4200-48T switch, which has a total of 48 Gigabit Ethernet ports, 8 which support Power over Ethernet (PoE). Some of the switch ports connect to Avaya IP telephones. Other ports connect to wireless access points, file servers, and printers. Table 143: Components of the Multiple VLAN Topology Property Settings Switch hardware J-EX4200-48T, 48 Gigabit Ethernet ports, 8 of them PoE-enabled (ge-0/0/0 through ge-0/0/07) 1071 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 143: Components of the Multiple VLAN Topology (continued) Property Settings VLAN names and tag IDs sales, tag 100 support, tag 200 VLAN subnets sales: 192.0.2.0/25 (addresses 192.0.2.1 through 192.0.2.126) support: 192.0.2.128/25 (addresses 192.0.2.129 through 192.0.2.254) Interfaces in VLAN sales Avaya IP telephones: ge-0/0/2 through ge-0/0/4 Wireless access point: ge-0/0/0 Printers: ge-0/0/22 and ge-0/0/23 File servers: ge-0/0/20 and ge-0/0/21 Interfaces in VLAN support Avaya IP telephones: ge-0/0/5 through ge-0/0/7 Wireless access point: ge-0/0/1 Printers: ge-0/0/44 and ge-0/0/45 File servers: ge-0/0/46 and ge-0/0/47 Unused interfaces ge-0/0/8 through ge0/0/19 and ge-0/0/24 through ge–0/0/43 This configuration example creates two IP subnets, one for the sales VLAN and the second for the support VLAN. The switch bridges traffic within a VLAN. For traffic passing between two VLANs, the switch routes the traffic using a Layer 3 routing interface on which you have configured the address of the IP subnet. To keep the example simple, the configuration steps show only a few devices in each of the VLANs. Use the same configuration procedure to add more LAN devices. Configuration Configure Layer 2 switching for two VLANs: CLI Quick Configuration To quickly configure Layer 2 switching for the two VLANs (sales and support) and to quickly configure Layer 3 routing of traffic between the two VLANs, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/0/0 unit 0 description “Sales wireless access point port” set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/3 unit 0 description “Sales phone port” set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/22 unit 0 description “Sales printer port” set interfaces ge-0/0/22 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/20 unit 0 description “Sales file server port” set interfaces ge-0/0/20 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/1 unit 0 description “Support wireless access point port” set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members support set interfaces ge-0/0/6 unit 0 description “Support phone port” set interfaces ge-0/0/6 unit 0 family ethernet-switching vlan members support set interfaces ge-0/0/44 unit 0 description “Support printer port” set interfaces ge-0/0/44 unit 0 family ethernet-switching vlan members support set interfaces ge-0/0/46 unit 0 description “Support file server port” set interfaces ge-0/0/46 unit 0 family ethernet-switching vlan members support 1072 Chapter 58: Examples: Bridging and VLAN Configuration set interfaces vlan unit 0 family inet address 192.0.2.0/25 set interfaces vlan unit 1 family inet address 192.0.2.128/25 set vlans sales l3–interface vlan.0 set vlans sales vlan-id 100 set vlans support vlan-id 200 set vlans support l3-interface vlan.1 Step-by-Step Procedure Configure the switch interfaces and the VLANs to which they belong. By default, all interfaces are in access mode, so you do not have to configure the port mode. 1. Configure the interface for the wireless access point in the sales VLAN: [edit interfaces ge-0/0/0 unit 0] user@switch# set description “Sales wireless access point port” user@switch# set family ethernet-switching vlan members sales 2. Configure the interface for the Avaya IP phone in the sales VLAN: [edit interfaces ge-0/0/3 unit 0] user@switch# set description “Sales phone port” user@switch# set family ethernet-switching vlan members sales 3. Configure the interface for the printer in the sales VLAN: [edit interfaces ge-0/0/22 unit 0] user@switch# set description “Sales printer port” user@switch# set family ethernet-switching vlan members sales 4. Configure the interface for the file server in the sales VLAN: [edit interfaces ge-0/0/20 unit 0] user@switch# set description “Sales file server port” user@switch# set family ethernet-switching vlan members sales 5. Configure the interface for the wireless access point in the support VLAN: [edit interfaces ge-0/0/1 unit 0] user@switch# set description “Support wireless access point port” user@switch# set family ethernet-switching vlan members support 6. Configure the interface for the Avaya IP phone in the support VLAN: [edit interfaces ge-0/0/6 unit 0] user@switch# set description “Support phone port” user@switch# set family ethernet-switching vlan members support 7. Configure the interface for the printer in the support VLAN: [edit interfaces ge-0/0/44 unit 0] user@switch# set description “Support printer port” user@switch# set family ethernet-switching vlan members support 8. Configure the interface for the file server in the support VLAN: [edit interfaces ge-0/0/46 unit 0] user@switch# set description “Support file server port” user@switch# set family ethernet-switching vlan members support 9. Create the subnet for the sales broadcast domain: [edit interfaces] user@switch# set vlan unit 0 family inet address 192.0.2.1/25 1073 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 10. Create the subnet for the support broadcast domain: [edit interfaces] user@switch# set vlan unit 1 family inet address 192.0.2.129/25 Configure the VLAN tag IDs for the sales and support VLANs: 11. [edit vlans] user@switch# set sales vlan-id 100 user@switch# set support vlan-id 200 12. To route traffic between the sales and support VLANs, define the interfaces that are members of each VLAN and associate a Layer 3 interface: [edit vlans] user@switch# set sales l3-interface user@switch# set support l3-interface vlan.1 Display the results of the configuration: user@switch> show configuration interfaces { ge-0/0/0 { unit 0 { description “Sales wireless access point port”; family ethernet-switching { vlan members sales; } } } ge-0/0/3 { unit 0 { description “Sales phone port”; family ethernet-switching { vlan members sales; } } } ge-0/0/22 { unit 0 { description “Sales printer port”; family ethernet-switching { vlan members sales; } } } ge-0/0/20 { unit 0 { description “Sales file server port”; family ethernet-switching { vlan members sales; } } } ge-0/0/1 { unit 0 { description “Support wireless access point port”; 1074 Chapter 58: Examples: Bridging and VLAN Configuration family ethernet-switching { vlan members support; } } } ge-0/0/6 { unit 0 { description “Support phone port”; family ethernet-switching { vlan members support; } } } ge-0/0/44 { unit 0 { description “Support printer port”; family ethernet-switching { vlan members support; } } } ge-0/0/46 { unit 0 { description “Support file server port”; family ethernet-switching { vlan members support; } } vlans { unit 0 { family inet address 192.0.2.0/25; } unit 1 { family inet address 192.0.2.128/25; } } } } vlans { sales { vlan-id 100; interface ge-0/0/0.0: interface ge-0/0/3/0; interface ge-0/0/20.0; interface ge-0/0/22.0; l3-interface vlan 0; } support { vlan-id 200; interface ge-0/0/1..0: interface ge-0/0/6.0; interface ge-0/0/44.0; interface ge-0/0/46.0; l3-interface vlan 1; } } 1075 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS TIP: To quickly configure the sales and support VLAN interfaces, issue the load merge terminal command, then copy the hierarchy and paste it into the switch terminal window. Verification To verify that the “sales” and “support” VLANs have been created and are operating properly, perform these tasks: • Verifying That the VLANs Have Been Created and Associated to the Correct Interfaces on page 1076 • Verifying That Traffic Is Being Routed Between the Two VLANs on page 1077 • Verifying That Traffic Is Being Switched Between the Two VLANs on page 1077 Verifying That the VLANs Have Been Created and Associated to the Correct Interfaces Purpose Action Verify that the VLANs sales and support have been created on the switch and that all connected interfaces on the switch are members of the correct VLAN. List all VLANs configured on the switch: Use the operational mode commands: user@switch> show vlans Name Tag Interfaces default ge-0/0/1.0, ge-0/0/2.0, ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/8.0, ge-0/0/9.0, ge-0/0/10.0*, ge-0/0/11.0, ge-0/0/12.0, ge-0/0/13.0*, ge-0/0/14.0, ge-0/0/15.0, ge-0/0/16.0, ge-0/0/17.0, ge-0/0/18.0, ge-0/0/19.0, ge-0/0/21.0, ge-0/0/23.0*, ge-0/0/25.0, ge-0/0/27.0, ge-0/0/28.0, ge-0/0/29.0, ge-0/0/30.0, ge-0/0/31.0, ge-0/0/32.0, ge-0/0/33.0, ge-0/0/34.0, ge-0/0/35.0, ge-0/0/36.0, ge-0/0/37.0, ge-0/0/38.0, ge-0/0/39.0, ge-0/0/40.0, ge-0/0/41.0, ge-0/0/42.0, ge-0/0/43.0, ge-0/0/45.0, ge-0/0/47.0, ge-0/1/0.0*, ge-0/1/1.0*, ge-0/1/2.0*, ge-0/1/3.0* sales 100 ge-0/0/0.0*, ge-0/0/3.0, ge-0/0/20.0, ge-0/0/22.0 support 200 ge-0/0/1.0, ge-0/0/6.0, ge-0/0/44.0, ge-0/0/46.0* mgmt me0.0* Meaning 1076 The show vlans command lists all VLANs configured on the switch and which interfaces are members of each VLAN. This command output shows that the sales and support VLANs have been created. The sales VLAN has a tag ID of 100 and is associated with interfaces ge-0/0/0.0, ge-0/0/3.0, ge-0/0/20.0, and ge-0/0/22.0. VLAN support has a Chapter 58: Examples: Bridging and VLAN Configuration tag ID of 200 and is associated with interfaces ge-0/0/1.0, ge-0/0/6.0, ge-0/0/44.0, and ge-0/0/46.0. Verifying That Traffic Is Being Routed Between the Two VLANs Purpose Action Verify routing between the two VLANs. List the Layer 3 routes in the switch's Address Resolution Protocol (ARP) table: user@switch> show arp MAC Address Address 00:00:0c:06:2c:0d 00:13:e2:50:62:e0 Meaning Name 192.0.2.3 192.0.2.11 Flags vlan.0 vlan.1 None None Sending IP packets on a multiaccess network requires mapping from an IP address to a MAC address (the physical or hardware address). The ARP table displays the mapping between the IP address and MAC address for both vlan.0 (associated with sales) and vlan.1 (associated with support). These VLANs can route traffic to each other. Verifying That Traffic Is Being Switched Between the Two VLANs Purpose Action Verify that learned entries are being added to the Ethernet switching table. List the contents of the Ethernet switching table: user@switch> show ethernet-switching table Ethernet-switching table: 8 entries, 5 learned VLAN MAC address Type default * Flood default 00:00:05:00:00:01 Learn default 00:00:5e:00:01:09 Learn default 00:19:e2:50:63:e0 Learn sales * Flood sales 00:00:5e:00:07:09 Learn support * Flood support 00:00:5e:00:01:01 Learn Meaning Related Documentation Age – – Interfaces All-members ge-0/0/10.0 ge-0/0/13.0 ge-0/0/23.0 All-members ge-0/0/0.0 All–members ge-0/0/46.0 The output shows that learned entries for the sales and support VLANs have been added to the Ethernet switching table, and are associated with interfaces ge-0/0/0.0 and ge-0/0/46.0. Even though the VLANs were associated with more than one interface in the configuration, these interfaces are the only ones that are currently operating. • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 1077 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Example: Connecting an Access Switch to a Distribution Switch In large local area networks (LANs), you commonly need to aggregate traffic from a number of access switches into a distribution switch. This example describes how to connect an access switch to a distribution switch: • Requirements on page 1078 • Overview and Topology on page 1078 • Configuring the Access Switch on page 1080 • Configuring the Distribution Switch on page 1084 • Verification on page 1086 Requirements This example uses the following hardware and software components: • For the distribution switch, one J-EX4200-24F switch. This model is designed to be used as a distribution switch for aggregation or collapsed core network topologies and in space-constrained data centers. It has twenty-four 1-Gigabit Ethernet fiber SFP ports and an uplink module with two 10-Gigabit Ethernet ports. • For the access switch, one J-EX4200-24T, which has twenty-four 1-Gigabit Ethernet ports, 8 of which support Power over Ethernet (PoE), and an uplink module with four 1-Gigabit Ethernet ports. Before you connect an access switch to a distribution switch, be sure you have: • Installed the two switches. See Installing and Connecting a J-EX4200 Switch. • Performed the initial software configuration on both switches. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. Overview and Topology In a large office that is spread across several floors or buildings, or in a data center, you commonly aggregate traffic from a number of access switches into a distribution switch. This configuration example shows a simple topology to illustrate how to connect a single access switch to a distribution switch. In the topology, the LAN is segmented into two VLANs, one for the sales department and the second for the support team. One 1-Gigabit Ethernet port on the access switch's uplink module connects to the distribution switch, to one 1-Gigabit Ethernet port on the distribution switch. Figure 28 on page 1079 shows one J-EX4200 switch that is connected to the three access switches. 1078 Chapter 58: Examples: Bridging and VLAN Configuration Figure 28: Topology for Configuration Table 144 on page 1079 explains the components of the example topology. The example shows how to configure one of the three access switches. The other access switches could be configured in the same manner. Table 144: Components of the Topology for Connecting an Access Switch to a Distribution Switch Property Settings Access switch hardware J-EX4200-24T, 24 1-Gigabit Ethernet ports, with 8 ports PoE-enabled (ge-0/0/0 through ge-0/0/7); one uplink module Distribution switch hardware J-EX4200-24F, 24 1-Gigabit Ethernet fiber SPF ports (ge-0/0/0 through ge-0/0/23); one uplink module VLAN names and tag IDs sales, tag 100 support, tag 200 VLAN subnets sales: 192.0.2.0/25 (addresses 192.0.2.1 through 192.0.2.126) support: 192.0.2.128/25 (addresses 192.0.2.129 through 192.0.2.254) Trunk port interfaces On the access switch: ge-0/1/0 On the distribution switch: ge-0/0/0 Access port interfaces in VLAN sales (on access switch) Avaya IP telephones: ge-0/0/2 through ge-0/0/4 Wireless access point: ge-0/0/0 Printers: ge-0/0/22 and ge-0/0/23 File servers: ge-0/0/20 and ge-0/0/21 1079 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 144: Components of the Topology for Connecting an Access Switch to a Distribution Switch (continued) Property Settings Access port interfaces in VLAN support (on access switch) Avaya IP telephones: ge-0/0/5 through ge-0/0/7 Wireless access point: ge-0/0/1 Printers: ge-0/0/44 and ge-0/0/45 File servers: ge-0/0/46 and ge-0/0/47 Unused interfaces on access switch ge-0/0/8 through ge-0/0/19 and ge-0/0/24 through ge-0/0/43 Configuring the Access Switch To configure the access switch: CLI Quick Configuration To quickly configure the access switch, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/0/0 unit 0 description “Sales Wireless access point port” set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/3 unit 0 description “Sales phone port” set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/22 unit 0 description “Sales printer port” set interfaces ge-0/0/22 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/20 unit 0 description “Sales file server port” set interfaces ge-0/0/20 unit 0 family ethernet-switching vlan members sales set interfaces ge-0/0/1 unit 0 description “Support wireless access point port” set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members support set interfaces ge-0/0/6 unit 0 description “Support phone port” set interfaces ge-0/0/6 unit 0 family ethernet-switching vlan members support set interfaces ge-0/0/44 unit 0 description “Support printer port” set interfaces ge-0/0/44 unit 0 family ethernet-switching vlan members support set interfaces ge-0/0/46 unit 0 description “Support file server port” set interfaces ge-0/0/46 unit 0 family ethernet-switching vlan members support set interfaces ge-0/1/0 unit 0 description “Uplink module port connection to distribution switch” set interfaces ge-0/1/0 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/1/0 unit 0 family ethernet-switching native-vlan-id 1 set interfaces ge-0/1/0 unit 0 family ethernet switching vlan members [sales support] set interfaces vlan unit 0 family inet address 192.0.2.1/25 set interfaces vlan unit 1 family inet address 192.0.2.129/25 set vlans sales interface ge-0/0/0.0 set vlans sales interface ge-0/0/3.0 set vlans sales interface ge-0/0/22.0 set vlans sales interface ge-0/0/20.0 set vlans sales l3-interface vlan.0 set vlans sales vlan-id 100 set vlans sales vlan-description “Sales VLAN” set vlans support interface ge-0/0/1.0 set vlans support interface ge-0/0/6.0 set vlans support interface ge-0/0/44.0 set vlans support interface ge-0/0/46.0 set vlans support vlan-id 200 set vlans support l3–interface vlan.1 set vlans support vlan-description “Support VLAN” 1080 Chapter 58: Examples: Bridging and VLAN Configuration Step-by-Step Procedure To configure the access switch: 1. Configure the 1-Gigabit Ethernet interface on the uplink module to be the trunk port that connects to the distribution switch: [edit interfaces ge-0/1/0 unit 0] user@access-switch# set description “Uplink module port connection to distribution switch” user@access-switch# set ethernet-switching port-mode trunk 2. Specify the VLANs to be aggregated on the trunk port: [edit interfaces ge-0/1/0 unit 0] user@access-switch# set ethernet-switching vlan members [ sales support ] 3. Configure the VLAN ID to use for packets that are received with no dot1q tag (untagged packets): [edit interfaces ge-0/1/0 unit 0] user@access-switch# set ethernet-switching native-vlan-id 1 4. Configure the sales VLAN: [edit vlans sales] user@access-switch# set vlan-description “Sales VLAN” user@access-switch# set vlan-id 100 user@access-switch# set l3-interface vlan.0 5. Configure the support VLAN: [edit vlans support] user@access-switch# set vlan-description “Support VLAN” user@access-switch# set vlan-id 200 user@access-switch# set l3-interface vlan.1 6. Create the subnet for the sales broadcast domain: [edit interfaces] user@access-switch# set vlan unit 0 family inet address 192.0.2.1/25 7. Create the subnet for the support broadcast domain: [edit interfaces] user@access-switch# set vlan unit 1 family inet address 192.0.2.129/25 8. Configure the interfaces in the sales VLAN: [edit interfaces] user@access-switch# port” user@access-switch# sales user@access-switch# user@access-switch# sales user@access-switch# user@access—switch# sales user@access-switch# user@access-switch# sales set ge-0/0/0 unit 0 description “Sales wireless access point set ge-0/0/0 unit 0 family ethernet-switching vlan members set ge-0/0/3 unit 0 description “Sales phone port” set ge-0/0/3 unit 0 family ethernet-switching vlan members set ge-0/0/20 unit 0 description “Sales file server port” set ge-0/0/20 unit 0 family ethernet-switching vlan members set ge-0/0/22 unit 0 description “Sales printer port” set ge-0/0/22 unit 0 family ethernet-switching vlan members 1081 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configure the interfaces in the support VLAN: 9. [edit interfaces] user@access-switch# port” user@access-switch# support user@access-switch# user@access-switch# support user@access-switch# user@access-switch# support user@access-switch# user@access-switch# support 10. set ge-0/0/1 unit 0 family ethernet-switching vlan members set ge-0/0/6 unit 0 description “Support phone port” set ge-0/0/6 unit 0 family ethernet-switching vlan members set ge-0/0/44 unit 0 description “Support printer port” set ge-0/0/44 unit 0 family ethernet-switching vlan members set ge-0/0/46 unit 0 description “Support file server port” set ge-0/0/46 unit 0 family ethernet-switching vlan members Configure descriptions and VLAN tag IDs for the sales and support VLANs: [edit vlans] user@access-switch# user@access-switch# user@access-switch# user@access-switch# 11. set ge-0/0/1 unit 0 description “Support wireless access point set sales vlan-description “Sales VLAN” set sales vlan-id 100 set support vlan-description “Support VLAN” set support vlan-id 200 To route traffic between the sales and support VLANs and associate a Layer 3 interface with each VLAN: [edit vlans] user@access-switch# set sales l3-interface vlan.0 user@access-switch# set support l3-interface vlan.1 Results Display the results of the configuration: user@access-switch> show interfaces { ge-0/0/0 { unit 0 { description “Sales wireless access point port”; family ethernet-switching { vlan members sales; } } } ge-0/0/3 { unit 0 { description “Sales phone port”; family ethernet-switching { vlan members sales; } } } ge-0/0/20 { unit 0 { description “Sales file server port”; family ethernet-switching { vlan members sales; } 1082 Chapter 58: Examples: Bridging and VLAN Configuration } } ge-0/0/22 { unit 0 { description “Sales printer port”; family ethernet-switching { vlan members sales; } } } ge-0/0/1 { unit 0 { description “Support wireless access point port”; family ethernet-switching { vlan members support; } } } ge-0/0/6 { unit 0 { description “Support phone port”; family ethernet-switching { vlan members support; } } } ge-0/0/44 { unit 0 { description “Support printer port”; family ethernet-switching { vlan members sales; } } } ge-0/0/46 { unit 0 { description “Support file server port”; family ethernet-switching { vlan members support; } } } ge-0/1/0 { unit 0 { description “Uplink module port connection to distribution switch”; family ethernet-switching { port-mode trunk; vlan members [ sales support ]; native-vlan-id 1; } } } vlan { unit 0 { family inet address 192.0.2.1/25; } 1083 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit 1 { family inet address 192.0.2.129/25; } } } vlans { sales { vlan-id 100; vlan-description “Sales VLAN”; l3-interface vlan.0; } support { vlan-id 200; vlan-description “Support VLAN”; l3-interface vlan.1; } } TIP: To quickly configure the distribution switch, issue the load merge terminal command, then copy the hierarchy and paste it into the switch terminal window. Configuring the Distribution Switch To configure the distribution switch: CLI Quick Configuration To quickly configure the distribution switch, copy the following commands and paste them into the switch terminal window: set interfaces ge-0/0/0 description “Connection to access switch” set interfaces ge-0/0/0 ethernet-switching port-mode trunk set interfaces ge-0/0/0 ethernet-switching vlan members [ sales support ] set interfaces ge-0/0/0 ethernet-switching native-vlan-id 1 set interfaces vlan unit 0 family inet address 192.0.2.2/25 set interfaces vlan unit 1 family inet address 192.0.2.130/25 set vlans sales vlan-description “Sales VLAN” set vlans sales vlan-id 100 set vlans sales l3-interface vlan.0 set vlans support vlan-description “Support VLAN” set vlans support vlan-id 200 set vlans support l3-interface vlan.1 Step-by-Step Procedure To configure the distribution switch: 1. Configure the interface on the switch to be the trunk port that connects to the access switch: [edit interfaces ge-0/0/0 unit 0] user@distribution-switch# set description “Connection to access switch” user@distribution-switch# set ethernet-switching port-mode trunk 2. Specify the VLANs to be aggregated on the trunk port: [edit interfaces ge-0/0/0 unit 0] user@distribution-switch# set ethernet-switching vlan members [ sales support ] 1084 Chapter 58: Examples: Bridging and VLAN Configuration 3. Configure the VLAN ID to use for packets that are received with no dot1q tag (untagged packets): [edit interfaces] user@distribution-switch# set ge-0/0/0 ethernet-switching native-vlan-id 1 4. Configure the sales VLAN: [edit vlans sales] user@distribution-switch# set vlan-description “Sales VLAN” user@distribution-switch# set vlan-id 100 user@distribution-switch# set l3-interface vlan.0 5. Configure the support VLAN: [edit vlans support] user@distribution-switch# set vlan-description “Support VLAN” user@distribution-switch# set vlan-id 200 user@distribution-switch# set l3-interface vlan.1 6. Create the subnet for the sales broadcast domain: [edit interfaces] user@distribution-switch# set vlan unit 0 family inet address 192.0.2.2/25 7. Create the subnet for the support broadcast domain: [edit interfaces] user@distribution-switch# set vlan unit 1 family inet address 192.0.2.130/25 Results Display the results of the configuration: user@distribution-switch> show interfaces { ge-0/0/0 { description “Connection to access switch”; unit 0 { family ethernet-switching { port-mode trunk; vlan members [ sales support ]; native-vlan-id 1; } } } vlan { unit 0 { family inet address 192.0.2.2/25; } unit 1 { family inet address 192.0.2.130/25; } } } vlans { sales { vlan-id 100; vlan-description “Sales VLAN”; l3-interface vlan.0; } 1085 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS support { vlan-id 200; vlan-description “Support VLAN”; l3-interface vlan.1; } } TIP: To quickly configure the distribution switch, issue the load merge terminal command, then copy the hierarchy and paste it into the switch terminal window. Verification To confirm that the configuration is working properly, perform these tasks: • Verifying the VLAN Members and Interfaces on the Access Switch on page 1086 • Verifying the VLAN Members and Interfaces on the Distribution Switch on page 1087 Verifying the VLAN Members and Interfaces on the Access Switch Purpose Action Verify that the sales and support have been created on the switch. List all VLANs configured on the switch: user@switch> show vlans Name default Tag Interfaces ge-0/0/1.0, ge-0/0/2.0, ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/8.0*, ge-0/0/9.0, ge-0/0/10.0, ge-0/0/14.0, ge-0/0/18.0, ge-0/0/25.0, ge-0/0/30.0, ge-0/0/34.0, ge-0/0/38.0, ge-0/0/42.0, ge-0/1/1.0*, sales ge-0/0/11.0*, ge-0/0/12.0, ge-0/0/13.0, ge-0/0/15.0, ge-0/0/16.0, ge-0/0/17.0, ge-0/0/19.0*,ge-0/0/21.0, ge-0/0/23.0, ge-0/0/27.0*,ge-0/0/28.0, ge-0/0/29.0, ge-0/0/31.0*,ge-0/0/32.0, ge-0/0/33.0, ge-0/0/35.0*,ge-0/0/36.0, ge-0/0/37.0, ge-0/0/39.0*,ge-0/0/40.0, ge-0/0/41.0, ge-0/0/43.0*,ge-0/0/45.0, ge-0/0/47.0, ge-0/1/2.0*, ge-0/1/3.0* 100 ge-0/0/0.0*, ge-0/0/3.0, ge-0/0/20.0, ge-0/0/22.0, ge-0/1/0.0*, support 200 ge-0/0/1.0*, ge-0/0/6.0, ge-0/0/44.0, ge-0/0/46.0, mgmt me0.0* Meaning 1086 The output shows the sales and support VLANs and the interfaces associated with them. Chapter 58: Examples: Bridging and VLAN Configuration Verifying the VLAN Members and Interfaces on the Distribution Switch Purpose Action Verify that the sales and support have been created on the switch. List all VLANs configured on the switch: user@switch> show vlans Name default Tag Interfaces ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0, ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0*, ge-0/0/8.0, ge-0/0/9.0, ge-0/0/10.0*, ge-0/0/11.0, ge-0/0/12.0, ge-0/0/13.0, ge-0/0/14.0, ge-0/0/15.0, ge-0/0/16.0, ge-0/0/17.0, ge-0/0/18.0*, ge-0/0/19.0, ge-0/0/20.0, ge-0/0/21.0, ge-0/0/22.0*, ge-0/0/23.0, ge-0/1/1.0*, ge-0/1/2.0*, ge-0/1/3.0* sales 100 ge-0/0/0.0* support 200 ge-0/0/0.0* mgmt me0.0* Meaning Related Documentation The output shows the sales and support VLANs associated to interface ge-0/0/0.0. Interface ge-0/0/0.0 is the trunk interface connected to the access switch. • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Example: Configure Automatic VLAN Administration Using GVRP As a network expands and the number of clients and VLANs increases, VLAN administration becomes complex, and the task of efficiently configuring VLANs on multiple J-EX Series switches becomes increasingly difficult. To automate VLAN administration, you can enable GARP VLAN Registration Protocol (GVRP) on the network. NOTE: Only trunk interfaces can be enabled for GVRP. 1087 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to use GVRP to automate administration of VLAN membership changes within your network: • Requirements on page 1088 • Overview and Topology on page 1088 • Configuring VLANs and GVRP on Access Switch A on page 1090 • Configuring VLANs and GVRP on Access Switch B on page 1093 • Configuring VLANS and GVRP on the Distribution Switch on page 1096 • Verification on page 1099 Requirements This example uses the following hardware and software components: • Two J-EX4200 access switches • One J-EX4200 distribution switch Before you configure GVRP on the access switches and on the distribution switch, be sure you have: • Performed the initial software configuration on the switches. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. • Configured the VLANs on both the access switches and on the distribution switch. (Dynamic VLAN configuration is not supported.) • Configured a trunk interface on all the switches. Overview and Topology When you are setting up your network, you should configure all VLANs on all switches, even though some switches are not actively participating in a VLAN. Then enable GVRP on the trunk interface of each switch. GVRP ensures that the VLAN membership information on the trunk interface is updated as the switch’s access interfaces become active or inactive in the configured VLANs. You do not need to take an extra step of explicitly binding a VLAN to the trunk interface. When GVRP is enabled, the trunk interface advertises all the VLANs that are active (bound to access interfaces) on that switch. A GVRP-enabled trunk interface does not advertise VLANs that have been configured on the switch but that are not currently bound to an access interface. Thus, GVRP provides the benefit of reducing network overhead—by limiting the scope of broadcast, unknown unicast, and multicast (BUM) traffic to interested devices only. This example shows a network with three VLANs: finance, sales, and lab. Access Switch A has been configured to support all three VLANS and all three VLANS are active, bound to interfaces that are connected to personal computers: 1088 • ge-0/0/1—Connects PC1 as member of finance vlan, VLAN ID 100 • ge-0/0/2—Connects PC2 as member of lab vlan, VLAN ID 200 Chapter 58: Examples: Bridging and VLAN Configuration • ge-0/0/3—Connects PC3 as member of sales vlan, VLAN ID 300 Access Switch B has also been configured to support three VLANS. However, currently only two VLANs are active, bound to interfaces that are connected to personal computers: • ge-0/0/0—Connects PC4 as member of finance vlan, VLAN ID 100 • ge-0/0/1—Connects PC5 as member of lab vlan, VLAN ID 200 The Distribution Switch is also configured to support the three VLANs (finance, lab, sales). However, the Distribution Switch does not have any access interfaces that are connecting devices as members of these VLANs. The Distribution Switch has two trunk interfaces: • xe-0/1/1—Connects Distribution Switch to Access Switch A. • xe-0/1/0—Connects Distribution Switch to Access Switch B. Figure 29 on page 1089 shows GVRP configured on two access switches and one distribution switch. Figure 29: GVRP Configured on Two Access Switches and One Distribution Switch for Automatic VLAN Administration 1089 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 145: Components of the Network Topology Property Settings Switch hardware • Access Switch A • Access Switch B • Distribution Switch VLAN names and tag IDs finance, tag 100 lab, tag 200 sales, tag 300 Interfaces Access Switch A Interfaces • ge-0/0/1—Connects PC1 to Access Switch A. • ge-0/0/2—Connects PC2 to Access Switch A. • ge-0/0/3—Connects PC3 to Access Switch A. • xe-0/1/1—Connects Access Switch A to Distribution Switch. (trunk) Access Switch B Interfaces • ge-0/0/0—Connects PC4 to Access Switch B. • ge-0/0/1—Connects PC5 to Access Switch B. • xe-0/1/0—Connects Access Switch B to Distribution Switch. (trunk) Distribution Switch Interfaces • xe-0/1/1—Connects Distribution Switch to Access Switch A. (trunk) • xe-0/1/0—Connects Distribution Switch to Access Switch B. (trunk) When VLAN access interfaces become active or inactive, GVRP ensures that the updated information is advertised on the trunk interface. Thus, the Distribution Switch does not forward traffic to inactive VLANs. Configuring VLANs and GVRP on Access Switch A To configure three VLANs on the switch, bind access interfaces for PC1, PC2, and PC3 to the VLANs (finance, lab, sales), and enable GVRP on the trunk interface of Access Switch A, perform these tasks: CLI Quick Configuration To quickly configure Access Switch A to support the three VLANs, bind interfaces for the three PCs to the appropriate VLANs, and enable GVRP on the trunk interface, copy the following commands and paste them into the switch terminal window of Switch A: [edit] set vlans finance vlan-id 100 set vlans lab vlan-id 200 set vlans sales vlan-id 300 set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members finance set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members lab set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members sales set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk 1090 Chapter 58: Examples: Bridging and VLAN Configuration set protocols gvrp interface xe-0/1/1.0 NOTE: As we recommend, default GVRP timers are used in this example. The default values associated with each GVRP timer are: 200 ms for the join timer, 600 ms for the leave timer, and 1000 cs (10000 ms) for the leaveall timer. Modifying timers to inappropriate values may cause an imbalance in the operation of GVRP. Refer to IEEE 802.1D [2004] Clause 12 for more information. The timer values are displayed when you use the show gvrp command to verify that GVRP is enabled. For more information on the timers, see gvrp and its associated configuration statements. Step-by-Step Procedure To configure Access Switch A to support the three VLANs, bind interfaces for the three PCs to the appropriate VLANs, and enable GVRP on the trunk interface, copy the following commands and paste them into the switch terminal window of Switch A: 1. Configure the finance VLAN: [edit] user@Access-Switch-A# set vlans finance vlan-id 100 2. Configure the lab VLAN: [edit] user@Access-Switch-A# set vlans lab vlan–id 200 3. Configure the sales VLAN: [edit] user@Access-Switch-A# set vlans sales vlan–id 300 4. Configure an Ethernet interface as a member of the finance VLAN: [edit] does user@Access-Switch-A# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members finance 5. Configure an Ethernet interface as a member of the lab VLAN: [edit] user@Access-Switch-A# set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members lab 6. Configure an Ethernet interface as a member of the sales VLAN: [edit] user@Access-Switch-A# set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members sales 7. Configure a trunk interface: user@Access-Switch-A# set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk 8. Enable GVRP on the trunk interface: [edit] user@Access-Switch-A# set protocols gvrp interface xe-0/1/1.0 1091 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Results Check the results of the configuration: interfaces { ge-0/0/0 { unit 0 { family ethernet-switching; } } ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members finance; } } } } ge-0/0/2 { unit 0 { family ethernet-switching { vlan { members lab; } } } } ge-0/0/3 { unit 0 { family ethernet-switching { vlan { members sales; } } } } xe-0/1/1 { unit 0 { family ethernet-switching { port-mode trunk; } } } ge-0/1/2 { unit 0 { family ethernet-switching; } } ge-0/1/3 { unit 0 { family ethernet-switching; } } } protocols { igmp-snooping { vlan all; 1092 Chapter 58: Examples: Bridging and VLAN Configuration } lldp { interface all; } lldp-med { interface all; } gvrp { interface xe-0/1/1.0; } rstp; } ethernet-switching-options { storm-control { interface all { level 50; } } } vlans { finance { vlan-id 100; } lab { vlan-id 200; } sales { vlan-id 300; } Configuring VLANs and GVRP on Access Switch B To configure three VLANs on the switch, bind access interfaces for PC4 and PC5 to the VLANs (finance and lab), and enable GVRP on the trunk interface of Access Switch Switch B, perform these tasks: CLI Quick Configuration To quickly configure Access Switch B to support the three VLANs, bind interfaces for the two PCs to the appropriate VLANs, and enable GVRP on the trunk interface, copy the following commands and paste them into the switch terminal window of Switch B: [edit] set vlans finance vlan-id 100 set vlans lab vlan-id 200 set vlans sales vlan-id 300 set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members finance set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members lab set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk set protocols gvrp interface xe-0/1/0.0 1093 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure Access Switch B to support the three VLANs, bind interfaces for the two PCs to the appropriate VLAN, and enable GVRP on the trunk interface, copy the following commands and paste them into the switch terminal window of Switch B: 1. Configure the finance VLAN: [edit] user@Access-Switch-B# set vlans finance vlan-id 100 2. Configure the lab VLAN: [edit] user@Access-Switch-B# set vlans lab vlan–id 200 3. Configure the sales VLAN: [edit] user@Access-Switch-B# set vlans sales vlan–id 300 4. Configure an Ethernet interface as a member of the finance VLAN: [edit] user@Access-Switch-B# set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members finance 5. Configure an Ethernet interface as a member of the lab VLAN: [edit] user@Access-Switch-B# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members lab 6. Configure a trunk interface: user@Access-Switch-B# set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk 7. Enable GVRP on the trunk interface: [edit] user@Access-Switch-B# set protocols gvrp xe-0/1/0.0 NOTE: As we recommend, default GVRP timers are used in this example. The default values associated with each GVRP timer are: 200 ms for the join timer, 600 ms for the leave timer, and 1000 cs (10000 ms) for the leaveall timer. Modifying timers to inappropriate values might cause an imbalance in the operation of GVRP. Refer to IEEE 802.1D [2004] Clause 12 for more information. The timer values are displayed when you use the show gvrp command to verify that GVRP is enabled. For more information on the timers, see gvrp and its associated configuration statements. Results Check the results of the configuration: [edit] user@Access-Switch-B #show interfaces { 1094 Chapter 58: Examples: Bridging and VLAN Configuration ge-0/0/0 { unit 0 { family ethernet-switching { vlan { members finance; } } } } ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members lab; } } } } ge-0/0/2 { unit 0 { family ethernet-switching; } } ge-0/0/3 { unit 0 { family ethernet-switching; } } ge-0/1/0 { unit 0 { family ethernet-switching; } } xe-0/1/0 { unit 0 { family ethernet-switching { port-mode trunk; } } } ge-0/1/1 { unit 0 { family ethernet-switching; } } xe-0/1/1 { unit 0 { family ethernet-switching; } } ge-0/1/2 { unit 0 { family ethernet-switching; } } ge-0/1/3 { 1095 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit 0 { family ethernet-switching; } } } protocols { igmp-snooping { vlan all; } lldp { interface all; } lldp-med { interface all; } gvrp { interface xe-0/1/0.0; } rstp; } ethernet-switching-options { storm-control { interface all { level 50; } } } vlans { finance { vlan-id 100; } lab { vlan-id 200; } sales { vlan-id 300; } } Configuring VLANS and GVRP on the Distribution Switch CLI Quick Configuration To quickly configure the finance, lab, and sales VLANs on the Distribution Switch and to enable GVRP on the trunk interface of the Distribution Switch, copy the following commands and paste them into the switch terminal window of the Distribution Switch: [edit] set vlans finance vlan-id 100 set vlans lab vlan-id 200 set vlans sales vlan-id 300 set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk set protocols gvrp interface xe-0/1/1.0 set protocols gvrp interface xe-0/1/0.0 1096 Chapter 58: Examples: Bridging and VLAN Configuration Step-by-Step Procedure To configure the three VLANs on the Distribution Switch, to configure the trunk interfaces, and to enable GVRP on the trunk interface of the Distribution Switch: 1. Configure the finance VLAN: [edit] user@Distribution-Switch# set vlans finance vlan–id 100 2. Configure the lab VLAN: [edit] user@Distribution-Switch# set vlans lab vlan–id 200 3. Configure the sales VLAN: [edit] user@Distribution-Switch# set vlans sales vlan–id 300 4. Configure the trunk interface to Access Switch A: [edit] user@Distribution-Switch# set interfaces xe-0/1/1 unit 0 familyethernet-switching port-mode trunk 5. Configure the trunk interface to Access Switch B: [edit] user@Distribution-Switch# set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk 6. Enable GVRP on the trunk interface for xe-0/1/1 : [edit] user@Distribution-Switch# set protocols gvrp interface xe-0/1/1.0 7. Enable GVRP on the trunk interface for xe-0/1/0 : [edit] user@Distribution-Switch# set protocols gvrp interface xe-0/1/0.0 Results Display the results of the configuration: [edit] user@Distribution Switch-D #show interfaces { ge-0/0/0 { unit 0 { family ethernet-switching; } } ge-0/0/1 { unit 0 { family ethernet-switching; } } ge-0/0/2 { unit 0 { family ethernet-switching; } } 1097 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/3 { unit 0 { family ethernet-switching; } } xe-0/1/0 { unit 0 { family ethernet-switching { port-mode trunk; } } } ge-0/1/1 { unit 0 { family ethernet-switching; } } xe-0/1/1 { unit 0 { family ethernet-switching { port-mode trunk; } } } ge-0/1/2 { unit 0 { family ethernet-switching; } } ge-0/1/3 { unit 0 { family ethernet-switching; } } } protocols { igmp-snooping { vlan all; } lldp { interface all; } lldp-med { interface all; } gvrp { interface xe-0/1/0.0; interface xe-0/1/1.0; } rstp; } ethernet-switching-options { storm-control { interface all { level 50; } 1098 Chapter 58: Examples: Bridging and VLAN Configuration } } vlans { finance { vlan-id 100; } lab { vlan-id 300; } sales { vlan-id 300; } } Verification To confirm that the configuration is updating VLAN membership, perform these tasks: • Verifying That GVRP Is Enabled on Access Switch A on page 1099 • Verifying That GVRP Is Updating VLAN Membership on Switch A on page 1099 • Verifying That GVRP Is Enabled on Access Switch B on page 1100 • Verifying That GVRP Is Updating VLAN Membership on Switch B on page 1100 • Verifying That GVRP Is Enabled on the Distribution Switch on page 1100 • Verifying That GVRP Is Updating VLAN Membership on the Distribution Switch on page 1101 Verifying That GVRP Is Enabled on Access Switch A Purpose Action Verify that GVRP is enabled on the switch. Show the GVRP configuration, using the show gvrp command: user@Access-Switch-A> show gvrp Global GVRP configuration GVRP status : Enabled GVRP Timers (ms) Join : 200 Leave : 600 LeaveAll : 10000 Interface Name Protocol Status ---------------------------xe-0/1/1.0 Enabled Meaning The results show that GVRP is enabled on the trunk interface of Switch A and that the default timers are used. Verifying That GVRP Is Updating VLAN Membership on Switch A Purpose To verify that GVRP is updating VLAN membership, display the Ethernet switching interfaces and associated VLANs that are active on switch A: 1099 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Action List Ethernet switching interfaces on the switch, using the show ethernet-switching interfaces command: user@Access-Switch-A> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/1.0 up finance unblocked ge-0/0/2.0 up lab unblocked ge-0/0/3.0 up sales unblocked xe-0/1/1.0 up finance unblocked lab unblocked Meaning GVRP has automatically added finance and lab as VLAN members on the trunk interface, because they are being advertised by Access Switch B. Verifying That GVRP Is Enabled on Access Switch B Purpose Action Verify that GVRP is enabled on the switch. Show the GVRP configuration: user@Access-Switch-B> show gvrp Global GVRP configuration GVRP status : Enabled GVRP Timers (ms) Join : 200 Leave : 600 LeaveAll : 10000 Interface Name Protocol Status ---------------------------xe-0/1/0.0 Enabled Meaning The results show that GVRP is enabled on the trunk interface of Switch B and that the default timers are used. Verifying That GVRP Is Updating VLAN Membership on Switch B Purpose Action To verify that GVRP is updating VLAN membership, display the Ethernet switching interfaces and associated VLANs that are active on switch B: List Ethernet switching interfaces on the switch: user@Access-Switch-B> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/0.0 up finance unblocked ge-0/0/1.0 up lab unblocked xe-0/1/1.0 up finance unblocked lab unblocked sales unblocked Meaning GVRP has automatically added finance, lab, and sales as VLAN members on the trunk interface because they are being advertised by Access Switch A. Verifying That GVRP Is Enabled on the Distribution Switch Purpose 1100 Verify that GVRP is enabled on the switch. Chapter 58: Examples: Bridging and VLAN Configuration Action Show the GVRP configuration: user@Distribution-Switch> show gvrp Global GVRP configuration GVRP status : Enabled GVRP Timers (ms) Join : 200 Leave : 600 LeaveAll : 10000 Interface Name Protocol Status ---------------------------xe-0/1/0.0 Enabled xe-0/1/1.0 Enabled Verifying That GVRP Is Updating VLAN Membership on the Distribution Switch Purpose Action To verify that GVRP is updating VLAN membership on the distribution switch, display the Ethernet switching interfaces and associated VLANs on the Distribution Switch: List the Ethernet switching interfaces on the switch: user@Distribution-Switch> show ethernet-switching interfaces Interface State VLAN members Blocking xe-0/1/1.0 up finance unblocked lab unblocked sales unblocked xe-0/1/0.0 up finance unblocked lab unblocked Meaning Related Documentation The Distribution Switch has two trunk interfaces. Interface xe-0/1/1.0 connects the Distribution Switch to Access Switch A and is therefore updated to show that it is a member of all the VLANs that are active on Access Switch A. Any traffic for those VLANs will be passed on from the Distribution Switch to Access Switch A, through interface xe-0/1/1.0. Interface xe-0/1/0.0 connects the Distribution Switch to Access Switch B and is updated to show that it is a member of the two VLANs that are active on Access Switch B. Thus, the Distribution Switch sends traffic for finance and lab to both Access Switch A and Access Switch B. But the Distribution Switch sends traffic for sales only to Access Switch A. • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Example: Configuring Redundant Trunk Links for Faster Recovery Simplify the convergence configuration in a typical enterprise network by configuring a primary link and a secondary link on trunk ports. If the primary link fails, the secondary link automatically takes over without waiting for normal STP convergence. This example describes how to create a redundant trunk group: • Requirements on page 1102 • Overview and Topology on page 1102 1101 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuration on page 1103 • Verification on page 1104 Requirements This example uses the following hardware and software components: • Two J-EX4200 distribution switches • One J-EX4200 access switch Before you configure the redundant trunk links network on the access and distribution switches, be sure you have: • Installed the access switch. See Installing and Connecting a J-EX4200 Switch. • Installed the two distribution switches. See Installing and Connecting a J-EX4200 Switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. Overview and Topology This example shows a simple configuration to illustrate the basic steps for creating a redundant trunk group. Configuring redundant trunk links places the primary link and the secondary link in a redundant group. However, a primary link need not be configured. If a primary link is not specified, the software compares the two links and selects the link with the highest port number as the active link. For example, if the two interfaces are ge-0/1/0 and ge-0/1/1, the software assigns ge-0/1/1 as the active link.. Whether a primary link is specified as the active link, or whether it is calculated by the software, traffic is handled in the same manner. Traffic passes through the active link but is blocked on the secondary link. If the active link goes down or is disabled administratively, the secondary link becomes active and begins forwarding traffic. However, there is a difference between the behavior of a primary, active link and an active link that is calculated to be active by the software. If an active link goes down, the secondary link begins forwarding traffic. If the old, active link comes up again, the following occurs: • If the old, active link was configured as the primary link, then it resumes the role of active link and the other link is blocked. An interface configured as primary continues to carry with it the primary role whenever it becomes active. • If no primary link was configured, and the active link was calculated by the software when the redundant group was formed, then the old, active link will not preempt the other interface (new active). NOTE: The Junos OS for J-EX Series switches does not allow an interface to be in a redundant trunk group and in an STP topology at the same time. 1102 Chapter 58: Examples: Bridging and VLAN Configuration Figure 30 on page 1103 displays an example topology containing three switches. Switch 1 and Switch 2 make up the distribution layer, and Switch 3 makes up the access layer. Switch 3 is connected to the distribution layer through trunk ports ge-0/0/9.0 (Link 1) and ge-0/0/10.0 (Link 2). Table 146 on page 1103 lists the components used in this redundant trunk group. Figure 30: Topology for Configuring the Redundant Trunk Links Table 146: Components of the Redundant Trunk Link Topology Property Settings Switch hardware • Switch 1–1 J-EX4200 distribution switch • Switch 2–1 J-EX4200 distribution switch • Switch 3–1 J-EX4200 access switch Trunk port interfaces On Switch 3 (access switch): ge-0/0/9.0 and ge-0/0/10.0 Redundant trunk group group1 This configuration example creates a redundant trunk group called group1 on Switch 3. The trunk ports ge-0/0/9.0 and ge-0/0/10.0 are the two links in group1. The trunk port ge-0/0/9.0 will be configured administratively as the primary link. The trunk port ge-0/0/10.0 will be the secondary link. Configuration CLI Quick Configuration To quickly configure the redundant trunk group group1 on Switch 3, copy the following commands and paste them into the switch terminal window: 1103 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit] set ethernet-switching-options redundant-trunk-group group-name group1 set ethernet-switching-options redundant-trunk-group group-name group1 interface ge-0/0/9.0 primary set ethernet-switching-options redundant-trunk-group group-name group1 interface ge-0/0/10.0 Step-by-Step Procedure Configure the redundant trunk group group1 on Switch 3 and specify the primary and secondary links. 1. Configure the redundant trunk group group1: [edit ethernet-switching-options] user@switch# set redundant-trunk-group group-name group1 2. Configure the trunk port ge-0/0/9.0 as the primary link and ge-0/0/10 as the secondary link: [edit ethernet-switching-options] user@switch# set redundant-trunk-group group-name group1 interface ge-0/0/9.0 primary user@switch# set redundant-trunk-group group-name group1 interface ge-0/0/10.0 Results Display the results of the configuration: user@switch# show ethernet-switching-options { redundant-trunk-group { group-name group1 { interface ge-0/0/9.0 primary; interface ge-0/0/10.0; } } } } Verification Verify that the redundant trunk group group1 has been created and is operating properly: • Verifying That the Redundant Group Has Been Created on page 1104 Verifying That the Redundant Group Has Been Created Purpose Action Verify that the redundant trunk group group1 has been created on the switch and that trunk ports are members of the redundant trunk group. List all redundant trunk groups configured on the switch: user@switch> show redundant-trunk-group group1 Redundant-trunk-group: group1 Interfaces : ge-0/0/9.0 (P) , DOWN : ge-0/0/10.0 (A) , UP Bandwidth : 1000 Mbps, 1000 Mbps Last Time of Flap : 1970-01-01 00:19:12 UTC (00:00:06 ago), Never #Flaps : 1, 0 1104 Chapter 58: Examples: Bridging and VLAN Configuration Meaning Related Documentation The show redundant-trunk-group command lists all redundant trunk groups configured on the switch and which trunk links are members of the group. For this configuration example, the output shows that the redundant trunk group group1 is configured on the switch. The (P) beside trunk port ge-0/0/9.0 indicates that it is configured as the primary link. The (A) beside the ge-0/0/10.0 trunk port indicates that it is the active link. • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches Service providers can use Q-in-Q tunneling to transparently pass Layer 2 VLAN traffic from a customer site, through the service provider network, to another customer site without removing or changing the customer VLAN tags or class-of-service (CoS) settings. You can configure Q-in-Q tunneling on J-EX Series switches. This example describes how to set up Q-in-Q: • Requirements on page 1105 • Overview and Topology on page 1105 • Configuration on page 1106 • Verification on page 1107 Requirements This example requires one J-EX Series switch. Before you begin setting up Q-in-Q tunneling, make sure you have created and configured the necessary customer VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. Overview and Topology In this service provider network, there are multiple customer VLANs mapped to one service VLAN. Table 147 on page 1105 lists the settings for the example topology. Table 147: Components of the Topology for Setting Up Q-in-Q Tunneling Interface Description ge-0/0/11.0 Tagged S-VLAN trunk port ge-0/0/12.0 Untagged customer-facing access port ge-0/0/13.0 Untagged customer-facing access port ge-0/0/14.0 Tagged S-VLAN trunk port 1105 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuration CLI Quick Configuration To quickly create and configure Q-in-Q tunneling, copy the following commands and paste them into the switch terminal window: [edit] set vlans qinqvlan vlan-id 4001 set vlans qinqvlan dot1q-tunneling customer-vlans 1-100 set vlans qinqvlan dot1q-tunneling customer-vlans 201-300 set interfaces ge-0/0/11 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/11 unit 0 family ethernet-switching vlan members 4001 set interfaces ge-0/0/12 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/12 unit 0 family ethernet-switching vlan members 4001 set interfaces ge-0/0/13 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/13 unit 0 family ethernet-switching vlan members 4001 set interfaces ge-0/0/14 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/14 unit 0 family ethernet-switching vlan members 4001 set ethernet-switching-options dot1q-tunneling ether-type 0x9100 Step-by-Step Procedure To configure Q-in-Q tunneling: 1. Set the VLAN ID for the S-VLAN: [edit vlans] user@switch# set qinqvlan vlan-id 4001 2. Enable Q-in-Q tuennling and specify the customer VLAN ranges: [edit vlans] user@switch# set qinqvlan dot1q-tunneling customer-vlans 1-100 user@switch# set qinqvlan dot1q-tunneling customer-vlans 201-300 3. Set the port mode and VLAN information for the interfaces: [edit interfaces] user@switch# set ge-0/0/11 unit 0 family ethernet-switching port-mode trunk user@switch# set ge-0/0/11 unit 0 family ethernet-switching vlan members 4001 user@switch# set ge-0/0/12 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/12 unit 0 family ethernet-switching vlan members 4001 user@switch# set ge-0/0/13 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/13 unit 0 family ethernet-switching vlan members 4001 user@switch# set ge-0/0/14 unit 0 family ethernet-switching port-mode trunk user@switch# set ge-0/0/14 unit 0 family ethernet-switching vlan members 4001 4. Set the Q-in-Q Ethertype value: [edit] user@switch# set ethernet-switching-options dot1q-tunneling ether-type 0x9100 Results Check the results of the configuration: user@switch> show configuration vlans qinqvlan vlan-id 4001; dot1q-tunneling { customer-vlans [ 1-100 201-300 ]; } 1106 Chapter 58: Examples: Bridging and VLAN Configuration Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That Q-in-Q Tunneling Was Enabled on page 1107 Verifying That Q-in-Q Tunneling Was Enabled Purpose Action Verify that Q-in-Q tunneling was properly enabled on the switch. Use the show vlans command: user@switch> show vlans qinqvlan extensive VLAN: qinqvlan, Created at: Thu Sep 18 07:17:53 2008 802.1Q Tag: 4001, Internal index: 18, Admin State: Enabled, Origin: Static Dot1q Tunneling Status: Enabled Customer VLAN ranges: 1-100 201-300 Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 4 (Active = 0) ge-0/0/11.0, tagged, trunk ge-0/0/14.0, tagged, trunk ge-0/0/12.0, untagged, access ge-0/0/13.0, untagged, access Meaning Related Documentation The output indicates that Q-in-Q tunneling is enabled and that the VLAN is tagged and shows the associated customer VLANs. • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 Example: Configuring a Private VLAN on a J-EX Series Switch For security reasons, it is often useful to restrict the flow of broadcast and unknown unicast traffic and to even limit the communication between known hosts. The private VLAN (PVLAN) feature on J-EX Series switches allow an administrator to split a broadcast domain into multiple isolated broadcast subdomains, essentially putting a VLAN inside a VLAN. This example describes how to create a private VLAN primary VLAN and secondary VLANs: NOTE: Configuring a voice over IP (VoIP) VLAN on PVLAN interfaces is not supported. • Requirements on page 1108 • Overview and Topology on page 1108 • Configuration on page 1108 • Verification on page 1110 1107 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example requires one J-EX Series switch. Before you begin configuring a private VLAN, make sure you have created and configured the necessary VLAN. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. Overview and Topology In a large office with multiple buildings and VLANs, you might need to isolate some workgroups or other endpoints for security reasons or to partition the broadcast domain. This configuration example shows a simple topology to illustrate how to create a private VLAN with one primary VLAN and two community VLANs, one for HR and one for finance, as well as two isolated ports for the mail server and the backup server. Table 148 on page 1108 lists the settings for the example topology. Table 148: Components of the Topology for Configuring a Private VLAN Interface Description ge-0/0/0.0 Primary VLAN (pvlan) trunk interface ge-0/0/11.0 User 1, HR Community (hr-comm) ge-0/0/12.0 User 2, HR Community (hr-comm) ge-0/0/13.0 User 3, Finance Community (finance-comm) ge-0/0/14.0 User 4, Finance Community (finance-comm) ge-0/0/15.0 Mail server, Isolated (isolated) ge-0/0/16.0 Backup server, Isolated (isolated) ge-1/0/0.0 Primary VLAN ( pvlan) trunk interface Configuration CLI Quick Configuration To quickly create and configure a private VLAN, copy the following commands and paste them into the switch terminal window: [edit] set vlans pvlan vlan-id 1000 set interfaces ge-0/0/0 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members pvlan set interfaces ge-1/0/0 unit 0 family ethernet-switching port-mode trunk set interfaces ge-1/0/0 unit 0 family ethernet-switching vlan members pvlan set interfaces ge-0/0/11 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/12 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/13 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/14 unit 0 family ethernet-switching port-mode access 1108 Chapter 58: Examples: Bridging and VLAN Configuration set interfaces ge-0/0/15 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/16 unit 0 family ethernet-switching port-mode access set vlans pvlan no-local-switching set vlans pvlan interface ge-0/0/0.0 set vlans pvlan interface ge-1/0/0.0 set vlans hr-comm interface ge-0/0/11.0 set vlans hr-comm interface ge-0/0/12.0 set vlans finance-comm interface ge-0/0/13.0 set vlans finance-comm interface ge-0/0/14.0 set vlans hr-comm primary-vlan pvlan set vlans finance-comm primary-vlan pvlan Step-by-Step Procedure To configure the private VLAN: 1. Set the VLAN ID for the primary VLAN: [edit vlans] user@switch# set pvlan vlan-id 1000 2. Set the interfaces and port modes: [edit interfaces] user@switch# set ge-0/0/0 unit 0 family ethernet-switching port-mode trunk user@switch# set ge-0/0/0 unit 0 family ethernet-switching vlan members pvlan user@switch# set ge-1/0/0 unit 0 family ethernet-switching port-mode trunk user@switch# set ge-1/0/0 unit 0 family ethernet-switching vlan members pvlan user@switch# set ge-0/0/11 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/12 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/13 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/14 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/15 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/16 unit 0 family ethernet-switching port-mode access 3. Set the primary VLAN to have no local switching: NOTE: The primary VLAN must be a tagged VLAN. [edit vlans] user@switch# set pvlan no-local-switching 4. Add the trunk interfaces to the primary VLAN: [edit vlans] user@switch# set pvlan interface ge-0/0/0.0 user@switch# set pvlan interface ge-1/0/0.0 5. For each secondary VLAN, configure access interfaces: NOTE: The secondary VLANs must be untagged VLANs. 1109 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit vlans] user@switch# set hr-comm interface ge-0/0/11.0 user@switch# set hr-comm interface ge-0/0/12.0 user@switch# set finance-comm interface ge-0/0/13.0 user@switch# set finance-comm interface ge-0/0/14.0 6. For each community VLAN, set the primary VLAN: [edit vlans] user@switch# set hr-comm primary-vlan pvlan user@switch# set finance-comm primary-vlan pvlan 7. Add each isolated interface to the primary VLAN: [edit vlans] user@switch# set pvlan interface ge-0/0/15.0 user@switch# set pvlan interface ge-0/0/16.0 Results Check the results of the configuration: user@switch> show configuration vlans finance-comm { interface { ge-0/0/13.0; ge-0/0/14.0; } primary-vlan pvlan; } hr-comm { interface { ge-0/0/11.0; ge-0/0/12.0; } primary-vlan pvlan; } pvlan { vlan-id 1000; interface { ge-0/0/15.0; ge-0/0/16.0; ge-0/0/0.0; ge-1/0/0.0; } no-local-switching; } Verification To confirm that the configuration is working properly, perform these tasks: • 1110 Verifying the Private VLAN and Secondary VLANs Were Created on page 1111 Chapter 58: Examples: Bridging and VLAN Configuration Verifying the Private VLAN and Secondary VLANs Were Created Purpose Action Verify that the primary VLAN and secondary VLANs were properly created on the switch. Use the show vlans command: user@switch> show vlans pvlan extensive VLAN: pvlan, Created at: Tue Sep 16 17:59:47 2008 802.1Q Tag: 1000, Internal index: 18, Admin State: Enabled, Origin: Static Private VLAN Mode: Primary Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 6 (Active = 0) ge-0/0/0.0, tagged, trunk ge-0/0/11.0, untagged, access ge-0/0/12.0, untagged, access ge-0/0/13.0, untagged, access ge-0/0/14.0, untagged, access ge-0/0/15.0, untagged, access ge-0/0/16.0, untagged, access ge-1/0/0.0, tagged, trunk Secondary VLANs: Isolated 2, Community 2 Isolated VLANs : __pvlan_pvlan_ge-0/0/15.0__ __pvlan_pvlan_ge-0/0/16.0__ Community VLANs : finance-comm hr-comm user@switch> show vlans hr-comm extensive VLAN: hr-comm, Created at: Tue Sep 16 17:59:47 2008 Internal index: 22, Admin State: Enabled, Origin: Static Private VLAN Mode: Community, Primary VLAN: pvlan Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 2 (Active = 0) ge-0/0/0.0, tagged, trunk ge-0/0/11.0, untagged, access ge-0/0/12.0, untagged, access ge-1/0/0.0, tagged, trunk user@switch> show vlans finance-comm extensive VLAN: finance-comm, Created at: Tue Sep 16 17:59:47 2008 Internal index: 21, Admin State: Enabled, Origin: Static Private VLAN Mode: Community, Primary VLAN: pvlan Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 2 (Active = 0) ge-0/0/0.0, tagged, trunk ge-0/0/13.0, untagged, access ge-0/0/14.0, untagged, access ge-1/0/0.0, tagged, trunk user@switch> show vlans __pvlan_pvlan_ge-0/0/15.0__ extensive VLAN: __pvlan_pvlan_ge-0/0/15.0__, Created at: Tue Sep 16 17:59:47 2008 Internal index: 19, Admin State: Enabled, Origin: Static Private VLAN Mode: Isolated, Primary VLAN: pvlan Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 1 (Active = 0) ge-0/0/0.0, tagged, trunk ge-0/0/15.0, untagged, access ge-1/0/0.0, tagged, trunk user@switch> show vlans __pvlan_pvlan_ge-0/0/16.0__ extensive 1111 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS VLAN: __pvlan_pvlan_ge-0/0/16.0__, Created at: Tue Sep 16 17:59:47 2008 Internal index: 20, Admin State: Enabled, Origin: Static Private VLAN Mode: Isolated, Primary VLAN: pvlan Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 1 (Active = 0) ge-0/0/0.0, tagged, trunk ge-0/0/16.0, untagged, access ge-1/0/0.0, tagged, trunk Meaning Related Documentation The output shows that the primary VLAN was created and identifies the interfaces and secondary VLANs associated with it. • Creating a Private VLAN (CLI Procedure) on page 1143 Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches Virtual routing instances allow each J-EX Series switch to have multiple routing tables on a device. With virtual routing instances, you can segment your network to isolate traffic without setting up additional devices. This example describes how to create virtual routing instances: • Requirements on page 1112 • Overview and Topology on page 1112 • Configuration on page 1113 • Verification on page 1114 Requirements This example uses the following hardware and software components: • One J-EX Series switch Before you create the virtual routing instances, make sure you have: • Configured the necessary VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. Overview and Topology In a large office, you may need multiple VLANs to properly manage your traffic. This configuration example shows a simple topology to illustrate how to connect a single J-EX Series switch with a virtual routing instance for each of two VLANs, enabling traffic to pass between those VLANs. In the example topology, the LAN is segmented into two VLANs, each associated with an interface and a routing instance on the J-EX Series switch. 1112 Chapter 58: Examples: Bridging and VLAN Configuration Configuration CLI Quick Configuration To quickly create and configure virtual routing instances, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/0/3 vlan-tagging set interfaces ge-0/0/3 unit 0 vlan-id 1030 family inet address 103.1.1.1/24 set interfaces ge-0/0/3 unit 1 vlan-id 1031 family inet address 103.1.1.1/24 set routing-instances r1 instance-type virtual-router set routing-instances r1 interface ge-0/0/1.0 set routing-instances r1 interface ge-0/0/3.0 set routing-instances r2 instance-type virtual-router set routing-instances r2 interface ge-0/0/2.0 set routing-instances r2 interface ge-0/0/3.1 Step-by-Step Procedure To configure virtual routing instances: 1. Create a VLAN-tagged interface: [edit] user@switch# set interfaces ge-0/0/3 vlan-tagging 2. Create two subinterfaces, on the interface, one for each routing instance: [edit] user@switch# set interfaces ge-0/0/3 unit 0 vlan-id 1030 family inet address 103.1.1.1/24 user@switch# set interfaces ge-0/0/3 unit 1 vlan-id 1031 family inet address 103.1.1.1/24 3. Create two virtual routers: [edit] user@switch# set routing-instances r1 instance-type virtual-router user@switch# set routing-instances r2 instance-type virtual-router 4. Set the interfaces for the virtual routers: [edit] user@switch# set routing-instances r1 interface ge-0/0/1.0 user@switch# set routing-instances r1 interface ge-0/0/3.0 user@switch# set routing-instances r2 interface ge-0/0/2.0 user@switch# set routing-instances r2 interface ge-0/0/3.1 Results Check the results of the configuration: user@switch> show configuration interfaces { ge-0/0/1 { unit 0 { family ethernet-switching; } } ge-0/0/2 { unit 0 { family ethernet-switching; } 1113 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } ge-0/0/3 { vlan-tagging; unit 0 { vlan-id 1030; family inet { address 103.1.1.1/24; } } unit 1 { vlan-id 1031; family inet { address 103.1.1.1/24; } } } routing-instances { r1 { instance-type virtual-router; interface ge-0/0/1.0; interface ge-0/0/3.0; } r2 { instance-type virtual-router; interface ge-0/0/2.0; interface ge-0/0/3.1; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That the Routing Instances Were Created on page 1114 Verifying That the Routing Instances Were Created Purpose Action Verify that the virtual routing instances were properly created on the switch. Use the show route instance command: user@switch> show route instance Instance Type Primary RIB master forwarding inet.0 r1 r2 1/0/0 virtual-router r2.inet.0 1114 3/0/0 virtual-router r1.inet.0 Meaning Active/holddown/hidden 1/0/0 Each routing instance created is displayed, along with its type, information about whether it is active or not, and its primary routing table. Chapter 58: Examples: Bridging and VLAN Configuration Related Documentation • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches As a network expands and the number of clients and VLANs increases, VLAN administration becomes complex and the task of efficiently configuring VLANs on multiple J-EX Series switches becomes increasingly difficult. To automate VLAN administration, you can enable Multiple VLAN Registration Protocol (MVRP) on the network. MVRP can also be used to dynamically create VLANs, further simplifying the network overhead required to statically configure VLANs. NOTE: Only trunk interfaces can be enabled for MVRP. This example describes how to use MVRP to automate administration of VLAN membership changes within your network and how to use MVRP to dynamically create VLANs: • Requirements on page 1115 • Overview and Topology on page 1115 • Configuring VLANs and MVRP on Access Switch A on page 1118 • Configuring VLANs and MVRP on Access Switch B on page 1120 • Configuring VLANS and MVRP on Distribution Switch C on page 1122 • Verification on page 1123 Requirements This example uses the following hardware and software components: • Two J-EX Series access switches • One J-EX Series distribution switch Overview and Topology MVRP is used to manage dynamic VLAN registration in a LAN. It can also be used to dynamically create VLANs. This example uses MVRP to dynamically create VLANs on the switching network. You can disable dynamic VLAN creation and create VLANs statically, if desired. Enabling MVRP on the trunk interface of each switch in your switching network ensures that the active VLAN information for the switches in the network is propagated to each switch through the trunk interfaces, assuming dynamic VLAN creation is enabled for MVRP. MVRP ensures that the VLAN membership information on the trunk interface is updated as the switch’s access interfaces become active or inactive in the configured VLANs in a static or dynamic VLAN creation setup. 1115 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS You do not need to explicitly bind a VLAN to the trunk interface. When MVRP is enabled, the trunk interface advertises all the VLANs that are active (bound to access interfaces) on that switch. An MVRP-enabled trunk interface does not advertise VLANs that have been configured on the switch but that are not currently bound to an access interface. Thus, MVRP provides the benefit of reducing network overhead—by limiting the scope of broadcast, unknown unicast, and multicast (BUM) traffic to interested devices only. When VLAN access interfaces become active or inactive, MVRP ensures that the updated information is advertised on the trunk interface. Thus, in this example, distribution Switch C does not forward traffic to inactive VLANs. This example shows a network with three VLANs: finance, sales, and lab. Access Switch A has been configured to support all three VLANS and all three VLANS are active, bound to interfaces that are connected to personal computers: • ge-0/0/1—Connects PC1 as a member of finance, VLAN ID 100 • ge-0/0/2—Connects PC2 as a member of lab, VLAN ID 200 • ge-0/0/3—Connects PC3 as a member of sales, VLAN ID 300 Access Switch B has also been configured to support three VLANS. However, currently only two VLANs are active, bound to interfaces that are connected to personal computers: • ge-0/0/0—Connects PC4 as a member of finance, VLAN ID 100 • ge-0/0/1—Connects PC5 as a member of lab, VLAN ID 200 Distribution Switch C learns the VLANs dynamically using MVRP through the connection to the access switches. Distribution Switch C has two trunk interfaces: • xe-0/1/1—Connects the switch to access Switch A. • xe-0/1/0—Connects the switch to access Switch B. Figure 31 on page 1117 shows MVRP configured on two access switches and one distribution switch. 1116 Chapter 58: Examples: Bridging and VLAN Configuration Figure 31: MVRP Configured on Two Access Switches and One Distribution Switch for Automatic VLAN Administration Table 149 on page 1117 explains the components of the example topology. Table 149: Components of the Network Topology Property Settings Switch hardware • Access Switch A • Access Switch B • Distribution Switch C VLAN names and tag IDs finance, tag 100 lab, tag 200 sales, tag 300 1117 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 149: Components of the Network Topology (continued) Property Settings Interfaces Access Switch A interfaces: • ge-0/0/1—Connects PC1 to access Switch A. • ge-0/0/2—Connects PC2 to access Switch A. • ge-0/0/3—Connects PC3 to access Switch A. • xe-0/1/1—Connects access Switch A to distribution Switch C (trunk). Access Switch B interfaces: • ge-0/0/0—Connects PC4 to access Switch B. • ge-0/0/1—Connects PC5 to access Switch B. • xe-0/1/0—Connects access Switch B to distribution Switch C. (trunk) Distribution Switch C interfaces: • xe-0/1/1—Connects distribution Switch C to access Switch A. (trunk) • xe-0/1/0—Connects distribution Switch C to access Switch B. (trunk) Configuring VLANs and MVRP on Access Switch A To configure VLANs on the switch, bind access interfaces to the VLANs, and enable MVRP on the trunk interface of access Switch A, perform these tasks: CLI Quick Configuration To quickly configure access Switch A for MVRP, copy the following commands and paste them into the switch terminal window of Switch A: [edit] set vlans finance vlan-id 100 set vlans lab vlan-id 200 set vlans sales vlan-id 300 set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members finance set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members lab set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members sales set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk set protocols mvrp interface xe-0/1/1.0 NOTE: As we recommend as a best practice, default MVRP timers are used in this example. The default values associated with each MVRP timer are: 200 ms for the join timer, 1000 ms for the leave timer, and 10000 ms for the leaveall timer. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. 1118 Chapter 58: Examples: Bridging and VLAN Configuration Step-by-Step Procedure To configure access Switch A for MVRP: 1. Configure the finance VLAN: [edit] user@Access-Switch-A# set vlans finance vlan-id 100 2. Configure the lab VLAN: [edit] user@Access-Switch-A# set vlans lab vlan–id 200 3. Configure the sales VLAN: [edit] user@Access-Switch-A# set vlans sales vlan–id 300 4. Configure an Ethernet interface as a member of the finance VLAN: [edit] user@Access-Switch-A# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members finance 5. Configure an Ethernet interface as a member of the lab VLAN: [edit] user@Access-Switch-A# set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members lab 6. Configure an Ethernet interface as a member of the sales VLAN: [edit] user@Access-Switch-A# set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members sales 7. Configure a trunk interface: [edit] user@Access-Switch-A# set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk 8. Enable MVRP on the trunk interface: [edit] user@Access-Switch-A# set protocols mvrp interface xe-0/1/1.0 Results Check the results of the configuration: [edit] user@switch# show interfaces { ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members finance; } } } } ge-0/0/2 { 1119 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit 0 { family ethernet-switching { vlan { members lab; } } } } ge-0/0/3 { unit 0 { family ethernet-switching { vlan { members sales; } } } } xe-0/1/1 { unit 0 { family ethernet-switching { port-mode trunk; } } } } protocols { mvrp { interface xe-0/1/1.0; } } vlans { finance { vlan-id 100; } lab { vlan-id 200; } sales { vlan-id 300; } } Configuring VLANs and MVRP on Access Switch B To configure three VLANs on the switch, bind access interfaces for PC4 and PC5 to the VLANs, and enable MVRP on the trunk interface of access Switch B, perform these tasks: CLI Quick Configuration To quickly configure Access Switch B for MVRP, copy the following commands and paste them into the switch terminal window of Switch B: [edit] set vlans finance vlan-id 100 set vlans lab vlan-id 200 set vlans sales vlan-id 300 set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members finance 1120 Chapter 58: Examples: Bridging and VLAN Configuration set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members lab set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk set protocols mvrp interface xe-0/1/0.0 Step-by-Step Procedure To configure access Switch B for MVRP: 1. Configure the finance VLAN: [edit] user@Access-Switch-B# set vlans finance vlan-id 100 2. Configure the lab VLAN: [edit] user@Access-Switch-B# set vlans lab vlan–id 200 3. Configure the sales VLAN: [edit] user@Access-Switch-B# set vlans sales vlan–id 300 4. Configure an Ethernet interface as a member of the finance VLAN: [edit] user@Access-Switch-B# set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members finance 5. Configure an Ethernet interface as a member of the lab VLAN: [edit] user@Access-Switch-B# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members lab 6. Configure a trunk interface: user@Access-Switch-B# set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk 7. Enable MVRP on the trunk interface: [edit] user@Access-Switch-B# set protocols mvrp xe-0/1/0.0 NOTE: As we recommend as a best practice, default MVRP timers are used in this example. The default values associated with each MVRP timer are: 200 ms for the join timer, 1000 ms for the leave timer, and 10000 ms for the leaveall timer. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. Results Check the results of the configuration: [edit] user@Access-Switch-B# show interfaces { ge-0/0/0 { unit 0 { family ethernet-switching { vlan { 1121 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS members finance; } } } } ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members lab; } } } } xe-0/1/0 { unit 0 { family ethernet-switching { port-mode trunk; } } } } } protocols { mvrp { interface xe-0/1/0.0; } } vlans { finance { vlan-id 100; } lab { vlan-id 200; } sales { vlan-id 300; } } Configuring VLANS and MVRP on Distribution Switch C CLI Quick Configuration To quickly configure distribution Switch C for MVRP, copy the following commands and paste them into the switch terminal window of distribution Switch C: [edit] set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk set protocols mvrp interface xe-0/1/1.0 set protocols mvrp interface xe-0/1/0.0 1122 Chapter 58: Examples: Bridging and VLAN Configuration Step-by-Step Procedure To configure distribution Switch C for MVRP: 1. Configure the trunk interface to access Switch A: [edit] user@Distribution-Switch-C# set interfaces xe-0/1/1 unit 0 family ethernet-switching port-mode trunk 2. Configure the trunk interface to access Switch B: [edit] user@Distribution-Switch-C# set interfaces xe-0/1/0 unit 0 family ethernet-switching port-mode trunk 3. Enable MVRP on the trunk interface for xe-0/1/1 : [edit] user@Distribution-Switch-C# set protocols mvrp interface xe-0/1/1.0 4. Enable MVRP on the trunk interface for xe-0/1/0 : [edit] user@Distribution-Switch-C# set protocols mvrp interface xe-0/1/0.0 Results Check the results of the configuration: [edit] user@Distribution Switch-D# show interfaces { xe-0/1/0 { unit 0 { family ethernet-switching { port-mode trunk; } } } xe-0/1/1 { unit 0 { family ethernet-switching { port-mode trunk; } } } } protocols { mvrp { interface xe-0/1/0.0; interface xe-0/1/1.0; } Verification To confirm that the configuration is updating VLAN membership, perform these tasks: • Verifying That MVRP Is Enabled on Access Switch A on page 1124 • Verifying That MVRP Is Updating VLAN Membership on Access Switch A on page 1124 • Verifying That MVRP Is Enabled on Access Switch B on page 1124 1123 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Verifying That MVRP Is Updating VLAN Membership on Access Switch B on page 1125 • Verifying That MVRP Is Enabled on Distribution Switch C on page 1125 • Verifying That MVRP Is Updating VLAN Membership on Distribution Switch C on page 1126 Verifying That MVRP Is Enabled on Access Switch A Purpose Action Verify that MVRP is enabled on the switch. Show the MVRP configuration: user@Access-Switch-A> show mvrp MVRP configuration MVRP status : Enabled MVRP dynamic VLAN creation : Enabled MVRP timers (ms): Interface -------------all xe-0/1/1.0 Interface -------------all xe-0/1/1.0 Meaning Join ----200 200 Leave -------1000 1000 Status -------Disabled Enabled LeaveAll ----------10000 10000 Registration Mode ----------------Normal Normal The results show that MVRP is enabled on the trunk interface of Switch A and that the default timers are used. Verifying That MVRP Is Updating VLAN Membership on Access Switch A Purpose Action Verify that MVRP is updating VLAN membership by displaying the Ethernet switching interfaces and associated VLANs that are active on Switch A. List Ethernet switching interfaces on the switch: user@Access-Switch-A> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/1.0 up finance unblocked ge-0/0/2.0 up lab unblocked ge-0/0/3.0 up sales unblocked xe-0/1/1.0 up finance unblocked lab unblocked Meaning MVRP has automatically added finance and lab as VLAN members on the trunk interface because they are being advertised by access Switch B. Verifying That MVRP Is Enabled on Access Switch B Purpose Action Verify that MVRP is enabled on the switch. Show the MVRP configuration: user@Access-Switch-B> show mvrp MVRP configuration 1124 Chapter 58: Examples: Bridging and VLAN Configuration MVRP status MVRP dynamic VLAN creation MVRP timers (ms): Interface Join -----------------all 200 xe-0/1/0.0 200 Interface -------------all xe-0/1/0.0 Meaning : Enabled : Enabled Leave -------1000 1000 Status -------Disabled Enabled LeaveAll ----------10000 10000 Registration Mode ----------------Normal Normal The results show that MVRP is enabled on the trunk interface of Switch B and that the default timers are used. Verifying That MVRP Is Updating VLAN Membership on Access Switch B Purpose Action Verify that MVRP is updating VLAN membership by displaying the Ethernet switching interfaces and associated VLANs that are active on Switch B. List Ethernet switching interfaces on the switch: user@Access-Switch-B> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/0.0 up finance unblocked ge-0/0/1.0 up lab unblocked xe-0/1/1.0 up finance unblocked lab unblocked sales unblocked Meaning MVRP has automatically added finance, lab, and sales as VLAN members on the trunk interface because they are being advertised by access Switch A. Verifying That MVRP Is Enabled on Distribution Switch C Purpose Action Verify that MVRP is enabled on the switch. Show the MVRP configuration: user@Distribution-Switch-C> show mvrp MVRP configuration MVRP status MVRP dynamic VLAN creation : Enabled : Enabled MVRP timers (ms): Interface -------------all xe-0/0/1.0 xe-0/1/1.0 Leave -------1000 1000 1000 Interface -------------all Join ----200 200 200 Status -------Disabled LeaveAll ----------10000 10000 10000 Registration Mode ----------------Normal 1125 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS xe-0/0/1.0 xe-0/1/1.0 Enabled Enabled Normal Normal Verifying That MVRP Is Updating VLAN Membership on Distribution Switch C Purpose Action Verify that MVRP is updating VLAN membership on distribution Switch C by displaying the Ethernet switching interfaces and associated VLANs on distribution Switch C. List the Ethernet switching interfaces on the switch: user@Distribution-Switch-C> show ethernet-switching interfaces Interface State VLAN members Blocking xe-0/1/1.0 up __mvrp_100__ unblocked __mvrp_200__ unblocked __mvrp_300__ unblocked xe-0/1/0.0 up __mvrp_100__ unblocked __mvrp_200__ unblocked List the VLANs that were created dynamically using MVRP on the switch: user@Distribution-Switch-C> show mvrp dynamic-vlan-memberships VLAN Name Interfaces ---------------------------------__mvrp_100__ xe-0/1/1.0 xe-0/1/0.0 __mvrp_200__ xe-0/1/1.0 xe-0/1/0.0 __mvrp_300__ xe-0/1/1.0 Meaning Distribution Switch C has two trunk interfaces. Interface xe-0/1/1.0 connects distribution Switch C to Access Switch A and is therefore updated to show that it is a member of all the VLANs that are active on Switch A. Any traffic for those VLANs will be passed on from distribution Switch C to Switch A, through interface xe-0/1/1.0. Interface xe-0/1/0.0 connects distribution Switch C to Switch B and is updated to show that it is a member of the two VLANs that are active on Switch B. Thus, distribution Switch C sends traffic for finance and lab to both Switch A and Switch B. But distribution Switch C sends traffic for sales only to Switch A. Distribution Switch C also has three dynamic VLANs created using MVRP: mvrp_100, mvrp_200, and mvrp_300. The dynamically created VLANs mvrp_100 and mvrp_200 are active on interfaces xe-0/1/1.0 and xe-0/1/1.0, and dynamically created VLAN mvrp_300 is active on interface xe-0/1/1.0. Related Documentation • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches Layer 2 protocol tunneling (L2PT) allows you to send Layer 2 protocol data units (PDUs) across a service provider network and deliver them to J-EX Series switches that are not part of the local broadcast domain. This feature is useful when you want to run Layer 2 1126 Chapter 58: Examples: Bridging and VLAN Configuration protocols on a network that includes switches located at remote sites that are connected across a service provider network. This example describes how to configure L2PT: • Requirements on page 1127 • Overview and Topology on page 1127 • Configuration on page 1129 • Verification on page 1130 Requirements This example uses the following hardware and software components: • Six J-EX Series switches, with three each at two customer sites, with one of the switches at each site designated as the provider edge (PE) device Overview and Topology L2PT allows you to send Layer 2 PDUs across a service provider network and deliver them to J-EX Series switches that are not part of the local broadcast domain. Figure 32 on page 1128 shows a customer network that includes two sites that are connected across a service provider network. Site 1 contains three switches connected in a Layer 2 network, with Switch A designated as a provider edge (PE) device in the service provider network. Site 2 contains a Layer 2 network with a similar topology to that of Site 1, with Switch D designated as a PE device. 1127 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 32: L2PT Topology When you enable L2PT on a VLAN, Q-in-Q tunneling is also (and must be) enabled. Q-in-Q tunneling ensures that Switches A, B, C, D, E, and F are part of the same broadcast domain. This example uses STP as the Layer 2 protocol being tunneled, but you could substitute any of the supported protocols for STP. You can also use the all keyword to enable L2PT for all supported Layer 2 protocols. Tunneled Layer 2 PDUs do not normally arrive at high rate. If the tunneled Layer 2 PDUs do arrive at high rate, there might be a problem in the network. Typically, you would want to shut down the interface that is receiving a high rate of tunneled Layer 2 PDUs so that problem can be isolated. However, if you do not want to completely shut down the interface, you can configure the switch to drop tunneled Layer 2 PDUs that exceed a certain threshold. 1128 Chapter 58: Examples: Bridging and VLAN Configuration The drop-theshold configuration statement allows you to specify the maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the interfaces in a specified VLAN before the switch begins dropping the Layer 2 PDUs. The drop threshold must be less than or equal to the shutdown threshold. If the drop threshold is greater than the shutdown threshold and you try to commit the configuration, the commit will fail. The shutdown-threshold configuration statement allows you to specify the maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the interfaces in a specified VLAN before the specified interface is disabled. The shutdown threshold must be greater than or equal to the drop threshold. You can specify a drop threshold without specifying a shutdown threshold, and you can specify a shutdown threshold without specifying a drop threshold. If you do not specify these thresholds, then no thresholds are enforced. As a result, the switch tunnels all Layer 2 PDUs regardless of the speed at which they are received, although the number of packets tunneled per second might be limited by other factors. In this example, we will configure both a drop threshold and a shutdown threshold to show how this is done. If L2PT-encapsulated packets are received on an access interface, the switch reacts as it does when there is a loop between the service provider network and the customer network and shuts down (disables) the access interface. Once an interface is disabled, you must explicitly reenable it using the clear ethernet-switching layer2-protocol-tunneling error command or else the interface will remain disabled. Configuration To configure L2PT, perform these tasks: CLI Quick Configuration To quickly configure L2PT, copy the following commands and paste them into the switch terminal window of each PE device (in Figure 32 on page 1128, Switch A and Switch D are the PE devices): [edit] set vlans customer-1 dot1q-tunneling set vlans customer-1 dot1q-tunneling layer2-protocol-tunneling stp set vlans customer-1 dot1q-tunneling layer2-protocol-tunneling stp drop-threshold 50 set vlans customer-1 dot1q-tunneling layer2-protocol-tunneling stp shutdown-threshold 100 Step-by-Step Procedure To configure L2PT, perform these tasks on each PE device (in Figure 32 on page 1128, Switch A and Switch D are the PE devices): 1. Enable Q-in-Q tunneling on VLAN customer-1: [edit] user@switch# set vlans customer-1 dot1q-tunneling 2. Enable L2PT for STP on VLAN customer-1: [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2-protocol-tunneling stp 3. Configure the drop threshold as 50: 1129 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2–protocol-tunneling stp drop-threshold 50 4. Configure the shutdown threshold as 100: [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2–protocol-tunneling stp shutdown-threshold 100 Results Check the results of the configuration: [edit] user@switch# show vlans customer-1 dot1q-tunneling layer2-protocol-tunneling { stp { drop-threshold 50; shutdown-threshold 100; } } Verification To verify that L2PT is working correctly, perform this task: • Verify That L2PT Is Working Correctly on page 1130 Verify That L2PT Is Working Correctly Purpose Action Verify that Q-in-Q tunneling and L2PT are enabled. Check to see that Q-in-Q tunneling and L2PT are enabled on each PE device (Switch A and Switch D are the PE devices): user@switchA> show vlans extensive customer-1 VLAN: customer–1, Created at: Thu Jun 25 05:07:38 2009 802.1Q Tag: 100, Internal index: 4, Admin State: Enabled, Origin: Static Dot1q Tunneling status: Enabled Layer2 Protocol Tunneling status: Enabled Protocol: Port Mode, Mac aging time: 300 seconds Number of interfaces: Tagged 0 (Active = 0), Untagged 3 (Active = 0) ge-0/0/7.0, untagged, access ge-0/0/8.0, untagged, access ge-0/0/9.0, untagged, access Check to see that L2PT is tunneling STP on VLAN customer-1 and that drop-threshold and shutdown-threshold have been configured: user@switchA> show ethernet-switching layer2-protocol-tunneling vlan customer-1 Layer2 Protocol Tunneling VLAN information: VLAN Protocol Drop Shutdown Threshold Threshold customer–1 stp 50 100 Check the state of the interfaces on which L2PT has been enabled, including what kind of operation (encapsulation or decapsulation) they are performing: 1130 Chapter 58: Examples: Bridging and VLAN Configuration user@switchA> show ethernet-switching layer2-protocol-tunneling interface Layer2 Protocol Tunneling information: Interface Operation State ge-0/0/0.0 Encapsulation Shutdown ge-0/0/1.0 Decapsulation Shutdown ge-0/0/2.0 Decapsulation Active Meaning Related Documentation Description Shutdown threshold exceeded Loop detected The show vlans extensive customer-1 command shows that Q-in-Q tunneling and L2PT have been enabled. The show ethernet-switching layer2-protocol-tunneling vlan customer-1 command shows that L2PT is tunneling the STP protocol on VLAN customer-1, the drop threshold is set to 50, and the shutdown threshold is set to 100. The show ethernet-switching layer2-protocol-tunneling interface command shows the type of operation being performed on each interface, the state of each interface and, if the state is Shutdown, the reason why the interface is shut down. • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 1131 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1132 CHAPTER 59 Configuring Bridging and VLANs • Configuring VLANs for J-EX Series Switches (J-Web Procedure) on page 1133 • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Configuring MAC Table Aging (CLI Procedure) on page 1138 • Configuring the Native VLAN Identifier (CLI Procedure) on page 1139 • Creating a Series of Tagged VLANs (CLI Procedure) on page 1140 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 • Creating a Private VLAN (CLI Procedure) on page 1143 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 • Configuring GVRP (J-Web Procedure) on page 1144 • Configuring Redundant Trunk Groups (J-Web Procedure) on page 1146 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 • Configuring MAC Notification (CLI Procedure) on page 1151 • Configuring Proxy ARP (CLI Procedure) on page 1153 Configuring VLANs for J-EX Series Switches (J-Web Procedure) You can use the VLAN Configuration page to add a new VLAN or to edit or delete an existing VLAN on a J-EX Series switch. To access the VLAN Configuration page: 1. Select Configure > Switching > VLAN. The VLAN Configuration page displays a list of existing VLANs. If you select a specific VLAN, the specific VLAN details are displayed in the Details section. 1133 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334s for details about all commit options. 2. Click one: • Add—creates a VLAN. • Edit—edits an existing VLAN configuration. • Delete—deletes an existing VLAN. NOTE: If you delete a VLAN, the VLAN configuration for all the associated interfaces is also deleted. When you are adding or editing a VLAN, enter information as described in Table 150 on page 1134. Table 150: VLAN Configuration Details Field Function Your Action VLAN Name Specifies a unique name for the VLAN. Enter a name. VLAN Id/Range Specifies the identifier or range for the VLAN. Select one: General tab • VLAN ID—Type a unique identification number from 1 through 4094. If no value is specified, it defaults to 0. • VLAN Range—Type a number range to create VLANs with IDs corresponding to the range. For example, the range 2–3 will create two VLANs with the IDs 2 and 3. Description Describes the VLAN. Enter a brief description for the VLAN. MAC-Table-Aging-Time Specifies the maximum time that an entry can remain in the forwarding table before it 'ages out'. Type the number of seconds from 60 through 1000000. Input filter Specifies the VLAN firewall filter that is applied to incoming packets. To apply an input firewall filter, select the firewall filter from the list. Output filter Specifies the VLAN firewall filter that is applied to outgoing packets. To apply an output firewall filter, select the firewall filter from the list. Ports tab 1134 Chapter 59: Configuring Bridging and VLANs Table 150: VLAN Configuration Details (continued) Field Function Your Action Ports Specifies the ports (interfaces) to be associated with this VLAN for data traffic. You can also remove the port association. Click one: • Add—Select the ports from the available list. • Remove—Select the port that you do not want associated with the VLAN. IP address tab IPv4 address Specifies IPv4 address options for the VLAN. Select IPv4 address to enable the IPv4 address options. To configure IPv4: 1. Enter the IP address. 2. Enter the subnet mask—for example, 255.255.255.0. You can also specify the address prefix. 3. To apply an input firewall filter to an interface, select the firewall filter from the list. 4. To apply an output firewall filter to an interface, select the firewall filter from the list. 5. Click the ARP/MAC Details button. Enter the static IP address and MAC address in the window that is displayed. IPv6 address Specifies IPv6 address options for the VLAN. Select IPv6 address to enable the IPv6 address options. To configure IPv6: 1. Enter the IP address—for example: 2001:ab8:85a3::8a2e:370:7334. 2. Specify the subnet mask. Voip tab Ports Specifies the ports to be associated with this VLAN for voice traffic. You can also remove the port association. NOTE: VoIP is not supported on J-EX8200 switches. Related Documentation Click one: • Add—Select the ports from the available list. • Remove—Select the port that you do not want associated with the VLAN. • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 1135 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring VLANs for J-EX Series Switches (CLI Procedure) J-EX Series switches use VLANs to make logical groupings of network nodes with their own broadcast domains. You can use VLANs to limit the traffic flowing across the entire LAN and reduce collisions and packet retransmissions. For each endpoint on the VLAN, configure the following VLAN parameters on the corresponding interface: 1. Set the description of the VLAN: [edit interfaces interface-name unit 0] user@switch# set description vlan-description 2. Set the unique name of the VLAN: [edit interfaces interface-name unit 0] user@switch# set family ethernet-switching vlan members vlan-name 3. Create the subnet for the VLAN: [edit interfaces] user@switch# set vlan unit 0 family inet address ip-address 4. Configure the VLAN tag ID or VLAN ID range for the VLAN: [edit vlans] user@switch# set vlan-name vlan-id vlan-id-number or [edit vlans] user@switch# set vlan-name vlan-range vlan-id-low-vlan-id-high 5. To specify the maximum time that an entry can remain in the forwarding table before it ages out (optional): [edit vlans] user@switch# set vlan-name mac-table-aging-time time 6. To specify a VLAN firewall filter to be applied to incoming or outgoing packets (optional): [edit vlans] user@switch# set vlan-name filter (input | output) filter-name Related Documentation 1136 • Configuring VLANs for J-EX Series Switches (J-Web Procedure) on page 1133 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Creating a Series of Tagged VLANs (CLI Procedure) on page 1140 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Chapter 59: Configuring Bridging and VLANs Configuring Routed VLAN Interfaces (CLI Procedure) Routed VLAN interfaces (RVIs) enable the J-EX Series switch to recognize which packets are being sent to local addresses so that they are bridged (switched) whenever possible and are routed only when needed. Whenever packets can be switched instead of routed, several layers of processing are eliminated. Switching also reduces the number of address lookups. An interface named vlan functions as the logical router, on which you can configure a Layer 3 logical interface for each VLAN. For redundancy, an RVI can be combined with implementations of the Virtual Router Redundancy Protocol (VRRP) in both bridging and VPLS environments. Jumbo frames of up to 9216 bytes are supported on an RVI. To route jumbo data packets on the RVI, you must configure the jumbo MTU size on the member physical interfaces of the RVI and not on the RVI itself (the vlan interface). However, for jumbo control packets—for example, to ping the RVI with a packet size of 6000 bytes or more—you must explicitly configure the jumbo MTU size on the interface named vlan (the RVI). CAUTION: Setting or deleting the jumbo MTU size on the RVI (the vlan interface) while the switch is transmitting packets might result in dropped packets. To configure the routed VLAN interface (RVI): 1. Create a Layer 2 VLAN by assigning it a name (for example, support) and a VLAN ID (for example, 111). [edit] user@switch# set vlans support vlan-id 111 2. Assign an interface (for example, ge-0/0/18) to the VLAN (support) by naming the VLAN as a trunk member on the logical interface, thereby making the interface part of the VLAN’s broadcast domain. [edit] user@switch# set interfaces ge-0/0/18 unit 0 family ethernet-switching vlan members support 3. Create a logical Layer 3 RVI (vlan.111) on a subnet for the VLAN’s broadcast domain. [edit] user@switch# set interfaces vlan unit 111 family inet address 111.111.111.1/24 4. Link the Layer 2 VLAN to the logical Layer 3 interface. [edit] user@switch# set vlans support l3-interface vlan.111 1137 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: Layer 3 interfaces on trunk ports allow the interface to transfer traffic between multiple VLANs. Within a VLAN, traffic is bridged, while across VLANs, traffic is routed. You can display the configuration settings: user@switch> show interfaces vlan terse Interface Admin Link Proto vlan up up vlan.111 up up inet Local Remote 111.111.111.1/24 user@switch> show vlans Name Tag Interfaces default None employee-vlan 20 ge-1/0/0.0, ge-1/0/1.0, ge-1/0/2.0 marketing 40 ge-1/0/10.0, ge-1/0/20.0, ge-1/0/30.0 support 111 ge-0/0/18.0 mgmt bme0.32769, bme0.32771* user@switch> show ethernet-switching table Ethernet-switching table: 1 entries, 0 learned VLAN MAC address Type support 00:19:e2:50:95:a0 Static Related Documentation Age Interfaces - Router • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Configuring IP Directed Broadcast on a J-EX Series Switch on page 904 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Configuring MAC Table Aging (CLI Procedure) The aging process ensures that the J-EX Series switch tracks only active nodes on the network and that it is able to flush out network nodes that are no longer available. To manage MAC entries more efficiently, you can configure an entry's aging time, which is the maximum time that an entry can remain in the Ethernet Switching table before it “ages out”. To configure how long entries remain in the Ethernet Switching table before expiring, using the CLI (here, the VLAN is employee-vlan): [edit vlans employee-vlan] user@switch# set mac-table-aging-time 200 Related Documentation 1138 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 Chapter 59: Configuring Bridging and VLANs • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 Configuring the Native VLAN Identifier (CLI Procedure) J-EX Series switches support receiving and forwarding routed or bridged Ethernet frames with 802.1Q VLAN tags. The logical interface on which untagged packets are to be received must be configured with the same native VLAN ID as that configured on the physical interface. To configure the native VLAN ID using the CLI: 1. Configure the port mode so that the interface is in multiple VLANs and can multiplex traffic between different VLANs. Trunk interfaces typically connect to other switches and to routers on the LAN. Configure the port mode as trunk: [edit interfaces ge-0/0/3 unit 0 family ethernet-switching] user@switch# set port-mode trunk 2. Configure the native VLAN ID: [edit interfaces ge-0/0/3 unit 0 family ethernet-switching] user@switch# set native-vlan-id 3 Related Documentation • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 1139 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Creating a Series of Tagged VLANs (CLI Procedure) To identify which VLAN traffic belongs to, all frames on an Ethernet VLAN are identified by a tag, as defined in the IEEE 802.1Q standard. These frames are tagged and are encapsulated with 802.1Q tags. For a simple network that has only a single VLAN, all traffic has the same 802.1Q tag. Instead of configuring VLANS and 802.1Q tags one at a time for a trunk interface, you can configure a VLAN range to create a series of tagged VLANs. When an Ethernet LAN is divided into VLANs, each VLAN is identified by a unique 802.1Q tag. The tag is applied to all frames so that the network nodes receiving the frames know which VLAN the frames belong to. Trunk ports, which multiplex traffic among a number of VLANs, use the tag to determine the origin of frames and where to forward them. For example, you could configure the VLAN employee and specify a tag range of 10-12. This creates the following VLANs and tags: • VLAN employee-10, tag 10 • VLAN employee-11, tag 11 • VLAN employee-12, tag 12 Creating tagged VLANs in a series has the following limitations: 1140 • Layer 3 interfaces do not support this feature. • Because an access interface can only support one VLAN member, access interfaces also do not support this feature. • Voice over IP (VoIP) configurations do not support a range of tagged VLANs. Chapter 59: Configuring Bridging and VLANs To configure a series of tagged VLANs using the CLI (here, the VLAN is employee): 1. Configure the series (here, a VLAN series from 120 through 130): [edit] user@switch# set vlans employee vlan-range 120-130 2. Associate a series of tagged VLANs when you configure an interface in one of two ways: • Include the name of the series: [edit interfaces] user@switch# set interfaces ge-0/0/22.0 family ethernet-switching vlan members employee • Include the VLAN range: [edit interfaces] user@switch# set interfaces ge-0/0/22.0 family ethernet-switching vlan members 120–130 Associating a series of tagged VLANS to an interface by name or by VLAN range have the same result: VLANs __employee_120__ through __employee_130__ are created. NOTE: When a series of VLANs are created using the vlan-range command, the VLAN names are prefixed and suffixed with a double underscore. Related Documentation • Verifying That a Series of Tagged VLANs Has Been Created on page 1155 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 1141 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Virtual Routing Instances (CLI Procedure) Use virtual routing and forwarding (VRF) to divide a J-EX Series switch into multiple virtual routing instances. VRF allows you to isolate traffic traversing the network without using multiple devices to segment your network. VRF is supported on all Layer 3 interfaces. Before you begin, make sure to set up your VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. To configure virtual routing instances: 1. Create a routing instance: [edit routing-instances] user@switch# set routing-instance-name instance-type virtual-router NOTE: J-EX Series switches only support the virtual-router instance type. 2. Bind each routing instance to the corresponding physical interfaces: [edit routing-instances] user@switch# set routing-instance-name interface interface-name.logical-unit-number 3. Create the logical interfaces that are bound to the routing instance. • To create a logical interface with an IPv4 address: [edit interfaces] user@switch# set interface-name unit logical-unit-number family inet address ip-address • To create a logical interface with an IPv6 address: [edit interfaces] user@switch# set interface-name unit logical-unit-number family inet6 address ipv6–address NOTE: Do not create a logical interface using the family ethernet-switching option in this step. Binding an interface using the family ethernet-switching option to a routing instance can cause the interface to shutdown. 4. Enable VLAN tagging on each physical interface that was bound to the routing instance: [edit interfaces] user@switch# set interface-name vlan-tagging Related Documentation 1142 • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Verifying That Virtual Routing Instances Are Working on page 1157 Chapter 59: Configuring Bridging and VLANs • Understanding Virtual Routing Instances on J-EX Series Switches on page 1048 Creating a Private VLAN (CLI Procedure) The private VLAN (PVLAN) feature on J-EX Series switches allows an administrator to split a broadcast domain into multiple isolated broadcast subdomains, essentially putting a VLAN inside a VLAN. Before you begin, make sure you set up your VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. NOTE: Configuring a voice over IP (VoIP) VLAN on PVLAN interfaces is not supported. To configure a private VLAN: 1. Set the primary VLAN to have no local switching: NOTE: The primary VLAN must be a tagged VLAN. [edit vlans] user@switch# set primary-vlan-name no-local-switching 2. For each community VLAN, configure access interfaces: NOTE: The secondary VLANs must be untagged VLANs. [edit vlans] user@switch# set community-vlan-name interface interface-name 3. For each community VLAN, set the primary VLAN: [edit vlans] user@switch# set community-vlan-name primary-vlan primary-vlan-name 4. For each isolated VLAN, add the interface to the primary VLAN: [edit vlans] user@switch# set primary-vlan-name interface interface-name Related Documentation • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 • Verifying That a Private VLAN Is Working on page 1159 • Understanding Private VLANs on J-EX Series Switches on page 1047 1143 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Q-in-Q Tunneling (CLI Procedure) Q-in-Q tunneling allows service providers on Ethernet access networks to segregate or bundle customer traffic into different VLANs by adding another layer of 802.1Q tags. You can configure Q-in-Q tunneling on J-EX Series switches. Before you begin configuring Q-in-Q tunneling, make sure you set up your VLANs. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136 or “Configuring VLANs for J-EX Series Switches (J-Web Procedure)” on page 1133. To configure Q-in-Q tunneling: 1. Enable Q-in-Q tunneling on the S-VLAN: [edit vlans] user@switch# set s-vlan-name dot1q-tunneling 2. Set the allowed C-VLANs on the S-VLAN (optional). Here, the C-VLANs are identified by VLAN range: [edit vlans] user@switch# set s-vlan-name dot1q-tunneling customer-vlans range 3. Change the global Ethertype value (optional): [edit] user@switch# set ethernet-switching-options dot1q-tunneling ether-type ether-type-value 4. Disable MAC address learning on the S-VLAN (optional): [edit vlans] user@switch# set s-vlan-name no-mac-learning Related Documentation • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Verifying That Q-in-Q Tunneling Is Working on page 1158 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 Configuring GVRP (J-Web Procedure) As a network expands and the number of clients and VLANs increases, VLAN administration becomes complex, and the task of efficiently configuring VLANs on multiple J-EX Series switches becomes increasingly difficult. To automate VLAN administration, you can enable GARP VLAN Registration Protocol (GVRP) on the network. GVRP learns VLANs on a particular 802.1Q trunk port and adds the corresponding trunk interface to the VLAN if the advertised VLAN is preconfigured or already exists on the switch. For example, a VLAN named “sales” is advertised to trunk interface 1 on the GVRP-enabled switch. The switch adds trunk interface 1 to the sales VLAN if the sales VLAN already exists on the switch. 1144 Chapter 59: Configuring Bridging and VLANs As individual interfaces become active and send requests to join a VLAN, the VLAN configuration is updated and propagated among the switches. Limiting the VLAN configuration to active participants reduces the network overhead. GVRP also provides the benefit of pruning VLANs to limit the scope of broadcast, unknown unicast, and multicast (BUM) traffic to interested network devices only. To configure GVRP using the J-Web interface: 1. Select Configure > Switching > GVRP. Interfaces on which GVRP has been enabled are listed. 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 334 for details about all commit options. 2. To enable GVRP on an interface, click Add. Click the arrow key to move the interface from the Interface Out of GVRP list to the Interface under GVRP list, and click OK. 3. To modify GVRP timers, click Global Settings. For modifying GVRP Timer settings for the interface, enter information as described in Table 151 on page 1145. 4. Click OK to apply changes to the configuration or click Cancel to cancel without saving changes. To disable an interface, select the interface and click Disable Port. Table 151: GVRP Timer Settings Field Function Your Action Join Timer Specifies the maximum number of milliseconds the interface waits before sending VLAN advertisements. Type a number. Leave Timer Specifies the number of milliseconds an interface waits after receiving a leave message before the interface leaves the VLAN specified in the message. Type a number. Leave All Timer Specifies the interval in milliseconds at which Leave All messages are sent on interfaces. Leave All messages help to maintain current GVRP VLAN membership information in the network. Type a number. Disable GVRP Disables GVRP on all interfaces. To disable GVRP, select the check box. To enable GVRP, clear the check box. Related Documentation • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Monitoring GVRP on page 1161 1145 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Redundant Trunk Groups (J-Web Procedure) A redundant trunk link provides a simple solution for network recovery when a trunk interface goes down. Traffic is routed to another trunk interface, keeping network convergence time to a minimum. You can configure redundant trunk groups (RTGs) with a primary link and a secondary link on trunk interfaces, or configure dynamic selection of the active interface. If the primary link fails, the secondary link automatically takes over without waiting for normal STP convergence. An RTG can be created only if the following conditions are satisfied: • A minimum of two trunk interfaces that are not part of any RTG are available. • All the selected trunk interfaces to be added to the RTG have the same VLAN configuration. • The selected trunk interfaces are not part of a spanning-tree configuration. To configure an RTG using the J-Web interface: 1. Select Configure > Switching > RTG. The RTG Configuration page displays a list of existing RTGs. If you select a specific RTG, the details of the selected RTG are displayed in the Details of group section. 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 334 for details about all commit options. 2. Click one: • Add—Creates an RTG. • Edit—Modifies an RTG. • Delete—Deletes an RTG. When you are adding or editing an RTG, enter information as described in Table 152 on page 1146. 3. Click OK to apply changes to the configuration or click Cancel to cancel without saving changes. Table 152: RTG Configuration Fields Field Function Your Action Group Name Specifies a unique name for the RTG. Enter a name. Member Interface 1 Specifies a logical interface containing multiple trunk interfaces. Select a trunk interface from the list. 1146 Chapter 59: Configuring Bridging and VLANs Table 152: RTG Configuration Fields (continued) Field Function Your Action Member Interface 2 Specifies a trunk interface containing multiple VLANs. Select a trunk interface from the list. Select Primary Interface Enables you to specify one of the interfaces in the RTG as the primary link. The interface without this option is the secondary link in the RTG. 1. Specifies that the system dynamically selects the active interface. Select the option button. Dynamically select my active interface Related Documentation Select the option button. 2. Select the primary interface. • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) Multiple VLAN Registration Protocol (MVRP) is used to manage dynamic VLAN registration in a LAN. You can use MVRP on J-EX Series switches. MVRP is disabled by default on J-EX Series switches. To enable MVRP or set MVRP options, follow these instructions: • Enabling MVRP on page 1147 • Disabling MVRP on page 1147 • Disabling Dynamic VLANs on page 1148 • Configuring Timer Values on page 1148 • Configuring MVRP Registration Mode on page 1149 Enabling MVRP MVRP can only be enabled on trunk interfaces. To enable MVRP on all trunk interfaces on the switch: [edit protocols mvrp] user@switch# set interface all To enable MVRP on a specific trunk interface: [edit protocols mvrp] user@switch# set interface xe-0/0/1.0 Disabling MVRP MVRP is disabled by default. You only need to perform this procedure if you have previously enabled MVRP. To disable MVRP on all trunk interfaces on the switch: 1147 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit protocols mvrp] user@switch# set disable To disable MVRP on a specific trunk interface: [edit protocols mvrp] user@switch# set disable interface xe-0/0/1.0 Disabling Dynamic VLANs Dynamic VLANs can be created on interfaces participating in MVRP by default. Dynamic VLANs are VLANs created on one switch that are propagated to other switches dynamically; in this case, using MVRP. Dynamic VLAN creation through MVRP cannot be disabled per switch interface. To disable dynamic VLAN creation for interfaces participating in MVRP, you must disable it for all interfaces on the switch. To disable dynamic VLAN creation: [edit protocols mvrp] user@switch# set no-dynamic-vlan Configuring Timer Values The timers in MVRP define the amount of time an interface waits to join or leave MVRP or to send or process the MVRP information for the switch after receiving an MVRP PDU. The join timer controls the amount of time the switch waits to accept a registration request, the leave timer controls the period of time that the switch waits in the Leave state before changing to the unregistered state, and the leaveall timer controls the frequency with which the LeaveAll messages are communicated. The default MVRP timer values are 200 ms for the join timer, 1000 ms for the leave timer, and 10000 ms for the leaveall timer. BEST PRACTICE: Maintain default timer settings unless there is a compelling reason to change the settings. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. To set the join timer for all interfaces on the switch: [edit protocols mvrp] user@switch# set interface all join-timer 300 To set the join timer for a specific interface: [edit protocols mvrp] user@switch# set interface xe-0/0/1.0 300 To set the leave timer for all interfaces on the switch: [edit protocols mvrp] user@switch# set interface all leave-timer 1200 To set the leave timer for a specific interface: 1148 Chapter 59: Configuring Bridging and VLANs [edit protocols mvrp] user@switch# set interface xe-0/0/1.0 leave-timer 1200 To set the leaveall timer for all interfaces on the switch: [edit protocols mvrp] user@switch# set interface all leaveall-timer 12000 To set the leaveall timer for a specific interface: [edit protocols mvrp] user@switch# set interface xe-0/0/1.0 leaveall-timer 12000 Configuring MVRP Registration Mode The default MVRP registration mode for any interface participating in MVRP is normal. An interface in normal registration mode participates in MVRP when MVRP is enabled on the switch. An interface in forbidden registration mode does not participate in MVRP even if MVRP is enabled on the switch. To set all interfaces to forbidden registration mode: [edit protocols mvrp] user@switch# set interface all registration forbidden To set one interface to forbidden registration mode: [edit protocols mvrp] user@switch# set interface xe-0/0/1.0 registration forbidden To set all interfaces to normal registration mode: [edit protocols mvrp] user@switch# set interface all registration normal To set one interface to normal registration mode: [edit protocols mvrp] user@switch# set interface xe-0/0/1.0 registration normal Related Documentation • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Verifying That MVRP Is Working Correctly on page 1162 1149 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) Layer 2 protocol tunneling (L2PT) allows you to send Layer 2 protocol data units (PDUs) across a service provider network and deliver them to J-EX Series switches at a remote location. This feature is useful when you have a network that includes remote sites that are connected across a service provider network and you want to run Layer 2 protocols on switches connected across the service provider network. Tunneled Layer 2 PDUs do not normally arrive at high rate. If the tunneled Layer 2 PDUs do arrive at high rate, there might be a problem in the network. Typically, you would want to shut down the interface that is receiving a high rate of tunneled Layer 2 PDUs so that the problem can be isolated. You do so using the shutdown-threshold statement. However, if you do not want to completely shut down the interface, you can configure the switch to drop tunneled Layer 2 PDUs that exceed a certain threshold using the drop-threshold statement. There are no default settings for drop-threshold and shutdown-threshold. If you do not specify these thresholds, then no thresholds are enforced. As a result, the switch tunnels all Layer 2 PDUs regardless of the speed at which they are received, although the number of packets tunneled per second might be limited by other factors. You can specify a drop threshold value without specifying a shutdown threshold value, and you can specify a shutdown threshold value without specifying a drop threshold value. If you specify both threshold values, then the drop threshold value must be less than or equal to the shutdown threshold value. If the drop threshold value is greater than the shutdown threshold value and you try to commit the configuration, the commit will fail. NOTE: If the switch receives untagged Layer 2 control PDUs to be tunnelled, then you must configure the switch to map untagged (native) packets to an L2PT-enabled VLAN. Otherwise, the untagged Layer 2 control PDU packets are discarded. For more information, see “Understanding Q-in-Q Tunneling on J-EX Series Switches” on page 1051 and “Configuring Q-in-Q Tunneling (CLI Procedure)” on page 1144. To configure L2PT on a J-EX Series switch: 1. Because L2PT operates under the Q-in-Q tunneling configuration, you must enable Q-in-Q tunneling before you can configure L2PT. Enable Q-in-Q tunneling on VLAN customer-1: [edit] user@switch# set vlans customer-1 dot1q-tunneling 2. Enable L2PT for the Layer 2 protocol you want to tunnel, on the VLAN: • To enable L2PT for a specific protocol (here, STP): [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2-protocol-tunneling stp 1150 Chapter 59: Configuring Bridging and VLANs • To enable L2PT for all supported protocols: [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2-protocol-tunneling all 3. (Optional) Configure the drop threshold: NOTE: If you also configure the shutdown threshold, ensure that you configure the drop threshold value to be less than or equal to the shutdown threshold value. If the drop threshold value is greater than the shutdown threshold value and you to try to commit the configuration changes, the commit will fail. [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2–protocol-tunneling stp drop-threshold 50 4. (Optional) Configure the shutdown threshold: NOTE: If you also configure the drop threshold, ensure that you configure the shutdown threshold value to be greater than or equal to the drop threshold value. If the shutdown threshold value is less than the drop threshold value and you to try to commit the configuration changes, the commit will fail. [edit] user@switch# set vlans customer-1 dot1q-tunneling layer2–protocol-tunneling stp shutdown-threshold 100 NOTE: Once an interface is disabled, you must explicitly reenable it using the clear ethernet-switching layer2-protocol-tunneling error command. Otherwise, the interface remains disabled. Related Documentation • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 Configuring MAC Notification (CLI Procedure) When a switch learns or unlearns a MAC address, SNMP notifications can be sent to the network management system at regular intervals to record the addition or removal of the MAC address. This process is known as MAC notification. The MAC notification interval defines how often Simple Network Management Protocol (SNMP) notifications logging the addition or removal of MAC addresses on the switch are sent to the network management system. 1151 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS MAC notification is disabled by default. When MAC notification is enabled, the default MAC notification interval is 30 seconds. To enable or disable MAC notification, or to set the MAC notification interval, perform these tasks: • Enabling MAC Notification on page 1152 • Disabling MAC Notification on page 1152 • Setting the MAC Notification Interval on page 1152 Enabling MAC Notification MAC notification is disabled by default. You need to perform this procedure to enable MAC notification. To enable MAC notification on the switch with the default MAC notification interval of 30 seconds: [edit ethernet-switching-options] user@switch# set mac-notification To enable MAC notification on the switch with any other MAC notification interval (here, the MAC notification interval is set to 60 seconds): [edit ethernet-switching-options] user@switch# set mac-notification notification-interval 60 Disabling MAC Notification MAC notification is disabled by default. Perform this procedure only if MAC notification was previously enabled on your switch. To disable MAC notification on the switch: [edit ethernet-switching-options] user@switch# delete mac-notification Setting the MAC Notification Interval The default MAC notification interval is 30 seconds. The procedure to change the MAC notification interval to a different interval is identical to the procedure to enable MAC notification on the switch with a nondefault value for the MAC notification interval. To set the MAC notification interval on the switch (here, the MAC notification interval is set to 5 seconds): [edit ethernet-switching-options] user@switch# set mac-notification notification-interval 5 Related Documentation 1152 • Verifying that MAC Notification Is Working Properly on page 1163 Chapter 59: Configuring Bridging and VLANs Configuring Proxy ARP (CLI Procedure) You can configure proxy Address Resolution Protocol (ARP) on your J-EX Series switch to enable the switch to respond to ARP queries for network addresses by offering its own media access control (MAC) address. With proxy ARP enabled, the switch captures and routes traffic to the intended destination. To configure proxy ARP on a single interface: [edit interfaces] user@switch# set ge-0/0/3 unit 0 proxy-arp restricted BEST PRACTICE: We recommend that you configure proxy ARP in restricted mode. In restricted mode, the switch is not a proxy if the source and target IP addresses are on the same subnet. If you use unrestricted mode, disable gratuitous ARP requests on the interface to avoid the situation of the switch’s response to a gratuitous ARP request appearing to the host to be an indication of an IP conflict: To configure proxy ARP on a routed VLAN interface (RVI): [edit interfaces] user@switch# set vlan unit 100 proxy-arp restricted Related Documentation • Example: Configuring Proxy ARP on a J-EX Series Switch on page 2621 • Verifying That Proxy ARP Is Working Correctly on page 1164 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 1153 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1154 CHAPTER 60 Verifying Bridging and VLAN Configuration • Verifying That a Series of Tagged VLANs Has Been Created on page 1155 • Verifying That Virtual Routing Instances Are Working on page 1157 • Verifying That Q-in-Q Tunneling Is Working on page 1158 • Verifying That a Private VLAN Is Working on page 1159 • Monitoring Ethernet Switching on page 1160 • Monitoring GVRP on page 1161 • Verifying That MVRP Is Working Correctly on page 1162 • Verifying That MAC Notification Is Working Properly on page 1163 • Verifying That Proxy ARP Is Working Correctly on page 1164 Verifying That a Series of Tagged VLANs Has Been Created Purpose Action Verify that a series of tagged VLANs is created on the switch. Display the VLANs in the ascending order of their VLAN ID: user@switch> show vlans sort-by tag Name Tag __employee_120__ 120 Interfaces ge-0/0/22.0* __employee_121__ 121 __employee_122__ 122 __employee_123__ 123 __employee_124__ 124 __employee_125__ 125 __employee_126__ 126 __employee_127__ 127 __employee_128__ 128 __employee_129__ 129 ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* ge-0/0/22.0* 1155 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS __employee_130__ 130 ge-0/0/22.0* Display the VLANs by the alphabetical order of the VLAN name: user@switch> show vlans sort-by name Name Tag Interfaces __employee_120__ 120 ge-0/0/22.0* __employee_121__ 121 ge-0/0/22.0* __employee_122__ 122 ge-0/0/22.0* __employee_123__ 123 ge-0/0/22.0* __employee_124__ 124 ge-0/0/22.0* __employee_125__ 125 ge-0/0/22.0* __employee_126__ 126 ge-0/0/22.0* __employee_127__ 127 ge-0/0/22.0* __employee_128__ 128 ge-0/0/22.0* __employee_129__ 129 ge-0/0/22.0* __employee_130__ 130 ge-0/0/22.0* Display the VLANs by specifying the VLAN-range name (here, the VLAN-range name is employee): user@switch> show vlans employee Name Tag Interfaces __employee_120__ 120 ge-0/0/22.0* __employee_121__ 121 ge-0/0/22.0* __employee_122__ 122 ge-0/0/22.0* __employee_123__ 123 ge-0/0/22.0* __employee_124__ 124 ge-0/0/22.0* __employee_125__ 125 ge-0/0/22.0* __employee_126__ 126 ge-0/0/22.0* __employee_127__ 127 ge-0/0/22.0* __employee_128__ 128 ge-0/0/22.0* __employee_129__ 129 ge-0/0/22.0* 1156 Chapter 60: Verifying Bridging and VLAN Configuration __employee_130__ 130 ge-0/0/22.0* Meaning The sample output shows the VLANs configured on the switch. The series of tagged VLANs is displayed: __employee__120__ through __employee_130__. Each of the tagged VLANs is configured on the trunk interface ge-0/0/22.0. The asterisk (*) beside the interface name indicates that the interface is UP. When a series of VLANs is created using the vlan-range statement, the VLAN names are prefixed and suffixed with a double underscore. Related Documentation • Creating a Series of Tagged VLANs (CLI Procedure) on page 1140 Verifying That Virtual Routing Instances Are Working Purpose Action After creating a virtual routing instance, make sure it is set up properly. 1. Use the show route instance command to list all of the routing instances and their properties: user@switch> show route instance Instance Type Primary RIB Active/holddown/hidden master forwarding inet.0 3/0/0 __juniper_private1__ forwarding __juniper_private1__.inet.0 1/0/3 __juniper_private2__ forwarding instance1 forwarding r1 virtual-router r1.inet.0 r2 1/0/0 virtual-router r2.inet.0 1/0/0 2. Use the show route forwarding-table command to view the forwarding table information for each routing instance: user@switch> show route forwarding-table Routing table: r1.inet Internet: Destination Type RtRef Next hop default perm 0 0.0.0.0/32 perm 0 103.1.1.0/24 ifdn 0 ge-0/0/3.0 103.1.1.0/32 iddn 0 103.1.1.0 ge-0/0/3.0 103.1.1.1/32 user 0 103.1.1.1/32 intf 0 103.1.1.1 Type Index NhRef Netif rjct 539 2 dscd 537 1 rslv 579 1 recv 577 1 rjct locl 539 578 2 2 1157 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 103.1.1.1/32 103.1.1.255/32 ge-0/0/3.0 224.0.0.0/4 224.0.0.1/32 255.255.255.255/32 Meaning Related Documentation iddn iddn 0 103.1.1.1 0 103.1.1.255 locl bcst 578 576 2 1 perm perm perm 0 0 224.0.0.1 0 mdsc mcst bcst 538 534 535 1 1 1 The output confirms that the virtual routing instances are created and the links are up and displays the routing table information. • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 Verifying That Q-in-Q Tunneling Is Working Purpose Action After creating a Q-in-Q VLAN, verify that it is set up properly. 1. Use the show configuration vlans command to determine if you successfully created the primary and secondary VLAN configurations: user@switch> show configuration vlans svlan { vlan-id 300; dot1q-tunneling { customer-vlans [ 101–200 ]; } } 2. Use the show vlans command to view VLAN information and link status: user@switch> show vlans s-vlan-name extensive VLAN: svlan, Created at: Thu Oct 23 16:53:20 2008 802.1Q Tag: 300, Internal index: 2, Admin State: Enabled, Origin: Static Dot1q Tunneling Status: Enabled Customer VLAN ranges: 101–200 Protocol: Port Mode Number of interfaces: Tagged 1 (Active = 0), Untagged 1 (Active = 0) ge-0/0/1, tagged, trunk ge-0/0/2, untagged, access Meaning Related Documentation 1158 The output confirms that Q-in-Q tunnling is enabled and that the VLAN is tagged, and lists the customer VLANs that are associated with the tagged VLAN. • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 Chapter 60: Verifying Bridging and VLAN Configuration Verifying That a Private VLAN Is Working Purpose Action After creating and configuring private VLANs, verify they are set up properly. 1. Use the show configuration vlans command to determine if you successfully created the primary and secondary VLAN configurations: user@switch> show configuration vlans community1 { interface { interface a; interface b; } primary-vlan pvlan; } community2 { interface { interface d; interface e; } primary-vlan pvlan; } pvlan { vlan-id 1000; interface { isolated1; isolated2; trunk1; trunk2; } no-local-switching; } 2. Use the show vlans command to view VLAN information and link status: user@switch> show vlans pvlan extensive VLAN: pvlan, Created at: time 802.1Q Tag: vlan-id, Internal index: index-number, Admin State: Enabled, Origin: Static Private VLAN Mode: Primary Protocol: Port Mode Number of interfaces: Tagged 2 (Active = 0), Untagged 6 (Active = 0) trunk1, tagged, trunk interface a, untagged, access interface b, untagged, access interface c, untagged, access interface d, untagged, access interface e, untagged, access interface f, untagged, access trunk2, tagged, trunk Secondary VLANs: Isolated 2, Community 2 Isolated VLANs : __pvlan_pvlan_isolated1__ __pvlan_pvlan_isolated2__ Community VLANs : community1 community2 1159 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3. Use the show ethernet-switching table vlan command to view logs for MAC learning on the VLANs: user@switch> vlan pvlan extensive pvlan, * Interface(s): trunk1 Interface(s): interface Interface(s): interface Interface(s): interface Interface(s): interface Interface(s): interface Interface(s): interface Interface(s): trunk2 Type: Flood Nexthop index: 1344 Meaning Related Documentation a b c d e f The output shows that the primary and secondary VLANs were created and associated and displays MAC learning information. • Creating a Private VLAN (CLI Procedure) on page 1143 • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 Monitoring Ethernet Switching Purpose Use the monitoring feature to view details that the J-EX Series switch maintains in its Ethernet switching table. These are details about the nodes on the LAN such as VLAN name, VLAN ID, member interfaces, MAC addresses, and so on. Action To display Ethernet switching details in the J-Web interface, select Monitor > Switching > Ethernet Switching. To view Ethernet switching details in the CLI, enter the following commands: Meaning • show ethernet-switching table • show vlans • show ethernet-switching interfaces Table 153 on page 1160 summarizes the Ethernet switching output fields. Table 153: Ethernet Switching Output Fields Field Value Ethernet Switching Table Information MAC Table Count The number of entries added to the Ethernet switching table. MAC Table Learned The number of dynamically learned MAC addresses in the Ethernet switching table. Ethernet Switching Table Information 1160 Chapter 60: Verifying Bridging and VLAN Configuration Table 153: Ethernet Switching Output Fields (continued) Field Value VLAN The VLAN name. MAC Address The MAC address associated with the VLAN. If a VLAN range has been configured for a VLAN, the output displays the MAC addresses for the entire series of VLANs that were created with that name. Type The type of MAC address. Values are: • static—The MAC address is manually created. • learn—The MAC address is learned dynamically from a packet's source MAC address. • flood—The MAC address is unknown and flooded to all members. Age The time remaining before the entry ages out and is removed from the Ethernet switching table. Interfaces The associated interfaces. MAC Learning Log VLAN-Name The VLAN name. MAC Address The learned MAC address associated with the VLAN ID. Time Timestamp for the time at which when the MAC address was added or deleted from the MAC learning log. State Operating state of the interface. Values are Up and Down. Related Documentation • Configuring MAC Table Aging (CLI Procedure) on page 1138 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Monitoring GVRP Purpose Action Use the monitoring feature to view information about the GVRP configuration on the J-EX Series switch. To monitor GVRP in the J-Web interface, select Monitor > Switching > GVRP. To monitor GVRP in the CLI, enter the following command: • Meaning show gvrp Table 154 on page 1162 summarizes the GVRP output fields. 1161 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 154: Summary of GVRP Output Fields Field Value Global GVRP Configuration GVRP Status Displays whether GVRP is enabled or disabled. GVRP Timers • Join—The number of milliseconds the interfaces must wait before sending VLAN advertisements. • Leave—The number of milliseconds an interface must wait after receiving a Leave message to remove the interface from the VLAN specified in the message. • Leave All—The interval in milliseconds at which Leave All messages are sent on interfaces. Leave All messages maintain current GVRP VLAN membership information in the network. GVRP Interface Details Interface Name The interface on which GVRP is configured. Protocol Status Displays whether GVRP is enabled or disabled on the interface. Related Documentation • Configuring GVRP (J-Web Procedure) on page 1144 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 Verifying That MVRP Is Working Correctly Purpose Action After configuring your J-EX Series switch to participate in MVRP, verify that the configuration is properly set and that MVRP messages are being sent and received on your switch. 1. Confirm that MVRP is enabled on your switch. user@switch> show mvrp Global MVRP configuration MVRP status : Enabled MVRP dynamic vlan creation: Enabled MVRP Timers (ms): Interface Join Leave LeaveAll ---------------------------all 200 600 10000 xe-0/1/1.0 200 600 10000 Interface based configuration: Interface Status Registration Dynamic VLAN Creation ---------------------------------------------------all Disabled Fixed Enabled xe-0/1/1.0 Enabled Normal Enabled 2. Confirm that MVRP messages are being sent and received on your switch. user@switch> show mvrp statistics interface xe-0/1/1.0 1162 Chapter 60: Verifying Bridging and VLAN Configuration MVRP statistics MRPDU received Invalid PDU received New received Join Empty received Join In received Empty received In received Leave received LeaveAll received MRPDU transmitted MRPDU transmit failures New transmitted Join Empty transmitted Join In transmitted Empty transmitted In transmitted Leave transmitted LeaveAll transmitted Meaning : : : : : : : : : : : : : : : : : : 3342 0 2 1116 2219 2 2 1 1117 3280 0 0 1114 2163 1 1 1 1111 The output of show mvrp shows that interface xe-0/1/1.0 is enabled for MVRP participation as shown in the status in the Interface based configuration field. The output for show mvrp statistics interface xe-0/1/1.0 confirms that MVRP messages are being transmitted and received on the interface. Related Documentation • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Verifying That MAC Notification Is Working Properly Purpose Verify that MAC notification is enabled or disabled, and that the MAC notification interval is set to the specified value. Action Verify that MAC notification is enabled while also verifying the MAC notification interval setting. user@switch> show ethernet-switching mac-notification Notification Status: Enabled Notification Interval: 30 Meaning The output in the Notification Status field shows that MAC notification is enabled. The output in the Notification Status field would display Disabled if MAC notification was disabled. The Notification Interval field output shows that the MAC notification interval is set to 30 seconds. Related Documentation • Configuring MAC Notification (CLI Procedure) on page 1151 1163 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verifying That Proxy ARP Is Working Correctly Purpose Action Verify that the switch is sending proxy ARP messages. List the system statistics for ARP: user@switch> show system statistics arp arp: 198319 datagrams received 45 ARP requests received 12 ARP replies received 2 resolution requests received 2 unrestricted proxy requests 0 restricted proxy requests 0 received proxy requests 0 proxy requests not proxied 0 restricted-proxy requests not proxied 0 with bogus interface 0 with incorrect length 0 for non-IP protocol 0 with unsupported op code 0 with bad protocol address length 0 with bad hardware address length 0 with multicast source address 0 with multicast target address 0 with my own hardware address 168705 for an address not on the interface 0 with a broadcast source address 0 with source address duplicate to mine 29555 which were not for me 0 packets discarded waiting for resolution 4 packets sent after waiting for resolution 27 ARP requests sent 47 ARP replies sent 0 requests for memory denied 0 requests dropped on entry 0 requests dropped during retry 0 requests dropped due to interface deletion 0 requests on unnumbered interfaces 0 new requests on unnumbered interfaces 0 replies for from unnumbered interfaces 0 requests on unnumbered interface with non-subnetted donor 0 replies from unnumbered interface with non-subnetted donor Meaning Related Documentation 1164 The statistics show that two proxy ARP requests were received, and the proxy requests not proxied field indicates that all the unproxied ARP requests received have been proxied by the switch. • Configuring Proxy ARP (CLI Procedure) on page 1153 CHAPTER 61 Troubleshooting Bridging and VLAN Configuration • Troubleshooting Ethernet Switching on page 1165 Troubleshooting Ethernet Switching Troubleshooting issues for Ethernet switching on J-EX Series switches: • MAC Address in the Switch’s Ethernet Switching Table Is Not Updated After a MAC Address Move on page 1165 MAC Address in the Switch’s Ethernet Switching Table Is Not Updated After a MAC Address Move Problem Sometimes a MAC address entry in the switch’s Ethernet switching table is not updated after the device with that MAC address has been moved from one interface to another on the switch. Typically, the switch does not wait for a MAC address expiration when a MAC move operation occurs. As soon as the switch detects the MAC address on the new interface, it immediately updates the table. Many network devices send a gratuitous ARP packet when switching an IP address from one device to another. The switch updates its ARP cache table after receipt of such gratuitous ARP messages, and then it also updates its Ethernet switching table. However, sometimes silent devices, such as SYSLOG servers or SNMP Trap receivers that receive UDP traffic but do not return acknowledgement (ACK ) messages to the traffic source, do not send gratuitous ARP packets when a device moves. If such a move occurs when the system administrator is not available to explicitly clear the affected interfaces by issuing the clear ethernet-switching table command, the entry for the moved device in the Ethernet switching table is not updated. Solution Set up the switch to handle unattended MAC address switchovers. 1. Reduce the system-wide ARP aging timer. (By default, the ARP aging timer is set at 20 minutes. The range of the timer is from 1 through 240 minutes.) [edit system arp] user@switch# set aging-timer 3 2. Set the MAC aging timer to the same value as the ARP timer. (By default, the MAC aging timer is set to 300 seconds. The range is 15 to 1,000,000 seconds.) 1165 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit vlans] user@switch# set vlans sales mac-table-aging-time 180 The ARP entry and the MAC address entry for the moved device expire within the times specified by the aging timer values. After the entries expire, the switch sends a new ARP message to the IP address of the device. The device responds to the ARP, thereby refreshing the entries in the switch’s ARP cache table and Ethernet switching table Related Documentation 1166 • arp on page 171 • mac-table-aging-time on page 1209 CHAPTER 62 Configuration Statements for Bridging and VLANs • [edit ethernet-switching-options] Configuration Statement Hierarchy on page 1167 • [edit interfaces] Configuration Statement Hierarchy on page 1169 • [edit protocols] Configuration Statement Hierarchy on page 1173 • [edit routing-instances] Configuration Hierarchy on page 1180 • [edit vlans] Configuration Statement Hierarchy on page 1180 [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; 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; } 1167 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mac-notification { notification-interval seconds; } mac-table-aging-time seconds; port-error-disable { disable-timeout timeout; } redundant-trunk-group { group-name name { interface interface-name ; } } secure-access-port { 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 ); 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 ); 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 ); (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-unknown-unicast; 1168 Chapter 62: Configuration Statements for Bridging and VLANs } } 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 ; } } } Related Documentation • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 [edit interfaces] Configuration Statement Hierarchy interfaces { aex { aggregated-ether-options { (flow-control | no-flow-control); lacp mode { periodic interval; } link-speed speed; minimum-links number; } description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; 1169 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } fe-fpc/pic/port { description text; disable; mtu bytes; no-gratuitous-arp-request; speed speed; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } ge-fpc/pic/port { description text; disable; ether-options { 802.3ad aex { lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); 1170 Chapter 62: Configuration Statements for Bridging and VLANs vlan-id vlan-id-number; } vlan-tagging; } interface-range interface-range name { description text; disable; ether-options { 802.3ad aex { lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control| no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; member interface-name; member-range starting-interface name to ending-interface name; mtu bytes; unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } } lo0 { description text; disable; hold-time up milliseconds down milliseconds; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); } } me0 { description text; disable; hold-time up milliseconds down milliseconds; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} 1171 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } vlan { description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); } } vme { description text; disable; hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } xe-fpc/pic/port { description text; disable; ether-options { 802.3ad aex { lacp (802.3ad) { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; speed (auto-negotiation | speed); } hold-time up milliseconds down milliseconds; mtu bytes; no-gratuitous-arp-request; traceoptions; 1172 Chapter 62: Configuration Statements for Bridging and VLANs (traps | no-traps); unit logical-unit-number { description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); rpm; (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } } Related Documentation • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 922 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 930 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure) on page 797 • J-EX Series Switches Interfaces Overview on page 863 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ [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; reauthentication { interval seconds; } retries number; server-fail (deny | permit | use-cache | vlan-id | vlan-name); server-reject-vlan (vlan-id | vlan-name); 1173 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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); } } gvrp { ; interface (all | [interface-name]) { disable; } join-timer millseconds; leave-timer milliseconds; leaveall-timer milliseconds; } 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 { group ip-address; } } proxy ; query-interval seconds; query-last-member-interval seconds; query-response-interval seconds; robust-count number; } } lldp { disable; advertisement-interval seconds; 1174 Chapter 62: Configuration Statements for Bridging and VLANs hold-multiplier number; interface (all | interface-name) { disable; } traceoptions { file filename ; flag flag (detail | disable | receive | send); } } 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; max-hops hops; 1175 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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); loss-threshold number; } mep mep-id { 1176 Chapter 62: Configuration Statements for Bridging and VLANs 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; alarm; } cost cost; 1177 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 number; } polling-interval seconds; sample-rate number; source-ip } stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; } vstp { bpdu-block-on-edge; disable; 1178 Chapter 62: Configuration Statements for Bridging and VLANs 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 { alarm; block; } cost cost; disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } } Related Documentation • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding MAC RADIUS Authentication on J-EX Series Switches • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Ethernet OAM Connectivity Fault Management for a J-EX Series Switch on page 3463 • Understanding Ethernet OAM Link Fault Management for a J-EX Series Switch on page 3427 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding How to Use sFlow Technology for Network Monitoring on a J-EX Series Switch on page 3283 • Understanding VSTP for J-EX Series Switches on page 1281 1179 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit routing-instances] Configuration Hierarchy routing-instances routing-instance-name { instance-type virtual-router interface interface-name } Related Documentation • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 [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)); } 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 1180 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Creating a Private VLAN (CLI Procedure) on page 1143 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 Chapter 62: Configuration Statements for Bridging and VLANs arp Syntax Hierarchy Level Release Information Description Options arp { aging-timer minutes; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the time interval between ARP updates. aging-timer minutes—Time interval in minutes between ARP updates. In environments where the number of ARP entries to update is high, increasing the time between updates can improve system performance. Range: 5 to 240 minutes Default: 20 minutes Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • For more information about ARP updates, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. 1181 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bridge-priority Syntax Hierarchy Level Release Information Description Default Options bridge-priority priority; [edit protocols mstp], [edit protocols mstp msti msti-id], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the bridge priority. The bridge priority determines which bridge is elected as the root bridge. If two bridges have the same path cost to the root bridge, the bridge priority determines which bridge becomes the designated bridge for a LAN segment. 32,768 priority—Bridge priority. It can be set only in increments of 4096. Range: 0 through 61,440 Default: 32,768 Required Privilege Level Related Documentation 1182 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 62: Configuration Statements for Bridging and VLANs customer-vlans Syntax Hierarchy Level Release Information Description Options customer-vlans (id | native | range); [edit vlans vlan-name dot1q-tunneling] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Limit the set of accepted C-VLAN tags to a range or to discrete values. id—Numeric identifier for a VLAN. native—Accepts untagged and priority-tagged packets from access interfaces and assigns the configured S-VLAN to the packet. range—Range of numeric identifiers for VLANs. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • dot1q-tunneling on page 1185 • ether-type on page 1188 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 1183 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS description Syntax Hierarchy Level description text-description; [edit vlans vlan-name] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Option text-description enhanced from supporting up to 128 characters to supporting up to 256 characters in Junos OS Release 10.2 for J-EX Series switches. Description Provide a textual description of the VLAN. The text has no effect on the operation of the VLAN or switch. Options text-description—Text to describe the interface. It can contain letters, numbers, and hyphens (-) and can be up to 256 characters long. If the text includes spaces, enclose the entire text in quotation marks. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 disable Syntax Hierarchy Level Release Information disable; [edit protocols gvrp], [edit protocols gvrp interface [interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. NOTE: GVRP can be enabled only on trunk interfaces. Description Default Required Privilege Level Related Documentation 1184 Disable the GVRP configuration on the interface. If you do not configure GVRP, it is disabled. You can use this command to disable a prior configuration of GVRP on a specified interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show gvrp on page 1253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 Chapter 62: Configuration Statements for Bridging and VLANs disable (MVRP) Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation disable; [edit protocols mvrp], [edit protocols mvrp interface(all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the MVRP configuration on the interface. MVRP is disabled by default. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 dot1q-tunneling (Ethernet Switching) Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation dot1q-tunneling { ether-type (0x8100 | 0x88a8 | 0x9100); } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. The remaining statement is explained separately. Set a global value for the Ethertype for Q-in-Q tunneling. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • dot1q-tunneling on page 1186 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 1185 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dot1q-tunneling (VLANs) Syntax Hierarchy Level Release Information Description dot1q-tunneling { customer-vlans (id | native | range); layer2-protocol-tunneling all | protocol-name { drop-threshold number; shutdown-threshold number; } } [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable Q-in-Q tunneling on the specified VLAN. NOTE: The VLAN on which you enable Q-in-Q tunneling must be a tagged VLAN. The remaining statements are explained separately. Required Privilege Level Related Documentation 1186 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • dot1q-tunneling on page 1185 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 Chapter 62: Configuration Statements for Bridging and VLANs drop-threshold Syntax Hierarchy Level Release Information Description drop-threshold number; [edit vlans vlan-name dot1q-tunneling layer2-protocol-tunneling all | protocol-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the interfaces in a specified VLAN before the switch begins dropping the Layer 2 PDUs. The drop threshold value must be less than or equal to the shutdown threshold value. NOTE: If the drop threshold value is greater than the shutdown threshold value and you try to commit the configuration, the commit will fail. You can specify a drop threshold value without specifying a shutdown threshold value. Default Options No drop threshold is specified. number—Maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the interfaces in a specified VLAN before the switch begins dropping the Layer 2 PDUs. Range: 1 through 1000 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • shutdown-threshold on page 1220 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 1187 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ether-type Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1188 ether-type (0x8100 | 0x88a8 | 0x9100) [edit ethernet-switching-options dot1q-tunneling] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a global value for the Ethertype. Only one Ethertype value is supported at a time. The Ethertype value appears in the Ethernet type field of the packet. It specifies the protocol being transported in the Ethernet frame. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • dot1q-tunneling on page 1186 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 Chapter 62: Configuration Statements for Bridging and VLANs ethernet-switching-options Syntax 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; 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 name { interface interface-name ; interface interface-name; } } secure-access-port { dhcp-snooping-file { location local_pathname | remote_URL; timeout seconds; write-interval seconds; } interface (all | interface-name) { allowed-mac { mac-address-list; } 1189 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS (dhcp-trusted | no-dhcp-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); 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); (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-unknown-unicast; } } 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 ; } } } 1190 Chapter 62: Configuration Statements for Bridging and VLANs Hierarchy Level Release Information Description [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Ethernet switching options. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 1191 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS filter Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation 1192 filter (input | output) filter-name; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a firewall filter to traffic coming into or exiting from the VLAN. All incoming traffic is accepted unmodified to the VLAN, and all outgoing traffic is sent unmodified from the VLAN. filter-name —Name of a firewall filter defined in a filter statement. • input—Apply a firewall filter to VLAN ingress traffic. • output—Apply a firewall filter to VLAN egress traffic. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 Chapter 62: Configuration Statements for Bridging and VLANs group-name Syntax Hierarchy Level Release Information Description Options group-name name { interface interface-name ; interface interface-name; } [edit ethernet-switching-options redundant-trunk-group] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Create a redundant trunk group. name—The name of the redundant trunk group. The group name must start with a letter and can consist of letters, numbers, dashes, and underscores. The remaining options are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 1193 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS gvrp Syntax Hierarchy Level Release Information gvrp { interface [interface-name] { disable; } join-timer milliseconds; leave-timer milliseconds; leaveall-timer milliseconds; } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. NOTE: GVRP can be enabled only on trunk interfaces. Description When GVRP is configured on a trunk interface, it ensures that the VLAN membership information on the trunk interface is updated as the switch’s access interfaces become active or inactive in the configured VLANs. The statements are explained separately. Default Required Privilege Level Related Documentation 1194 GVRP is disabled by default. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show gvrp on page 1253 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 Chapter 62: Configuration Statements for Bridging and VLANs instance-type Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation instance-type virtual-router [edit routing-instances] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the type of routing instance. virtual-router—A logical entity. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 interface Syntax Hierarchy Level Release Information Description Default Options interface (all | [interface-name]) { ; } [edit protocols gvrp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure GARP VLAN Registration Protocol (GVRP) for one or more interfaces. By default, GVRP is disabled. all—All interfaces. interface-name—The list of interfaces to be configured for GVRP. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show gvrp on page 1253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 1195 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface (MVRP) Syntax Hierarchy Level Release Information Description Default Options interface (all | interface-name) { disable; join-timer milliseconds; leave-timer milliseconds; leaveall-timer milliseconds; registration (forbidden | normal); } [edit protocols mvrp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify interfaces on which to configure Multiple VLAN Registration Protocol (MVRP). By default, MVRP is disabled. all—All interfaces on the switch. interface-name—Names of interface to be configured for MVRP. The remaining statements are explained separately. Required Privilege Level Related Documentation 1196 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Chapter 62: Configuration Statements for Bridging and VLANs interface Syntax Hierarchy Level Release Information Description Options interface interface-name ; interface interface-name; [edit ethernet-switching-options redundant-trunk-group group-name name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a primary link and secondary link on trunk ports. If the primary link fails, the secondary link automatically takes over as the primary link without waiting for normal STP convergence. interface interface-name—A logical interface or an aggregated interface containing multiple ports. primary—(Optional) Specify one of the interfaces in the redundant group as the primary link. The interface without this option is the secondary link in the redundant group. If a link is not specified as primary, the software compares the two links and selects the link with the highest port number as the active link. For example, if the two interfaces are ge-0/1/0 and ge-0/1/1, the software assigns ge-0/1/1 as the active link. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 interface Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation interface interface-name; [edit routing-instances] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For virtual routing instances, configure an interface. interface-name—Name of a Gigabit Ethernet interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 • Understanding Virtual Routing Instances on J-EX Series Switches on page 1048 1197 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Options interface interface-name { mapping (native (push | swap) | policy | tag (push | swap)); } [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For a specific VLAN, configure an interface. interface-name—Name of a Gigabit Ethernet interface. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 interfaces Syntax Hierarchy Level Release Information interfaces interface-name { no-mac-learning; } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure settings for interfaces that have been assigned to family ethernet-switching. Options interface-name --Name of an interface that is configured for family ethernet-switching. The remaining statement is explained separately. Required Privilege Level Related Documentation 1198 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 Chapter 62: Configuration Statements for Bridging and VLANs join-timer Syntax Hierarchy Level Release Information Description Default Options join-timer milliseconds; [edit protocols gvrp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For GARP VLAN Registration Protocol (GVRP), configure the maximum number of milliseconds interfaces must wait before sending VLAN advertisements. 20 milliseconds milliseconds —Number of milliseconds. Default: 20 milliseconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show gvrp on page 1253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 1199 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS join-timer (MVRP) Syntax Hierarchy Level Release Information Description join-timer milliseconds; [edit protocols mvrp interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the maximum number of milliseconds interfaces must wait before sending Multiple VLAN Registration Protocol (MVRP) protocol data units (PDUs). Maintain default timer settings unless there is a compelling reason to change the settings. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. Default Options 200 milliseconds milliseconds—Number of milliseconds that the interface must wait before sending MVRP PDUs. Required Privilege Level Related Documentation 1200 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • leave-timer on page 1204 • leaveall-timer on page 1206 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Chapter 62: Configuration Statements for Bridging and VLANs l3-interface Syntax Hierarchy Level Release Information Description Default Options l3-interface vlan.logical-interface-number; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate a Layer 3 interface with the VLAN. Configure Layer 3 interfaces on trunk ports to allow the interface to transfer traffic between multiple VLANs. Within a VLAN, traffic is bridged, while across VLANs, traffic is routed. No Layer 3 (routing) interface is associated with the VLAN. vlan.logical-interface-number—Number of the logical interface defined with a set interfaces vlan unit command. For the logical interface number, use the same number you configure in the unit statement. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show ethernet-switching interfaces on page 997 • show vlans on page 1263 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 1201 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS layer2-protocol-tunneling Syntax Hierarchy Level Release Information Description layer2-protocol-tunneling all | protocol-name { drop-threshold number; shutdown-threshold number; } [edit vlans vlan-name dot1q-tunneling] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable Layer 2 protocol tunneling (L2PT) on the VLAN. The remaining statements are explained separately. Default Options L2PT is not enabled. all—Enable all supported Layer 2 protocols. protocol-name—Name of the Layer 2 protocol. Values are: • 802.1x—IEEE 802.1X authentication • 802.3ah—IEEE 802.3ah Operation, Administration, and Maintenance (OAM) link fault management (LFM) NOTE: If you enable L2PT for untagged OAM LFM packets, do not configure LFM on the corresponding access interface. • cdp—Cisco Discovery Protocol • e-lmi—Ethernet local management interface • gvrp—GARP VLAN Registration Protocol • lacp—Link Aggregation Control Protocol NOTE: If you enable L2PT for untagged LACP packets, do not configure LACP on the corresponding access interface. • llpd—Link Layer Discovery Protocol • mmrp—Multiple MAC Registration Protocol • mvrp—Multiple VLAN Registration Protocol • stp—Spanning Tree Protocol, Rapid Spanning Tree Protocol, and Multiple Spanning Tree Protocol 1202 • vstp—VLAN Spanning Tree Protocol • vtp—VLAN Trunking Protocol Chapter 62: Configuration Statements for Bridging and VLANs Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show ethernet-switching layer2-protocol-tunneling interface on page 1234 • show ethernet-switching layer2-protocol-tunneling statistics on page 1236 • show ethernet-switching layer2-protocol-tunneling vlan on page 1239 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 leave-timer Syntax Hierarchy Level Release Information Description Default Options leave-timer milliseconds; [edit protocols gvrp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For GARP VLAN Registration Protocol (GVRP), configure the number of milliseconds an interface waits after receiving a leave message before the interface leaves the VLAN specified in the message. If the interface receives a join message before the timer expires, the software keeps the interface in the VLAN. 60 centiseconds milliseconds —Number of milliseconds. At a minimum, the leave timer interval should be twice the join timer interval. Default: 60 centiseconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show gvrp on page 1253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 1203 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS leave-timer (MVRP) Syntax Hierarchy Level Release Information Description leave-timer milliseconds; [edit protocols mvrp interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Multiple VLAN Registration Protocol (MVRP), configure the number of milliseconds the switch retains a VLAN in the Leave state before the VLAN is unregistered. If the interface receives a join message before this timer expires, the VLAN remains registered. Maintain default timer settings unless there is a compelling reason to change the settings. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. Default Options 1000 milliseconds milliseconds—Number of milliseconds that the switch retains a VLAN in the Leave state before the VLAN is unregistered. At a minimum, set the leave-timer interval at twice the join-timer interval. Required Privilege Level Related Documentation 1204 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • join-timer on page 1200 • leaveall-timer on page 1206 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Chapter 62: Configuration Statements for Bridging and VLANs leaveall-timer Syntax Hierarchy Level Release Information Description Default Options leaveall-timer milliseconds; [edit protocols gvrp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For GARP VLAN Registration Protocol (GVRP), configure the interval at which Leave All messages are sent on the interfaces. Leave All messages maintain current GVRP VLAN membership information in the network. A Leave All message instructs the port to change the GVRP state for all its VLANs to a leaving state and remove them unless a Join message is received before the leave timer expires. 1000 centiseconds milliseconds —Number of milliseconds. Range: 5 times leave-timer value Default: 1000 centiseconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show gvrp on page 1253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 1205 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS leaveall-timer (MVRP) Syntax Hierarchy Level Release Information Description leaveall-timer milliseconds; [edit protocols mvrp interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Multiple VLAN Registration Protocol (MVRP), configure the interval at which the LeaveAll state operates on the interface. Maintain default timer settings unless there is a compelling reason to change the settings. Modifying timers to inappropriate values might cause an imbalance in the operation of MVRP. Default Options Required Privilege Level Related Documentation 1206 10000 milliseconds milliseconds—Number of milliseconds between the sending of Leave All messages. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • join-timer on page 1200 • leave-timer on page 1204 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Chapter 62: Configuration Statements for Bridging and VLANs mac-limit Syntax Hierarchy Level Release Information Description mac-limit number; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the number of MAC addresses allowed on a VLAN. The number of MAC addresses allowed per VLAN varies between J-EX switches. The output of the set vlans vlan-name mac-limit ? provides the number of MAC addresses allowed on your J-EX switch. Default MAC limit is disabled. Options number—Maximum number of MAC addresses. Range: 1 through 32768. NOTE: Do not set mac-limit to 1. The first learned MAC address is often inserted into the forwarding database automatically (for instance, for routed VLAN Interfaces (RVIs), the first MAC address inserted into the forwarding database is the MAC address of the RVI. For aggregated Ethernet bundles using LACP, the first MAC address inserted into the forwarding database in the forwarding table is the source address of the protocol packet). The switch will therefore not learn MAC addresses other than the automatic addresses when the mac-limit is set to 1, and this will cause problems with MAC learning and forwarding. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Configuring MAC Table Aging (CLI Procedure) on page 1138 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 1207 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mac-notification Syntax Hierarchy Level Release Information Description mac-notification { notification-interval seconds; } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable MAC notification for a switch. If you configure this statement without setting a notification interval, MAC notification is enabled with the default MAC notification interval of 30 seconds. The remaining statement is explained separately. Default Required Privilege Level Related Documentation 1208 MAC notification is disabled by default. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring MAC Notification (CLI Procedure) on page 1151 Chapter 62: Configuration Statements for Bridging and VLANs mac-table-aging-time Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation mac-table-aging-time seconds; [edit ethernet-switching-options], [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define how long entries remain in the Ethernet switching table before expiring: • If you specify this statement at the [edit ethernet-switching-options] hierarchy level, it applies to all VLANs on the switch. • If you specify this statement at the [edit vlans] hierarchy level, it applies to the specified VLAN. Entries remain in the Ethernet switching table for 300 seconds seconds—Time that entries remain in the Ethernet switching table before being removed. • Range—60 through 1,000,000 seconds • Default—300 seconds routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show ethernet-switching statistics aging on page 1244 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Configuring MAC Table Aging (CLI Procedure) on page 1138 • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 1209 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mapping Syntax Hierarchy Level Release Information Description mapping (native (push | swap) | policy | tag (push | swap)); [edit vlans vlan-name interface interface-name ingress]: [edit vlans vlan-name interface interface-name egress]: [edit vlans vlan-name interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Map a specific C-VLAN to an S-VLAN. By default, the received incoming or outgoing tag is replaced with the new tag. This statement is also required if you are configuring firewall filters to map traffic from an interface to a VLAN. If you are configuring firewall filters to map traffic from an interface to a VLAN, the mapping policy option must be configured using this command. The firewall filter also has to be configured using the vlan action for a match condition in the firewall filter stanza for firewall filters to map traffic from an interface for a VLAN. Options native—Maps untagged and priority-tagged packets to an S-VLAN. policy—Maps the interface to a firewall filter policy to an S-VLAN. push—Retains the incoming tag and add an additional VLAN tag instead of replacing the original tag. swap—Swaps the incoming VLAN tag with the VLAN ID tag of the S-VLAN. Use of this option is also referred to as VLAN ID translation. tag—Retains the incoming 802.1Q tag on the interface. Required Privilege Level Related Documentation 1210 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Chapter 62: Configuration Statements for Bridging and VLANs members Syntax Hierarchy Level Release Information Description members [ (all | names | vlan-ids) ]; [edit interfaces interface-name unit logical-unit-number family ethernet-switching vlan] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For trunk interfaces, configure the VLANs for which the interface can carry traffic. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Options all—Specifies that this trunk interface is a member of all the VLANs that are configured on this switch. When a new VLAN is configured on the switch, this trunk interface automatically becomes a member of the VLAN. NOTE: Each VLAN that is configured must have a specified VLAN ID when you attempt to commit the configuration; otherwise, the configuration commit fails. Also, all cannot be the name of a VLAN on the switch. names—Name of one or more VLANs. vlan-ids—Numeric identifier of one or more VLANs. For a series of tagged VLANs, specify a range; for example, 10-20 or 10-20 23 27-30. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • show ethernet-switching interfaces on page 997 • show vlans on page 1263 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Creating a Series of Tagged VLANs (CLI Procedure) on page 1140 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 1211 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mvrp Syntax Hierarchy Level Release Information Description 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; } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Multiple VLAN Registration Protocol (MVRP) on a trunk interface to ensure that the VLAN membership information on the trunk interface is updated as the switch’s access interfaces become active or inactive in the configured VLANs. The remaining statements are explained separately. Default Required Privilege Level Related Documentation 1212 MVRP is disabled by default. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 Chapter 62: Configuration Statements for Bridging and VLANs native-vlan-id Syntax Hierarchy Level Release Information Description Options native-vlan-id vlan-id; [edit interfaces interface-name unit 0 family ethernet-switching] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the VLAN identifier to associate with untagged packets received on the interface. vlan-id—Numeric identifier of the VLAN. Range: 0 through 4095 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • show ethernet-switching interfaces on page 997 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 1213 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-dynamic-vlan Syntax Hierarchy Level Release Information Description no-dynamic-vlan; [edit protocols mvrp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the dynamic creation of VLANs using Multiple VLAN Registration Protocol (MVRP) for interfaces participating in MVRP. Dynamic VLAN configuration can be enabled on an interface independent of MVRP. The MVRP dynamic VLAN configuration setting does not override the interface configuration dynamic VLAN configuration setting. If dynamic VLAN creation is disabled on the interface in the interface configuration, no dynamic VLANs are created on the interface, including dynamic VLANs created using MVRP. This option can only be applied globally; it cannot be applied per interface. Default Required Privilege Level Related Documentation If MVRP is enabled, the dynamic creation of VLANs as a result of MVRP protocol exchange messages is enabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 no-local-switching Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1214 no-local-switching [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify that access ports in this VLAN domain do not forward packets to each other. You use this statement with primary VLANs and isolated secondary VLANs. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 • Creating a Private VLAN (CLI Procedure) on page 1143 Chapter 62: Configuration Statements for Bridging and VLANs no-mac-learning Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation no-mac-learning; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disables MAC address learning for the specified VLAN. There are no options to this statement. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 no-mac-learning Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation no-mac-learning; [edit ethernet-switching-options interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable MAC address learning for the specified interface. Disabling MAC address learning on an interface disables learning for all the VLANs of which that interface is a member. There are no options to this statement. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 1215 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS notification-interval Syntax Hierarchy Level Release Information Description notification-interval seconds; [edit ethernet-switching-options mac-notification] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the MAC notification interval for a switch. The MAC notification interval is the amount of time the switch waits before sending learned or unlearned MAC address SNMP notifications to the network management server. For instance, if the MAC notification interval is set to 10, all of the MAC address addition and removal SNMP notifications will be sent to the network management system every 10 seconds. Options seconds—The MAC notification interval, in seconds. Range: 1 through 60 Default: 30 Required Privilege Level Related Documentation 1216 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring MAC Notification (CLI Procedure) on page 1151 Chapter 62: Configuration Statements for Bridging and VLANs port-mode Syntax Hierarchy Level Release Information Description Default Options port-mode mode; [edit interfaces interface-name unit logical-unit-number family ethernet-switching] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether an interface on the switch operates in access or trunk mode. All switch interfaces are in access mode. access—Have the interface operate in access mode. In this mode, the interface can be in a single VLAN only. Access interfaces typically connect to network devices such as PCs, printers, IP telephones, and IP cameras. trunk—Have the interface operate in trunk mode. In this mode, the interface can be in multiple VLANs and can multiplex traffic between different VLANs. Trunk interfaces typically connect to other switches and to routers on the LAN. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Connecting an Access Switch to a Distribution Switch on page 1078 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 1217 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS primary-vlan Syntax Hierarchy Level Release Information Description primary-vlan vlan-name [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the primary VLAN for this community VLAN. The primary VLAN must be tagged, and the community VLAN must be untagged. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 • Creating a Private VLAN (CLI Procedure) on page 1143 redundant-trunk-group Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1218 redundant-trunk-group { group-name name { interface interface-name ; interface interface-name; } } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a primary link and secondary link on trunk ports. If the primary link fails, the secondary link automatically takes over without waiting for normal STP convergence. The statements are explained separately. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 Chapter 62: Configuration Statements for Bridging and VLANs registration Syntax Hierarchy Level Release Information Description Default Options registration (forbidden | normal); [edit protocols mvrp interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specifies the Multiple VLAN Registration Protocol (MVRP) registration mode for the interface if MVRP is enabled. normal forbidden—The interface or interfaces do not register and do not participate in MVRP. normal—The interface or interfaces accept MVRP messages and participate in MVRP. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Multiple VLAN Registration Protocol (MVRP) (CLI Procedure) on page 1147 routing-instances Syntax Hierarchy Level Release Information Description Options routing-instances routing-instance-name { instance-type virtual-router; interface interface-name; } [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a virtual routing entity. routing-instance-name—Name for this routing instance. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Using Virtual Routing Instances to Route Among VLANs on J-EX Series Switches on page 1112 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 1219 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS shutdown-threshold Syntax Hierarchy Level Release Information Description shutdown-threshold number; [edit vlans vlan-name dot1q-tunneling layer2-protocol-tunneling all | protocol-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the interfaces in a specified VLAN before the interface is disabled. Once an interface is disabled, you must explicitly reenable it using the clear ethernet-switching layer2-protocol-tunneling error command. Otherwise, the interface remains disabled. The shutdown threshold value must be greater than or equal to the drop threshold value. If the shutdown threshold value is less than the drop threshold value, the drop threshold value has no effect. You can specify a shutdown threshold value without specifying a drop threshold value. Default Options No shutdown threshold is specified. number—Maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the interfaces in a specified VLAN before the interface is disabled. Range: 1 through 1000 Required Privilege Level Related Documentation 1220 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • drop-threshold on page 1187 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 Chapter 62: Configuration Statements for Bridging and VLANs vlan Syntax Hierarchy Level Release Information Description vlan { members [ (all | names | vlan-ids) ]; } [edit interfaces interface-name unit logical-unit-number family ethernet-switching] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Bind an 802.1Q VLAN tag ID to a logical interface. The remaining statement is explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • show ethernet-switching interfaces on page 997 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ vlan-id Syntax Hierarchy Level Release Information Description Default Options vlan-id number; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an 802.1Q tag to apply to all traffic that originates on the VLAN. If you use the default factory configuration, all traffic originating on the VLAN is untagged and has a VLAN identifier of 0. number —VLAN tag identifier. Range: 0 through 4093. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 1221 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan-range Syntax Hierarchy Level Release Information Description Default Options vlan-range vlan-id-low-vlan-id-high; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range. None. vlan-id-low-vlan-id-high —Specify the first and last VLAN ID number for the group of VLANs. Required Privilege Level Related Documentation 1222 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Configuring VLANs for J-EX Series Switches (J-Web Procedure) on page 1133 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 Chapter 62: Configuration Statements for Bridging and VLANs vlans Syntax Hierarchy Level Release Information Description Default Options vlans { vlan-name { description text-description; dot1q-tunneling { customer-vlans (id | 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)); } 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; } } [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure VLAN properties on J-EX Series switches. The following configuration guidelines apply: • Only private VLAN (PVLAN) firewall filters can be used when the VLAN is enabled for Q-in-Q tunneling. • An S-VLAN tag is added to the packet if the VLAN is dot1q-tunneled and the packet is arriving from an access interface. • You cannot use a firewall filter to assign a routed VLAN interface (RVI) to a VLAN. • VLAN assignments performed using a firewall filter override all other VLAN assignments. If you use the default factory configuration, all switch interfaces become part of the VLAN default. vlan-name—Name of the VLAN. The name can contain letters, numbers, hyphens (-), and periods (.) and can be up to 255 characters long. The remaining statements are explained separately. 1223 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation 1224 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Configuring VLANs for J-EX Series Switches (J-Web Procedure) on page 1133 • Configuring Q-in-Q Tunneling (CLI Procedure) on page 1144 • Creating a Series of Tagged VLANs (CLI Procedure) on page 1140 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 CHAPTER 63 Operational Mode Commands for Bridging and VLANs 1225 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear ethernet-switching layer2-protocol-tunneling error Syntax Release Information Description Options clear ethernet-switching layer2-protocol-tunneling error Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Layer 2 protocol tunneling (L2PT) errors on one or more interfaces. If an interface has been disabled because the amount of Layer 2 protocol traffic exceeded the shutdown-threshold or because the switch has detected an error in the network topology or configuration, use this command to reenable the interface. none—Clears L2PT errors on all interfaces. interface interface-name—(Optional) Clear L2PT errors on the specified interface. Required Privilege Level Related Documentation view • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 List of Sample Output clear ethernet-switching layer2-protocol-tunneling error on page 1226 clear ethernet-switching layer2-protocol-tunneling error interface ge-0/1/1.0 on page 1226 clear ethernet-switching layer2-protocol-tunneling error user@switch> clear ethernet-switching layer2-protocol-tunneling error clear ethernet-switching layer2-protocol-tunneling error interface ge-0/1/1.0 user@switch> clear ethernet-switching layer2-protocol-tunneling error interface ge-0/1/1.0 1226 Chapter 63: Operational Mode Commands for Bridging and VLANs clear ethernet-switching layer2-protocol-tunneling statistics Syntax Release Information Description Options clear ethernet-switching layer2-protocol-tunneling statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Layer 2 protocol tunneling (L2PT) statistics on one or more interfaces or VLANs. none—Clear L2PT statistics on all interfaces and VLANs. interface interface-name—(Optional) Clear L2PT statistics on the specified interface. vlan vlan-name—(Optional) Clear L2PT statistics on the specified VLAN. Required Privilege Level Related Documentation view • show ethernet-switching layer2-protocol-tunneling statistics on page 1236 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 List of Sample Output clear ethernet-switching layer2-protocol-tunneling statistics on page 1227 clear ethernet-switching layer2-protocol-tunneling error interface ge-0/1/1.0 on page 1227 clear ethernet-switching layer2-protocol-tunneling error vlan v2 on page 1227 clear ethernet-switching layer2-protocol-tunneling statistics user@switch> clear ethernet-switching layer2-protocol-tunneling statistics clear ethernet-switching layer2-protocol-tunneling error interface ge-0/1/1.0 user@switch> clear ethernet-switching layer2-protocol-tunneling statistics interface ge-0/1/1.0 clear ethernet-switching layer2-protocol-tunneling error vlan v2 user@switch> clear ethernet-switching layer2-protocol-tunneling statistics vlan v2 1227 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear ethernet-switching table Syntax Release Information Description Options clear ethernet-switching table Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear learned entries, which are media access control (MAC) addresses, in the Ethernet switching table (also called the forwarding database table). none—Clear learned entries in the Ethernet switching table. interface interface-name—(Optional) Clear all learned MAC addresses for the specified interface from the Ethernet switching table. mac mac-address—(Optional) Clear the specified learned MAC address from the Ethernet switching table. management-vlan—(Optional) Clear all MAC addresses learned for the management VLAN from the Ethernet switching table. Note that you do not specify a VLAN name because only one management VLAN exists. vlan vlan-name—(Optional) Clear all MAC addresses learned for the specified VLAN from the Ethernet switching table. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ethernet-switching table 1228 view • show ethernet-switching table on page 1249 clear ethernet-switching table on page 1228 This command produces no output. user@host> clear ethernet-switching table Chapter 63: Operational Mode Commands for Bridging and VLANs clear gvrp statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output clear gvrp statistics clear gvrp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear GARP VLAN Registration Protocol (GVRP) statistics. clear • show spanning-tree statistics on page 1416 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 clear gvrp statistics on page 1229 user@switch> clear gvrp statistics 1229 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear mvrp statistics Syntax Release Information Description Options clear mvrp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Multiple VLAN Registration Protocol (MVRP) statistics. none—Clear all MVRP statistics. interface interface-name—Clear the MVRP statistics on the specified interface. Required Privilege Level Related Documentation List of Sample Output Output Fields clear • show mvrp statistics on page 1260 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 clear mvrp statistics on page 1230 clear mvrp statistics interface ge-0/0/1.0 on page 1230 When you enter this command, you are provided feedback on the status of your request. clear mvrp statistics user@switch> clear mvrp statistics clear mvrp statistics interface ge-0/0/1.0 user@switch> clear mvrp statistics interface ge-0/0/1.0 1230 Chapter 63: Operational Mode Commands for Bridging and VLANs show ethernet-switching interfaces Syntax Release Information Description Options show ethernet-switching interfaces Command introduced before Junos OS Release 10.2 for J-EX Series switches. • Blocking field output updated. • The default view updated to include information about 802.1Q-tags. • The detail view updated to include information VLAN mapping. Display information about switched Ethernet interfaces. none—(Optional) Display brief information for Ethernet switching interfaces. brief | detail | summary—(Optional) Display the specified level of output. interface interface-name—(Optional) Display Ethernet switching information for a specific interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ethernet-switching mac-learning-log on page 1241 • show ethernet-switching table on page 1249 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 show ethernet-switching interfaces on page 1232 show ethernet-switching interfaces ge-0/0/15 brief on page 1233 show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) on page 1233 show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) on page 1233 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) on page 1233 show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) on page 1233 Table 155 on page 1232 lists the output fields for the show ethernet-switching interfaces command. Output fields are listed in the approximate order in which they appear. 1231 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 155: show ethernet-switching interfaces Output Fields Field Name Field Description Level of Output Interface Name of a switching interface. All levels State Interface state. Values are up and down. none, brief, detail, summary VLAN members Name of a VLAN. none, brief, detail, summary Tag Number of the 802.1Q-tag. All levels Tagging Specifies whether the interface forwards 802.1Q-tagged or untagged traffic. All levels Blocking The forwarding state of the interface: none, brief, detail, summary • unblocked—Traffic is forwarded on the interface. • blocked—Traffic is not being forwarded on the interface. • Disabled by bpdu control—The interface is disabled due to receiving BPDUs on a protected interface. If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. • blocked by RTG—The specified redundant trunk group is disabled. • blocked by STP—The interface is disabled due to a spanning tree protocol error. • MAC limit exceeded—The interface is temporarily disabled due to a MAC limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • MAC move limit exceeded—The interface is temporarily disabled due to a MAC move limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • Storm control in effect—The interface is temporarily disabled due to a storm control error. The disabled interface is automatically restored to service when the disable timeout expires. Index The VLAN index internal to Junos OS. detail mapping The C-VLAN to S-VLAN mapping information: detail • dot1q-tunneled—The interface maps all traffic to the S-VLAN (all-in-one bundling). • native—The interface maps untagged and priority tagged packets to the S-VLAN. • push—The interface maps packets to a firewall filter to an S-VLAN. • policy-mapped—The interface maps packets to a specifically defined S-VLAN. • integer—The interface maps packets to the specified S-VLAN. show ethernet-switching interfaces 1232 user@switch> show ethernet-switching interfaces Interface State VLAN members Tag Tagging Blocking Chapter 63: Operational Mode Commands for Bridging and VLANs ae0.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 ge-0/0/6.0 ge-0/0/7.0 ge-0/0/13.0 ge-0/0/14.0 up up up down down down down up up ge-0/0/15.0 up ge-0/0/16.0 ge-0/0/17.0 down down default vlan300 default default default default default default vlan100 vlan200 vlan100 vlan200 default vlan100 300 100 200 100 200 100 vlan200 show ethernet-switching interfaces ge-0/0/15 brief show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) 200 untagged unblocked untagged blocked by RTG (rtggroup) blocked by STP MAC limit exceeded MAC move limit exceeded Storm control in effect unblocked untagged unblocked tagged unblocked tagged unblocked tagged blocked by STP tagged blocked by STP untagged unblocked tagged Disabled by bpdu-control tagged Disabled by bpdu-control user@switch> show ethernet-switching interfaces ge-0/0/15 brief Interface State VLAN members Tag Tagging Blocking ge-0/0/15.0 up vlan100 vlan200 100 200 tagged tagged blocked by STP blocked by STP user@switch> show ethernet-switching interfaces ge-0/0/2 detail Interface: ge-0/0/2.0, Index: 65, State: up, Port mode: Access VLAN membership: vlan300, 802.1Q Tag: 300, untagged, msti-id: 0, blocked by RTG(rtggroup) Number of MACs learned on IFL: 0 user@switch> show ethernet-switching interfaces ge-0/0/15 detail Interface: ge-0/0/15.0, Index: 70, State: up, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 0, blocked by STP vlan200, 802.1Q Tag: 200, tagged, msti-id: 0, blocked by STP Number of MACs learned on IFL: 0 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) user@switch> show ethernet-switching interfaces ge-0/0/17 detail show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) user@switch>show ethernet-switching interfaces ge-0/0/6.0 detail Interface: ge-0/0/6.0, Index: 73, State: up, Port mode: Access VLAN membership: map, 802.1Q Tag: 134, Mapped Tag: native, push, dot1q-tunneled, unblocked map, 802.1Q Tag: 134, Mapped Tag: 20, push, dot1q-tunneled, unblocked Interface: ge-0/0/17.0, Index: 71, State: down, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 1, Disabled by bpdu-control vlan200, 802.1Q Tag: 200, tagged, msti-id: 2, Disabled by bpdu-control Number of MACs learned on IFL: 0 1233 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching layer2-protocol-tunneling interface Syntax Release Information Description Options show ethernet-switching-layer2-protocol-tunneling interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Layer 2 protocol tunneling (L2PT) on interfaces that have been configured for L2PT. none—Display L2PT information about all interfaces on which L2PT is enabled. interface-name—(Optional) Display L2PT information for the specified interface. Required Privilege Level Related Documentation view • show ethernet-switching layer2-protocol-tunneling statistics on page 1236 • show ethernet-switching layer2-protocol-tunneling vlan on page 1239 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 List of Sample Output show ethernet-switching layer2-protocol-tunneling interface on page 1234 show ethernet-switching layer2-protocol-tunneling interface ge-0/0/0.0 on page 1235 Output Fields Table 156 on page 1234 lists the output fields for the show ethernet-switching layer2-protocol-tunneling interface command. Output fields are listed in the approximate order in which they appear. Table 156: show ethernet-switching layer2-protocol-tunneling interface Output Fields Field Name Field Description Interface Name of an interface on the switch. Operation Type of operation being performed on the interface. Values are Encapsulation and Decapsulation. State State of the interface. Values are active and shutdown. Description If the interface state is shutdown, displays why the interface is shut down. If the description says Loop detected, it means that the interface is an access interface that has received L2PT-enabled PDUs. Access interfaces should not receive L2PT-enabled PDUs. This scenario might mean that there is a loop in the network. show ethernet-switching layer2-protocol-tunneling interface 1234 user@switch> show ethernet-switching layer2-protocol-tunneling interface Layer2 Protocol Tunneling information: Interface Operation State ge-0/0/0.0 Encapsulation Shutdown Description Shutdown threshold exceeded Chapter 63: Operational Mode Commands for Bridging and VLANs ge-0/0/1.0 ge-0/0/2.0 show ethernet-switching layer2-protocol-tunneling interface ge-0/0/0.0 Decapsulation Decapsulation Shutdown Active Loop detected user@switch> show ethernet-switching layer2-protocol-tunneling interface ge-0/0/0.0 Layer2 Protocol Tunneling information: Interface Operation State ge-0/0/0.0 Encapsulation Shutdown Description Shutdown threshold exceeded 1235 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching layer2-protocol-tunneling statistics Syntax Release Information Description show ethernet-switching-layer2-protocol-tunneling statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Layer 2 protocol tunneling (L2PT) statistics for Layer 2 PDU packets received by the switch. NOTE: The show ethernet-switching-layer2-protocol-tunneling statistics command does not display L2PT statistics for Layer 2 PDU packets transmitted from the switch. Options none—Display L2PT statistics for all interfaces on which you enabled L2PT. —(Optional) Display L2PT statistics for the specified interface. —(Optional) Display L2PT statistics for the specified VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear ethernet-switching layer2-protocol-tunneling statistics on page 1227 • show ethernet-switching layer2-protocol-tunneling interface on page 1234 • show ethernet-switching layer2-protocol-tunneling vlan on page 1239 • show vlans on page 1263 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 show ethernet-switching layer2-protocol-tunneling statistics on page 1237 show ethernet-switching layer2-protocol-tunneling statistics interface ge-0/0/0.0 on page 1237 show ethernet-switching layer2-protocol-tunneling statistics vlan v2 on page 1237 Table 157 on page 1236 lists the output fields for the show ethernet-switching layer2-protocol-tunneling statistics command. Output fields are listed in the approximate order in which they appear. Table 157: show ethernet-switching layer2-protocol-tunneling statistics Output Fields VLAN Field Description VLAN Name of a VLAN on which L2PT has been configured. 1236 Chapter 63: Operational Mode Commands for Bridging and VLANs Table 157: show ethernet-switching layer2-protocol-tunneling statistics Output Fields (continued) VLAN Field Description Interface Name of an interface on which L2PT has been configured. Protocol Name of a protocol for which L2PT has been enabled. Values are all, 802.1x, 802.3ah, cdp, e-lmi, gvrp, lacp, lldp, mmrp, mvrp, stp, vstp, and vtp. Operation Type of operation being performed on the interface. Values are Encapsulation and Decapsulation. Packets Number of packets that have been encapsulated or decapsulated. Drops Number of packets that have exceeded the drop threshold and have been dropped. Shutdowns Number of times that packets have exceeded the shutdown threshold and the interface has been shut down. show ethernet-switching layer2-protocol-tunneling statistics user@switch> show ethernet-switching layer2-protocol-tunneling statistics show ethernet-switching layer2-protocol-tunneling statistics interface ge-0/0/0.0 user@switch> show ethernet-switching layer2-protocol-tunneling statistics interface ge-0/0/0.0 show ethernet-switching layer2-protocol-tunneling statistics vlan v2 user@switch> show ethernet-switching layer2-protocol-tunneling statistics vlan v2 Layer2 VLAN v1 v1 v1 v2 v2 v2 Protocol Tunneling Statistics: Interface Protocol Operation ge-0/0/0.0 mvrp Encapsulation ge-0/0/1.0 mvrp Decapsulation ge-0/0/2.0 mvrp Decapsulation ge-0/0/0.0 cdp Encapsulation ge-0/0/0.0 gvrp Encapsulation ge-0/0/0.0 lldp Encapsulation Layer2 Protocol Tunneling Statistics: VLAN Interface Protocol Operation v1 ge-0/0/0.0 mvrp Encapsulation v2 ge-0/0/0.0 cdp Encapsulation v2 ge-0/0/0.0 gvrp Encapsulation v2 ge-0/0/0.0 lldp Encapsulation v2 ge-0/0/0.0 mvrp Encapsulation v2 ge-0/0/0.0 stp Encapsulation v2 ge-0/0/0.0 vtp Encapsulation v2 ge-0/0/0.0 vstp Encapsulation Packets 0 0 60634 0 0 0 Layer2 Protocol Tunneling Statistics: VLAN Interface Protocol Operation v2 ge-0/0/0.0 cdp Encapsulation v2 ge-0/0/0.0 gvrp Encapsulation v2 ge-0/0/0.0 lldp Encapsulation v2 ge-0/0/0.0 mvrp Encapsulation v2 ge-0/0/0.0 stp Encapsulation v2 ge-0/0/0.0 vtp Encapsulation v2 ge-0/0/0.0 vstp Encapsulation v2 ge-0/0/1.0 cdp Decapsulation v2 ge-0/0/1.0 gvrp Decapsulation v2 ge-0/0/1.0 lldp Decapsulation Drops 0 0 0 0 0 0 Packets 0 0 0 0 0 0 0 0 Packets 0 0 0 0 0 0 0 0 0 0 Drops 0 0 0 0 0 0 0 0 Drops 0 0 0 0 0 0 0 0 0 0 Shutdowns 0 0 0 0 0 0 Shutdowns 0 0 0 0 0 0 0 0 Shutdowns 0 0 0 0 0 0 0 0 0 0 1237 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS v2 v2 v2 1238 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 mvrp stp vtp Decapsulation Decapsulation Decapsulation 0 0 0 0 0 0 0 0 0 Chapter 63: Operational Mode Commands for Bridging and VLANs show ethernet-switching layer2-protocol-tunneling vlan Syntax Release Information Description Options show ethernet-switching-layer2-protocol-tunneling vlan Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Layer 2 protocol tunneling (L2PT) on VLANs that have been configured for L2PT. none—Display information about L2PT for the VLANs on which you have configured L2PT. vlan-name—(Optional) Display information about L2PT for the specified VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ethernet-switching layer2-protocol-tunneling interface on page 1234 • show ethernet-switching layer2-protocol-tunneling statistics on page 1236 • show vlans on page 1263 • Example: Configuring Layer 2 Protocol Tunneling on J-EX Series Switches on page 1126 • Configuring Layer 2 Protocol Tunneling on J-EX Series Switches (CLI Procedure) on page 1150 show ethernet-switching layer2-protocol-tunneling vlan on page 1239 show ethernet-switching layer2-protocol-tunneling vlan v2 on page 1240 Table 158 on page 1239 lists the output fields for the show ethernet-switching layer2-protocol-tunneling vlan command. Output fields are listed in the approximate order in which they appear. Table 158: show ethernet-switching layer2-protocol-tunneling vlan Output Fields Field Name Field Description VLAN Name of the VLAN on which L2PT has been configured. Protocol Name of a protocol for which L2PT has been enabled. Values are all, 802.1x, 802.3ah, cdp, e-lmi, gvrp, lacp, lldp, mmrp, mvrp, stp, vstp, and vtp. Drop Threshold Maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the VLAN before the switch begins dropping the Layer 2 PDUs. Shutdown Threshold Maximum number of Layer 2 PDUs of the specified protocol that can be received per second on the VLAN before the interface is disabled. show ethernet-switching user@switch> show ethernet-switching layer2-protocol-tunneling vlan Layer2 Protocol Tunneling VLAN information: 1239 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS layer2-protocol-tunneling vlan VLAN Protocol v1 v2 v2 v2 mvrp cdp cdp gvrp show ethernet-switching layer2-protocol-tunneling vlan v2 user@switch> show ethernet-switching layer2-protocol-tunneling vlan v2 1240 Drop Threshold 100 0 0 0 Shutdown Threshold 200 0 0 0 Layer2 Protocol Tunneling VLAN information: VLAN Protocol Drop Shutdown Threshold Threshold v2 cdp 0 0 v2 cdp 0 0 v2 gvrp 0 0 Chapter 63: Operational Mode Commands for Bridging and VLANs show ethernet-switching mac-learning-log Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show ethernet-switching mac-learning-log Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays the event log of learned MAC addresses. view • show ethernet-switching table on page 1249 • show ethernet-switching interfaces on page 997 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Connecting an Access Switch to a Distribution Switch on page 1078 show ethernet-switching mac-learning-log on page 1241 Table 159 on page 1241 lists the output fields for the show ethernet-switching mac-learning-log command. Output fields are listed in the approximate order in which they appear. Table 159: show ethernet-switching mac-learning-log Output Fields Field Name Field Description Date and Time Timestamp when the MAC address was added or deleted from the log. vlan_name VLAN name. A value defined by the user for all user-configured VLANs. MAC Learned MAC address. Deleted | Added MAC address deleted or added to the MAC learning log. Blocking The forwarding state of the interface: • blocked—Traffic is not being forwarded on the interface. • unblocked—Traffic is forwarded on the interface. show ethernet-switching mac-learning-log user@switch> show ethernet-switching mac-learning-log Mon Feb 25 08:07:05 2008 vlan_name v1 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name v9 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name HR_vlan mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 1241 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan_name v3 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name v12 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name v13 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name sales_vlan mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name employee1 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name employee2 mac 00:00:00:00:00:00 was deleted Mon Feb 25 08:07:05 2008 vlan_name v3 mac 00:00:00:00:00:00 was added Mon Feb 25 08:07:05 2008 vlan_name HR_vlan mac 00:00:00:00:00:00 was added Mon Feb 25 08:07:05 2008 vlan_name employee2 mac 00:00:00:00:00:00 was added Mon Feb 25 08:07:05 2008 vlan_name employee1 mac 00:00:00:00:00:00 was added Mon Feb 25 08:07:05 2008 vlan_name employee2 mac 00:00:05:00:00:05 was learned Mon Feb 25 08:07:05 2008 vlan_name employee1 mac 00:30:48:90:54:89 was learned Mon Feb 25 08:07:05 2008 vlan_name HR_vlan mac 00:00:5e:00:01:00 was learned Mon Feb 25 08:07:05 2008 vlan_name sales_vlan mac 00:00:5e:00:01:08 was learned [output truncated] 1242 Chapter 63: Operational Mode Commands for Bridging and VLANs show ethernet-switching mac-notification Syntax Release Information Description Required Privilege Level Related Documentation Output Fields show ethernet-switching mac-notification Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about MAC notification. view • Verifying That MAC Notification Is Working Properly on page 1163 Table 160 on page 1243 lists the output fields for the show ethernet-switching mac-notification command. Output fields are listed in the order in which they appear. Table 160: show ethernet-switching mac-notification Output Fields Field Name Field Description Notification Status Displays the MAC notification status: Notification Interval • Enabled—MAC notification is enabled. • Disabled—MAC notification is disabled. Displays the MAC notification interval in seconds. show ethernet-switching mac-notification (MAC Notification Enabled) user@switch> show ethernet-switching mac-notification Notification Status : Enabled Notification Interval : 30 show ethernet-switching mac-notification (MAC Notification Disabled) user@switch> show ethernet-switching mac-notification Notification Status : Disabled Notification Interval : 0 1243 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching statistics aging Syntax Release Information Description Options show ethernet-switching statistics aging Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display media access control (MAC) aging statistics. none—(Optional) Display MAC aging statistics. brief | detail—(Optional) Display the specified level of output. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ethernet-switching statistics mac-learning on page 1246 • Configuring MAC Table Aging (CLI Procedure) on page 1138 show ethernet-switching statistics aging on page 1244 Table 161 on page 1244 lists the output fields for the show ethernet-switching statistics aging command. Output fields are listed in the approximate order in which they appear. Table 161: show ethernet-switching statistics aging Output Fields Field Name Field Description Level of Output Total age messages received Total number of aging messages received from the hardware. All levels Immediate aging Aging message indicating that the entry should be removed immediately. All levels MAC address seen Aging message indicating that the MAC address has been detected by hardware and that the aging timer should be stopped. All levels MAC address not seen Aging message indicating that the MAC address has not been detected by the hardware and that the aging timer should be started. All levels Error age messages The received aging message contains the following errors: All levels • Invalid VLAN—The VLAN of the packet does not exist. • No such entry—The MAC address and VLAN pair provided by the aging message does not exist. • Static entry—An unsuccessful attempt was made to age out a static MAC entry. show ethernet-switching statistics aging 1244 user@switch> show ethernet-switching statistics aging Total age messages received: 0 Immediate aging: 0, MAC address seen: 0, MAC address not seen: 0 Chapter 63: Operational Mode Commands for Bridging and VLANs Error age messages: 0 Invalid VLAN: 0, No such entry: 0, Static entry: 0 1245 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching statistics mac-learning Syntax Release Information Description Options show ethernet-switching statistics mac-learning Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display media access control (MAC) learning statistics. none—(Optional) Display MAC learning statistics for all interfaces. brief | detail—(Optional) Display the specified level of output. interface interface-name —(Optional) Display MAC learning statistics for the specified interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ethernet-switching statistics aging on page 1244 • show ethernet-switching mac-learning-log on page 1241 • show ethernet-switching table on page 1249 • show ethernet-switching interfaces on page 997 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 show ethernet-switching statistics mac-learning on page 1247 show ethernet-switching statistics mac-learning detail on page 1247 show ethernet-switching statistics mac-learning interface ge-0/0/1 on page 1248 Table 162 on page 1246 lists the output fields for the show ethernet-switching statistics mac-learning command. Output fields are listed in the approximate order in which they appear. Table 162: show ethernet-switching statistics mac-learning Output Fields Field Name Field Description Level of Output Interface Name of the interface for which statistics are being reported. All levels Learning message from local packets MAC learning message generated due to packets coming in on the management interface. All levels Learning message from transit packets MAC learning message generated due to packets coming in on network interfaces. All levels 1246 Chapter 63: Operational Mode Commands for Bridging and VLANs Table 162: show ethernet-switching statistics mac-learning Output Fields (continued) Field Name Field Description Level of Output Learning message with error MAC learning messages received with errors: All levels • Invalid VLAN—The VLAN of the packet does not exist. • Invalid MAC—The MAC address is either NULL or a multicast MAC address. • Security violation—The MAC address is not an allowed MAC address. • Interface down—The MAC address is learned on an interface that is down. • Incorrect membership—The MAC address is learned on an interface that is not a member of the VLAN. • Interface limit—The number of MAC addresses learned on the interface has exceeded the limit. • MAC move limit—This MAC address has moved among multiple interfaces too many times in a given interval. • VLAN limit—The number of MAC addresses learned on the VLAN has exceeded the limit. • Invalid VLAN index—The VLAN of the packet, while configured, does not yet exist in the kernel. • Interface not learning—The MAC address is learned on an interface that does not yet allow learning—for example, the interface is blocked. • No nexthop—The MAC address is learned on an interface that does not have a unicast next hop. • MAC learning disabled—The MAC address is learned on an interface on which MAC learning has been disabled. • Others—The message contains some other error. show ethernet-switching statistics mac-learning user@switch> show ethernet-switching statistics mac-learning show ethernet-switching statistics mac-learning detail user@switch> show ethernet-switching statistics mac-learning detail Learning stats: 0 learn msg rcvd, 0 error Learning stats: 0 learn msg rcvd, 0 error Interface Local pkts Transit pkts ge-0/0/0.0 0 0 ge-0/0/1.0 0 0 ge-0/0/2.0 0 0 ge-0/0/3.0 0 0 Error 0 0 0 0 Interface: ge-0/0/0.0 Learning message from local packets: 0 Learning message from transit packets: 1 Learning message with error: 0 Invalid VLAN: 0 Invalid MAC: Security violation: 0 Interface down: Incorrect membership: 0 Interface limit: MAC move limit: 0 VLAN limit: Invalid VLAN index: 0 Interface not learning: No nexthop: 0 MAC learning disabled: Others: 0 0 0 0 0 0 0 Interface: ge-0/0/1.0 Learning message from local packets: 0 Learning message from transit packets: 2 1247 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Learning message with error: Invalid VLAN: Security violation: Incorrect membership: MAC move limit: Invalid VLAN index: No nexthop: Others: show ethernet-switching statistics mac-learning interface ge-0/0/1 1248 0 0 0 0 0 0 0 0 Invalid MAC: Interface down: Interface limit: VLAN limit: Interface not learning: MAC learning disabled: user@switch> show ethernet-switching statistics mac-learning interface ge-0/0/1 Interface Local pkts Transit pkts Error ge-0/0/1.0 0 1 1 0 0 0 0 0 0 Chapter 63: Operational Mode Commands for Bridging and VLANs show ethernet-switching table Syntax Release Information Description Options show ethernet-switching table Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays the Ethernet switching table. none—(Optional) Display brief information about the Ethernet switching table. brief | detail | extensive | summary—(Optional) Display the specified level of output. management-vlan—(Optional) Display the Ethernet switching table for a management VLAN. interface-name—(Optional) Display the Ethernet switching table for a specific interface. sort-by (name | tag)—(Optional) Display VLANs in ascending order of VLAN IDs or VLAN names. vlan vlan-name—(Optional) Display the Ethernet switching table for a specific VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 show ethernet-switching table on page 1250 show ethernet-switching table brief on page 1251 show ethernet-switching table detail on page 1251 show ethernet-switching table extensive on page 1252 show ethernet-switching table interface ge-0/0/1 on page 1252 Table 163 on page 1249 lists the output fields for the show ethernet-switching table command. Output fields are listed in the approximate order in which they appear. Table 163: show ethernet-switching table Output Fields Field Name Field Description Level of Output VLAN The name of a VLAN. All levels 1249 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 163: show ethernet-switching table Output Fields (continued) Field Name Field Description Level of Output Tag The VLAN ID tag name or number. extensive MAC or MAC address The MAC address associated with the VLAN. All levels Type The type of MAC address. Values are: All levels • static—The MAC address is manually created. • learn—The MAC address is learned dynamically from a packet's source MAC address. • flood—The MAC address is unknown and flooded to all members. Age The time remaining before the entry ages out and is removed from the Ethernet switching table. All levels Interfaces Interface associated with learned MAC addresses or All-members (flood entry). All levels Learned For learned entries, the time which the entry was added to the Ethernet-switching table. detail, extensive Nexthop index The nexthop index number. detail, extensive show ethernet-switching table 1250 user@switch> show ethernet-switching table Ethernet-switching table: 57 entries, 17 learned VLAN MAC address Type F2 * Flood F2 00:00:05:00:00:03 Learn F2 00:19:e2:50:7d:e0 Static Linux * Flood Linux 00:19:e2:50:7d:e0 Static Linux 00:30:48:90:54:89 Learn T1 * Flood T1 00:00:05:00:00:01 Learn T1 00:00:5e:00:01:00 Static T1 00:19:e2:50:63:e0 Learn T1 00:19:e2:50:7d:e0 Static T10 * Flood T10 00:00:5e:00:01:09 Static T10 00:19:e2:50:63:e0 Learn T10 00:19:e2:50:7d:e0 Static T111 * Flood T111 00:19:e2:50:63:e0 Learn T111 00:19:e2:50:7d:e0 Static T111 00:19:e2:50:ac:00 Learn T2 * Flood T2 00:00:5e:00:01:01 Static T2 00:19:e2:50:63:e0 Learn T2 00:19:e2:50:7d:e0 Static T3 * Flood T3 00:00:5e:00:01:02 Static T3 00:19:e2:50:63:e0 Learn T3 00:19:e2:50:7d:e0 Static T4 * Flood Age 0 0 0 0 0 0 0 0 0 - Interfaces All-members ge-0/0/44.0 Router All-members Router ge-0/0/47.0 All-members ge-0/0/46.0 Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members ge-0/0/15.0 Router ge-0/0/15.0 All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members Chapter 63: Operational Mode Commands for Bridging and VLANs T4 T4 [output truncated] 00:00:5e:00:01:03 Static 00:19:e2:50:63:e0 Learn - Router 0 ge-0/0/46.0 show ethernet-switching table brief user@switch> show ethernet-switching table brief Ethernet-switching table: 57 entries, 17 learned VLAN MAC address Type F2 * Flood F2 00:00:05:00:00:03 Learn F2 00:19:e2:50:7d:e0 Static Linux * Flood Linux 00:19:e2:50:7d:e0 Static Linux 00:30:48:90:54:89 Learn T1 * Flood T1 00:00:05:00:00:01 Learn T1 00:00:5e:00:01:00 Static T1 00:19:e2:50:63:e0 Learn T1 00:19:e2:50:7d:e0 Static T10 * Flood T10 00:00:5e:00:01:09 Static T10 00:19:e2:50:63:e0 Learn T10 00:19:e2:50:7d:e0 Static T111 * Flood T111 00:19:e2:50:63:e0 Learn T111 00:19:e2:50:7d:e0 Static T111 00:19:e2:50:ac:00 Learn T2 * Flood T2 00:00:5e:00:01:01 Static T2 00:19:e2:50:63:e0 Learn T2 00:19:e2:50:7d:e0 Static T3 * Flood T3 00:00:5e:00:01:02 Static T3 00:19:e2:50:63:e0 Learn T3 00:19:e2:50:7d:e0 Static T4 * Flood T4 00:00:5e:00:01:03 Static T4 00:19:e2:50:63:e0 Learn [output truncated] show ethernet-switching table detail user@switch> show ethernet-switching table detail Ethernet-switching table: 5 entries, 2 learned VLAN: default, Tag: 0, MAC: *, Interface: All-members Interfaces: ge-0/0/11.0, ge-0/0/20.0, ge-0/0/30.0, ge-0/0/36.0, ge-0/0/3.0 Type: Flood Nexthop index: 1307 Age 0 0 0 0 0 0 0 0 0 0 Interfaces All-members ge-0/0/44.0 Router All-members Router ge-0/0/47.0 All-members ge-0/0/46.0 Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members ge-0/0/15.0 Router ge-0/0/15.0 All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 VLAN: default, Tag: 0, MAC: 00:1f:12:30:b8:83, Interface: ge-0/0/3.0 Type: Learn, Age: 0, Learned: 20:09:26 Nexthop index: 1315 VLAN: v1, Tag: 101, MAC: *, Interface: All-members Interfaces: ge-0/0/31.0 Type: Flood Nexthop index: 1313 VLAN: v1, Tag: 101, MAC: 00:1f:12:30:b8:89, Interface: ge-0/0/31.0 Type: Learn, Age: 0, Learned: 20:09:25 Nexthop index: 1312 1251 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS VLAN: v2, Tag: 102, MAC: *, Interface: All-members Interfaces: ae0.0 Type: Flood Nexthop index: 1317 show ethernet-switching table extensive user@switch> show ethernet-switching table extensive Ethernet-switching table: 3 entries, 1 learned VLAN: v1, Tag: 10, MAC: *, Interface: All-members Interfaces: ge-0/0/14.0, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0, ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/8.0, ge-0/0/10.0, ge-0/0/0.0 Type: Flood Nexthop index: 567 VLAN: v1, Tag: 10, MAC: 00:21:59:c6:93:22, Interface: Router Type: Static Nexthop index: 0 VLAN: v1, Tag: 10, MAC: 00:21:59:c9:9a:4e, Interface: ge-0/0/14.0 Type: Learn, Age: 0, Learned: 18:40:50 Nexthop index: 564 show ethernet-switching table interface ge-0/0/1 1252 user@switch> show ethernet-switching table interface ge-0/0/1 Ethernet-switching table: 1 unicast entries VLAN MAC address Type Age Interfaces V1 * Flood - All-members V1 00:00:05:00:00:05 Learn 0 ge-0/0/1.0 Chapter 63: Operational Mode Commands for Bridging and VLANs show gvrp Syntax Release Information Description Options show gvrp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display GARP VLAN Registration Protocol (GVRP) information. none—Displays all GVRP configuration attributes. interface interface-name —(Optional) Displays GVRP statistics for a specific interface only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show gvrp statistics on page 1255 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 show gvrp on page 1253 Table 164 on page 1253 lists the output fields for the show gvrp command. Output fields are listed in the approximate order in which they appear. Table 164: show gvrp Output Fields Field Name Field Description Global GVRP Configuration Displays global GVRP information: • GVRP status—Displays whether GVRP is enabledor disabled. • Join—The maximum number of milliseconds the interfaces must wait before sending VLAN advertisements. • Leave— The number of milliseconds an interface must wait after receiving a Leave message to remove the interface from the VLAN specified in the message. • Leaveall—The interval at which Leave All messages are sent on interfaces. Leave all messages maintain current GVRP VLAN membership information in the network. Interface based configuration Displays interface-specific GVRP information: • Interface—The interface on which GVRP is configured.. • GVRP status—Displays whether GVRP is enabled or disabled. show gvrp user@switch> show gvrp Global GVRP configuration GVRP status : Enabled GVRP timers (ms) Join : 40 Leave : 120 Leaveall : 2000 1253 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Interface based configuration: Interface GVRP status ---------- ----------ge-0/0/0.0 Enabled 1254 Chapter 63: Operational Mode Commands for Bridging and VLANs show gvrp statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show gvrp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Generic VLAN Registration Protocol (GVRP) statistics in the form of GARP Information Propagation (GIP) messages. clear • show gvrp on page 1253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 show gvrp statistics on page 1256 Table 165 on page 1255 lists the output fields for the show gvrp statistics command. Output fields are listed in the approximate order in which they appear. Table 165: show gvrp statistics Output Fields Field Name Field Description Join Empty received Number of GIP Join Empty messages received on the switch. Join In received Number of GIP Join In messages received on the switch. Empty received Number of GIP Empty messages received on the switch. Leave In received Number of GIP Leave In messages received on the switch. Leave Empty received Number of GIP Leave Empty messages received on the switch. Leave All received Number of GIP Leave All messages received on the switch. Join Empty transmitted Number of GIP Join Empty messages sent from the switch. Join In transmitted Number of GIP Join In messages sent from the switch. Empty transmitted Number of GIP Empty messages sent from the switch. Leave In transmitted Number of GIP Leave In messages sent from the switch. Leave Empty transmitted Number of GIP Leave Empty messages sent from the switch. Leave All transmitted Number of GIP Leave All messages sent from the switch. 1255 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show gvrp statistics 1256 user@switch> show gvrp statistics GVRP statistics Join Empty received Join In received Empty received Leave In received Leave Empty received Leave All received Join Empty transmitted Join In transmitted Empty transmitted Leave In transmitted Leave Empty transmitted Leave All transmitted : : : : : : : : : : : : 0 12 0 0 0 0 0 48 4 0 0 4 Chapter 63: Operational Mode Commands for Bridging and VLANs show mvrp Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show mvrp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiple VLAN Registration Protocol (MVRP) configuration information. view • show mvrp statistics on page 1260 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Verifying That MVRP Is Working Correctly on page 1162 show mvrp on page 1257 Table 166 on page 1257 lists the output fields for the show mvrp command. Output fields are listed in the approximate order in which they appear. Table 166: show mvrp Output Fields Field Name Field Description Global MVRP configuration Displays global MVRP information: MVRP Timers (ms) • MVRP status—Displays whether MVRP is Enabled or Disabled. • MVRP dynamic vlan creation—Displays whether global MVRP dynamic VLAN creation is Dnabled or Disabled. Displays MVRP timer information: • Interface—The interface on which MVRP is configured. • Join—The maximum number of milliseconds the interfaces must wait before sending VLAN advertisements. • Leave—The number of milliseconds an interface must wait after receiving a Leave message to remove the interface from the VLAN specified in the message. • LeaveAll—The interval at which LeaveAll messages are sent on interfaces. LeaveAll messages maintain current MVRP VLAN membership information in the network. Interface based configuration Displays interface-specific MVRP information: • Interface—The interface on which MVRP is configured. • Status—Displays whether MVRP is Enabled or Disabled. • Registration—Displays whether registration for the interface is Forbidden or Normal. • Dynamic VLAN Creation—Displays whether interface dynamic VLAN creation is Enabled or Disabled. show mvrp user@switch> show mvrp Global MVRP configuration 1257 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS MVRP status MVRP dynamic vlan MVRP Timers (ms): Interface -------------all xe-0/1/1.0 : Enabled creation: Enabled Join ---200 200 Leave ----600 600 LeaveAll -------10000 10000 Interface based configuration: Interface Status Registration Dynamic VLAN Creation ---------------------------------------------------all Disabled Normal Enabled xe-0/1/1.0 Enabled Normal Enabled 1258 Chapter 63: Operational Mode Commands for Bridging and VLANs show mvrp dynamic-vlan-memberships Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show mvrp dynamic-vlan-memberships Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display all VLANs that have been created dynamically using Multiple VLAN Registration Protocol (MVRP) on the switch. clear • show mvrp on page 1257 • show mvrp statistics on page 1260 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Verifying That MVRP Is Working Correctly on page 1162 show mvrp dynamic-vlan-memberships on page 1259 Table 167 on page 1259 lists the output fields for the show mvrp dynamic-vlan-memberships command. Output fields are listed in the approximate order in which they appear. Table 167: show mvrp dynamic-vlan-memberships Output Fields Field Name Field Description VLAN Name The name of the dynamically created VLAN. Interfaces The interface or interfaces that are bound to the dynamically created VLAN. show mvrp dynamic-vlan-memberships user@switch> show mvrp dynamic-vlan-memberships VLAN Name Interfaces ---------------------------------__mvrp_100__ xe-0/1/1.0 xe-0/1/0.0 __mvrp_200__ xe-0/1/1.0 xe-0/1/0.0 __mvrp_300__ xe-0/1/1.0 1259 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show mvrp statistics Syntax Release Information Description Options show mvrp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiple VLAN Registration Protocol (MVRP) statistics in the form of Multiple Registration Protocol data unit (MRPDU) messages. none—Show MVRP statistics for all interfaces on the switch. interface interface-name—Show MVRP statistics for the specified interface. Required Privilege Level Related Documentation List of Sample Output Output Fields clear • show mvrp on page 1257 • clear mvrp statistics on page 1230 • Example: Configuring Automatic VLAN Administration Using MVRP on J-EX Series Switches on page 1115 • Verifying That MVRP Is Working Correctly on page 1162 show mvrp statistics interface xe-0/1/1.0 on page 1261 Table 168 on page 1260 lists the output fields for the show mvrp statistics command. Output fields are listed in the approximate order in which they appear. Table 168: show mvrp statistics Output Fields Field Name Field Description MRPDU received Number of MRPDU messages received on the switch. Invalid PDU received Number of invalid MRPDU messages received on the switch. New received Number of new messages received on the switch. Join Empty received Number of MRP Join Empty messages received on the switch. Join In received Number of MRP Join In messages received on the switch. Empty received Number of MRP Empty messages received on the switch. In received Number of MRP In messages received on the switch. Leave received Number of MRP Leave messages received on the switch. LeaveAll received Number of LeaveAll messages received on the switch. 1260 Chapter 63: Operational Mode Commands for Bridging and VLANs Table 168: show mvrp statistics Output Fields (continued) Field Name Field Description MRPDU transmitted Number of MRPDU messages transmitted from the switch. MRPDU transmit failures Number of MRPDU transmit failures from the switch. New transmitted Number of new messages transmitted from the switch. Join Empty transmitted Number of Join Empty messages sent from the switch. Join In transmitted Number of MRP Join In messages sent from the switch. Empty transmitted Number of MRP Empty messages sent from the switch. In transmitted Number of MRP In messages sent from the switch. Leave transmitted Number of MRP Leave Empty messages sent from the switch. LeaveAll transmitted Number of MRP LeaveAll messages sent from the switch. show mvrp statistics interface xe-0/1/1.0 user@switch> show mvrp statistics interface xe-0/1/1.0 MVRP statistics MRPDU received : 3342 Invalid PDU received : 0 New received : 2 Join Empty received : 1116 Join In received : 2219 Empty received : 2 In received : 2 Leave received : 1 LeaveAll received : 1117 MRPDU transmitted : 3280 MRPDU transmit failures : 0 New transmitted : 0 Join Empty transmitted : 1114 Join In transmitted : 2163 Empty transmitted : 1 In transmitted : 1 Leave transmitted : 1 LeaveAll transmitted : 1111 1261 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show redundant-trunk-group Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show redundant-trunk-group Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about redundant trunk groups. group-name group-name—Display information about the specified redundant trunk group. view • Example: Configuring Redundant Trunk Links for Faster Recovery on page 1101 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 show redundant-trunk-group group-name Group1 on page 1262 Table 169 on page 1262 lists the output fields for the show redundant-trunk-group command. Output fields are listed in the approximate order in which they appear. Table 169: show redundant-trunk-group Output Fields Field Name Field Description Group Name Name of the redundant trunk port group. Interface Name of an interface belonging to the trunk port group. • (P) denotes a primary interface. • (A) denotes an active interface. • Lack of (A) denotes a blocking interface. State Operating state of the interface: UP or DOWN. Last Time of Flap Date and time at which the advertised link became unavailable, and then, available again. # Flaps Total number of flaps since the last switch reboot. show redundant-trunk-group group-name Group1 1262 user@switch> show redundant—trunk-group group-name Group1 show redundant-trunk-group group-name Group1 Group Name Interface Group1 ge-0/0/45.0 (P) ge-0/0/47.0 State UP UP Last Time of Flap Fri Jan 2 04:10:58 Fri Jan 2 04:10:58 # Flaps 0 0 Chapter 63: Operational Mode Commands for Bridging and VLANs show vlans Syntax Release Information Description show vlans Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about VLANs configured on bridged Ethernet interfaces. For interfaces configured to support a VoIP VLAN and a data VLAN, the show vlans command displays both tagged and untagged membership for those VLANs. NOTE: When a series of VLANs is created with the vlan-range statement, such VLAN names are prefixed and suffixed with a double underscore. For example, a series of VLANs using the VLAN range 1–3 and the base VLAN name marketing are displayed as __marketing_1__, __marketing_2__, and __marketing_3__. NOTE: To display an 802.1X supplicant successfully authenticated in multiple-supplicant mode with dynamic VLAN movement, use the show vlans vlan-name extensive operational mode command, where vlan-name is the dynamic VLAN. Options none—Display information for all VLANs. VLAN information is displayed by VLAN name in ascending order. brief | detail | extensive—(Optional) Display the specified level of output. dot1q-tunneling—(Optional) Display VLANs with the Q-in-Q tunneling feature enabled. management-vlan—(Optional) Display management VLANs. sort-by (name | tag)—(Optional) Display VLANs in ascending order of VLAN IDs or VLAN names. summary—(Optional) Display the total number of VLANs and counts of VLANs by type—for example, the number of dynamic, 802.1Q, and Q-in-Q tunneled VLANs. vlan-name—(Optional) Display information for the specified VLAN. vlan-range-name—(Optional) Display information for the specified VLAN range. To see information for all members of the VLAN range, specify the base VLAN name—for 1263 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS example, employee for a VLAN range that includes __employee_1__ through __employee_10__. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show ethernet-switching interfaces on page 997 • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Configuring a Private VLAN on a J-EX Series Switch on page 1107 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 show vlans on page 1266 show vlans brief on page 1267 show vlans detail on page 1267 show vlans extensive (MAC-based) on page 1268 show vlans extensive (Port-based) on page 1268 show vlans sort-by tag on page 1269 show vlans sort-by name on page 1270 show vlans employee (vlan-range-name) on page 1270 show vlans summary on page 1271 Table 170 on page 1264 lists the output fields for the show vlans command. Output fields are listed in the approximate order in which they appear. Table 170: show vlans Output Fields Field Name Field Description Level of Output Name Name of a VLAN. none, brief Tag The 802.1Q tag applied to this VLAN. If none is displayed, no tag is applied. All levels Interfaces Interface associated with learned MAC addresses or all-members (flood entry). An asterisk (*) beside the interface indicates that the interface is UP. All levels Address The IP address. none, brief Ports Active / Total The number of interfaces associated with a VLAN. The Active column indicates interfaces that are UP, and the Total column indicates interfaces that are active and inactive. brief VLAN Name of a VLAN. detail, extensive Admin state Indicates whether the physical link is operational and can pass packets. detail, extensive 1264 Chapter 63: Operational Mode Commands for Bridging and VLANs Table 170: show vlans Output Fields (continued) Field Name Field Description Level of Output Dot1q Tunneling Status Indicates whether Q-in-Q tunneling is enabled. detail, extensive MAC learning Status Indicates whether MAC learning is disabled. detail, extensive Description A description for the VLAN. detail,extensive Primary IP Primary IP address associated with a VLAN. detail Number of interfaces The number of interfaces associated with a VLAN. Both the total number of interfaces and the number of active interfaces associated with a VLAN are displayed. detail, extensive STP The spanning tree associated with a VLAN. detail, extensive RTG The redundant trunk group associated with a VLAN. detail, extensive Tagged interfaces The tagged interfaces to which a VLAN is associated. detail, extensive Untagged interfaces The untagged interfaces to which a VLAN is associated. detail. extensive Customer VLAN Ranges Lists the customer VLAN (C-VLAN) ranges associated with this service VLAN (S-VLAN). extensive Private VLAN Mode The private VLAN mode for this VLAN. Values are Primary, Isolated, and Community. extensive Primary VLAN The primary VLAN tag for this secondary VLAN. extensive Interrnal Index VLAN index internal to the Junos OS. extensive Origin The manner in which the VLAN was created. Values are static and learn. extensive Protocol Port-based VLAN or MAC-based VLAN. MAC-based protocol is displayed when VLAN assignment is done either statically or dynamically through 802.1X. extensive Mac aging time The MAC aging timer. extensive IP addresses IP address associated with a VLAN. extensive Number of MAC entries For MAC-based VLANs created either statically or dynamically, the MAC addresses associated with an interface. extensive Secondary VLANs The secondary VLANs associated with a primary VLAN. extensive Isolated VLANs The isolated VLANs associated with a primary VLAN. extensive Community VLANs The community VLANs associated with a primary VLAN. extensive 1265 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 170: show vlans Output Fields (continued) Field Name Field Description Level of Output VLANs summary VLAN counts: All levels • Total—Total number of VLANs on the switch. • Configured VLANs—Number of VLANs that are based on user-configured settings. • Internal VLANs—Number of VLANs created by the system with no explicit configuration or protocol—for example, the default VLAN and the VLAN created when a trunk interface is not configured with native VLAN membership. • Temporary VLANs—Number of VLANs from the previous configuration that the system retains for a limited time after restart. Temporary VLANs are converted into one of the other types of VLAN, or are removed from the system if the current configuration does not require them. Dot1q VLANs summary 802.1Q VLAN counts: All levels • Total—Total number of 802.1Q VLANs on the switch. • Tagged VLANs—Number of tagged 802.1Q VLANs. • Untagged VLANs—Number of untagged 802.1Q VLANs. • Private VLAN—Counts of the following kinds of 802.1Q private VLANs (PVLANs): • Primary VLANs—Number of primary forwarding private VLANs. • Community VLANs—Number of secondary transporting and forwarding private VLANs. • Isolated VLANs—Number of secondary receiving and forwarding private VLANs. Dot1q Tunneled VLANs summary Q-in-Q VLAN counts: All levels • Total—Total number of Q-in-Q VLANs on the switch. • Private VLAN—Counts of primary, community, and isolated Q-in-Q private VLANs (PVLANs). Dynamic VLANs Counts of VLANs assigned or created dynamically by a protocol: All levels • Total—Total number of dynamic VLANs on the switch. • Dot1x—Number of 802.1X VLANs authenticated and assigned when the switch learns the MAC address of a supplicant host from a packet’s source MAC address. • MVRP—Number of VLANs created by the Multiple VLAN Registration Protocol (MVRP). show vlans user@switch> show vlans Name default Tag None Interfaces ge-0/0/34.0, ge-0/0/30.0, ge-0/0/26.0, ge-0/0/17.0, ge-0/0/13.0, 1266 ge-0/0/33.0, ge-0/0/29.0, ge-0/0/25.0, ge-0/0/16.0, ge-0/0/11.0, ge-0/0/32.0, ge-0/0/31.0, ge-0/0/28.0, ge-0/0/27.0, ge-0/0/19.0, ge-0/0/18.0, ge-0/0/15.0, ge-0/0/14.0, ge-0/0/9.0, ge-0/0/8.0, Chapter 63: Operational Mode Commands for Bridging and VLANs ge-0/0/3.0, ge-0/0/2.0, ge-0/0/1.0 v0001 1 v0002 2 v0003 3 v0004 4 v0005 5 ge-0/0/24.0, ge-0/0/23.0, ge-0/0/22.0, ge-0/0/21.0 None None None None show vlans brief user@switch> show vlans brief Name default v0001 v0002 v0003 v0004 v0005 v0006 v0007 v0008 v0009 v0010 v0011 v0012 v0013 v0014 v0015 v0016 show vlans detail Tag None 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Address Ports Active/Total 0/23 0/4 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/2 0/0 0/0 0/0 0/0 0/0 0/0 user@switch> show vlans detail VLAN: default, Tag: Untagged, Admin state: Enabled Description: None Primary IP: None, Number of interfaces: 23 (Active = 0) STP: None, RTG: None Untagged interfaces: ge-0/0/34.0, ge-0/0/33.0, ge-0/0/32.0, ge-0/0/31.0, ge-0/0/30.0, ge-0/0/29.0, ge-0/0/28.0, ge-0/0/27.0, ge-0/0/26.0, ge-0/0/25.0, ge-0/0/19.0, ge-0/0/18.0, ge-0/0/17.0, ge-0/0/16.0, ge-0/0/15.0, ge-0/0/14.0, ge-0/0/13.0, ge-0/0/11.0, ge-0/0/9.0, ge-0/0/8.0, ge-0/0/3.0, ge-0/0/2.0, ge-0/0/1.0, Tagged interfaces: None VLAN: v0001, Tag: 802.1Q Tag 1, Admin state: Enabled Description: None Primary IP: None, Number of interfaces: 4 (Active = 0) Dot1q Tunneling Status: Enabled STP: None, RTG: None Untagged interfaces: None Tagged interfaces: ge-0/0/24.0, ge-0/0/23.0, ge-0/0/22.0, ge-0/0/21.0, VLAN: v0002, Tag: 802.1Q Tag 2, Admin state: Enabled Description: None Primary IP: None, Number of interfaces: 0 (Active = 0) STP: None, RTG: None Untagged interfaces: None Tagged interfaces: None VLAN: v0003, Tag: 802.1Q Tag 3, Admin state: Enabled 1267 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Description: None Primary IP: None, Number of interfaces: 0 (Active = 0) STP: None, RTG: None Untagged interfaces: None Tagged interfaces: None VLAN: vlan4000, 802.1Q Tag: Untagged, Admin State: Enabled MAC learning Status: Disabled Number of interfaces: 0 (Active = 0) show vlans extensive (MAC-based) user@switch> show vlans extensive VLAN: default, Created at: Thu May 15 13:43:09 2008 Internal index: 3, Admin State: Enabled, Origin: Static Protocol: Port Mode, Mac aging time: 300 seconds Number of interfaces: Tagged 0 (Active = 0), Untagged 2 (Active = 2) ge-0/0/0.0*, untagged, access ge-0/0/14.0*, untagged, access VLAN: vlan_dyn, Created at: Thu May 15 13:43:09 2008 Internal index: 4, Admin State: Enabled, Origin: Static Protocol: Port Mode Number of interfaces: Tagged 0 (Active = 0), Untagged 0 (Active = 0) Protocol: MAC Based Number of MAC entries: 6 ge-0/0/0.0* 00:00:00:00:00:02 (untagged) 00:00:00:00:00:03 (untagged) 00:00:00:00:00:04 (untagged) 00:00:00:00:00:05 (untagged) 00:00:00:00:00:06 (untagged) 00:00:00:00:00:07 (untagged) show vlans extensive (Port-based) 1268 user@switch> show vlans extensive VLAN: default, created at Mon Feb 4 12:13:47 2008 Tag: None, Internal index: 0, Admin state: Enabled, Origin: static Description: None Dot1q Tunneling Status: Enabled Customer VLAN ranges: 1-4100 Private VLAN Mode: Primary Protocol: Port based, Layer 3 interface: None IP addresses: None STP: None, RTG: None. Number of interfaces: Tagged 0 (Active = 0), Untagged 23 (Active = 0) ge-0/0/34.0 (untagged, access) ge-0/0/33.0 (untagged, access) ge-0/0/32.0 (untagged, access) ge-0/0/31.0 (untagged, access) ge-0/0/30.0 (untagged, access) ge-0/0/29.0 (untagged, access) ge-0/0/28.0 (untagged, access) ge-0/0/27.0 (untagged, access) ge-0/0/26.0 (untagged, access) ge-0/0/25.0 (untagged, access) ge-0/0/19.0 (untagged, access) ge-0/0/18.0 (untagged, access) ge-0/0/17.0 (untagged, access) ge-0/0/16.0 (untagged, access) ge-0/0/15.0 (untagged, access) ge-0/0/14.0 (untagged, access) ge-0/0/13.0 (untagged, access) Chapter 63: Operational Mode Commands for Bridging and VLANs ge-0/0/11.0 (untagged, access) ge-0/0/9.0 (untagged, access) ge-0/0/8.0 (untagged, access) ge-0/0/3.0 (untagged, access) ge-0/0/2.0 (untagged, access) ge-0/0/1.0 (untagged, access) Secondary VLANs: Isolated 1, Community Isolated VLANs : __pvlan_pvlan_ge-0/0/3.0__ Community VLANs : comm1 1 VLAN: v0001, created at Mon Feb 4 12:13:47 2008 Tag: 1, Internal index: 1, Admin state: Enabled, Origin: static Description: None Protocol: Port based, Layer 3 interface: None IP addresses: None STP: None, RTG: None. Number of interfaces: Tagged 4 (Active = 0), Untagged 0 (Active = 0) ge-0/0/24.0 (tagged, trunk) ge-0/0/23.0 (tagged, trunk) ge-0/0/22.0 (tagged, trunk) ge-0/0/21.0 (tagged, trunk) VLAN: v0002, created at Mon Feb 4 12:13:47 2008 Tag: 2, Internal index: 2, Admin state: Enabled, Origin: static Description: None Protocol: Port based, Layer 3 interface: None IP addresses: None STP: None, RTG: None. Number of interfaces: Tagged 0 (Active = 0), Untagged 0 (Active = 0) None VLAN: v0003, created at Mon Feb 4 12:13:47 2008 Tag: 3, Internal index: 3, Admin state: Enabled, Origin: static Description: None Protocol: Port based, Layer 3 interface: None IP addresses: None STP: None, RTG: None. Number of interfaces: Tagged 0 (Active = 0), Untagged 0 (Active = 0) None show vlans sort-by tag user@switch> show vlans sort-by tag Name Tag Interfaces default None __vlan-x_1__ 1 None __vlan-x_2__ 2 None __vlan-x_3__ 3 None __vlan-x_4__ 4 None __vlan-x_5__ 5 None __vlan-x_6__ 6 None __vlan-x_7__ 7 None __vlan-x_8__ 8 1269 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS None __vlan-x_9__ 9 __vlan-x_10__ 10 __vlan-x_11__ 11 __vlan-x_12__ 12 __vlan-x_13__ 13 __vlan-x_14__ 14 __vlan-x_15__ 15 __vlan-x_16__ 16 __vlan-x_17__ 17 __vlan-x_18__ 18 __vlan-x_19__ 19 __vlan-x_20__ 20 None None None None None None None None None None None None show vlans sort-by name user@switch> show vlans sort-by name Name Tag Interfaces __employee_120__ 120 ge-0/0/22.0* __employee_121__ 121 ge-0/0/22.0* __employee_122__ 122 ge-0/0/22.0* __employee_123__ 123 ge-0/0/22.0* __employee_124__ 124 ge-0/0/22.0* __employee_125__ 125 ge-0/0/22.0* __employee_126__ 126 ge-0/0/22.0* __employee_127__ 127 ge-0/0/22.0* __employee_128__ 128 ge-0/0/22.0* __employee_129__ 129 ge-0/0/22.0* __employee_130__ 130 ge-0/0/22.0* show vlans employee (vlan-range-name) user@switch> show vlans employee Name Tag Interfaces __employee_120__ 120 ge-0/0/22.0* __employee_121__ 121 ge-0/0/22.0* 1270 Chapter 63: Operational Mode Commands for Bridging and VLANs __employee_122__ 122 ge-0/0/22.0* __employee_123__ 123 ge-0/0/22.0* __employee_124__ 124 ge-0/0/22.0* __employee_125__ 125 ge-0/0/22.0* __employee_126__ 126 ge-0/0/22.0* __employee_127__ 127 ge-0/0/22.0* __employee_128__ 128 ge-0/0/22.0* __employee_129__ 129 ge-0/0/22.0* __employee_130__ 130 ge-0/0/22.0* show vlans summary user@switch> show vlans summary VLANs summary: Total: 8, Configured VLANs: 5 Internal VLANs: 1, Temporary VLANs: 0 Dot1q VLANs summary: Total: 8, Tagged VLANs: 2, Untagged VLANs: 6 Private VLAN: Primary VLANs: 2, Community VLANs: 2, Isolated VLANs: 3 Dot1q Tunneled VLANs summary: Total: 0 Private VLAN: Primary VLANs: 0, Community VLANs: 0, Isolated VLANs: 0 Dynamic VLANs: Total: 2, Dot1x: 2, MVRP: 0 1271 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1272 PART 14 Spanning-Tree Protocols • Spanning-Tree Protocols—Overview on page 1275 • Examples of Spanning-Tree Protocols Configuration on page 1283 • Configuring Spanning-Tree Protocols on page 1335 • Verifying Spanning Tree Protocols on page 1343 • Configuration Statements for Spanning-Tree Protocols on page 1347 • Operational Mode Commands for Spanning-Tree Protocols on page 1389 1273 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1274 CHAPTER 64 Spanning-Tree Protocols—Overview • Understanding STP for J-EX Series Switches on page 1275 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1279 • Understanding Root Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1280 • Understanding VSTP for J-EX Series Switches on page 1281 Understanding STP for J-EX Series Switches J-EX Series Switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and VLAN Spanning Tree Protocol (VSTP). The default spanning-tree protocol for J-EX Series switches is RSTP. RSTP provides faster convergence times than STP. However, some legacy networks require the slower convergence times of basic STP. If your network includes 802.1D 1998 bridges, you can remove RSTP and explicitly configure STP. See “Configuring STP (CLI Procedure)” on page 1336. When you explicitly configure STP, the J-EX Series switches use the IEEE 802.1D 2004 specification, force version 0. This configuration runs a version of RSTP that is compatible with the classic, basic STP. If you use VLANs, you should enable VSTP and use it on your network. See “Understanding VSTP for J-EX Series Switches” on page 1281. You can use the same operational commands (show spanning-tree bridge and show spanning-tree interface) to check the status of your spanning-tree configuration, regardless of which spanning-tree protocol has been configured. STP uses bridge protocol data unit (BPDU) packets to exchange information with other switches. BPDUs send hello packets out at regular intervals to exchange information across bridges and detect loops in a network topology. There are two types of BPDUs: 1275 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuration BPDUs: Contain configuration information about the transmitting switch and its ports, including switch and port MAC addresses, switch priority, port priority, and port cost. • Topology Change Notification (TCN) BPDUs: When a bridge needs to signal a topology change, it starts to send TCNs on its root port. The designated bridge receives the TCN, acknowledges it, and generates another one for its own root port. The process continues until the TCN reaches the root bridge. STP uses the information provided by the BPDUs to elect a root bridge, identify root ports for each switch, identify designated ports for each physical LAN segment, and prune specific redundant links to create a loop-free tree topology. All leaf devices calculate the best path to the root device and place their ports in blocking or forwarding states based on the best path to the root. The resulting tree topology provides a single active Layer 2 data path between any two end stations. Related Documentation • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding VSTP for J-EX Series Switches on page 1281 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 Understanding RSTP for J-EX Series Switches J-EX Series Switches use Rapid Spanning Tree Protocol (RSTP) to provide better reconvergence time than that provided by the base Spanning Tree Protocol (STP). RSTP identifies certain links as point to point. When a point-to-point link fails, the alternate link can transition to the forwarding state. Although STP provides basic loop prevention functionality, it does not provide fast network convergence when there are topology changes. STP's process to determine network state transitions is slower than RSTP's because it is timer-based. A device must reinitialize every time a topology change occurs. The device must start in the listening state and transition to the learning state and eventually to a forwarding or blocking state. When default values are used for the maximum age (20 seconds) and forward delay (15 seconds), it takes 50 seconds for the device to converge. RSTP converges faster because it uses a handshake mechanism based on point-to-point links instead of the timer-based process used by STP. For networks with VLANs, you can use VLAN Spanning Tree Protocol (VSTP) to run one or more STP or RSTP instances for each VLAN on which VSTP is enabled. VSTP takes the paths of each VLAN into account when calculating routes.. VSTP uses RSTP instances by default. An RSTP domain running on a switch has the following components: 1276 • A root port, which is the “best path” to the root device. • A designated port, which indicates that the switch is the designated bridge for the other switch connecting to this port. Chapter 64: Spanning-Tree Protocols—Overview • An alternate port, which provides an alternate root port. • A backup port, which provides an alternate designated port. Port assignments change through messages exchanged throughout the domain. An RSTP device generates configuration messages once per every hello time interval. If an RSTP device does not receive a configuration message from its neighbor after an interval of three hello times, it determines that the connection with the neighbor is lost. When a root port or a designated port fails on a device, the device generates a configuration message with the proposal bit set. Once its neighbor device receives this message, it verifies that this configuration message is better than the one saved for that port and then it starts a synchronizing operation to ensure that all of its ports are in sync with the new information. Similar waves of proposal agreement handshake messages propagate toward the leaves of the network, quickly restoring the connectivity after a topology change (in a well-designed network that uses RSTP, network convergence can take as little as 0.5 seconds). If a device does not receive an agreement to a proposal message it has sent, it returns to the original IEEE 802.D convention. RSTP was originally defined in the IEEE 802.1w draft specification and later incorporated into the IEEE 802.1D-2004 specification. VSTP and RSTP can be configured concurrently. You can selectively configure up to 253 VLANs using VSTP; the remaining VLANs will be configured using RSTP. VSTP and RSTP are the only spanning-tree protocols that can be configured concurrently on the switch. Related Documentation • Understanding STP for J-EX Series Switches on page 1275 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 Understanding MSTP for J-EX Series Switches Although RSTP provides faster convergence time than STP, it still does not solve a problem inherent in STP: All VLANs within a LAN must share the same spanning tree. To solve this problem, J-EX Series Switches use Multiple Spanning Tree Protocol (MSTP) to create a loop-free topology in networks with multiple spanning-tree regions. An MSTP region allows a group of bridges to be modeled as a single bridge. An MSTP region contains multiple spanning tree instances (MSTIs). MSTIs provide different paths for different VLANs. This functionality facilitates better load sharing across redundant links. MSTP region can support up to 64 MSTIs and each instance can support anywhere from 1 through 4094 vlans. 1277 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS MSTP was originally defined in the IEEE 802.1s draft specification and later incorporated into the IEEE 802.1Q-2003 specification. Related Documentation • Understanding STP for J-EX Series Switches on page 1275 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches J-EX Series Switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), and Multiple Spanning Tree Protocol (MSTP). BPDU protection can help prevent STP misconfigurations that can lead to network outages. A loop-free network is supported through the exchange of a special type of frame called bridge protocol data unit (BPDU). Receipt of BPDUs on certain interfaces in an STP, RSTP, VSTP, or MSTP topology, however, can lead to network outages. Enable BPDU protection on those interfaces to prevent these outages. Peer STP applications running on the switch interfaces use BPDUs to communicate. Ultimately, the exchange of BPDUs determines which interfaces block traffic and which interfaces become root ports and forward traffic. However, a user bridge application running on a PC can also generate BPDUs. If these BPDUs are picked up by STP applications running on the switch, they can trigger STP miscalculations, and those miscalculations can lead to network outages. Enable BPDU protection on switch interfaces connected to user devices or on interfaces on which no BPDUs are expected, such as edge ports. If BPDUs are received on a protected interface, the interface is disabled and stops forwarding frames. Not only can you configure BPDU protection on a switch with a spanning tree, but also on a switch without a spanning tree. This type of topology typically consists of a non-STP switch connected to an STP switch through a trunk interface. To configure BPDU protection on a switch with a spanning tree, include the bpdu-block-on-edge statement at the [edit protocols (stp | mstp | rstp )] hierarchy level. To configure BPDU protection on a switch without a spanning tree, include the bpdu-block statement at the [edit ethernet-switching-options interface interface-name] hierarchy level. After the misconfiguration that triggered the BPDUs being sent to an interface is fixed in the topology, the interface can be unblocked in one of two ways: 1278 • If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. • Use the operational mode command clear ethernet-switching bpdu-error. Chapter 64: Spanning-Tree Protocols—Overview Disabling the BPDU protection configuration does not unblock the interface. Related Documentation • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1279 • Understanding Root Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1280 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches J-EX Series Switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), and Multiple Spanning Tree Protocol (MSTP). Loop protection increases the efficiency of STP, RSTP, and MSTP by preventing ports from moving into a forwarding state that would result in a loop opening up in the network. A loop-free network in spanning-tree topologies is supported through the exchange of a special type of frame called bridge protocol data unit (BPDU). Peer STP applications running on the switch interfaces use BPDUs to communicate. Ultimately, the exchange of BPDUs determines which interfaces block traffic (preventing loops) and which interfaces become root ports and forward traffic. However, a blocking interface can transition to the forwarding state in error if the interface stops receiving BPDUs from its designated port on the segment. Such a transition error can occur when there is a hardware error on the switch or software configuration error between the switch and its neighbor. When loop protection is enabled, the spanning-tree topology detects root ports and blocked ports and makes sure both keep receiving BPDUs. If a loop-protection-enabled interface stops receiving BPDUs from its designated port, it reacts as it would react to a problem with the physical connection on this interface. It doesn't transition the interface to a forwarding state, but instead transitions it to a loop-inconsistent state. The interface recovers and then it transitions back to the spanning-tree blocking state as soon as it receives a BPDU. We recommend that you enable loop protection on all switch interfaces that have a chance of becoming root or designated ports. Loop protection is most effective when 1279 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS enabled in the entire switched network. When you enable loop protection, you must configure at least one action (alarm, block, or both). An interface can be configured for either loop protection or root protection, but not for both. Related Documentation • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Understanding Root Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1280 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Understanding Root Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches J-EX Series Switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), and Multiple Spanning Tree Protocol (MSTP). A loop-free network is supported through the exchange of a special type of frame called bridge protocol data unit (BPDU). Peer STP applications running on the switch interfaces use BPDUs to communicate. Ultimately, the exchange of BPDUs determines which interfaces block traffic and which interfaces become root ports and forward traffic. However, a root port elected through this process has the possibility of being wrongly elected. A user bridge application running on a PC can generate BPDUs, too, and interfere with root port election. Root protection allows network administrators to manually enforce the root bridge placement in the network. Enable root protection on interfaces that should not receive superior BPDUs from the root bridge and should not be elected as the root port. These interfaces become designated ports and are typically located on an administrative boundary. If the bridge receives superior STP BPDUs on a port that has root protection enabled, that port transitions to a root-prevented STP state (inconsistency state) and the interface is blocked. This blocking prevents a bridge that should not be the root bridge from being elected the root bridge. After the bridge stops receiving superior STP BPDUs on the interface with root protection, the interface returns to a listening state, followed by a learning state, and ultimately back to a forwarding state. Recovery back to the forwarding state is automatic. When root protection is enabled on an interface, it is enabled for all the STP instances on that interface. The interface is blocked only for instances for which it receives superior BPDUs. Otherwise, it participates in the spanning-tree topology. 1280 Chapter 64: Spanning-Tree Protocols—Overview An interface can be configured for either root protection or loop protection, but not for both. Related Documentation • Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches on page 1329 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Understanding VSTP for J-EX Series Switches VLAN Spanning Tree Protocol (VSTP) allows J-EX Series Switches to run one or more Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP) instances for each VLAN on which VSTP is enabled. For networks with multiple VLANs, VSTP improves intelligent tree spanning by defining best paths within the VLANs instead of within the entire network. You can configure VSTP for a maximum of 253 VLANs. If you need to run a spanning-tree protocol on more than 253 VLANs, you must configure VSTP and RSTP concurrently. When VSTP and RSTP are configured, up to 253 VLANs can use VSTP and the remaining VLANs use RSTP. You can selectively configure which VLANs use VSTP when VSTP and RSTP are configured. VSTP and RSTP are the only spanning-tree protocols that can be configured concurrently on the switch. NOTE: We recommend that you enable VSTP on all VLANs that could receive VSTP bridge protocol data units (BPDUs). Related Documentation • Understanding STP for J-EX Series Switches on page 1275 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 • Configuring VLAN Spanning Tree Protocol (CLI Procedure) on page 1340 1281 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1282 CHAPTER 65 Examples of Spanning-Tree Protocols Configuration • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches on page 1329 Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches J-EX Series switches use Rapid Spanning Tree Protocol (RSTP) to provide a loop-free topology. RSTP identifies certain links as point to point. When a point-to-point link fails, the alternate link can transition to the forwarding state. RSTP provides better reconvergence time than original STP because it uses protocol handshake messages rather than fixed timeouts. Eliminating the need to wait for timers to expire makes RSTP more efficient than STP. This example describes how to configure RSTP on four J-EX Series switches: • Requirements on page 1284 • Overview and Topology on page 1284 • Configuring RSTP on Switch 1 on page 1286 • Configuring RSTP on Switch 2 on page 1288 • Configuring RSTP on Switch 3 on page 1290 • Configuring RSTP on Switch 4 on page 1293 • Verification on page 1295 1283 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example uses the following hardware and software components: • Four J-EX Series switches Before you configure the switches for RSTP, be sure you have: • Installed the four switches. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. • Performed the initial software configuration on all switches. See Installing and Connecting a J-EX4200 Switch. Overview and Topology In this example, four J-EX Series switches are connected in the topology displayed in Figure 33 on page 1284 to create a loop-free topology. Figure 33: Network Topology for RSTP The interfaces shown in Table 171 on page 1285 will be configured for RSTP. NOTE: You can configure RSTP on logical or physical interfaces. This example shows RSTP configured on logical interfaces. 1284 Chapter 65: Examples of Spanning-Tree Protocols Configuration Table 171: Components of the Topology for Configuring RSTP on J-EX Series Switches Property Settings Switch 1 The following ports on Switch 1 are connected in this way: Switch 2 • ge-0/0/9 is connected to Switch 2 • ge-0/0/13 is connected to Switch 4 • ge-0/0/11 is connected to Switch 3 The following ports on Switch 2 are connected in this way: Switch 3 • ge-0/0/14 is connected to Switch 1 • ge-0/0/18 is connected to Switch 3 The following ports on Switch 3 are connected in this way: Switch 4 • ge-0/0/26 is connected to Switch 1 • ge-0/0/28 is connected to Switch 2 • ge-0/0/24 is connected to Switch 4 The following ports on Switch 4 are connected in this way: VLAN names and tag IDs • ge-0/0/19 is connected to Switch 1 • ge-0/0/23 is connected to Switch 3 voice-vlan, tag 10 employee-vlan, tag 20 guest-vlan, tag 30 camera-vlan, tag 40 This configuration example creates a loop-free topology between four J-EX Series switches using RSTP. An RSTP topology contains ports that have specific roles: • The root port is responsible for forwarding data to the root bridge. • The alternate port is a standby port for the root port. When a root port goes down, the alternate port becomes the active root port. • The designated port forwards data to the downstream network segment or device. • The backup port is a backup port for the designated port. When a designated port goes down, the backup port becomes the active designated port and starts forwarding data. NOTE: You also can create a loop-free topology between the aggregation layer and the distribution layer using redundant trunk links. For more information about configuring redundant trunk links, see “Example: Configuring Redundant Trunk Links for Faster Recovery” on page 1101. 1285 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring RSTP on Switch 1 To configure RSTP on Switch 1, perform these tasks: CLI Quick Configuration To quickly configure interfaces and RSTP on Switch 1, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan-id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan-id 40 set interfaces ge-0/0/13 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/9 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/11 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/13 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/9 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/11 unit 0 family ethernet-switching port-mode trunk set protocols rstp bridge-priority 16k set protocols rstp interface ge-0/0/13.0 cost 1000 set protocols rstp interface ge-0/0/13.0 mode point-to-point set protocols rstp interface ge-0/0/9.0 cost 1000 set protocols rstp interface ge-0/0/9.0 mode point-to-point set protocols rstp interface ge-0/0/11.0 cost 1000 set protocols rstp interface ge-0/0/11.0 mode point-to-point Step-by-Step Procedure To configure interfaces and RSTP on Switch 1: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch1# set ge-0/0/13 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch1# set ge-0/0/9 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch1# set ge-0/0/11 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch1# set ge-0/0/13 unit 0 family ethernet-switching port-mode trunk user@switch1# set ge-0/0/9 unit 0 family ethernet-switching port-mode trunk 1286 Chapter 65: Examples of Spanning-Tree Protocols Configuration user@switch1# set ge-0/0/11 unit 0 family ethernet-switching port-mode trunk 4. Configure RSTP on the switch: [edit protocols] user@switch1# rstp bridge-priority 16k user@switch1# rstp interface ge-0/0/13.0 cost 1000 user@switch1# rstp interface ge-0/0/13.0 mode point-to-point user@switch1# rstp interface ge-0/0/9.0 cost 1000 user@switch1# rstp interface ge-0/0/9.0 mode point-to-point user@switch1# rstp interface ge-0/0/11.0 cost 1000 user@switch1# rstp interface ge-0/0/11.0 mode point-to-point Results Check the results of the configuration: user@switch1> show configuration interfaces { ge-0/0/13 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } ge-0/0/9 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } ge-0/0/11 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } } protocols { rstp { bridge-priority 16k; interface ge-0/0/13.0 { cost 1000; mode point-to-point; } interface ge-0/0/9.0 { 1287 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS cost 1000; mode point-to-point; } interface ge-0/0/11.0 { cost 1000; mode point-to-point; } } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } Configuring RSTP on Switch 2 To configure RSTP on switch 2, perform these tasks: CLI Quick Configuration To quickly configure interfaces and RSTP on Switch 2, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan-id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan-id 40 set interfaces ge-0/0/14 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/18 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/14 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/18 unit 0 family ethernet-switching port-mode trunk set protocols rstp bridge-priority 32k set protocols rstp interface ge-0/0/14.0 cost 1000 set protocols rstp interface ge-0/0/14.0 mode point-to-point set protocols rstp interface ge-0/0/18.0 cost 1000 set protocols rstp interface ge-0/0/18.0 mode point-to-point 1288 Chapter 65: Examples of Spanning-Tree Protocols Configuration Step-by-Step Procedure To configure interfaces and RSTP on Switch 2: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan vlan-description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch2# set ge-0/0/14 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch2# set ge-0/0/18 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch2# set ge-0/0/14 unit 0 family ethernet-switching port-mode trunk user@switch2# set ge-0/0/18 unit 0 family ethernet-switching port-mode trunk 4. Configure RSTP on the switch: [edit protocols] user@switch2# rstp bridge-priority 32k user@switch2# rstp interface ge-0/0/14.0 cost 1000 user@switch2# rstp interface ge-0/0/14.0 mode point-to-point user@switch2# rstp interface ge-0/0/18.0 cost 1000 user@switch2# rstp interface ge-0/0/18.0 mode point-to-point Results Check the results of the configuration: user@switch2> show configuration interfaces { ge-0/0/14 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } ge-0/0/18 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } 1289 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } } } protocols { rstp { bridge-priority 32k; interface ge-0/0/14.0 { cost 1000; mode point-to-point; } interface ge-0/0/18.0 { cost 1000; mode point-to-point; } } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } Configuring RSTP on Switch 3 To configure RSTP on switch 3, perform these tasks: CLI Quick Configuration To quickly configure interfaces and RSTP on Switch 3, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan-id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan-id 40 set interfaces ge-0/0/26 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/28 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/24 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/26 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/28 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/24 unit 0 family ethernet-switching port-mode trunk set protocols rstp bridge-priority 8k set protocols rstp interface ge-0/0/26.0 cost 1000 1290 Chapter 65: Examples of Spanning-Tree Protocols Configuration set protocols rstp interface ge-0/0/26.0 mode point-to-point set protocols rstp interface ge-0/0/28.0 cost 1000 set protocols rstp interface ge-0/0/28.0 mode point-to-point set protocols rstp interface ge-0/0/24.0 cost 1000 set protocols rstp interface ge-0/0/24.0 mode point-to-point Step-by-Step Procedure To configure interfaces and RSTP on Switch 3: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch3# set ge-0/0/26 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch3# set ge-0/0/28 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch3# set ge-0/0/24 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch3# set ge-0/0/26 unit 0 family ethernet-switching port-mode trunk user@switch3# set ge-0/0/28 unit 0 family ethernet-switching port-mode trunk user@switch3# set ge-0/0/24 unit 0 family ethernet-switching port-mode trunk 4. Configure RSTP on the switch: [edit protocols] user@switch3# rstp bridge-priority 8k user@switch3# rstp interface ge-0/0/26.0 cost 1000 user@switch3# rstp interface ge-0/0/26.0 mode point-to-point user@switch3# rstp interface ge-0/0/28.0 cost 1000 user@switch3# rstp interface ge-0/0/28.0 mode point-to-point user@switch3# rstp interface ge-0/0/24.0 cost 1000 user@switch3# rstp interface ge-0/0/24.0 mode point-to-point Results Check the results of the configuration: user@switch3> show configuration interfaces { ge-0/0/26 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } 1291 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } } ge-0/0/28 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } ge-0/0/24 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } } } protocols { rstp { bridge-priority 8k; interface ge-0/0/26.0 { cost 1000; mode point-to-point; } interface ge-0/0/28.0 { cost 1000; mode point-to-point; } interface ge-0/0/24.0 { cost 1000; mode point-to-point; } } bridge-priority 8k; } } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } 1292 Chapter 65: Examples of Spanning-Tree Protocols Configuration camera-vlan { vlan-id 40; } } Configuring RSTP on Switch 4 To configure RSTP on switch 4, perform these tasks: CLI Quick Configuration To quickly configure interfaces and RSTP on Switch 4, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan–id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan-id 40 set interfaces ge-0/0/23 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/19 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/23 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/19 unit 0 family ethernet-switching port-mode trunk set protocols rstp bridge-priority 16k set protocols rstp interface ge-0/0/23.0 cost 1000 set protocols rstp interface ge-0/0/23.0 mode point-to-point set protocols rstp interface ge-0/0/19.0 cost 1000 set protocols rstp interface ge-0/0/19.0 mode point-to-point Step-by-Step Procedure To configure interfaces and RSTP on Switch 4: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch4# set ge-0/0/23 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch4# set ge-0/0/19 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch4# set ge-0/0/23 unit 0 family ethernet-switching port-mode trunk 1293 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch4# set ge-0/0/19 unit 0 family ethernet-switching port-mode trunk 4. Configure RSTP on the switch: [edit protocols] user@switch4# rstp bridge-priority 16k user@switch4# rstp interface all cost 1000 user@switch4# rstp interface ge-0/0/23.0 cost 1000 user@switch4# rstp interface ge-0/0/23.0 mode point-to-point user@switch4# rstp interface ge-0/0/19.0 cost 1000 user@switch4# rstp interface ge-0/0/19.0 mode point-to-point Results Check the results of the configuration: user@switch4> show configuration interfaces { ge-0/0/23 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } ge-0/0/19 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members [10 20 30 40]; } } } } } protocols { rstp { bridge-priority 16k; interface ge-0/0/23.0 { cost 1000; mode point-to-point; } interface ge-0/0/19.0 { cost 1000; mode point-to-point; } } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { 1294 Chapter 65: Examples of Spanning-Tree Protocols Configuration vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying RSTP Configuration on Switch 1 on page 1295 • Verifying RSTP Configuration on Switch 2 on page 1295 • Verifying RSTP Configuration on Switch 3 on page 1296 • Verifying RSTP Configuration on Switch 4 on page 1296 Verifying RSTP Configuration on Switch 1 Purpose Action Verify the RSTP configuration on Switch 1. Use the operational mode command: user@switch1> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/13.0 ge-0/0/9.0 ge-0/0/11.0 Meaning Port ID 128:527 128:529 128:531 Designated port ID 128:525 128:513 128:513 Designated bridge ID 16384.0019e25040e0 32768.0019e2503d20 8192.0019e25051e0 Port Cost 1000 1000 1000 State Role BLK BLK FWD ALT ALT ROOT Refer to the topology in Figure 33 on page 1284. The operational mode command show spanning-tree interface shows that ge-0/0/13.0 is in a forwarding state. The other interfaces on Switch 1 are blocking. Verifying RSTP Configuration on Switch 2 Purpose Action Verify the RSTP configuration on Switch 2. Use the operational mode command: user@switch2> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/14.0 Port ID Designated port ID 128:513 128:513 Designated bridge ID 32768.0019e2503d20 Port State Cost 1000 BLK Role DESG 1295 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/18.0 Meaning 128:519 128:515 8192.0019e25051e0 1000 FWD ROOT Refer to the topology in Figure 33 on page 1284. The operational mode command show spanning-tree interface shows that ge-0/0/18.0 is in a forwarding state and the root port. The other interface on Switch 2 is blocking. Verifying RSTP Configuration on Switch 3 Purpose Action Verify the RSTP configuration on Switch 3. Use the operational mode commands: user@switch3> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/26.0 ge-0/0/28.0 ge-0/0/24.0 Meaning Port ID Designated port ID 128:513 128:513 128:515 128:515 128:517 128:517 Designated bridge ID 8192.0019e25051e0 8192.0019e25051e0 8192.0019e25051e0 Port State Cost 1000 FWD 1000 FWD 1000 FWD Role DESG DESG DESG Refer to the topology in Figure 33 on page 1284. The operational mode command show spanning-tree interface shows that no interface is the root interface. Verifying RSTP Configuration on Switch 4 Purpose Action Verify the RSTP configuration on Switch 4. Use the operational mode commands: user@switch4> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/23.0 ge-0/0/19.0 Meaning Related Documentation 1296 Port ID 128:523 128:525 Designated port ID 128:517 128:525 Designated bridge ID 8192.0019e25051e0 16384.0019e25040e0 Port Cost 1000 1000 State Role FWD FWD ROOT DESG Refer to the topology in Figure 33 on page 1284. The operational mode command show spanning-tree interface shows that interface ge-0/0/23.0 is the root interface and forwarding. • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding RSTP for J-EX Series Switches on page 1276 Chapter 65: Examples of Spanning-Tree Protocols Configuration Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches Multiple Spanning Tree Protocol (MSTP) is used to create a loop-free topology in networks using multiple spanning tree regions, each region containing multiple spanning-tree instances (MSTIs). MSTIs provide different paths for different VLANs. This functionality facilitates better load sharing across redundant links. Up to 64 MSTI instances can be created for a J-EX Series switch, and each MSTI can support up to 4094 VLANs. This example describes how to configure MSTP on four J-EX Series switches: • Requirements on page 1297 • Overview and Topology on page 1297 • Configuring MSTP on Switch 1 on page 1300 • Configuring MSTP on Switch 2 on page 1303 • Configuring MSTP on Switch 3 on page 1305 • Configuring MSTP on Switch 4 on page 1308 • Verification on page 1311 Requirements This example uses the following hardware and software components: • Four J-EX Series switches Before you configure the switches for MSTP, be sure you have: • Installed the four switches. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. • Performed the initial software configuration on all switches. See Installing and Connecting a J-EX4200 Switch. Overview and Topology When the number of VLANs grows in a network, MSTP provides a more efficient way of creating a loop-free topology using MSTIs. Each MSTI in the spanning tree domain maintains its own tree. Each tree can be mapped to different links, utilizing bandwidth that would be unavailable to a single tree. MSTIs reduce demand on system resources. 1297 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 34: Network Topology for MSTP The interfaces shown in Table 172 on page 1298 will be configured for MSTP. NOTE: You can configure MSTP on logical or physical interfaces. This example shows MSTP configured on logical interfaces. Table 172: Components of the Topology for Configuring MSTP on J-EX Series Switches Property Settings Switch 1 The following ports on Switch 1 are connected in this way: Switch 2 1298 • ge-0/0/9 is connected to Switch 2 • ge-0/0/13 is connected to Switch 4 • ge-0/0/11 is connected to Switch 3 The following ports on Switch 2 are connected in this way: • ge-0/0/14 is connected to Switch 1 • ge-0/0/18 is connected to Switch 3 Chapter 65: Examples of Spanning-Tree Protocols Configuration Table 172: Components of the Topology for Configuring MSTP on J-EX Series Switches (continued) Property Settings Switch 3 The following ports on Switch 3 are connected in this way: Switch 4 • ge-0/0/26 is connected to Switch 1 • ge-0/0/28 is connected to Switch 2 • ge-0/0/24 is connected to Switch 4 The following ports on Switch 4 are connected in this way: • ge-0/0/19 is connected to Switch 1 • ge-0/0/23 is connected to Switch 3 VLAN names and tag IDs voice-vlan, tag 10 employee-vlan, tag 20 guest-vlan, tag 30 camera-vlan, tag 40 MSTIs 1 2 The topology in Figure 34 on page 1298 shows a Common Internal Spanning Tree (CIST). The CIST is a single spanning tree connecting all devices in the network. The switch with the highest priority is elected as the root bridge of the CIST. Also in an MSTP topology are ports that have specific roles: • The root port is responsible for forwarding data to the root bridge. • The alternate port is a standby port for the root port. When a root port goes down, the alternate port becomes the active root port. • The designated port forwards data to the downstream network segment or device. • The backup port is a backup port for the designated port. When a designated port goes down, the backup port becomes the active designated port and starts forwarding data. In this example, one MSTP region, region1, contains Switch 1, Switch 2, Switch 3, and Switch 4. Within the region, four VLANs are created: • The voice-vlan supports voice traffic and has a VLAN tag identifier of 10. • employee-vlan supports data traffic and has a VLAN tag identifier of 20. • The guest-vlan supports guest VLAN traffic (for supplicants that fail 802-1X authentication) and has a VLAN tag identifier of 30. • The camera-vlan supports video traffic and has a VLAN tag identifier of 40. The VLANs are associated with specific interfaces on each of the four switches. Two MSTIs, 1 and 2, are then associated with the VLAN tag identifiers, and some MSTP parameters, such as cost, are configured on each switch. 1299 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring MSTP on Switch 1 To configure MSTP on Switch 1, perform these tasks: CLI Quick Configuration To quickly configure interfaces and MSTP on Switch 1, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan-id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan-id 40 set interfaces ge-0/0/13 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/9 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/11 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/13 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/9 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/11 unit 0 family ethernet-switching port-mode trunk set protocols mstp configuration-name region1 set protocols mstp bridge-priority 16k set protocols mstp interface ge-0/0/13.0 cost 1000 set protocols mstp interface ge-0/0/13.0 mode point-to-point set protocols mstp interface ge-0/0/9.0 cost 1000 set protocols mstp interface ge-0/0/9.0 mode point-to-point set protocols mstp interface ge-0/0/11.0 cost 1000 set protocols mstp interface ge-0/0/11.0 mode point-to-point set protocols mstp msti 1 bridge-priority 16k set protocols mstp msti 1 vlan [10 20] set protocols mstp msti 1 interface ge-0/0/11.0 cost 4000 set protocols mstp msti 2 bridge-priority 8k set protocols mstp msti 2 vlan [30 40] Step-by-Step Procedure To configure interfaces and MSTP on Switch 1: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# user@switch1# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch1# set ge–0/0/13 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch1# set ge-0/0/9 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch1# set ge-0/0/11 unit 0 family ethernet-switching vlan members [10 20 30 40] 1300 Chapter 65: Examples of Spanning-Tree Protocols Configuration 3. Configure the port mode for the interfaces: [edit interfaces] user@switch1# set ge–0/0/13 unit 0 family ethernet-switching port-mode trunk user@switch1# set ge-0/0/9 unit 0 family ethernet-switching port-mode trunk user@switch1# set ge-0/0/11 unit 0 family ethernet-switching port-mode trunk 4. Configure MSTP on the switch, including the two MSTIs: [edit protocols] user@switch1# mstp configuration-name region1 user@switch1# mstp bridge-priority 16k user@switch1# mstp interface ge-0/0/13.0 cost 1000 user@switch1# mstp interface ge-0/0/13.0 mode point-to-point user@switch1# mstp interface ge-0/0/9.0 cost 1000 user@switch1# mstp interface ge-0/0/9.0 mode point-to-point user@switch1# mstp interface ge-0/0/11.0 cost 4000 user@switch1# mstp interface ge-0/0/11.0 mode point-to-point user@switch1# mstp msti 1 bridge-priority 16k user@switch1# mstp msti 1 vlan [10 20] user@switch1# mstp msti 1 interface ge-0/0/11.0 cost 4000 user@switch1# mstp msti 2 bridge-priority 8k user@switch1# mstp msti 2 vlan [30 40] Results Check the results of the configuration: user@switch1> show configuration interfaces { ge-0/0/13 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } ge-0/0/9 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } ge-0/0/11 { unit 0 { family ethernet-switching { 1301 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } } protocols { mstp { configuration-name region1; bridge-priority 16k; interface ge-0/0/13.0 { cost 1000; mode point-to-point; } interface ge-0/0/9.0 { cost 1000; mode point-to-point; } interface ge-0/0/11.0 { cost 4000; mode point-to-point; } msti 1 { bridge-priority 16k; vlan [ 10 20 ]; interface ge-0/0/11.0 { cost 4000; } } msti 2 { bridge-priority 8k; vlan [ 30 40 ]; } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } 1302 Chapter 65: Examples of Spanning-Tree Protocols Configuration Configuring MSTP on Switch 2 To configure on Switch 2, perform these tasks: CLI Quick Configuration To quickly configure interfaces and MSTP on Switch 2, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan—id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan-id 40 set interfaces ge–0/0/14 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/18 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/14 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/18 unit 0 family ethernet-switching port-mode trunk set protocols mstp configuration-name region1 set protocols mstp bridge-priority 32k set protocols mstp interface ge-0/0/14.0 cost 1000 set protocols mstp interface ge-0/0/14.0 mode point-to-point set protocols mstp interface ge-0/0/18.0 cost 1000 set protocols mstp interface ge-0/0/18.0 mode point-to-point set protocols mstp msti 1 bridge-priority 32k set protocols mstp msti 1 vlan [10 20] set protocols mstp msti 2 bridge-priority 4k set protocols mstp msti 2 vlan [30 40] Step-by-Step Procedure To configure interfaces and MSTP on Switch 2: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# user@switch2# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan vlan-description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch2# set ge-0/0/14 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch2# set ge-0/0/18 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch2# set ge-0/0/14 unit 0 family ethernet-switching port-mode trunk user@switch2# set ge-0/0/18 unit 0 family ethernet-switching port-mode trunk 1303 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 4. Configure MSTP on the switch, including the two MSTIs: [edit protocols] user@switch2# mstp configuration-name region1 user@switch2# mstp bridge-priority 32k user@switch2# mstp interface ge-0/0/14.0 cost 1000 user@switch2# mstp interface ge-0/0/14.0 mode point-to-point user@switch2# mstp interface ge-0/0/18.0 cost 1000 user@switch2# mstp interface ge-0/0/18.0 mode point-to-point user@switch2# mstp interface all cost 1000 user@switch2# mstp msti 1 bridge-priority 32k user@switch2# mstp msti 1 vlan [10 20] user@switch2# mstp msti 2 bridge-priority 4k user@switch2# mstp msti 2 vlan [30 40] Results Check the results of the configuration: user@switch2> show configuration interfaces { ge-0/0/14 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } ge-0/0/18 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } } protocols { mstp { configuration-name region1; bridge-priority 32k; interface ge-0/0/14.0 { cost 1000; mode point-to-point; } interface ge-0/0/18.0 { cost 1000; 1304 Chapter 65: Examples of Spanning-Tree Protocols Configuration mode point-to-point; } msti 1 { bridge-priority 32k; vlan [ 10 20 ]; } msti 2 { bridge-priority 4k; vlan [ 30 40 ]; } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } Configuring MSTP on Switch 3 To configure MSTP on Switch 3, perform these tasks: CLI Quick Configuration To quickly configure interfaces and MSTP on Switch 3, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice-vlan description “Voice VLAN” set vlans voice-vlan vlan-id 10 set vlans employee-vlan description “Employee VLAN” set vlans employee-vlan vlan-id 20 set vlans guest-vlan description “Guest VLAN” set vlans guest-vlan vlan-id 30 set vlans camera-vlan description “Camera VLAN” set vlans camera-vlan vlan—id 40 set interfaces ge–0/0/26 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/28 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge–0/0/24 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/26 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/28 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/24 unit 0 family ethernet-switching port-mode trunk set protocols mstp configuration-name region1 set protocols mstp bridge-priority 8k set protocols mstp interface ge-0/0/26.0 cost 1000 set protocols mstp interface ge-0/0/26.0 mode point-to-point set protocols mstp interface ge-0/0/28.0 cost 1000 set protocols mstp interface ge-0/0/28.0 mode point-to-point set protocols mstp interface ge-0/0/24.0 cost 1000 set protocols mstp interface ge-0/0/24.0 mode point-to-point 1305 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS set protocols mstp msti 1 bridge-priority 4k set protocols mstp msti 1 vlan [10 20] set protocols mstp msti 2 bridge-priority 16k set protocols mstp msti 2 vlan [30 40] Step-by-Step Procedure To configure interfaces and MSTP on Switch 3: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# user@switch3# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan-id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan-id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan-id 30 set camera-vlan description “Camera VLAN” set guest-vlan vlan-id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch3# set ge-0/0/26 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch3# set ge-0/0/28 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch3# set ge-0/0/24 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch3# set ge-0/0/26 unit 0 family ethernet-switching port-mode trunk user@switch3# set ge-0/0/28 unit 0 family ethernet-switching port-mode trunk user@switch3# set ge-0/0/24 unit 0 family ethernet-switching port-mode trunk 4. Configure MSTP on the switch, including the two MSTIs: [edit protocols] user@switch3# mstp configuration-name region1 user@switch3# mstp bridge-priority 8k user@switch3# mstp interface ge-0/0/26.0 cost 1000 user@switch3# mstp interface ge-0/0/26.0 mode point-to-point user@switch3# mstp interface ge-0/0/28.0 cost 1000 user@switch3# mstp interface ge-0/0/28.0 mode point-to-point user@switch3# mstp interface ge-0/0/24.0 cost 1000 user@switch3# mstp interface ge-0/0/24.0 mode point-to-point user@switch3# mstp interface all cost 1000 user@switch3# mstp msti 1 bridge-priority 4k user@switch3# mstp msti 1 vlan [10 20] user@switch3# mstp msti 2 bridge-priority 16k user@switch3# mstp msti 2 vlan [30 40] Results Check the results of the configuration: user@switch3> show configuration interfaces { ge-0/0/26 { unit 0 { 1306 Chapter 65: Examples of Spanning-Tree Protocols Configuration family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } ge-0/0/28 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } ge-0/0/24 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } } } protocols { mstp { configuration-name region1; bridge-priority 8k; interface ge-0/0/26.0 { cost 1000; mode point-to-point; } interface ge-0/0/28.0 { cost 1000; mode point-to-point; } interface ge-0/0/24.0 { cost 1000; mode point-to-point; } msti 1 { 1307 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bridge-priority 4k; vlan [ 10 20 ]; } msti 2 { bridge-priority 16k; vlan [ 30 40 ]; } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } Configuring MSTP on Switch 4 To configure MSTP on Switch 4, perform these tasks: CLI Quick Configuration To quickly configure interfaces and MSTP on Switch 4, copy the following commands and paste them into the switch terminal window: [edit] set vlans voice–vlan description “Voice VLAN” set vlans voice-vlan vlan–id 10 set vlans employee—vlan description “Employee VLAN” set vlans employee—vlan vlan—id 20 set vlans guest—vlan description “Guest VLAN” set vlans guest—vlan vlan—id 30 set vlans camera—vlan description “Camera VLAN” set vlans camera—vlan vlan—id 40 set interfaces ge-0/0/23 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge-0/0/19 unit 0 family ethernet-switching vlan members [10 20 30 40] set interfaces ge—0/0/23 unit 0 family ethernet-switching port-mode trunk set interfaces ge—0/0/19 unit 0 family ethernet-switching port-mode trunk set protocols mstp configuration-name region1 set protocols mstp bridge-priority 16k set protocols mstp interface ge—0/0/23.0 cost 1000 set protocols mstp interface ge—0/0/23.0 mode point-to-point set protocols mstp interface ge—0/0/19.0 cost 1000 set protocols mstp interface ge—0/0/19.0 mode point-to-point set protocols mstp msti 1 bridge-priority 16k set protocols mstp msti 1 vlan [10 20] set protocols mstp msti 2 bridge-priority 32k set protocols mstp msti 2 vlan [30 40] 1308 Chapter 65: Examples of Spanning-Tree Protocols Configuration Step-by-Step Procedure To configure interfaces and MSTP on Switch 4: 1. Configure the VLANs voice-vlan, employee-vlan, guest-vlan, and camera-vlan: [edit vlans] user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# user@switch4# 2. set voice-vlan description “Voice VLAN” set voice-vlan vlan—id 10 set employee-vlan description “Employee VLAN” set employee-vlan vlan—id 20 set guest-vlan description “Guest VLAN” set guest-vlan vlan—id 30 set camera-vlan description “Camera VLAN” set guest-vlan vlan—id 40 Configure the VLANs on the interfaces, including support for the Ethernet Switching protocol: [edit interfaces] user@switch4# set ge-0/0/23 unit 0 family ethernet-switching vlan members [10 20 30 40] user@switch4# set ge-0/0/19 unit 0 family ethernet-switching vlan members [10 20 30 40] 3. Configure the port mode for the interfaces: [edit interfaces] user@switch4# set ge—0/0/23 unit 0 family ethernet-switching port-mode trunk user@switch4# set ge—0/0/19 unit 0 family ethernet-switching port-mode trunk 4. Configure MSTP on the switch, including the two MSTIs: [edit protocols] user@switch4# mstp configuration-name region1 user@switch4# mstp bridge-priority 16k user@switch4# mstp interface all cost 1000 user@switch4# mstp interface ge—0/0/23.0 cost 1000 user@switch4# mstp interface ge—0/0/23.0 mode point-to-point user@switch4# mstp interface ge—0/0/19.0 cost 1000 user@switch4# mstp interface ge—0/0/19.0 mode point-to-point user@switch4# mstp msti 1 bridge-priority 16k user@switch4# mstp msti 1 vlan [10 20] user@switch4# mstp msti 2 bridge-priority 32k user@switch4# mstp msti 2 vlan [30 40] Results Check the results of the configuration: user@switch4> show configuration interfaces { ge-0/0/23 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } 1309 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } ge-0/0/19 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 10; members 20; members 30; members 40; } } } } } protocols { mstp { configuration-name region1; bridge-priority 16k; interface ge-0/0/23.0 { cost 1000; mode point-to-point; } interface ge-0/0/19.0 { cost 1000; mode point-to-point; } msti 1 { bridge-priority 16k; vlan [ 10 20 ]; } msti 2 { bridge-priority 32k; vlan [ 30 40 ]; } } } vlans { voice-vlan { vlan-id 10; } employee-vlan { vlan-id 20; } guest-vlan { vlan-id 30; } camera-vlan { vlan-id 40; } } 1310 Chapter 65: Examples of Spanning-Tree Protocols Configuration Verification To confirm that the configuration is working properly, perform these tasks: • Verifying MSTP Configuration on Switch 1 on page 1311 • Verifying MSTP Configuration on Switch 2 on page 1312 • Verifying MSTP Configuration on Switch 3 on page 1314 • Verifying MSTP Configuration on Switch 4 on page 1315 Verifying MSTP Configuration on Switch 1 Purpose Action Verify the MSTP configuration on Switch 1. Use the operational mode commands: user@switch1> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/13.0 ge-0/0/9.0 ge-0/0/11.0 Port ID 128:527 128:529 128:531 Designated port ID 128:525 128:513 128:513 Designated bridge ID 16384.0019e25040e0 32768.0019e2503d20 8192.0019e25051e0 Port Cost 1000 1000 4000 State Role FWD BLK BLK ROOT ALT ALT Port Cost 1000 1000 4000 State Role FWD BLK BLK ROOT ALT ALT Port Cost 1000 1000 1000 State Role FWD FWD FWD DESG ROOT DESG Spanning tree interface parameters for instance 1 Interface ge-0/0/13.0 ge-0/0/9.0 ge-0/0/11.0 Port ID 128:527 128:529 128:531 Designated port ID 128:525 128:513 128:513 Designated bridge ID 16385.0019e25040e0 32769.0019e2503d20 4097.0019e25051e0 Spanning tree interface parameters for instance 2 Interface ge-0/0/13.0 ge-0/0/9.0 ge-0/0/11.0 Port ID 128:527 128:529 128:531 Designated port ID 128:527 128:513 128:531 Designated bridge ID 8194.0019e25044e0 4098.0019e2503d20 8194.0019e25044e0 user@switch1> show spanning-tree bridge STP bridge parameters Context ID : 0 Enabled protocol : MSTP STP bridge parameters for CIST Root ID Root cost Root port CIST regional root CIST internal root cost Hello time Maximum age Forward delay Hop count Message age Number of topology changes : : : : : : : : : : : 8192.00:19:e2:50:51:e0 0 ge-0/0/13.0 8192.00:19:e2:50:51:e0 2000 2 seconds 20 seconds 15 seconds 18 0 3 1311 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Time since last topology change Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 1 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 2 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Local parameters Bridge ID Extended system ID Internal instance ID Meaning : 921 seconds : 16384.00:19:e2:50:44:e0 : 0 : 0 : : : : : : : 4097.00:19:e2:50:51:e0 2000 ge-0/0/13.0 2 seconds 20 seconds 15 seconds 18 : 16385.00:19:e2:50:44:e0 : 0 : 1 : : : : : : : 4098.00:19:e2:50:3d:20 1000 ge-0/0/9.0 2 seconds 20 seconds 15 seconds 19 : 8194.00:19:e2:50:44:e0 : 0 : 2 The operational mode command show spanning-tree interface displays spanning-tree domain information such as the designated port and the port roles. The operational mode command show spanning-tree bridge displays the spanning-tree domain information at either the bridge level or interface level. If the optional interface name is omitted, all interfaces in the spanning-tree domain are displayed. Verifying MSTP Configuration on Switch 2 Purpose Action Verify the MSTP configuration on Switch 2. Use the operational mode commands: user@switch2> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/14.0 ge-0/0/18.0 Port ID Designated port ID 128:513 128:513 128:519 128:515 Designated bridge ID 32768.0019e2503d20 8192.0019e25051e0 Port State Cost 1000 FWD 1000 FWD Role Port Role DESG ROOT Spanning tree interface parameters for instance 1 Interface 1312 Port ID Designated Designated State Chapter 65: Examples of Spanning-Tree Protocols Configuration ge-0/0/14.0 ge-0/0/18.0 128:513 128:519 port ID 128:513 128:515 bridge ID 32769.0019e2503d20 4097.0019e25051e0 Cost 1000 1000 FWD FWD DESG ROOT Spanning tree interface parameters for instance 2 Interface Port ID ge-0/0/14.0 Designated port ID 128:513 128:513 Designated bridge ID 4098.0019e2503d20 ge-0/0/18.0 128:519 4098.0019e2503d20 128:519 Port State Cost 1000 FWD 1000 FWD Role DESG DESG user@switch2> show spanning-tree bridge STP bridge parameters Context ID : 0 Enabled protocol : MSTP STP bridge parameters for CIST Root ID Root cost Root port CIST regional root CIST internal root cost Hello time Maximum age Forward delay Hop count Message age Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 1 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 2 MSTI regional root Hello time Maximum age Forward delay Local parameters Bridge ID Extended system ID Internal instance ID Meaning : : : : : : : : : : : : 8192.00:19:e2:50:51:e0 0 ge-0/0/18.0 8192.00:19:e2:50:51:e0 1000 2 seconds 20 seconds 15 seconds 19 0 1 782 seconds : 32768.00:19:e2:50:3d:20 : 0 : 0 : : : : : : : 4097.00:19:e2:50:51:e0 1000 ge-0/0/18.0 2 seconds 20 seconds 15 seconds 19 : 32769.00:19:e2:50:3d:20 : 0 : 1 : : : : 4098.00:19:e2:50:3d:20 2 seconds 20 seconds 15 seconds : 4098.00:19:e2:50:3d:20 : 0 : 2 The operational mode command show spanning-tree interface displays spanning-tree domain information such as the designated port and the port roles. 1313 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS The operational mode command show spanning-tree bridge displays the spanning-tree domain information at either the bridge level or interface level. If the optional interface name is omitted, all interfaces in the spanning-tree domain are displayed. Verifying MSTP Configuration on Switch 3 Purpose Action Verify the MSTP configuration on Switch 3. Use the operational mode commands: user@switch3> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/26.0 ge-0/0/28.0 ge-0/0/24.0 Port ID Designated port ID 128:513 128:513 128:515 128:515 128:517 128:517 Designated bridge ID 8192.0019e25051e0 8192.0019e25051e0 8192.0019e25051e0 Port State Cost 1000 FWD 1000 FWD 1000 FWD Role Port State Cost 1000 FWD 1000 FWD 1000 FWD Role Port State Cost 1000 BLK 1000 FWD 1000 FWD Role DESG DESG DESG Spanning tree interface parameters for instance 1 Interface ge-0/0/26.0 ge-0/0/28.0 ge-0/0/24.0 Port ID Designated port ID 128:513 128:513 128:515 128:515 128:517 128:517 Designated bridge ID 4097.0019e25051e0 4097.0019e25051e0 4097.0019e25051e0 DESG DESG DESG Spanning tree interface parameters for instance 2 Interface ge-0/0/26.0 ge-0/0/28.0 ge-0/0/24.0 Port ID Designated port ID 128:513 128:531 128:515 128:519 128:517 128:517 Designated bridge ID 8194.0019e25044e0 4098.0019e2503d20 16386.0019e25051e0 user@switch3> show spanning-tree bridge STP bridge parameters Context ID : 0 Enabled protocol : MSTP STP bridge parameters for CIST Root ID CIST regional root CIST internal root cost Hello time Maximum age Forward delay Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 1 MSTI regional root Hello time 1314 : : : : : : : : 8192.00:19:e2:50:51:e0 8192.00:19:e2:50:51:e0 0 2 seconds 20 seconds 15 seconds 3 843 seconds : 8192.00:19:e2:50:51:e0 : 0 : 0 : 4097.00:19:e2:50:51:e0 : 2 seconds ALT ROOT DESG Chapter 65: Examples of Spanning-Tree Protocols Configuration Maximum age Forward delay Local parameters Bridge ID Extended system ID Internal instance ID : 20 seconds : 15 seconds : 4097.00:19:e2:50:51:e0 : 0 : 1 STP bridge parameters for MSTI 2 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Local parameters Bridge ID Extended system ID Internal instance ID Meaning : : : : : : : 4098.00:19:e2:50:3d:20 1000 ge-0/0/28.0 2 seconds 20 seconds 15 seconds 19 : 16386.00:19:e2:50:51:e0 : 0 : 2 The operational mode command show spanning-tree interface displays spanning-tree domain information such as the designated port and the port roles. The operational mode command show spanning-tree bridge displays the spanning-tree domain information at either the bridge level or interface level. If the optional interface name is omitted, all interfaces in the spanning-tree domain are displayed. Verifying MSTP Configuration on Switch 4 Purpose Action Verify the MSTP configuration on Switch 4. Use the operational mode commands: user@switch4> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/23.0 ge-0/0/19.0 Port ID 128:523 128:525 Designated port ID 128:517 128:525 Designated bridge ID 8192.0019e25051e0 16384.0019e25040e0 Port Cost State Role FWD FWD ROOT DESG Port Cost 1000 1000 State Role FWD FWD ROOT DESG Port Cost 1000 1000 State Role BLK FWD ALT ROOT 1000 1000 Spanning tree interface parameters for instance 1 Interface ge-0/0/23.0 ge-0/0/19.0 Port ID 128:523 128:525 Designated port ID 128:517 128:525 Designated bridge ID 4097.0019e25051e0 16385.0019e25040e0 Spanning tree interface parameters for instance 2 Interface ge-0/0/23.0 ge-0/0/19.0 Port ID 128:523 128:525 Designated port ID 128:517 128:527 Designated bridge ID 16386.0019e25051e0 8194.0019e25044e0 user@switch4> show spanning-tree bridge 1315 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS STP bridge parameters Context ID Enabled protocol STP bridge parameters for CIST Root ID Root cost Root port CIST regional root CIST internal root cost Hello time Maximum age Forward delay Hop count Message age Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 1 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 2 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Local parameters Bridge ID Extended system ID Internal instance ID Meaning : 0 : MSTP : : : : : : : : : : : : 8192.00:19:e2:50:51:e0 0 ge-0/0/23.0 8192.00:19:e2:50:51:e0 1000 2 seconds 20 seconds 15 seconds 19 0 4 887 seconds : 16384.00:19:e2:50:40:e0 : 0 : 0 : : : : : : : 4097.00:19:e2:50:51:e0 1000 ge-0/0/23.0 2 seconds 20 seconds 15 seconds 19 : 16385.00:19:e2:50:40:e0 : 0 : 1 : : : : : : : 4098.00:19:e2:50:3d:20 2000 ge-0/0/19.0 2 seconds 20 seconds 15 seconds 18 : 32770.00:19:e2:50:40:e0 : 0 : 2 The operational mode command show spanning-tree interface displays spanning-tree domain information such as the designated port and the port roles. The operational mode command show spanning-tree bridge displays the spanning-tree domain information at either the bridge level or interface level. If the optional interface name is omitted, all interfaces in the spanning-tree domain are displayed. Related Documentation 1316 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 Chapter 65: Examples of Spanning-Tree Protocols Configuration Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches J-EX Series switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP). Configure BPDU protection on interfaces to prevent them from receiving BPDUs that could result in STP misconfigurations, which could lead to network outages. This example describes how to configure BPDU protection on access interfaces on a J-EX Series switch in an RSTP topology: • Requirements on page 1317 • Overview and Topology on page 1317 • Configuration on page 1318 • Verification on page 1319 Requirements This example uses the following hardware and software components: • Two J-EX Series switches in an RSTP topology Before you configure the interfaces on Switch 2 for BPDU protection, be sure you have: • RSTP operating on the switches. NOTE: By default, RSTP is enabled on all J-EX Series switches. Overview and Topology A loop-free network is supported through the exchange of a special type of frame called bridge protocol data unit (BPDU). Receipt of BPDUs on certain interfaces in an STP, RSTP, or MSTP topology, however, can lead to network outages by triggering an STP misconfiguration. To prevent such outages, enable BPDU protection on those interfaces that should not receive BPDUs. Enable BPDU protection on switch interfaces connected to user devices or on interfaces on which no BPDUs are expected, such as edge ports. If a BPDU is received on a BPDU-protected interface, the interface is disabled and stops forwarding frames. Two J-EX Series switches are displayed in Figure 35 on page 1318. In this example, Switch 1 and Switch 2 are configured for RSTP and create a loop-free topology. The interfaces on Switch 2 are access ports. This example shows you how to configure interface ge-0/0/5 and interface ge-0/0/6 as edge ports and to configure BPDU protection. When BPDU protection is enabled, the interfaces will transition to a blocking state when BPDUs are received on them. 1317 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 35: BPDU Protection Topology Table 173 on page 1318 shows the components that will be configured for BPDU protection. Table 173: Components of the Topology for Configuring BPDU Protection on J-EX Series Switches Property Settings Switch 1 (Distribution Layer) Switch 1 is connected to Switch 2 on a trunk interface. Switch 2 (Access Layer) Switch 2 has these access ports that require BPDU protection: • ge-0/0/5 • ge-0/0/6 This configuration example is using an RSTP topology. You also can configure BPDU protection for STP or MSTP topologies at the [edit protocols (mstp | stp)] hierarchy level. Configuration To configure BPDU protection on two access interfaces: CLI Quick Configuration To quickly configure BPDU protection on Switch 2, copy the following commands and paste them into the switch terminal window: [edit] set protocols rstp interface ge-0/0/5 edge set protocols rstp interface ge-0/0/6 edge set protocols rstp bpdu-block-on-edge 1318 Chapter 65: Examples of Spanning-Tree Protocols Configuration Step-by-Step Procedure To configure BPDU protection: 1. Configure interface ge-0/0/5 and interface ge-0/0/6 on Switch 2 as edge ports: [edit protocols rstp] user@switch# set interface ge-0/0/5 edge user@switch#set interface ge-0/0/6 edge 2. Configure BPDU protection on all edge ports: [edit protocols rstp] user@switch# set bpdu-block-on-edge Results Check the results of the configuration: user@switch> show configuration protocols rstp interface ge-0/0/5.0 { edge; } interface ge-0/0/6.0 { edge; } bpdu-block-on-edge; Verification To confirm that the configuration is working properly: • Displaying the Interface State Before BPDU Protection Is Triggered on page 1319 • Verifying That BPDU Protection is Working Correctly on page 1320 Displaying the Interface State Before BPDU Protection Is Triggered Purpose Action Before BPDUs are being received from the PCs connected to interface ge-0/0/5 and interface ge-0/0/6, confirm the interface state. Use the operational mode command: user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface Port ID ge-0/0/0.0 128:513 ge-0/0/1.0 128:514 ge-0/0/2.0 128:515 ge-0/0/3.0 128:516 ge-0/0/4.0 128:517 ge-0/0/5.0 128:518 ge-0/0/6.0 128:519 [output truncated] Meaning Designated port ID 128:513 128:514 128:515 128:516 128:517 128:518 128:519 Designated bridge ID 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 Port Cost 20000 20000 20000 20000 20000 20000 20000 State Role BLK BLK BLK FWD FWD FWD FWD DIS DIS DIS DESG DESG DESG DESG The output from the operational mode command show spanning-tree interface shows that ge-0/0/5.0 and interface ge-0/0/6.0 are designated ports in a forwarding state. 1319 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verifying That BPDU Protection is Working Correctly Purpose Action In this example, the PCs connected to Switch 2 start sending BPDUs to interface ge-0/0/5.0 and interface ge-0/0/6.0 . Verify that BPDU protection is configured on the interfaces. Use the operational mode command: user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface Port ID ge-0/0/0.0 128:513 ge-0/0/1.0 128:514 ge-0/0/2.0 128:515 ge-0/0/3.0 128:516 ge-0/0/4.0 128:517 ge-0/0/5.0 128:518 (Bpdu—Incon) ge-0/0/6.0 128:519 (Bpdu—Incon) ge-0/0/7.0 128:520 ge-0/0/8.0 128:521 [output truncated] Meaning Designated port ID 128:513 128:514 128:515 128:516 128:517 128:518 Designated bridge ID 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 Port Cost 20000 20000 20000 20000 20000 20000 State Role BLK BLK BLK FWD FWD BLK DIS DIS DIS DESG DESG DIS 128:519 32768.0019e2503f00 20000 BLK DIS 128:1 128:521 16384.00aabbcc0348 32768.0019e2503f00 20000 20000 FWD FWD ROOT DESG When BPDUs are sent from the PCs to interface ge-0/0/5.0 and interface ge-0/0/6.0 on Switch 2, the output from the operational mode command show spanning-tree interface shows that the interfaces have transitioned to a BPDU inconsistent state. The BPDU inconsistent state makes the interfaces block and prevents them from forwarding traffic. Disabling the BPDU protection configuration on an interface does not unblock the interface. If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. Otherwise, use the operational mode command clear ethernet-switching bpdu-error to unblock the interface. If the PCs connected to Switch 2 send BPDUs to the interfaces again, BPDU protection is triggered once more and the interfaces transition back to the BPDU inconsistent state. In such cases, you need to find and repair the misconfiguration on the PCs that is triggering BPDUs being sent to Switch 2. Related Documentation 1320 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches on page 1329 Chapter 65: Examples of Spanning-Tree Protocols Configuration • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches J-EX Series switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP). Configure BPDU protection on non-STP interfaces that are connected to switches with spanning trees to prevent the non-STP interfaces from receiving BPDUs. When non-STP interfaces receive BPDUs, it can result in an STP misconfiguration, which could lead to network outages. This example describes how to configure BPDU protection on non-STP interfaces on a J-EX Series switch: • Requirements on page 1321 • Overview and Topology on page 1321 • Configuration on page 1323 • Verification on page 1323 Requirements This example uses the following hardware and software components: • One J-EX Series switch in an RSTP topology • One J-EX Series switch that is not in a spanning-tree topology Before you configure the interface for BPDU protection, be sure you have: • RSTP operating on Switch 1. • Disabled RSTP on Switch 2. NOTE: By default, RSTP is enabled on all J-EX Series switches. Overview and Topology A loop-free network is supported through the exchange of a special type of frame called bridge protocol data unit (BPDU). Receipt of BPDUs on certain interfaces can lead to network outages by triggering an STP miscalculation. Enable BPDU protection on those interfaces that should not receive BPDUs to prevent network outages. BPDU protection for non-STP interfaces can be enabled on interfaces on a non-STP switch connected to an STP switch through a trunk interface. Enable BPDU protection on interfaces on which no BPDUs are expected, such as access ports connected to user devices. If BPDUs are received on a BPDU-protected interface, the interface transitions to a blocking state and stops forwarding frames. 1321 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Two J-EX Series switches are displayed in Figure 36 on page 1322. In this example, Switch 1 and Switch 2 are connected through a trunk interface. Switch 1 is configured for RSTP, but Switch 2 has no spanning tree. Switch 2 has two access ports: interface ge-0/0/5 and interface ge-0/0/6. This example shows you how to configure BPDU protection on interface ge-0/0/5 and interface ge-0/0/6. When BPDU protection is enabled, the interfaces will transition to a blocking state if BPDUs are received. Figure 36: BPDU Protection Topology Table 174 on page 1322 shows the components that will be configured for BPDU protection. Table 174: Components of the Topology for Configuring BPDU Protection on J-EX Series Switches Property Settings Switch 1 (Distribution Layer) Switch 1 is connected to Switch 2 through a trunk interface. Switch 1 is configured for RSTP. Switch 2 (Access Layer) Switch 2 has RSTP disabled and has these access ports that require BPDU protection: 1322 • ge-0/0/5 • ge-0/0/6 Chapter 65: Examples of Spanning-Tree Protocols Configuration CAUTION: When configuring BPDU protection on a non-STP configured switch connected to an STP-configured switch, be careful that you do not configure BPDU protection on all interfaces. Doing so could prevent BPDUs being received on interfaces (such as a trunk interface) that should be receiving BPDUs from an STP-configured switch. Configuration To configure BPDU protection on the interfaces: CLI Quick Configuration To quickly configure BPDU protection on Switch 2, copy the following commands and paste them into the switch terminal window: [edit] set ethernet-switching-options bpdu-block interface ge-0/0/5 set ethernet-switching-options bpdu-block interface ge-0/0/6 Step-by-Step Procedure To configure BPDU protection: 1. Configure interface ge-0/0/5 and interface ge-0/0/6 on Switch 2: [edit ethernet-switching-options] user@switch# set bpdu-block interface ge-0/0/5 user@switch# set bpdu-block interface ge-0/0/6 Results Check the results of the configuration: user@switch> show ethernet-switching-options bpdu-block { interface ge-0/0/5.0; interface ge-0/0/6.0; } Verification To confirm that the configuration is working properly, perform these tasks: • Displaying the Interface State Before BPDU Protection Is Triggered on page 1323 • Verifying That BPDU Protection Is Working Correctly on page 1324 Displaying the Interface State Before BPDU Protection Is Triggered Purpose Action Before BPDUs are being received from the PCs connected to interface ge-0/0/5 and interface ge-0/0/6, confirm the interface state. Use the operational mode command: user@switch> show ethernet-switching interfaces Interface ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/3.0 State down down down up VLAN members default default default default Blocking unblocked unblocked unblocked unblocked 1323 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/4.0 up ge-0/0/5.0 up ge-0/0/6.0 up [output truncated] Meaning v1 v1 default unblocked unblocked unblocked The output from the operational mode command show ethernet-switching interfaces shows that ge-0/0/5.0 and interface ge-0/0/6.0 are up and unblocked. Verifying That BPDU Protection Is Working Correctly Purpose Action In this example, the PCs connected to Switch 2 start sending BPDUs to interface ge-0/0/5.0 and interface ge-0/0/6.0. Verify that BPDU protection is configured on the interfaces. Use the operational mode command: user@switch> show ethernet-switching interfaces Interface State ge-0/0/0.0 up ge-0/0/1.0 up ge-0/0/2.0 up ge-0/0/3.0 up ge-0/0/4.0 up ge-0/0/5.0 down ge-0/0/6.0 down [output truncated] Meaning VLAN members default default default default v1 v1 default Blocking unblocked unblocked unblocked unblocked unblocked blocked - blocked by bpdu-control blocked - blocked by bpdu-control When BPDUs are sent from the PCs to interface ge-0/0/5.0 and interface ge-0/0/6.0 on Switch 2, the output from the operational mode command show spanning-tree interface shows that the interfaces have transitioned to a BPDU inconsistent state. The BPDU inconsistent state makes the interfaces shut down and prevents them from forwarding traffic. Disabling the BPDU protection configuration on an interface does not unblock the interface. If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. Otherwise, use the operational mode command clear ethernet-switching bpdu-error to recover from the error condition and restore the interface to service. If the PCs connected to Switch 2 send BPDUs to the interfaces again, BPDU protection is triggered once more and the interfaces transition back to the BPDU inconsistent state. In such cases, you need to find and repair the misconfiguration on the PCs that is triggering BPDUs being sent to Switch 2. Related Documentation 1324 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 Chapter 65: Examples of Spanning-Tree Protocols Configuration • Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches on page 1329 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches J-EX Series switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP). Loop protection increases the efficiency of STP, RSTP, and MSTP by preventing interfaces from moving into a forwarding state that would result in a loop opening up in the network. This example describes how to configure loop protection for an interface on a J-EX Series switch in an RSTP topology: • Requirements on page 1325 • Overview and Topology on page 1325 • Configuration on page 1327 • Verification on page 1327 Requirements This example uses the following hardware and software components: • Three J-EX Series switches in an RSTP topology Before you configure the interface for loop protection, be sure you have: • RSTP operating on the switches. NOTE: By default, RSTP is enabled on all J-EX Series switches. Overview and Topology A loop-free network in spanning-tree topologies is supported through the exchange of a special type of frame called bridge protocol data unit (BPDU). Peer STP applications running on the switch interfaces use BPDUs to communicate. Ultimately, the exchange of BPDUs determines which interfaces block traffic (preventing loops) and which interfaces become root ports and forward traffic. A blocking interface can transition to the forwarding state in error if the interface stops receiving BPDUs from its designated port on the segment. Such a transition error can occur when there is a hardware error on the switch or software configuration error between the switch and its neighbor. When this happens, a loop opens up in the spanning tree. Loops in a Layer 2 topology cause broadcast, unicast, and multicast frames to 1325 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS continuously circle the looped network. As a switch processes a flood of frames in a looped network, its resources become depleted and the ultimate result is a network outage. CAUTION: An interface can be configured for either loop protection or root protection, but not for both. Three J-EX Series switches are displayed in Figure 37 on page 1326. In this example, they are configured for RSTP and create a loop-free topology. Interface ge-0/0/6 is blocking traffic between Switch 3 and Switch 1; thus, traffic is forwarded through interface ge-0/0/7 on Switch 2. BPDUs are being sent from the root bridge on Switch 1 to both of these interfaces. This example shows how to configure loop protection on interface ge-0/0/6 to prevent it from transitioning from a blocking state to a forwarding state and creating a loop in the spanning-tree topology. Figure 37: Network Topology for Loop Protection Table 175 on page 1326 shows the components that will be configured for loop protection. Table 175: Components of the Topology for Configuring Loop Protection on J-EX Series Switches Property Settings Switch 1 Switch 1 is the root bridge. Switch 2 Switch 2 has the root port ge-0/0/7. Switch 3 Switch 3 is connected to Switch 1 through interface ge-0/0/6. 1326 Chapter 65: Examples of Spanning-Tree Protocols Configuration A spanning-tree topology contains ports that have specific roles: • The root port is responsible for forwarding data to the root bridge. • The alternate port is a standby port for the root port. When a root port goes down, the alternate port becomes the active root port. • The designated port forwards data to the downstream network segment or device. This configuration example uses an RSTP topology. However, you also can configure loop protection for STP or MSTP topologies at the [edit protocols (mstp | stp)] hierarchy level. Configuration To configure loop protection on an interface: CLI Quick Configuration To quickly configure loop protection on interface ge-0/0/6: Step-by-Step Procedure To configure loop protection: [edit] set protocols rstp interface ge-0/0/6 bpdu-timeout-action block 1. Configure interface ge-0/0/6 on Switch 3: [edit protocols rstp] user@switch# set interface ge-0/0/6 bpdu-timeout-action block Results Check the results of the configuration: user@switch> show configuration protocols rstp interface ge-0/0/6.0 { bpdu-timeout-action { block; } } Verification To confirm that the configuration is working properly, perform these tasks: • Displaying the Interface State Before Loop Protection Is Triggered on page 1327 • Verifying That Loop Protection Is Working on an Interface on page 1328 Displaying the Interface State Before Loop Protection Is Triggered Purpose Action Before loop protection is triggered on interface ge-0/0/6, confirm that the interface is blocking. Use the operational mode command: user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface Port ID Designated Designated Port State Role 1327 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/0.0 128:513 ge-0/0/1.0 128:514 ge-0/0/2.0 128:515 ge-0/0/3.0 128:516 ge-0/0/4.0 128:517 ge-0/0/5.0 128:518 ge-0/0/6.0 128:519 [output truncated] Meaning port ID 128:513 128:514 128:515 128:516 128:517 128:518 128:2 bridge ID 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 16384.00aabbcc0348 Cost 20000 20000 20000 20000 20000 20000 20000 BLK BLK BLK FWD FWD FWD BLK DIS DIS DIS DESG DESG DESG ALT The output from the operational mode command show spanning-tree interface shows that ge-0/0/6.0 is the alternate port and in a blocking state. Verifying That Loop Protection Is Working on an Interface Purpose Action Verify the loop protection configuration on interface ge-0/0/6. RSTP has been disabled on interface ge-0/0/4 on Switch 1. This will stop BPDUs from being sent to interface ge-0/0/6 and trigger loop protection on the interface. Use the operational mode command: user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface Port ID ge-0/0/0.0 128:513 ge-0/0/1.0 128:514 ge-0/0/2.0 128:515 ge-0/0/3.0 128:516 ge-0/0/4.0 128:517 ge-0/0/5.0 128:518 ge-0/0/6.0 128:519 (Loop-Incon) [output truncated] Meaning Related Documentation 1328 Designated port ID 128:513 128:514 128:515 128:516 128:517 128:518 128:519 Designated bridge ID 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 Port Cost 20000 20000 20000 20000 20000 20000 20000 State Role BLK BLK BLK FWD FWD FWD BLK DIS DIS DIS DESG DESG DESG DIS The operational mode command show spanning-tree interface shows that interface ge-0/0/6.0 has detected that BPDUs are no longer being forwarded to it and has moved into a loop-inconsistent state. The loop-inconsistent state prevents the interface from transitioning to a forwarding state. The interface recovers and transitions back to its original state as soon as it receives BPDUs. • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches on page 1329 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 Chapter 65: Examples of Spanning-Tree Protocols Configuration • Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1279 Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches J-EX Series switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP). Root protection increases the efficiency of STP, RSTP, and MSTP by allowing network administrators to manually enforce the root bridge placement in the network. This example describes how to configure root protection on an interface on a J-EX Series switch: • Requirements on page 1329 • Overview and Topology on page 1329 • Configuration on page 1331 • Verification on page 1332 Requirements This example uses the following hardware and software components: • Four J-EX Series switches in an RSTP topology Before you configure the interface for root protection, be sure you have: • RSTP operating on the switches. NOTE: By default, RSTP is enabled on all J-EX Series switches. Overview and Topology Peer STP applications running on switch interfaces exchange a special type of frame called a bridge protocol data unit (BPDU). Switches communicate interface information using BPDUs to create a loop-free topology that ultimately determines the root bridge and which interfaces block or forward traffic in the spanning tree. However, a root port elected through this process has the possibility of being wrongly elected. A user bridge application running on a PC can generate BPDUs, too, and interfere with root port election. To prevent this from happening, enable root protection on interfaces that should not receive superior BPDUs from the root bridge and should not be elected as the root port. These interfaces are typically located on an administrative boundary and are designated ports. When root protection is enabled on an interface: 1329 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • The interface is blocked from becoming the root port. • Root protection is enabled for all STP instances on that interface. • The interface is blocked only for instances for which it receives superior BPDUs. Otherwise, it participates in the spanning-tree topology. CAUTION: An interface can be configured for either root protection or loop protection, but not for both. Four J-EX Series switches are displayed in Figure 38 on page 1330. In this example, they are configured for RSTP and create a loop-free topology. Interface ge-0/0/7 on Switch 1 is a designated port on an administrative boundary. It connects to Switch 4. Switch 3 is the root bridge. Interface ge-0/0/6 on Switch 1 is the root port. This example shows how to configure root protection on interface ge-0/0/7 to prevent it from transitioning to become the root port. Figure 38: Network Topology for Root Protection 1330 Chapter 65: Examples of Spanning-Tree Protocols Configuration Table 176 on page 1331 shows the components that will be configured for root protection. Table 176: Components of the Topology for Configuring Root Protection on J-EX Series Switches Property Settings Switch 1 Switch 1 is connected to Switch 4 through interface ge-0/0/7. Switch 2 Switch 2 is connected to Switch 1 and Switch 3. Interface ge-0/0/4 is the alternate port in the RSTP topology. Switch 3 Switch 3 is the root bridge and is connected to Switch 1 and Switch 2. Switch 4 Switch 4 is connected to Switch 1. After loop protection is configured on interface ge-0/0/7, Switch 4 will send superior BPDUs that will trigger loop protection on interface ge-0/0/7. A spanning tree topology contains ports that have specific roles: • The root port is responsible for forwarding data to the root bridge. • The alternate port is a standby port for the root port. When a root port goes down, the alternate port becomes the active root port. • The designated port forwards data to the downstream network segment or device. This configuration example uses an RSTP topology. However, you also can configure root protection for STP or MSTP topologies at the [edit protocols (mstp | stp)] hierarchy level. Configuration To configure root protection on an interface: CLI Quick Configuration To quickly configure root protection on interface ge-0/0/7, copy the following command and paste it into the switch terminal window: [edit] set protocols rstp interface ge-0/0/7 no-root-port Step-by-Step Procedure To configure root protection: 1. Configure interface ge-0/0/7: [edit protocols rstp] user@switch# set interface ge-0/0/7 no-root-port Results Check the results of the configuration: user@switch> show configuration protocols rstp interface ge-0/0/7.0 { no-root-port; } 1331 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verification To confirm that the configuration is working properly: • Displaying the Interface State Before Root Protection Is Triggered on page 1332 • Verifying That Root Protection Is Working on the Interface on page 1332 Displaying the Interface State Before Root Protection Is Triggered Purpose Action Before root protection is triggered on interface ge-0/0/7, confirm the interface state. Use the operational mode command: user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface Port ID ge-0/0/0.0 128:513 ge-0/0/1.0 128:514 ge-0/0/2.0 128:515 ge-0/0/3.0 128:516 ge-0/0/4.0 128:517 ge-0/0/5.0 128:518 ge-0/0/6.0 128:519 ge-0/0/7.0 128:520 [output truncated] Meaning Designated port ID 128:513 128:514 128:515 128:516 128:517 128:2 128:1 128:520 Designated bridge ID 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 16384.00aabbcc0348 16384.00aabbcc0348 32768.0019e2503f00 Port Cost 20000 20000 20000 20000 20000 20000 20000 20000 State Role BLK BLK BLK FWD FWD BLK FWD FWD DIS DIS DIS DESG DESG ALT ROOT DESG The output from the operational mode command show spanning-tree interface shows that ge-0/0/7.0 is a designated port in a forwarding state. Verifying That Root Protection Is Working on the Interface Purpose Action A configuration change takes place on Switch 4. A smaller bridge priority on the Switch 4 causes it to send superior BPDUs to interface ge-0/0/7. Receipt of superior BPDUs on interface ge-0/0/7 will trigger root protection. Verify that root protection is operating on interface ge-0/0/7. Use the operational mode command: user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 ge-0/0/6.0 ge-0/0/7.0 1332 Port ID 128:513 128:514 128:515 128:516 128:517 128:518 128:519 128:520 Designated port ID 128:513 128:514 128:515 128:516 128:517 128:2 128:1 128:520 Designated bridge ID 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 32768.0019e2503f00 16384.00aabbcc0348 16384.00aabbcc0348 32768.0019e2503f00 Port Cost 20000 20000 20000 20000 20000 20000 20000 20000 State Role BLK BLK BLK FWD FWD BLK FWD BLK DIS DIS DIS DESG DESG ALT ROOT DIS Chapter 65: Examples of Spanning-Tree Protocols Configuration (Root—Incon) [output truncated] Meaning Related Documentation The operational mode command show spanning-tree interface shows that interface ge-0/0/7.0 has transitioned to a loop inconsistent state. The loop inconsistent state makes the interface block and prevents the interface from becoming a candidate for the root port. When the root bridge no longer receives superior STP BPDUs from the interface, the interface will recover and transition back to a forwarding state. Recovery is automatic. • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Understanding Root Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1280 1333 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1334 CHAPTER 66 Configuring Spanning-Tree Protocols • Unblocking an Interface That Receives BPDUs in Error (CLI Procedure) on page 1335 • Configuring STP (CLI Procedure) on page 1336 • Configuring Spanning-Tree Protocols (J-Web Procedure) on page 1336 • Configuring VLAN Spanning Tree Protocol (CLI Procedure) on page 1340 Unblocking an Interface That Receives BPDUs in Error (CLI Procedure) J-EX Series switches use bridge protocol data unit (BPDU) protection on interfaces to prevent them from receiving BPDUs that could trigger a spanning-tree misconfiguration. If BPDUs are received on a BPDU-protected interface, the interface transitions to a blocking state and stops forwarding frames. After the misconfiguration that triggered the BPDUs being sent to an interface is fixed in the topology, the interface can be unblocked and returned to service. To unblock an interface and return it to service using the CLI: • Automatically unblock an interface by configuring a timer that expires (here, the interface is ge-0/0/6): [edit ethernet-switching-options] user@switch# set bpdu-block disable-timeout 30 interface ge-0/0/6 • Manually unblock an interface using the operational mode command: user@switch> clear ethernet-switching bpdu-error interface ge-0/0/6 Related Documentation • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 1335 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring STP (CLI Procedure) The default spanning-tree protocol for J-EX Series switches is Rapid Spanning Tree Protocol (RSTP). RSTP provides faster convergence times than Spanning Tree Protocol (STP). However, some legacy networks require the slower convergence times of basic STP. If your network includes 802.1D 1998 bridges, you can remove RSTP and explicitly configure STP. When you explicitly configure STP, the J-EX Series switches use the IEEE 802.1D 2004 specification, force version 0. This configuration runs a version of RSTP that is compatible with the classic, basic STP. To configure STP using the CLI: 1. Delete the RSTP configuration on the interface (here, the interface is ge-0/0/5): [edit] user@switch# delete protocols rstp interface ge-0/0/5 2. Configure STP on the interface: [edit] user@switch# set protocols stp interface ge-0/0/5 3. Commit the configuration: [edit] user@switch# commit Related Documentation • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Understanding STP for J-EX Series Switches on page 1275 Configuring Spanning-Tree Protocols (J-Web Procedure) J-EX Series switches provide Layer 2 loop prevention through Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and VLAN Spanning Tree Protocol (VSTP). You can configure STP, RSTP, and MSTP using the J-Web interface. You can configure bridge protocol data unit (BPDU) protection on interfaces to prevent them from receiving BPDUs that could result in STP misconfigurations, which could lead to network outages. To configure STP, MSTP, or RSTP for a J-EX Series switch using the J-Web interface: 1. Select Configure > Switching > Spanning Tree. The Spanning Tree Configuration page displays the spanning-tree protocol configuration parameters and a list of interfaces configured for each spanning-tree protocol configuration. 1336 Chapter 66: Configuring Spanning-Tree Protocols 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 334 for details about all commit options. 2. Click one: • Add—Creates a spanning-tree protocol configuration. a. Select a protocol name. b. Enter information as described in Table 177 on page 1337. c. Click OK to apply changes to the configuration or click Cancel to cancel without saving changes. • Edit—Modifies a selected spanning-tree protocol configuration. a. Enter information as described in Table 177 on page 1337. b. Click OK to apply changes to the configuration or click Cancel to cancel without saving changes. • Delete—Deletes a selected spanning-tree protocol configuration. Table 177: Spanning-Tree Protocol Configuration Parameters Field Function Your Action Protocol Name Specifies the spanning-tree protocol type: STP, MSTP, or RSTP. None. Disable Disables spanning-tree protocol on the interface. To enable this option, select the check box. BPDU Protect Specifies BPDU protection on all edge interfaces on the switch. To enable this option, select the check box. Bridge Priority Specifies the bridge priority. The bridge priority determines which bridge is elected as the root bridge. If two bridges have the same path cost to the root bridge, the bridge priority determines which bridge becomes the designated bridge for a LAN segment. Select a value from the list. Forward Delay Specifies the number of seconds an interface waits before changing from spanning-tree learning and listening states to the forwarding state. Type a value. Hello Time Specifies the time interval in seconds at which the root bridge transmits configuration BPDUs. Type a value. General 1337 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 177: Spanning-Tree Protocol Configuration Parameters (continued) Field Function Your Action Max Age Specifies the maximum-aging time in seconds for all MST instances. The maximum aging time is the number of seconds a switch waits without receiving spanning-tree configuration messages before attempting a reconfiguration. Type a value. Max Hops (MSTP only) Specifies the number of hops in a region before the BPDU is discarded. Type a value. Configuration Name (MSTP only) Specifies the MSTP region name carried in the MSTP BPDUs. Type a name. Revision Level (MSTP only) Specifies the revision number of the MSTP configuration. Type a value. Specifies an interface for the spanning-tree protocol. 1. Ports Interface Name Click the Ports tab. 2. Choose one: • Click Add and select an interface from the list. • Select an interface in the Port/State table and click Edit. • To delete an interface from the configuration, select it in the Port/State table and click Remove. Cost Specifies the link cost to determine which bridge is the designated bridge and which interface is the designated interface. Type a value. Priority Specifies the interface priority to determine which interface is elected as the root port. Select a value from the list. Disable Port Disables the spanning-tree protocol on the interface. To enable the option, select the check box. Edge Configures the interface as an edge interface. Edge interfaces immediately transition to a forwarding state. To enable the option, select the check box. No Root Port Specifies an interface as a spanning-tree designated port. If the bridge receives superior STP BPDUs on a root-protected interface, that interface transitions to a root-prevented STP state (inconsistency state) and the interface is blocked. This blocking prevents a bridge that should not be the root bridge from being elected the root bridge. When the bridge stops receiving superior STP BPDUs on the root-protected interface, interface traffic is no longer blocked. To enable the option, select the check box. 1338 Chapter 66: Configuring Spanning-Tree Protocols Table 177: Spanning-Tree Protocol Configuration Parameters (continued) Field Function Your Action Interface Mode Specifies the link mode. 1. To enable the option, select the check box. 2. Select one: • Point to Point–For a full-duplex link, the default link mode is point-to-point. • Shared–For a half-duplex link, the default link mode is shared. BPDU Timeout Action Specifies the BPDU timeout action for the interface. Select one: • Alarm • Block MSTI (MSTP only) MSTI Name Specifies a name (an MSTI ID) for the MST instance. 1. Click the MSTI tab. 2. Choose one: • Click Add. • Select an MSTI ID and click Edit. • To delete an MSTI from the configuration, select the MSTI ID and slick Remove. Bridge Priority Specifies the bridge priority. The bridge priority determines which bridge is elected as the root bridge. If two bridges have the same path cost to the root bridge, the bridge priority determines which bridge becomes the designated bridge for a LAN segment. Select a value from the list. VLAN ID Specifies the VLAN for the MST instance. In the VLAN box, choose one: • Click Add, select a VLAN from the list and click OK. • To remove a VLAN association, select the VLAN ID, click Remove, and click OK. 1339 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 177: Spanning-Tree Protocol Configuration Parameters (continued) Field Function Your Action Interfaces Specifies an interface for the MST instance. 1. In the Interfaces box, click Add and select an interface from the list, or select an interface from the list and click Edit. 2. Specify the link cost to determine which bridge is the designated bridge and which interface is the designated interface. 3. Specify the interface priority to determine which interface is elected as the root port. 4. If you want to disable the interface, select the check box. 5. Click OK. To delete an interface configuration, select the interface, click Remove, and click OK. Related Documentation • Configuring STP (CLI Procedure) on page 1336 • Monitoring Spanning-Tree Protocols on page 1343 • Unblocking an Interface That Receives BPDUs in Error (CLI Procedure) on page 1335 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 Configuring VLAN Spanning Tree Protocol (CLI Procedure) VLAN Spanning Tree Protocol (VSTP) allows J-EX Series switches to run one or more Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP) instances for each VLAN on which VSTP is enabled. For networks with multiple VLANs, VSTP improves intelligent tree spanning by defining best paths within the VLANs instead of within the entire network. To configure VSTP: 1. (Optional) Enable Rapid Spanning Tree Protocol (RSTP): [edit protocols] user@switch# set rstp VSTP can run on a maximum of 253 VLANs; RSTP runs on the remaining VLANs if configured. Enabling RSTP ensures that a spanning-tree protocol runs on all VLANs. 2. Enable VSTP. 1340 Chapter 66: Configuring Spanning-Tree Protocols • To enable VSTP on multiple VLANs using a VLAN group: [edit protocols] user@switch# set vstp vlan-group group group-name vlan vlan-id-range • To enable VSTP on all VLANs: [edit protocols] user@switch# set vstp vlan all NOTE: RSTP must be enabled if the set vstp vlan all statement is used to enable VSTP and the switch has more than 253 VLANs. If the set vstp vlan all statement is used to enable VSTP on a switch with more than 253 VLANs, the configuration cannot be committed. • To enable VSTP on a VLAN using a single VLAN ID: [edit protocols] user@switch# set vstp vlan vlan-id • To enable VSTP on a VLAN using a single VLAN name: [edit protocols] user@switch# set vstp vlan vlan-name Related Documentation • Understanding VSTP for J-EX Series Switches on page 1281 1341 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1342 CHAPTER 67 Verifying Spanning Tree Protocols • Monitoring Spanning-Tree Protocols on page 1343 Monitoring Spanning-Tree Protocols Purpose Action Use the monitoring feature to view status and information about the spanning-tree protocol parameters on your J-EX Series switch. To display spanning-tree protocol parameter details in the J-Web interface, select Monitor > Switching > STP. To display spanning-tree protocol parameter details in the CLI, enter the following commands: Meaning • show spanning-tree interface • show spanning-tree bridge Table 178 on page 1343 summarizes the spanning-tree protocol parameters. Table 178: Summary of Spanning-Tree Protocols Output Fields Field Values Bridge Parameters Context ID An internally generated identifier. Enabled Protocol Spanning-tree protocol type enabled. Root ID Bridge ID of the elected spanning-tree root bridge. The bridge ID consists of a configurable bridge priority and the MAC address of the bridge. Bridge ID Locally configured bridge ID. Hello Time The time for which the bridge interface remains in the listening or learning state. Forward Delay The time for which the bridge interface remains in the listening or learning state before transitioning to the forwarding state. 1343 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 178: Summary of Spanning-Tree Protocols Output Fields (continued) Field Values Extended System ID The system ID. Inter Instance ID An internally generated instance identifier. Maximum Age Maximum age of received bridge protocol data units (BPDUs). Number of topology changes Total number of STP topology changes detected since the switch last booted. Spanning Tree Interface Details Interface Name Interface configured to participate in the STP instance. Port ID Logical interface identifier configured to participate in the STP instance. Designated Port ID Port ID of the designated port for the LAN segment to which the interface is attached. Designated Bridge ID ID of the designated bridge to which the interface is attached. Port Cost Configured cost for the interface. Port State STP port state: Role • Forwarding (FWD) • Blocking (BLK) • Listening • Learning • Disabled MSTP or RSTP port role, Designated (DESG), backup (BKUP), alternate (ALT), or root. Spanning Tree Statistics of Interface Interface Interface for which statistics is being displayed. BPDUs Sent Total number of BPDUs sent. BPDUs Received Total number of BPDUs received. Next BPDU Transmission Number of seconds until the next BPDU is scheduled to be sent. Related Documentation 1344 • show spanning-tree interface on page 1407 • show spanning-tree bridge on page 1398 • Configuring Spanning-Tree Protocols (J-Web Procedure) on page 1336 • Configuring STP (CLI Procedure) on page 1336 Chapter 67: Verifying Spanning Tree Protocols • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 1345 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1346 CHAPTER 68 Configuration Statements for Spanning-Tree Protocols • [edit protocols] Configuration Statement Hierarchy on page 1347 [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; 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); } } gvrp { 1347 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ; interface (all | [interface-name]) { disable; } join-timer millseconds; leave-timer milliseconds; leaveall-timer milliseconds; } 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 { 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; } traceoptions { file filename ; flag flag (detail | disable | receive | send); } } lldp-med { 1348 Chapter 68: Configuration Statements for Spanning-Tree Protocols 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } 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; 1349 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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); loss-threshold number; } mep mep-id { auto-discovery; direction down; interface interface-name; remote-mep mep-id { action-profile profile-name; } } } } } link-fault-management { 1350 Chapter 68: Configuration Statements for Spanning-Tree Protocols 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; 1351 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } sflow { agent-id collector { ip-address; udp-port port-number; } disable; interfaces interface-name { disable; polling-interval seconds; sample-rate number; } polling-interval seconds; sample-rate number; source-ip } stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; } 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 { alarm; block; } cost cost; 1352 Chapter 68: Configuration Statements for Spanning-Tree Protocols disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } } Related Documentation • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding MAC RADIUS Authentication on J-EX Series Switches • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Ethernet OAM Connectivity Fault Management for a J-EX Series Switch on page 3463 • Understanding Ethernet OAM Link Fault Management for a J-EX Series Switch on page 3427 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding How to Use sFlow Technology for Network Monitoring on a J-EX Series Switch on page 3283 • Understanding VSTP for J-EX Series Switches on page 1281 1353 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS alarm Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1354 alarm; [edit protocols mstp interface (all | interface-name) bpdu-timeout-action], [edit protocols rstp interface (all | interface-name) bpdu-timeout-action], [edit protocols stp interface (all | interface-name) bpdu-timeout-action], [edit protocols vstp vlan vlan-id interface (all | interface-name) bpdu-timeout-action] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For interfaces configured for loop protection, configure the software to generate a message to be sent to the system log file to record the loop-protection event. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1279 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols block Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation block; [edit protocols mstp interface (all | interface-name) bpdu-timeout-action], [edit protocols rstp interface (all | interface-name) bpdu-timeout-action], [edit protocols stp interface (all | interface-name) bpdu-timeout-action], [edit protocols vstp vlan vlan-id interface (all | interface-name) bpdu-timeout-action] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure loop protection on a specific interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1279 • Understanding VSTP for J-EX Series Switches on page 1281 1355 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bpdu-block Syntax Hierarchy Level Release Information Description bpdu-block { interface (all | [interface-name]); disable-timeout timeout; } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure BPDU protection on an interface. If the interface receives BPDUs, it is disabled. The statements are explained separately. Required Privilege Level Related Documentation 1356 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • clear ethernet-switching bpdu-error on page 1390 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Unblocking an Interface That Receives BPDUs in Error (CLI Procedure) on page 1335 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 Chapter 68: Configuration Statements for Spanning-Tree Protocols bpdu-block-on-edge Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation bpdu-block-on-edge; [edit protocols mstp], [edit protocols rstp], [edit protocols vstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure bridge protocol data unit (BPDU) protection on all edge ports of a switch. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • clear ethernet-switching bpdu-error on page 1390 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Understanding VSTP for J-EX Series Switches on page 1281 1357 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bpdu-timeout-action Syntax Hierarchy Level Release Information Description bpdu-timeout-action { block; alarm; } [edit protocols mstp interface (all | interface-name)], [edit protocols rstp interface (all | interface-name)], [edit protocols stp interface (all | interface-name)], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the BPDU timeout action on a specific interface. You must configure at least one action (alarm, block, or both). The remaining statements are explained separately. Required Privilege Level Related Documentation 1358 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to Forwarding in a Spanning Tree on J-EX Series Switches on page 1325 • Understanding Loop Protection for STP, RSTP, VSTP, and MSTP on J-EX Series Switches on page 1279 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols bridge-priority Syntax Hierarchy Level Release Information Description Default Options bridge-priority priority; [edit protocols mstp], [edit protocols mstp msti msti-id], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the bridge priority. The bridge priority determines which bridge is elected as the root bridge. If two bridges have the same path cost to the root bridge, the bridge priority determines which bridge becomes the designated bridge for a LAN segment. 32,768 priority—Bridge priority. It can be set only in increments of 4096. Range: 0 through 61,440 Default: 32,768 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 1359 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS configuration-name Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1360 configuration-name configuration-name; [edit protocols mstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the configuration name. The configuration name is the MSTP region name carried in the MSTP BPDUs. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 Chapter 68: Configuration Statements for Spanning-Tree Protocols cost Syntax Hierarchy Level Release Information Description Default Options cost cost; [edit protocols mstp interface (all | interface-name)], [edit protocols mstp msti msti-id interface interface-name], [edit protocols rstp interface (all | interface-name)], [edit protocols stp interface (all | interface-name)], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), configure the link cost to control which bridge is the designated bridge and which interface is the designated interface. The link cost is determined by the link speed. cost—Link cost associated with the port. Range: 1 through 200,000,000 Default: Link cost is determined by the link speed. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Understanding STP for J-EX Series Switches on page 1275 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 1361 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1362 disable; [edit protocols mstp], [edit protocols mstp interface interface-name], [edit protocols mstp msti msti-id vlan (vlan-id | vlan-name) interface interface-name], [edit protocols rstp], [edit protocols rstp interface interface-name], [edit protocols stp], [edit protocols stp interface interface-name], [edit protocols vstp], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable STP, MSTP, RSTP, or VSTP on the switch or on a specific interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols disable-timeout Syntax Hierarchy Level Release Information Description Default Options disable-timeout timeout; [edit ethernet-switching-options bpdu-block] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For interfaces configured for BPDU protection, specify the amount of time an interface receiving BPDUs is disabled. The disable timeout is not enabled. timeout —Amount of time, in seconds, the interface receiving BPDUs is disabled. Once the timeout expires, the interface is brought back into service. Range: 10 through 3600 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 1363 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS edge Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 1364 edge; [edit protocols mstp interface (all | interface-name)], [edit protocols mstp msti msti-id interface interface-name], [edit protocols rstp interface (all | interface-name)], [edit protocols stp interface (all | interface-name)], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), configure interfaces as edge interfaces. Edge interfaces immediately transition to a forwarding state. Edge interfaces are not enabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols force-version Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation force-version stp; [edit protocols vstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Force VLAN Spanning Tree Protocol (VSTP) to use the STP protocol instead of the default protocol, RSTP. stp—Spanning Tree Protocol routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Understanding VSTP for J-EX Series Switches on page 1281 1365 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS forward-delay Syntax Hierarchy Level Release Information Description Default Options forward-delay seconds; [edit protocols mstp], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), specify how long a bridge interface remains in the listening and learning states before transitioning to the forwarding state. 15 seconds seconds—Number of seconds the bridge interface remains in the listening and learning states. Range: 4 through 30 seconds Default: 15 seconds Required Privilege Level Related Documentation 1366 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols hello-time Syntax Hierarchy Level Release Information Description Default Options hello-time seconds; [edit protocols mstp], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), specify the time interval at which the root bridge transmits configuration BPDUs. 2 seconds seconds—Number of seconds between transmissions of configuration BPDUs. Range: 1 through 10 seconds Default: 2 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 1367 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Options interface (all | [interface-name]); [edit ethernet-switching-options bpdu-block] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply BPDU protection to all interfaces or one or more interfaces. all—All interfaces. interface-name —Name of a Gigabit Ethernet interface. Required Privilege Level Related Documentation 1368 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Example: Configuring BPDU Protection on non-STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1321 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 Chapter 68: Configuration Statements for Spanning-Tree Protocols interface Syntax Hierarchy Level Release Information Description interface interface-name { disable; cost cost; edge; mode mode; no-root-port; priority priority; } [edit protocols mstp], [edit protocols mstp msti msti-id], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), configure an interface. The edge, mode, and no-root-port options are not available at the [edit protocols mstp msti msti-id] hierarchy level. Options interface-name—Name of a Gigabit Ethernet interface. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 1369 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS max-age Syntax Hierarchy Level Release Information Description Default Options max-age seconds; [edit protocols mstp], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), specify the maximum age of received protocol BPDUs. 20 seconds seconds—The maximum age of received protocol BPDUs. Range: 6 through 40 seconds Default: 20 seconds Required Privilege Level Related Documentation 1370 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols max-hops Syntax Hierarchy Level Release Information Description Default Options max-hops hops; [edit protocols mstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Multiple Spanning Tree Protocol (MSTP), configure the maximum number of hops a BPDU can be forwarded in the MSTP region. 20 hops hops — Number of hops the BPDU can be forwarded. Range: 1 through 255 hops Default: 20 hops Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding MSTP for J-EX Series Switches on page 1277 1371 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mode Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation 1372 mode mode; [edit protocols mstp interface (all | interface-name)], [edit protocols mstp msti msti-id interface interface-name], [edit protocols rstp interface (all | interface-name)], [edit protocols stp interface (all | interface-name)], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), configure the link mode to identify point-to-point links. For a full-duplex link, the default link mode is point-to-point. For a half-duplex link, the default link mode is shared. mode—Link mode: • point-to-point—Link is point to point. • shared—Link is shared media. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols msti Syntax Hierarchy Level Release Information Description Default Options msti msti-id { vlan (vlan-id | vlan-name); interface interface-name { disable; cost cost; priority priority; } } [edit protocols mstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Multiple Spanning Tree Instance (MSTI) identifier for Multiple Spanning Tree Protocol (MSTP). MSTI IDs are local to each region, so you can reuse the same MSTI ID in different regions. MSTI is disabled. msti-id —MSTI identifier. Range: 1 through 4094. The Common Instance Spanning Tree (CIST) is always MSTI 0. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding MSTP for J-EX Series Switches on page 1277 1373 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mstp Syntax Hierarchy Level Release Information Description mstp { disable; bpdu-block-on-edge; bridge-priority priority; configuration-name name; forward-delay seconds; hello-time seconds; interface ( all | interface-name { bpdu-timeout-action { block; alarm; } disable; cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; max-hops hops; msti msti-id { vlan (vlan-id | vlan-name); interface interface-name { disable; cost cost; priority priority; } } traceoptions { file filename ; flag flag; } revision-level revision-level; } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Multiple Spanning Tree Protocol (MSTP). MSTP is defined in the IEEE 802.1Q-2003 specification and is used to create a loop-free topology in networks with multiple spanning tree regions. The statements are explained separately. Default Required Privilege Level 1374 MSTP is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 68: Configuration Statements for Spanning-Tree Protocols Related Documentation • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding MSTP for J-EX Series Switches on page 1277 no-root-port Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-root-port; [edit protocols mstp interface (all | interface-name)], [edit protocols rstp interface (all | interface-name)], [edit protocols stp interface (all | interface-name)], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an interface to be a spanning tree designated port. If the bridge receives superior STP bridge protocol data units (BPDUs) on a root-protected interface, that interface transitions to a root-prevented STP state (inconsistency state) and the interface is blocked. This blocking prevents a bridge that should not be the root bridge from being elected the root bridge. When the bridge stops receiving superior STP BPDUs on the root-protected interface, interface traffic is no longer blocked. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on J-EX Series Switches on page 1329 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding VSTP for J-EX Series Switches on page 1281 1375 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS priority Syntax Hierarchy Level Release Information Description Default Options priority priority; [edit protocols mstp interface (all | interface-name)], [edit protocols mstp msti msti-id interface interface-name], [edit protocols rstp interface (all | interface-name)], [edit protocols stp interface (all | interface-name)], [edit protocols vstp vlan vlan-id interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning Tree Protocol (MSTP), specify the interface priority to control which interface is elected as the root port. The default value is 128. priority—Interface priority. The interface priority must be set in increments of 16. Range: 0 through 240 Required Privilege Level Related Documentation 1376 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols revision-level Syntax Hierarchy Level Release Information Description Default Options revision-level revision-level; [edit protocols mstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Multiple Spanning Tree Protocol (MSTP), set the revision number of the MSTP configuration. The revision level is disabled. revision-level —Revision number of the MSTP region configuration. Range: 0 through 65535 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding MSTP for J-EX Series Switches on page 1277 1377 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rstp Syntax Hierarchy Level Release Information Description rstp { disable; bpdu-block-on-edge; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action{ alarm; block; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Rapid Spanning Tree Protocol (RSTP). RSTP is defined in the IEEE 802.1D-2004 specification and is used to prevent loops in Layer 2 networks, which results in shorter convergence times than those provided by basic Spanning Tree Protocol (STP). VSTP and RSTP can be configured concurrently. You can selectively configure up to 253 VLANs using VSTP; the remaining VLANs will be configured using RSTP. VSTP and RSTP are the only spanning-tree protocols that can be configured concurrently on the switch. See Configuring VSTP (CLI Procedure) for more information on configuring VSTP and RSTP concurrently. BEST PRACTICE: Configure RSTP when you configure VSTP. RSTP overhead is minimal and this configuration ensures that a spanning-tree protocol is running on all VLANs on your switch, even when your switch is supporting more than 253 VLANs. The remaining statements are explained separately. Default 1378 RSTP is enabled on all Ethernet switching interfaces. Chapter 68: Configuration Statements for Spanning-Tree Protocols Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding RSTP for J-EX Series Switches on page 1276 1379 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS stp Syntax Hierarchy Level Release Information Description stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. When you explicitly configure STP, the J-EX Series switches use the IEEE 802.1D 2004 specification, force version 0. This configuration runs a version of RSTP that is compatible with the classic, basic STP (defined in the IEEE 802.1D 1998 specification). The remaining statements are explained separately. Default Required Privilege Level Related Documentation 1380 STP is disabled; by default, RSTP is enabled on all Ethernet switching ports. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring BPDU Protection on STP Interfaces to Prevent STP Miscalculations on J-EX Series Switches on page 1317 • Configuring STP (CLI Procedure) on page 1336 • Understanding STP for J-EX Series Switches on page 1275 Chapter 68: Configuration Statements for Spanning-Tree Protocols traceoptions Syntax Hierarchy Level Release Information Description Default Options traceoptions { file name <(world-readable | no-world-readable)>; flag flag ; } [edit protocols mstp], [edit protocols rstp], [edit protocols stp], [edit protocols vstp vlan vlan-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set protocol-level tracing options for STP, RSTP, MSTP, and VSTP. Traceoptions is disabled. disable—(Optional) Disable the tracing operation. One use of this option is to disable a single operation when you have defined a broad group of tracing operations, such as all. file name —Name of the file to receive the output of the tracing operation. Enclose the name in quotation marks. We recommend that you place STP tracing output in the file /var/log/stp-log. 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. Range: 2 through 1000 files Default: 1 trace file only flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements: • all —Trace all operations. • all-failures—Trace all failure conditions. • bpdu —Trace BPDU reception and transmission. Note that you must also use port-transmit-state-machine in order to log transmit operations. • bridge-detection-state-machine —Trace the bridge detection state machine. • events —Trace events of the protocol state machine. 1381 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • port-information-state-machine —Trace the port information state machine. • port-migration-state-machine —Trace the port migration state machine. • port-receive-state-machine —Trace the port receive state machine. • port-role-select-state-machine —Trace the port role selection state machine. • port-role-transit-state-machine —Trace the port role transit state machine. • port-state-transit-state-machine —Trace the port state transit state machine. • port-transmit-state-machine —Trace the port transmit state machine • ppmd —Trace the state and events for the ppmd process • state-machine-variables —Trace when the state machine variables change • timers —Trace protocol timers • topology-change-state-machine —Trace the topology change state machine. no-stamp—(Optional) Do not place timestamp information at the beginning of each line in the trace file. Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output. no-world-readable—(Optional) Prevent aney user from reading the log file. replace—(Optional) Replace an existing trace file if there is one. Default: If you do not include this option, tracing output is appended to an existing trace file. size size —(Optional) Maximum size of each trace file, in kilobytes (KB) or megabytes (MB). 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 must also specify a maximum number of trace files with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 1 MB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level 1382 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 68: Configuration Statements for Spanning-Tree Protocols Related Documentation • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Example: Configuring Faster Convergence and Improving Network Stability with RSTP on J-EX Series Switches on page 1283 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding VSTP for J-EX Series Switches on page 1281 1383 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan Syntax Hierarchy Level Release Information Description vlan (vlan-id | vlan-name) { bridge-priority priority; forward-delay seconds; hello-time seconds; interface interface-name { bpdu-timeout-action { alarm; block; } cost cost; disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } [edit protocols mstp msti msti-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the VLANs for a Multiple Spanning Tree Instance (MSTI). TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Default Options Not enabled. vlan-id—Numeric VLAN identifier. vlan-name—Name of the VLAN. The remaining statements are explained separately. Required Privilege Level Related Documentation 1384 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 Chapter 68: Configuration Statements for Spanning-Tree Protocols • Understanding MSTP for J-EX Series Switches on page 1277 1385 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan (VSTP) Syntax Hierarchy Level Release Information Description vlan (all | vlan-id | vlan-name) { bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { bpdu-timeout-action { alarm; block; } cost cost; disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } [edit protocols vstp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure VSTP VLAN parameters. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Options all—All VLANs. vlan-id—Numeric VLAN identifier. vlan-name—Name of the VLAN. The remaining statements are explained separately. Required Privilege Level Related Documentation 1386 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 68: Configuration Statements for Spanning-Tree Protocols vstp Syntax Hierarchy Level Release Information Description vstp { bpdu-block-on-edge; disable; force-version stp; vlan (vlan-id | vlan-name) { bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action{ alarm; block; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure VLAN Spanning Tree Protocol (VSTP). VSTP is used to prevent loops in Layer 2 networks on a per-VLAN basis. You cannot commit a configuration that uses VSTP on more than 253 VLANs. If there are more than 253 VLANs on your switch, you must use the vlan statement to specify which VLANs or VLAN groups should use VSTP, and the total number of VLANs using VSTP cannot exceed 253. You also cannot use the vlan all option to configure VSTP when your switch has more than 253 VLANs. Run RSTP with VSTP in networks with large numbers of VLANs to ensure all VLANs are running a spanning-tree protocol. BEST PRACTICE: Configure RSTP when you configure VSTP. RSTP overhead is minimal and this configuration ensures that a spanning-tree protocol is running on all VLANs on your switch, even when your switch is supporting more than 253 VLANs. 1387 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS The remaining statements are explained separately. Default Required Privilege Level Related Documentation 1388 VSTP is not enabled by default. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Configuring VLAN Spanning Tree Protocol (CLI Procedure) on page 1340 • Understanding VSTP for J-EX Series Switches on page 1281 CHAPTER 69 Operational Mode Commands for Spanning-Tree Protocols 1389 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear ethernet-switching bpdu-error Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output clear ethernet-switching bpdu-error interface ge-0/0/1.0 1390 clear ethernet-switching bpdu-error interface interface-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear bridge protocol data unit (BPDU) errors from an interface and unblock the interface. interface-name —Clear BPDU errors on the specified interface. clear • show spanning-tree statistics on page 1416 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 clear ethernet-switching bpdu-error interface ge-0/0/1.0 on page 1390 user@switch> clear ethernet-switching bpdu-error interface ge-0/0/1.0 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols clear spanning-tree statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear spanning-tree statistics clear spanning-tree statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Spanning Tree Protocol statistics. none—Reset STP counters for all interfaces for all routing instances. interface interface-name—(Optional) Clear STP statistics for the specified interface only. logical-system logical-system-name—(Optional) Clear STP statistics on a particular logical system. Required Privilege Level Related Documentation List of Sample Output clear stp statistics clear • show spanning-tree statistics on page 1414 clear stp statistics on page 1391 user@host> clear stp statistics 1391 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear spanning-tree statistics Syntax Release Information Description Options clear spanning-tree statistics ; Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reset STP statistics for the all interfaces or a specified interface. none—Reset STP counters for all interfaces. interface-name —(Optional) The name of the interface for which statistics should be reset. logical-unit-number —(Optional) The logical unit number of the interface. Required Privilege Level Related Documentation List of Sample Output Output Fields clear spanning-tree statistics 1392 clear • show spanning-tree bridge on page 1398 • show spanning-tree interface on page 1407 • Understanding STP for J-EX Series Switches on page 1275 clear spanning-tree statistics on page 1392 This command produces no output. user@switch> clear spanning—tree statistics Chapter 69: Operational Mode Commands for Spanning-Tree Protocols show spanning-tree bridge Syntax Syntax (J-EX Series Switch) Release Information Description Options show spanning-tree bridge show spanning-tree bridge Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the configured or calculated Spanning Tree Protocol (STP) parameters. none—(Optional) Display brief STP bridge information for all multiple spanning-tree instances (MSTIs). brief | detail—(Optional) Display the specified level of output. msti msti-id—(Optional) Display STP bridge information for the specified MSTI. routing-instance routing-instance-name—(Optional) Display STP bridge information for the specified routing instance. vlan-id vlan-id—(Optional) Display STP bridge information for the specified VLAN. Required Privilege Level List of Sample Output Output Fields view show spanning-tree bridge routing-instance on page 1394 show spanning-tree bridge msti on page 1395 show spanning-tree bridge vlan-id (MSTP) on page 1395 show spanning-tree bridge (VSTP) on page 1396 show spanning-tree bridge vlan-id (VSTP) on page 1397 Table 179 on page 1393 lists the output fields for the show spanning-tree bridge command. Output fields are listed in the approximate order in which they appear. Table 179: show spanning-tree bridge Output Fields Field Name Field Description Routing instance name Name of the routing instance under which the bridge is configured. Enabled protocol Spanning Tree Protocol type enabled. Root ID Bridge ID of the elected spanning tree root bridge. The bridge ID consists of a configurable bridge priority and the MAC address of the bridge. 1393 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 179: show spanning-tree bridge Output Fields (continued) show spanning-tree bridge routing-instance Field Name Field Description Root cost Calculated cost to reach the root bridge from the bridge where the command is entered. Root port Interface that is the current elected root port for this bridge. CIST regional root Bridge ID of the elected MSTP regional root bridge. CIST internal root cost Calculated cost to reach the regional root bridge from the bridge where the command is entered. Hello time Configured number of seconds between transmissions of configuration bridge protocol data units (BPDUs). Maximum age Configured maximum expected arrival time of hello bridge protocol data units (BPDUs). Forward delay Configured time an STP bridge port remains in the listening and learning states before transitioning to the forwarding state. Hop count Configured maximum number of hops a BPDU can be forwarded in the MSTP region. Message age Number of elapsed seconds since the most recent BPDU was received. Number of topology changes Total number of STP topology changes detected since the routing device last booted. Time since last topology change Number of elapsed seconds since the most recent topology change. Bridge ID (Local) Locally configured bridge ID. The bridge ID consists of a configurable bridge priority and the MAC address of the bridge. Extended system ID System identifier. MSTI regional root Bridge ID of the elected MSTP regional root bridge. user@host> show spanning-tree bridge routing-instance vs1 detail STP bridge parameters Routing instance name : vs1 Enabled protocol : MSTP STP bridge parameters for CIST Root ID Root cost Root port CIST regional root CIST internal root cost Hello time 1394 : : : : : : 32768.00:13:c3:9e:c8:80 0 xe-10/2/0 32768.00:13:c3:9e:c8:80 22000 2 seconds Chapter 69: Operational Mode Commands for Spanning-Tree Protocols Maximum age Forward delay Hop count Message age Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID STP bridge parameters for MSTI 1 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID STP bridge parameters for MSTI 2 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID show spanning-tree bridge msti 20 seconds 15 seconds 18 0 1 1191 seconds : 32768.00:90:69:0b:7f:d1 : 1 : : : : : : : : : 32769.00:13:c3:9e:c8:80 22000 xe-10/2/0 2 seconds 20 seconds 15 seconds 18 1 1191 seconds : 32769.00:90:69:0b:7f:d1 : 1 : : : : : : : : : 32770.00:13:c3:9e:c8:80 22000 xe-10/2/0 2 seconds 20 seconds 15 seconds 18 1 1191 seconds : 32770.00:90:69:0b:7f:d1 : 1 user@host> show spanning-tree bridge msti 1 routing-instance vs1 detail STP bridge parameters Routing instance name : vs1 Enabled protocol : MSTP STP bridge parameters for MSTI 1 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID show spanning-tree bridge vlan-id (MSTP) : : : : : : : : : : : : : : : 32769.00:13:c3:9e:c8:80 22000 xe-10/2/0 2 seconds 20 seconds 15 seconds 18 1 1191 seconds : 32769.00:90:69:0b:7f:d1 : 1 user@host> show spanning-tree bridge vlan-id 1 101 routing-instance vs1 detail STP bridge parameters Routing instance name : vs1 Enabled protocol : MSTP 1395 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS STP bridge parameters for CIST Root ID Root cost Root port CIST regional root CIST internal root cost Hello time Maximum age Forward delay Hop count Message age Number of topology changes Local parameters Bridge ID Extended system ID Hello time Maximum age Forward delay Path cost method Maximum hop count show spanning-tree bridge (VSTP) user@host> show spanning-tree bridge STP bridge parameters Routing instance name Enabled protocol Root ID Hello time Maximum age Forward delay Message age Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID : : : : : : : : : : : 32768.00:13:c3:9e:c8:80 0 xe-10/2/0 32768.00:13:c3:9e:c8:80 22000 2 seconds 20 seconds 15 seconds 18 0 0 : : : : : : : 32768.00:90:69:0b:7f:d1 1 2 seconds 20 seconds 15 seconds 32 bit 20 : : : : : : : : : GLOBAL RSTP 28672.00:90:69:0b:3f:d0 2 seconds 20 seconds 15 seconds 0 58 14127 seconds : 28672.00:90:69:0b:3f:d0 : 0 STP bridge parameters for bridge VLAN 10 Root ID : 28672.00:90:69:0b:3f:d0 Hello time : 2 seconds Maximum age : 20 seconds Forward delay : 15 seconds Message age : 0 Number of topology changes : 58 Time since last topology change : 14127 seconds Local parameters Bridge ID : 28672.00:90:69:0b:3f:d0 Extended system ID : 0 STP bridge parameters for bridge VLAN 20 Root ID : 28672.00:90:69:0b:3f:d0 Hello time : 2 seconds Maximum age : 20 seconds Forward delay : 15 seconds Message age : 0 Number of topology changes : 58 Time since last topology change : 14127 seconds Local parameters 1396 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols Bridge ID Extended system ID show spanning-tree bridge vlan-id (VSTP) : 28672.00:90:69:0b:3f:d0 : 0 user@host> show spanning-tree bridge vlan-id 10 STP bridge parameters Routing instance name : GLOBAL Enabled protocol : RSTP STP bridge parameters for VLAN 10 Root ID Hello time Maximum age Forward delay Message age Number of topology changes Time since last topology change Local parameters Bridge ID Extended system ID : : : : : : : 28672.00:90:69:0b:3f:d0 2 seconds 20 seconds 15 seconds 0 58 14127 seconds : 28672.00:90:69:0b:3f:d0 : 0 1397 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show spanning-tree bridge Syntax Release Information Description Options show spanning-tree bridge Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the configured or calculated spanning-tree protocol (can be either STP, RSTP, or MSTP) parameters. none—(Optional) Display brief STP bridge information for all Multiple Spanning Tree Instances (MSTIs). brief | detail—(Optional) Display the specified level of output. msti msti-id—(Optional) Display STP bridge information for the specified MSTP instance ID or Common and Internal Spanning Tree (CIST). Specify 0 for CIST. Specify a value from 1 through 4094 for an MSTI. vlan vlan-id—(Optional) Display STP bridge information for the specified VLAN. Specify a VLAN tag identifier from 1 through 4094. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show spanning-tree interface on page 1407 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding STP for J-EX Series Switches on page 1275 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 show spanning-tree bridge on page 1400 show spanning-tree bridge brief on page 1400 show spanning-tree bridge detail on page 1401 Table 180 on page 1398 lists the output fields for the show spanning-tree bridge command. Output fields are listed in the approximate order in which they appear. Table 180: show spanning-tree bridge Output Fields 1398 Field Name Field Description Context ID An internally generated identifier. Chapter 69: Operational Mode Commands for Spanning-Tree Protocols Table 180: show spanning-tree bridge Output Fields (continued) Field Name Field Description Enabled protocol Spanning-tree protocol type enabled. Root ID Bridge ID of the elected spanning tree root bridge. The bridge ID consists of a configurable bridge priority and the MAC address of the bridge. Root cost Calculated cost to reach the root bridge from the bridge where the command is entered. Root port Interface that is the current elected root port for this bridge. CIST regional root Bridge ID of the elected MSTP regional root bridge. CIST internal root cost Calculated cost to reach the regional root bridge from the bridge where the command is entered. Hello time Configured number of seconds between transmissions of configuration BPDUs. Maximum age Maximum age of received protocol BPDUs. Forward delay Configured time an STP bridge port remains in the listening and learning states before transitioning to the forwarding state. Hop count Configured maximum number of hops a BPDU can be forwarded in the MSTP region. Message age Number of seconds elapsed since the most recent BPDU was received. Number of topology changes Total number of STP topology changes detected since the switch last booted. Time since last topology change Number of seconds elapsed since the most recent topology change. Topology change initiator Interface name of the interface that received the topology change request. Topology change last recvd. from Bridge ID of the bridge that requested the last topology change. Bridge ID (Local) Locally configured bridge ID. The bridge ID consists of a configurable bridge priority and the MAC address of the bridge. Extended system ID Internally generated system identifier. MSTI regional root Bridge ID of the elected MSTP regional root bridge. Internal instance ID An internally generated identifier. 1399 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 180: show spanning-tree bridge Output Fields (continued) show spanning-tree bridge Field Name Field Description Path Cost Method Bridges supporting 802.1D (legacy) implement only 16-bit values for path cost. Newer versions of this standard support 32-bit values. user@switch> show spanning-tree bridge STP bridge parameters Context ID : 0 Enabled protocol : MSTP STP bridge parameters for CIST Root ID Root cost Root port CIST regional root CIST internal root cost Hello time Maximum age Forward delay Hop count Message age Number of topology changes Time since last topology change Topology change initiator Topology change last recvd. from Local parameters Bridge ID Extended system ID Internal instance ID STP bridge parameters for MSTI 10 MSTI regional root Root cost Root port Hello time Maximum age Forward delay Hop count Number of topology changes Time since last topology change Topology change initiator Topology change last recvd. from Local parameters Bridge ID Extended system ID Internal instance ID show spanning-tree bridge brief 1400 : : : : : : : : : : : : : : 32768.00:11:f2:56:df:40 0 ge-0/0/1.0 32768.00:11:f2:56:df:40 20000 2 seconds 20 seconds 15 seconds 19 0 1 108 seconds ge-0/0/1.0 00:11:f2:56:df:4c : 32768.00:11:f2:57:1c:00 : 0 : 0 : : : : : : : : : : : 32778.00:11:f2:56:df:40 20000 ge-0/0/1.0 2 seconds 20 seconds 15 seconds 19 1 108 seconds ge-0/0/1.0 00:11:f2:56:df:41 : 32778.00:11:f2:57:1c:00 : 0 : 1 user@switch> show spanning-tree bridge brief STP bridge parameters Context ID : 0 Enabled protocol : RSTP Root ID : 32768.00:19:e2:50:95:a0 Hello time : 2 seconds Maximum age : 20 seconds Forward delay : 15 seconds Message age : 0 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols Number of topology changes : 0 Local parameters Bridge ID : 32768.00:19:e2:50:95:a0 Extended system ID : 0 Internal instance ID : 0 show spanning-tree bridge detail user@switch> show spanning-tree bridge detail STP bridge parameters Context ID : 0 Enabled protocol : RSTP Root ID : 32768.00:19:e2:50:95:a0 Hello time : 2 seconds Maximum age : 20 seconds Forward delay : 15 seconds Message age : 0 Number of topology changes : 0 Local parameters Bridge ID : 32768.00:19:e2:50:95:a0 Extended system ID : 0 Internal instance ID : 0 Hello time : 2 seconds Maximum age : 20 seconds Forward delay : 15 seconds Path cost method : 32 bit 1401 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show spanning-tree interface Syntax Syntax (J-EX Series Switch) Release Information Description Options show spanning-tree interface show spanning-tree interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the configured or calculated interface-level STP parameters. none—Display brief STP interface information. brief | detail—(Optional) Display the specified level of output. msti msti-id—(Optional) Display STP interface information for the specified MST instance. routing-instance routing-instance-name—(Optional) Display STP interface information for the specified routing instance. vlan-id vlan-id—(Optional) Display STP interface information for the specified VLAN. Required Privilege Level List of Sample Output Output Fields view show spanning-tree interface on page 1403 show spanning-tree interface detail on page 1404 show spanning-tree interface msti on page 1405 show spanning-tree interface vlan-id 101 on page 1406 show spanning-tree interface (VSTP) on page 1406 show spanning-tree interface vlan-id (VSTP) on page 1406 Table 181 on page 1402 lists the output fields for the show spanning-tree Interface command. Output fields are listed in the approximate order in which they appear. Table 181: show spanning-tree Interface Output Fields 1402 Field Name Field Description Interface name Interface configured to participate in the STP, RSTP, VSTP, or MSTP instance. Port ID Logical interface identifier configured to participate in the MSTP or VSTP instance. Designated port ID Port ID of the designated port for the LAN segment to which this interface is attached. Chapter 69: Operational Mode Commands for Spanning-Tree Protocols Table 181: show spanning-tree Interface Output Fields (continued) show spanning-tree interface Field Name Field Description Designated bridge ID Bridge ID of the designated bridge for the LAN segment to which this interface is attached. Port Cost Configured cost for the interface. Port State STP port state: forwarding (FWD), blocking (BLK), listening, learning, or disabled. Port Role MSTP, VSTP, or RSTP port role: designated (DESG), backup (BKUP), alternate (ALT), root, or Root Prevented (Root-Prev). Link type MSTP, VSTP, or RSTP link type. Shared or point-to-point (pt-pt) and edge or nonedge. Alternate Identifies the interface as an MSTP, VSTP, or RSTP alternate root port (Yes) or nonalternate root port (No). Boundary Port Identifies the interface as an MSTP regional boundary port (Yes) or nonboundary port (No). user@host> show spanning-tree interface routing-instance vs1 detail Spanning tree interface parameters for instance 0 Interface ae1 ge-2/1/2 ge-2/1/5 ge-2/2/1 xe-9/2/0 xe-9/3/0 Port ID 128:1 128:2 128:3 128:4 128:5 128:6 Designated port ID 128:1 128:2 128:3 128:26 128:5 128:6 Designated bridge ID 32768.0090690b47d1 32768.0090690b47d1 32768.0090690b47d1 32768.0013c39ec880 32768.0090690b47d1 32768.0090690b47d1 Port Cost 1000 20000 29999 20000 2000 2000 State Role FWD FWD FWD FWD FWD FWD DESG DESG DESG ROOT DESG DESG Port Cost 1000 20000 29999 20000 2000 2000 State Role FWD FWD FWD FWD FWD FWD DESG DESG DESG ROOT DESG DESG Port Cost 1000 20000 29999 20000 State Role FWD FWD FWD FWD DESG DESG DESG ROOT Spanning tree interface parameters for instance 1 Interface ae1 ge-2/1/2 ge-2/1/5 ge-2/2/1 xe-9/2/0 xe-9/3/0 Port ID 128:1 128:2 128:3 128:4 128:5 128:6 Designated port ID 128:1 128:2 128:3 128:26 128:5 128:6 Designated bridge ID 32769.0090690b47d1 32769.0090690b47d1 32769.0090690b47d1 32769.0013c39ec880 32769.0090690b47d1 32769.0090690b47d1 Spanning tree interface parameters for instance 2 Interface ae1 ge-2/1/2 ge-2/1/5 ge-2/2/1 Port ID 128:1 128:2 128:3 128:4 Designated port ID 128:1 128:2 128:3 128:26 Designated bridge ID 32770.0090690b47d1 32770.0090690b47d1 32770.0090690b47d1 32770.0013c39ec880 1403 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS xe-9/2/0 xe-9/3/0 show spanning-tree interface detail 1404 128:5 128:6 128:5 128:6 32770.0090690b47d1 32770.0090690b47d1 user@host> show spanning-tree interface routing-instance vs1 detail Spanning tree interface parameters for instance 0 Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : ae1 128.1 128.1 1000 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : Interface name Port identifier Designated port ID Port cost Port state : : : : : ge-2/1/2 128.2 128.2 20000 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No ge-2/1/5 128.3 128.3 29999 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No ge-2/2/1 128.4 128.26 20000 Forwarding 32768.00:13:c3:9e:c8:80 Root Pt-Pt/NONEDGE : No xe-9/2/0 128.5 128.5 2000 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No xe-9/3/0 128.6 128.6 2000 Forwarding 2000 2000 FWD FWD DESG DESG Chapter 69: Operational Mode Commands for Spanning-Tree Protocols Designated bridge ID Port role Link type Boundary port : 32768.00:90:69:0b:47:d1 : Designated : Pt-Pt/NONEDGE : No Spanning tree interface parameters for instance 1 Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : ae1 128.1 128.1 1000 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : Interface name Port identifier Designated port ID Port cost Port state Designated bridge ID Port role Link type Boundary port : : : : : : : : ge-2/1/2 128.2 128.2 20000 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No ge-2/1/5 128.3 128.3 29999 Forwarding 32768.00:90:69:0b:47:d1 Designated Pt-Pt/NONEDGE : No ge-2/2/1 128.4 128.26 20000 Forwarding 32768.00:13:c3:9e:c8:80 Root Pt-Pt/NONEDGE : No ... show spanning-tree interface msti user@host> show spanning-tree interface msti 1 routing-instance vs1 detail Spanning tree interface parameters for instance 1 Interface xe-7/0/0 ge-5/1/0 ge-5/1/1 ae1 Port ID 128:1 128:2 128:3 128:4 Designated port ID 128:1 128:2 128:3 128:1 Designated bridge ID 32769.0090690b4fd1 32769.0090690b4fd1 32769.0090690b4fd1 32769.0090690b47d1 Port Cost 2000 20000 20000 10000 State Role FWD FWD FWD BLK DESG DESG DESG ALT 1405 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-5/1/4 xe-7/2/0 show spanning-tree interface vlan-id 101 128:3 128:6 32769.0090690b47d1 32769.0090690b47d1 20000 2000 BLK FWD ALT ROOT Port Cost 20000 20000 20000 20000 20000 2000 2000 State Role FWD BLK BLK BLK BLK BLK FWD DESG BKUP ALT ALT ALT ALT ROOT Cost State Role FWD FWD DESG DESG State Role FWD FWD DESG DESG State Role FWD FWD DESG DESG State Role FWD FWD DESG DESG user@host> show spanning-tree interface vlan-id 101 routing-instance vs1 detail Spanning tree interface parameters for instance 0 Interface ge-11/0/5 ge-11/0/6 ge-11/1/0 ge-11/1/1 ge-11/1/4 xe-10/0/0 xe-10/2/0 show spanning-tree interface (VSTP) 128:5 128:6 Port ID 128:1 128:2 128:3 128:4 128:5 128:6 128:7 Designated port ID 128:1 128:1 128:2 128:3 128:1 128:5 128:4 Designated bridge ID 32768.0090690b7fd1 32768.0090690b7fd1 32768.0090690b4fd1 32768.0090690b4fd1 32768.0090690b47d1 32768.0090690b4fd1 32768.0090690b47d1 user@host> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-1/0/1 ge-1/0/2 Port ID 128:1 128:2 Designated port ID 128:1 128:2 Designated bridge ID 28672.0090690b3fe0 28672.0090690b3fe0 20000 20000 Spanning tree interface parameters for VLAN 10 Interface ge-1/0/1 ge-1/0/2 Port ID 128:1 128:2 Designated port ID 128:1 128:2 Designated bridge ID 28672.0090690b3fe0 28672.0090690b3fe0 Cost 20000 20000 Spanning tree interface parameters for VLAN 20 Interface ge-1/0/1 ge-1/0/2 show spanning-tree interface vlan-id (VSTP) 128:1 128:2 Designated port ID 128:1 128:2 Designated bridge ID 28672.0090690b3fe0 28672.0090690b3fe0 Cost 20000 20000 user@host> show spanning-tree interface vlan-id 10 Spanning tree interface parameters for VLAN 10 Interface ge-1/0/1 ge-1/0/2 1406 Port ID Port ID 128:1 128:2 Designated port ID 128:1 128:2 Designated bridge ID 28672.0090690b3fe0 28672.0090690b3fe0 Cost 20000 20000 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols show spanning-tree interface Syntax Release Information Description Options show spanning-tree interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the configured or calculated interface-level spanning-tree protocol (can be either STP, RSTP, or MSTP) parameters. In brief mode, will not display interfaces that are administratively disabled or do not have a physical link. none—(Optional) Display brief STP interface information. brief | detail—(Optional) Display the specified level of output. interface-name interface-name—(Optional) Name of an interface. msti msti-id—(Optional) Display STP bridge information for the specified MSTP instance ID or Common and Internal Spanning Tree (CIST). Specify 0 for CIST. Specify a value from 1 through 4094 for an MSTI. vlan-id vlan-id—(Optional) For MSTP interfaces, display interface information for the specified VLAN. Specify a value from 0 through 4094. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show spanning-tree bridge on page 1398 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding STP for J-EX Series Switches on page 1275 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 show spanning-tree interface on page 1408 show spanning-tree interface brief on page 1409 show spanning-tree interface detail on page 1409 show spanning-tree interface ge-1/0/0 on page 1410 Table 182 on page 1408 lists the output fields for the show spanning-tree Interface command. Output fields are listed in the approximate order in which they appear. 1407 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 182: show spanning-tree interface Output Fields Field Name Field Description Interface name Interface configured to participate in the STP, RSTP, or MSTP instance. Port ID Logical interface identifier configured to participate in the MSTP instance. Designated port ID Port ID of the designated port for the LAN segment this interface is attached to. Designated bridge ID Bridge ID of the designated bridge for the LAN segment this interface is attached to. Port Cost Configured cost for the interface. Port State STP port state. Forwarding (FWD), blocking (BLK), listening, learning, or disabled. Port Role MSTP or RSTP port role. Designated (DESG), backup (BKUP), alternate (ALT), or root. Link type MSTP or RSTP link type. Shared or point-to-point (pt-pt) and edge or non edge. Alternate Identifies the interface as an MSTP or RSTP alternate root port (yes) or nonalternate root port (no). Boundary Port Identifies the interface as an MSTP regional boundary port (yes) or nonboundary port (no). show spanning-tree interface user@switch> show spanning-tree interface Spanning tree interface parameters for instance 0 Interface ge-0/0/0.0 ge-0/0/2.0 ge-0/0/4.0 ge-0/0/23.0 Port ID 128:513 128:515 128:517 128:536 Designated Designated port ID bridge ID 128:513 8192.0019e2500340 128:515 8192.0019e2500340 128:517 8192.0019e2500340 128:536 8192.0019e2500340 Port Cost 1000 1000 1000 1000 State Role FWD BLK FWD FWD DESG DIS DESG DESG Port Cost 1000 1000 1000 1000 State Role FWD BLK FWD FWD DESG DIS DESG DESG Spanning tree interface parameters for instance 1 Interface ge-0/0/0.0 ge-0/0/2.0 ge-0/0/4.0 ge-0/0/23.0 Port ID 128:513 128:515 128:517 128:536 Designated Designated port ID bridge ID 128:513 8193.0019e2500340 128:515 8193.0019e2500340 128:517 8193.0019e2500340 128:536 8193.0019e2500340 Spanning tree interface parameters for instance 2 Interface ge-0/0/0.0 ge-0/0/2.0 ge-0/0/4.0 1408 Port ID 128:513 128:515 128:517 Designated Designated Port State Role port ID bridge ID Cost 128:1 8194.001b549fd000 1000 FWD ROOT 128:515 32770.0019e2500340 4000 BLK DIS 128:1 16386.001b54013080 1000 BLK ALT Chapter 69: Operational Mode Commands for Spanning-Tree Protocols ge-0/0/23.0 128:536 show spanning-tree interface brief 128:536 32770.0019e2500340 1000 DESG user@switch> show spanning-tree interface brief Spanning tree interface parameters for instance 0 Interface Port ID Designated Designated port ID bridge ID Cost ge-1/0/0.0 128:625 128:625 32768.0019e25095a0 ge-1/0/1.0 128:626 128:626 32768.0019e25095a0 ge-1/0/2.0 128:627 128:627 32768.0019e25095a0 ge-1/0/10.0 128:635 128:635 32768.0019e25095a0 ge-1/0/20.0 128:645 128:645 32768.0019e25095a0 ge-1/0/30.0 128:655 128:655 32768.0019e25095a0 show spanning-tree interface detail FWD Port 20000 20000 20000 20000 20000 20000 State BLK BLK BLK BLK BLK BLK Role DIS DIS DIS DIS DIS DIS user@switch> show spanning-tree interface detail Spanning tree interface parameters for instance 0 Interface name : ge-1/0/0.0 Port identifier : 128.625 Designated port ID : 128.625 Port cost : 20000 Port state : Blocking Designated bridge ID : 32768.00:19:e2:50:95:a0 Port role : Disabled Link type : Pt-Pt/EDGE Boundary port : NA Interface name : ge-1/0/1.0 Port identifier : 128.626 Designated port ID : 128.626 Port cost : 20000 Port state : Blocking Designated bridge ID : 32768.00:19:e2:50:95:a0 Port role : Disabled Link type : Pt-Pt/NONEDGE Boundary port : NA Interface name : ge-1/0/2.0 Port identifier : 128.627 Designated port ID : 128.627 Port cost : 20000 Port state : Blocking Designated bridge ID : 32768.00:19:e2:50:95:a0 Port role : Disabled Link type : Pt-Pt/NONEDGE Boundary port : NA Interface name : ge-1/0/10.0 Port identifier : 128.635 Designated port ID : 128.635 Port cost : 20000 Port state : Blocking Designated bridge ID : 32768.00:19:e2:50:95:a0 Port role : Disabled Link type : Pt-Pt/NONEDGE Boundary port : NA Interface name : ge-1/0/20.0 Port identifier : 128.645 Designated port ID : 128.645 1409 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Port cost : 20000 Port state : Blocking Designated bridge ID : 32768.00:19:e2:50:95:a0 Port role : Disabled Link type : Pt-Pt/NONEDGE Boundary port : NA [output truncated] show spanning-tree interface ge-1/0/0 user@switch> show spanning-tree interface ge-1/0/0 Interface Port ID Designated Designated Port State Role port ID bridge ID Cost ge-1/0/0.0 128:625 128:625 32768.0019e25095a0 20000 BLK DIS 1410 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols show spanning-tree mstp configuration Syntax Syntax (J-EX Series Switch) Release Information Description Options show spanning-tree mstp configuration show spanning-tree mstp configuration Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the MSTP configuration. none—Display MSTP configuration information. brief | detail—(Optional) Display the specified level of output. routing-instance routing-instance-name—(Optional) Display MSTP configuration information for the specified routing instance. Required Privilege Level List of Sample Output Output Fields view show spanning-tree mstp configuration on page 1411 Table 183 on page 1411 lists the output fields for the show spanning-tree mstp configuration command. Output fields are listed in the approximate order in which they appear. Table 183: show spanning-tree mstp configuration Output Fields show spanning-tree mstp configuration Field Name Field Description Context id Internally generated identifier. Region name MSTP region name carried in the MSTP BPDUs. Revision Revision number of the MSTP configuration. Configuration digest Numerical value derived from the VLAN-to-instance mapping table. MSTI ID MST instance identifier. Member VLANs VLAN identifiers associated with the MSTI. user@host> show spanning-tree mstp configuration routing-instance vs1 detail MSTP configuration information Context identifier : 1 Region name : henry Revision : 3 Configuration digest : 0x6da4b5c4fd587757eef35675365e1 1411 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS MSTI Member VLANs 0 0-99,101-199,201-4094 1 100 2 200 1412 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols show spanning-tree mstp configuration Syntax Release Information Description Options show spanning-tree mstp configuration Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the MSTP configuration. none—Display MSTP configuration information. brief | detail—(Optional) Display the specified level of output. Required Privilege Level List of Sample Output Output Fields view show spanning-tree mstp configuration on page 1413 Table 184 on page 1413 lists the output fields for the show spanning-tree mstp configuration command. Output fields are listed in the approximate order in which they appear. Table 184: show spanning-tree mstp configuration Output Fields Field Name Field Description Context identifier Internally generated identifier. Region name MSTP region name carried in the MSTP BPDUs. Revision Revision number of the MSTP configuration. Configuration digest Numerical value derived from the VLAN-to-instance mapping table. MSTI MSTI instance identifier. Member VLANs Identifiers for VLANs associated with the MSTI. show spanning-tree mstp configuration user@host> show spanning-tree mstp configuration MSTP configuration information Context identifier : 0 Region name : region1 Revision : 0 Configuration digest : 0xc92e7af9febb44d8df928b87f16b MSTI Member VLANs 0 0-100,105-4094 1 101-102 2 103-104 1413 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show spanning-tree statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show spanning-tree statistics show spanning-tree statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display STP statistics. none—Display brief STP statistics. brief | detail—(Optional) Display the specified level of output. interface interface-name—(Optional) Display STP statistics for the specified interface. routing-instance routing-instance-name—(Optional) Display STP statistics for the specified routing instance. Required Privilege Level List of Sample Output Output Fields view show spanning-tree statistics routing-instance on page 1415 show spanning-tree statistics interface on page 1415 Table 185 on page 1414 lists the output fields for the show spanning-tree statistics command. Output fields are listed in the approximate order in which they appear. Table 185: show spanning-tree statistics Output Fields 1414 Field Name Field Description Message type Type of message being counted. BPDUs sent Total number of BPDUs sent. BPDUs received Total number of BPDUs received. BPDUs sent in last 5 secs Number of BPDUs sent in the most recent 5-second period. BPDUs received in last 5 secs Number of BPDUs received in the most recent 5-second period. Interface Interface for which the statistics are being displayed. Next BPDU transmission Number of seconds until the next BPDU is scheduled to be sent. Chapter 69: Operational Mode Commands for Spanning-Tree Protocols show spanning-tree statistics routing-instance user@host> show spanning-tree statistics routing-instance vs1 detail Routing instance level STP statistics Message type : bpdus BPDUs sent : 121 BPDUs received : 537 BPDUs sent in last 5 secs : 5 BPDUs received in last 5 secs : 27 show spanning-tree statistics interface user@host> show spanning-tree statistics interface ge-11/1/4 routing-instance vs1 detail Interface BPDUs sent BPDUs received Next BPDU transmission ge-11/1/4 7 190 0 1415 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show spanning-tree statistics Syntax Release Information Description Options show spanning-tree statistics interface interface-name vlan vlan-id Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display STP statistics on an interface, or for a VLAN when VSTP is enabled. none—Display brief STP statistics. brief | detail—(Optional) Display the specified level of output. interface interface-name—(Optional) The name of the interface. vlan vlan-id—(Optional) The name of a VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show spanning-tree bridge on page 1398 • Example: Configuring Network Regions for VLANs with MSTP on J-EX Series Switches on page 1297 • Understanding STP for J-EX Series Switches on page 1275 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding VSTP for J-EX Series Switches on page 1281 show spanning-tree statistics interface on page 1417 Table 186 on page 1416 lists the output fields for the show spanning-tree statistics command. Output fields are listed in the approximate order in which they appear. Table 186: show spanning-tree statistics Output Fields Field Name Field Description BPDUs sent Total number of BPDUs sent. BPDUs received Total number of BPDUs received. Interface Interface for which the statistics are being displayed. Next BPDU transmission Number of seconds until the next BPDU is scheduled to be sent. 1416 Chapter 69: Operational Mode Commands for Spanning-Tree Protocols show spanning-tree statistics interface user@switch> show spanning-tree statistics interface ge-0/0/4 Interface BPDUs sent BPDUs received Next BPDU transmission ge-0/0/4 7 190 0 1417 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1418 PART 15 Layer 3 Protocols • Layer 3 Protocols—Overview on page 1421 • Configuring Layer 3 Protocols on page 1431 • Verifying Layer 3 Protocols Configuration on page 1455 • Configuration Statements for Layer 3 Protocols on page 1465 • Operational Commands for Layer 3 Protocols on page 1747 1419 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1420 CHAPTER 70 Layer 3 Protocols—Overview • Layer 3 Protocols Supported on J-EX Series Switches on page 1421 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 1422 • Understanding Distributed Periodic Packet Management on J-EX Series Switches on page 1424 • Understanding VRRP on J-EX Series Switches on page 1425 • Understanding IPsec Authentication for OSPF Packets on J-EX Series Switches on page 1428 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 187 on page 1421: Table 187: Supported Junos OS Layer 3 Protocol Statements and Features Protocol Notes For More Information BGP Fully supported. See the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. BFD Fully supported. See the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. ICMP Fully supported. See the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/ IGMPv1, v2 and v3 Fully supported. See the Junos OS Multicast Configuration Guide at http://www.juniper.net/techpubs/software/junos/. IS-IS MPLS Supported, with the exceptions noted in “Layer 3 Protocols Not Supported on J-EX Series Switches” on page 14. See the Junos OS Routing Protocols Configuration Guide at Supported, with the exceptions noted in “Layer 3 Protocols Not Supported on J-EX Series Switches” on page 14. See the Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/. http://www.juniper.net/techpubs/software/junos/. 1421 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 187: Supported Junos OS Layer 3 Protocol Statements and Features (continued) Protocol Notes For More Information OSPFv1, v2 and v3 Supported, with the exceptions noted in “Layer 3 Protocols Not Supported on J-EX Series Switches” on page 14. See the Junos OS Routing Protocols Configuration Guide at Supported, with the exception of IPv6. See the Junos OS Multicast Configuration Guide at PIM http://www.juniper.net/techpubs/software/junos/. http://www.juniper.net/techpubs/software/junos/. RIP Fully supported. See the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. RIPng Fully supported. See the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. SNMP Fully supported. See the Junos OS Network Management Configuration Guide at http://www.juniper.net/techpubs/software/junos/. VRRP Fully supported with exception of IPv6 support of VRRP on routed VLAN interfaces (RVIs). Related Documentation See “Understanding VRRP on J-EX Series Switches” on page 1425. See also the Junos OS High Availability Guide at http://www.juniper.net/techpubs/software/junos/. • Layer 3 Protocols Not Supported on J-EX Series Switches on page 14 • 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 188 on page 1422: Table 188: 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 1422 Chapter 70: Layer 3 Protocols—Overview Table 188: Junos OS Layer 3 Protocol Statements and Features That Are Not Supported (continued) Feature Configuration Statements Not Supported on J-EX Series Switches 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 MPLS: • ldp and all subordinate statements 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 • inet6 family • l2vpn and subordinate statements • ldp and subordinate statements • vpls and subordinate statements • sap and all subordinate statements • ES-IS • IPv6 in multicast routing protocols • Fast Reroute (FRR) • Label Distribution Protocol (LDP) • Layer 3 VPNs • Multiprotocol BGP (MP-BGP) for VPN-IPv4 family • Pseudowire emulation (PWE3) • Routing policy statements related to Layer 3 VPNs and MPLS • Virtual Private LAN Service (VPLS) PIM: • IPv6 Routing instances: • Routing instance forwarding SAP and SDP 1423 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 188: Junos OS Layer 3 Protocol Statements and Features That Are Not Supported (continued) Feature Configuration Statements Not Supported on J-EX Series Switches 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 • accounting and subordinate statements • family mpls and family multiservice under hash-key hierarchy • Under monitoring group-name family inet output hierarchy: MPLS and label-switched-paths Traffic sampling and fowarding in the forwarding-options hierarchy Related Documentation • 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 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 • J-EX Series Switch Software Features Overview on page 3 Understanding Distributed Periodic Packet Management on J-EX Series Switches Periodic packet management (PPM) is responsible for processing a variety of time-sensitive periodic tasks for particular processes so that other processes on the J-EX Series Switch can more optimally direct their resources. PPM is responsible for the periodic transmission of packets on behalf of its various client processes, which include the process that controls Link Aggregation Control Protocol (LACP), and also for receiving packets on behalf of these client processes. PPM also gathers some statistics and sends process-specific packets. PPM cannot be disabled and is always running on any operational switch. The responsibility for PPM processing on the switch is distributed between the Routing Engine and either the access interfaces (on J-EX4200 switches) or the line cards (on J-EX8200 switches) for all protocols that use PPM by default. This distributed model provides a faster response time for protocols that use PPM than the response time provided by the nondistributed model. If distributed PPM is disabled, the PPM process runs on the Routing Engine only. Distributed PPM can be disabled for all protocols that use PPM or for a single protocol that uses PPM. There is no way to disable PPM entirely. 1424 Chapter 70: Layer 3 Protocols—Overview BEST PRACTICE: We recommend that, generally, you disable distributed PPM only if Dell Support advises you to do so (see “Requesting Technical Support” on page lxxi). You should disable distributed PPM only if you have a compelling reason to disable it. Related Documentation • Configuring Distributed Periodic Packet Management on a J-EX Series Switch (CLI Procedure) on page 1451 Understanding VRRP on J-EX Series Switches J-EX Series Switches support the Virtual Router Redundancy Protocol (VRRP) and VRRP for IPv6. This topic covers: • Overview of VRRP on J-EX Series Switches on page 1425 • Examples of VRRP Topologies on page 1426 Overview of VRRP on J-EX Series Switches 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 J-EX Series 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 J-EX Series 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. VRRP for IPv6 provides a much faster switchover to an alternate default routing platform than IPv6 Neighbor Discovery (ND) procedures. VRRP for IPv6 does not support the authentication-type or authentication-key statements. NOTE: Do not confuse the VRRP master and backup routing platforms with the master and backup member switches of a Virtual Chassis configuration. The master and backup members of a Virtual Chassis configuration compose a single host. In a VRRP topology, one host operates as the master routing platform and another operates as the backup routing platform, as shown in Figure 40 on page 1427. Switches running VRRP dynamically elect master and backup routing platforms. You can also force assignment of master and backup routing platforms using priorities from 1 through 255, with 255 being the highest priority. In VRRP operation, the default master 1425 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS routing platform sends advertisements to backup routing platforms at regular intervals. The default interval is 1 second. If the backup routing platforms do not receive an advertisement for a set period, the backup routing platform with the highest priority takes over as master and begins forwarding packets. NOTE: Priority 255 cannot be set for routed VLAN interfaces (RVIs). VRRP is defined in RFC 3768, Virtual Router Redundancy Protocol. Examples of VRRP Topologies Figure 39 on page 1426 illustrates a basic VRRP topology with J-EX Series switches. In this example, Switches A, B, and C are running VRRP and together they make up a virtual routing platform. The IP address of this virtual routing platform is 10.10.0.1 (the same address as the physical interface of Switch A). Figure 39: Basic VRRP on J-EX Series Switches Figure 40 on page 1427 illustrates a basic VRRP topology using Virtual Chassis configurations. Switch A, Switch B, and Switch C are each composed of multiple interconnected J-EX4200 Ethernet Switches. Each Virtual Chassis configuration operates as a single switch, which is running VRRP, and together they make up a virtual routing platform. The IP address of this virtual routing platform is 10.10.0.1 (the same address as the physical interface of Switch A). 1426 Chapter 70: Layer 3 Protocols—Overview Figure 40: VRRP on Virtual Chassis Switches Because the virtual routing platform uses the IP address of the physical interface of Switch A, Switch A is the master VRRP routing platform, while Switch B and Switch C function as backup VRRP routing platforms. Clients 1 through 3 are configured with the default gateway IP address of 10.10.0.1 as the master router, Switch A, forwards packets sent to its IP address. If the master routing platform fails, the switch configured with the higher priority becomes the master virtual routing platform and provides uninterrupted service for the LAN hosts. When Switch A recovers, it becomes the master virtual routing platform again. Related Documentation • For more information on VRRP or VRRP for IPv6, see the Junos OS High Availability Configuration Guide at http://www.juniper.net/techpubs/software/junos/. • High Availability Features for J-EX Series Switches Overview on page 18 • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 1427 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding IPsec Authentication for OSPF Packets on J-EX Series Switches IP Security (IPsec) provides a secure way to authenticate senders and encrypt IP version 4 (IPv4) traffic between network devices. IPsec offers network administrators for J-EX Series Ethernet Switches and their users the benefits of data confidentiality, data integrity, sender authentication, and anti-replay services. IPsec is a framework for ensuring secure private communication over IP networks and is based on standards developed by the International Engineering Task Force (IETF). IPsec provides security services at the network layer of the Open Systems Interconnection (OSI) model by enabling a system to select required security protocols, determine the algorithms to use for the security services, and implement any cryptographic keys required to provide the requested services. You can use IPsec to protect one or more paths between a pair of hosts, between a pair of security gateways (such as switches), or between a security gateway and a host. OSPF version 3 (OSPFv3), unlike OSPF version 2 (OSPFv2), does not have a built-in authentication method and relies on IPsec to provide this functionality. You can secure specific OSPFv3 interfaces and protect OSPFv3 virtual links. • Authentication Algorithms on page 1428 • Encryption Algorithms on page 1429 • IPsec Protocols on page 1429 • Security Associations on page 1429 • IPsec Modes on page 1430 Authentication Algorithms Authentication is the process of verifying the identity of the sender. Authentication algorithms use a shared key to verify the authenticity of the IPsec devices. The Junos operating system (Junos OS) uses the following authentication algorithms: • Message Digest 5 (MD5) uses a one-way hash function to convert a message of arbitrary length to a fixed-length message digest of 128 bits. Because of the conversion process, it is mathematically infeasible to calculate the original message by computing it backwards from the resulting message digest. Likewise, a change to a single character in the message will cause it to generate a very different message digest number. To verify that the message has not been tampered with, Junos OS compares the calculated message digest against a message digest that is decrypted with a shared key. Junos OS uses the MD5 hashed message authentication code (HMAC) variant that provides an additional level of hashing. MD5 can be used with an authentication header (AH) and Encapsulating Security Payload (ESP). • 1428 Secure Hash Algorithm 1 (SHA-1) uses a stronger algorithm than MD5. SHA-1 takes a message of less than 264 bits in length and produces a 160-bit message digest. The large message digest ensures that the data has not been changed and that it originates from the correct source. Junos OS uses the SHA-1 HMAC variant that provides an additional level of hashing. SHA-1 can be used with AH, ESP, and Internet Key Exchange (IKE). Chapter 70: Layer 3 Protocols—Overview • SHA-256, SHA-384, and SHA-512 (sometimes grouped under the name SHA-2) are variants of SHA-1 and use longer message digests. Junos OS supports the SHA-256 version of SHA-2, which can process all versions of Advanced Encryption Standard (AES), Data Encryption Standard (DES), and Triple DES (3DES) encryption. Encryption Algorithms Encryption encodes data into a secure format so that it cannot be deciphered by unauthorized users. As with authentication algorithms, a shared key is used with encryption algorithms to verify the authenticity of IPsec devices. Junos OS uses the following encryption algorithms: • Data Encryption Standard cipher-block chaining (DES-CBC) is a symmetric secret-key block algorithm. DES uses a key size of 64 bits, where 8 bits are used for error detection and the remaining 56 bits provide encryption. DES performs a series of simple logical operations on the shared key, including permutations and substitutions. CBC takes the first block of 64 bits of output from DES, combines this block with the second block, feeds this back into the DES algorithm, and repeats this process for all subsequent blocks. • Triple DES-CBC (3DES-CBC) is an encryption algorithm that is similar to DES-CBC but provides a much stronger encryption result because it uses three keys for 168-bit (3 x 56-bit) encryption. 3DES works by using the first key to encrypt the blocks, the second key to decrypt the blocks, and the third key to reencrypt the blocks. IPsec Protocols IPsec protocols determine the type of authentication and encryption applied to packets that are secured by the switch. Junos OS supports the following IPsec protocols: • AH—Defined in RFC 2402, AH provides connectionless integrity and data origin authentication for IPv4. It also provides protection against replays. AH authenticates as much of the IP header as possible, as well as the upper-level protocol data. However, some IP header fields might change in transit. Because the value of these fields might not be predictable by the sender, they cannot be protected by AH. In an IP header, AH can be identified with a value of 51 in the Protocol field of an IPv4 packet. • ESP—Defined in RFC 2406, ESP can provide encryption and limited traffic flow confidentiality or connectionless integrity, data origin authentication, and an anti-replay service. In an IP header, ESP can be identified with a value of 50 in the Protocol field of an IPv4 packet. Security Associations An IPsec consideration is the type of security association (SA) that you wish to implement. An SA is a set of IPsec specifications that are negotiated between devices that are establishing an IPsec relationship. These specifications include preferences for the type of authentication, encryption, and IPsec protocol to be used when establishing the IPsec connection. An SA can be either unidirectional or bidirectional, depending on the choices made by the network administrator. An SA is uniquely identified by a Security Parameter 1429 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Index (SPI), an IPv4 or IPv6 destination address, and a security protocol (AH or ESP) identifier. IPsec Modes Junos OS supports the following IPsec modes: • Tunnel mode is supported for both AH and ESP in Junos OS. In tunnel mode, the SA and associated protocols are applied to tunneled IPv4 or IPv6 packets. For a tunnel mode SA, an outer IP header specifies the IPsec processing destination and an inner IP header specifies the ultimate destination for the packet. The security protocol header appears after the outer IP header and before the inner IP header. In addition, there are slight differences for tunnel mode when you implement it with AH and ESP: • For AH, portions of the outer IP header are protected, as well as the entire tunneled IP packet. • For ESP, only the tunneled packet is protected, not the outer header. When one side of an SA is a security gateway (such as a switch), the SA must use tunnel mode. However, when traffic (for example, SNMP commands or BGP sessions) is destined for a switch, the system acts as a host. Transport mode is allowed in this case because the system does not act as a security gateway and does not send or receive transit traffic. NOTE: Tunnel mode is not supported for OSPF v3 control packet authentication. • Related Documentation 1430 Transport mode provides an SA between two hosts. In transport mode, the protocols provide protection primarily for upper-layer protocols. A transport mode security protocol header appears immediately after the IP header and any options and before any higher-layer protocols (for example, TCP or UDP). There are slight differences for transport mode when you implement it with AH and ESP: • For AH, selected portions of the IP header are protected, as well as selected portions of the extension headers and selected options within the IPv4 header. • For ESP, only the higher-layer protocols are protected, not the IP header or any extension headers preceding the ESP header. • Using IP Security to Secure OSPFv3 Networks on page 1453 • Configuring an OSPF Network (J-Web Procedure) on page 1435 CHAPTER 71 Configuring Layer 3 Protocols • Configuring BGP Sessions (J-Web Procedure) on page 1431 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Configuring a RIP Network (J-Web Procedure) on page 1439 • Configuring Static Routing (CLI Procedure) on page 1444 • Configuring Static Routing (J-Web Procedure) on page 1444 • Configuring Routing Policies (J-Web Procedure) on page 1446 • Configuring Distributed Periodic Packet Management on a J-EX Series Switch (CLI Procedure) on page 1451 • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 • Using IPsec to Secure OSPFv3 Networks (CLI Procedure) on page 1453 Configuring BGP Sessions (J-Web Procedure) You can use the J-Web interface to create BGP peering sessions on a routing device. NOTE: To configure BGP sessions, you must have a license for BGP installed on the J-EX Series switch. To configure a BGP peering session: 1. Select Configure > Routing > BGP. 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 334 for details about all commit options. 1431 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2. Click one: • Add—Adds a BGP group. Enter information into the configuration page as described in Table 189 on page 1432. • Edit—Modifies an existing BGP group. Enter information into the configuration page as described in Table 189 on page 1432. • Delete—Deletes an existing BGP group. • Disable—Disables BGP configuration. 3. To modify BGP global settings, click Edit in the Global Information section. Enter information as described in Table 190 on page 1434. Table 189: BGP Routing Configuration Summary Field Function Your Action Group Type Specifies whether the group is an internal BGP (IBGP) group or an external BGP (EBGP) group. Select the option: Internal or External. Group Name Specifies the name for the group. Type a new name or select and edit the name. ASN Sets the unique numeric identifier of the AS in which the routing device is configured. Type the routing device’s 32-bit AS number, in dotted decimal notation. General tab If you enter an integer, the value is converted to a 32-bit equivalent. For example, if you enter 3, the value assigned to the AS is 0.0.0.3. Preference Specifies the degree of preference for an external route. The route with the highest local preference value is preferred. Type or select and edit the value. Cluster Id Specifies the cluster identifier to be used by the route reflector cluster in an internal BGP group. Type or select and edit the IPv6 or IPv4 address to be used as the identifier. Description Specifies the text description of the global, group, or neighbor configuration. Type or select and edit the description. Damping Specifies whether route flap damping is enabled or not. To enable route flap damping, select the check box. To disable route flap damping do not select the check box. Advertise Inactive Routes 1432 Specifies whether BGP advertises the best route even if the routing table did not select it to be an active route. To enable advertising inactive routes, select the check box. To disable advertising inactive routes, do not select the check box. Chapter 71: Configuring Layer 3 Protocols Table 189: BGP Routing Configuration Summary (continued) Field Function Your Action Advertise Peer AS Routes Specifies whether to disable the default behavior of suppressing AS routes. To enable advertising peer AS routes, select the check box. To disable advertising peer AS routes, do not select the check box. Neighbors tab Dynamic Neighbors Configures a neighbor (peer). Type the IPv4 address of the peer. Static Neighbors Configures the system’s peers statically. To configure a static neighbor: 1. Specify the IP address. 2. Specify the address of the local end of a BGP session. 3. Specify the degree of preference for an external route. 4. Enter a description. 5. Specify the hold-time value to use when negotiating a connection with the peer. 6. Specify how long a route must be present in the routing table before it is exported to BGP. Use this time delay to help bundle routing updates. 7. Select Passive if you do not want to send active open messages to the peer. 8. Select the option to compare the AS path of an incoming advertised route with the AS number of the BGP peer under the group and replace all occurrences of the peer AS number in the AS path with its own AS number before advertising the route to the peer. 9. Specify an import policy and export policy. 10. Click OK. Policies tab Import Policy Specifies one or more routing policies to routes being imported into the routing table from BGP. Click Add to add an import policy. Select the policy and click OK. Click Move up or Move down to move the selected policy up or down the list of policies. Select the policy and click Remove. Export Policy Specifies one or more policies to routes being exported from the routing table into BGP. Click Add to add an export policy. Select the policy and click OK. Click Move up or Move down to move the selected policy up or down the list of policies. Select the policy and click Remove. 1433 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 190: BGP Global Settings Field Function Your Action Router ASN Specifies the routing device’s AS number. Type or select and edit the value. Router Identifier Specify the routing device’s IP address. Type or select and edit the IP address. BGP Status Enables or disables BGP. • To enable BGP, select Enabled. • To disable BGP, select Disabled. General tab Description Describes of the global, group, or neighbor configuration. Type or select and edit the description. Confederation Number Specifies the routing device’s confederation AS number. Type or select and edit the value. Confederation Members Specifies the AS numbers for the confederation members. To add a member AS number, click Add and enter the number in the Member ASN box. Click OK. To modify a confederation member’s AS number, select the member click Edit and, enter the number and click OK. To delete a confederation member, select the member and click Remove. Advance Options You can configure the following: Select All or None to configure Keep Routes. • Keep routes—Specifies whether routes learned Enter a value in the TCP MSS box. from a BGP peer must be retained in the routing table even if they contain an AS number that was exported from the local AS. Click to enable MTU Discovery. • TCP MSS—Configures the maximum segment size (MSS) for the TCP connection for BGP neighbors. • MTU Discovery—Select to configure MTU discovery. • Remove Private ASN—Select to have the local system strip private AS numbers from the AS path when advertising AS paths to remote systems. • Graceful Restart—Specifies the time period when the restart is expected to be complete. Specify the maximum time that stale routes are kept during restart. • Multihop—Configures the maximum time-to-live (TTL) value for the TTL in the IP header of BGP packets. • Authentication Type—Select the authentication algorithm: None, MD5, SHA1, AES. Policies tab 1434 Click to enable Remove Private ASN. Enter the time period for a graceful restart and the maximum time that stale routes must be kept. To configure Multihop, select Nexthop Change to allow unconnected third-party next hops. Enter a TTL value. Select the authentication algorithm. If you select None, specify an authentication key (password). Chapter 71: Configuring Layer 3 Protocols Table 190: BGP Global Settings (continued) Field Function Your Action Import Policy Specifies one or more routing policies to routes being imported into the routing table from BGP. Click Add to add an import policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an import policy. Export Policy Specifies one or more policies to routes being exported from the routing table into BGP. Click Add to add an export policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an export policy. Trace Options tab File Name Specifies the name of the file to receive the output of the tracing operation. Type or select and edit the name. Number of Files Specifies the maximum number of trace files. Type or select and edit the value. File Size Specifies the maximum size for each trace file. Type or select and edit the value. World Readable Specifies whether the trace file can be read by any user or not. Select True to allow any user to read the file. Select False to disallow all users being able to read the file. Flags Specifies the tracing operation to perform. Related Documentation Select a value from the list. • Monitoring BGP Routing Information on page 1455 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Configuring an OSPF Network (J-Web Procedure) You can use the J-Web interface to create multiarea OSPF networks on a J-EX Series switch. To configure a multiarea OSPF network: 1435 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1. Select Configure > Routing > OSPF. 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 334 for details about all commit options. 2. Click one: • Add—Adds an OSPF area. Enter information into the configuration page as described in Table 191 on page 1436. • Edit—Modifies an existing OSPF area. Enter information into the configuration page as described in Table 191 on page 1436. • Delete—Deletes an existing OSPF area. 3. To modify OSPF global settings, click Edit. Enter information as described in Table 192 on page 1438. 4. To disable OSPF, click Disable. Table 191: OSPF Routing Configuration Summary Field Function Your Action Uniquely identifies the area within its AS. Type a 32-bit numeric identifier for the area. Type an integer or select and edit the value. General tab Area Id If you enter an integer, the value is converted to a 32-bit equivalent. For example, if you enter 3, the value assigned to the area is 0.0.0.3. Area Ranges Specifies a range of IP addresses for an area when sending summary link advertisements (within an area). To add a range: 1. Click Add. 2. Type the area range. 3. Specify the subnet mask. 4. To override the metric for the IP address range, type a specific metric value. 5. If you do not want to display the routes that are contained within a summary, select Restrict advertisements of this area range. 6. If you want a summary of a route to be advertised only when an exact match is made with the configured summary range, select Enforce exact match for advertisement of this area range. 7. Click OK. To modify an existing area range, select the area range, click Edit, and edit the value. Click OK. To delete an area range, select the area range and click Delete. 1436 Chapter 71: Configuring Layer 3 Protocols Table 191: OSPF Routing Configuration Summary (continued) Field Function Your Action Area Type Designates the type of OSPF area. Select the type of OSPF area you are creating from the list. If you select stub: • regular—A regular OSPF area, including the backbone area • stub—A stub area • nssa—A not-so-stubby 1. Enter the default metric. 2. To flood summary LSAs into the stub area, select the check box. If you select nssa: area (NSSA) 1. Specify the metric type. 2. Enter the default metric. 3. To flood summary LSAs into the nssa area, select the check box. 4. To flood Type-7 LSAs into the nssa area, select the check box. Interfaces tab Interfaces Specifies the interfaces to be associated with the OSPF configuration To associate an interface with the configuration, select the interface from the list, select Associate and click OK. To edit an interface’s configuration: 1. Select the interface from the list and click Edit. 2. Specify the cost of an OSPF interface. 3. Specify the traffic engineering metric. 4. Specify how often the routing device sends hello packets from the interface. 5. Specify how long the routing device waits to receive a link-state acknowledgment packet before retransmitting link-state advertisements to an interface’s neighbors. 6. To enable OSPF on the interface, select the check box. 7. To inform other protocols about neighbor down events, select the check box. 8. To treat the interface as a secondary interface, select the check box. 9. To only advertise OSPF, select the check box. 10. Click OK. Policies tab Import Policy Specifies one or more policies to control which routes learned from an area are used to generate summary link-state advertisements (LSAs) into other areas. Click Add to add an import policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an import policy. 1437 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 191: OSPF Routing Configuration Summary (continued) Field Function Your Action Export Policy Specifies one or more policies to control which summary LSAs are flooded into an area. Click Add to add an export policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an export policy. Table 192: Edit OSPF Global Settings Field Function Your Action Router Id Specifies the ID for the routing device. Type or select and edit the value. RIB Group Installs the routes learned from OSPF routing instances into routing tables in the OSPF routing table group. Select a value. Internal Route Preference Specifies the route preference for internal groups. Type or select and edit the value. External Route Preference Specifies the route preference for external groups. Type or select and edit the value. Graceful Restart Configures graceful restart for OSPF. To configure graceful restart: General tab 1. Specify the estimated time to send out purged grace LSAs over all the interfaces. 2. Specified the estimated time to reacquire a full OSPF neighbor from each area. 3. To disable No Strict LSA Checking, select the check box. 4. To disable graceful restart helper capability, select the check box. Helper mode is enabled by default. 5. Click OK. SPF Options Configure options for running the shortest-path-first (SPF) algorithm. You can configure a delay for when to run the SPF algorithm after a network topology change is detected, the maximum number of times the SPF algorithm can run in succession, and a hold-down interval after the SPF algorithm runs the maximum number of times. To configure SPF: 1. Specify the time interval between the detection of a topology change and when the SPF algorithm runs. 2. Specify the time interval to hold down, or wait before a subsequent SPF algorithm runs after the SPF algorithm has run the configured maximum number of times in succession. 3. Specify the maximum number of times the SPF algorithm can run in succession. After the maximum is reached, the hold-down interval begins. 1438 Chapter 71: Configuring Layer 3 Protocols Table 192: Edit OSPF Global Settings (continued) Field Function Your Action Specifies one or more policies to control which routes learned from an area are used to generate summary link-state advertisements (LSAs) into other areas. Click Add to add an import policy. Policies tab Import Policy Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an import policy. Export Policy Specifies one or more policies to control which summary LSAs are flooded into an area. Click Add to add an export policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an export policy. Trace Options tab File Name Specifies the name of the file to receive the output of the tracing operation. Type or select and edit the name. Number of Files Specifies the maximum number of trace files. Type or select and edit the name. File Size Specifies the maximum size for each trace file. Type or select and edit the name. World Readable Specifies whether the trace file can be read by any user or not. Select True to allow any user to read the file. Select False to disallow all users being able to read the file. Flags Specifies the tracing operation to perform. Related Documentation Select a value from the list. • Monitoring OSPF Routing Information on page 1457 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Configuring a RIP Network (J-Web Procedure) You can use the J-Web interface to create RIP networks. To configure a RIP network: 1439 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1. Select Configure > Routing > RIP. 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 334 for details about all commit options. 2. Click one: • Add—Configures a RIP instance. Enter information into the RIP Configuration page as described in Table 193 on page 1440. • Edit—Modifies an existing RIP instance. Enter information into the configuration page for RIP as described in Table 193 on page 1440. • Delete—Deletes an existing RIP instance. 4. To modify RIP global settings, click Edit. Enter information in the configuration as described in Table 194 on page 1441. Table 193: RIP Routing Configuration Summary Field Function Your Action Routing instance name Specifies a name for the routing instance. Type or select and edit the name. Preference Specifies the preference of external routes learned by RIP as compared to those learned from other routing protocols. Type or select and edit the value. Metric Out Specifies the metric value to add to routes transmitted to the neighbor. Type or select and edit the value. Update interval Specifies an update time interval to periodically send out routes learned by RIP to neighbors. Type or select and edit the value. Route timeout Specifies the route timeout interval for RIP. Type or select and edit the value. Applies one or more policies to routes being imported into the local routing device from the neighbors. Click Add to add an import policy. General tab Policies tab Import Policy Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an import policy. 1440 Chapter 71: Configuring Layer 3 Protocols Table 193: RIP Routing Configuration Summary (continued) Field Function Your Action Export Policy Applies a policy to routes being exported to the neighbors. Click Add to add an export policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an export policy. Neighbors tab RIP-Enabled Interfaces Selects the interfaces to be associated with the RIP instance. To enable RIP on an interface, click the check box next to the interface name. Click Edit if you want to modify an interface’s settings. Table 194: Edit RIP Global Settings Field Function Your Action Send Specifies RIP send options. Select a value. Receive Configure RIP receive options. Select a value. Route timeout (sec) Specifies the route timeout interval for RIP. Type a value. Update interval (sec) Specifies the update time interval to periodically send out routes learned by RIP to neighbors. Type or select and edit the value. Hold timeout (sec) Specifies the time period the expired route is retained in the routing table before being removed. Type or select and edit the value. Metric in Specifies the metric to add to incoming routes when advertising into RIP routes that were learned from other protocols. Type or select and edit the value. RIB Group Specifies a routing table group to install RIP routes into multiple routing tables. Select and edit the name of the routing table group. Message size Specifies the number of route entries to be included in every RIP update message. Type or select and edit the value. General tab 1441 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 194: Edit RIP Global Settings (continued) Field Function Your Action Check Zero Specifies whether the reserved fields in a RIP packet are zero. Options are: Select a value. • check-zero—Discard version 1 packets that have nonzero values in the reserved fields and version 2 packets that have nonzero values in the fields that must be zero. This default behavior implements the RIP version 1 and version 2 specifications. • no-check-zero—Receive RIP version 1 packets with nonzero values in the reserved fields or RIP version 2 packets with nonzero values in the fields that must be zero. This is in spite of the fact that they are being sent in violation of the specifications in RFC 1058 and RFC 2453. Graceful switchover Configures graceful switchover for OSPF. To disable graceful restart, select Disable. Type or select and edit the estimated time for the restart to finish, in seconds. Authentication Type Specifies the type of authentication for RIP route queries received on an interface. Options are: Select the authentication type. Enter the authentication key for MD5. • None • MD5 • Simple Policies tab Import Policy Applies one or more policies to routes being imported into the local routing device from the neighbors. Click Add to add an import policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an import policy. Export Policy Applies a policy to routes being exported to the neighbors. Click Add to add an export policy. Click Move up or Move down to move the selected policy up or down the list of policies. Click Remove to remove an export policy. Trace Options tab File Name Specifies the name of the file to receive the output of the tracing operation. Type or select and edit the name. Number of Files Specifies the maximum number of trace files. Type or select and edit the name. File Size Specifies the maximum size for each trace file. Type or select and edit the name. 1442 Chapter 71: Configuring Layer 3 Protocols Table 194: Edit RIP Global Settings (continued) Field Function Your Action World Readable Specifies whether the trace file can be read by any user or not. Select True to allow any user to read the file. Select False to disallow all users being able to read the file. Flags Specifies the tracing operation to perform. Related Documentation Select a value from the list. • Monitoring RIP Routing Information on page 1460 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 1443 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Static Routing (CLI Procedure) Static routes are routes that are manually configured and entered into the routing table. Dynamic routes, in contrast, are learned by the J-EX Series switch and added to the routing table using a protocol such as OSPF or RIP. The switch uses static routes: • When the switch does not have a route to a destination that has a better (lower) preference value. The preference is an arbitrary value in the range from 0 through 255 that the software uses to rank routes received from different protocols, interfaces, or remote systems. The routing protocol process generally determines the active route by selecting the route with the lowest preference value. In the given range, 0 is the lowest and 255 is the highest. • When the switch cannot determine the route to a destination. • When the switch is forwarding unroutable packets. To configure basic static route options using the CLI: • To configure the switch's default gateway: [edit] user@switch# set routing–options static route 0.0.0.0/0 next-hop 10.0.1.1 • To configure a static route and specify the next address to be used when routing traffic to the static route: [edit] user@switch# set routing-options static route 20.0.0.0/24 next-hop 10.0.0.2.1 • To always keep the static route in the forwarding table: [edit] user@switch# set routing-options static route 20.0.0.0/24 retain • To prevent the static route from being readvertised: [edit] user@switch# set routing-options static route 20.0.0.0/24 no-readvertise • To remove inactive routes from the forwarding table: [edit] user@switch# set routing-options static route 20.0.0.0/24 active Related Documentation • Configuring Static Routing (J-Web Procedure) on page 1444 • Monitoring Routing Information on page 1461 Configuring Static Routing (J-Web Procedure) You can use the J-Web interface to configure static routes for J-EX Series switches. 1444 Chapter 71: Configuring Layer 3 Protocols To configure static routes: 1. Select Configure > Routing > Static Routing. The Static Routing page displays details of the configured routes. 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 334 for details about all commit options. 2. Click one: • Add—To configure a route. Enter information into the routing page as described in Table 195 on page 1445. • Edit—To modify an existing route. Enter information into the routing page as described in Table 195 on page 1445. • Delete—To delete an existing route. Table 195: Static Routing Configuration Summary Field Function Your Action Specifies the default gateway for the switch. To specify an IPv4 address: Default Route Default Route 1. Select IPv4. 2. Type an IP address—for example, 10.10.10.10. 3. Enter the subnet mask or address prefix. For example, 24 bits represents 255.255.255.0. To specify an IPv6 address: 1. Select IPv6. 2. Type an IP address— for example, 2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. Static Routes 1445 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 195: Static Routing Configuration Summary (continued) Field Function Your Action Nexthop Specifies the next-hop address or addresses to be used when routing traffic to the static route. To add an address: 1. Click Add. 2. In the IP address dialog, enter the IP address. NOTE: If a route has multiple next-hop addresses, traffic is routed across each address in round-robin fashion. 3. Click OK. To delete a next-hop address, select it from the list and click Delete. Related Documentation • Configuring Static Routing (CLI Procedure) on page 1444 • Monitoring Routing Information on page 1461 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Configuring Routing Policies (J-Web Procedure) All routing protocols use the Junos OS routing table to store the routes that they learn and to determine which routes are advertised in the protocol packets. Routing policy allows you to control which routes the routing protocols store in and retrieve from the routing table on the routing device. To configure routing policies for a J-EX Series switch using the J-Web interface: 1. Select Configure > Routing > Policies. 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 334 for details about all commit options. 2. Click one: • Global Options—Configures global options for policies. Enter information into the configuration page as described in Table 196 on page 1447. • Add—Configures a new policy. Select New and specify a policy name. To add terms, enter information into the configuration page as described in Table 197 on page 1448. Select Clone to create a copy of an existing policy. 1446 Chapter 71: Configuring Layer 3 Protocols • Edit—Edits an existing policy. To modify an existing term, enter information into the configuration page as described in Table 197 on page 1448. • Term Up—Moves a term up in the list. • Term Down—Moves a term down in the list. • Delete—Deletes the selected policy. • Test Policy—Tests the policy. Use this option to check whether the policy produces the results that you expect. Table 196: Policies Global Configuration Parameters Field Function Your Action Prefix List Specifies a list of IPv4 address prefixes for use in a routing policy statement. To add a prefix list: 1. Click Add. 2. Enter a name for the prefix list. 3. To add an IP address, click Add. 4. Enter the IP address and the subnet mask and click OK. 5. Click OK. To edit a prefix list, click Edit. Edit the settings and click OK. To delete a prefix list, select it and click Delete. BGP Community Specifies a BGP community. To add a BGP community: 1. Click Add. 2. Enter a name for the community. 3. To add a community, click Add. 4. Enter the community ID and click OK. 5. Click OK. To edit a BGP community, click Edit. Edit the settings and click OK. To delete a BGP community, select it and click Delete. AS Path Specifies an AS path. This is applicable to BGP only. To add an AS path: 1. Click Add. 2. Enter the AS path name. 3. Enter the regular expression and click OK. 4. Click OK. To edit an AS path, click Edit. Edit the settings and click OK. To delete an AS path, select it and click Delete. 1447 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 197: Terms Configuration Parameters Field Function Your Action Term Name Specifies a term name. Type or select and edit the name. Family Specifies an address family protocol. Select a value from the list. Routing Instance Specifies a routing instance. Select a value from the list. RIB Specifies the name of a routing table. Select a value from the list Preference Specifies the individual preference value for the route. Type or select and edit the value. Metric Specifies a metric value. You can specify up to four metric values. Type or select and edit the value. Interface Specifies a name or IP address of one or more routing device interfaces. Do not use this qualifier with protocols that are not interface-specific, such as internal BGP (IBGP). To add an interface, select Add > Interface. Select the interface from the list. Source tab To add an address, select Add > Address. Select the address from the list. To remove an interface, select it and click Remove. Prefix List Specifies a named list of IP addresses. You can specify an exact match with incoming routes. Click Add. Select the prefix list from the list and click OK. To remove a prefix list, select it and click Remove. Protocol Specifies the name of the protocol from which the route was learned or to which the route is being advertised. Click Add and select the protocol from the list. To remove a protocol, select it and click Remove. Policy Specifies the name of a policy to evaluate as a subroutine. Click Add. Select the policy from the list. To remove a policy, select it and click Remove. More Specifies advanced configuration options for policies. Click More for advanced configuration. OSPF Area ID Specifies the area identifier. Type the IP address. BGP Origin Specifies the origin of the AS path information. Select a value from the list. Local Preference Specifies the BGP local preference. Type a value. 1448 Chapter 71: Configuring Layer 3 Protocols Table 197: Terms Configuration Parameters (continued) Field Function Your Action Route Specifies the type of route. Select External. Select the OSPF type from the list. AS Path Specifies the name of an AS path regular expression. Click Add. Select the AS path from the list. Community Specifies the name of one or more communities. Click Add. Select the community from the list. Family Specifies an address family protocol. Select a value from the list. Routing Instance Specifies a routing instance. Select a value from the list. RIB Specifies the name of a routing table. Select a value from the list. Preference Specifies the individual preference value for the route. Type a value. Metric Specifies a metric value. Type a value. Interface Specifies a name or IP address of one or more routing device interfaces. Do not use this qualifier with protocols that are not interface-specific, such as internal BGP (IBGP). To add an interface, select Add > Interface. Select the interface from the list. Destination tab To add an address, select Add > Address. Select the address from the list. To delete an interface, select it and click Remove. Protocol Specifies the name of the protocol from which the route was learned or to which the route is being advertised. Click Add and select the protocol from the list. To delete a protocol, select it and click Remove. Action tab Action Specifies the action to take if the conditions match. Select a value from the list. Default Action Specifies that any action that is intrinsic to the protocol is overridden. This action is also nonterminating, so that various policy terms can be evaluated before the policy is terminated. Select a value from the list. Next Specifies the default control action if a match occurs, and there are no further terms in the current routing policy. Select a value from the list. Priority Specifies a priority for prefixes included in an OSPF import policy. Prefixes learned through OSPF are installed in the routing table based on the priority assigned to the prefixes. Select a value from the list. BGP Origin Specifies the BGP origin attribute. Select a value from the list. 1449 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 197: Terms Configuration Parameters (continued) Field Function Your Action AS Path Prepend Affixes an AS number at the beginning of the AS path. The AS numbers are added after the local AS number has been added to the path. This action adds an AS number to AS sequences only, not to AS sets. If the existing AS path begins with a confederation sequence or set, the affixed AS number is placed within a confederation sequence. Otherwise, the affixed AS number is placed with a nonconfederation sequence. Enter a value. AS Path Expand Extracts the last AS number in the existing AS path and affixes that AS number to the beginning of the AS path n times, where n is a number from 1 through 32. The AS number is added before the local AS number has been added to the path. This action adds AS numbers to AS sequences only, not to AS sets. If the existing AS path begins with a confederation sequence or set, the affixed AS numbers are placed within a confederation sequence. Otherwise, the affixed AS numbers are placed within a nonconfederation sequence. This option is typically used in non-IBGP export policies. Select the type and type a value. Load Balance Per Packet Specifies that all next-hop addresses in the forwarding table must be installed and have the forwarding table perform per-packet load balancing. This policy action allows you to optimize VPLS traffic flows across multiple paths. Select the check box to enable the option. Tag Specifies the tag value. The tag action sets the 32-bit tag field in OSPF external link-state advertisement (LSA) packets. Select the action and type a value. Metric Changes the metric (MED) value by the specified negative or positive offset. This action is useful only in an external BGP (EBGP) export policy. Select the action and type a value. Route Specifies whether the route is external. Select the External check box to enable the option, and select the OSPF type. Preference Specifies the preference value. Select the preference action and type a value. Local Preference Specifies the BGP local preference attribute. Select the action and type a value. Class of Service Specifies and applies the class-of-service parameters to routes installed into the routing table. Type the source class. Type the destination class. • Source class The value entered here maintains the packet counts for a route passing through your network, based on the source address. • Destination class The value entered here maintains packet counts for a route passing through your network, based on the destination address in the packet. • 1450 Forwarding class Type the forwarding class. Chapter 71: Configuring Layer 3 Protocols Related Documentation • Configuring BGP Sessions (J-Web Procedure) on page 1431 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Configuring a RIP Network (J-Web Procedure) on page 1439 • Configuring Static Routing (J-Web Procedure) on page 1444 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Configuring Distributed Periodic Packet Management on a J-EX Series Switch (CLI Procedure) Periodic packet management (PPM) is responsible for processing a variety of time-sensitive periodic tasks so that other processes on the J-EX Series switch can more optimally direct their resources. The responsibility for PPM processing on the switch is distributed between the Routing Engine and either the access interfaces (on J-EX4200 switches) or the line cards (on J-EX8200 switches) for all protocols that use PPM by default. This distributed model provides a faster response time for protocols that use PPM than the response time provided by the nondistributed model. If distributed PPM is disabled, the PPM process runs on the Routing Engine only. Distributed PPM can be disabled for all protocols that use PPM or for a single protocol that uses PPM. BEST PRACTICE: We recommend that, generally, you disable distributed PPM only if Dell Support advises you to do so (see “Requesting Technical Support” on page lxxi). You should disable distributed PPM only if you have a compelling reason to disable it. This topic describes: • Disabling or Enabling Distributed Periodic Packet Management Globally on page 1451 • Disabling or Enabling Distributed Periodic Packet Management for Link Aggregation Control Protocol (LACP) Packets on page 1452 Disabling or Enabling Distributed Periodic Packet Management Globally Distributed PPM is enabled by default. Disable distributed PPM if you need to move all PPM processing to the Routing Engine. Enable distributed PPM if it was previously disabled and you need to run distributed PPM. To disable distributed PPM: [edit routing-options] user@switch# set ppm no-delegate-processing To enable distributed PPM if it was previously disabled: [edit routing-options] 1451 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch# delete ppm no-delegate-processing Disabling or Enabling Distributed Periodic Packet Management for Link Aggregation Control Protocol (LACP) Packets Distributed PPM is enabled by default. Disable distributed PPM for only LACP packets if you need to move all PPM processing for LACP packets to the Routing Engine. To disable distributed PPM for LACP packets: [edit protocols] user@switch# set lacp ppm centralized To enable distributed PPM for LACP packets if it was previously disabled: [edit protocols] user@switch# delete lacp ppm centralized Related Documentation • Understanding Distributed Periodic Packet Management on J-EX Series Switches on page 1424 • Understanding Aggregated Ethernet Interfaces and LACP on page 867 Configuring VRRP for IPv6 (CLI Procedure) By configuring the Virtual Router Redundancy Protocol (VRRP) on J-EX Series switches, you can enable 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. You can configure VRRP for IPv6 on Gigabit Ethernet, 10-Gigabit Ethernet, and logical interfaces. To configure VRRP for IPv6: 1. Configure VRRP group support on interfaces: [edit interfaces interface-name unit logical-unit-number family inet6 address address] user@switch# set vrrp-inet6-group group-id priority number virtual-inet6-address address virtual-link-local-address ipv6-address You must explicitly define a virtual link local address for each VRRP for IPv6 group. Otherwise, when you attempt to commit the configuration, the commit request fails. The virtual link local address must be on the same subnet as the physical interface address. 2. If you want to configure the priority order in which this switch functioning as a backup router becomes the master router if the master router becomes nonoperational, configure a priority for this switch: [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] user@switch# set priority number 3. Specify the interval in milliseconds in which the master router sends advertisement packets to the members of the VRRP group: [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] 1452 Chapter 71: Configuring Layer 3 Protocols user@switch# set inet6-advertise-interval milliseconds 4. By default, a higher-priority backup router preempts a lower-priority master router. • To explicitly enable the master router to be preempted: [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] user@switch# set preempt • To prohibit a higher-priority backup router from preempting a lower priority master router: [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] user@switch# set no-preempt Related Documentation • show vrrp on page 2036 • Understanding VRRP on J-EX Series Switches on page 1425 Using IPsec to Secure OSPFv3 Networks (CLI Procedure) OSPF version 3 (OSPFv3) does not have a built-in authentication method and relies on IP Security (IPsec) to provide this functionality. You can use IPsec to secure OSPFv3 interfaces on J-EX Series switches. This topic includes: • Configuring Security Associations on page 1453 • Securing OPSFv3 Networks on page 1454 Configuring Security Associations When you configure a security association (SA), include your choices for authentication, encryption, direction, mode, protocol, and security parameter index (SPI). To configure a security association: 1. Specify a name for the security association: [edit security ipsec] user@switch# set security-association sa-name 2. Specify the mode of the security association: [edit security ipsec security-association sa-name] user@switch# set mode transport 3. Specify the type of security association: [edit security ipsec security-association sa-name] user@switch# set type manual 4. Specify the direction of the security association: [edit security ipsec security-association sa-name] 1453 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch# set direction bidirectional 5. Specify the value of the security parameter index: [edit security ipsec security-association sa-name] user@switch# set spi spi-value 6. Specify the type of authentication to be used: [edit security ipsec security-association sa-name] user@switch# set authentication algorithm type 7. Specify the encryption algorithm and key: [edit security ipsec security-association sa-name] user@switch# set encryption algorithm algorithm key type Securing OPSFv3 Networks You can secure the OSPFv3 network by applying the SA to the OSPFv3 configuration. To secure the OSPFv3 network: [edit protocols ospf3 area area-number interface interface-name] user@switch# set ipsec-sa sa-name Related Documentation 1454 • Understanding IPsec Authentication for OSPF Packets on J-EX Series Switches on page 1428 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • For details on these configuration statements, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/index.html. CHAPTER 72 Verifying Layer 3 Protocols Configuration • Monitoring BGP Routing Information on page 1455 • Monitoring OSPF Routing Information on page 1457 • Monitoring RIP Routing Information on page 1460 • Monitoring Routing Information on page 1461 Monitoring BGP Routing Information Purpose Action Use the monitoring functionality to monitor BGP routing information on the routing device. To view BGP routing information in the J-Web interface, select Monitor>Routing>BGP Information. To view BGP routing information in the CLI, enter the following commands: Meaning • show bgp summary • show bgp neighbor Table 198 on page 1455 summarizes key output fields in the BGP routing display in the J-Web interface. Table 198: Summary of Key BGP Routing Output Fields Field Values Additional Information BGP Peer Summary Total Groups Number of BGP groups. Total Peers Number of BGP peers. Down Peers Number of unavailable BGP peers. Unconfigured Peers Address of each BGP peer. RIB Summary tab RIB Name Name of the RIB group. 1455 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 198: Summary of Key BGP Routing Output Fields (continued) Field Values Total Prefixes Total number of prefixes from the peer, both active and inactive, that are in the routing table. Active Prefixes Number of prefixes received from the EBGP peers that are active in the routing table. Suppressed Prefixes Number of routes received from EBGP peers currently inactive because of damping or other reasons. History Prefixes History of the routes received or suppressed. Dumped Prefixes Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols. Pending Prefixes Number of pending routes. State Status of the graceful restart process for this routing table: BGP restart is complete, BGP restart in progress, VPN restart in progress, or VPN restart is complete. BGP Neighbors Details Click this button to view the selected BGP neighbor details. Peer Address Address of the BGP neighbor. Autonomous System AS number of the peer. 1456 Additional Information Chapter 72: Verifying Layer 3 Protocols Configuration Table 198: Summary of Key BGP Routing Output Fields (continued) Field Values Additional Information Peer State Current state of the BGP session: Generally, the most common states are Active, which indicates a problem establishing the BGP connection, and Established, which indicates a successful session setup. The other states are transition states, and BGP sessions normally do not stay in those states for extended periods of time. • Active—BGP is initiating a TCP connection in an attempt to connect to a peer. If the connection is successful, BGP sends an open message. • Connect—BGP is waiting for the TCP connection to become complete. • Established—The BGP session has been established, and the peers are exchanging BGP update messages. • Idle—This is the first stage of a connection. BGP is waiting for a Start event. • OpenConfirm—BGP has acknowledged receipt of an open message from the peer and is waiting to receive a keepalive or notification message. • OpenSent—BGP has sent an open message and is waiting to receive an open message from the peer. Elapsed Time Elapsed time since the peering session was last reset. Description Description of the BGP session. Related Documentation • Configuring BGP Sessions (J-Web Procedure) on page 1431 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Monitoring OSPF Routing Information Purpose Action Use the monitoring functionality to monitor OSPF routing information on routing devices. To view OSPF routing information in the J-Web interface, select Monitor > Routing > OSPF Information. To view OSPF routing information in the CLI, enter the following CLI commands: Meaning • show ospf neighbor • show ospf interface • show ospf statistics Table 199 on page 1458 summarizes key output fields in the OSPF routing display in the J-Web interface. 1457 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 199: Summary of Key OSPF Routing Output Fields Field Values Additional Information OSPF Interfaces Interface Name of the interface running OSPF. State State of the interface: BDR, Down, DR, DRother, Loop, PtToPt, or Waiting. Area Number of the area that the interface is in. DR ID Address of the area's designated device. BDR ID Address of the area's backup designated device. Neighbors Number of neighbors on this interface. Adjacency Count Number of devices in the area using the same area identifier. Stub Type The areas into which OSPF does not flood AS external advertisements Passive Mode In this mode the interface is present on the network but does not transmit or receive packets. Authentication Type The authentication scheme for the backbone or area. Interface Address The IP address of the interface. Address Mask The subnet mask or address prefix. MTU The maximum transmission unit size. Interface Cost The path cost used to calculate the root path cost from any given LAN segment is determined by the total cost of each link in the path. Hello Interval How often the routing device sends hello packets out of the interface. Dead Interval The interval during which the routing device receives no hello packets from the neighbor. Retransmit Interval The interval for which the routing device waits to receive a link-state acknowledgment packet before retransmitting link-state advertisements to an interface’s neighbors. 1458 The Down state, indicating that the interface is not functioning, and PtToPt state, indicating that a point-to-point connection has been established, are the most common states. Chapter 72: Verifying Layer 3 Protocols Configuration Table 199: Summary of Key OSPF Routing Output Fields (continued) Field Values Additional Information OSPF Statistics Packets tab Sent Displays the total number of packets sent. Received Displays the total number of packets received. Details tab Flood Queue Depth Number of entries in the extended queue. Total Retransmits Number of retransmission entries enqueued. Total Database Summaries Total number of database description packets. OSPF Neighbors Address Address of the neighbor. Interface Interface through which the neighbor is reachable. State State of the neighbor: Attempt, Down, Exchange, ExStart, Full, Init, Loading, or 2way. ID ID of the neighbor. Priority Priority of the neighbor to become the designated router. Activity Time The activity time. Area Area that the neighbor is in. Options Option bits received in the hello packets from the neighbor. DR Address Address of the designated router. BDR Address Address of the backup designated router. Uptime Length of time since the neighbor came up. Generally, only the Down state, indicating a failed OSPF adjacency, and the Full state, indicating a functional adjacency, are maintained for more than a few seconds. The other states are transitional states that a neighbor is in only briefly while an OSPF adjacency is being established. 1459 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 199: Summary of Key OSPF Routing Output Fields (continued) Field Values Adjacency Length of time since the adjacency with the neighbor was established. Related Documentation Additional Information • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Monitoring RIP Routing Information Purpose Action Use the monitoring functionality to monitor RIP routing on routing devices. To view RIP routing information in the J-Web interface, select Monitor > Routing > RIP Information. To view RIP routing information in the CLI, enter the following CLI commands: Meaning • show rip statistics • show rip neighbor Table 200 on page 1460 summarizes key output fields in the RIP routing display in the J-Web interface. Table 200: Summary of Key RIP Routing Output Fields Field Values RIP Statistics Protocol Name The RIP protocol name. Port number The port on which RIP is enabled. Hold down time The interval during which routes are neither advertised nor updated. Global routes learned Number of RIP routes learned on the logical interface. Global routes held down Number of RIP routes that are not advertised or updated during the hold-down interval. Global request dropped Number of requests dropped. Global responses dropped Number of responses dropped. 1460 Additional Information Chapter 72: Verifying Layer 3 Protocols Configuration Table 200: Summary of Key RIP Routing Output Fields (continued) Field Values Additional Information Neighbor Name of the RIP neighbor. This value is the name of the interface on which RIP is enabled. Click the name to see the details for this neighbor. State State of the RIP connection: Up or Dn (Down). Source Address Local source address. This value is the configured address of the interface on which RIP is enabled. Destination Address Destination address. This value is the configured address of the immediate RIP adjacency. Send Mode The mode of sending RIP messages. Receive Mode The mode in which messages are received. In Metric Value of the incoming metric configured for the RIP neighbor. RIP Neighbors Related Documentation • Configuring a RIP Network (J-Web Procedure) on page 1439 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 Monitoring Routing Information Purpose Action Use the monitoring functionality to view the inet.0 routing table on the routing device. To view the routing tables in the J-Web interface, select Monitor > Routing > Route Information. Apply a filter or a combination of filters to view messages. You can use filters to display relevant events. To view the routing table in the CLI, enter the following commands in the CLI interface: Meaning • show route terse • show route detail Table 201 on page 1462 describes the different filters, their functions, and the associated actions. Table 202 on page 1462 summarizes key output fields in the routing information display. 1461 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 201: Filtering Route Messages Field Function Your Action Destination Address Specifies the destination address of the route. Enter the destination address. Protocol Specifies the protocol from which the route was learned. Enter the protocol name. Next hop address Specifies the network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it. Enter the next hop address. Receive protocol Specifies the dynamic routing protocol using which the routing information was received through a particular neighbor. Enter the routing protocol. Best route Specifies only the best route available. Select the view details of the best route. Inactive routes Specifies the inactive routes. Select the view details of inactive routes. Exact route Specifies the exact route. Select the view details of the exact route. Hidden routes Specifies the hidden routes. Select the view details of hidden routes. Search Applies the specified filter and displays the matching messages. To apply the filter and display messages, click Search. Table 202: Summary of Key Routing Information Output Fields Field Values Static Route Addresses The list of static route addresses. Protocol Protocol from which the route was learned: Static, Direct, Local, or the name of a particular protocol. Preference The preference is the individual preference value for the route. 1462 Additional Information The route preference is used as one of the route selection criteria. Chapter 72: Verifying Layer 3 Protocols Configuration Table 202: Summary of Key Routing Information Output Fields (continued) Field Values Additional Information Next-Hop Network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it. If a next hop is listed as Discard, all traffic with that destination address is discarded rather than routed. This value generally means that the route is a static route for which the discard attribute has been set. If a next hop is listed as Reject, all traffic with that destination address is rejected. This value generally means that the address is unreachable. For example, if the address is a configured interface address and the interface is unavailable, traffic bound for that address is rejected. If a next hop is listed as Local, the destination is an address on the host (either the loopback address or Ethernet management port 0 address, for example). Age How long the route has been active. State Flags for this route. AS Path AS path through which the route was learned. The letters of the AS path indicate the path origin: • I—IGP. • E—EGP. • ?—Incomplete. Typically, the AS path was There are many possible flags. aggregated. Related Documentation • Configuring Static Routing (J-Web Procedure) on page 1444 • Configuring Static Routing (CLI Procedure) on page 1444 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 1463 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1464 CHAPTER 73 Configuration Statements for Layer 3 Protocols accept-remote-nexthop Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation accept-remote-nexthop; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify that a single-hop EBGP peer accept a remote next hop with which it does not share a common subnet. Configure a separate import policy on the EBGP peer to specify the remote next hop. You cannot configure the multihop statement at the same time. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • multipath on page 1623 • Configuring Single-Hop EBGP Peers to Accept Remote Next Hops • Applying Policies to BGP Routes 1465 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS active Syntax Hierarchy Level Release Information Description (active | passive); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether static, aggregate, or generated routes are removed from the routing and forwarding tables when they become inactive. Routes that have been configured to remain continually installed in the routing and forwarding tables are marked with reject next hops when they are inactive. • active—Remove a route from the routing and forwarding tables when it becomes inactive. • passive—Have a route remain continually installed in the routing and forwarding tables even when it becomes inactive. Default Required Privilege Level Related Documentation 1466 active routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static Routes • Configuring Aggregate Routes • Configuring Generated Routes Chapter 73: Configuration Statements for Layer 3 Protocols advertise-external Syntax Hierarchy Level Release Information Description Options advertise-external { conditional; } [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor neighbor-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Have BGP advertise the best external route into an IBGP mesh group, a route reflector cluster, or an AS confederation even if the best route is an internal route. conditonal—(Optional) Advertise the best external path only if the route selection process reaches the point where the multiple exit discriminator (MED) metric is evaluated. As a result, an external path with an AS path worse than that of the active path is not advertised. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • advertise-inactive on page 1468 • Applying Policies to BGP Routes 1467 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS advertise-inactive Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1468 advertise-inactive; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Have BGP advertise the best route even if the routing table did not select it to be an active route. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to BGP Routes Chapter 73: Configuration Statements for Layer 3 Protocols advertise-peer-as Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation advertise-peer-as; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the default behavior of suppressing AS routes. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to BGP Routes 1469 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS aggregate Syntax Hierarchy Level Release Information Description Options aggregate { defaults { ... aggregate-options ... } route destination-prefix { policy policy-name; ... aggregate-options ... } } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name], [edit logical-systems logical-system-name routing-options], [edit logical-systems logical-system-name routing-options rib routing-table-name], [edit routing-instances routing-instance-name routing-options], [edit routing-instances routing-instance-name routing-options rib routing-table-name], [edit routing-options], [edit routing-options rib routing-table-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure aggregate routes. aggregate-options—Additional information about aggregate routes that is included with the route when it is installed in the routing table. Specify zero or more of the following options in aggregate-options. Each option is explained separately. • (active | passive); • as-path ; • (brief | full); • community [ community-ids ]; • discard; • (metric | metric2 | metric3 | metric4) value ; • (preference | preference2 | color | color2) preference ; • tag string; defaults—Specify global aggregate route options. These options only set default attributes inherited by all newly created aggregate routes. These are treated as global defaults and apply to all the aggregate routes you configure in the aggregate statement. This part of the aggregate statement is optional. route destination-prefix—Configure a nondefault aggregate route: 1470 Chapter 73: Configuration Statements for Layer 3 Protocols • default—For the default route to the destination. This is equivalent to specifying an IP address of 0.0.0.0/0. • destination-prefix/prefix-length—destination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length. The policy statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Aggregate Routes aggregate-label Syntax Hierarchy Level Release Information Description Options aggregate-label { community community-name; } [edit logical-systems logical-system-name protocols bgp family inet labeled-unicast], [edit logical-systems logical-system-name protocols bgp family inet-vpn labeled-unicast], [edit protocols bgp family inet labeled-unicast], [edit protocols bgp family inet-vpn labeled-unicast], [edit protocols bgp family inet6 labeled-unicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable aggregate labels for VPN traffic. community community-name—Specify the name of the community to which to apply the aggregate label. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Aggregate Labels for VPNs 1471 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS allow Syntax Hierarchy Level Release Information Description Options allow (all | [ network/mask-length ]); [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Implicitly configure BGP peers, allowing peer connections from any of the specified networks or hosts. To configure multiple BGP peers, configure one or more networks and hosts within a single allow statement or include multiple allow statements. all—Allow all addresses, which is equivalent to 0.0.0.0/0 (or ::/0). network/mask-length—IPv6 or IPv4 network number of a single address or a range of allowable addresses for BGP peers, followed by the number of significant bits in the subnet mask. Required Privilege Level Related Documentation 1472 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • neighbor on page 1624 • Minimum BGP Configuration • Configuring BGP Groups and Peers Chapter 73: Configuration Statements for Layer 3 Protocols any-sender Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation any-sender; [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable strict sender address checks. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling Strict Address Checking for RIP Messages 1473 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS area Syntax Hierarchy Level Release Information Description area area-id; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the area identifier for this routing device to use when participating in OSPF routing. All routing devices in an area must use the same area identifier to establish adjacencies. Specify multiple area statements to configure the routing device as an area border router. An area border router does not automatically summarize routes between areas; use the area-range statement to configure route summarization. By definition, an area border router must be connected to the backbone area either through a physical link or through a virtual link. To create a virtual link, include the virtual-link statement. To specify that the routing device is directly connected to the OSPF and OSPFv3 backbone, include the area 0.0.0.0 statement. All routing devices on the backbone must be contiguous. If they are not, use the virtual-link statement to create the appearance of connectivity to the backbone. Options area-id—Area identifier. The identifier can be up to 32 bits. It is common to specify the area number as a simple integer or an IP address. Area number 0.0.0.0 is reserved for the OSPF and OSPFv3 backbone area. Required Privilege Level Related Documentation 1474 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • virtual-link on page 1742 • Configuring OSPF Areas • Configuring Multiple Address Families for OSPFv3 Chapter 73: Configuration Statements for Layer 3 Protocols area-range Syntax Hierarchy Level Release Information Description area-range network/mask-length ; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa], [edit logical-systems logical-system-name realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa], [edit logical-systems logical-system-name routing-instances routing-instance-name realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit protocols (ospf | ospf3) area area-id], [edit protocols (ospf | ospf3) area area-id nssa], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa], [edit routing-instances routing-instance-name realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Area border routers only) For an area, summarize a range of IP addresses when sending summary link advertisements (within an area). To summarize multiple ranges, include multiple area-range statements. For a not-so-stubby area (NSSA), summarize a range of IP addresses when sending NSSA link-state advertisements. The specified prefixes are used to aggregate external routes learned within the area when the routes are advertised to other areas. To specify multiple prefixes, include multiple area-range statements. All external routes learned within the area that do not fall into one of the prefixes are advertised individually to other areas. Default Options By default, area border routers do not summarize routes being sent from one area to other areas, but rather send all routes explicitly. exact—(Optional) Summarization of a route is advertised only when an exact match is made with the configured summary range. mask-length—Number of significant bits in the network mask. network—IP address. You can specify one or more IP addresses. override-metric metric—(Optional) Override the metric for the IP address range and configure a specific metric value. restrict—(Optional) Do not advertise the configured summary. This hides all routes that are contained within the summary, effectively creating a route filter. Range: 1 through 16,777,215 1475 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Summarizing Ranges of Routes in OSPF Link-State Advertisements as-override Syntax Hierarchy Level Release Information Description as-override; [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Compare the AS path of an incoming advertised route with the AS number of the BGP peer under the group and replace all occurrences of the peer AS number in the AS path with its own AS number before advertising the route to the peer. NOTE: The as-override statement is specific to a particular BGP group. This statement does not affect peers from the same remote AS configured in different groups. Enabling the AS override feature allows routes originating from an AS to be accepted by a router residing in the same AS. Without AS override enabled, the routing device refuses the route advertisement once the AS path shows that the route originated from its own AS. This is done by default to prevent route loops. The as-override statement overrides this default behavior. Note that enabling the AS override feature may result in routing loops. Use this feature only for specific applications that require this type of behavior, and in situations with strict network control. One application is the IGP protocol between the provider edge routing device and the customer edge routing device in a virtual private network. For more information, see the Junos OS MPLS Applications Configuration Guide. Required Privilege Level Related Documentation 1476 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BGP Groups and Peers Chapter 73: Configuration Statements for Layer 3 Protocols as-path Syntax Hierarchy Level Release Information Description as-path ; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate BGP autonomous system (AS) path information with a static, aggregate, or generated route. The numeric range for the AS number provides BGP support for 2-byte AS numbers and 4-byte AS numbers. . Options aggregator—(Optional) Attach the BGP aggregator path attribute to the aggregate route. You must specify the last AS number that formed the aggregate route (encoded as two octets) for as-number, followed by the IP address of the BGP system that formed the aggregate route for in-address. as-path—(Optional) AS path to include with the route. It can include a combination of individual AS path numbers and AS sets. Enclose sets in brackets ( [ ] ). The first AS number in the path represents the AS immediately adjacent to the local AS. Each subsequent number represents an AS that is progressively farther from the local AS, heading toward the origin of the path. You cannot specify a regular expression for as-path; you must use a full, valid AS path. atomic-aggregate—(Optional) Attach the BGP atomic-aggregate path attribute to the aggregate route. This path attribute indicates that the local system selected a less specific route instead of a more specific route. origin egp—(Optional) BGP origin attribute that indicates that the path information originated in another AS. origin igp—(Optional) BGP origin attribute that indicates that the path information originated within the local AS. origin incomplete—(Optional) BGP origin attribute that indicates that the path information was learned by some other means. 1477 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static Routes • Configuring Aggregate Routes • Configuring Generated Routes asm-override-ssm Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1478 asm-override-ssm; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the routing device to accept any-source multicast join messages (*,G) for group addresses that are within the default or configured range of source-specific multicast groups. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Source-Specific Multicast Groups Chapter 73: Configuration Statements for Layer 3 Protocols authentication-algorithm Syntax Hierarchy Level Release Information Description Options authentication-algorithm algorithm; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an authentication algorithm type. algorithm—Type of authentication algorithm. Specify md5, hmac-sha-1-96, or aes-128-cmac-96 as the algorithm type. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Authentication for BGP 1479 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-key Syntax Hierarchy Level Release Information Description Options authentication-key key; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an MD5 authentication key (password). Neighboring routing devices use the same password to verify the authenticity of BGP packets sent from this system. key—Authentication password. It can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). Required Privilege Level Related Documentation 1480 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Authentication for BGP Chapter 73: Configuration Statements for Layer 3 Protocols authentication-key Syntax Hierarchy Level Release Information Description authentication-key key; [edit logical-systems logical-system-name protocols isislevel level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Authentication key (password). Neighboring routing devices use the password to verify the authenticity of packets sent from this interface. For the key to work, you also must include the authentication-type statement. All routing devices must use the same password. If you are using the Junos OS IS-IS software with another implementation of IS-IS, the other implementation must be configured to use the same password for the domain, the area, and all interfaces adjacent to the Dell PowerConnect J-Series routing device. Default If you do not include this statement and the authentication-type statement, IS-IS authentication is disabled. Options key—Authentication password. The password can be up to 1024 characters long. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). CAUTION: A simple password for authentication is truncated if it exceeds 254 characters. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Authentication 1481 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-key Syntax Hierarchy Level Release Information Description Options authentication-key password; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Require authentication for RIP route queries received on an interface. password—Authentication password. If the password does not match, the packet is rejected. The password can be from 1 through 16 contiguous characters long and can include any ASCII strings. Required Privilege Level Related Documentation 1482 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Authentication for RIP Chapter 73: Configuration Statements for Layer 3 Protocols authentication-key-chain Syntax Hierarchy Level Release Information Description Options authentication-key-chain key-chain; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply and enable an authentication keychain to the routing device. key-chain—Authentication keychain name. It can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Authentication for BGP 1483 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-key-chains Syntax Hierarchy Level Release Information authentication-key-chains { key-chain key-chain-name { description text-string; key key { secret secret-data; start-time yyyy-mm-dd.hh:mm:ss; } tolerance seconds; } } [edit security] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure authentication key updates for the Border Gateway Protocol (BGP), the Label Distribution Protocol (LDP) routing protocols, and the Bidirectional Forwarding Detection (BFD) protocol. When the authentication-key-chains statement is configured at the [edit security] hierarchy level, and is associated with the BGP and LDP protocols at the [edit protocols] hierarchy level or with the BFD protocol using the bfd-liveness-detection statement, authentication key updates can occur without interrupting routing and signaling protocols such as Open Shortest Path First (OSPF), and Resource Reservation Setup Protocol (RSVP). Options key-chain key-chain-name—Keychain name. This name is configured at the [edit protocols bgp] or the [edit protocols ldp] hierarchy level to associate unique authentication key-chain attributes with each protocol as specified using the following options: • description text-string—A text string of the authentication-key-chain. Put the text string in quotes (“text description”). • key key—Each key within a keychain is identified by a unique integer value. Range: 0 through 63 • secret secret-data—Each key must specify a secret in encrypted text or plain text format. The secret always appears in encrypted format. • start-time yyyy–mm-dd.hh:mm:ss—Start times are specified in UTC (Coordinated Universal Time), and must be unique within the keychain. • tolerance seconds—Specify the clock skew tolerance, in seconds. Range: 0 through 999999999 Required Privilege Level Related Documentation 1484 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Authentication Key Update Mechanism for BGP and LDP Routing Protocols Chapter 73: Configuration Statements for Layer 3 Protocols • Configuring BFD Authentication for Static Routes authentication-type Syntax Hierarchy Level Release Information Description Default Options authentication-type authentication; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable authentication and specify the authentication scheme for IS-IS. If you enable authentication, you must specify a password by including the authentication-key statement. If you do not include this statement and the authentication-key statement, IS-IS authentication is disabled. authentication—Authentication scheme: • md5—Use HMAC authentication in combination with MD5. HMAC-MD5 authentication is defined in RFC 2104, HMAC: Keyed-Hashing for Message Authentication. • simple—Use a simple password for authentication. The password is included in the transmitted packet, making this method of authentication relatively insecure. We recommend that you not use this authentication method. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • authentication-key on page 1481 • no-authentication-check on page 1631 • Configuring IS-IS Authentication 1485 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-type Syntax Hierarchy Level Release Information Description Default Options authentication-type type; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the type of authentication for RIP route queries received on an interface. If you do not include this statement and the authentication-key statement, RIP authentication is disabled. type—Authentication type: • md5—Use the MD5 algorithm to create an encoded checksum of the packet. The encoded checksum is included in the transmitted packet. The receiving routing device uses the authentication key to verify the packet, discarding it if the digest does not match. This algorithm provides a more secure authentication scheme. • none—Disable authentication. If none is configured, the configured authentication key is ignored. • simple—Use a simple password. The password is included in the transmitted packet, which makes this method of authentication relatively insecure. The password can be from 1 through 16 contiguous letters or digits long. Required Privilege Level Related Documentation 1486 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • authentication-key on page 1482 • Configuring Authentication for RIP Chapter 73: Configuration Statements for Layer 3 Protocols autonomous-system Syntax Hierarchy Level Release Information Description autonomous-system autonomous-system { independent-domain; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the routing device’s AS number. The numeric range provides BGP support for 4-byte AS numbers as defined in RFC 4893, BGP Support for Four-octet AS Number Space. You can also configure a 4-byte AS number using the AS-dot notation format of two integer values joined by a period: <16-bit high-order value in decimal>.<16-bit low-order value in decimal>. For example, the 4-byte AS number of 65,546 in plain-number format is represented as 1.10 in the AS-dot notation format. Options autonomous-system—AS number. Use a number assigned to you by the Network Information Center (NIC). 32 Range: 1 through 4,294,967,295 (2 – 1) in plain-number format Range: 0.0 through 65535.65535 in AS-dot notation format asdot-notation—(Optional) Display the configured 4-byte autonomous system number in the AS-dot notation format. Default: Even if a 4-byte AS number is configured in the AS-dot notation format, the default is to display the AS number in the plain-number format. number—(Optional) Maximum number of times this AS number can appear in an AS path. Range: 1 through 10 Default: 1 (AS number can appear once) 1487 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: When you specify the same AS number in more than one routing instance on the local routing device, you must configure the same number of loops for the AS number in each instance. For example, if you configure a value of 3 for the loops statement in a VRF routing instance that uses the same AS number as that of the master instance, you must also configure a value of 3 loops for the AS number in the master instance. Use the independent-domain option if the loops statement must be enabled only on a subset of routing instances. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • independent-domain • Configuring AS Numbers for BGP backup-pe-group Syntax Hierarchy Level Release Information Description Options backup-pe-group group-name { backups [ addresses ]; local-address address; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a backup provider edge (PE) group for ingress PE redundancy when point-to-multipoint label-switched paths (LSPs) are used for multicast distribution. group-name—Name of the group for PE backups. The remaining statements are explained separately. Required Privilege Level Related Documentation 1488 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Ingress PE Redundancy Chapter 73: Configuration Statements for Layer 3 Protocols backups Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation backups [ addresses ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast backup-pe-group group-name], [edit logical-systems logical-system-name routing-options multicast backup-pe-group group-name], [edit routing-instances routing-instance-name routing-options multicast backup-pe-group group-name], [edit routing-options multicast backup-pe-group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the address of backup PEs for ingress PE redundancy when point-to-multipoint label-switched paths (LSPs) are used for multicast distribution. addresses—Addresses of other PEs in the backup group. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Ingress PE Redundancy 1489 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bandwidth Syntax Hierarchy Level Release Information Description Options bandwidth ( bps | adaptive ); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast flow-map], [edit logical-systems logical-system-name routing-options multicast flow-map], [edit routing-instances routing-instance-name routing-options multicast flow-map], [edit routing-options multicast flow-map] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the bandwidth property for multicast flow maps. adaptive—Specify that the bandwidth is measured for the flows that are matched by the flow map. bps—Bandwidth, in bits per second, for the flow map. Range: 0 through any amount of bandwidth Default: 2 Mbps Required Privilege Level Related Documentation 1490 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Defining Bandwidth for Multicast Flows Chapter 73: Configuration Statements for Layer 3 Protocols bandwidth-based-metrics Syntax Hierarchy Level Release Information Description Options bandwidth-based-metrics { bandwidth value; metric number; } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf area area-id interface interface-name topology topology-name], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf area area-id interface interface-name topology topology-name], [edit logical-systems logical-system-name routing-instances routing-instances protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf area area-id interface interface-name topology topology-name], [edit protocols ospf3 realm (ivp4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf area area-id interface interface-name topology topology-name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a set of bandwidth threshold values and associated metric values for an OSPF interface or for a topology on an OSPF interface. When the bandwidth of an interface changes, the Junos OS automatically sets the interface metric to the value associated with the appropriate bandwidth threshold value. bandwidth value—Specify the bandwidth threshold in bits per second. Range: 9600 through 1,000,000,000,000,000 metric number—Specify a metric value to associate with a specific bandwidth value. Range: 1 through 65,535 NOTE: You must also configure a static metric value for the OSPF interface or topology with the metric statement. The Junos OS uses this value to calculate the cost of a route from the OSPF interface or topology if the bandwidth for the interface is higher than of any bandwidth threshold values configured for bandwidth-based metrics. 1491 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation 1492 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • metric on page 1611 • Dynamically Adjusting OSPF Interface Metrics Based on Bandwidth Chapter 73: Configuration Statements for Layer 3 Protocols bfd-liveness-detection Syntax Hierarchy Level Release Information Description bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; ; } detection-time { threshold milliseconds; } holddown-interval milliseconds; minimum-interval milliseconds; minimum-receive-interval milliseconds; multiplier number; no-adaptation; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } version (1 | automatic); } [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure bidirectional failure detection timers and authentication. For IBGP and multihop EBGP support, configure the bfd-liveness-detection statement at the global [edit bgp protocols] hierarchy level. You can also configure IBGP and multihop support for a routing instance or a logical system. Options authentication algorithm algorithm-name —Configure the algorithm used to authenticate the specified BFD session: simple-password, keyed-md5, keyed-sha-1, meticulous-keyed-md5, meticulous-keyed-sha-1. 1493 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication key-chain key-chain-name—Associate a security key with the specified BFD session using the name of the security keychain. The keychain name must match one of the keychains configured in the authentication-key-chains key-chain statement at the [edit security] hierarchy level. authentication loose-check—(Optional) Configure loose authentication checking on the BFD session. Use only for transitional periods when authentication may not be configured at both ends of the BFD session. detection-time threshold milliseconds—Configure a threshold. When the BFD session detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent. holddown-interval milliseconds—Configure an interval specifying how long a BFD session must remain up before a state change notification is sent. Range: 0 through 255,000 Default: 0 NOTE: You can configure the holddown-interval option only for EBGP peers. minimum-interval milliseconds—Configure the minimum intervals at which the local routing device transmits hello packets and then expects to receive a reply from a neighbor with which it has established a BFD session. Range: 1 through 255,000 minimum-receive-interval milliseconds— Configure only the minimum interval at which the local routing device expects to receive a reply from a neighbor with which it has established a BFD session. Range: 1 through 255,000 multiplier number—Configure the number of hello packets not received by a neighbor that causes the originating interface to be declared down. Range: 1 through 255 Default: 3 no-adaptation—Configure BFD sessions not to adapt to changing network conditions. We recommend that you not disable BFD adaptation unless it is preferable to not to have BFD adaptation enabled in your network. transmit-interval threshold milliseconds—Configure a threshold. When the BFD session transmit interval adapts to a value greater than the threshold, a single trap and a single system message are sent. The interval threshold must be greater than the minimum transmit interval. 32 Range: 0 through 4,294,967,295 (2 1494 – 1) Chapter 73: Configuration Statements for Layer 3 Protocols transmit-interval minimum-interval milliseconds—Configure only the minimum interval at which the local routing device transmits hello packets to a neighbor with which it has established a BFD session. Range: 1 through 255,000 version—Configure the BFD version to detect. Range: 1 or automatic (autodetect the BFD version) Default: automatic The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BFD for BGP • Configuring BFD Authentication for BGP 1495 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bfd-liveness-detection Syntax Hierarchy Level Release Information Description Options bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; no-adaptation; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; version (1 | automatic); } [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure bidirectional failure detection timers and authentication. authentication algorithm algorithm-name —Configure the algorithm used to authenticate the specified BFD session: simple-password, keyed-md5, keyed-sha-1, meticulous-keyed-md5, meticulous-keyed-sha-1. authentication key-chain key-chain-name—Associate a security key with the specified BFD session using the name of the security keychain. The name you specify must match one of the keychains configured in the authentication-key-chains key-chain statement at the [edit security] hierarchy level. authentication loose-check—(Optional) Configure loose authentication checking on the BFD session. Use only for transitional periods when authentication may not be configured at both ends of the BFD session. detection-time threshold milliseconds—Configure a threshold. When the BFD session detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent. minimum-interval milliseconds—Configure the minimum intervals at which the local routing device transmits a hello packet and then expects to receive a reply from the neighbor with which it has established a BFD session. 1496 Chapter 73: Configuration Statements for Layer 3 Protocols Range: 1 through 255,000 minimum-receive-interval milliseconds—Configure only the minimum interval at which the local routing device expects to receive a reply from a neighbor with which it has established a BFD session. Range: 1 through 255,000 multiplier number—Configure the number of hello packets not received by a neighbor that causes the originating interface to be declared down. Range: 1 through 255 Default: 3 no-adaptation—Specify that BFD sessions not adapt to changing network conditions. We recommend that you not disable BFD adaptation unless it is preferable not to have BFD adaptation enabled in your network. transmit-interval threshold milliseconds—Configure a threshold. When the BFD session transmit interval adapts to a value greater than the threshold, a single trap and a single system log message are sent. The interval threshold must be greater than the minimum transmit interval. 32 Range: 0 through 4,294,967,295 (2 – 1) transmit-interval minimum-interval milliseconds—Configure only the minimum interval at which the routing device sends hello packets to a neighbor with which it has established a BFD session. Range: 1 through 255,000 version—Specify the BFD version to detect. Range: 1 (BFD version 1), or automatic (autodetection) Default: automatic The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BFD for IS-IS • Configuring BFD Authentication for IS-IS 1497 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bfd-liveness-detection Syntax Hierarchy Level Release Information Description Options bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } full-neighbors-only minimum-interval milliseconds; minimum-receive-interval milliseconds; no-adaptation; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; version (1 | automatic); } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure bidirectional failure detection timers and authentication. authentication algorithm algorithm-name —Configure the algorithm used to authenticate the specified BFD session: simple-password, keyed-md5, keyed-sha-1, meticulous-keyed-md5, or meticulous-keyed-sha-1. authentication key-chain key-chain-name—Associate a security key with the specified BFD session using the name of the security keychain. The name you specify must match one of the keychains configured in the authentication-key-chains key-chain statement at the [edit security] hierarchy level. 1498 Chapter 73: Configuration Statements for Layer 3 Protocols authentication loose-check—(Optional) Configure loose authentication checking on the BFD session. Use only for transitional periods when authentication may not be configured at both ends of the BFD session. detection-time threshold milliseconds—Configure a threshold. When the BFD session detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent. full-neighbors-only—Establish BFD sessions only for OSPF neighbors in the full state. The default behavior is to establish BFD sessions for all OSPF neighbors. minimum-interval milliseconds—Configure the minimum intervals at which the local routing device transmits a hello packet and then expects to receive a reply from the neighbor with which it has established a BFD session. Range: 1 through 255,000 milliseconds minimum-receive-interval milliseconds—Configure only the minimum interval at which the routing device expects to receive a reply from a neighbor with which it has established a BFD session. Range: 1 through 255,000 milliseconds multiplier number—Configure the number of hello packets not received by a neighbor that causes the originating interface to be declared down. Range: 1 through 255 Default: 3 no-adaptation—Specify that BFD sessions should not adapt to changing network conditions. We recommend that you not disable BFD adaptation unless it is preferable not to have BFD adaptation enabled in your network. transmit-interval threshold milliseconds—Configure a threshold. When the BFD session transmit interval adapts to a value greater than the threshold, a single trap and a single system log message are sent. The interval threshold must be greater than the minimum transmit interval. 32 Range: 0 through 4,294,967,295 (2 – 1) transmit-interval minimum-interval milliseconds—Configure the minimum interval at which the routing device transmits hello packets to a neighbor with which it has established a BFD session. Range: 1 through 255,000 version—Specify the BFD version to detect. Range: 1 (BFD version 1) or automatic (autodetect version) Default: automatic The remaining statements are explained separately. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 1499 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation 1500 • Configuring BFD for OSPF • Configuring BFD Authentication for OSPF Chapter 73: Configuration Statements for Layer 3 Protocols bfd-liveness-detection Syntax Hierarchy Level Release Information Description Options bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; ; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; no-adaptation; version (1 | automatic); } [edit logical-systems logical-system-name protocols rip group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] [edit protocols rip group group-name], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure bidirectional failure detection timers and authentication. authentication algorithm algorithm-name —Configure the algorithm used to authenticate the specified BFD session: simple-password, keyed-md5, keyed-sha-1, meticulous-keyed-md5, or meticulous-keyed-sha-1. authentication key-chain key-chain-name—Associate a security key with the specified BFD session using the name of the security keychain. The name you specify must match one of the keychains configured in the authentication-key-chains key-chain statement at the [edit security] hierarchy level. authentication loose-check—(Optional) Configure loose authentication checking on the BFD session. Use only for transitional periods when authentication may not be configured at both ends of the BFD session. detection-time threshold milliseconds—Configure a threshold. When the BFD session detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent. 1501 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS minimum-interval milliseconds—Configure the minimum intervals at which the local routing device transmits a hello packet and then expects to receive a reply from the neighbor with which it has established a BFD session. Range: 1 through 255,000 milliseconds minimum-receive-interval milliseconds—Configure only the minimum interval at which the local routing device expects to receive a reply from a neighbor with which it has established a BFD session. Range: 1 through 255,000 milliseconds multiplier number—Configure the number of hello packets not received by a neighbor that causes the originating interface to be declared down. Range: 1 through 255 Default: 3 no-adaptation—Configure BFD sessions not to adapt to changing network conditions. We recommend that you not disable BFD adaptation unless it is preferable not to have BFD adaptation enabled in your network. transmit-interval threshold milliseconds—Configure a threshold. When the BFD session transmit interval adapts to a value greater than the threshold, a single trap and a single system log message are sent. The interval threshold must be greater than the minimum transmit interval. 32 Range: 0 through 4,294,967,295 (2 – 1) transmit-interval minimum-interval milliseconds—Configure only a minimum interval at which the local routing device transmits hello packets to a neighbor. Range: 1 through 255,000 version—Specify the BFD version to detect. Range: (BFD version 1), or automatic (autodetect the version) Default: automatic The remaining statements are explained separately. Required Privilege Level Related Documentation 1502 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BFD for RIP • Configuring BFD Authentication for RIP Chapter 73: Configuration Statements for Layer 3 Protocols bfd-liveness-detection Syntax Hierarchy Level bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } holddown-interval milliseconds; local-address ip-address; minimum-interval milliseconds; minimum-receive-interval milliseconds; minimum-receive-ttl number; multiplier number; neighbor address; no-adaptation; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } version (1 | automatic); } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static route destination-prefix], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static route destination-prefix qualified-next-hop (interface-name | address)], [edit logical-systems logical-system-name routing-options rib routing-table-name static route destination-prefix], [edit logical-systems logical-system-name routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit logical-systems logical-system-name routing-options static route destination-prefix], [edit logical-systems logical-system-name routing-options static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix], [edit routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-instances routing-instance-name routing-options static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-instances routing-instance-name routing-options static route destination-prefix], [edit routing-options rib routing-table-name static route destination-prefix], [edit routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-options static route destination-prefix], 1503 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit routing-options static route destination-prefix qualified-next-hop (interface-name | address)] Release Information Description 1504 Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure bidirectional failure detection timers and authentication criteria for static routes. Chapter 73: Configuration Statements for Layer 3 Protocols Options authentication algorithm algorithm-name —Configure the algorithm used to authenticate the specified BFD session: simple-password, keyed-md5, keyed-sha-1, meticulous-keyed-md5, or meticulous-keyed-sha-1. authentication key-chain key-chain-name—Associate a security key with the specified BFD session using the name of the security keychain. The name you specify must match one of the keychains configured in the authentication-key-chains key-chain statement at the [edit security] hierarchy level. authentication loose-check—(Optional) Configure loose authentication checking on the BFD session. Use only for transitional periods when authentication may not be configured at both ends of the BFD session. detection-time threshold milliseconds—Configure a threshold. When the Bidirectional Forwarding Detection (BFD) protocol session detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent. holddown-interval milliseconds—Configure an interval specifying how long a BFD session must remain up before a state change notification is sent. Range: 0 through 255,000 Default: 0 local-address ip-address—Enable a multihop BFD session and configure the source address for the BFD session. minimum-interval milliseconds—Configure the minimum intervals at which the local routing device transmits a hello packet and then expects to receive a reply from the neighbor with which it has established a BFD session. Range: 1 through 255,000 minimum-receive-interval milliseconds—Configure the minimum interval at which the local routing device expects to receive a reply from a neighbor with which it has established a BFD session. Range: 1 through 255,000 minimum-receive-ttl number—Configure the time-to-live (TTL) for the multihop BFD session. Range: 1 through 255 Default: 255 multiplier number—Configure number of hello packets not received by the neighbor that causes the originating interface to be declared down. Range: 1 through 255 Default: 3 neighbor address—Configure a next-hop address for the BFD session for a next hop specified as an interface name. 1505 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-adaptation—Specify for BFD sessions not to adapt to changing network conditions. We recommend that you not disable BFD adaptation unless it is preferable not to have BFD adaptation enabled in your network. transmit-interval threshold milliseconds—Configure a threshold. When the BFD session transmit interval adapts to a value greater than the threshold, a single trap and a single system log message are sent. The interval threshold must be greater than the minimum transmit interval. Range: 0 through 4,294,967,295 transmit-interval minimum-interval milliseconds—Configure the minimum interval at which the local routing device transmits hello packets to a neighbor with which it has established a BFD session. Range: 1 through 255,000 version—Configure the BFD protocol version to detect. Range: 1 or automatic Default: automatic (autodetect the BFD protocol version) The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Bidirectional Forwarding Detection • Configuring BFD Authentication for Static Routes bgp Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 1506 bgp { ... } [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable BGP on the routing device or for a routing instance. BGP is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling BGP Chapter 73: Configuration Statements for Layer 3 Protocols bgp-orf-cisco-mode Syntax Hierarchy Level Release Information Description bgp-orf-cisco-mode; [edit logical-systems logical-system-name protocols bgp outbound-route-filter], [edit logical-systems logical-system-name protocols bgp group group-name outbound-route-filter], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address outbound-route-filter], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp outbound-route-filter], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name outbound-route-filter, [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address outbound-route-filter], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options outbound-route-filter], [edit logical-systems logical-system-name routing-options outbound-route-filter], [edit protocols bgp outbound-route-filter], [edit protocols bgp group group-name outbound-route-filter], [edit protocols bgp group group-name neighbor address outbound-route-filter], [edit routing-instances routing-instance-name protocols bgp outbound-route-filter], [edit routing-instances routing-instance-name protocols bgp group group-name outbound-route-filter], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address outbound-route-filter], [edit routing-instances routing-instance-name routing-options outbound-route-filter], [edit routing-options outbound-route-filter] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable interoperability with routing devices that use the vendor-specific outbound route filter compatibility code of 130 and code type of 128. NOTE: To enable interoperability for all BGP peers configured on the routing device, include the statement at the [edit routing-options outbound-route-filter] hierarchy level. Default Required Privilege Level Related Documentation Disabled routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Filters Provided by BGP Peers to Outbound Routes 1507 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bmp Syntax Hierarchy Level Release Information bmp { memory limit bytes; station-address (ip-address | name); station-port port-number; statistics-timeout seconds; } [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the BGP Monitoring Protocol (BMP), which enables the routing device to collect data from the BGP Adjacency-RIB-In routing tables and periodically send that data to a monitoring station. Options memory-limit bytes—(Optional) Specify a threshold at which to stop collecting BMP data if the limit is exceeded. Default: 10 MB Range: 1,048,576 through 52,428,800 station-address (ip-address | name)—Specify the IP address or a valid URL for the monitoring where BMP data should be sent. station-port port-number—Specify the port number of the monitoring station to use when sending BMP data. statistics-timeout seconds—(Optional) Specify how often to send BMP data to the monitoring station. Required Privilege Level Related Documentation 1508 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the BGP Monitoring Protocol Chapter 73: Configuration Statements for Layer 3 Protocols brief Syntax Hierarchy Level Release Information Description (brief | full); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit routing-instances routing-instance-name routing-options (aggregate | generate) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit routing-options (aggregate | generate) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure all AS numbers from all contributing paths to be included in the aggregate or generated route’s path. • brief—Include only the longest common leading sequences from the contributing AS paths. If this results in AS numbers being omitted from the aggregate route, the BGP ATOMIC_ATTRIBUTE path attribute is included with the aggregate route. • full—Include all AS numbers from all contributing paths in the aggregate or generated route’s path. Default Required Privilege Level Related Documentation full routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • Configuring Aggregate Routes • Configuring Generated Routes 1509 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS centralized Syntax Hierarchy Level Release Information Description centralized; [edit protocols lacp ppm] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Disable distributed periodic packet management (PPM) processing for Link Aggregation Control Protocol (LACP) packets and run all PPM processing for LACP packets on the Routing Engine. This statement disables distributed PPM processing for only LACP packets. You can disable distributed PPM processing for all packets that use PPM and run all PPM processing on the Routing Engine by configuring the no-delegate-processing statement in the [edit routing-options ppm] hierarchy. BEST PRACTICE: We recommend that, generally, you disable distributed PPM only if Dell Support advises you to do so (see “Requesting Technical Support” on page lxxi). You should disable distributed PPM only if you have a compelling reason to disable it. Default Required Privilege Level Related Documentation 1510 Distributed PPM processing is enabled for all packets that use PPM. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Distributed Periodic Packet Management on a J-EX Series Switch (CLI Procedure) on page 1451 • Configuring Aggregated Ethernet LACP (CLI Procedure) on page 926 Chapter 73: Configuration Statements for Layer 3 Protocols check-zero Syntax Hierarchy Level Release Information Description (check-zero | no-check-zero); [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Check whether the reserved fields in a RIP packet are zero: • check-zero—Discard version 1 packets that have nonzero values in the reserved fields and version 2 packets that have nonzero values in the fields that must be zero. This default behavior implements the RIP version 1 and version 2 specifications. • no-check-zero—Receive RIP version 1 packets with nonzero values in the reserved fields or RIP version 2 packets with nonzero values in the fields that must be zero. This is in spite of the fact that they are being sent in violation of the specifications in RFC 1058 and RFC 2453. Default Required Privilege Level Related Documentation check-zero routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Accepting RIP Packets with Nonzero Values in Reserved Fields 1511 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS checksum Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1512 checksum; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable checksum for packets on this interface. The checksum cannot be enabled with MD5 hello authentication on the same interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Packet Checksum on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols cluster Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation cluster cluster-identifier; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the cluster identifier to be used by the route reflector cluster in an internal BGP group. cluster-identifier—IPv6 or IPv4 address to use as the cluster identifier. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • no-client-reflect on page 1632 • Configuring BGP Route Reflection 1513 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS community Syntax Hierarchy Level Release Information Description Options community ([ community-ids ] | no-advertise | no-export | no-export-subconfed | none); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)] [edit routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate BGP community information with a static, aggregate, or generated route. community-ids—One or more community identifiers. The community-ids format varies according to the type of attribute that you use. The BGP community attribute format is as-number:community-value: • as-number—AS number of the community member. It can be a value from 1 through 65,535. • community-value—Identifier of the community member. It can be a number from 0 through 65,535. For more information about BGP community attributes, see the “Configuring the Extended Communities Attribute” section in the Junos OS Policy Framework Configuration Guide. For specifying the BGP community attribute only, you also can specify community-ids as one of the following well-known community names defined in RFC 1997: • no-advertise—Routes containing this community name are not advertised to other BGP peers. • no-export—Routes containing this community name are not advertised outside a BGP confederation boundary. • no-export-subconfed—Routes containing this community name are not advertised to external BGP peers, including peers in other members’ ASs inside a BGP confederation. • none—Explicitly exclude BGP community information with a static route. Include this option when configuring an individual route in the route portion to override a community option specified in the defaults portion. 1514 Chapter 73: Configuration Statements for Layer 3 Protocols NOTE: Extended community attributes are not supported at the [edit routing-options] hierarchy level. You must configure extended communities at the [edit policy-options] hierarchy level. For information about configuring extended communities, see the Junos OS Policy Framework Configuration Guide. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • static on page 1708 • Configuring Static Routes • Configuring Aggregate Routes • Configuring Generated Routes confederation Syntax Hierarchy Level Release Information Description Options confederation confederation-autonomous-system members [ autonomous-systems ]; [edit logical-systems logical-system-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the routing device’s confederation AS number. autonomous-system—AS numbers of the confederation members. Range: 1 through 65,535 confederation-autonomous-system—Confederation AS number. Use one of the numbers assigned to you by the NIC. Range: 1 through 65,535 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring AS Confederation Members 1515 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS csnp-interval Syntax Hierarchy Level Release Information Description Options csnp-interval (seconds | disable); [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the interval between complete sequence number (CSN) packets on a LAN interface. disable—Do not send CSN packets on this interface. seconds—Number of seconds between the sending of CSN packets. Range: 1 through 65,535 seconds Default: 10 seconds Required Privilege Level Related Documentation 1516 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Transmission Frequency for CSNP Packets on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols damping Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation damping; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable route flap damping. Flap damping is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Flap Damping for BGP Routes • Junos OS Policy Framework Configuration Guide 1517 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dead-interval Syntax Hierarchy Level Release Information Description Options dead-interval seconds; [edit logical-systems logical-system-name protocols ospf area area-id peer-interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols ospf area area-id peer-interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id virtual-link], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id virtual-link], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long OSPF waits before declaring that a neighboring routing device is unavailable. This is an interval during which the routing device receives no hello packets from the neighbor. seconds—Interval to wait. Range: 1 through 65,535 seconds Default: 40 seconds (four times the hello interval) Required Privilege Level Related Documentation 1518 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • hello-interval on page 1559 • Configuring OSPF Timers Chapter 73: Configuration Statements for Layer 3 Protocols default-lsa Syntax Hierarchy Level Release Information Description default-lsa { default-metric metric; metric-type type; type-7; } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa], [edit protocols (ospf | ospf3) area area-id nssa], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On area border routers only, for an NSSA, inject a default LSA with a specified metric value into the area. The default route matches any destination that is not explicitly reachable from within the area. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • nssa on page 1642 • stub on page 1710 • Configuring OSPF Areas 1519 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS default-metric Syntax Hierarchy Level Release Information Description Options default-metric metric; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id stub], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id stub], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id stub], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id stub], [edit protocols (ospf | ospf3) area area-id nssa default-lsa], [edit protocols (ospf | ospf3) area area-id stub], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id stub], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id stub], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id stub] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. On area border routers only, for a stub area, inject a default route with a specified metric value into the area. The default route matches any destination that is not explicitly reachable from within the area. metric—Metric value. Range: 1 through 16,777,215 Required Privilege Level Related Documentation 1520 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • nssa on page 1642 • stub on page 1710 • Configuring OSPF Areas Chapter 73: Configuration Statements for Layer 3 Protocols description Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation description text-description; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Text description of the global, group, or neighbor configuration. text-description—Text description of the configuration. It is limited to 126 characters. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling BGP • Configuring BGP Groups and Peers • Configuring BGP Groups and Peers 1521 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1522 disable; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit protocols bgp], [edit routing-instances routing-instance-name protocols bgp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable BGP on the system. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling BGP Chapter 73: Configuration Statements for Layer 3 Protocols disable (IS-IS) Syntax Hierarchy Level Release Information Description disable; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name protocols isis interface interface-namelevel level-number], [edit logical-systems logical-system-name protocols isis traffic-engineering], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis traffic-engineering], [edit protocols isis], [edit protocols isis interface interface-name], [edit protocols isis interface interface-name level level-number], [edit protocols isis traffic-engineering], [edit routing-instances routing-instance-name protocols isis], [edit routing-instances routing-instance-name protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis traffic-engineering] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable IS-IS on the routing device, on an interface, or on a level. At the [edit protocols isis traffic-engineering] hierarchy level, disable IS-IS support for traffic engineering. Enabling IS-IS on an interface (by including the interface statement at the [edit protocols isis] or the [edit routing-instances routing-instance-name protocols isis] hierarchy level), disabling it (by including the disable statement), and not actually having IS-IS run on an interface (by including the passive statement) are mutually exclusive states. Default IS-IS is enabled for Level 1 and Level 2 routers on all interfaces on which an International Organization for Standardization (ISO) protocol family is enabled. IS-IS support for traffic engineering is enabled. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • IS-IS Overview • Configuring IS-IS Traffic Engineering Attributes • Disabling IS-IS 1523 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable (OSPF) Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 1524 disable; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) virtual-link], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) virtual-link], [edit logical-systems logical-system-name routing-instances routing-instances protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3)], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols (ospf | ospf3) virtual-link], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) virtual-link], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable OSPF, an OSPF interface, or an OSPF virtual link. The configured object is enabled (operational) unless explicitly disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum OSPF Configuration Chapter 73: Configuration Statements for Layer 3 Protocols disable Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation disable; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options graceful-restart], [edit logical-systems logical-system-name routing-options graceful-restart], [edit routing-instances routing-instance-name routing-options graceful-restart], [edit routing-options graceful-restart] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable graceful restart. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart 1525 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS discard Syntax Hierarchy Level Release Information [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit routing-instances routing-instance-name routing-options (aggregate | generate) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit routing-options (aggregate | generate) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Do not forward packets addressed to this destination. Instead, drop the packets, do not send ICMP unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table. Default When an aggregate route becomes active, it is installed in the routing table with a reject next hop, which means that ICMP unreachable messages are sent. Required Privilege Level Related Documentation 1526 discard; routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • Configuring Aggregate Routes • Configuring Generated Routes Chapter 73: Configuration Statements for Layer 3 Protocols domain-id Syntax Hierarchy Level Release Information Description Options domain-id domain-id; [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a domain ID for a route. The domain ID identifies the OSPF domain from which the route originated. domain-id—You can specify either an IP address or an IP address and a local identifier using the following format: ip-address:local-identifier. If you do not specify a local identifier with the IP address, the identifier is assumed to have a value of 0. Default: If the router ID is not configured in the routing instance, the router ID is derived from an interface address belonging to the routing instance. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Domain IDs for VPNs domain-vpn-tag Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation domain-vpn-tag number; [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set a virtual private network (VPN) tag for OSPFv2 external routes generated by the provider edge (PE) router. number—VPN tag. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Domain IDs for VPNs 1527 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS explicit-null Syntax Hierarchy Level Release Information Description 1528 explicit-null; [edit logical-systems logical-system-name protocols mpls], [edit logical-systems logical-system-name protocols bgp family inet labeled-unicast], [edit logical-systems logical-system-name protocols bgp family inet6 labeled-unicast], [edit logical-systems logical-system-name protocols bgp group group-name family inet labeled-unicast], [edit logical-systems logical-system-name protocols bgp group group-name family inet6 labeled-unicast], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address family inet labeled-unicast], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address family inet6 labeled-unicast], [edit logical-systems logical-system-name protocols ldp], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp family inet labeled-unicast], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp family inet6 labeled-unicast], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name family inet labeled-unicast], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name family inet6 labeled-unicast], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name neighbor address family inet labeled-unicast], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name neighbor address family inet6 labeled-unicast], [edit logical-systems logical-system-name routing-instances instance-name protocols ldp], [edit protocols mpls], [edit protocols bgp family inet labeled-unicast], [edit protocols bgp family inet6 labeled-unicast], [edit protocols bgp group group-name family inet labeled-unicast], [edit protocols bgp group group-name family inet6 labeled-unicast], [edit protocols bgp group group-name neighbor address family inet labeled-unicast] [edit protocols bgp group group-name neighbor address family inet6 labeled-unicast], [edit protocols ldp], [edit routing-instances instance-name protocols bgp family inet labeled-unicast], [edit routing-instances instance-name protocols bgp family inet6 labeled-unicast], [edit routing-instances instance-name protocols bgp group group-name family inet labeled-unicast], [edit routing-instances instance-name protocols bgp group group-name family inet6 labeled-unicast], [edit routing-instances instance-name protocols bgp group group-name neighbor address family inet labeled-unicast], [edit routing-instances instance-name protocols bgp group group-name neighbor address family inet6 labeled-unicast], [edit routing-instances instance-name protocols ldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Advertise label 0 to the egress routing device of an LSP. Chapter 73: Configuration Statements for Layer 3 Protocols Default Required Privilege Level Related Documentation If you do not include the explicit-null statement in the configuration, label 3 (implicit null) is advertised. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Advertising Explicit Null Labels to BGP Peers export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation export [ policy-names ]; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being exported from the routing table into BGP. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • import on page 1567 • Applying Policies to BGP Routes • Junos OS Policy Framework Configuration Guide 1529 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1530 export [ policy-names ]; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being exported from the routing table into IS-IS. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to Routes Exported to IS-IS • Junos OS Policy Framework Configuration Guide • Junos OS Interfaces and Routing Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation export [ policy--names ]; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being exported from the routing table into OSPF. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to OSPF Routes • Junos OS Policy Framework Configuration Guide 1531 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation export [ policy-names ]; [edit logical-systems logical-system-name protocols rip group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name], [edit protocols rip group group-name], [edit routing-instances routing-instance-name protocols rip group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a policy to routes being exported to the neighbors. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • import on page 1569 • Configuring Group-Specific RIP Properties • Junos OS Policy Framework Configuration Guide export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1532 export [ policy-names ]; [edit logical-systems logical-system-name protocols ripng group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name], [edit protocols ripng group group-name], [edit routing-instances routing-instance-name protocols ripng group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a policy or list of policies to routes being exported to the neighbors. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • import on page 1570 • Configuring Group-Specific RIPng Properties Chapter 73: Configuration Statements for Layer 3 Protocols export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation export [ policy--names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options forwarding-table], [edit logical-systems logical-system-name routing-options forwarding-table], [edit routing-instances routing-instance-name routing-options forwarding-table], [edit routing-options forwarding-table] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being exported from the routing table into the forwarding table. policy-name—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Per-Packet Load Balancing • Junos OS Policy Framework Configuration Guide export-rib Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation export-rib routing-table-name; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib-group group-name], [edit logical-systems logical-system-name routing-options passive group-name], [edit routing-instances routing-instance-name routing-options rib-group group-name], [edit routing-options passive group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Name of the routing table from which the Junos OS should export routing information. routing-table-name—Routing table group name. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • import-rib on page 1572 • passive • Creating Routing Table Groups 1533 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS external-preference Syntax Hierarchy Level Release Information Description Options external-preference preference; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the preference of external routes. preference—Preference value. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 15 (for Level 1 internal routes), 18 (for Level 2 internal routes), 160 (for Level 1 external routes), 165 (for Level 2 external routes) Required Privilege Level Related Documentation 1534 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • preference on page 1661 • Configuring Preference Values for IS-IS Routes Chapter 73: Configuration Statements for Layer 3 Protocols external-preference Syntax Hierarchy Level Release Information Description Options external-preference preference; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ip4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast } ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the route preference for OSPF external routes. preference—Preference value. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 150 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • preference on page 1662 • Configuring Preference Values for OSPF Routes 1535 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS family Syntax 1536 family { (inet | inet6 | inet-vpn | inet6-vpn | iso-vpn) { (any | flow | labeled-unicast | multicast | unicast) { accepted-prefix-limit { maximum number; teardown ; } ; prefix-limit { maximum number; teardown ; } rib-group group-name; } flow { no-validate policy-name; } labeled-unicast { accepted-prefix-limit { maximum number; teardown ; } aggregate-label { community community-name: } explicit-null { connected-only; } prefix-limit { maximum number; teardown ; } resolve-vpn; rib inet.3; rib-group group-name; } } route-target { accepted-prefix-limit { maximum number; teardown ; } advertise-default; external-paths number; prefix-limit { maximum number; teardown ; } } (inet-mdt | inet-mvpn | inet6-mvpn | l2-vpn) { signaling { accepted-prefix-limit { Chapter 73: Configuration Statements for Layer 3 Protocols maximum number; teardown ; } ; prefix-limit { maximum number; teardown ; } rib-group group-name } } } Hierarchy Level Release Information Description [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable multiprotocol BGP (MP-BGP) by configuring BGP to carry network layer reachability information (NLRI) for address families other than unicast IPv4, to specify MP-BGP to carry NLRI for the IPv6 address family, or to carry NLRI for VPNs. 1537 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Options any—Configure the family type to be both unicast and multicast. inet—Configure NLRI parameters for IPv4. inet6—Configure NLRI parameters for IPv6. inet-mdt—Configure NLRI parameters for the multicast distribution tree (MDT) subaddress family identifier (SAFI) for IPv4 traffic in Layer 3 VPNs. inet-mvpn—Configure NLRI parameters for IPv4 for multicast VPNs. inet6-mvpn—Configure NLRI parameters for IPv6 for multicast VPNs. inet-vpn—Configure NLRI parameters for IPv4 for Layer 3 VPNs. inet6-vpn—Configure NLRI parameters for IPv6 for Layer 3 VPNs. iso-vpn—Configure NLRI parameters for IS-IS for Layer 3 VPNs. l2-vpn—Configure NLRI parameters for IPv4 for MPLS-based Layer 2 VPNs and VPLS. labeled-unicast—Configure the family type to be labeled-unicast. This means that the BGP peers are being used only to carry the unicast routes that are being used by labeled-unicast for resolving the labeled-unicast routes. This statement is supported only with inet and inet6. loops number—(Optional) Specify the maximum number of times that the AS number can appear in the AS path received from a BGP peer for the specified address family. For number, include a value from 1 through 10. NOTE: When you configure the loops statement for a specific BGP address family, that value is used to evaluate the AS path for routes received by a BGP peer for the specified address family rather than the loops value configured for the global AS number. multicast—Configure the family type to be multicast. This means that the BGP peers are being used only to carry the unicast routes that are being used by multicast for resolving the multicast routes. unicast—Configure the family type to be unicast. This means that the BGP peers only carry the unicast routes that are being used for unicast forwarding purposes. Default: unicast The remaining statements are explained separately. Required Privilege Level 1538 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 73: Configuration Statements for Layer 3 Protocols Related Documentation • autonomous-system on page 1487 • local-as on page 1597 • Enabling Multiprotocol BGP fate-sharing Syntax Hierarchy Level Release Information Description Options fate-sharing { group group-name { cost value; from address ; } } [edit logical-systems logical-system-name routing-options], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit routing-options], [edit routing-instances routing-instance-name routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify groups of objects that share characteristics resulting in backup paths to be used if primary paths fail. All objects are treated as /32 host addresses. You specify one or more objects within a group. The objects can be LAN interfaces, router IDs, or point-to-point links. The sequence is insignificant. cost value—Cost assigned to the group. Range: 1 through 65,535 Default: 1 from address—Address of the router or address of the LAN/NBMA interface. For example, an Ethernet network with four hosts in the same fate-sharing group would require you to list all four of the separate from addresses in the group. group group-name—Each fate-sharing group must have a name, which can have a maximum of 32 characters, including letters, numbers, periods (.), and hyphens (-). You can define up to 512 groups. to address—(Optional) Address of egress router. For point-to-point link objects, you must specify both a from and a to address. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Ingress Router for MPLS-Signaled LSPs 1539 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS flow Syntax Hierarchy Level Release Information Description Default Options flow { route name { match { match-conditions; } term-order (legacy | standard); then { actions; } } validation { traceoptions { file filename ; flag flag ; } } } [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a flow route. legacy actions—An action to take if conditions match. match-conditions—Match packets to these conditions. route name—Name of the flow route. standard—Specify to use version 7 or later of the flow-specification algorithm. term-order (legacy | standard)—Specify the version of the flow-specification algorithm. • legacy—Use version 6 of the flow-specification algorithm. • standard—Use version 7 of the flow-specification algorithm. then—Actions to take on matching packets. Required Privilege Level Related Documentation 1540 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Flow Routes Chapter 73: Configuration Statements for Layer 3 Protocols flow-map Syntax Hierarchy Level Release Information Description Options flow-map flow-map-name { bandwidth (bps | adaptive); forwarding-cache { timeout (never | minutes); } policy [ policy-names ]; redundant-sources [ addresses ]; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure multicast flow maps. flow-map-name—Name of the flow-map. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Creating a Multicast Flow Map forwarding-cache (Flow Maps) Syntax Hierarchy Level Release Information Description Required Privilege Level forwarding-cache { timeout (minutes | never ); } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name], [edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit routing-options multicast flow-map flow-map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure multicast forwarding cache properties for the flow map. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 1541 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS forwarding-cache (Multicast) Syntax Hierarchy Level Release Information Description forwarding-cache { threshold suppress value ; timeout minutes; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure multicast forwarding cache properties. These properties include threshold suppression and reuse limits and timeout values. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring General Multicast Forwarding Cache Properties forwarding-table Syntax Hierarchy Level Release Information Description forwarding-table { export [ policy--names ]; (indirect-next-hop | no-indirect-next-hop); unicast-reverse-path (active-paths | feasible-paths); } [edit logical-systems logical-system-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure information about the routing device’s forwarding table. The remaining statements are explained separately. Required Privilege Level Related Documentation 1542 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Per-Packet Load Balancing Chapter 73: Configuration Statements for Layer 3 Protocols generate Syntax Hierarchy Level Release Information Description Options generate { defaults { generate-options; } route destination-prefix { policy policy-name; generate-options; } } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name], [edit routing-options], [edit routing-options rib routing-table-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure generated routes, which are used as routes of last resort. generate-options—Additional information about generated routes, which is included with the route when it is installed in the routing table. Specify zero or more of the following options in generate-options. Each option is explained separately. • (active | passive); • as-path ; • community [ community-ids ]; • discard; • (brief | full); • (metric | metric2 | metric3 | metric4) value ; • (preference | preference2 | color | color2) preference ; • tag string; defaults—Specify global generated route options. These options only set default attributes inherited by all newly created generated routes. These are treated as global defaults and apply to all the generated routes you configure in the generate statement. This part of the generate statement is optional. route destination-prefix—Configure a non-default generated route: • default—For the default route to the destination. This is equivalent to specifying an IP address of 0.0.0.0/0. 1543 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • destination-prefix/prefix-length—/destination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length. The policy statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Generated Routes graceful-restart Syntax Hierarchy Level Release Information Description Options graceful-restart { disable; restart-timeseconds; stale-routes-time seconds; } [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure graceful restart for BGP. disable—Disable graceful restart for BGP. restart-time seconds—Time period when the restart is expected to be complete. Range: 1 through 600 seconds stale-routes-time seconds—Maximum time that stale routes are kept during restart. Range: 1 through 600 seconds Required Privilege Level Related Documentation 1544 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart • Configuring Graceful Restart for BGP • Junos OS High Availability Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols graceful-restart Syntax Hierarchy Level Release Information Description Options graceful-restart { disable; helper-disable; restart-duration seconds; } [edit logical-systems logical-system-name protocols isis], [edit protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure graceful restart for IS-IS. disable—Disable graceful restart. helper-disable—Disable graceful restart helper capability. Helper mode is enabled by default. restart-duration seconds—Configure the time period for the restart to last, in seconds. Range: 30 through 300 seconds Default: 30 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart • Configuring Graceful Restart for IS-IS 1545 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS graceful-restart Syntax Hierarchy Level Release Information Description Options graceful-restart { disable; helper-disable; notify-duration seconds; restart-duration seconds; } [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit protocols (ospf | ospf3)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure graceful restart for OSPF. disable—Disable graceful restart for OSPF. helper-disable—Disable graceful restart helper capability. Helper mode is enabled by default. notify-duration seconds—Estimated time to send out purged grace LSAs over all the interfaces. Range: 1 through 3600 seconds Default: 30 seconds restart-duration seconds—Estimated time to reacquire a full OSPF neighbor from each area. Range: 1 through 3600 seconds Default: 180 seconds Required Privilege Level Related Documentation 1546 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart for OSPF and OSPFv3 • Junos OS High Availability Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols graceful-restart Syntax Hierarchy Level Release Information Description Options graceful-restart { disable; restart-time seconds; } [edit logical-systems logical-system-name protocols rip], [edit protocols rip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure graceful restart for RIP. disable—Disables graceful restart for RIP. seconds—Estimated time for the restart to finish, in seconds. Range: 1 through 600 seconds Default: 60 seconds The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart • Configuring Graceful Restart for RIP 1547 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS graceful-restart Syntax Hierarchy Level Release Information Description Options graceful-restart { disable; restart-time seconds; } [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit protocols ripng], [edit routing-instances routing-instance-name protocols ripng] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure graceful restart for RIPng. disable—Disables graceful restart for RIPng. seconds—Estimated time period for the restart to finish. Range: 1 through 600 seconds Default: 60 seconds Required Privilege Level Related Documentation 1548 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart • Configuring Graceful Restart for RIPng Chapter 73: Configuration Statements for Layer 3 Protocols graceful-restart Syntax Hierarchy Level Release Information Description graceful-restart { disable; restart-duration seconds; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure graceful restart. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart • Junos OS High Availability Configuration Guide 1549 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS group Syntax 1550 group group-name { advertise-inactive; allow [ network/mask-length ]; authentication-key key; cluster cluster-identifier; damping; description text-description; export [ policy-names ]; family { (inet | inet6 | inet-vpn | inet6-vpn | l2-vpn) { (any | multicast | unicast | signaling) { accepted-prefix-limit { maximum number; teardown ; } prefix-limit { maximum number; teardown ; } rib-group group-name; } flow { no-validate policy-name; } labeled-unicast { accepted-prefix-limit { maximum number; teardown ; } explicit-null { connected-only; } prefix-limit { maximum number; teardown ; } resolve-vpn; rib inet.3; rib-group group-name; } } route-target { accepted-prefix-limit { maximum number; teardown ; } advertise-default; external-paths number; prefix-limit { maximum number; teardown ; } Chapter 73: Configuration Statements for Layer 3 Protocols } } hold-time seconds; import [ policy-names ]; ipsec-sa ipsec-sa; keep (all | none); local-address address; local-as autonomous-system ; local-preference local-preference; log-updown; metric-out metric; multihop ; multipath { multiple-as; } no-aggregator-id; no-client-reflect; out-delay seconds; passive; peer-as autonomous-system; preference preference; remove-private; tcp-mss segment-size; traceoptions { file filename ; flag flag ; } type type; neighbor address { ... peer-specific-options ... } } Hierarchy Level Release Information Description [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit protocols bgp], [edit routing-instances routing-instance-name protocols bgp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a BGP peer group. BGP peer groups share a common type, peer autonomous system (AS) number, and cluster ID, if present. To configure multiple BGP groups, include multiple group statements. By default, the group’s options are identical to the global BGP options. To override the global options, include group-specific options within the group statement. The group statement is one of the statements you must include in the configuration to run BGP on the routing device. See Minimum BGP Configuration. Options group-name—Name of the BGP group. The remaining statements are explained separately. 1551 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation 1552 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BGP Groups and Peers Chapter 73: Configuration Statements for Layer 3 Protocols group Syntax group group-name { bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; version (0 | 1 | automatic); } preference number; metric-out metric; export policy; route-timeout seconds; update-interval seconds; neighbor neighbor-name { authentication-key password; authentication-type type; bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; version (0 | 1 | automatic); } (check-zero | no-check-zero); import policy-name; message-size number; metric-in metric; metric-out metric; receive receive-options; route-timeout seconds; 1553 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS send send-options; update-interval seconds; } } Hierarchy Level Release Information Description Options [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit protocols rip], [edit routing-instances routing-instance-name protocols rip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a set of RIP neighbors that share an export policy and metric. The export policy and metric govern what routes to advertise to neighbors in a given group. group-name—Name of a group, up to 16 characters long. The remaining statements are explained separately. Required Privilege Level Related Documentation 1554 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Group-Specific RIP Properties Chapter 73: Configuration Statements for Layer 3 Protocols group Syntax Hierarchy Level Release Information Description Options group group-name { export [ policy-names ]; metric-out metric; preference number; route-timeout seconds; update-interval seconds; neighbor neighbor-name { import policy-name; metric-in metric; receive ; route-timeout seconds; send ; update-interval seconds; } } [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit protocols ripng], [edit routing-instances routing-instance-name protocols ripng] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a set of RIPng neighbors that share an export policy and metric. The export policy and metric govern what routes to advertise to neighbors in a given group. group-name—Name of a group, up to 16 characters long. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Group-Specific RIPng Properties 1555 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS hello-authentication-key Syntax Hierarchy Level Release Information Description Default Options hello-authentication-key password; [edit logical-systems logical-system-name protocols isis interface interface-namelevel number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level number], [edit protocols isis interface interface-name level number], [edit routing-instances routing-instance-name protocols isis interface interface-name level number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an authentication key (password) for hello packets. Neighboring routing devices use the password to verify the authenticity of packets sent from an interface. For the key to work, you also must include the hello-authentication-type statement. By default, hello authentication is not configured on an interface. However, if IS-IS authentication is configured, the hello packets are authenticated using the IS-IS authentication type and password. password—Authentication password. The password can be up to 255 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). Required Privilege Level Related Documentation 1556 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • authentication-key on page 1481 • authentication-type on page 1485 • hello-authentication-type on page 1557 • Configuring Levels on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols hello-authentication-type Syntax Hierarchy Level Release Information Description Default Options hello-authentication-type (md5 | simple); [edit logical-systems logical-system-name protocols isis interface interface-name level number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level number], [edit protocols isis interface interface-name level number], [edit routing-instances routing-instance-name protocols isis interface interface-name level number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable authentication on an interface for hello packets. If you enable authentication on hello packets, you must specify a password by including the hello-authentication-key statement. By default, hello authentication is not configured on an interface. However, if IS-IS authentication is configured, the hello packets are authenticated using the IS-IS authentication type and password. md5—Specifies Message Digest 5 as the packet verification type. simple—Specifies simple authentication as the packet verification type. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • authentication-key on page 1481 • authentication-type on page 1485 • hello-authentication-key on page 1556 • Configuring Levels on IS-IS Interfaces 1557 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS hello-interval Syntax Hierarchy Level Release Information Description Options hello-interval seconds; [edit logical-systems logical-system-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Frequency with which the routing device sends hello packets out of an interface, in seconds. seconds—Frequency of transmission for hello packets. Range: 1 through 20,000 seconds Default: 3 seconds (for designated intersystem [DIS] routers), 9 seconds (for non-DIS routers) Required Privilege Level Related Documentation 1558 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • hold-time • Configuring Levels on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols hello-interval Syntax Hierarchy Level Release Information Description Options hello-interval seconds; [edit logical-systems logical-system-name protocols ospf area area-id peer-interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols ospf area area-id peer-interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id virtual-link], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id virtual-link], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how often the routing device sends hello packets out the interface. The hello interval must be the same for all routing devices on a shared logical IP network. seconds—Time between hello packets, in seconds. Range: 1 through 255 seconds Default: 10 seconds; 120 seconds (nonbroadcast networks) Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • dead-interval on page 1518 • Configuring OSPF Timers 1559 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS hello-padding Syntax Hierarchy Level Release Information Description Options hello-padding (adaptive | loose | strict); [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure padding on hello packets to accommodate asymmetrical maximum transfer units (MTUs) from different hosts. adaptive—Configure padding until state of neighbor adjacency is up. loose—Configure padding until state of adjacency is initialized. strict—Configure padding for all adjacency states. Required Privilege Level Related Documentation 1560 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Padding of IS-IS Hello Packets Chapter 73: Configuration Statements for Layer 3 Protocols holddown Syntax Hierarchy Level Release Information Description Options holddown seconds; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit protocols rip], [edit routing-instances routing-instance-name protocols rip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the time period the expired route is retained in the routing table before being removed. seconds—Estimated time to wait before making updates to the routing table. Range: 10 through 180 seconds Default: 180 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RIP Timers holddown Syntax Hierarchy Level Release Information Description Options holddown seconds; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit protocols ripng], [edit routing-instances routing-instance-name protocols ripng] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the time period the expired route is retained in the routing table before being removed. seconds—Estimated time to wait before making updates to the routing table. Default: 180 seconds Range: 10 through 180 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RIPng Timers 1561 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS hold-time Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1562 hold-time seconds; [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the time in seconds after which a backup router with the highest priority preempts the master router. seconds—Hold-time period. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 Chapter 73: Configuration Statements for Layer 3 Protocols hold-time Syntax Hierarchy Level Release Information Description hold-time seconds; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the hold-time value to use when negotiating a connection with the peer. The hold-time value is advertised in open packets and indicates to the peer the length of time that it should consider the sender valid. If the peer does not receive a keepalive, update, or notification message within the specified hold time, the BGP connection to the peer is closed and routing devices through that peer become unavailable. The hold time is three times the interval at which keepalive messages are sent. Options seconds—Hold time. Range: 20 through 65,535 seconds Default: 90 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Delay Before BGP Peers Mark the Routing Device as Down 1563 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS hold-time (IS-IS) Syntax Hierarchy Level Release Information Description Options hold-time seconds; [edit logical-systems logical-system-name protocols isis interface interface-namelevel level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the length of time a neighbor considers this router to be operative (up) after receiving a hello packet. If the neighbor does not receiver another hello packet within the specified time, it marks this routing device as inoperative (down). The hold time itself is advertised in the hello packets. seconds—Hold-time value, in seconds. Range: 3 through 65,535 seconds, or 1 to send out hello packets every 333 milliseconds Default: 9 seconds (for DIS routers), 27 seconds (for non-DIS routers; three times the default hello interval) Required Privilege Level Related Documentation 1564 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • hello-interval on page 1558 • Configuring Levels on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols idle-after-switch-over Syntax Hierarchy Level Release Information idle-after-switch-over (forever | seconds); [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the routing device not to automatically reestablish BGP peering sessions after a nonstop active routing (NSR) switchover. This feature is particularly useful if you are using dynamic routing policies because the dynamic database is not synchronized with the backup Routing Engine when NSR is enabled. Options forever—Do not reestablish a BGP peering session after an NSR switchover until the clear bgp neighbor command is issued. seconds—Do not reestablish a BGP peering session after an NSR switchover until after the specified period. 32 Range: 1 through 4,294,967,295 (2 Required Privilege Level Related Documentation – 1) routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Preventing Automatic Reestablishment of BGP Peering Sessions After NSR Switchovers • Junos OS Policy Framework Configuration Guide • Junos OS High Availability Configuration Guide 1565 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ignore-attached-bit Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation ignore-attached-bit; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Ignore the attached bit on IS-IS Level 1 routers. Configuring this statement allows the routing device to ignore the attached bit on incoming Level 1 LSPs. If the attached bit is ignored, no default route, which points to the routing device which has set the attached bit, is installed. The ignore-attached-bit statement is disabled by default. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS ignore-lsp-metrics Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1566 ignore-lsp-metrics; [edit logical-systems logical-system-name protocols ospf traffic-engineering shortcuts], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf traffic-engineering shortcuts], [edit protocols ospf traffic-engineering shortcuts], [edit routing-instances routing-instance-name protocols ospf traffic-engineering shortcuts] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Ignore RSVP LSP metrics in OSPF traffic engineering shortcut calculations. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling OSPF Traffic Engineering Support Chapter 73: Configuration Statements for Layer 3 Protocols import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation import [ policy-names ]; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more routing policies to routes being imported into the Junos OS routing table from BGP. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • export on page 1529 • Applying Policies to BGP Routes • Junos OS Policy Framework Configuration Guide 1567 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1568 import [ policy--names ]; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Filter OSPF routes from being added to the routing table. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to OSPF Routes • Junos OS Policy Framework Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation import [ policy-names ]; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being imported by the local router from its neighbors. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • export on page 1532 • Applying Policies to RIP Routes Imported from Neighbors • Junos OS Policy Framework Configuration Guide 1569 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1570 import [ policy-names ]; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name], [edit protocols ripng], [edit protocols ripng group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols ripng], [edit routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being imported into the local routing device from the neighbors. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • export on page 1532 • Applying Policies to RIPng Routes Imported from Neighbors Chapter 73: Configuration Statements for Layer 3 Protocols import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation import [ policy-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options resolution rib], [edit logical-systems logical-system-name routing-options resolution rib], [edit routing-instances routing-instance-name routing-options resolution rib], [edit routing-options resolution rib] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify one or more import policies to use for route resolution. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Resolution import-policy Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation import-policy [ policy-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib-group group-name], [edit logical-systems logical-system-name routing-options passive group-name], [edit routing-instances routing-instance-name routing-options rib-group group-name], [edit routing-options rib-groups group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes imported into the routing table group. The import-policy statement complements the import-rib statement and cannot be used unless you first specify the routing tables to which routes are being imported. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • export-rib on page 1533 • passive • Creating Routing Table Groups 1571 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS import-rib Syntax Hierarchy Level Release Information Description import-rib [ routing-table--names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib-group group-name], [edit logical-systems logical-system-name routing-options rib-group group-name], [edit routing-instances routing-instance-name routing-options rib-group group-name], [edit routing-options rib-group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Name of the routing table into which Junos OS should import routing information. The first routing table name you enter is the primary routing table. Any additional names you enter identify secondary routing tables. When a protocol imports routes, it imports them into the primary and any secondary routing tables. If the primary route is deleted, the secondary route also is deleted. For IPv4 import routing tables, the primary routing table must be inet.0 or routing-instance-name.inet.0. For IPv6 import routing tables, the primary routing table must be inet6.0. You can configure an IPv4 import routing table that includes both IPv4 and IPv6 routing tables. Including both types of routing tables permits you, for example, to populate an IPv6 routing table with IPv6 addresses that are compatible with IPv4. Options Required Privilege Level Related Documentation 1572 routing-table-names—Name of one or more routing tables. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • export-rib on page 1533 • passive • Creating Routing Table Groups Chapter 73: Configuration Statements for Layer 3 Protocols include-mp-next-hop Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation include-mp-next-hop; [edit logical-systems logical-system-name protocols bgp], [edit protocols bgp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable multiprotocol updates to contain next-hop reachability information. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Including Next-Hop Reachability Information in Multiprotocol Updates indirect-next-hop Syntax Hierarchy Level Release Information Description (indirect-next-hop | no-indirect-next-hop); [edit logical-systems logical-system-name routing-options forwarding-table], [edit routing-options forwarding-table] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable indirectly connected next hops for route convergence. NOTE: When virtual private LAN service (VPLS) is configured on the routing device, the indirect-next-hop statement is not supported. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Indirect Next Hops 1573 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS inet6-advertise-interval Syntax Hierarchy Level Release Information Description Options inet6-advertise-interval milliseconds; [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the interval between Virtual Router Redundancy Protocol (VRRP) IPv6 advertisement packets. milliseconds—Interval, in milliseconds, between advertisement packets. Range: 100 to 40,000 ms Default: 1 second Required Privilege Level Related Documentation 1574 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 Chapter 73: Configuration Statements for Layer 3 Protocols install Syntax Hierarchy Level Release Information Description Options (install | no-install); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-options static (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit routing-instances routing-instance-name routing-options static (defaults | route)], [edit routing-options rib routing-table-name static (defaults | route)] [edit routing-options static (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether the Junos OS installs all static routes into the forwarding table. Even if you configure a route so it is not installed in the forwarding table, the route is still eligible to be exported from the routing table to other protocols. install—Explicitly install all static routes into the forwarding table. no-install—Do not install the route into the forwarding table, even if it is the route with the lowest preference. Default: install Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • static on page 1708 • Configuring Static Routes 1575 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS instance-export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation instance-export [ policy--names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being exported from a routing instance. policy-names—Name of one or more export policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Policy-Based Export for Routing Instances • Junos OS Policy Framework Configuration Guide instance-import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1576 instance-import [ policy--names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being imported into a routing instance. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Policy-Based Export for Routing Instances • Junos OS Policy Framework Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols inter-area-prefix-export Syntax Hierarchy Level inter-area-prefix-export [ policy-names ]; [edit logical-systems logical-system-name protocols ospf3 area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ip4-unicast | ipv4-multicast | ipv6-multicast) area area-id [edit protocols ospf3 area area-id], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit routing-instances routing-instance-name protocols ospf3 area area-id], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-muticast | ipv6-multicast) area area-id] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Apply an export policy for OSPFv3 to specify which interarea prefix link-state advertisements (LSAs) are flooded into an area. Options policy-name—Name of a policy configured at the [edit policy-options policy-statement policy-name term term-name] hierarchy level. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • inter-area-prefix-import on page 1578 • Applying Policies to OSPF Routes • Junos OS Policy Framework Configuration Guide 1577 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS inter-area-prefix-import Syntax Hierarchy Level Release Information Description Options inter-area-prefix-import [ policy-names ]; [edit logical-systems logical-system-name protocols ospf3 area area-id], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit protocols ospf3 area area-id], [edit protocols ospf3 realm (ip4-unicast | ipv4-multicast | ipv6-multicast)], area area-id], [edit routing-instances routing-instance-name protocols ospf3 area area-id], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply an import policy for OSPFv3 to specify which routes learned from an area are used to generate interarea prefixes into other areas. policy-name—Name of a policy configured at the [edit policy-options policy-statement policy-name term term-name] hierarchy level. Required Privilege Level Related Documentation 1578 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • inter-area-prefix-export on page 1577 • Applying Policies to OSPF Routes • Junos OS Policy Framework Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols interface Syntax Hierarchy Level interface (all | interface-name) { disable; bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; } checksum; csnp-interval (seconds | disable); hello-padding (adaptive | loose | strict); ldp-synchronization { disable; hold-time seconds; } lsp-interval milliseconds; mesh-group (value | blocked); no-adjacency-holddown; no-ipv4-multicast; no-ipv6-multicast; no-ipv6-unicast; no-unicast-topology; passive; point-to-point; level level-number { disable; hello-authentication-type authentication; hello-authentication-key key; hello-interval seconds; hold-time seconds; ipv4-multicast-metric number; ipv6-multicast-metric number; ipv6-unicast-metric number; metric metric; passive; priority number; te-metric metric; } } [edit logical-systems logical-system-name protocols isis], 1579 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Release Information Description Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure interface-specific IS-IS properties. To configure more than one interface, include the interface statement multiple times. Enabling IS-IS on an interface (by including the interface statement at the [edit protocols isis] or the [edit routing-instances routing-instance-name protocols isis] hierarchy level), disabling it (by including the disable statement), and not actually having IS-IS run on an interface (by including the passive statement) are mutually exclusive states. Options all—Have the Junos OS create IS-IS interfaces automatically. interface-name—Name of an interface. Specify the full interface name, including the physical and logical address components. For details about specifying interfaces, see the Junos OS Network Interfaces Configuration Guide and the Junos OS Services Interfaces Configuration Guide. The remaining statements are explained separately. Required Privilege Level Related Documentation 1580 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring of Interface-Specific IS-IS Properties Chapter 73: Configuration Statements for Layer 3 Protocols interface Syntax Hierarchy Level interface interface-name { disable; authentication key ; bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; } dead-interval seconds; demand-circuit; hello-interval seconds; ipsec-sa name; interface-type type; ldp-synchronization { disable; hold-time seconds; } metric metric; neighbor address ; passive; poll-interval seconds; priority number; retransmit-interval seconds; te-metric metric; topology (ipv4-multicast | name) { metric metric; } transit-delay seconds; transmit-interval seconds; } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], [edit protocols (ospf | ospf3) area area-id], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id], 1581 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id] Release Information Description Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable OSPF routing on a routing device interface. You must include at least one interface statement in the configuration to enable OSPF on the routing device. Options interface-name—Name of the interface. Specify the interface by IP address or interface name for OSPFv2, or only the interface name for OSPFv3. Using both the interface name and IP address of the same interface produces an invalid configuration. To configure all interfaces, you can specify all. Specifying a particular interface and all produces an invalid configuration. For details about specifying interfaces, see interface naming in the Junos OS Network Interfaces Configuration Guide. NOTE: For nonbroadcast interfaces, specify the IP address of the nonbroadcast interface as interface-name. The remaining statements are explained separately. NOTE: You cannot run both OSPF and ethernet-tcc encapsulation between two routing devices. Required Privilege Level Related Documentation 1582 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • neighbor • Minimum OSPF Configuration • Configuring Multitopology Routing in OSPF • Configuring Multiple Address Families for OSPFv3 Chapter 73: Configuration Statements for Layer 3 Protocols interface (Routing Options) Syntax Hierarchy Level Release Information Description Options interface interface-names { maximum-bandwidth bps; no-qos-adjust; reverse-oif-mapping { no-qos-adjust; } subscriber-leave-timer seconds; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the maximum bandwidth for an interface on which you want to apply bandwidth management. interface-name—Names of the physical or logical interface. For details about specifying interfaces, see the Junos OS Network Interfaces Configuration Guide. The remaining statements are explained separately. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 1583 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface (Multicast via Static Routes) Syntax Hierarchy Level Release Information Description interface interface-names { maximum-bandwidth bps; no-qos-adjust; reverse-oif-mapping { no-qos-adjust; } subscriber-leave-timer seconds; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable multicast traffic on an interface. NOTE: You cannot enable multicast traffic on an interface using the enable statement and configure PIM on the same interface simultaneously. Options interface-name—Name of the interface on which to enable multicast traffic. Specify the interface-name to enable multicast traffic on the interface. Required Privilege Level Related Documentation 1584 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Multicast Forwarding Without PIM Chapter 73: Configuration Statements for Layer 3 Protocols interface-routes Syntax Hierarchy Level Release Information Description Options interface-routes { family (inet | inet6) { export { lan; point-to-point; } } rib-group group-name; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate a routing table group with the routing device’s interfaces and specify routing table groups into which interface routes are imported. inet—Specify the IPv4 address family. inet6—Specify the IPv6 address family. lan—Export LAN routes. point-to-point—Export point-to-point routes. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • passive • Configuring How Interface Routes Are Imported into Routing Tables 1585 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface-type Syntax Hierarchy Level Release Information Description interface-type (nbma | p2mp | p2p); [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name] [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the type of interface. By default, the software chooses the correct interface type based on the type of physical interface. Therefore, you should never have to set the interface type. The exception to this is for NBMA interfaces, which default to an interface type of point-to-multipoint. To have these interfaces explicitly run in NBMA mode, configure the nbma interface type, using the IP address of the local ATM interface. A point-to-point interface can be an Ethernet interface without a subnet. For more information about configuring interfaces, see the Junos OS Network Interfaces Configuration Guide. Default Options The software chooses the correct interface type based on the type of physical interface. nbma (OSPFv2 only)—Nonbroadcast multiaccess (NBMA) interface. p2mp (OSPFv2 only)—Point-to-multipoint interface. p2p—Point-to-point interface. Required Privilege Level Related Documentation 1586 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF on Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols ipv4-multicast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation ipv4-multicast; [edit logical-systems logical-system-name protocols isis topologies], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis topologies], [edit protocols isis topologies], [edit routing-instances routing-instance-name protocols isis topologies] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure alternate IPv4 multicast topologies. Multicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies ipv4-multicast-metric Syntax Hierarchy Level Release Information Description Options ipv4-multicast-metric metric; [edit logical-systems logical-system-name protocols isis interface interface-namelevel level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the multicast topology metric value for the level. metric—Metric value. Range: 0 through 16,777,215 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies 1587 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ipv6-multicast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation ipv6-multicast; [edit logical-systems logical-system-name protocols isis topologies], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis topologies], [edit protocols isis topologies], [edit routing-instances routing-instance-name protocols isis topologies] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure alternate IPv6 multicast topologies. Multicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies ipv6-multicast-metric Syntax Hierarchy Level Release Information Description Options ipv6-multicast-metric metric; [edit logical-systems logical-system-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the IPv6 alternate multicast topology metric value for the level. metric—Metric value. Range: 0 through 16,777,215 Required Privilege Level Related Documentation 1588 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies Chapter 73: Configuration Statements for Layer 3 Protocols ipv6-unicast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation ipv6-unicast; [edit logical-systems logical-system-name protocols isis topologies], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis topologies], [edit protocols isis topologies], [edit routing-instances routing-instance-name protocols isis topologies] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure alternate IPv6 unicast topologies. IPv6 unicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS IPv6 Unicast Topologies ipv6-unicast-metric Syntax Hierarchy Level Release Information Description Options ipv6-unicast-metric metric; [edit logical-systems logical-system-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the IPv6 unicast topology metric value for the level. metric—Metric value. Range: 0 through 16,777,215 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS IPv6 Unicast Topologies 1589 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS isis Syntax Hierarchy Level Release Information Description isis { ... } [edit logical-systems logical-system-name protocols], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable IS-IS routing on the routing device or for a routing instance. The isis statement is the one statement you must include in the configuration to run IS-IS on the routing device or in a routing instance. Default Required Privilege Level Related Documentation 1590 IS-IS is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum IS-IS Configuration Chapter 73: Configuration Statements for Layer 3 Protocols keep Syntax Hierarchy Level Release Information Description Default Options keep (all | none); [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify whether routes learned from a BGP peer are retained in the routing table even if they contain an AS number that was exported from the local AS. If you do not include this statement, most routes are retained in the routing table. all—Retain all routes. none—Retain none of the routes. When keep none is configured for the BGP session and the inbound policy changes, the Junos OS forces readvertisement of the full set of routes advertised by the peer. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to BGP Routes 1591 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS labeled-unicast Syntax Hierarchy Level Release Information Description labeled-unicast { accepted-prefix-limit { maximum number; teardown ; } aggregate-label { community community-name; } explicit-null { connected-only; } prefix-limit { maximum number; teardown ; } resolve-vpn; rib inet.3; rib-group group-name; } [edit logical-systems logical-system-name protocols bgp family (inet | inet6)], [edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6)], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet6)], [edit protocols bgp family (inet | inet6)], [edit protocols bgp group group-name family (inet | inet6)], [edit protocols bgp group group-name neighbor address family (inet | inet6)], [edit routing-instances routing-instance-name protocols bgp family (inet | inet6)], [edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet6)], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the family type to be labeled-unicast. The remaining statements are explained separately. Required Privilege Level Related Documentation 1592 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Multiprotocol BGP Chapter 73: Configuration Statements for Layer 3 Protocols level (Global IS-IS) Syntax Hierarchy Level Release Information Description Options level level-number { authentication-key key; authentication-type type; external-preference preference; no-csnp-authentication; no-hello-authentication; no-psnp-authentication; preference preference; wide-metrics-only; } [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the global-level properties. level-number—IS-IS level number. Values: 1 or 2 The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Preference Values for IS-IS Routes 1593 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS link-protection Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1594 link-protection; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable link protection on the specified IS-IS interface. The Junos OS creates a backup loop-free alternate path to the primary next hop for all destination routes that traverse the protected interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • node-link-protection on page 1641 • Configuring Loop-Free Alternate Routes for IS-IS Chapter 73: Configuration Statements for Layer 3 Protocols local-address Syntax Hierarchy Level Release Information local-address address; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Specify the address of the local end of a BGP session. This address is used to accept incoming connections to the peer and to establish connections to the remote peer. When none of the operational interfaces are configured with the specified local address, a session with a BGP peer is placed in the idle state. Default If you do not configure a local address, BGP uses the routing device’s source address selection rules to set the local address. For more information, see the Junos OS Network Interfaces Configuration Guide. Options Required Privilege Level Related Documentation address—IPv6 or IPv4 address of the local end of the connection. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • router-id on page 1697 • Enabling BGP 1595 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS local-address Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1596 local-address address; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast backup-pe-group group-name], [edit logical-systems logical-system-name routing-options multicast backup-pe-group group-name], [edit routing-instances routing-instance-name routing-options multicast backup-pe-group group-name], [edit routing-options multicast backup-pe-group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the address of the local PE for ingress PE redundancy when point-to-multipoint LSPs are used for multicast distribution. address—Address of local PEs in the backup group. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Ingress PE Redundancy Chapter 73: Configuration Statements for Layer 3 Protocols local-as Syntax Hierarchy Level Release Information Description local-as autonomous-system ; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the local AS number. The autonomous system (AS) numeric range in plain-number format provides BGP support for 4-byte AS numbers, as defined in RFC 4893, BGP Support for Four-octet AS Number Space. You can also configure a 4-byte AS number using the AS-dot notation format of two integer values joined by a period: <16-bit high-order value in decimal>.<16-bit low-order value in decimal>. For example, the 4-byte AS number of 65546 in plain-number format is represented as 1.10 in the AS-dot notation format. Options alias—(Optional) Configure the local AS as an alias of the global AS number configured for the router at the [edit routing-options] hierarchy level. As a result, a BGP peer considers any local AS to which it is assigned as equivalent to the primary AS number configured for the routing device. When you use the alias option, only the AS (global or local) used to establish the BGP session is prepended in the AS path sent to the BGP neighbor. autonomous-system—AS number. 32 Range: 1 through 4,294,967,295 (2 – 1) in plain-number format Range: 0.0 through 65535.65535 in AS-dot notation format loops number—(Optional) Specify the maximum number of times that the local AS number can appear in an AS path received from a BGP peer. For number, include a value from 1 through 10. no-prepend-global-as—(Optional) Specify to strip the global AS and to prepend only the local AS in AS paths sent to external peers. 1597 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS private—(Optional) Configure to use the local AS only during the establishment of the BGP session with a BGP neighbor but to hide it in the AS path sent to external BGP peers. Only the global AS is included in the AS path sent to external peers. NOTE: The private and alias options are mutually exclusive. You cannot configure both options with the same local-as statement. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • autonomous-system on page 1487 • family on page 1536 • Configuring a Local AS for EBGP Sessions local-interface Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1598 local-interface interface-name; [edit logical-systems logical-system-name protocols bgp group group-name neighbor ipv6-link-local-address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor ipv6-link-local-address], [edit protocols bgp group group-name neighbor ipv6-link-local-address], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor ipv6-link-local-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the interface name of the peer for IPv6 peering using link-local addresses. This peer is link-local in scope. interface-name—Interface name of the EBGP IPv6 peer. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring EBGP Peering Using IPv6 Link-Local Addresses Chapter 73: Configuration Statements for Layer 3 Protocols local-preference Syntax Hierarchy Level Release Information Description local-preference local-preference; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Modify the value of the LOCAL_PREF path attribute, which is a metric used by IBGP sessions to indicate the degree of preference for an external route. The route with the highest local preference value is preferred. The LOCAL_PREF path attribute always is advertised to internal BGP peers and to neighboring confederations. It is never advertised to external BGP peers. Default Options If you omit this statement, the LOCAL_PREF path attribute, if present, is not modified. local-preference—Preference to assign to routes learned from BGP or from the group or peer. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: If the LOCAL_PREF path attribute is present, do not modify its value. If a BGP route is received without a LOCAL_PREF attribute, the route is handled locally (it is stored in the routing table and advertised by BGP) as if it were received with a LOCAL_PREF value of 100. By default, non-BGP routes that are advertised by BGP are advertised with a LOCAL_PREF value of 100. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • preference on page 1660 • Configuring the Local Preference Value for BGP Routes 1599 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS log-updown Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1600 log-updown; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Log a message whenever a BGP peer makes a state transition. Messages are logged using the system logging mechanism located at the [edit system syslog] hierarchy level. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • traceoptions on page 1718 • Configuring System Logging of BGP Peer State Transitions • Junos OS System Basics Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols loose-authentication-check Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation loose-authentication-check; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Allow the use of MD5 authentication without requiring network-wide deployment. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Authentication for IS-IS Without Network-Wide Deployment lsp-interval Syntax Hierarchy Level Release Information Description Options lsp-interval milliseconds; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the link-state PDU interval time. milliseconds—Number of milliseconds between the sending of link-state PDUs. Specifying a value of 0 blocks all link-state PDU transmission. Range: 0 through 1000 milliseconds Default: 100 milliseconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Transmission Frequency for Link-State PDUs on IS-IS Interfaces 1601 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS lsp-lifetime Syntax Hierarchy Level Release Information Description Options lsp-lifetime seconds; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long a link-state PDU originating from the routing device should persist in the network. The routing device sends link-state PDUs often enough so that the link-state PDU lifetime never expires. seconds—link-state PDU lifetime, in seconds. Range: 350 through 65,535 seconds Default: 1200 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Link-State PDU Lifetime for IS-IS lsp-metric-into-summary Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1602 lsp-metric-into-summary; [edit logical-systems logical-system-name protocols (ospf | ospf3) traffic-engineering shortcuts], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) traffic-engineering shortcuts], [edit protocols (ospf | ospf3) traffic-engineering shortcuts], [edit routing-instances routing-instance-name protocols (ospf | ospf3) traffic-engineering shortcuts] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Advertise the LSP metric in summary LSAs. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling OSPF Traffic Engineering Support Chapter 73: Configuration Statements for Layer 3 Protocols martians Syntax Hierarchy Level Release Information Description Options martians { destination-prefix match-type ; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name], [edit logical-systems logical-system-name routing-options], [edit logical-systems logical-system-name routing-options rib routing-table-name], [edit routing-instances routing-instance-name routing-options], [edit routing-instances routing-instance-name routing-options rib routing-table-name], [edit routing-options], [edit routing-options rib routing-table-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure martian addresses. allow—(Optional) Explicitly allow a subset of a range of addresses that has been disallowed. destination-prefix—Destination route you are configuring: • destination-prefix/prefix-length—destination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length. • default—Default route to use when routing packets do not match a network or host in the routing table. This is equivalent to specifying the IP address 0.0.0.0/0. match-type—Criteria that the destination must match: • exact—Exactly match the route’s mask length. • longer—The route’s mask length is greater than the specified mask length. • orlonger—The route’s mask length is equal to or greater than the specified mask length. • through destination-prefix—The route matches the first prefix, the route matches the second prefix for the number of bits in the route, and the number of bits in the route is less than or equal to the number of bits in the second prefix. • upto prefix-length—The route’s mask length falls between the two destination prefix lengths, inclusive. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Martian Addresses 1603 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS max-areas Syntax Hierarchy Level Release Information Description Options max-areas number; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis] [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Modify the maximum number of IS-IS areas advertised. number—Maximum number of areas to include in the IS-IS hello (IIH) PDUs and link-state PDUs. Range: 3 through 36 Default: 3 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Limiting the Number of Advertised IS-IS Areas maximum-bandwidth Syntax Hierarchy Level Release Information Description Options maximum-bandwidth bps; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast interface interface-name], [edit logical-systems logical-system-name routing-options multicast interface interface-name], [edit routing-instances routing-instance-name routing-options multicast interface interface-name], [edit routing-options multicast interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the multicast bandwidth for the interface. bps—Bandwidth rate, in bits per second, for the multicast interface. Range: 0 through any amount of bandwidth Required Privilege Level Related Documentation 1604 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Defining Interface Bandwidth Maximums Chapter 73: Configuration Statements for Layer 3 Protocols maximum-paths Syntax Hierarchy Level Release Information Description Options maximum-paths path-limit ; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a limit for the number of routes installed in a routing table based upon the route path. log-interval seconds—(Optional) Minimum time interval (in seconds) between log messages. Range: 5 through 86,400 log-only—(Optional) Sets the route limit as an advisory limit. An advisory limit triggers only a warning, and additional routes are not rejected. path-limit—Maximum number of routes. If this limit is reached, a warning is triggered and additional routes are rejected. 32 Range: 1 through 4,294,967,295 (2 – 1) Default: No default threshold value—(Optional) Percentage of the maximum number of routes that starts triggering warning. You can configure a percentage of the path-limit value that starts triggering the warnings. Range: 1 through 100 NOTE: When the number or routes reaches the threshold value, routes are still installed into the routing table while warning messages are sent. When the number or routes reaches the path-limit value, then additional routes are rejected. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Limits for Routing Tables 1605 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS maximum-prefixes Syntax Hierarchy Level Release Information Description Options maximum-prefixes prefix-limit ; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a limit for the number of routes installed in a routing table based upon the route prefix. log-interval seconds—(Optional) Minimum time interval (in seconds) between log messages. Range: 5 through 86,400 log-only—(Optional) Sets the prefix limit as an advisory limit. An advisory limit triggers only a warning, and additional routes are not rejected. prefix-limit—Maximum number of route prefixes. If this limit is reached, a warning is triggered and any additional routes are rejected. Range: 1 through 4,294,967,295 Default: No default threshold value—(Optional) Percentage of the maximum number of prefixes that starts triggering warning. You can configure a percentage of the prefix-limit value that starts triggering the warnings. Range: 1 through 100 NOTE: When the number or routes reaches the threshold value, routes are still installed into the routing table while warning messages are sent. When the number or routes reaches the prefix-limit value, then additional routes are rejected. Required Privilege Level Related Documentation 1606 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Limits for Routing Tables Chapter 73: Configuration Statements for Layer 3 Protocols med-igp-update-interval Syntax Hierarchy Level Release Information Description Options med-igp-update-interval minutes; [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a timer for how long to delay updates for the multiple-exit discriminator (MED) path attribute for BGP groups and peers configured with the metric-out igp offset delay-med-update statement. The timer delays MED updates for the interval configured unless the MED is lower than the previously advertised attribute or another attribute associated with the route has changed or if the BGP peer is responding to a refresh route request. minutes—Interval to delay MED updates. Default: 10 minutes Range: 10 through 600 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • metric-out on page 1615 • Delaying Updates of the MED Path Attribute for BGP 1607 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mesh-group Syntax Hierarchy Level Release Information Description Options mesh-group (blocked | value); [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an interface to be part of a mesh group, which is a set of fully connected nodes. blocked—Configure the interface so that it does not flood link-state PDU packets. value—Number that identifies the mesh group. 32 Range: 1 through 4,294,967,295 (2 Required Privilege Level Related Documentation 1608 – 1; 32 bits are allocated to identify a mesh group) routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Mesh Groups of IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols message-size Syntax Hierarchy Level Release Information Description Options message-size number; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the number of route entries to be included in every RIP update message. To ensure interoperability with other vendors’ equipment, use the standard of 25 route entries per message. number—Number of route entries per update message. Range: 25 through 255 entries Default: 25 entries Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Number of Route Entries in RIP Update Messages 1609 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS metric Syntax Hierarchy Level Release Information Description Options metric metric; [edit logical-systems logical-system-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the metric value for the level. metric—Metric value. Range: 1 through 63, or 1 through 16,777,215 (if you have configured wide metrics) Default: 10 (for all interfaces except lo0), 0 (for the lo0 interface) Required Privilege Level Related Documentation 1610 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • te-metric • wide-metrics-only on page 1745 • Configuring Levels on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols metric Syntax Hierarchy Level Release Information Description metric metric; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf area area-id interface interface-name topology (ipv4-multicast | name)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf area area-id sham-link-remote], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf area area-id interface interface-name topology (ipv4-multicast | name)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf area area-id interface interface-name topology (ipv4-multicast | name)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf area area-id sham-link-remote], [edit routing-instances routing-instance-name protocols ospf area area-id interface interface-name topology (ipv4-multicast | name)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the cost of an OSPF interface. The cost is a routing metric that is used in the link-state calculation. To set the cost of routes exported into OSPF, configure the appropriate routing policy. Options metric—Cost of the route. Range: 1 through 65,535 Default: By default, the cost of an OSPF route is calculated by dividing the reference-bandwidth value by the bandwidth of the physical interface. Any specific value you configure for the metric overrides the default behavior of using the reference-bandwidth value to calculate the cost of route for that interface. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • bandwidth-based-metrics on page 1491 • reference-bandwidth on page 1677 1611 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring the Metric Value for OSPF Interfaces • Configuring OSPF Sham Links • Configuring Multitopology Routing in OSPF metric (Aggregate, Generated, or Static Route) Syntax Hierarchy Level Release Information Description Options (metric | metric2 | metric3 | metric4) metric ; [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options (aggregate | generate | static) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Metric value for an aggregate, generated, or static route. You can specify up to four metric values, starting with metric (for the first metric value) and continuing with metric2, metric3, and metric4. metric—Metric value. 32 Range: 0 through 4,294,967,295 (2 – 1) type type—(Optional) Type of route. Range: 1 through 16 Required Privilege Level Related Documentation 1612 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • static on page 1708 • Configuring Static Route Options • Configuring Aggregate Route Options • Configuring Generated Route Options Chapter 73: Configuration Statements for Layer 3 Protocols metric-in Syntax Hierarchy Level Release Information Description Options metric-in metric; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the metric to add to incoming routes when advertising into RIP routes that were learned from other protocols. Use this statement to configure the routing device to prefer RIP routes learned through a specific neighbor. metric—Metric value. Range: 1 through 16 Default: 1 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Metric Value Added to Imported RIP Routes 1613 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS metric-in Syntax Hierarchy Level Release Information Description Options metric-in metric; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name], [edit protocols ripng], [edit protocols ripng group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols ripng], [edit routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the metric to add to incoming routes when advertising into RIPng routes that were learned from other protocols. Use this statement to configure the routing device to prefer RIPng routes learned through a specific neighbor. metric—Metric value. Range: 1 through 16 Default: 1 Required Privilege Level Related Documentation 1614 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Metric Value Added to Imported RIPng Routes Chapter 73: Configuration Statements for Layer 3 Protocols metric-out Syntax Hierarchy Level Release Information Description metric-out (metric | minimum-igp offset | igp (delay-med-update | offset); [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Metric for all routes sent using the multiple exit discriminator (MED, or MULTI_EXIT_DISC) path attribute in update messages. This path attribute is used to discriminate among multiple exit points to a neighboring AS. If all other factors are equal, the exit point with the lowest metric is preferred. You can specify a constant metric value by including the metric option. For configurations in which a BGP peer sends third-party next hops that require the local system to perform next-hop resolution—IBGP configurations, configurations within confederation peers, or EBGP configurations that include the multihop command—you can specify a variable metric by including the minimum-igp or igp option. You can increase or decrease the variable metric calculated from the IGP metric (either from the igp or igp-minimum statement) by specifying a value for offset. The metric is increased by specifying a positive value for offset, and decreased by specifying a negative value for offset. You can specify for a BGP group or peer not to advertise updates for the MED path attributes used to calculate IGP costs for BGP next hops unless the MED is lower. You can also configure an interval to delay when MED updates are sent by including the med-igp-update-interval minutes at the [edit routing-options] hierarchy level. Options delay-med-update—Specify for a BGP group or peer configured with the metric-out igp statement not to advertise MED updates when the value worsens, that is, unless the value is lower. 1615 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: You cannot configure delay-med–update statement at the global BGP level. igp—Set the metric to the most recent metric value calculated in the IGP to get to the BGP next hop. metric—Primary metric on all routes sent to peers. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: No metric is sent. minimum-igp—Set the metric to the minimum metric value calculated in the IGP to get to the BGP next hop. If a newly calculated metric is greater than the minimum metric value, the metric value remains unchanged. If a newly calculated metric is lower, the metric value is lowered to that value. offset—(Optional) Increases or decreases the metric by this value. 31 31 Range: –2 through 2 – 1 Default: None Required Privilege Level Related Documentation 1616 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • med-igp-update-interval on page 1607 • Configuring the MED in BGP Updates Chapter 73: Configuration Statements for Layer 3 Protocols metric-out Syntax Hierarchy Level Release Information Description Options metric-out metric; [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the metric value to add to routes transmitted to the neighbor. Use this statement to control how other routing devices prefer RIP routes sent from this neighbor. metric—Metric value. Range: 1 through 16 Default: 1 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Group-Specific RIP Properties 1617 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS metric-out Syntax Hierarchy Level Release Information Description Options metric-out metric; [edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name], [edit protocols ripng group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the metric value to add to routes transmitted to the neighbor. Use this statement to control how other routing devices prefer RIPng routes sent from this neighbor. metric—Metric value. Range: 1 through 16 Default: 1 Required Privilege Level Related Documentation 1618 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Group-Specific RIPng Properties Chapter 73: Configuration Statements for Layer 3 Protocols metric-type Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation metric-type type; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id nssadefault-lsa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id nssa default-lsa], [edit protocols (ospf | ospf3) area area-id nssa default-lsa], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id nssa default-lsa], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit routing-instances routing-instances protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id nssa default-lsa] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the external metric type for the default LSA. type—Metric type: 1 or 2 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Areas 1619 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mtu-discovery Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1620 mtu-discovery; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure TCP path maximum transmission unit (MTU) discovery. MTU discovery improves convergence times for IBGP sessions. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring MTU Discovery for BGP Sessions Chapter 73: Configuration Statements for Layer 3 Protocols multicast Syntax Hierarchy Level Release Information Description multicast { forwarding-cache { threshold suppress value ; } interface interface-name { enable; } scope scope-name { interface [ interface-names ]; prefix destination-prefix; } ssm-groups { address; } } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure generic multicast properties. NOTE: You cannot apply a scoping policy to a specific routing instance. All scoping policies are applied to all routing instances. However, you can apply the scope statement to a specific routing instance. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • (indirect-next-hop on page 1573 | no-indirect-next-hop) • Configuring Multicast Scoping • Configuring Additional Source-Specific Multicast Groups • Junos OS Multicast Configuration Guide 1621 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS multihop Syntax Hierarchy Level Release Information Description multihop { no-nexthop-change; ttl-value; } [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an EBGP multihop session. External confederation peering is a special case that allows unconnected third-party next hops. You do not need to configure multihop sessions explicitly in this particular case; multihop behavior is implied. If you have confederation external BGP peer-to-loopback addresses, you still need the multihop configuration. Default Options If you omit this statement, all EBGP peers are assumed to be directly connected (that is, you are establishing a nonmultihop, or “regular,” BGP session), and the default time-to-live (TTL) value is 1. no-nexthop-change—Specify not to change the BGP next-hop value; for route advertisements, specify the no-nexthop-self option. ttl-value—Configure the maximum TTL value for the TTL in the IP header of BGP packets. Range: 1 through 255 Default: 64 (for multihop EBGP sessions, confederations, and IBGP sessions) Required Privilege Level 1622 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 73: Configuration Statements for Layer 3 Protocols Related Documentation • Configuring EBGP Multihop Sessions multipath Syntax Hierarchy Level Release Information Description Options multipath { multiple-as; } [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Allow load sharing among multiple EBGP paths and multiple IBGP paths. multiple-as—Disable the default check requiring that paths accepted by BGP multipath must have the same neighboring AS. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Selecting Multiple Equal-Cost Active Paths 1623 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS neighbor Syntax 1624 neighbor address { accept-remote-nexthop; advertise-external ; advertise-inactive; (advertise-peer-as | no-advertise-peer-as); as-override; authentication-algorithm algorithm; authentication-key key; authentication-key-chain key-chain; cluster cluster-identifier; damping; description text-description; export [ policy-names ]; family { (inet | inet6 | inet-mvpn | inet6-mpvn | inet-vpn | inet6-vpn | iso-vpn | l2-vpn) { (any | flow | multicast | unicast | signaling) { accepted-prefix-limit { maximum number; teardown ; } prefix-limit { maximum number; teardown ; } rib-group group-name; } flow { no-validate policy-name; } labeled-unicast { accepted-prefix-limit { maximum number; teardown ; } aggregate-label { community community-name: } explicit-null { connected-only; } prefix-limit { maximum number; teardown ; } resolve-vpn; rib inet.3; rib-group group-name; } } route-target { advertise-default; external-paths number; Chapter 73: Configuration Statements for Layer 3 Protocols accepted-prefix-limit { maximum number; teardown ; } prefix-limit { maximum number; teardown ; } } signaling { prefix-limit { maximum number; teardown ; } } } graceful-restart { disable; restart-time seconds; stale-routes-time seconds; } hold-time seconds; import [ policy-names ]; ipsec-sa ipsec-sa; keep (all | none); local-address address; local-as autonomous-system ; local-interface interface-name; local-preference preference; log-updown; metric-out (metric | minimum-igp | igp ); mtu-discovery; multihop ; multipath { multiple-as; } no-aggregator-id; no-client-reflect; out-delay seconds; passive; peer-as autonomous-system; preference preference; tcp-mss segment-size; traceoptions { file filename ; flag flag ; } vpn-apply-export; } Hierarchy Level [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name] 1625 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Release Information Description Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Explicitly configure a neighbor (peer). To configure multiple BGP peers, include multiple neighbor statements. By default, the peer’s options are identical to those of the group. You can override these options by including peer-specific option statements within the neighbor statement. The neighbor statement is one of the statements you can include in the configuration to define a minimal BGP configuration on the routing device. (You can include an allow all statement in place of a neighbor statement.) Options address—IPv6 or IPv4 address of a single peer. The remaining statements are explained separately. Required Privilege Level Related Documentation 1626 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum BGP Configuration • Configuring BGP Groups and Peers Chapter 73: Configuration Statements for Layer 3 Protocols neighbor Syntax Hierarchy Level Release Information neighbor neighbor-name { authentication-key password; authentication-type type; bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } multiplier number; version (0 | 1 | automatic); } (check-zero | no-check-zero); import policy-name; message-size number; metric-in metric; metric-out metric; receive receive-options; route-timeout seconds; send send-options; update-interval seconds; } [edit logical-systems logical-system-name protocols rip group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name], [edit protocols rip group group-name], [edit routing-instances routing-instance-name protocols rip group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure neighbor-specific RIP parameters, thereby overriding the defaults set for the routing device. Options neighbor-name—Name of an interface over which a routing device communicates to its neighbors. The remaining statements are explained separately. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 1627 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Overview of RIP Neighbor Properties neighbor Syntax Hierarchy Level Release Information Description Options neighbor neighbor-name { import [ policy-names ]; metric-in metric; receive ; route-timeout seconds; send ; update-interval seconds; } [edit logical-systems logical-system-name protocols ripng group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name], [edit protocols ripng group group-name], [edit routing-instances routing-instance-name protocols ripng group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure neighbor-specific RIPng parameters, thereby overriding the defaults set for the routing device. neighbor-name—Name of an interface over which a routing device communicates to its neighbors. The remaining statements are explained separately. Required Privilege Level Related Documentation 1628 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Overview of RIPng Neighbor Properties Chapter 73: Configuration Statements for Layer 3 Protocols no-adjacency-holddown Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-adjacency-holddown; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the hold-down timer for IS-IS adjacencies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Quicker Advertisement of IS-IS Adjacency State Changes 1629 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-aggregator-id Syntax Hierarchy Level Release Information [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Set the router ID in the BGP aggregator path attribute to zero. (This is one of the path attributes included in BGP update messages.) Doing this prevents different routing devices within an AS from creating aggregate routes that contain different AS paths. Default If you omit this statement, the router ID is included in the BGP aggregator path attribute. Required Privilege Level Related Documentation 1630 no-aggregator-id; routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Overview of BGP Messages • Controlling BGP Route Aggregation Chapter 73: Configuration Statements for Layer 3 Protocols no-authentication-check Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-authentication-check; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Generate authenticated packets and check the authentication on received packets, but do not reject packets that cannot be authenticated. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • csnp-interval on page 1516 • hello-authentication-type on page 1557 • Configuring IS-IS Authentication 1631 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-client-reflect Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1632 no-client-reflect; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable intracluster route redistribution by the system acting as the route reflector. Include this statement when the client cluster is fully meshed to prevent the sending of redundant route advertisements. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • cluster on page 1513 • Configuring BGP Route Reflection Chapter 73: Configuration Statements for Layer 3 Protocols no-csnp-authentication Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-csnp-authentication; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Suppress authentication check on complete sequence number PDU (CSNP) packets. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • csnp-interval on page 1516 • Configuring IS-IS Authentication no-eligible-backup Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-eligible-backup; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Exclude the specified interface as a backup interface for IS-IS interfaces on which link protection or node-link protection is enabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • link-protection on page 1594 • node-link-protection on page 1641 • Configuring Loop-Free Alternate Routes for IS-IS 1633 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-hello-authentication Syntax Hierarchy Level no-hello-authentication; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Suppress authentication check on complete sequence number hello packets. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • hello-authentication-type on page 1557 • Configuring IS-IS Authentication no-ipv4-multicast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 1634 no-ipv4-multicast; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Exclude an interface from the IPv4 multicast topologies. Multicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies Chapter 73: Configuration Statements for Layer 3 Protocols no-ipv4-routing Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-ipv4-routing; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable IP version 4 (IPv4) routing. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling IPv4 Routing for IS-IS no-ipv6-multicast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation no-ipv6-multicast; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Exclude an interface from the IPv6 multicast topologies. Multicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies 1635 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-ipv6-routing Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-ipv6-routing; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable IP version 6 (IPv6) routing. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling IPv6 Routing for IS-IS no-ipv6-unicast Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 1636 no-ipv6-unicast; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Exclude an interface from the IPv6 unicast topologies. IPv6 unicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS IPv6 Unicast Topologies Chapter 73: Configuration Statements for Layer 3 Protocols no-nssa-abr Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-nssa-abr; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable exporting Type 7 link-state advertisements into not-stubby-areas (NSSAs) for an autonomous system boundary router (ASBR) or an area border router (ABR). routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling Export of LSAs into NSSAs Attached to ASBR ABRs no-psnp-authentication Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-psnp-authentication; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Suppress authentication check on partial sequence number PDU (PSNP) packets. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Authentication 1637 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-qos-adjust Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1638 no-qos-adjust; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast interface interface-name reverse-oif-mapping], [edit logical-systems logical-system-name routing-options multicast interface interface-name], [edit logical-systems logical-system-name routing-options multicast interface interface-name reverse-oif-mapping], [edit routing-instances routing-instance-name routing-options multicast interface interface-name], [edit routing-instances routing-instance-name routing-options multicast interface interface-name reverse-oif-mapping], [edit routing-options multicast interface interface-name], [edit routing-options multicast interface interface-name reverse-oif-mapping] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable hierarchical bandwidth adjustment for all subscriber interfaces that are identified by their MLD or IGMP request from a specific multicast interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Managing Subscriber Overcommitment Chapter 73: Configuration Statements for Layer 3 Protocols no-rfc-1583 Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation no-rfc-1583; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable compatibility with RFC 1583, OSPF Version 2. If the same external destination is advertised by AS boundary routers that belong to different OSPF areas, disabling compatibility with RFC 1583 can prevent routing loops. Compatibility with RFC 1583 is enabled by default. routing—To view this statement in the configuration. routing-control-level—To add this statement to the configuration. • Disabling OSPFv2 Compatibility with RFC 1583 1639 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-unicast-topology Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation no-unicast-topology; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Exclude an interface from the IPv4 unicast topologies. IPv4 unicast topologies are disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies no-validate Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1640 no-validate policy-name; [edit protocols bgp group group-name family (inet | inet flow)], [edit protocols bgp group group-name neighbor address family (inet | inet flow)], [edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet flow)], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet flow)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Omits the flow route validation procedure after packets are accepted by a policy. policy-name—Import policy to match NLRI messages. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling BGP to Carry Flow-Specification Routes Chapter 73: Configuration Statements for Layer 3 Protocols node-link-protection Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation node-ink-protection; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-routers logical-router-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable node-link protection on the specified IS-IS interface. The Junos OS creates an alternate loop-free path to the primary next hop for all destination routes that traverse a protected interface. This alternate path avoids the primary next-hop routing device altogether and establishes a path through a different routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • link-protection on page 1594 • Configuring Loop-Free Alternate Routes for IS-IS 1641 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS nssa Syntax Hierarchy Level Release Information Description nssa { area-range network/mask-length ; default-lsa { default-metric metric; metric-type type; type-7; } (no-summaries | summaries); } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3) area area-id], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a not-so-stubby area (NSSA). An NSSA allows external routes to be flooded within the area. These routes are then leaked into other areas. You cannot configure an area as being both a stub area and an NSSA. The remaining statements are explained separately. Required Privilege Level Related Documentation 1642 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • stub on page 1710 • Configuring OSPF Areas Chapter 73: Configuration Statements for Layer 3 Protocols options Syntax Hierarchy Level Release Information options { syslog (level level | upto level level); } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the types of system logging messages sent about the routing protocols process to the system message logging file. These messages are also displayed on the system console. You can log messages at a particular level, or up to and including a particular level. Options level level—Severity of the message. It can be one or more of the following levels, in order of decreasing urgency: • alert—Conditions that should be corrected immediately, such as a corrupted system database. • critical—Critical conditions, such as hard drive errors. • debug—Software debugging messages. • emergency—Panic or other conditions that cause the system to become unusable. • error—Standard error conditions. • info—Informational messages. • notice—Conditions that are not error conditions, but might warrant special handling. • warning—System warning messages. upto level level—Log all messages up to a particular level. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • syslog in the Junos OS System Basics Configuration Guide • Configuring System Logging for the Routing Protocol Process 1643 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ospf Syntax Hierarchy Level Release Information Description ospf { ... } [edit logical-systems logical-system-name protocols], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable OSPF routing on the routing device. You must include the ospf statement to enable OSPF on the routing device. Default Required Privilege Level Related Documentation OSPF is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum OSPF Configuration ospf3 Syntax Hierarchy Level Release Information Description ospf3 { ... } [edit logical-systems logical-system-name protocols], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable OSPFv3 routing on the routing device. You must include the ospf3 statement to enable OSPFv3. Default Required Privilege Level Related Documentation 1644 OSPFv3 is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum OSPF Configuration Chapter 73: Configuration Statements for Layer 3 Protocols out-delay Syntax Hierarchy Level Release Information Description Default Options out-delay seconds; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long a route must be present in the Junos OS routing table before it is exported to BGP. Use this time delay to help bundle routing updates. If you omit this statement, routes are exported to BGP immediately after they have been added to the routing table. seconds—Output delay time. Range: 0 through 65,535 seconds Default: 0 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Policies to BGP Routes 1645 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS outbound-route-filter Syntax Hierarchy Level Release Information outbound-route-filter { bgp-orf-cisco-mode; prefix-based { accept { (inet | inet6); } } } [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure a BGP peer to accept outbound route filters from a remote peer. Options accept—Specify that outbound route filters from a BGP peer be accepted. inet—Specify that IPv4 prefix-based outbound route filters be accepted. inet6—Specify that IPv6 prefix-based outbound route filters be accepted. NOTE: You can specify that both IPv4 and IPv6 outbound route filters be accepted. prefix-based—Specify that prefix-based filters be accepted. The bgp-orf-cisco-mode statement is explained separately. Required Privilege Level Related Documentation 1646 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Applying Filters Provided by BGP Peers to Outbound Routes Chapter 73: Configuration Statements for Layer 3 Protocols overload Syntax Hierarchy Level Release Information Description overload { advertise-high-metrics; timeout seconds; } [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the local routing device so that it appears to be overloaded. You might want to do this when you want the routing device to participate in IS-IS routing, but do not want it to be used for transit traffic. Note that traffic to immediately attached interfaces continues to transit the routing device. You can also advertise maximum link metrics in network layer reachability information (NLRI) instead of setting the overload bit. NOTE: If the time elapsed after the IS-IS instance is enabled is less than the specified timeout, overload mode is set. Options advertise-high-metrics—Advertise maximum link metrics in NLRIs instead of setting the overload bit. timeout seconds—Number of seconds at which the overloading is reset. Default: 0 seconds Range: 60 through 1800 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS to Make Routing Devices Appear Overloaded 1647 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS overload Syntax Hierarchy Level Release Information Description overload { timeout seconds; } [edit logical-systems logical-system-name protocols (oospf | ospf3)], [edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast | name)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical systems logical-system-name routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf topology (default | ipv4-multicast | name)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)] [edit routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the local routing device so that it appears to be overloaded. You might do this when you want the routing device to participate in OSPF routing, but do not want it to be used for transit traffic. NOTE: Traffic destined to immediately attached interfaces continues to reach the routing device. Options timeout seconds—(Optional) Number of seconds at which the overloading is reset. If no timeout interval is specified, the routing device remains in overload state until the overload statement is deleted or a timeout is set. Range: 60 through 1800 seconds Default: 0 seconds NOTE: Multitopology Routing does not support the timeout option. Required Privilege Level 1648 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 73: Configuration Statements for Layer 3 Protocols Related Documentation • Configuring OSPF to Make Routing Devices Appear Overloaded • Configuring Multitopology Routing in OSPF passive Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation passive; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Do not send active open messages to the peer. Rather, wait for the peer to issue an open request. If you omit this statement, all explicitly configured peers are active, and each peer periodically sends open requests until its peer responds. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling Transmission of Open Requests to BGP Peers 1649 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS passive Syntax Hierarchy Level Release Information Description passive; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Advertise the direct interface addresses on an interface or into a level on the interface without actually running IS-IS on that interface or level. This statement effectively prevents IS-IS from running on the interface. To enable IS-IS on an interface, include the interface statement at the [edit protocols isis] or the [edit routing-instances routing-instance-name protocols isis] hierarchy level. To disable it, include the disable statement at those hierarchy levels. The three states are mutually exclusive. Required Privilege Level Related Documentation 1650 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • disable • Configuring Levels on IS-IS Interfaces Chapter 73: Configuration Statements for Layer 3 Protocols passive Syntax Hierarchy Level Release Information Description passive { traffic-engineering { remote-node-id address; } } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Advertise the direct interface addresses on an interface without actually running OSPF on that interface. A passive interface is one for which the address information is advertised as an internal route in OSPF, but on which the protocol does not run. To configure an interface in OSPF passive traffic engineering mode, include the traffic-engineering statement. Configuring OSPF passive traffic engineering mode enables the dynamic discovery of OSPF AS boundary routers. Enable OSPF on an interface by including the interface statement at the [edit protocols (ospf | ospf3) area area-id] or the [edit routing-instances routing-instance-name protocols ospf area area-id] hierarchy levels. Disable it by including the disable statement, To prevent OSPF from running on an interface, include the passive statement. These three states are mutually exclusive. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • disable on page 1524 • Advertising Interface Addresses Without Running OSPF • Configuring OSPF Passive Traffic Engineering Mode 1651 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS peer-as Syntax Hierarchy Level Release Information Description peer-as autonomous-system; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the neighbor (peer) AS number. The autonomous system (AS) numeric range in plain-number format provides BGP support for 4-byte AS numbers, as defined in RFC 4893, BGP Support for Four-octet AS Number Space. You can also configure a 4-byte AS number using the AS-dot notation format of two integer values joined by a period: <16-bit high-order value in decimal>.<16-bit low-order value in decimal>. For example, the 4-byte AS number of 65,546 in plain-number format is represented as 1.10 in the AS-dot notation format. Options autonomous-system—AS number. 32 Range: 1 through 4,294,967,295 (2 – 1) in plain-number format Range: 0.0 through 65535.65535 in AS-dot notation format Required Privilege Level Related Documentation 1652 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BGP Groups and Peers • Configuring BGP Groups and Peers Chapter 73: Configuration Statements for Layer 3 Protocols pim-to-igmp-proxy Syntax Hierarchy Level Release Information Description pim-to-igmp-proxy { upstream-interface [ interface-names ]; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the rendezvous point (RP) routing device that resides between a customer edge–facing Protocol Independent Multicast (PIM) domain and a core-facing PIM domain to translate PIM join or prune messages into corresponding Internet Group Management Protocol (IGMP) report or leave messages. The routing device then transmits the report or leave messages by proxying them to one or two upstream interfaces that you configure on the RP routing device. Including the pim-to-igmp-proxy statement enables you to use IGMP to forward IPv4 multicast traffic across the PIM sparse mode domains. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM-to-IGMP Message Translation 1653 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS pim-to-mld-proxy Syntax Hierarchy Level Release Information Description pim-to-mld-proxy { upstream-interface [ interface-names ]; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the rendezvous point (RP) routing device that resides between a customer edge–facing Protocol Independent Multicast (PIM) domain and a core-facing PIM domain to translate PIM join or prune messages into corresponding Multicast Listener Discovery (MLD) report or leave messages. The routing device then transmits the report or leave messages by proxying them to one or two upstream interfaces that you configure on the RP routing device. Including the pim-to-mld-proxy statement enables you to use MLD to forward IPv6 multicast traffic across the PIM sparse mode domains. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM-to-MLD Message Translation point-to-point Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1654 point-to-point; [edit logical-systems logical-system-name protocols isis interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name], [edit protocols isis interface interface-name], [edit routing-instances routing-instance-name protocols isis interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an IS-IS interface to behave like a point-to-point connection. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Point-to-Point Interfaces for IS-IS Chapter 73: Configuration Statements for Layer 3 Protocols policy Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation policy policy-name; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit routing-instances routing-instance-name routing-options (aggregate | generate) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)], [edit routing-options (aggregate | generate) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate a routing policy when configuring an aggregate or generated route’s destination prefix in the routes part of the aggregate or generate statement. This provides the equivalent of an import routing policy filter for the destination prefix. That is, each potential contributor to an aggregate route, along with any aggregate options, is passed through the policy filter. The policy then can accept or reject the route as a contributor to the aggregate route and, if the contributor is accepted, the policy can modify the default preferences. The contributor with the numerically smallest prefix becomes the most preferred, or primary, contributor. A rejected contributor still can contribute to a less specific aggregate route. If you do not specify a policy filter, all candidate routes contribute to an aggregate route. policy-name—Name of a routing policy. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • Configuring Aggregate Routes • Configuring Generated Routes 1655 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS policy (Flow Maps) Syntax Hierarchy Level Release Information Description Options Required Privilege Level policy [ policy-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name], [edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit routing-options multicast flow-map flow-map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a flow map policy. policy-names—Name of one or more policies for flow mapping. routing—To view this statement in the configuration. policy (SSM Maps) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1656 policy [ policy-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast ssm-map ssm-map-name], [edit logical-systems logical-system-name routing-options multicast ssm-map ssm-map-name], [edit routing-instances routing-instance-name routing-options multicast ssm-map ssm-map-name], [edit routing-options multicast ssm-map ssm-map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to an SSM map. policy-names—Name of one or more policies for SSM mapping. routing—To view this statement in the configuration. routing-control—To view this statement in the configuration. • Example: Configuring SSM Mapping Chapter 73: Configuration Statements for Layer 3 Protocols ppm Syntax Hierarchy Level Release Information Description ppm { centralized; } [edit protocols lacp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure PPM processing options for Link Aggregation Control Protocol (LACP) packets. This command configures the PPM processing options for LACP packets only. You can disable distributed PPM processing for all packets that use PPM and run all PPM processing on the Routing Engine by entering the no-delegate-processing configuration statement in the [edit routing-options ppm] statement hierarchy. Default Required Privilege Level Related Documentation Distributed PPM processing is enabled for all packets that use PPM. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Distributed Periodic Packet Management on a J-EX Series Switch (CLI Procedure) on page 1451 1657 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ppm Syntax Hierarchy Level Release Information Description ppm { no-delegate-processing; } [edit logical-systems logical-system-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. no-delegate-processing statement introduced in Junos OS Release 10.2 for J-EX Series switches. Disable distributed periodic packet management (PPM) to the Packet Forwarding Engine (on routers), to access ports (on J-EX4200 switches), or line cards (on J-EX8200 switches). After you disable PPM, PPM processing continues to run on the Routing Engine. Default Options enabled no-delegate-processing—Disable PPM to the Packet Forwarding Engine, access ports, or line cards. Distributed PPM is enabled by default. Required Privilege Level Related Documentation 1658 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling Distributed Periodic Packet Management on the Packet Forwarding Engine Chapter 73: Configuration Statements for Layer 3 Protocols preempt Syntax Hierarchy Level Release Information Description (preempt | no-preempt) { hold-time seconds; } [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether a backup router can preempt a master router: • preempt—Allow the master router to be preempted. • no-preempt—Prohibit the preemption of the master router. The remaining statement is explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 1659 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS preference Syntax Hierarchy Level Release Information Description preference preference; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the preference for routes learned from BGP. At the BGP global level, the preference statement sets the preference for routes learned from BGP. You can override this preference in a BGP group or peer preference statement. At the group or peer level, the preference statement sets the preference for routes learned from the group or peer. Use this statement to override the preference set in the BGP global preference statement when you want to favor routes from one group or peer over those of another. Options preference—Preference to assign to routes learned from BGP or from the group or peer. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 170 for the primary preference Required Privilege Level Related Documentation 1660 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • local-preference on page 1599 • Configuring the Default Preference Value for BGP Routes Chapter 73: Configuration Statements for Layer 3 Protocols preference Syntax Hierarchy Level Release Information Description Options preference preference; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the preference of internal routes. preference—Preference value. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 15 (for Level 1 internal routes), 18 (for Level 2 internal routes), 160 (for Level 1 external routes), 165 (for Level 2 external routes) Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • external-preference on page 1534 • Configuring Preference Values for IS-IS Routes 1661 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS preference Syntax Hierarchy Level Release Information Description Options preference preference; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the route preference for OSPF internal routes. preference—Preference value. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 10 Required Privilege Level Related Documentation 1662 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • external-preference on page 1535 • Configuring Preference Values for OSPF Routes Chapter 73: Configuration Statements for Layer 3 Protocols preference Syntax Hierarchy Level Release Information Description Options preference preference; [edit logical-systems logical-system-name protocols rip group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name], [edit protocols rip group group-name], [edit routing-instances routing-instance-name protocols rip group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the preference of external routes learned by RIP as compared to those learned from other routing protocols. preference—Preference value. A lower value indicates a more preferred route. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 100 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Group-Specific RIP Properties preference Syntax Hierarchy Level Release Information Description Options preference preference; [edit logical-systems logical-system-name protocols ripng group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name], [edit protocols ripng group group-name], [edit routing-instances routing-instance-name protocols ripng group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the preference of external routes learned by RIPng as compared to those learned from other routing protocols. preference—Preference value. A lower value indicates a more preferred route. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 100 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Group-Specific RIPng Properties 1663 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS preference Syntax Hierarchy Level Release Information Description Options (preference | preference2 | color | color2) preference ; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Preference value for a static, aggregated, or generated route. You also can specify a secondary preference value (preference2), as well as colors, which are even finer-grained preference values (color and color2). preference—Preference value. A lower number indicates a more preferred route. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 5 (for static routes), 130 (for aggregate and generated routes) type—(Optional) Type of route. Range: 1 through 16 Required Privilege Level Related Documentation 1664 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • static on page 1708 • Configuring Static Routes • Configuring Aggregate Routes • Configuring Generated Routes Chapter 73: Configuration Statements for Layer 3 Protocols prefix Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation prefix destination-prefix; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast scope scope-name], [edit logical-systems logical-system-name routing-options multicast scope scope-name], [edit routing-instances routing-instance-name routing-options multicast scope scope-name], [edit routing-options multicast scope scope-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the prefix for multicast scopes. destination-prefix—Address range for the multicast scope. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • multicast on page 1621 • Configuring Multicast Scoping prefix-export-limit Syntax Hierarchy Level Release Information Description Options prefix-export-limit number; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a limit to the number of prefixes exported into IS-IS. number—Prefix limit. 32 Range: 0 through 4,294,967,295 (2 Required Privilege Level Related Documentation – 1) routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Limiting the Number of Prefixes Exported to IS-IS 1665 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS prefix-export-limit Syntax Hierarchy Level Release Information Description Options prefix-export-limit number; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast | name)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf topology (default | ipv4-multicast | name)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a limit to the number of prefixes exported into OSPF. number—Prefix limit. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: None Required Privilege Level Related Documentation 1666 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Limiting the Number of Prefixes Exported to OSPF • Configuring Multitopology Routing in OSPF Chapter 73: Configuration Statements for Layer 3 Protocols prefix-limit Syntax Hierarchy Level Release Information Description Options prefix-limit { maximum number; teardown ; } [edit logical-systems logical-system-name protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit protocols bgp group group-name family (inet | inet6) (any | labeled-unicast | multicast | unicast)], [edit protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit routing-instances routing-instance-name protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Limit the number of prefixes received on a BGP peering session and a rate-limit logging when injected prefixes exceed a set limit. maximum number—When you set the maximum number of prefixes, a message is logged when that number is exceeded. 32 Range: 1 through 4,294,967,295 (2 – 1) teardown —If you include the teardown statement, the session is torn down when the maximum number of prefixes is reached. If you specify a percentage, messages are logged when the number of prefixes exceeds that percentage. After the session is torn down, it is reestablished in a short time unless you include the idle-timeout statement. Then the session can be kept down for a specified amount of time, or forever. If you specify forever, the session is reestablished only after you issue a clear bgp neighbor command. Range: 1 through 100 1667 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS idle-timeout (forever | timeout-in-minutes)—(Optional) If you include the idle-timeout statement, the session is torn down for a specified amount of time, or forever. If you specify a period of time, the session is allowed to reestablish after this timeout period. If you specify forever, the session is reestablished only after you intervene with a clear bgp neighbor command. Range: 1 through 2400 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • accepted-prefix-limit • Enabling Multiprotocol BGP priority Syntax Hierarchy Level Release Information priority number; [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-id], [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure a switch’s priority for becoming the master default routing platform. The routing platform with the highest priority within the group becomes the master. Options number—Routing platform’s priority for being elected to be the master router in the VRRP group. A larger value indicates a higher priority for being elected. Range: 1 through 255 Default: 100 (for backup routers) NOTE: Priority 255 cannot be assigned to routed VLAN interfaces (RVIs). Required Privilege Level Related Documentation 1668 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 Chapter 73: Configuration Statements for Layer 3 Protocols priority Syntax Hierarchy Level Release Information Description priority number; [edit logical-systems logical-system-name protocols isis interface interface-name level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis interface interface-name level level-number], [edit protocols isis interface interface-name level level-number], [edit routing-instances routing-instance-name protocols isis interface interface-name level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. The interface’s priority for becoming the designated router. The interface with the highest priority value becomes that level’s designated router. The priority value is meaningful only on a multiaccess network. It has no meaning on a point-to-point interface. Options number—Priority value. Range: 0 through 127 Default: 64 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Levels on IS-IS Interfaces 1669 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS priority Syntax Hierarchy Level Release Information Description Options priority number; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the routing device’s priority for becoming the designated routing devices. The routing device that has the highest priority value on the logical IP network or subnet becomes the network’s designated router. You must configure at least one routing device on each logical IP network or subnet to be the designated router. You also should specify a routing device’s priority for becoming the designated router on point-to-point interfaces. number—Routing device’s priority for becoming the designated router. A priority value of 0 means that the routing device never becomes the designated router. A value of 1 means that the routing device has the least chance of becoming a designated router. Range: 0 through 255 Default: 128 Required Privilege Level Related Documentation 1670 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • OSPF Designated Router Overview • Configuring the Designated Router Priority for OSPF Chapter 73: Configuration Statements for Layer 3 Protocols qualified-next-hop Syntax Hierarchy Level Release Information Description Options qualified-next-hop (address | interface-name) { interface interface-name; metric metric; preference preference; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static route destination-prefix], [edit logical-systems logical-system-name routing-options rib inet6.0 static route destination-prefix], [edit logical-systems logical-system-name routing-options static route destination-prefix], [edit routing-instances routing-instance-name routing-options static route destination-prefix], [edit routing-options rib inet6.0 static route destination-prefix], [edit routing-options static route destination-prefix] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an independent metric or preference on a static route. address—IPv4, IPv6, or ISO network address of the next hop. interface-name—Name of the interface on which to configure an independent metric or preference for a static route. To configure an unnumbered Ethernet interface as the next-hop interface for a static route, specify qualified-next-hop interface-name, where interface-name is the name of the IPv4 or IPv6 unnumbered Ethernet interface. metric—Metric value. 32 Range: 0 through 4,294,967,295 (2 – 1) preference—Preference value. A lower number indicates a more preferred route. 32 Range: 0 through 4,294,967,295 (2 – 1) Default: 5 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring an Independent Preference for Static Routes 1671 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS readvertise Syntax Hierarchy Level Release Information Description (readvertise | no-readvertise); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-options static (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit routing-instances routing-instance-name routing-options static (defaults | route)], [edit routing-options rib routing-table-name static (defaults | route)], [edit routing-options static (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether static routes are eligible to be readvertised by routing protocols: • readvertise—Readvertise static routes. • no-readvertise—Mark a static route as being ineligible for readvertisement; include the no-readvertise option when configuring the route. Default Required Privilege Level Related Documentation 1672 readvertise routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • static on page 1708 • Configuring Static Routes Chapter 73: Configuration Statements for Layer 3 Protocols realm Syntax Hierarchy Level Release Information Description Options realm (ipv4-unicast | ipv4-multicast | ipv6-unicast) { area area-id { interface interface-name; } } [edit logical-systems logical-system-name protocols ospf3], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3], [edit protocols ospf3], [edit routing-instances routing-instance-name protocols ospf3] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure OSPFv3 to advertise address families other than unicast IPv6. The Junos OS maps each address family you configure to a separate realm with its own set of neighbors and link-state database. ipv4-unicast—Configure a realm for IPv4 unicast routes. ipv4-multicast—Configure a realm for IPv4 multicast routes. ipv6-multicast—Configure a realm for IPv6 multicast routes. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Multiple Address Families for OSPFv3 1673 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS receive Syntax Hierarchy Level Release Information Description Options receive receive-options; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RIP receive options. receive-options—One of the following: • both—Accept both RIP version 1 and version 2 packets. • none—Do not receive RIP packets. • version-1—Accept only RIP version 1 packets. • version-2—Accept only RIP version 2 packets. Default: both Required Privilege Level Related Documentation 1674 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • send on page 1700 • Configuring RIP Update Messages Chapter 73: Configuration Statements for Layer 3 Protocols receive Syntax Hierarchy Level Release Information Description Options receive ; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name], [edit protocols ripng], [edit protocols ripng group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols ripng], [edit routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable or disable receiving of update messages. none—(Optional) Disable receiving update messages. Default: Enabled Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • send on page 1701 • Configuring RIPng Update Messages 1675 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS redundant-sources Syntax Hierarchy Level Release Information Description Options redundant-sources [ addresses ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name], [edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit routing-options multicast flow-map flow-map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a list of redundant sources for multicast flows defined by a flow map. addresses—List of IPv4 or IPv6 addresses for use as redundant (backup) sources for multicast flows defined by a flow map. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Defining Flow Properties reference-bandwidth Syntax Hierarchy Level Release Information Description reference-bandwidth reference-bandwidth; [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the reference bandwidth used in calculating the default interface cost. The cost is calculated using the following formula: cost = reference-bandwidth/bandwidth Options reference-bandwidth—Reference bandwidth, in megabits per second. Default: 10 Mbps Range: 9600 through 1,000,000,000,000 Mbps Required Privilege Level Related Documentation 1676 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the Reference Bandwidth Used in IS-IS Metric Calculations Chapter 73: Configuration Statements for Layer 3 Protocols reference-bandwidth Syntax Hierarchy Level Release Information Description reference-bandwidth reference-bandwidth; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the reference bandwidth used in calculating the default interface cost. The cost is calculated using the following formula: cost = ref-bandwidth/bandwidth Options ref-bandwidth—Reference bandwidth, in bits per second. Default: 100 Mbps (100,000,000 bits) Range: 9600 through 1,000,000,000,000 bits NOTE: The default behavior is to use the reference-bandwidth value to calculate the cost of OSPF interfaces. You can override this behavior for any OSPF interface by configuring a specific cost with the metric statement. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • metric on page 1611 • Configuring the Metric Value for OSPF Interfaces 1677 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS remove-private Syntax Hierarchy Level Release Information Description remove-private; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. When advertising AS paths to remote systems, have the local system strip private AS numbers from the AS path. The numbers are stripped from the AS path starting at the left end of the AS path (the end where AS paths have been most recently added). The routing device stops searching for private ASs when it finds the first nonprivate AS or a peer’s private AS. This operation takes place after any confederation member ASs have already been removed from the AS path, if applicable. The Junos OS recognizes the set of AS numbers that is considered private, a range that is defined in the Internet Assigned Numbers Authority (IANA) assigned numbers document. The set of reserved AS numbers is in the range from 64,512 through 65,535. Required Privilege Level Related Documentation 1678 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Removing Private AS Numbers from AS Paths Chapter 73: Configuration Statements for Layer 3 Protocols resolution Syntax Hierarchy Level Release Information Description resolution { rib routing-table-name { import [ policy-names ]; resolution-ribs [ routing-table-names ]; } } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure route resolution. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Resolution resolution-ribs Syntax Hierarchy Level Release Information Description resolution-ribs [ routing-table-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options resolution rib], [edit logical-systems logical-system-name routing-options resolution rib], [edit routing-instances routing-instance-name routing-options resolution rib], [edit routing-options resolution rib] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify one or more routing tables to use for route resolution. The remaining statements are explained separately. Options Required Privilege Level Related Documentation routing-table-names—Name of one or more routing tables. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Resolution 1679 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS resolve Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1680 resolve; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-options static (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit routing-instances routing-instance-name routing-options static (defaults | route)], [edit routing-options rib routing-table-name static (defaults | route)], [edit routing-options static (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure statically configured routes to be resolved to a next hop that is not directly connected. The route is resolved through the inet.0 and inet.3 routing tables. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • static on page 1708 • Configuring Static Route Options Chapter 73: Configuration Statements for Layer 3 Protocols restart-duration Syntax Hierarchy Level Release Information Description Options restart-duration seconds; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options graceful-restart], [edit logical-systems logical-system-name routing-options graceful-restart], [edit routing-instances routing-instance-name routing-options graceful-restart], [edit routing-options graceful-restart] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the restart timer for graceful restart. restart-duration seconds—Configure the time period for the restart to last. Range: 120 through 900 seconds Default: 90 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Graceful Restart 1681 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS retain Syntax Hierarchy Level Release Information Description (retain | no-retain); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name static (defaults | route)], [edit logical-systems logical-system-name routing-options static (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name static (defaults | route)], [edit routing-instances routing-instance-name routing-options static (defaults | route)], [edit routing-options rib routing-table-name static (defaults | route)], [edit routing-options static (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure statically configured routes to be deleted from or retained in the forwarding table when the routing protocol process shuts down normally: • retain—Have a static route remain in the forwarding table when the routing protocol process shuts down normally. Doing this greatly reduces the time required to restart a system that has a large number of routes in its routing table. • no-retain—Delete statically configured routes from the forwarding table when the routing protocol process shuts down normally. Default Required Privilege Level Related Documentation 1682 no-retain routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • static on page 1708 • Configuring Static Routes Chapter 73: Configuration Statements for Layer 3 Protocols retransmit-interval Syntax Hierarchy Level Release Information Description Options retransmit-interval seconds; [edit logical-systems logical-system-name protocols ospf area area-id peer-interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols ospf area area-id peer-interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id virtual-link], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id virtual-link], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long the routing device waits to receive a link-state acknowledgment packet before retransmitting link-state advertisements to an interface’s neighbors. seconds—Interval to wait. Range: 1 through 65,535 seconds Default: 5 seconds NOTE: You must configure link-state advertisement (LSA) retransmit intervals to be equal to or greater than 3 seconds to avoid triggering a retransmit trap, because the Junos OS delays LSA acknowledgments by up to 2 seconds. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Timers 1683 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS reverse-oif-mapping Syntax Hierarchy Level Release Information Description reverse-oif-mapping { no-qos-adjust; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast interface interface-name], [edit logical-systems logical-system-name routing-options multicast interface interface-name], [edit routing-instances routing-instance-name routing-options multicast interface interface-name], [edit routing-options multicast interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the routing device to identify a subscriber VLAN or interface based on an IGMP or MLD request it receives over the multicast VLAN. The remaining statement is explained separately. Required Privilege Level Related Documentation 1684 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Managing Subscriber Overcommitment Chapter 73: Configuration Statements for Layer 3 Protocols rib (General) Syntax Hierarchy Level Release Information Description rib routing-table-name { aggregate { defaults { ... aggregate-options ... } route destination-prefix { policy policy-name; ... aggregate-options ... } generate { defaults { generate-options; } route destination-prefix { policy policy-name; generate-options; } } martians { destination-prefix match-type ; } } static { defaults { static-options; } rib-group group-name; route destination-prefix { next-hop; static-options; } } } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Create a routing table. Explicitly creating a routing table with the routing-table-name statement is optional if you are not adding any static, martian, aggregate, or generated routes to the routing table and if you also are creating a routing table group. Simply including the passive statement to indicate that a routing table is part of a routing table group is sufficient to create it. 1685 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: The IPv4 multicast routing table (inet.1) and the IPv6 multicast routing table (inet6.1) are not supported for this statement. Default Options If you do not specify a routing table name with the routing-table-name statement, the software uses the default routing tables, which are inet.0 for unicast routes and inet.1 for the multicast cache. routing-table-name—Name of the routing table, in the following format: protocol [.identifier] • protocol is the protocol family. It can be inet6 for the IPv6 family, inet for the IPv4 family, iso for the ISO protocol family, or instance-name.iso.0 for an ISO routing instance. • identifier is a positive integer that specifies the instance of the routing table. Default: inet.0 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • passive • Creating Routing Tables rib (Route Resolution) Syntax Hierarchy Level Release Information Description rib routing-table-name { import [ policy-names ]; resolution-ribs [ routing-table-names ]; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options resolution], [edit logical-systems logical-system-name routing-options resolution], [edit routing-instances routing-instance-name routing-options resolution], [edit routing-options resolution] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a routing table name for route resolution. The remaining statements are explained separately. Required Privilege Level Related Documentation 1686 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Resolution Chapter 73: Configuration Statements for Layer 3 Protocols rib-group Syntax Hierarchy Level Release Information Description Options rib-group group-name; [edit logical-systems logical-system-name protocols bgp family inet (any | labeled-unicast | unicast | multicast)], [edit logical-systems logical-system-name protocols bgp group group-name family inet (any | labeled-unicast | unicast | multicast)], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address family inet (any | labeled-unicast | unicast | multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp family inet (any | labeled-unicast | unicast | multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name family inet (any | labeled-unicast | unicast | multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address family inet (any | labeled-unicast | unicast | multicast)], [edit protocols bgp family inet (any | labeled-unicast | unicast | multicast)], [edit protocols bgp group group-name family inet (any | labeled-unicast | unicast | multicast)], [edit protocols bgp group group-name neighbor address family inet (any | labeled-unicast | unicast | multicast)], [edit routing-instances routing-instance-name protocols bgp family inet (any | labeled-unicast | unicast | multicast)], [edit routing-instances routing-instance-name protocols bgp group group-name family inet (any | labeled-unicast | unicast | multicast)], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family inet (any | labeled-unicast | unicast | multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Add unicast prefixes to unicast and multicast tables. group-name—Name of the routing table group. The name must start with a letter and can include letters, numbers, and hyphens. You generally specify only one routing table group. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • interface-routes on page 1585 • rib-group on page 1691 • Creating Routing Table Groups • Configuring How Interface Routes Are Imported into Routing Tables • Enabling Multiprotocol BGP 1687 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rib-group Syntax Hierarchy Level Release Information Description rib-group { inet group-name; inet6 group-name; } [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Install routes learned from IS-IS routing instances into routing tables in the IS-IS routing table group. You can install IPv4 routes or IPv6 routes. Support for IPv6 routing table groups in IS-IS enables IPv6 routes that are learned from IS-IS routing instances to be installed into other routing tables defined in an IS-IS routing table group. Options group-name—Name of the routing table group. inet—Install IPv4 IS-IS routes. inet6—Install IPv6 IS-IS routes. Required Privilege Level Related Documentation 1688 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Creating Routing Table Groups • Configuring How Interface Routes Are Imported into Routing Tables • Enabling Multiprotocol BGP Chapter 73: Configuration Statements for Layer 3 Protocols rib-group Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation rib-group group-name; [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Install routes learned from OSPF routing instances into routing tables in the OSPF routing table group. group-name—Name of the routing table group. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • interface-routes on page 1585 • rib-group on page 1691 • Creating Routing Table Groups • Configuring How Interface Routes Are Imported into Routing Tables • Enabling Multiprotocol BGP 1689 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rib-group Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1690 rib-group group-name; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit protocols rip], [edit routing-instances routing-instance-name protocols rip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Install RIP routes into multiple routing tables by configuring a routing table group. group-name—Name of the routing table group. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Routing Table Groups for RIP Chapter 73: Configuration Statements for Layer 3 Protocols rib-group Syntax Hierarchy Level Release Information Description Options rib-group group-name; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options interface-routes], [edit logical-systems logical-system-name routing-options interface-routes], [edit logical-systems logical-system-name routing-options rib routing-table-name static], [edit logical-systems logical-system-name routing-options static], [edit routing-instances routing-instance-name routing-options interface-routes], [edit routing-options interface-routes], [edit routing-options rib routing-table-name static], [edit routing-options static] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure which routing table groups interface routes are imported into. group-name—Name of the routing table group. The name must start with a letter and can include letters, numbers, and hyphens. It generally does not make sense to specify more than a single routing table group. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • interface-routes on page 1585 • rib-groups on page 1692 • Configuring How Interface Routes Are Imported into Routing Tables • Creating Routing Table Groups 1691 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rib-groups Syntax Hierarchy Level Release Information Description rib-groups { group-name { export-rib group-name; import-policy [ policy-names ]; import-rib [ group-names ]; } } [edit logical-systems logical-system-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Group one or more routing tables to form a routing table group. A routing protocol can import routes into all the routing tables in the group and can export routes from a single routing table. Each routing table group must contain one or more routing tables that the Junos OS uses when importing routes (specified in the import-rib statement) and optionally can contain one routing table group that the Junos OS uses when exporting routes to the routing protocols (specified in the export-rib statement). Options group-name—Name of the routing table group. The name must start with a letter and can include letters, numbers, and hyphens. The remaining statements are explained separately. Required Privilege Level Related Documentation 1692 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • rib-group on page 1691 • Creating Routing Table Groups Chapter 73: Configuration Statements for Layer 3 Protocols rip Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation rip {...} [edit logical-systems logical-system-name protocols], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable RIP routing on the routing device. RIP is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum RIP Configuration ripng Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation ripng {...} [edit logical-systems logical-system-name protocols], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable RIPng routing on the routing device. RIPng is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Minimum RIPng Configuration 1693 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS route-distinguisher-id Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation route-distinguisher-id address; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a route distinguisher identifier for a routing instance, specifying an IP address. If a route distinguisher is configured for a particular routing instance, that value supersedes the route distinguisher configured by this statement. address—IP address. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Distinguishers for VRF and Layer 2 VPN Instances route-record Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1694 route-record; [edit logical-systems logical-system-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Export the AS path and routing information to the traffic sampling process. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Route Recording for Flow Aggregation • Junos OS Network Interfaces Configuration Guide Chapter 73: Configuration Statements for Layer 3 Protocols route-timeout Syntax Hierarchy Level Release Information Description Options route-timeout seconds; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name], [edit protocols rip], [edit protocols rip group group-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the route timeout interval for RIP. seconds—Estimated time to wait before making updates to the routing table. Range: 30 through 360 seconds Default: 180 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RIP Timers 1695 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS route-timeout Syntax Hierarchy Level Release Information Description Options route-timeout seconds; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit protocols ripng], [edit routing-instances routing-instance-name protocols ripng] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the route timeout interval for RIPng. seconds—Estimated time to wait before making updates to the routing table. Range: 30 through 360 seconds Default: 180 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RIPng Timers route-type-community Syntax Hierarchy Level Release Information Description Options route-type-community (iana | vendor); [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify an extended community value to encode the OSPF route type. Each extended community is coded as an eight-octet value. This statement sets the most significant bit to either an IANA or vendor-specific route type. iana—Encode a route type with the value 0x0306. This is the default value. vendor—Encode the route type with the value 0x8000. Required Privilege Level Related Documentation 1696 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Domain IDs for VPNs Chapter 73: Configuration Statements for Layer 3 Protocols router-id Syntax Hierarchy Level Release Information Description router-id address; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the routing device’s IP address. NOTE: We strongly recommend that you configure the router identifier under the [edit routing-options] hierarchy level to avoid unpredictable behavior if the interface address on a loopback interface changes. Options address—IP address of the routing device. Default: Address of the first interface encountered by the Junos OS Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Router Identifiers for BGP and OSPF routing-options Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation routing-options { ... } [edit], [edit logical-systems logical-system-name], [edit logical-systems logical-system-name routing-instances routing-instance-name], [edit routing-instances routing-instance-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure protocol-independent routing properties. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Protocol-Independent Routing Properties Configuration Statements 1697 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rpf-check-policy Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation rpf-check-policy [ policy-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply policies for disabling RPF checks on arriving multicast packets. The policies must be correctly configured. policy-names—Name of one or more multicast RPF check policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RPF Policies scope Syntax Hierarchy Level Release Information Description Options scope scope-name { interface [ interface-names ]; prefix destination-prefix; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure multicast scoping. scope-name—Name of the multicast scope. The remaining statements are explained separately. Required Privilege Level Related Documentation 1698 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Creating a Named Scope for Multicast Scoping Chapter 73: Configuration Statements for Layer 3 Protocols scope-policy Syntax Hierarchy Level scope-policy [ policy-names ]; [edit logical-systems logical-system-name routing-options multicast], [edit routing-options multicast] NOTE: You can configure a scope policy at these two hierarchy levels only. You cannot apply a scope policy to a specific routing instance, because all scoping policies are applied to all routing instances. However, you can apply the scope statement to a specific routing instance at the [edit routing-instances routing-instance-name routing-options multicast] or [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast] hierarchy level. Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Apply policies for scoping. The policy must be correctly configured at the edit policy-options policy-statement hierarchy level. Options Required Privilege Level Related Documentation policy-names—Name of one or more multicast scope policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • scope on page 1698 • Using a Scope Policy for Multicast Scoping 1699 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS send Syntax Hierarchy Level Release Information Description Options send send-options; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name], [edit protocols rip], [edit protocols rip group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols rip], [edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RIP send options. send-options—One of the following: • broadcast—Broadcast RIP version 2 packets (RIP version 1 compatible). • multicast—Multicast RIP version 2 packets. This is the default. • none—Do not send RIP updates. • version-1—Broadcast RIP version 1 packets. Default: multicast Required Privilege Level Related Documentation 1700 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • receive on page 1674 • Configuring RIP Update Messages Chapter 73: Configuration Statements for Layer 3 Protocols send Syntax Hierarchy Level Release Information Description Options send ; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instances-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name], [edit protocols ripng], [edit protocols ripng group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols ripng], [edit routing-instances routing-instance-name protocols ripng group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable or disable sending of update messages. none—(Optional) Disable sending of update messages. Default: Enabled Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • receive on page 1675 • Configuring RIPng Update Messages 1701 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS shortcuts Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation shortcuts; lsp-metric-into-summary; } [edit logical-systems logical-system-name protocols (ospf | ospf3) traffic-engineering], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) traffic-engineering], [edit protocols (ospf | ospf3) traffic-engineering], [edit routing-instances routing-instance-name protocols (ospf | ospf3)traffic-engineering] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure OSPF to use MPLS label-switched paths (LSPs) as shortcut next hops. By default, shortcut routes calculated through OSPFv2 are installed in theinet.3 routing table, and shortcut routes calculated through OSPFv3 are installed in the inet6.3 routing table. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling OSPF Traffic Engineering Support source Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1702 source [ addresses ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast ssm-map ssm-map-name], [edit logical-systems logical-system-name routing-options multicast ssm-map ssm-map-name], [edit routing-instances routing-instance-name routing-options multicast ssm-map ssm-map-name], [edit routing-options multicast ssm-map ssm-map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify IPv4 or IPv6 source addresses for an SSM map. addresses—IPv4 or IPv6 source addresses. routing—To view this statement in the configuration. routing-control—To view this statement in the configuration. • Example: Configuring SSM Mapping Chapter 73: Configuration Statements for Layer 3 Protocols source-routing Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation source-routing { (ip | ipv6) } [edit routing-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable source routing. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling Source Routing 1703 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS spf-options Syntax Hierarchy Level Release Information spf-options { delay milliseconds; holddown milliseconds; rapid-runs number; } [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure options for running the shortest-path-first (SPF) algorithm. You can configure a delay for when to run the SPF algorithm after a network topology change is detected, the maximum number of times the SPF algorithm can run in succession, and a holddown interval after SPF algorithm runs the maximum number of times. Options delay milliseconds—Time interval between the detection of a topology change and when the SPF algorithm runs. Range: 50 through 1000 milliseconds Default: 200 milliseconds holddown milliseconds—Time interval to hold down, or wait before a subsequent SPF algorithm runs after the SPF algorithm has run the configured maximum number of times in succession. Range: 2000 through 10,000 milliseconds Default: 5000 milliseconds rapid-runs number—Maximum number of times the SPF algorithm can run in succession. After the maximum is reached, the holddown interval begins. Range: 1 through 5 Default: 3 Required Privilege Level Related Documentation 1704 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring SPF Options for IS-IS Chapter 73: Configuration Statements for Layer 3 Protocols spf-options Syntax Hierarchy Level Release Information spf-options { delay milliseconds; holddown milliseconds; rapid-runs number; } [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast | name)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf topology (default | ipv4-multicast | name)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure options for running the shortest-path-first (SPF) algorithm. You can configure a delay for when to run the SPF algorithm after a network topology change is detected, the maximum number of times the SPF algorithm can run in succession, and a hold-down interval after the SPF algorithm runs the maximum number of times. Options delay milliseconds—Time interval between the detection of a topology change and when the SPF algorithm runs. Range: 50 through 8000 milliseconds Default: 200 milliseconds holddown milliseconds—Time interval to hold down, or wait before a subsequent SPF algorithm runs after the SPF algorithm has run the configured maximum number of times in succession. Range: 2000 through 20,000 milliseconds Default: 5000 milliseconds rapid-runs number—Maximum number of times the SPF algorithm can run in succession. After the maximum is reached, the holddown interval begins. Range: 1 through 5 Default: 3 1705 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring SPF Options for OSPF • Configuring Multitopology Routing in OSPF ssm-groups Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 1706 ssm-groups [ ip-addresses ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure additional source-specific multicast (SSM) groups. ip-addresses—List of one or more additional SSM group addresses separated by a space. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Source-Specific Multicast Groups Chapter 73: Configuration Statements for Layer 3 Protocols ssm-map Syntax Hierarchy Level Release Information Description Options ssm-map ssm-map-name { policy [ policy-names ]; source [ addresses ]; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast], [edit logical-systems logical-system-name routing-options multicast], [edit routing-instances routing-instance-name routing-options multicast], [edit routing-options multicast] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure SSM mapping. ssm-map-name—Name of the SSM map. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring SSM Mapping 1707 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS static Syntax Hierarchy Level Release Information Description 1708 static { defaults { static-options; } rib-group group-name; route destination-prefix { bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } local-address ip-address; minimum-interval milliseconds; minimum-receive-interval milliseconds; minimum-receive-ttl number; multiplier number; neighbor address; no-adaptation; transmit-interval { threshold milliseconds; minimum-interval milliseconds; } version (1 | automatic); } next-hop address; next-hop options; qualified-next-hop address { metric metric; preference preference; } static-options; } } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit logical-systems logical-system-name routing-options rib routing-table-name], [edit routing-instances routing-instance-name routing-options], [edit routing-options], [edit routing-options rib routing-table-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure static routes to be installed in the routing table. You can specify any number of routes within a single static statement, and you can specify any number of static options in the configuration. Chapter 73: Configuration Statements for Layer 3 Protocols Options defaults—Specify global static route options. These options only set default attributes inherited by all newly created static routes. These are treated as global defaults and apply to all the static routes you configure in the static statement. This part of the static statement is optional. route destination-prefix—Destination of the static route. • defaults—For the default route to the destination. This is equivalent to specifying an IP address of 0.0.0.0/0. • destination-prefix/prefix-length—destination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length. • next-hop address—Reach the next-hop routing device by specifying an IP address, an interface name, or an ISO network entity title (NET). • nsap-prefix—nsap-prefix is the network service access point (NSAP) address for ISO. next-hop options—Additional information for how to manage forwarding of packets to the next hop. • discard—Do not forward packets addressed to this destination. Instead, drop the packets, do not send ICMP unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table. • iso-net—Reach the next-hop routing device by specifying an ISO NSAP. • next-table routing-table-name—Name of the next routing table to the destination. • receive—Install a receive route for this destination into the routing table. • reject—Do not forward packets addressed to this destination. Instead, drop the packets, send ICMP unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table. static-options—(Optional under route) Additional information about static routes, which is included with the route when it is installed in the routing table. You can specify one or more of the following in static-options. Each of the options is explained separately. • (active | passive); • as-path ; • community [ community-ids ]; • (install | no-install); • (metric | metric2 | metric3 | metric4) value ; • (preference | preference2 | color | color2) preference ; • (readvertise | no-readvertise); 1709 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • (resolve | no-resolve); • (no-retain | retain); • tag string; The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static Routes stub Syntax Hierarchy Level Release Information Description stub <(no-summaries | summaries)>; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3) area area-id], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify that this area not be flooded with AS external link-state advertisements (LSA)s. You must include the stub statement when configuring all routing devices that are in the stub area. The backbone cannot be configured as a stub area. You cannot configure an area to be both a stub area and a not-so-stubby area (NSSA). Options no-summaries—(Optional) Do not advertise routes into the stub area. If you include the default-metric option, only the default route is advertised. summaries—(Optional) Flood summary LSAs into the stub area. The remaining statement is explained separately. Required Privilege Level Related Documentation 1710 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • nssa on page 1642 • Configuring OSPF Areas Chapter 73: Configuration Statements for Layer 3 Protocols subscriber-leave-timer Syntax Hierarchy Level Release Information subscriber-leave-timer seconds; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast interface interface-name], [edit logical-systems logical-system-name routing-options multicast interface interface-name], [edit routing-instances routing-instance-name routing-options multicast interface interface-name], [edit routing-options multicast interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Length of time before the multicast VLAN updates QoS data (for example, available bandwidth) for subscriber interfaces after it receives an IGMP leave message. Options seconds—Length of time before the multicast VLAN updates QoS data (for example, available bandwidth) for subscriber interfaces after it receives an IGMP leave message. Specifying a value of 0 results in an immediate update; this is the same as if the statement were not configured. Range: 0 through 30 Default: 0 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Managing Subscriber Overcommitment 1711 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS summaries Syntax Hierarchy Level Release Information Description (summaries | no-summaries); [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa], [edit protocols (ospf | ospf3) area area-id nssa], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id nssa], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure whether or not area border routers advertise summary routes into an not-so-stubby area (NSSA): • summaries—Flood summary link-state advertisements (LSAs) into the NSSA. • no-summaries—Prevent area border routers from advertising summaries into an NSSA. If default-metric is configured for an NSSA, a Type 3 LSA is injected into the area by default. Required Privilege Level Related Documentation 1712 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • nssa on page 1642 • stub on page 1710 • Configuring OSPF Areas Chapter 73: Configuration Statements for Layer 3 Protocols tag Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation tag string; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options aggregate | generate | static) (defaults | route)], [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate an OSPF tag with a static, aggregate, or generated route. string—OSPF tag string. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • aggregate on page 1470 • generate on page 1543 • static on page 1708 • Configuring Static Routes • Configuring Aggregate Routes • Configuring Generated Routes 1713 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS tcp-mss Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 1714 tcp-mss segment-size; [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor neighbor-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor neighbor-name], [edit protocols bgp], [edit protocol bgp group group-name], [edit protocols bgp group group-name neighbor neighbor-name], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor neighbor-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the maximum segment size (MSS) for the TCP connection for BGP neighbors. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Limiting TCP Segment Size for BGP Chapter 73: Configuration Statements for Layer 3 Protocols threshold Syntax Hierarchy Level Release Information threshold suppress value ; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast forwarding-cache], [edit logical-systems logical-system-name routing-options multicast forwarding-cache], [edit routing-instances routing-instance-name routing-options multicast forwarding-cache], [edit routing-options multicast forwarding-cache] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the suppression and reuse thresholds for multicast forwarding cache limits. Options reuse value—Value at which to begin creating new multicast forwarding cache entries. This value is optional. If configured, this number should be less than the suppress value. Range: 1 through 200,000 suppress value—Value at which to begin suppressing new multicast forwarding cache entries. This value is mandatory. This number should be greater than the reuse value. Range: 1 through 200,000 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Multicast Forwarding Cache Limits 1715 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS timeout (Flow Maps) Syntax Hierarchy Level Release Information Description Options timeout (never | minutes); [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name], [edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-name], [edit routing-options multicast flow-map flow-map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the timeout value for multicast forwarding cache entries associated with the flow map. minutes—Length of time that the forwarding cache entry remains active. Range: 1 through 720 never—Specify that the forwarding cache entry always remain active. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. timeout (Multicast) Syntax Hierarchy Level Release Information Description Options timeout minutes; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast forwarding-cache], [edit logical-systems logical-system-name routing-options multicast forwarding-cache], [edit routing-instances routing-instance-name routing-options multicast forwarding-cache], [edit routing-options multicast forwarding-cache] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the timeout value for multicast forwarding cache entries. minutes—Length of time that the forwarding cache limit remains active. Range: 1 through 720 Required Privilege Level Related Documentation 1716 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring General Multicast Forwarding Cache Properties Chapter 73: Configuration Statements for Layer 3 Protocols topologies Syntax Hierarchy Level Release Information Description topologies { ipv4-multicast; ipv6-multicast; ipv6-unicast; } [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure alternate IS-IS topologies. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IS-IS Multicast Topologies 1717 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions (BGP) Syntax Hierarchy Level Release Information traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address], [edit routing-instances routing-instance-name protocols bgp], [edit routing-instances routing-instance-name protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure BGP protocol-level tracing options. To specify more than one tracing operation, include multiple flag statements. Default The default BGP protocol-level tracing options are inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level. The default group-level trace options are inherited from the BGP protocol-level traceoptions statement. The default peer-level trace options are inherited from the group-level traceoptions statement. Options disable—(Optional) Disable the tracing operation. You can use this option is to disable a single operation when you have defined a broad group of tracing operations, such as all. file name—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place BGP tracing output in the file bgp-log. 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. Range: 2 through 1000 files Default: 10 files 1718 Chapter 73: Configuration Statements for Layer 3 Protocols flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. BGP Tracing Flags • 4byte-as—4-byte AS events • bfd—BFD protocol events • damping—Damping operations • graceful-restart—Graceful restart events • keepalive—BGP keepalive messages. If you enable the the BGP update flag only, received keepalive messages do not generate a trace message. • nsr-synchronization—Nonstop routing synchronization events • open—Open packets. These packets are sent between peers when they are establishing a connection. • packets—All BGP protocol packets • refresh—BGP refresh packets • update—Update packets. These packets provide routing updates to BGP systems. If you enable only this flag, received keepalive messages do not generate a trace message. Use the keepalive flag to generate a trace message for keepalive messages. Global Tracing Flags • all—All tracing operations • general—A combination of the normal and route trace operations • normal—All normal operations Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions • route—Routing table changes • state—State transitions • task—Routing protocol task processing • timer—Routing protocol timer processing flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: • detail—Provide detailed trace information • filter—Filter trace information. Applies only to route and damping tracing flags. • receive—Packets being received. • send—Packets being transmitted. 1719 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-world-readable—(Optional) Prevent any user from reading the log file. 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. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 128 KB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level Related Documentation 1720 routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • log-updown on page 1600 statement • Tracing BGP Protocol Traffic • Configuring OSPF Refresh and Flooding Reduction in Stable Topologies Chapter 73: Configuration Statements for Layer 3 Protocols traceoptions (IS-IS) Syntax Hierarchy Level Release Information Description traceoptions { file name ; flag flag ; } [edit logical-systems logical-system-name protocols isis], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis], [edit protocols isis], [edit routing-instances routing-instance-name protocols isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure IS-IS protocol-level tracing options. To specify more than one tracing operation, include multiple flag statements. Default The default IS-IS protocol-level tracing options are those inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level. Options disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all. file name—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks (“ ”). All files are placed in the directory /var/log. We recommend that you place IS-IS tracing output in the file isis-log. 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 also must specify a maximum file size with the size option. Range: 2 through 1000 files Default: 10 files flag flag—Tracing operation to perform. To specify more than one flag, include multiple flag statements. IS-IS Protocol-Specific Tracing Flags • csn—Complete sequence number PDU (CSNP) packets • error—Errored IS-IS packets • graceful-restart—Graceful restart operation • hello—Hello packets 1721 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • ldp-synchronization—Synchronization between IS-IS and LDP • lsp—Link-state PDU packets • lsp-generation—Link-state PDU generation packets • packets—All IS-IS protocol packets • psn—Partial sequence number PDU (PSNP) packets • spf—Shortest-path-first calculations Global Tracing Flags • all—All tracing operations • general—A combination of the normal and route trace operations • normal—All normal operations, including adjacency changes Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions • route—Routing table changes • state—State transitions • task—Routing protocol task processing • timer—Routing protocol timer processing flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: • detail—Detailed trace information • receive—Packets being received • send—Packets being transmitted no-world-readable—(Optional) Prevent any user from reading the log file. 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. Note that if you specify a maximum file size, you also must specify a maximum number of trace files with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 128 KB world-readable—(Optional) Allow any user to read the log file. 1722 Chapter 73: Configuration Statements for Layer 3 Protocols Required Privilege Level Related Documentation routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • Tracing IS-IS Protocol Traffic 1723 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions (OSPF) Syntax Hierarchy Level Release Information Description traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure OSPF protocol-level tracing options. To specify more than one tracing operation, include multiple flag statements. Default The default OSPF protocol-level tracing options are those inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level. Options disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place OSPF tracing output in the file ospf-log. 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 also must specify a maximum file size with the size option. Range: 2 through 1000 files Default: 10 files flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. OSPF Tracing Flags 1724 Chapter 73: Configuration Statements for Layer 3 Protocols • database-description—Database description packets, which are used in synchronizing the OSPF and OSPFv3 topological database. • error—OSPF and OSPFv3 error packets. • event—OSPF and OSPFv3 state transitions. • flooding—Link-state flooding packets. • graceful-restart—Graceful-restart events. • hello—Hello packets, which are used to establish neighbor adjacencies and to determine whether neighbors are reachable. • ldp-synchronization—Synchronization events between OSPF and LDP • lsa-ack—Link-state acknowledgment packets, which are used in synchronizing the OSPF topological database. • lsa-analysis—Link-state analysis packets • lsa-request—Link-state request packets, which are used in synchronizing the OSPF topological database. • lsa-update—Link-state updates packets, which are used in synchronizing the OSPF topological database. • nsr-synchronization—Nonstop routing synchronization events. • on-demand—Trace demand circuit extensions. • packet-dump—Content of selected packet types. • packets—All OSPF packets. • spf—Shortest-path-first (SPF) calculations. Global Tracing Flags • all—All tracing operations. • general—A combination of the normal and route trace operations. • normal—All normal operations. Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions. • route—Routing table changes. • state—State transitions. • task—Routing protocol task processing. • timer—Routing protocol timer processing. flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: 1725 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • detail—Provide detailed trace information. • receive—Packets being received. • send—Packets being transmitted. no-world-readable—(Optional) Prevent any user from reading the log file. 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. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 128 KB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level Related Documentation 1726 routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • Tracing OSPF Protocol Traffic Chapter 73: Configuration Statements for Layer 3 Protocols traceoptions (RIP) Syntax Hierarchy Level Release Information Description traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit protocols rip], [edit routing-instances routing-instance-name protocols rip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set RIP protocol-level tracing options. Default The default RIP protocol-level trace options are inherited from the global traceoptions statement. Options disable—(Optional) Disable the tracing operation. One use of this option is to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename—Name of the file to receive the output of the tracing operation. Enclose the name in quotation marks. We recommend that you place RIP tracing output in the file /var/log/rip-log. 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. Range: 2 through 1000 files Default: 10 files flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. RIP Tracing Options • auth—RIP authentication • error—RIP error packets • expiration—RIP route expiration processing • holddown—RIP hold-down processing • nsr-synchronization—Nonstop routing synchronization events • packets—All RIP packets 1727 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • request—RIP information packets such as request, poll, and poll entry packets • trigger—RIP triggered updates • update—RIP update packets Global Tracing Options • all—All tracing operations • general—A combination of the normal and route trace operations • normal—All normal operations Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions • route—Routing table changes • state—State transitions • task—Routing protocol task processing • timer—Routing protocol timer processing flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: • detail—Provide detailed trace information • receive—Packets being received • receive-detail—Provide detailed trace information for packets being received • send—Packets being transmitted • send-detail—Provide detailed trace information for packets being transmitted no-world-readable—(Optional) Prevent any user from reading the log file. size size—(Optional) Maximum size of each trace file, in kilobytes (KB) or megabytes (MB). 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 must also specify a maximum number of trace files with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 128 KB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level 1728 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 73: Configuration Statements for Layer 3 Protocols Related Documentation • Tracing RIP Protocol Traffic 1729 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions (RIPng) Syntax Hierarchy Level Release Information Description traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit protocols ripng], [edit routing-instances routing-instance-name protocols ripng] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set RIPng protocol-level tracing options. Default The default RIPng protocol-level trace options are inherited from the global traceoptions statement. Options disable—(Optional) Disable the tracing operation. One use of this option is to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename—Name of the file to receive the output of the tracing operation. Enclose the name in quotation marks. We recommend that you place RIPng tracing output in the file /var/log/ripng-log. 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. Range: 2 through 1000 files Default: 10 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. RIPng Tracing Options 1730 • error—RIPng error packets • expiration—RIPng route expiration processing • holddown—RIPng hold-down processing • nsr-synchronization—Nonstop routing synchronization events • packets—All RIPng packets • request—RIPng information packets such as request, poll, and poll entry packets Chapter 73: Configuration Statements for Layer 3 Protocols • trigger—RIPng triggered updates • update—RIPng update packets Global Tracing Options • all—All tracing operations • general—A combination of the normal and route trace operations • normal—All normal operations Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions • route—Routing table changes • state—State transitions • task—Routing protocol task processing • timer—Routing protocol timer processing flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: • detail—Provide detailed trace information • receive—Packets being received • receive-detail—Provide detailed trace information for packets being received • send—Packets being transmitted • send-detail—Provide detailed trace information for packets being transmitted no-world-readable—(Optional) Do not allow any user to read the log file. 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 must also specify a maximum number of trace files with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 128 KB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 1731 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation 1732 • Tracing RIPng Protocol Traffic Chapter 73: Configuration Statements for Layer 3 Protocols traceoptions (All Routing Protocols) Syntax Hierarchy Level Release Information Description traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options], [edit routing-options flow] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations that track all routing protocol functionality in the routing device. To specify more than one tracing operation, include multiple flag statements. Default If you do not include this statement, no global tracing operations are performed. Options Values: disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place global routing protocol tracing output in the file routing-log. 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. Note that if you specify a maximum number of files, you also must specify a maximum file size with the size option. Range: 2 through 1000 files Default: 10 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. These are the global routing protocol tracing options: • all—All tracing operations • condition-manager—Condition-manager events • config-internal—Configuration internals 1733 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • general—All normal operations and routing table changes (a combination of the normal and route trace operations) • graceful-restart—Graceful restart operations • normal—All normal operations • nsr-synchronization—Nonstop active routing synchronization • parse—Configuration parsing • policy—Routing policy operations and actions • regex-parse—Regular-expression parsing • route—Routing table changes • state—State transitions • task—Interface transactions and processing • timer—Timer usage no-world-readable—(Optional) Prevent any user from reading the log file. 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. Note that if you specify a maximum file size, you also must specify a maximum number of trace files with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 128 KB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level Related Documentation 1734 routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • Tracing Global Routing Protocol Operations Chapter 73: Configuration Statements for Layer 3 Protocols traffic-engineering (OSPF) Syntax Hierarchy Level Release Information Description Default Options traffic-engineering { ; ; ignore-lsp-metrics; multicast-rpf-routes; no-topology; shortcuts { lsp-metric-into-summary; } } [edit logical-systems logical-system-name protocols (ospf | ospf3)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)], [edit protocols (ospf | ospf3)], [edit routing-instances routing-instance-name protocols (ospf | ospf3)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the OSPF traffic engineering features. Traffic engineering support is disabled. advertise-unnumbered-interfaces—(Optional) (OSPFv2 only) Include the link-local identifier in the link-local traffic-engineering link-state advertisement. You do not need to include this statement if RSVP is able to signal unnumbered interfaces as defined in RFC 3477. credibility-protocol-preference—(Optional) (OSPFv2 only) Specify to use the configured preference value for OSPF routes to calculate the traffic engineering database credibility value used to select IGP routes. Use this statement to override the default behavior of having the traffic engineering database prefer IS-IS routes even if OSPF routes are configured a with a lower, that is, preferred, preference value. multicast-rpf-routes—(Optional) (OSPFv2 only) Install routes for multicast RPF checks into the inet.2 routing table. no-topology—(Optional) (OSPFv2 only) Disable the dissemination of the link-state topology information. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling OSPF Traffic Engineering Support 1735 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS transit-delay Syntax Hierarchy Level Release Information Description transit-delay seconds; [edit logical-systems logical-system-name protocols ospf area area-id peer-interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id virtual-link], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf area area-id virtual-link], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name], [edit protocols ospf area area-id peer-interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id virtual-link], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)] area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf area area-id virtual-link], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the estimated time required to transmit a link-state update on the interface. When calculating this time, make sure to account for transmission and propagation delays. You should never have to modify the transit delay time. Options seconds—Estimated time, in seconds. Range: 1 through 65,535 seconds Default: 1 second Required Privilege Level Related Documentation 1736 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Timers Chapter 73: Configuration Statements for Layer 3 Protocols type Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation type type; [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit protocols bgp group group-name], [edit routing-instances routing-instance-name protocols bgp group group-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the type of BGP peer group. type—Type of group: • external—External group • internal—Internal group routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring BGP Groups and Peers 1737 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS type-7 Syntax Hierarchy Level Release Information Description type-7; [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit protocols (ospf | ospf3) area area-id nssa default-lsa], [edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id nssa default-lsa], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id nssa default-lsa] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Flood Type 7 default link-state advertisements (LSAs) if the no-summaries statement is configured. By default, when the no-summaries statement is configured, a Type 3 LSA is injected into not-so-stubby areas (NSSAs). This statement enables NSSA ABRs to advertise a Type 7 default LSA into the NSSA if you have also included the no-summaries statement in the configuration. Required Privilege Level Related Documentation 1738 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Areas Chapter 73: Configuration Statements for Layer 3 Protocols update-interval Syntax Hierarchy Level Release Information Description Options update-interval seconds; [edit logical-systems logical-system-name protocols rip], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip], [edit protocols rip], [edit routing-instances routing-instance-name protocols rip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an update time interval to periodically send out routes learned by RIP to neighbors. seconds—Estimated time to wait before making updates to the routing table. Range: 10 through 60 seconds Default: 30 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RIP Timers update-interval Syntax Hierarchy Level Release Information Description Options update-interval seconds; [edit logical-systems logical-system-name protocols ripng], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ripng], [edit protocols ripng], [edit routing-instances routing-instance-name protocols ripng] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an update time interval to periodically send out routes learned by RIP to neighbors. seconds—Estimated time to wait before making updates to the routing table. Range: 10 through 60 seconds Default: 30 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring RIP Timers 1739 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS upstream-interface Syntax Hierarchy Level Release Information Description Options upstream-interface [ interface-names ]; [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast pim-to-igmp-proxy], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast pim-to-mld-proxy], [edit logical-systems logical-system-name routing-options multicast pim-to-igmp-proxy], [edit logical-systems logical-system-name routing-options multicast pim-to-mld-proxy], [edit routing-instances routing-instance-name routing-options multicast pim-to-igmp-proxy], [edit routing-instances routing-instance-name routing-options multicast pim-to-mld-proxy], [edit routing-options multicast pim-to-igmp-proxy], [edit routing-options multicast pim-to-mld-proxy] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure at least one, but not more than two, upstream interfaces on the rendezvous point (RP) routing device that resides between a customer edge–facing Protocol Independent Multicast (PIM) domain and a core-facing PIM domain. The RP routing device translates PIM join or prune messages into corresponding IGMP report or leave messages (if you include the pim-to-igmp-proxy statement), or into corresponding MLD report or leave messages (if you include the pim-to-mld-proxy statement). The routing device then proxies the IGMP or MLD report or leave messages to one or both upstream interfaces to forward IPv4 multicast traffic (for IGMP) or IPv6 multicast traffic (for MLD) across the PIM domains. interface-names—Names of one or two upstream interfaces to which the RP routing device proxies IGMP or MLD report or leave messages for transmission of multicast traffic across PIM domains. You can specify a maximum of two upstream interfaces on the RP routing device. To configure a set of two upstream interfaces, specify the full interface names, including all physical and logical address components, within square brackets ( [ ] ). For details about specifying interfaces, see the Junos OS Network Interfaces Configuration Guide. Required Privilege Level Related Documentation 1740 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM-to-IGMP Message Translation • Configuring PIM-to-MLD Message Translation Chapter 73: Configuration Statements for Layer 3 Protocols virtual-inet6-address Syntax Hierarchy Level Release Information Description virtual-inet6-address [addresses]; [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the addresses of the virtual routers in a Virtual Router Redundancy Protocol (VRRP) IPv6 group. You can configure up to eight addresses. NOTE: The address of an aggregated Ethernet interface (a LAG) or a routed VLAN interface (RVI) cannot be assigned as the virtual router address in a VRRP IPv6 group. Options addresses—Addresses of one or more virtual routers. Do not include a prefix length. If the address is the same as the interface’s physical address, the interface becomes the master virtual router for the group. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 1741 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS virtual-link Syntax Hierarchy Level Release Information Description Options virtual-link neighbor-id router-id transit-area area-id { disable; authentication key ; dead-interval seconds; hello-interval seconds; ipsec-sa name; retransmit-interval seconds; transit-delay seconds; } [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf area area-id], [edit protocols (ospf | ospf3) area area-id], [edit routing-instances routing-instance-name protocols ospf area area-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For backbone areas only, create a virtual link to use in place of an actual physical link. All area border routers and other routing devices on the backbone must be contiguous. If this is not possible and there is a break in OSPF connectivity, use virtual links to create connectivity to the OSPF backbone. When configuring virtual links, you must configure links on the two routing devices that form the end points of the link, and both these two routing devices must be area border routers. You cannot configure links through stub areas. neighbor-id router-id—IP address of the routing device at the remote end of the virtual link. transit-area area-id—Area identifier of the area through which the virtual link transits. Virtual links are not allowed to transit the backbone area. The remaining statements are explained separately. Required Privilege Level Related Documentation 1742 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring OSPF Areas Chapter 73: Configuration Statements for Layer 3 Protocols virtual-link-local-address Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation virtual-link-local-address ipv6-address; [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-group group-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a virtual link local address for a Virtual Router Redundancy Protocol (VRRP) IPv6 group. You must explicitly define a virtual link local address for each VRRP IPv6 group. The virtual link local address must be in the same subnet as the physical interface address. ipv6-address—Virtual link local IPv6 address for VRRP for an IPv6 group. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 1743 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vrrp-inet6-group Syntax Hierarchy Level Release Information Description Options vrrp-inet6-group group-id { inet6-advertise-interval milliseconds; preempt{ hold-time seconds; } priority number; virtual-inet6-address; virtual-link-local-address } [edit interfaces interface-name unit logical-unit-number family inet6 address address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a Virtual Router Redundancy Protocol (VRRP) IPv6 group. group-id—VRRP group identifier. If you enable MAC source address filtering on the interface, you must include the virtual MAC address in the list of source MAC addresses that you specify in the source-address-filter statement. MAC addresses ranging from 00:00:5e:00:01:00 through 00:00:5e:00:01:ff are reserved for VRRP, as defined in RFC 3768. The VRRP group number must be the decimal equivalent of the last hexadecimal byte of the virtual MAC address. Range: 0 through 255 The remaining statements are explained separately. Required Privilege Level Related Documentation 1744 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 Chapter 73: Configuration Statements for Layer 3 Protocols wide-metrics-only Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation wide-metrics-only; [edit logical-systems logical-system-name protocols isis level level-number], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis level level-number], [edit protocols isis level level-number], [edit routing-instances routing-instance-name protocols isis level level-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure IS-IS to generate metric values greater than 63 on a per IS-IS level basis. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • te-metric • Enabling Wide IS-IS Metrics for Traffic Engineering 1745 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1746 CHAPTER 74 Operational Commands for Layer 3 Protocols 1747 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear (ospf | ospf3) database Syntax Syntax (J-EX Series Switch) Release Information Description clear (ospf | ospf3) database clear (ospf | ospf3) database Command introduced before Junos OS Release 10.2 for J-EX Series switches. With the master Routing Engine, delete entries in the Open Shortest Path First (OSPF) link-state advertisement (LSA) database. With the backup Routing Engine, delete the OSPF LSA database and sync the new database with the master Routing Engine. You can also use the purge command with any of the options to discard rather than delete the specified LSA entries. CAUTION: This command is useful only for testing. Use it with care, because it causes significant network disruption. 1748 Chapter 74: Operational Commands for Layer 3 Protocols Options none—Delete all LSAs other than the system’s own LSAs, which are regenerated. To resynchronize the database, the system destroys all adjacent neighbors that are in the state EXSTART or higher. The neighbors are then reacquired and the databases are synchronized. advertising-router (router-id | self)—(Optional) Discard entries for the LSA entries advertised by the specified routing device or by this routing device. area area-id—(Optional) Discard entries for the LSAs in the specified area. asbrsummary—(Optional) Discard summary AS boundary router LSA entries. external—(Optional) Discard external LSAs. instance instance-name—(Optional) Delete or discard entries for the specified routing instance only. inter-area-prefix—(OSPFv3 only) (Optional) Discard interarea prefix LSAs. inter-area-router—(OSPFv3 only) (Optional) Discard interarea router LSAs. intra-area-prefix—(OSPFv3 only) (Optional) Discard intra-area prefix LSAs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. link-local—(Optional) Delete link-local LSAs. lsa-id lsa-id—(Optional) Discard the LSA entries with the specified LSA identifier. netsummary—(Optional) Discard summary network LSAs. network—(Optional) Discard network LSAs. nssa—(Optional) Discard not-so-stubby area (NSSA) LSAs. opaque-area—(Optional) Discard opaque area-scope LSAs. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(OSPFv3 only) (Optional) Delete the entries for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. router—(Optional) Discard router LSAs. purge—(Optional) Discard all entries in the link-state advertisement database. All link-state advertisements are set to MAXAGE and are flooded. The database is repopulated when the originators of the link-state advertisements receive the MAXAGE link-state advertisements and reissue them. Required Privilege Level Related Documentation clear • show ospf database on page 1878 1749 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • List of Sample Output Output Fields clear ospf database 1750 show ospf3 database on page 1868 clear ospf database on page 1750 When you enter this command, you are provided feedback on the status of your request. user@host> clear ospf database Chapter 74: Operational Commands for Layer 3 Protocols clear (ospf | ospf3) io-statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear (ospf | osfp3) statistics clear (ospf | osfp3) statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Open Shortest Path First (OSPF) input and output statistics. none—Clear OSPF input and output statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields clear ospf io-statistics clear clear ospf io-statistics on page 1751 When you enter this command, you are provided feedback on the status of your request. user@host> clear ospf io-statistics 1751 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear (ospf | ospf3) neighbor Syntax Syntax (J-EX Series Switch) Release Information Description Options clear (ospf | ospf3) neighbor clear (ospf | ospf3) neighbor Command introduced before Junos OS Release 10.2 for J-EX Series switches. Tear down Open Shortest Path First (OSPF) neighbor connections. none—Tear down OSPF connections with all neighbors for all routing instances. area area-id—(Optional) Tear down neighbor connections for the specified area only. instance instance-name—(Optional) Tear down neighbor connections for the specified routing instance only. interface interface-name—(Optional) Tear down neighbor connections for the specified interface only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. neighbor—(Optional) Clear the state of the specified neighbor only. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) (OSPFv3 only) Clear the state of the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ospf neighbor 1752 clear • show (ospf | ospf3) neighbor on page 1782 clear ospf neighbor on page 1752 When you enter this command, you are provided feedback on the status of your request. user@host> clear ospf neighbor Chapter 74: Operational Commands for Layer 3 Protocols clear (ospf | ospf3) statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear (ospf | osfp3) statistics clear (ospf | osfp3) statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Open Shortest Path First (OSPF) statistics. none—Clear OSPF statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) (OSPFv3 only) Clear statistics for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ospf statistics clear • show (ospf | ospf3) statistics on page 1796 clear ospf statistics on page 1753 See show (ospf | ospf3) statistics for an explanation of output fields. The following sample output displays OSPF statistics before and after the clear ospf statistics command is entered: user@host> show ospf statistics Packet type Hello DbD LSReq LSUpdate LSAck Total Sent 3254 41 8 212 65 Received 2268 46 7 154 98 Last 5 seconds Sent Received 3 1 0 0 0 0 0 0 0 0 LSAs retransmitted: 3, last 5 seconds: 0 Flood queue depth: 0 Total rexmit entries: 0, db summaries: 0, lsreq entries: 0 Receive errors: 626 subnet mismatches user@host> clear ospf statistics 1753 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@host> show ospf statistics Packet type Total Sent Received Hello 3 1 DbD 0 0 LSReq 0 0 LSUpdate 0 0 LSAck 0 0 Last 5 seconds Sent Received 3 1 0 0 0 0 0 0 0 0 LSAs retransmitted: 0, last 5 seconds: 0 Flood queue depth: 0 Total rexmit entries: 0, db summaries: 0, lsreq entries: 0 Receive errors: None 1754 Chapter 74: Operational Commands for Layer 3 Protocols clear bgp damping Syntax Syntax (J-EX Series Switch) Release Information Description Options clear bgp damping clear bgp damping Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Border Gateway Protocol (BGP) route flap damping information. none—Clear all BGP route flap damping information. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. prefix—(Optional) Clear route flap damping information for only the specified destination prefix. Required Privilege Level Related Documentation List of Sample Output Output Fields clear bgp damping clear • show policy damping on page 1886 • show route damping on page 1922 clear bgp damping on page 1755 When you enter this command, you are provided feedback on the status of your request. user@host> clear bgp damping 1755 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear bgp neighbor Syntax Syntax (J-EX Series Switch) Release Information Description Options clear bgp neighbor clear bgp neighbor Command introduced before Junos OS Release 10.2 for J-EX Series switches. Perform one of the following tasks: • Change the state of one or more Border Gateway Protocol (BGP) neighbors to IDLE. For neighbors in the ESTABLISHED state, this command drops the TCP connection to the neighbors and then reestablishes the connection. • (soft or soft-inbound keyword only) Reapply export policies or import policies, respectively, and send refresh updates to one or more BGP neighbors without changing their state. none—Change the state of all BGP neighbors to IDLE. as as-number—(Optional) Apply this command only to neighbors in the specified autonomous system (AS). instance instance-name—(Optional) Apply this command only to neighbors for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. neighbor—(Optional) IP address of a BGP peer. Apply this command only to the specified neighbor. soft—(Optional) Reapply any export policies and send refresh updates to neighbors without clearing the state. soft-inbound—(Optional) Reapply any import policies and send refresh updates to neighbors without clearing the state. soft-minimum-igp—(Optional) Provides soft refresh of the outbound state when the interior gateway protocol (IGP) metric is reset. 1756 Chapter 74: Operational Commands for Layer 3 Protocols Required Privilege Level Related Documentation List of Sample Output Output Fields clear bgp neighbor clear • show bgp neighbor on page 1812 clear bgp neighbor on page 1757 When you enter this command, you are provided feedback on the status of your request. user@host> clear bgp neighbor 1757 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear bgp table Syntax Syntax (J-EX Series Switch) Release Information Description Options clear bgp table table-name clear bgp table table-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Request BGP to refresh routes in a specified routing table. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. table-name—Request that BGP refresh routes in the specified table. Additional Information Required Privilege Level List of Sample Output Output Fields clear bgp table private.inet.0 1758 In some cases, a prefix limit is associated with a routing table for a VPN instance. When this limit is exceeded (for example, because of a network misconfiguration), some routes might not be inserted in the table. Such routes need to be added to the table after the network issue is resolved. Use the clear bgp table command to request that BGP refresh routes in a VPN instance table. clear clear bgp table private.inet.0 on page 1758 This command produces no output. user@host> clear bgp table private.inet.0 Chapter 74: Operational Commands for Layer 3 Protocols clear ipv6 neighbors Syntax Release Information Description Options clear ipv6 neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IPv6 neighbor cache information. none—Clear all IPv6 neighbor cache information. all—(Optional) Clear all IPv6 neighbor cache information. host hostname—(Optional) Clear the information for the specified IPv6 neighbors. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ipv6 neighbors view • show ipv6 neighbors on page 1031 clear ipv6 neighbors on page 1759 When you enter this command, you are provided feedback on the status of your request. user@host> clear ipv6 neighbors 1759 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear isis adjacency Syntax Syntax (J-EX Series Switch) Release Information Description Options clear isis adjacency clear isis adjacency Command introduced before Junos OS Release 10.2 for J-EX Series switches. Remove entries from the Intermediate System-to-Intermediate System (IS-IS) adjacency database. none—Remove all entries from the adjacency database. instance instance-name—(Optional) Clear all adjacencies for the specified routing instance only. interface interface-name—(Optional) Clear all adjacencies for the specified interface only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. neighbor—(Optional) Clear adjacencies for the specified neighbor only. Required Privilege Level Related Documentation List of Sample Output Output Fields clear isis adjacency clear • show isis adjacency on page 1830 clear isis adjacency on page 1760 See show isis adjacency for an explanation of output fields. The following sample output displays IS-IS adjacency database information before and after the clear isis adjacency command is entered: user@host> show isis adjacency IS-IS adjacency database: Interface System so-1/0/0.0 karakul so-1/1/3.0 1921.6800.5080 so-5/0/0.0 1921.6800.5080 L 3 3 3 State Up Up Up user@host> clear isis adjacency karakul 1760 Hold (secs) SNPA 26 23 19 Chapter 74: Operational Commands for Layer 3 Protocols user@host> show isis adjacency IS-IS adjacency database: Interface System so-1/0/0.0 karakul so-1/1/3.0 1921.6800.5080 so-5/0/0.0 1921.6800.5080 L 3 3 3 State Hold (secs) SNPA Initializing 26 Up 24 Up 21 1761 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear isis database Syntax Syntax (J-EX Series Switch) Release Information Description clear isis database clear isis database Command introduced before Junos OS Release 10.2 for J-EX Series switches. Remove the entries from the Intermediate System-to-Intermediate System (IS-IS) link-state database, which contains prefixes and topology information. You can also use purge with any of the options to initiate a network-wide purge of link-state PDUs (LSPs) rather than the local deletion of entries from the IS-IS link-state database. CAUTION: In a production network, the purge command option may cause short-term network-wide traffic disruptions. Use with caution! Options none—Remove all entries from the IS-IS link-state database for all routing instances. entries—(Optional) Name of the database entry. instance instance-name—(Optional) Clear all entries for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. purge—(Optional) Discard all entries in the IS-IS link-state database. Required Privilege Level Related Documentation List of Sample Output Output Fields clear isis database clear • show isis database on page 1843 clear isis database on page 1762 See show isis database for an explanation of output fields. The following sample output displays IS-IS link-state database information before and after the clear isis database command is entered: user@host> show isis database IS-IS level 1 link-state database: LSP ID Sequence Checksum Lifetime (secs) crater.00-00 0x12 0x84dd 1139 1762 Chapter 74: Operational Commands for Layer 3 Protocols 1 LSPs IS-IS level 2 link-state database: LSP ID Sequence Checksum Lifetime (secs) crater.00-00 0x19 0xe92c 1134 badlands.00-00 0x16 0x1454 985 carlsbad.00-00 0x33 0x220b 1015 ranier.00-00 0x2e 0xfc31 1007 1921.6800.5066.00-00 0x11 0x7313 566 1921.6800.5067.00-00 0x14 0xd9d4 939 6 LSPs user@host> clear isis database user@host> show isis database IS-IS level 1 link-state database: LSP ID Sequence Checksum Lifetime (secs) IS-IS level 2 link-state database: LSP ID Sequence Checksum Lifetime (secs) 1763 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear isis overload Syntax Syntax (J-EX Series Switch) Release Information Description Options clear isis overload clear isis overload Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reset the Intermediate System-to-Intermediate System (IS-IS) dynamic overload bit. This command can appear to not work, continuing to display overload after execution. The bit is reset only if the root cause is corrected by configuration remotely or locally. none—Reset the IS-IS dynamic overload bit. instance instance-name—(Optional) Reset the IS-IS dynamic overload bit for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear isis overload clear • show isis database on page 1843 clear isis overload on page 1764 See show isis database for an explanation of output fields. The following sample output displays IS-IS database information before and after the clear isis overload command is entered: user@host> show isis database IS-IS level 1 link-state database: LSP ID Sequence Checksum Lifetime Attributes pro3-c.00-00 0x4 0x10db 1185 L1 L2 Overload 1 LSPs IS-IS level 2 link-state database: LSP ID Sequence Checksum Lifetime Attributes pro3-c.00-00 0x5 0x429f 1185 L1 L2 Overload pro2-a.00-00 pro2-a.02-00 3 LSPs user@host> clear isis overload 1764 0x91e 0x1 0x2589 0xcbc 874 L1 L2 874 L1 L2 Chapter 74: Operational Commands for Layer 3 Protocols user@host> show isis database IS-IS level 1 link-state database: LSP ID Sequence Checksum Lifetime Attributes pro3-c.00-00 0xa 0x429e 1183 L1 L2 1 LSPs IS-IS level 2 link-state database: LSP ID Sequence Checksum Lifetime Attributes pro3-c.00-00 0xc 0x9c39 1183 L1 L2 pro2-a.00-00 0x91e 0x2589 783 L1 L2 pro2-a.02-00 0x1 0xcbc 783 L1 L2 3 LSPs 1765 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear isis statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear isis statistics clear isis statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set statistics about Intermediate System-to-Intermediate System (IS-IS) traffic to zero. none—Set IS-IS traffic statistics to zero for all routing instances. instance instance-name—(Optional) Set IS-IS traffic statistics to zero for the specified routing instance only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear isis statistics view • show isis statistics on page 1866 clear isis statistics on page 1766 See show isis statistics for an explanation of output fields. The following sample output displays IS-IS statistics before and after the clear isis statistics command is entered: user@host> show isis statistics IS-IS statistics for merino: PDU type LSP IIH CSNP PSNP Unknown Totals Received 12793 116751 203956 7356 0 340856 Processed 12793 116751 203956 7350 0 340850 Drops 0 0 0 6 0 6 Sent 8666 118834 204080 8635 0 340215 Total packets received: 340856 Sent: 340934 SNP queue length: LSP queue length: SPF runs: Fragments rebuilt: LSP regenerations: 1766 0 Drops: 0 Drops: 1064 1087 436 0 0 Rexmit 719 0 0 0 0 719 Chapter 74: Operational Commands for Layer 3 Protocols Purges initiated: 0 user@host> clear isis statistics user@host> show isis statistics IS-IS statistics for merino: PDU type LSP IIH CSNP PSNP Unknown Totals Received 0 3 2 0 0 5 Processed 0 3 2 0 0 5 Drops 0 0 0 0 0 0 Sent 0 3 4 0 0 7 Rexmit 0 0 0 0 0 0 Total packets received: 5 Sent: 7 SNP queue length: LSP queue length: 0 Drops: 0 Drops: SPF runs: Fragments rebuilt: LSP regenerations: Purges initiated: 0 0 0 0 0 0 1767 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear ospf overload Syntax Syntax (J-EX Series Switch) Release Information Description Options clear ospf overload clear ospf overload Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear the Open Shortest Path First version 2 (OSPFv2) overload bit and rebuild link-state advertisements (LSAs). none—Clear the overload bit and rebuild LSAs for all routing instances. instance instance-name—(Optional) Clear the overload bit and rebuild LSAs for the specified routing instance only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields clear ospf overload 1768 clear clear ospf overload on page 1768 When you enter this command, you are provided feedback on the status of your request. user@host> clear ospf overload Chapter 74: Operational Commands for Layer 3 Protocols clear rip general-statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear rip general-statistics clear rip general-statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Routing Information Protocol (RIP) general statistics. none—Clear RIP general statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear rip general-statistics clear • show rip general-statistics on page 1888 clear rip general-statistics on page 1769 When you enter this command, you are provided feedback on the status of your request. user@host> clear rip general-statistics 1769 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear rip statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear rip statistics clear rip statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Routing Information Protocol (RIP) statistics. none—Reset RIP counters for all neighbors for all routing instances. instance (all | instance-name)—(Optional) Clear RIP statistics for all instances or for the specified routing instance only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. neighbor—(Optional) Clear RIP statistics for the specified neighbor only. Required Privilege Level Related Documentation List of Sample Output Output Fields clear rip statistics 1770 clear • show rip statistics on page 1891 clear rip statistics on page 1770 When you enter this command, you are provided feedback on the status of your request. user@host> clear rip statistics Chapter 74: Operational Commands for Layer 3 Protocols clear ripng general-statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear ripng general-statistics clear ripng general-statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Routing Information Protocol next generation (RIPng) general statistics. none—Clear RIPng general statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ripng general-statistics clear • show ripng general-statistics on page 1894 clear ripng general-statistics on page 1771 When you enter this command, you are provided feedback on the status of your request. user@host> clear ripng general-statistics 1771 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear ripng statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear ripng statistics clear ripng statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Routing Information Protocol next-generation (RIPng) statistics. none—Reset RIPng counters for all neighbors for all routing instances. instance—(Optional) Reset RIPng counters for the specified instance. name—(Optional) Reset RIPng counters for the specified neighbor. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear ripng statistics 1772 clear • show ripng statistics on page 1897 clear ripng statistics on page 1772 When you enter this command, you are provided feedback on the status of your request. user@host> clear ripng statistics Chapter 74: Operational Commands for Layer 3 Protocols show (ospf | ospf3) interface Syntax Syntax (J-EX Series Switch) Release Information Description Options show (ospf | ospf3) interface show (ospf | ospf3) interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the status of Open Shortest Path First (OSPF) interfaces. none—Display standard information about the status of all OSPF interfaces for all routing instances brief | detail | extensive—(Optional) Display the specified level of output. area area-id—(Optional) Display information about the interfaces that belong to the specified area. interface-name—(Optional) Display information for the specified interface. instance instance-name—(Optional) Display all OSPF interfaces under the named routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) (OSPFv3 only) Display information about the interfaces for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level List of Sample Output view show ospf interface brief on page 1775 show ospf interface detail on page 1775 show ospf3 interface detail on page 1776 show ospf interface detail(When Multiarea Adjacency Is Configured) on page 1776 show ospf interface area area-id on page 1777 show ospf interface extensive (When Flooding Reduction Is Enabled) on page 1777 1773 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output Fields Table 203 on page 1774 lists the output fields for the show (ospf | ospf3) interface command. Output fields are listed in the approximate order in which they appear. Table 203: show (ospf | ospf3) interface Output Fields Field Name Field Description Level of Output Interface Name of the interface running OSPF version 2 or OSPF version 3. All levels State State of the interface: BDR, Down, DR, DRother, Loop, PtToPt, or Waiting. All levels Area Number of the area that the interface is in. All levels DR ID Address of the area's designated router. All levels BDR ID Backup designated router for a particular subnet. All levels Nbrs Number of neighbors on this interface. All levels Type Type of interface: LAN, NBMA, P2MP, P2P, or Virtual. detail extensive Address IP address of the neighbor. detail extensive Mask Netmask of the neighbor. detail extensive Prefix-length (OSPFv3) IPv6 prefix length, in bits. detail extensive OSPF3-Intf-Index (OSPFv3) OSPF version 3 interface index. detail extensive MTU Interface's maximum transmission unit (MTU). detail extensive Cost Interface's cost (metric). detail extensive DR addr Address of the designated router. detail extensive BDR addr Address of the backup designated router. detail extensive Adj count Number of adjacent neighbors. detail extensive Secondary Indicates that this interface is configured as a secondary interface for this area. This interface can belong to more than one area, but can be designated as a primary interface only for one area. detail extensive Flood Reduction Indicates that this interface is configured with flooding reduction. All self-originated LSAs from this interface are initially sent with the DoNotAge bit set. As a result, LSAs are refreshed only when a change occurs. extensive Priority Router priority used in designated router (DR) election on this interface. detail extensive Flood list List of link-state advertisements (LSAs) that might be about to flood this interface. extensive 1774 Chapter 74: Operational Commands for Layer 3 Protocols Table 203: show (ospf | ospf3) interface Output Fields (continued) Field Name Field Description Level of Output Ack list Acknowledgment list. List of pending acknowledgments on this interface. extensive Descriptor list List of packet descriptors. extensive Hello Configured value for the Hello timer. detail extensive Dead Configured value for the Dead timer. detail extensive Auth type (OSPFv2) Authentication mechanism for sending and receiving OSPF protocol packets: detail extensive • MD5—MD5 mechanism is configured in accordance with RFC 2328. • None—No authentication method is configured. • Password—Simple password (RFC 2328) is configured. Topology (Multiarea adjacency) Name of topology: default or name IPSec SA name (OSPFv2) Name of the IPsec security association name detail extensive Active key ID (OSPFv2 and MD5) Number from 0 to 255 that uniquely identifies an MD5 key. detail extensive Start time (OSPFv2 and MD5) Time at which the routing device starts using an MD5 key to authenticate OSPF packets transmitted on the interface on which this key is configured. To authenticate received OSPF protocol packets, the key becomes effective immediately after the configuration is committed. If the start time option is not configured, the key is effective immediately for send and receive and is displayed as Start time 1970 Jan 01 00:00:00 PST. detail extensive ReXmit Configured value for the Retransmit timer. detail extensive Stub, Not Stub, or Stub NSSA Type of area. detail extensive show ospf interface brief user@host> show ospf interface brief Intf State Area at-5/1/0.0 PtToPt 0.0.0.0 ge-2/3/0.0 DR 0.0.0.0 lo0.0 DR 0.0.0.0 so-0/0/0.0 Down 0.0.0.0 so-6/0/1.0 PtToPt 0.0.0.0 so-6/0/2.0 Down 0.0.0.0 so-6/0/3.0 PtToPt 0.0.0.0 show ospf interface detail user@host> show ospf interface detail Interface State Area DR ID BDR ID Nbrs fe-0/0/1.0 BDR 0.0.0.0 192.168.37.12 10.255.245.215 1 Type LAN, address 192.168.37.11, Mask 255.255.255.248, MTU 4460, Cost 40 DR addr 192.168.37.12, BDR addr 192.168.37.11, Adj count 1, Priority 128 Hello 10, Dead 40, ReXmit 5, Not Stub t1-0/2/1.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 0 DR ID 0.0.0.0 192.168.4.16 192.168.4.16 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 BDR ID 0.0.0.0 192.168.4.15 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 Nbrs 1 1 0 0 1 0 1 1775 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Type P2P, Address 0.0.0.0, Mask 0.0.0.0, MTU 1500, Cost 2604 Adj count 0 Hello 10, Dead 40, ReXmit 5, Not Stub Auth type: MD5, Active key ID 3, Start time 2002 Nov 19 10:00:00 PST IPsec SA Name: sa show ospf3 interface detail show ospf interface detail (When Multiarea Adjacency Is Configured) user@host> show ospf3 interface so-0/0/3.0 detail Interface State Area DR-ID BDR-ID so-0/0/3.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 Address fe80::2a0:a5ff:fe28:1dfc, Prefix-length 64 OSPF3-Intf-index 1, Type P2P, MTU 4470, Cost 12, Adj-count 1 Hello 10, Dead 40, ReXmit 5, Not Stub user@host> show ospf interface detail regress@router> show ospf interface detail Interface State Area lo0.0 DR 0.0.0.0 DR ID 10.255.245.2 Nbrs 1 BDR ID 0.0.0.0 Type: LAN, Address: 127.0.0.1, Mask: 255.255.255.255, MTU: 65535, Cost: 0 DR addr: 127.0.0.1, Adj count: 0, Priority: 128 Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 0 lo0.0 DR 0.0.0.0 10.255.245.2 0.0.0.0 Nbrs 0 0 Type: LAN, Address: 10.255.245.2, Mask: 255.255.255.255, MTU: 65535, Cost: 0 DR addr: 10.255.245.2, Adj count: 0, Priority: 128 Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 0 so-0/0/0.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1 Adj count: 1 Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 so-0/0/0.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 0 Type: P2P, Address: 192.168.37.46, Mask: 255.255.255.254, MTU: 4470, Cost: 1 Adj count: 0, , Passive Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Passive, Cost: 1 so-1/0/0.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1 Adj count: 1 Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 so-1/0/0.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 0 Type: P2P, Address: 192.168.37.54, Mask: 255.255.255.254, MTU: 4470, Cost: 1 Adj count: 0, , Passive Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Passive, Cost: 1 so-0/0/0.0 PtToPt 1.1.1.1 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1 1776 Chapter 74: Operational Commands for Layer 3 Protocols Adj count: 1, Secondary Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 so-1/0/0.0 PtToPt 1.1.1.1 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1 Adj count: 1, Secondary Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 so-0/0/0.0 PtToPt 2.2.2.2 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1 Adj count: 1, Secondary Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 so-1/0/0.0 PtToPt 2.2.2.2 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1 Adj count: 1, Secondary Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 show ospf interface area area-id user@host> show ospf interface area 1.1.1.1 Interface State Area so-0/0/0.0 PtToPt 1.1.1.1 so-1/0/0.0 PtToPt 1.1.1.1 DR ID 0.0.0.0 0.0.0.0 BDR ID 0.0.0.0 0.0.0.0 Nbrs 1 1 show ospf interface extensive (When Flooding Reduction Is Enabled) user@host> show ospf interface extensive Interface State Area fe-0/0/0.0 PtToPt 0.0.0.0 DR ID 0.0.0.0 BDR ID 0.0.0.0 Nbrs 0 Type: P2P, Address: 10.10.10.1, Mask: 255.255.255.0, MTU: 1500, Cost: 1 Adj count: 0 Secondary, Flood Reduction Hello: 10, Dead: 40, ReXmit: 5, Not Stub Auth type: None Topology default (ID 0) -> Cost: 1 1777 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show (ospf | ospf3) io-statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show (ospf | ospf3) io-statistics show (ospf | ospf3) io-statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Open Shortest Path First (OSPF) input and output statistics. none—Display OSPF input and output statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear (ospf | ospf3) statistics on page 1753 show ospf io-statistics on page 1778 Table 204 on page 1778 lists the output fields for the show ospf io-statistics command. Output fields are listed in the approximate order in which they appear. Table 204: show (ospf | ospf3) io-statistics Output Fields show ospf io-statistics Field Name Field Description Packets read Number of OSPF packets read since the last time the routing protocol was started. average per run Total number of packets divided by the total number of times the OSPF read operation is scheduled to run. max run Maximum number of packets for a given run among all scheduled runs. Receive errors Number of faulty packets received with errors. user@host> show ospf io-statistics Packets read: 7361, average per run: 1.00, max run: 1 Receive errors: None 1778 Chapter 74: Operational Commands for Layer 3 Protocols show (ospf | ospf3) log Syntax Syntax (J-EX Series Switch) Release Information show (ospf | osfp3) log show (ospf | osfp3) log Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the entries in the Open Shortest Path First (OSPF) log of SPF calculations. Options none—Display entries in the OSPF log of SPF calculations for all routing instances. instance instance-name—(Optional) Display entries for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. topology topology-name—(Optional) Display entries for the specified topology. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(OSPFv3 only) (Optional) Display entries for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level List of Sample Output Output Fields view show ospf log on page 1780 show ospf log topology voice on page 1780 Table 205 on page 1779 lists the output fields for the show (ospf | ospf3) log command. Output fields are listed in the approximate order in which they appear. Table 205: show (ospf | ospf3) log Output Fields Field Name Field Description When Time, in weeks (w) and days (d), since the SPF calculation was made. Type Type of calculation: Cleanup, External, Interarea, NSSA, Redist, SPF, Stub, Total, or Virtuallink. Elapsed Amount of time, in seconds, that elapsed during the operation, or the time required to complete the SPF calculation. The start time is the time displayed in the When field. 1779 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ospf log user@host> show ospf log When Type 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d 1w4d ... show ospf log topology voice 17:25:58 17:25:58 17:25:58 17:25:58 17:25:58 17:25:58 17:25:58 17:24:48 17:24:48 17:24:48 17:24:48 17:24:48 17:24:48 17:24:48 17:24:48 Stub SPF Stub Interarea External Cleanup Total SPF Stub SPF Stub Interarea External Cleanup Total Elapsed 0.000017 0.000070 0.000019 0.000054 0.000005 0.000203 0.000537 0.000125 0.000017 0.000100 0.000016 0.000056 0.000005 0.000238 0.000600 user@host> show ospf log topology voice Topology voice SPF log: Last instance of each event type When Type Elapsed 00:06:11 SPF 0.000116 00:06:11 Stub 0.000114 00:06:11 Interarea 0.000126 00:06:11 External 0.000067 00:06:11 NSSA 0.000037 00:06:11 Cleanup 0.000186 Maximum length of each event type When Type Elapsed 00:13:43 SPF 0.000140 00:13:33 Stub 0.000116 00:13:43 Interarea 0.000128 00:13:33 External 0.000075 00:13:38 NSSA 0.000039 00:13:53 Cleanup 0.000657 Last 100 events When Type 00:13:53 00:13:53 00:13:53 00:13:53 00:13:53 00:13:53 00:13:53 . . 00:06:11 00:06:11 00:06:11 00:06:11 00:06:11 1780 Elapsed SPF Stub Interarea External NSSA Cleanup Total 0.000090 0.000041 0.000123 0.000040 0.000038 0.000657 0.001252 SPF Stub Interarea External NSSA 0.000116 0.000114 0.000126 0.000067 0.000037 Chapter 74: Operational Commands for Layer 3 Protocols 00:06:11 00:06:11 Cleanup Total 0.000186 0.000818 1781 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show (ospf | ospf3) neighbor Syntax Syntax (J-EX Series Switch) Release Information Description Options show (ospf | ospf3) neighbor show (ospf | ospf3) neighbor Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Open Shortest Path First (OSPF) neighbors. none—Display standard information about all OSPF neighbors for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. area area-id—(Optional) Display information about the OSPF neighbors for the specified area. instance (all | instance-name—(Optional) Display all OSPF interfaces for all routing instances or under the named routing instance. interface interface-name—(Optional) Display information about OSPF neighbors for the specified logical interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. neighbor—(Optional) Display information about the specified OSPF neighbor. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) (OSPFv3 only) Display information about the OSPF neighbors for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level Related Documentation List of Sample Output 1782 view • clear (ospf | ospf3) neighbor on page 1752 show ospf neighbor brief on page 1784 Chapter 74: Operational Commands for Layer 3 Protocols show ospf neighbor detail on page 1784 show ospf neighbor extensive on page 1785 show ospf3 neighbor detail on page 1786 show ospf neighbor area area-id on page 1786 show ospf neighbor interface interface-name on page 1786 show ospf3 neighbor instance all (OSPFv3 Multiple Family Address Support Enabled) on page 1786 Output Fields Table 206 on page 1783 lists the output fields for the show (ospf | ospf3) neighbor command. Output fields are listed in the approximate order in which they appear. Table 206: show (ospf | ospf3) neighbor Output Fields Field Name Field Description Level of Output Address Address of the neighbor. All levels Interface Interface through which the neighbor is reachable. All levels State State of the neighbor: All levels • Attempt—Valid only for neighbors attached to nonbroadcast networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort must be made to contact the neighbor. • Down—Initial state of a neighbor conversation. It indicates that no recent information has been received from the neighbor. Hello packets might continue to be sent to neighbors in the Down state, although at a reduced frequency. • Exchange—Routing device is describing its entire link-state database by sending database description packets to the neighbor. Each packet has a sequence number and is explicitly acknowledged. • ExStart—First step in creating an adjacency between the two neighboring routing devices. The goal of this step is to determine which routing device is the master, and to determine the initial sequence number. • Full—Neighboring routing devices are fully adjacent. These adjacencies appear in router link and network link advertisements. • Init—A Hello packet has recently been sent by the neighbor. However, bidirectional communication has not yet been established with the neighbor. This state may occur, for example, because the routing device itself did not appear in the neighbor's hello packet. • Loading—Link-state request packets are sent to the neighbor to acquire more recent advertisements that have been discovered (but not yet received) in the Exchange state. • 2Way—Communication between the two routing devices is bidirectional. This state has been ensured by the operation of the Hello Protocol. This is the most advanced state short of beginning adjacency establishment. The (backup) designated router is selected from the set of neighbors in state 2Way or greater. ID Router ID of the neighbor. All levels Pri Priority of the neighbor to become the designated router. All levels Dead Number of seconds until the neighbor becomes unreachable. All levels 1783 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 206: show (ospf | ospf3) neighbor Output Fields (continued) Field Name Field Description Level of Output Link state acknowledgment list Number of link-state acknowledgments received. extensive Link state retransmission list Total number of link-state advertisements retransmitted. For extensive output only, the following information is also displayed: detail extensive • Type—Type of link advertisement: ASBR, Sum, Extern, Network, NSSA, OpaqArea, Router, or Summary. • LSA ID—LSA identifier included in the advertisement. An asterisk preceding the identifier marks database entries that originated from the local routing device. • Adv rtr—Address of the routing device that sent the advertisement. • Seq—Link sequence number of the advertisement. Neighbor-address (OSPFv3 only) If the neighbor uses virtual links, the Neighbor-address is the site-local, local, or global address. If the neighbor uses a physical interface, the Neighbor-address is an IPv6 link-local address. detail extensive area Area that the neighbor is in. detail extensive OSPF3-Intf-Index (OSPFv3 only) Displays the OSPFv3 interface index. detail extensive opt Option bits received in the hello packets from the neighbor. detail extensive DR or DR-ID Address of the designated router. detail extensive BDR or BDR-ID Address of the backup designated router. detail extensive Up Length of time since the neighbor came up. detail extensive adjacent Length of time since the adjacency with the neighbor was established. detail extensive show ospf neighbor brief user@host> show ospf neighbor brief Address Intf 192.168.254.225 fxp3.0 192.168.254.230 fxp3.0 192.168.254.229 fxp3.0 10.1.1.129 fxp2.0 10.1.1.131 fxp2.0 10.1.2.1 fxp1.0 10.1.2.81 fxp0.0 show ospf neighbor detail user@host> show ospf neighbor detail Address Interface State ID 10.5.1.2 ge-1/2/0.1 Full 10.5.1.2 area 0.0.0.1, opt 0x42, DR 10.5.1.2, BDR 10.5.1.1 Up 06:09:28, adjacent 05:17:36 Link state acknowledgment list: 3 entries 1784 State 2Way Full Full Full Full Full Full ID 10.250.240.32 10.250.240.8 10.250.240.35 10.250.240.12 10.250.240.11 10.250.240.9 10.250.240.10 Pri 128 128 128 128 128 128 128 Dead 36 38 33 37 38 32 33 Pri 128 Dead 37 Chapter 74: Operational Commands for Layer 3 Protocols Link state retransmission list: show ospf neighbor extensive 9 entries 10.5.10.2 ge-1/2/0.10 ExStart 10.5.1.38 area 0.0.0.1, opt 0x42, DR 10.5.10.2, BDR 10.5.10.1 Up 06:09:28 master, seq 0xac1530f8, rexmit DBD in 3 sec rexmit LSREQ in 0 sec 10.5.11.2 ge-1/2/0.11 Full 10.5.1.42 area 0.0.0.1, opt 0x42, DR 10.5.11.2, BDR 10.5.11.1 Up 06:09:28, adjacent 05:26:46 Link state retransmission list: 1 entries 128 34 128 38 10.5.12.2 ge-1/2/0.12 ExStart 10.5.1.46 area 0.0.0.1, opt 0x42, DR 10.5.12.2, BDR 10.5.12.1 Up 06:09:28 master, seq 0xac188a68, rexmit DBD in 2 sec rexmit LSREQ in 0 sec 128 33 Pri 128 Dead 33 128 38 user@host> show ospf neighbor extensive Address Interface State ID 10.5.1.2 ge-1/2/0.1 Full 10.5.1.2 area 0.0.0.1, opt 0x42, DR 10.5.1.2, BDR 10.5.1.1 Up 06:09:42, adjacent 05:17:50 Link state retransmission list: Type LSA ID Adv rtr Seq Summary 10.8.56.0 172.25.27.82 0x8000004d Router 10.5.1.94 10.5.1.94 0x8000005c Network 10.5.24.2 10.5.1.94 0x80000036 Summary 10.8.57.0 172.25.27.82 0x80000024 Extern 1.10.90.0 10.8.1.2 0x80000041 Extern 1.4.109.0 10.6.1.2 0x80000041 Router 10.5.1.190 10.5.1.190 0x8000005f Network 10.5.48.2 10.5.1.190 0x8000003d Summary 10.8.58.0 172.25.27.82 0x8000004d Extern 1.10.91.0 10.8.1.2 0x80000041 Extern 1.4.110.0 10.6.1.2 0x80000041 Router 10.5.1.18 10.5.1.18 0x8000005f Network 10.5.5.2 10.5.1.18 0x80000033 Summary 10.8.59.0 172.25.27.82 0x8000003a Summary 10.8.62.0 172.25.27.82 0x80000025 10.5.10.2 ge-1/2/0.10 ExStart 10.5.1.38 area 0.0.0.1, opt 0x42, DR 10.5.10.2, BDR 10.5.10.1 Up 06:09:42 master, seq 0xac1530f8, rexmit DBD in 2 sec 1785 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rexmit LSREQ in 0 sec 10.5.11.2 ge-1/2/0.11 Full 10.5.1.42 area 0.0.0.1, opt 0x42, DR 10.5.11.2, BDR 10.5.11.1 Up 06:09:42, adjacent 05:27:00 Link state retransmission list: Type show ospf3 neighbor detail show ospf neighbor area area-id show ospf neighbor interface interface-name show ospf3 neighbor instance all (OSPFv3 Multiple Family Address Support Enabled) 1786 LSA ID Adv rtr 33 Seq Summary 10.8.58.0 172.25.27.82 0x8000004d Extern 1.10.91.0 10.8.1.2 0x80000041 Extern 1.1.247.0 10.5.1.2 0x8000003f Extern 1.4.110.0 10.6.1.2 0x80000041 Router 10.5.1.18 10.5.1.18 0x8000005f Network 10.5.5.2 10.5.1.18 0x80000033 Summary 10.8.59.0 172.25.27.82 0x8000003a user@host> show ospf3 neighbor detail ID Interface State 10.255.71.13 fe-0/0/2.0 Full Neighbor-address fe80::290:69ff:fe9b:e002 area 0.0.0.0, opt 0x13, OSPF3-Intf-Index 2 DR-ID 10.255.71.13, BDR-ID 10.255.71.12 Up 02:51:43, adjacent 02:51:43 user@host >show ospf neighbor area 1.1.1.1 Address Interface 192.168.37.47 so-0/0/0.0 Area 1.1.1.1 192.168.37.55 so-1/0/0.0 Area 1.1.1.1 128 Pri 128 Dead 30 State Full ID 10.255.245.4 Pri 128 Dead 33 Full 10.255.245.5 128 37 ID 10.255.245.4 Pri 128 Dead 37 10.255.245.4 128 33 10.255.245.4 128 32 user@host >show ospf neighbor interface so-0/0/0.0 Address Interface State 192.168.37.47 so-0/0/0.0 Full Area 0.0.0.0 192.168.37.47 so-0/0/0.0 Full Area 1.1.1.1 192.168.37.47 so-0/0/0.0 Full Area 2.2.2.2 user @host > show ospf3 neighbor instance all Instance: ina Realm: ipv6-unicast ID Interface State 100.1.1.1 fe-0/0/2.0 Full Neighbor-address fe80::217:cb00:c87c:8c03 Instance: inb Realm: ipv4-unicast ID Interface State 100.1.2.1 fe-0/0/2.1 Full Neighbor-address fe80::217:cb00:c97c:8c03 Pri 128 Pri 128 Dead 37 Dead 33 Chapter 74: Operational Commands for Layer 3 Protocols show (ospf | ospf3) overview Syntax Syntax (J-EX Series Switch) Release Information Description Options show (ospf | ospf3) overview show (ospf | ospf3) overview Command introduced before Junos OS Release 10.2 for J-EX Series switches. Database protection introduced in Junos OS Release 10.2. Display Open Shortest Path First (OSPF) overview information. none—Display standard information about all OSPF neighbors for all routing instances. brief | extensive—(Optional) Display the specified level of output. instance instance-name—(Optional) Display all OSPF interfaces under the named routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) (OSPFv3 only) Display information about the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level List of Sample Output Output Fields view show ospf overview on page 1789 show ospf overview (with Database Protection) on page 1789 show ospf3 overview (with database protection) on page 1790 show ospf overview extensive on page 1790 Table 207 on page 1787 lists the output fields for the show ospf overview command. Output fields are listed in the approximate order in which they appear. Table 207: show ospf overview Output Fields Field name Field Description Level of Output Instance OSPF routing instance. All levels Router ID Router ID of the routing device. All levels Route table index Route table index. All levels 1787 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 207: show ospf overview Output Fields (continued) Field name Field Description Level of Output Configured overload Overload capability is enabled. If the overload timer is also configured, display the time that remains before it is set to expire. This field is not displayed after the timer expires. All levels Full SPF runs Number of complete Shortest Path First calculations. All levels SPF delay Delay before performing consecutive Shortest Path First calculations. All levels SPF holddown Delay before performing additional Shortest Path First (SPF) calculations after the maximum number of consecutive SPF calculations is reached. All levels SPF rapid runs Maximum number of Shortest Path First calculations that can be performed in succession before the holddown timer begins. All levels LSA refresh time Refresh period for link-state advertisement (in minutes). All levels Database protection state Current state of database protection. All levels Warning threshold Threshold at which a warning message is logged (percentage of maximum LSA count). All levels Non self-generated LSAs Number of LSAs whose router ID is not equal to the local router ID: Current, Warning (threshold), and Allowed. All levels Ignore time How long the database has been in the ignore state. All levels Reset time How long the database must stay out of the ignore or isolated state before it returns to normal operations. All levels Ignore count Number of times the database has been in the ignore state: Current and Allowed. All levels Restart Graceful restart capability: enabled or disabled. All levels Restart duration Time period for complete reacquisition of OSPF neighbors. All levels Restart grace period Time period for which the neighbors should consider the restarting routing device as part of the topology. All levels Helper mode Graceful restart helper capability: enabled or disabled. All levels Trace options OSPF-specific trace options. extensive Trace file Name of the file to receive the output of the tracing operation. extensive Area Area number. Area 0.0.0.0 is the backbone area. All levels Stub type Stub type of area: Normal Stub, Not Stub, or Not so Stubby Stub. All levels 1788 Chapter 74: Operational Commands for Layer 3 Protocols Table 207: show ospf overview Output Fields (continued) Field name Field Description Level of Output Authentication Type Type of authentication: None, Password, or MD5. All levels Area border routers Number of area border routers. All levels Neighbors Number of autonomous system boundary routers. All levels show ospf overview user@host> show ospf overview Instance: master Router ID: 10.255.245.6 Route table index: 0 Configured overload, expires in 118 seconds LSA refresh time: 50 minutes Restart: Enabled Restart duration: 20 sec Restart grace period: 40 sec Helper mode: enabled Area: 0.0.0.0 Stub type: Not Stub Authentication Type: None Area border routers: 0, AS boundary routers: 0 Neighbors Up (in full state): 0 Topology: default (ID 0) Prefix export count: 0 Full SPF runs: 1 SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3 show ospf overview (with Database Protection) user@host> show ospf overview Instance: master Router ID: 10.255.112.218 Route table index: 0 LSA refresh time: 50 minutes Traffic engineering Restart: Enabled Restart duration: 180 sec Restart grace period: 210 sec Helper mode: Enabled Database protection state: Normal Warning threshold: 70 percent Non self-generated LSAs: Current 582, Warning 700, Allowed 1000 Ignore time: 30, Reset time: 60 Ignore count: Current 0, Allowed 1 Area: 0.0.0.0 Stub type: Not Stub Authentication Type: None Area border routers: 0, AS boundary routers: 0 Neighbors Up (in full state): 160 Topology: default (ID 0) Prefix export count: 0 Full SPF runs: 70 1789 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3 Backup SPF: Not Needed show ospf3 overview (with database protection) show ospf overview extensive 1790 user@host> show ospf3 overview Instance: master Router ID: 10.255.112.128 Route table index: 0 LSA refresh time: 50 minutes Database protection state: Normal Warning threshold: 80 percent Non self-generated LSAs: Current 3, Warning 8, Allowed 10 Ignore time: 30, Reset time: 60 Ignore count: Current 0, Allowed 2 Area: 0.0.0.0 Stub type: Not Stub Area border routers: 0, AS boundary routers: 0 Neighbors Up (in full state): 1 Topology: default (ID 0) Prefix export count: 0 Full SPF runs: 7 SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3 Backup SPF: Not Needed user@host> show ospf overview extensive Instance: master Router ID: 1.1.1.103 Route table index: 0 Full SPF runs: 13, SPF delay: 0.200000 sec LSA refresh time: 50 minutes Restart: Disabled Trace options: lsa Trace file: /var/log/ospf size 131072 files 10 Area: 0.0.0.0 Stub type: Not Stub Authentication Type: None Area border routers: 0, AS boundary routers: 0 Neighbors Up (in full state): 1 Chapter 74: Operational Commands for Layer 3 Protocols show (ospf | ospf3) route Syntax Syntax (J-EX Series Switch) Release Information Description Options show (ospf | ospf3) route show (ospf | ospf3) route Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the Open Shortest Path First (OSPF) routing table. none—Display standard information about all entries in the OSPF routing table for all routing instances and all topologies. brief | detail | extensive—(Optional) Display the specified level of output. abr—(Optional) Display routes to area border routers. asbr—(Optional) Display routes to autonomous system border routers. extern—(Optional) Display external routes. inter—(Optional) Display interarea routes. intra—(Optional) Display intra-area routes. instance instance-name—(Optional) Display entries for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. network—(Optional) Display routes to networks. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(OSPFv3 only) (Optional) Display entries in the routing table for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. 1791 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS router—(Optional) Display routes to all routers. topology topology-name—(OSPF only) (Optional) Display routes for a particular topology. transit—(Optional) (OSPFv3 only) Display OSPFv3 routes to pseudonodes. Required Privilege Level List of Sample Output Output Fields view show ospf route on page 1793 show ospf route detail on page 1793 show ospf3 route on page 1794 show ospf3 route detail on page 1794 show ospf route topology voice on page 1795 Table 208 on page 1792 list the output fields for the show (ospf | ospf3) route command. Output fields are listed in the approximate order in which they appear. Table 208: show (ospf | ospf3) route Output Fields Field Name Field Description Output Level Topology Name of the topology. All levels Prefix Destination of the route. All levels Path type How the route was learned: All levels Route type • Inter—Interarea route • Ext1—External type 1 route • Ext2—External type 2 route • Intra—Intra-area route The type of routing device from which the route was learned: • AS BR—Route to AS border router • Area BR—Route to area border router • Area/AS BR—Route to router that is both an Area BR and AS BR. • Network—Network router. • Router—Route to a router that is neither an Area BR nor an AS BR. • Transit—(OSPFv3 only) Route to a pseudonode representing a transit network, All levels LAN, or nonbroadcast multiaccess (NBMA) link. • Discard—Route to a summary discard. NH Type Next-hop type: LSP or IP. All levels Metric Route's metric value. All levels NH-interface (OSPFv3 only) Interface through which the route's next hop is reachable. All levels NH-addr (OSPFv3 only) IPv6 address of the next hop. All levels 1792 Chapter 74: Operational Commands for Layer 3 Protocols Table 208: show (ospf | ospf3) route Output Fields (continued) Field Name Field Description Output Level NextHop Interface (OSPFv2 only) Interface through which the route's next hop is reachable. All levels Nexthop addr/label (OSPFv2 only) If the NH Type is IP, then it is the address of the next hop. If the NH Type is LSP, then it is the name of the label-switched path. All levels Area Area ID of the route. detail Origin Router from which the route was learned. detail Type 7 Route was learned through a not-so-stubby area (NSSA) link-state advertisement (LSA). detail P-bit Route was learned through NSSA LSA and the propagate bit was set. detail Fwd NZ Forwarding address is nonzero. Fwd NZ is only displayed if the route is learned through an NSSA LSA. detail optional-capability Optional capabilities propagated in the router LSA. This field is in the output for intraarea router routes only (when Route Type is Area BR, AS BR, Area/AS BR, or Router), not for interarea router routes or network routes. Three bits in this field are defined as follows: detail priority • 0x4 (V)—Routing device is at the end of a virtual active link. • 0x2 (E)—Routing device is an autonomous system boundary router. • 0x1 (B)—Routing device is an area border router. The priority assigned to the prefix: • high • medium • low detail NOTE: The priority field applies only to routes of type Network. show ospf route show ospf route detail user@host> show ospf route Prefix Path Route Type NH addr/label 10.255.71.12 Intra Router 10.255.71.13/32 192.168.222.84/30 Intra Intra Network Network Type IP IP LSP Metric Type 1 0 1 NextHop Nexthop Interface fe-0/0/2.0 lo0.0 fe-0/0/2.0 192.16.22.86 lsp-ab user@host> show ospf route detail Topology default Route Table: Prefix Path Type Route Type NH Metric Type label 10.255.14.174 Inter AS BR IP area 0.0.0.2, origin 10.255.14.185 210 NextHop Interface Nexthop addr/ t1-3/0/1.0 1793 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 10.255.14.178 area 0.0.0.2, 10.210.1.0/30 area 0.0.0.2, 100.1.1.1/32 area 0.0.0.2, 112.3.1.0/24 area 0.0.0.0, 200.3.3.0/30 area 0.0.0.2, show ospf3 route Intra Router IP 200 t3-3/1/3.0 origin 10.255.14.178, optional-capability 0x0 Intra Network IP 10 t3-3/1/2.0 origin 10.255.14.172, priority medium Inter Network IP 210 t1-3/0/1.0 origin 10.255.14.185, priority low Ext2 Network IP 0 t1-3/0/1.0 origin 10.255.14.174, priority high Inter Network IP 220 t1-3/0/1.0 origin 10.255.14.185, priority high user@host> show ospf3 route Prefix Path Route NH Metric type type type 10.255.71.13 Intra Router IP 1 NH-interface fe-0/0/2.0, NH-addr fe80::290:69ff:fe9b:e002 10.255.71.13;0.0.0.2 Prefix Path Route NH Metric NextHop Nexthop Type Type Type Interface addr/label 10.255.245.1 Intra Router IP 40 fxp1.1 192.168.36.17 area 0.0.0.0, origin 10.255.245.1 optional-capability 0x0, 10.255.245.3 Intra AS BR IP 1 fxp2.3 192.168.36.34 area 0.0.0.0, origin 10.255.245.3 optional-capability 0x0, 10.255.245.1/32 Intra Network IP 40 fxp1.1 192.168.36.17 area 0.0.0.0, origin 10.255.245.1, priority high 10.255.245.2/32 Intra Network IP 0 lo0.0 area 0.0.0.0, origin 10.255.245.2, priority medium 10.255.245.3/32 Intra Network IP 1 fxp2.3 192.168.36.34 area 0.0.0.0, origin 10.255.245.3, priority low Intra Transit IP 1 NH-interface fe-0/0/2.0 192::168:222:84/126 NH-interface fe-0/0/2.0 abcd::71:12/128 NH-interface lo0.0 abcd::71:13/128 NH-interface fe-0/0/2.0, NH-addr lsp-cd show ospf3 route detail user@host> show ospf3 route detail Prefix Metric 10.255.14.174 NH-interface so-1/2/2.0 Area 0.0.0.0, Origin 10.255.14.174, 10.255.14.178 NH-interface t3-3/1/3.0 Area 0.0.0.0, Origin 10.255.14.178, 10.255.14.185;0.0.0.2 NH-interface t1-3/0/1.0 NH-interface so-1/2/2.0 Area 0.0.0.0, Origin 10.255.14.185 1000:1:1::1/128 NH-interface so-1/2/2.0 Area 0.0.0.0, Origin 10.255.14.174, 1001:2:1::/48 NH-interface so-1/2/2.0 Area 0.0.0.0, Origin 10.255.14.174, 1002:1:7::/48 NH-interface so-1/2/2.0 1794 Intra Network IP 1 Intra Network IP 0 Intra Network LSP Path Route NH type Intra type Area/AS BR type IP 110 1 Optional-capability 0x3 Intra Router IP 200 Optional-capability 0x0 Intra Transit IP 200 Network IP 110 Priority low Ext1 Network IP 110 Fwd NZ, Priority medium Ext2 Network IP 0 Inter Chapter 74: Operational Commands for Layer 3 Protocols Area 0.0.0.0, Origin 10.255.14.174, Fwd NZ, Priority low 1002:3:4::/48 Ext2 Network NH-interface so-1/2/2.0 Area 0.0.0.0, Origin 10.255.14.174, Fwd NZ, Priority high abcd::10:255:14:172/128 Intra Network NH-interface lo0.0 Area 0.0.0.0, Origin 10.255.14.172, Priority low show ospf route topology voice user@host show ospf route topology voice Topology voice Route Table: Prefix Path Route Type Type 10.255.8.2 Intra Router 10.255.8.3 Intra Router 10.255.8.1/32 Intra Network 10.255.8.2/32 Intra Network 10.255.8.3/32 Intra Network 192.168.8.0/29 Intra Network 192.168.8.44/30 Intra Network 192.168.8.46/32 Intra Network 192.168.8.48/30 Intra Network 192.168.8.52/30 Intra Network 192.168.9.44/30 Intra Network 192.168.9.45/32 Intra Network NH Metric Type IP 1 IP 2 IP 0 IP 1 IP 2 IP 2 IP 2 IP 1 IP 1 IP 2 IP 1 IP 2 NextHop Interface so-0/2/0.0 so-0/2/0.0 lo0.0 so-0/2/0.0 so-0/2/0.0 so-0/2/0.0 so-0/2/0.0 so-0/2/0.0 so-0/2/1.0 so-0/2/0.0 so-0/2/0.0 so-0/2/0.0 IP 0 IP 0 Nexthop addr/label 1795 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show (ospf | ospf3) statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show (ospf | ospf3) statistics show (ospf | ospf3) statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display OSPF statistics. none—Display OSPF statistics for all routing instances. instance instance-name—(Optional) Display all statistics for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) (OSPFv3 only) Display all statistics for the specified OSPFv3 realm, or address family. Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast, which is the default. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear (ospf | ospf3) statistics on page 1753 show ospf statistics on page 1797 Table 209 on page 1796 lists the output fields for the show (ospf | ospf3) statistics command. Output fields are listed in the approximate order in which they appear. Table 209: show (ospf | ospf3) statistics Output Fields 1796 Field Name Field Description Packet type Type of OSPF packet. Total Sent/Total Received Total number of packets sent and received. Last 5 seconds Sent/Last 5 seconds Received Total number of packets sent and received in the last 5 seconds. LSAs retransmitted Total number of link-state advertisements transmitted, and number retransmitted in the last 5 seconds. Receive errors Number and type of receive errors. Chapter 74: Operational Commands for Layer 3 Protocols show ospf statistics user@host> show ospf statistics Packet type Total Sent Received Hello 505739 990495 DbD 20 26 LSReq 6 5 LSUpdate 27060 15319 LSAck 10923 52470 Last 5 seconds Sent Received 4 5 0 0 0 0 0 0 0 0 LSAs retransmitted: 16, last 5 seconds: 0 Receive errors: 862 no interface found 115923 no virtual link found 1797 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show as-path Syntax Syntax (J-EX Series Switch) Release Information Description Options show as-path show as-path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the distribution of autonomous system (AS) paths that the local routing device is using (usually through the routing table). Use this command to debug problems for AS paths and to understand how AS paths have been manipulated through a policy (through the as-path-prepend action) or through aggregation. none—Display basic information about AS paths that the local routing device is using (same as brief). brief | detail—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show as-path on page 1799 show as-path detail on page 1800 Table 210 on page 1798 lists the output fields for the show as-path command. Output fields are listed in the approximate order in which they appear. Table 210: show as-path Output Fields Field Name Field Description Level of Output Total AS paths Total number of AS paths. brief none Bucket Bucket value. This value represents a traffic classification on the interface. All levels Count Path reference count. All levels AS path AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: All levels 1798 • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. • Atomic—Route is an aggregate of several route prefixes. • Aggregator—Routing device has summarized a range of prefixes. Chapter 74: Operational Commands for Layer 3 Protocols Table 210: show as-path Output Fields (continued) Field Name Field Description Level of Output domain Number of independent AS domains. The AS paths of an independent AS domain are not shared with the AS paths and AS path attributes of other domains, including the master routing instance domain. detail neighbor as AS peer address. detail length Length of the AS path. detail segments Length of the AS segment descriptor. detail references Path reference count. detail show as-path user@host> show as-path Total AS paths: 30382 Bucket 0 Count: 36 I 14203 2914 174 31752 I 14203 2914 701 21512 I 14203 2914 1239 26632 I 14203 2914 1239 29704 I 14203 2914 4323 10248 I 14203 2914 4766 23560 I 14203 2914 6395 32776 I 14203 2914 7911 11272 I 14203 2914 12180 18440 I 14203 2914 17408 17416 I 14203 2914 701 702 24586 I 14203 2914 1239 4657 9226 I 14203 2914 1239 7132 16394 I 14203 2914 1299 8308 34826 I 14203 2914 3320 5603 28682 I 14203 2914 3491 1680 33802 I 14203 2914 3549 7908 27658 I 14203 2914 3549 20804 30730 I 14203 2914 7018 2687 9226 I 14203 2914 174 9318 9318 23564 I 14203 2914 701 3786 3786 23564 I 14203 2914 701 4761 4795 9228 I 14203 2914 1239 7132 5673 18444 I 14203 2914 3491 20485 24588 24588 I 14203 2914 5511 2200 1945 2060 I 14203 2914 7911 14325 14325 14348 I 14203 2914 701 4637 9230 9230 9230 I 14203 2914 6395 14 14 14 14 I 14203 2914 9299 6163 6163 6163 6163 9232 I 14203 2914 3356 3356 3356 3356 3356 11955 21522 I 14203 2914 9837 9837 9219 I Aggregator: 9219 202.27.91.253 14203 2914 174 30209 30222 30222 30222 ? 14203 2914 1299 5377 I (Atomic) Aggregator: 5377 193.219.192.22 14203 2914 4323 36097 I (Atomic) Aggregator: 36097 216.69.252.254 14203 2914 209 2516 17676 23813 I (Atomic) Aggregator: 23813 219.127.233.66 Bucket 1 Count: 28 14203 2914 35847 I 14203 2914 174 19465 I 1799 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 14203 14203 14203 14203 14203 2914 2914 2914 2914 2914 174 35849 I 2828 32777 I 4323 14345 I 4323 29705 I 6395 32777 I ... show as-path detail 1800 user@host> show as-path detail Total AS paths: 30410 Bucket 0 Count: 36 AS path: I domain 0, length 0, segments 0, references 54 AS path: 14203 2914 174 31752 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 701 21512 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 1239 26632 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 1239 29704 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 4323 10248 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 4766 23560 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 6395 32776 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 7911 11272 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 12180 18440 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 17408 17416 I domain 1, neighbor as: 14203, length 4, segments AS path: 14203 2914 701 702 24586 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 1239 4657 9226 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 1239 7132 16394 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 1299 8308 34826 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 3320 5603 28682 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 3491 1680 33802 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 3549 7908 27658 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 3549 20804 30730 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 7018 2687 9226 I domain 1, neighbor as: 14203, length 5, segments AS path: 14203 2914 174 9318 9318 23564 I domain 1, neighbor as: 14203, length 6, segments AS path: 14203 2914 701 3786 3786 23564 I domain 1, neighbor as: 14203, length 6, segments AS path: 14203 2914 701 4761 4795 9228 I domain 1, neighbor as: 14203, length 6, segments AS path: 14203 2914 1239 7132 5673 18444 I domain 1, neighbor as: 14203, length 6, segments AS path: 14203 2914 3491 20485 24588 24588 I domain 1, neighbor as: 14203, length 6, segments 1, references 2 1, references 2 1, references 2 1, references 2 1, references 2 1, references 2 1, references 3 1, references 2 1, references 3 1, references 3 1, references 3 1, references 7 1, references 2 1, references 2 1, references 2 1, references 2 1, references 2 1, references 2 1, references 3 1, references 2 1, references 2 1, references 14 1, references 2 1, references 4 Chapter 74: Operational Commands for Layer 3 Protocols AS path: domain AS path: domain AS path: domain AS path: domain 14203 2914 5511 2200 1945 2060 I 1, neighbor as: 14203, length 6, segments 14203 2914 7911 14325 14325 14348 I 1, neighbor as: 14203, length 6, segments 14203 2914 701 4637 9230 9230 9230 I 1, neighbor as: 14203, length 7, segments 14203 2914 6395 14 14 14 14 I 1, neighbor as: 14203, length 7, segments 1, references 2 1, references 2 1, references 3 1, references 10 ... 1801 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show as-path domain Syntax Syntax (J-EX Series Switch) Release Information Description Options show as-path domain show as-path domain Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display autonomous system (AS) path domain information. none—(Optional) Display AS path domain information for all routing instances. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show as-path domain on page 1803 Table 211 on page 1802 lists the output fields for the show as-path domain command. Output fields are listed in the approximate order in which they appear Table 211: show as-path domain Output Fields 1802 Field Name Field Description Domain Number of independent AS domains. The AS paths of an independent AS domain are not shared with the AS paths and AS path attributes of other domains, including the master routing instance domain. Primary Primary AS number. References Path reference count. Number Paths Number of known AS paths. Flags Information about the AS path: • ASLoop—Path contains an AS loop. • Atomic—Path includes the ATOMIC_AGGREGATE path attribute. • Local—Path was created by local aggregation. • Master—Path was created by the master routing instance. Local AS AS number of the local routing device. Loops How many times this AS number can appear in an AS path. Chapter 74: Operational Commands for Layer 3 Protocols show as-path domain user@host> show as-path domain Domain: 1 Primary: 10458 References: 3 Paths: Flags: Master Local AS: 10458 Loops: 1 30383 1803 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show as-path summary Syntax Syntax (J-EX Series Switch) Release Information Description Options show as-path summary show as-path summary Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display autonomous system (AS) path summary information. none—(Optional) Display AS path summary information for all routing instances. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show as-path summary on page 1804 Table 212 on page 1804 lists the output fields for the show as-path summary command. Output fields are listed in the approximate order in which they appear. Table 212: show as-path summary Output Fields show as-path summary 1804 Field Name Field Description AS Path AS path number. Buckets Bucket value. This value represents a traffic classification on the interface. Max Maximum limit for the number of AS numbers. Min Minimum limit for the number of AS numbers. Avg Average number of AS numbers. Std deviation Standard deviation for the number of AS numbers. user@host> show as-path summary AS Paths Buckets Max Min 30425 1024 95 12 Avg 29 Std deviation 6.481419 Chapter 74: Operational Commands for Layer 3 Protocols show bgp bmp Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show bgp bmp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the BGP Monitoring Protocol (BMP). This command has no options. view show bgp bmp on page 1805 Table 213 on page 1805 lists the output fields for the show bgp bmp command. Output fields are listed in the approximate order in which they appear. Table 213: show bgp bmp Output Fields show bgp bmp Field Name Field Description BMP station address/port: IP address and port number of monitoring station to which BGP Monitoring Protocol (BMP) statistics are sent. BMP session state Status of the BMP session: UP or DOWN. Memory consumed by BMP Memory used by the active BMP session. Statistics timeout Amount of time, in seconds, between transmissions of BMP data to the monitoring station. Memory limit Threshold, in bytes, at which the routing device stops collecting BMP data if it is exceeded. Memory-connect retry timeout Amount of time, in seconds, after which the routing device attempts to resume a BMP session that was ended after the configured memory threshold was exceeded. user@host> show bgp bmp BMP station address/port: 172.24.24.157+5454 BMP session state: DOWN Memory consumed by BMP: 0 Statistics timeout: 15 Memory limit: 10485760 Memory connect retry timeout: 600 1805 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show bgp group Syntax Syntax (J-EX Series Switch) Release Information Description Options show bgp group show bgp group Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the configured Border Gateway Protocol (BGP) groups. none—Display group information about all BGP groups. brief | detail | summary—(Optional) Display the specified level of output. group-name—(Optional) Display group information for the specified group. instance instance-name—(Optional) Display information about a particular BGP peer in the specified instance. The instance name can be master for the main instance, or any valid configured instance name or its prefix. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. rtf—(Optional) Display BGP group route targeting information. Required Privilege Level List of Sample Output Output Fields view show bgp group on page 1809 show bgp group on page 1810 show bgp group brief on page 1810 show bgp group detail on page 1810 show bgp group rtf detail on page 1811 show bgp group summary on page 1811 show bgp group summary on page 1811 Table 214 on page 1806 describes the output fields for the show bgp group command. Output fields are listed in the approximate order in which they appear. Table 214: show bgp group Output Fields Field Name Field Description Level of Output Group type or Group Type of BGP group: Internal or External. All levels 1806 Chapter 74: Operational Commands for Layer 3 Protocols Table 214: show bgp group Output Fields (continued) Level of Output Field Name Field Description AS AS number of the peer. For internal BGP (IBGP), this number is the same as Local AS. brief detail AS number of the local routing device. brief detail Local AS none none Name Name of a specific BGP group. brief detail none Flags associated with the BGP group. This field is used by Dell Support (see “Requesting Technical Support” on page lxxi). brief detail Export policies configured for the BGP group with the export statement. brief detail MED tracks IGP metric update delay Time interval, in seconds, that updates to multiple exit discriminator (MED) are delayed. Also displays the time remaining before the interval is set to expire All Total peers Total number of peers in the group. brief detail Flags Export none none none Established Number of peers in the group that are in the established state. All levels Active/Received/Accepted/Damped Multipurpose field that displays information about BGP peer sessions. The field’s contents depend upon whether a session is established and whether an established session was established in the main routing device or in a routing instance. summary • If a peer is not established, the field shows the state of the peer session: Active, Connect, or Idle. • If a BGP session is established in the main routing device, the field shows the number of active, received, accepted, and damped routes that are received from a neighbor and appear in the inet.0 (main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the following: • 8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer appear in the inet.0 routing table. • 2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer appear in the inet.2 routing table. ip-addresses List of peers who are members of the group. The address is followed by the peer’s port number. All levels Route Queue Timer Number of seconds until queued routes are sent. If this time has already elapsed, this field displays the number of seconds by which the updates are delayed. detail 1807 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 214: show bgp group Output Fields (continued) Level of Output Field Name Field Description Route Queue Number of prefixes that are queued up for sending to the peers in the group. detail inet.number Number of active, received, accepted, and damped routes in the routing table. For example, inet.0: 7/10/9/0 indicates the following: none • Table inet.number 7 active routes, 10 received routes, 9 accepted routes, and no damped routes from a BGP peer appear in the inet.0 routing table. Information about the routing table. • detail Received prefixes—Total number of prefixes from the peer, both active and inactive, that are in the routing table. • Active prefixes—Number of prefixes received from the peer that are active in the routing table. • Suppressed due to damping—Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols. • Advertised prefixes—Number of prefixes advertised to a peer. • Received external prefixes—Total number of prefixes from the external BGP (EBGP) peers, both active and inactive, that are in the routing table. • Active external prefixes—Number of prefixes received from the EBGP peers that are active in the routing table. • Externals suppressed—Number of routes received from EBGP peers currently inactive because of damping or other reasons. • Received internal prefixes—Total number of prefixes from the IBGP peers, both active and inactive, that are in the routing table. • Active internal prefixes—Number of prefixes received from the IBGP peers that are active in the routing table. • Internals suppressed—Number of routes received from IBGP peers currently inactive because of damping or other reasons. • RIB State—Status of the graceful restart process for this routing table: BGP restart is complete, BGP restart in progress, VPN restart in progress, or VPN restart is complete. Groups Total number of groups. All levels Peers Total number of peers. All levels External Total number of external peers. All levels Internal Total number of internal peers. All levels Down peers Total number of unavailable peers. All levels Flaps Total number of flaps that occurred. All levels Table Name of a routing table. brief, none 1808 Chapter 74: Operational Commands for Layer 3 Protocols Table 214: show bgp group Output Fields (continued) Field Name Field Description Level of Output Tot Paths Total number of paths. brief, none Act Paths Number of active routes. brief, none Suppressed Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols. brief, none History Number of withdrawn routes stored locally to keep track of damping history. brief, none Damp State Number of active routes with a figure of merit greater than zero, but lower than the threshold at which suppression occurs. brief, none Pending Routes being processed by BGP import policy. brief, none Group Group the peer belongs to in the BGP configuration. detail Receive mask Mask of the received target included in the advertised route. detail Entries Number of route entries received. detail Target Route target that is to be passed by route-target filtering. If a route advertised from the provider edge (PE) routing device matches an entry in the route-target filter, the route is passed to the peer. detail Mask Mask which specifies that the peer receive routes with the given route target. detail show bgp group user@host> show bgp group Group Type: Internal AS: 21 Name: from_vpn04_to_other Index: 0 Holdtime: 0 Total peers: 3 Established: 3 10.255.14.178+179 10.255.71.24+179 10.255.14.182+179 inet.0: 2/7/0 Local AS: 21 Flags: <> Group Type: External Name: from_vpn04_to_vpn06 Index: 1 Export: [ internal-and-bgp ] Holdtime: 0 Traffic Statistics Interval: 300 Total peers: 1 Established: 1 100.1.3.2+2910 inet.0: 5/10/0 Groups: 2 Peers: 4 External: 1 Local AS: 21 Flags: Internal: 3 Down peers: 0 Flaps: 2 1809 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table inet.0 show bgp group show bgp group detail Act Paths Suppressed 7 0 user@host> show bgp group Group Type: External Name: as65501peers Index: 0 Export: [ export-policy ] Holdtime: 0 Total peers: 1 Established: 1 192.168.4.222+179 Trace options: all Trace file: /var/log/bgp size 10485760 files 10 inet.0: 7/10/9/0 inet.2: 0/0/0/0 Groups: 1 Table inet.0 inet.2 show bgp group brief Tot Paths 17 Pending 0 Local AS: 65500 Flags: Export Peers: 1 External: 1 Internal: 0 Down peers: 0 Flaps: 0 Tot Paths Act Paths Suppressed History Damp State Pending 10 7 0 0 0 0 0 0 0 0 0 0 The output for the show bgp group brief command is identical to that for the show bgp group command. For sample output, see show bgp group on page 1809. user@host> show bgp group detail Group Type: Internal AS: 21 Name: from_vpn04_to_other Index: 0 Holdtime: 0 Total peers: 3 Established: 3 10.255.14.178+179 10.255.71.24+179 10.255.14.182+179 Route Queue Timer: unset Route Queue: empty Table inet.0 Active prefixes: 2 Received prefixes: 7 Suppressed due to damping: 0 Advertised prefixes: 5 Group Type: External Name: from_vpn04_to_vpn06 Index: 1 Export: [ internal-and-bgp ] Holdtime: 0 Traffic Statistics Interval: 300 Total peers: 1 Established: 1 100.1.3.2+2910 Route Queue Timer: unset Route Queue: empty Table inet.0 Active prefixes: 5 Received prefixes: 10 Suppressed due to damping: 0 Advertised prefixes: 6 Groups: 2 Peers: 4 External: 1 Table inet.0 Received prefixes: 17 Active prefixes: 7 Suppressed due to damping: 0 Received external prefixes: 10 Active external prefixes: 5 1810 History Damp State 0 0 Internal: 3 Local AS: 21 Flags: <> Local AS: 21 Flags: Down peers: 0 Flaps: 2 Chapter 74: Operational Commands for Layer 3 Protocols Externals suppressed: 0 Received internal prefixes: 7 Active internal prefixes: 2 Internals suppressed: 0 RIB State: BGP restart is complete show bgp group rtf detail show bgp group summary user@host> show bgp group rtf detail Group: asbr Receive mask: 00000001 Table: bgp.rtarget.0 Target 109:1/64 109:2/64 701:1/64 10458:2/64 Flags: Filter Mask 00000001 00000001 00000001 00000001 Entries: 4 Group: mesh_0 Receive mask: 0000000e Table: bgp.rtarget.0 Target 109:1/64 701:1/64 701:2/64 10458:1/64 10458:2/64 10458:3/64 10458:5/64 10458:6/64 10458:7/64 10458:8/64 10458:10/64 Flags: Filter Mask 00000002 00000002 00000002 0000000e 00000006 00000006 00000006 00000004 00000008 00000008 00000002 Entries: 12 user@host> show bgp group summary Group Type Peers Established from_vpn04_to_other Internal 3 3 inet.0 : 2/7/0 from_vpn04_to_vpn06 External 1 1 inet.0 : 5/10/0 Groups: 2 inet.0 show bgp group summary Active/Received/Damped Peers: 4 External: 1 Internal: 3 Down peers: 0 : 7/17/0 External: 5/10/0 Internal: 2/7/0 Flaps: 2 user@host> show bgp group summary Group Type Peers Established Active/Received/Accepted/Damped as65501peers External 1 1 Trace options: all Trace file: /var/log/bgp size 10485760 files 10 inet.0 : 7/10/9/0 inet.2 : 0/0/0/0 Groups: 1 inet.0 inet.2 Peers: 1 External: 1 Internal: 0 Down peers: 0 : 7/10/9/0 External: 7/10/9/0 Internal: 0/0/0/0 : 0/0/0/0 External: 0/0/0/0 Internal: 0/0/0/0 Flaps: 0 1811 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show bgp neighbor Syntax Syntax (J-EX Series Switch) Release Information Description Options show bgp neighbor show bgp neighbor Peer: 10.245.245.1+179 AS 200 Local: 10.245.245.3+3770 AS 100 Type: External State: Established Flags: Last State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Options: Address families configured: iso-vpn-unicast Local Address: 10.245.245.3 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 10.245.245.1 Local ID: 10.245.245.3 Active Holdtime: 90 Keepalive Interval: 30 Peer index: 0 NLRI advertised by peer: iso-vpn-unicast NLRI for this session: iso-vpn-unicast Peer supports Refresh capability (2) Table bgp.isovpn.0 Bit: 10000 RIB State: BGP restart is complete RIB State: VPN restart is complete Send state: in sync Active prefixes: 3 Received prefixes: 3 Suppressed due to damping: 0 Advertised prefixes: 3 Table aaaa.iso.0 RIB State: BGP restart is complete RIB State: VPN restart is complete Send state: not advertising Active prefixes: 3 Received prefixes: 3 Suppressed due to damping: 0 Last traffic (seconds): Received 6 Sent 5 Checked 5 Input messages: Total 1736 Updates 4 Refreshes 0 Octets 33385 Output messages: Total 1738 Updates 3 Refreshes 0 Octets 33305 Output Queue[0]: 0 Output Queue[1]: 0 Chapter 74: Operational Commands for Layer 3 Protocols show bgp neighbor (Layer 2 VPN) user@host> show bgp neighbor Peer: 10.69.103.2 AS 65100 Local: 10.69.103.1 AS 65103 Type: External State: Active Flags: Last State: Idle Last Event: Start Last Error: None Export: [ BGP-INET-import ] Options: Address families configured: inet-unicast Local Address: 10.69.103.1 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer: 10.69.104.2 AS 65100 Local: 10.69.104.1 AS 65104 Type: External State: Active Flags: Last State: Idle Last Event: Start Last Error: None Export: [ BGP-L-import ] Options: Address families configured: inet-labeled-unicast Local Address: 10.69.104.1 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer: 10.255.14.182+179 AS 69 Local: 10.255.14.176+2131 AS 69 Type: Internal State: Established Flags: Last State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Options: Address families configured: inet-vpn-unicast l2vpn Local Address: 10.255.14.176 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 10.255.14.182 Local ID: 10.255.14.176 Active Holdtime: 90 Keepalive Interval: 30 NLRI for restart configured on peer: inet-vpn-unicast l2vpn NLRI advertised by peer: inet-vpn-unicast l2vpn NLRI for this session: inet-vpn-unicast l2vpn Peer supports Refresh capability (2) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-vpn-unicast l2vpn NLRI peer can save forwarding state: inet-vpn-unicast l2vpn NLRI that peer saved forwarding for: inet-vpn-unicast l2vpn NLRI that restart is negotiated for: inet-vpn-unicast l2vpn NLRI of received end-of-rib markers: inet-vpn-unicast l2vpn Table bgp.l3vpn.0 Bit: 10000 RIB State: BGP restart in progress RIB State: VPN restart in progress Send state: in sync Active prefixes: 10 Received prefixes: 10 Suppressed due to damping: 0 Table bgp.l2vpn.0 Bit: 20000 RIB State: BGP restart in progress RIB State: VPN restart in progress Send state: in sync Active prefixes: 1 Received prefixes: 1 Suppressed due to damping: 0 Table BGP-INET.inet.0 Bit: 30000 RIB State: BGP restart in progress RIB State: VPN restart in progress 1819 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Send state: in sync Active prefixes: 2 Received prefixes: 2 Suppressed due to damping: 0 Table BGP-L.inet.0 Bit: 40000 RIB State: BGP restart in progress RIB State: VPN restart in progress Send state: in sync Active prefixes: 2 Received prefixes: 2 Suppressed due to damping: 0 Table LDP.inet.0 Bit: 50000 RIB State: BGP restart is complete RIB State: VPN restart in progress Send state: in sync Active prefixes: 1 Received prefixes: 1 Suppressed due to damping: 0 Table OSPF.inet.0 Bit: 60000 RIB State: BGP restart is complete RIB State: VPN restart in progress Send state: in sync Active prefixes: 2 Received prefixes: 2 Suppressed due to damping: 0 Table RIP.inet.0 Bit: 70000 RIB State: BGP restart is complete RIB State: VPN restart in progress Send state: in sync Active prefixes: 2 Received prefixes: 2 Suppressed due to damping: 0 Table STATIC.inet.0 Bit: 80000 RIB State: BGP restart is complete RIB State: VPN restart in progress Send state: in sync Active prefixes: 1 Received prefixes: 1 Suppressed due to damping: 0 Table L2VPN.l2vpn.0 Bit: 90000 RIB State: BGP restart is complete RIB State: VPN restart in progress Send state: in sync Active prefixes: 1 Received prefixes: 1 Suppressed due to damping: 0 Last traffic (seconds): Received 0 Sent 0 Input messages: Total 14 Updates 13 Output messages: Total 3 Updates 0 Output Queue[0]: 0 Output Queue[1]: 0 Output Queue[2]: 0 Output Queue[3]: 0 Output Queue[4]: 0 Output Queue[5]: 0 Output Queue[6]: 0 Output Queue[7]: 0 Output Queue[8]: 0 show bgp neighbor (Layer 3 VPN) 1820 user@host> show bgp neighbor Checked 0 Refreshes 0 Refreshes 0 Octets 1053 Octets 105 Chapter 74: Operational Commands for Layer 3 Protocols Peer: 4.4.4.4+179 AS 10045 Local: 5.5.5.5+1214 AS 10045 Type: Internal State: Established Flags: Last State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Export: [ match-all ] Import: [ match-all ] Options: Address families configured: inet-vpn-unicast Local Address: 5.5.5.5 Holdtime: 90 Preference: 170 Flags for NLRI inet-labeled-unicast: TrafficStatistics Traffic Statistics: Options: all File: /var/log/bstat.log size 131072 files 10 Traffic Statistics Interval: 60 Number of flaps: 0 Peer ID: 192.168.1.110 Local ID: 192.168.1.111 Active Holdtime: 90 Keepalive Interval: 30 NLRI for restart configured on peer: inet-vpn-unicast NLRI advertised by peer: inet-vpn-unicast NLRI for this session: inet-vpn-unicast Peer supports Refresh capability (2) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-vpn-unicast NLRI peer can save forwarding state: inet-vpn-unicast NLRI that peer saved forwarding for: inet-vpn-unicast NLRI that restart is negotiated for: inet-vpn-unicast NLRI of received end-of-rib markers: inet-vpn-unicast NLRI of all end-of-rib markers sent: inet-vpn-unicast Table bgp.l3vpn.0 Bit: 10000 RIB State: BGP restart is complete RIB State: VPN restart is complete Send state: in sync Active prefixes: 2 Received prefixes: 2 Suppressed due to damping: 0 Table vpn-green.inet.0 Bit: 20001 RIB State: BGP restart is complete RIB State: VPN restart is complete Send state: in sync Active prefixes: 2 Received prefixes: 2 Suppressed due to damping: 0 Last traffic (seconds): Received 15 Sent 20 Checked 20 Input messages: Total 40 Updates 2 Refreshes 0 Octets 856 Output messages: Total 44 Updates 2 Refreshes 0 Octets 1066 Output Queue[0]: 0 Output Queue[1]: 0 Trace options: detail packets Trace file: /var/log/bgpgr.log size 131072 files 10 show bgp neighbor neighbor-address user@host> show bgp neighbor 192.168.1.111 Peer: 10.255.245.12+179 AS 35 Local: 10.255.245.13+2884 AS 35 Type: Internal State: Established (route reflector client)Flags: Last State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Options: Address families configured: inet-vpn-unicast inet-labeled-unicast Local Address: 10.255.245.13 Holdtime: 90 Preference: 170 Flags for NLRI inet-vpn-unicast: AggregateLabel 1821 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Flags for NLRI inet-labeled-unicast: AggregateLabel Number of flaps: 0 Peer ID: 10.255.245.12 Local ID: 10.255.245.13 Active Holdtime: 90 Keepalive Interval: 30 BFD: disabled NLRI advertised by peer: inet-vpn-unicast inet-labeled-unicast NLRI for this session: inet-vpn-unicast inet-labeled-unicast Peer supports Refresh capability (2) Restart time configured on the peer: 300 Stale routes from peer are kept for: 60 Restart time requested by this peer: 300 NLRI that peer supports restart for: inet-unicast inet6-unicast NLRI that restart is negotiated for: inet-unicast inet6-unicast NLRI of received end-of-rib markers: inet-unicast inet6-unicast NLRI of all end-of-rib markers sent: inet-unicast inet6-unicast Table inet.0 Bit: 10000 RIB State: restart is complete Send state: in sync Active prefixes: 4 Received prefixes: 6 Suppressed due to damping: 0 Table inet6.0 Bit: 20000 RIB State: restart is complete Send state: in sync Active prefixes: 0 Received prefixes: 2 Suppressed due to damping: 0 Last traffic (seconds): Received 3 Sent 3 Checked 3 Input messages: Total 9 Updates 6 Refreshes 0 Octets 403 Output messages: Total 7 Updates 3 Refreshes 0 Octets 365 Output Queue[0]: 0 Output Queue[1]: 0 Trace options: detail packets Trace file: /var/log/bgpgr size 131072 files 10 show bgp neighbor neighbor-address 1822 user@host> show bgp neighbor 192.168.4.222 Peer: 192.168.4.222+4902 AS 65501 Local: 192.168.4.221+179 AS 65500 Type: External State: Established Flags: Last State: OpenConfirm Last Event: RecvKeepAlive Last Error: Cease Export: [ export-policy ] Import: [ import-policy ] Options: Address families configured: inet-unicast inet-multicast Holdtime: 60000 Preference: 170 Number of flaps: 4 Last flap event: RecvUpdate Error: 'Cease' Sent: 5 Recv: 0 Peer ID: 10.255.245.6 Local ID: 10.255.245.5 Active Holdtime: 60000 Keepalive Interval: 20000 Peer index: 0 BFD: disabled, down Local Interface: fxp0.0 NLRI advertised by peer: inet-unicast inet-multicast NLRI for this session: inet-unicast inet-multicast Peer supports Refresh capability (2) Table inet.0 Bit: 10000 RIB State: BGP restart is complete Send state: in sync Active prefixes: 8 Received prefixes: 10 Accepted prefixes: 10 Suppressed due to damping: 0 Chapter 74: Operational Commands for Layer 3 Protocols Advertised prefixes: 3 Table inet.2 Bit: 20000 RIB State: BGP restart is complete Send state: in sync Active prefixes: 0 Received prefixes: 0 Accepted prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Last traffic (seconds): Received 357 Sent 357 Checked 357 Input messages: Total 4 Updates 2 Refreshes 0 Octets 211 Output messages: Total 4 Updates 1 Refreshes 0 Octets 147 Output Queue[0]: 0 Output Queue[1]: 0 Trace options: all Trace file: /var/log/bgp size 10485760 files 10 show bgp neighbor orf neighbor-address detail user@host > show bgp neighbor orf 192.168.165.56 detail Peer: 192.168.165.56+179 Type: External Group: ext1 inet-unicast Filter updates recv: 1 Immediate: 1 Filter: prefix-based receive Received filter entries: seq 1: prefix 2.2.2.2/32: minlen 32: maxlen 32: match deny: inet6-unicast Filter updates recv: 0 Immediate: Filter: prefix-based receive Received filter entries: *:* 1 1823 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show bgp summary Syntax Syntax (J-EX Series Switch) Release Information Description Options show bgp summary show bgp summary Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Border Gateway Protocol (BGP) summary information. none—Display BGP summary information for all routing instances. instance instance-name—(Optional) Display information for the specified instance only. The instance name can be master for the main instance, or any valid configured instance name or its prefix. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show bgp summary (When a Peer Is Not Established) on page 1826 show bgp summary (When a Peer Is Established) on page 1826 show bgp summary (CLNS) on page 1826 show bgp summary (Layer 2 VPN) on page 1826 show bgp summary (Layer 3 VPN) on page 1827 Table 216 on page 1824 describes the output fields for the show bgp summary command. Output fields are listed in the approximate order in which they appear. Table 216: show bgp summary Output Fields Field Name Field Description Groups Number of BGP groups. Peers Number of BGP peers. Down peers Number of down BGP peers. Table Name of routing table. Tot Paths Total number of paths. Act Paths Number of active routes. Suppressed Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols. 1824 Chapter 74: Operational Commands for Layer 3 Protocols Table 216: show bgp summary Output Fields (continued) Field Name Field Description History Number of withdrawn routes stored locally to keep track of damping history. Damp State Number of routes with a figure of merit greater than zero, but still active because the value has not reached the threshold at which suppression occurs. Pending Routes in process by BGP import policy. Peer Address of each BGP peer. Each peer has one line of output. AS Peer's AS number. InPkt Number of packets received from the peer. OutPkt Number of packets sent to the peer. OutQ Count of the number of BGP packets that are queued to be transmitted to a particular neighbor. It normally is 0 because the queue usually is emptied quickly. Flaps Number of times the BGP session has gone down and then come back up. Last Up/Down Last time since the neighbor transitioned to or from the established state. State|#Active /Received/Accepted /Damped Multipurpose field that displays information about BGP peer sessions. The field’s contents depend upon whether a session is established and whether an established session was established in the main routing device or in a routing instance. • If a peer is not established, the field shows the state of the peer session: Active, Connect, or Idle. • If a BGP session is established in the main routing device, the field shows the number of active, received, accepted, and damped routes that are received from a neighbor and appear in the inet.0 (main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the following: • • 8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer appear in the inet.0 routing table. • 2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer appear in the inet.2 routing table. If a BGP session is established in a routing instance, the field indicates the established (Establ) state, identifies the specific routing table that receives BGP updates, and shows the number of active, received, and damped routes that are received from a neighbor. For example, Establ VPN-AB.inet.0: 2/4/0 indicates the following: • The BGP session is established. • Routes are received in the VPN-AB.inet.0 routing table. • The local routing device has two active routes, four received routes, and no damped routes from a BGP peer. When a BGP session is established, the peers are exchanging update messages. 1825 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show bgp summary (When a Peer Is Not Established) user@host> show bgp summary Groups: 2 Peers: 4 Down peers: 1 Table Tot Paths Act Paths Suppressed History Damp State Pending inet.0 6 4 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Damped... 10.0.0.3 65002 86 90 0 2 42:54 0/0/0 0/0/0 10.0.0.4 65002 90 91 0 1 42:54 0/2/0 0/0/0 10.0.0.6 10.1.12.1 65002 65001 87 89 90 89 0 0 3 1 3 Active 42:54 4/4/0 0/0/0 show bgp summary (When a Peer Is Established) user@host> show bgp summary Groups: 1 Peers: 3 Down peers: 0 Table Tot Paths Act Paths Suppressed History Damp State Pending inet.0 6 4 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Damped... 10.0.0.2 65002 88675 88652 0 2 42:38 2/4/0 0/0/0 10.0.0.3 65002 54528 54532 0 1 2w4d22h 0/0/0 0/0/0 10.0.0.4 65002 51597 51584 0 0 2w3d22h 2/2/0 OutPkt OutQ 1737 0 0/0/0 show bgp summary (CLNS) show bgp summary (Layer 2 VPN) 1826 user@host> show bgp summary Groups: 1 Peers: 1 Down peers: 0 Peer AS InPkt State|#Active/Received/Damped... 10.245.245.1 200 1735 bgp.isovpn.0: 3/3/0 aaaa.iso.0: 3/3/0 Flaps Last Up/Dwn 0 14:26:12 Establ user@host> show bgp summary Groups: 1 Peers: 5 Down peers: 0 Table Tot Paths Act Paths Suppressed History Damp State bgp.l2vpn.0 1 1 0 0 0 inet.0 0 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Damped... 10.255.245.35 65299 72 74 0 1 19:00 bgp.l2vpn.0: 1/1/0 frame-vpn.l2vpn.0: 1/1/0 10.255.245.36 65299 2164 2423 0 4 19:50 bgp.l2vpn.0: 0/0/0 frame-vpn.l2vpn.0: 0/0/0 10.255.245.37 65299 36 37 0 4 17:07 inet.0: 0/0/0 10.255.245.39 65299 138 168 0 6 53:48 bgp.l2vpn.0: 0/0/0 frame-vpn.l2vpn.0: 0/0/0 Pending 0 0 Establ Establ Establ Establ Chapter 74: Operational Commands for Layer 3 Protocols 10.255.245.69 65299 inet.0: 0/0/0 show bgp summary (Layer 3 VPN) 134 140 0 6 53:42 Establ user@host> show bgp summary Groups: 2 Peers: 2 Down peers: 0 Table Tot Paths Act Paths Suppressed History Damp State Pending bgp.l3vpn.0 2 2 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Damped... 10.39.1.5 2 21 22 0 0 6:26 Establ VPN-AB.inet.0: 1/1/0 10.255.71.15 1 19 21 0 0 6:17 Establ bgp.l3vpn.0: 2/2/0 VPN-A.inet.0: 1/1/0 VPN-AB.inet.0: 2/2/0 VPN-B.inet.0: 1/1/0 1827 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ipv6 neighbors Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show ipv6 neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the IPv6 neighbor cache. This command has no options. view • clear ipv6 neighbors on page 990 show ipv6 neighbors on page 1828 show ipv6 neighbors on page 1828 Table 217 on page 1828 describes the output fields for the show ipv6 neighbors command. Output fields are listed in the approximate order in which they appear. Table 217: show ipv6 neighbors Output Fields show ipv6 neighbors show ipv6 neighbors 1828 Field Name Field Description IPv6 Address Name of the IPv6 interface. Linklayer Address Link-layer address. State State of the link: up, down, incomplete, reachable, stale, or unreachable. Exp Number of seconds until the entry expires. Rtr Whether the neighbor is a routing device: yes or no. Secure Whether this entry was created using the Secure Neighbor Discovery (SEND) protocol: yes or no. Interface Name of the interface. user@host> show ipv6 neighbors IPv6 Address Linklayer Address fe80::2a0:c9ff:fe5b:4c1e 00:a0:c9:5b:4c:1e user@host > show ipv6 neighbors IPv6 Address Linklayer Address Interface State reachable Exp 15 Rtr yes Interface fxp0.0 State Exp Rtr Secure Chapter 74: Operational Commands for Layer 3 Protocols fe80::14fb:5dcf:54bd:ff76 ge-3/2/0.0 00:90:69:a0:a8:bc stale 1113 yes yes 1829 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis adjacency Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis adjacency show isis adjacency Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Intermediate System-to-Intermediate System (IS-IS) neighbors. none—Display standard information about IS-IS neighbors for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. instance instance-name—(Optional) Display adjacencies for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear isis adjacency on page 1760 show isis adjacency on page 1832 show isis adjacency brief on page 1832 show isis adjacency detail on page 1832 show isis adjacency extensive on page 1833 Table 218 on page 1830 describes the output fields for the show isis adjacency command. Output fields are listed in the approximate order in which they appear. Table 218: show isis adjacency Output Fields Field Name Field Description Level of Output Interface Interface through which the neighbor is reachable. All levels System System identifier (sysid), displayed as a name, if possible. brief 1830 Chapter 74: Operational Commands for Layer 3 Protocols Table 218: show isis adjacency Output Fields (continued) Field Name Field Description Level of Output L or Level Level: All levels • 1—Level 1 only • 2—Level 2 only • 3—Level 1 and Level 2 An exclamation point (!) preceding the level number indicates that the adjacency is missing an IP address. State State of the adjacency: Up, Down, New, One-way, Initializing, or Rejected. All levels Hold (secs) Remaining hold time of the adjacency. brief SNPA Subnetwork point of attachment (MAC address of the next hop). brief Expires in How long until the adjacency expires, in seconds. detail Priority Priority to become the designated intermediate system. detail extensive Up/Down transitions Count of adjacency status changes from Up to Down or from Down to Up. detail Last transition Time of the last Up/Down transition. detail Circuit type Bit mask of levels on this interface: L1=Level 1 router; L2=Level 2 router; L1/L2=both Level 1 and Level 2 router. detail Speaks Protocols supported by this neighbor. detail extensive MAC address MAC address of the interface. detail extensive Topologies Supported topologies. detail extensive Restart capable Whether a neighbor is capable of graceful restart: Yes or No. detail extensive Adjacency advertisement: Advertise This router has signaled not to advertise this interface to its neighbors in their label-switched paths (LSPs). detail extensive Adjacency advertisement: Suppress This neighbor has signaled not to advertise the interface in the router's outbound LSPs. detail extensive IP addresses IP address of this neighbor. detail extensive 1831 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 218: show isis adjacency Output Fields (continued) Field Name Field Description Level of Output Transition log List of recent transitions, including: extensive • When—Time at which an IS-IS adjacency transition occurred. • State—Current state of the IS-IS adjacency (up, down, or rejected). • • • Up—Adjacency is up and operational. • Down—Adjacency is down and not available. • Rejected—Adjacency has been rejected. Event—Type of transition that occurred. • Seenself—Possible routing loop has been detected. • Interface down—IS-IS interface has gone down and is no longer available. • Error—Adjacency error. Down reason—Reason that an IS-IS adjacency is down: • 3-Way Handshake Failed—Connection establishment failed. • Address Mismatch—Address mismatch caused link failure. • Aged Out—Link expired. • ISO Area Mismatch—IS-IS area mismatch caused link failure. • Bad Hello—Unacceptable hello message caused link failure. • BFD Session Down—Bidirectional failure detection caused link failure. • Interface Disabled—IS-IS interface is disabled. • Interface Down—IS-IS interface is unavailable. • Interface Level Disabled—IS-IS level is disabled. • Level Changed—IS-IS level has changed on the adjacency. • Level Mismatch—Levels on adjacency are not compatible. • MPLS LSP Down—Label-switched path (LSP) is unavailable. • MT Topology Changed—IS-IS topology has changed. • MT Topology Mismatch—IS-IS topology is mismatched. • Remote System ID Changed—Adjacency peer system ID changed. • Protocol Shutdown—IS-IS protocol is disabled. • CLI Command—Adjacency brought down by user. • Unknown—Unknown. show isis adjacency user@host> show isis adjacency Interface System at-2/3/0.0 ranier L State 3 Up Hold (secs) SNPA 23 show isis adjacency brief The output for the show isis adjacency brief command is identical to that for the show isis adjacency command. For sample output, see show isis adjacency on page 1832. show isis adjacency detail user@host> show isis adjacency detail ranier Interface: at-2/3/0.0, Level: 3, State: Up, Expires in 21 secs Priority: 0, Up/Down transitions: 1, Last transition: 00:01:09 ago Circuit type: 3, Speaks: IP, IPv6 Topologies: Unicast 1832 Chapter 74: Operational Commands for Layer 3 Protocols Restart capable: Yes IP addresses: 11.1.1.2 show isis adjacency extensive user@host> show isis adjacency extensive ranier Interface: at-2/3/0.0, Level: 3, State: Up, Expires in 22 secs Priority: 0, Up/Down transitions: 1, Last transition: 00:01:16 ago Circuit type: 3, Speaks: IP, IPv6 Topologies: Unicast Restart capable: Yes IP addresses: 11.1.1.2 Transition log: When State Event Down reason Wed Nov 8 21:24:25 Up Seenself 1833 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis authentication Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis authentication show isis authentication Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Intermediate System-to-Intermediate System (IS-IS) authentication. none—Display information about IS-IS authentication. brief | detail | extensive—(Optional) Display the specified level of output. instance instance-name—(Optional) Display IS-IS authentication for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show isis authentication on page 1835 Table 219 on page 1834 describes the output fields for the show isis authentication command. Output fields are listed in the approximate order in which they appear. Table 219: show isis authentication Output Fields 1834 Field Name Field Description Interface Interface name. Level IS-IS level. IIH Auth IS-IS Hello (IIH) packet authentication type. CSN Auth Complete sequence number authentication type. PSN Auth Partial sequence number authentication type. L1 LSP Authentication Layer 1 link-state PDU authentication type. Chapter 74: Operational Commands for Layer 3 Protocols Table 219: show isis authentication Output Fields (continued) show isis authentication Field Name Field Description L2 LSP Authentication Layer 2 link-state PDU authentication type. user@host> show isis authentication Interface Level IIH Auth at-2/3/0.0 1 Simple 2 MD5 CSN Auth Simple MD5 PSN Auth Simple MD5 L1 LSP Authentication: Simple L2 LSP Authentication: MD5 1835 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis backup coverage Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis backup coverage show isis backup coverage Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the level of backup coverage available. none—Display information about the level of backup coverage available for all the nodes and prefixes in the network. instance instance-name—(Optional) Display information about the level of backup coverage for a specific IS-IS routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show isis backup label-switched-path on page 1838 show isis backup coverage on page 1837 Table 220 on page 1836 lists the output fields for the show isis backup coverage command. Output fields are listed in the approximate order in which they appear. Table 220: show isis backup coverage Output Fields 1836 Field Name Field Description Topology Type of topology or address family: IPV4 Unicast or IPV6 Unicast. Level IS-IS level: • 1—Level 1 • 2—Level 2 Node By topology, the percentage of all routes configured on the node that are protected through backup coverage. IPv4 Unicast Percentage of IPv4 unicast routes that are protected through backup coverage. IPv6 Unicast Percentage of IPv6 unicast routes that are protected through backup coverage. Chapter 74: Operational Commands for Layer 3 Protocols Table 220: show isis backup coverage Output Fields (continued) show isis backup coverage Field Name Field Description CLNS Percentage of Connectionless Network Service (CLNS) routes that are protected through backup coverage. user@host> show isis backup coverage Backup Coverage: Topology Level Node IPV4 Unicast 2 28.57% IPV6 Unicast 2 0.00% IPv4 22.22% 0.00% IPv6 0.00% 0.00% CLNS 0.00% 0.00% 1837 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis backup label-switched-path Syntax show isis backup label-switched-path Syntax (J-EX Series Switch) show isis backup label-switched-path Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display information about MPLS label-switched-paths (LSPs) designated as backup routes for IS-IS routes. Options none—Display information about MPLS LSPs designated as backup routes for IS-IS routes. logical-system (all | logical-system-name—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level view Related Documentation • List of Sample Output show isis backup coverage on page 1836 show isis backup label-switched-path on page 1839 Output Fields Table 221 on page 1838 lists the output fields for the show isis backup label-switched-path command. Output fields are listed in the approximate order in which they appear. Table 221: show isis backup label-switched-path Output Fields Field Name Field Description Backup MPLS LSPs List of MPLS LSPs designated as backup paths for IS-IS routes. Egress IP address of the egress routing device for the LSP. Status State of the LSP: • Up—The router can detect RSVP hello messages from the neighbor. • Down—The router has received one of the following indications: • • Communication failure from the neighbor. • Communication from IGP that the neighbor is unavailable. • Change in the sequence numbers in the RSVP hello messages sent by the neighbor. Deleted—LSP is no longer available as a backup path. Last change Time elapsed since the neighbor state changed either from up or down or from down to up. The format is hh:mm:ss. TE-metric Configured traffic engineering metric. 1838 Chapter 74: Operational Commands for Layer 3 Protocols Table 221: show isis backup label-switched-path Output Fields (continued) Field Name Field Description Metric Configured metric. show isis backup label-switched-path user@host> show isis backup label-switched-path Backup MPLS LSPs: f-to-g, Egress: 192.168.1.4, Status: up, Last change: 06:12:03 TE-metric: 9, Metric: 0 1839 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis backup spf results Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis backup spf results show isis backup spf results Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about IS-IS shortest-path-first (SPF) calculations for backup paths. none—Display information about IS-IS shortest-path-first (SPF) calculations for all backup paths for all destination nodes. instance instance-name—(Optional) Display SPF calculations for backup paths for the specified routing instance. level (1 | 2)—(Optional) Display SPF calculations for the backup paths for the specified IS-IS level. logical-system logical-system-name—(Optional) Display SPF calculations for the backup paths for all logical systems or on a particular logical system. no-coverage—(Optional) Display SPF calculations only for destinations that do not have backup coverage. topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)—(Optional) Display SPF calculations for backup paths for the specified topology only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show isis backup coverage on page 1836 show isis backup spf results on page 1841 Table 222 on page 1840 lists the output fields for the show isis backup spf results command. Output fields are listed in the approximate order in which they appear. Table 222: show isis backup spf results Output Fields 1840 Field Name Field Description node-name Name of the destination node. Chapter 74: Operational Commands for Layer 3 Protocols Table 222: show isis backup spf results Output Fields (continued) show isis backup spf results Field Name Field Description Address Address of the destination node. Primary next-hop Interface and name of the node of the primary next hop to reach the destination. Root Name of the next-hop neighbor. Metric Metric to the node. Eligible Indicates that the next-hop neighbor has been designated as a backup path to the destination node. Backup next-hop Name of the interface of the backup next hop. SNPA Subnetwork point of attachment (MAC address of the next hop). LSP Name of the MPLS LSP designated as a backup path. Not eligible Indicates that the next-hop neighbor cannot function as a backup path to the destination. Reason Describes why the next-hop neighbor is designated as Not eligible as a backup path. user@host> show isis backup spf results IS-IS level 1 SPF results: 0 nodes IS-IS level 2 SPF results: kobuk.00, Address 0x8d85600 Primary next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Primary next-hop: so-0/1/2.0, crater Primary next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Primary next-hop: so-0/1/2.0, crater Root: crater, Metric: 10 Not eligible, Reason: Primary next-hop multipath Root: camaro, Metric: 10 Not eligible, Reason: Primary next-hop multipath Root: olympic, Metric: 25 Not eligible, Reason: Primary next-hop multipath glacier.00, Address 0x8d85200 Primary next-hop: so-0/1/2.0, crater Primary next-hop: so-0/1/2.0, crater Root: crater, Metric: 10 Not eligible, Reason: Primary next-hop link fate sharing Root: olympic, Metric: 15 Eligible, Backup next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Eligible, Backup next-hop: so-1/0/2.0, olympic Eligible, Backup next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Eligible, Backup next-hop: so-1/0/2.0, olympic Root: camaro, Metric: 20 1841 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Eligible, Backup next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Eligible, Backup next-hop: so-1/0/2.0, olympic Eligible, Backup next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Eligible, Backup next-hop: so-1/0/2.0, olympic olympic.00, Address 0x8d00c00 Primary next-hop: so-1/0/2.0, olympic Primary next-hop: so-1/0/2.0, olympic Root: olympic, Metric: 0 Not eligible, Reason: Primary next-hop link fate sharing Root: crater, Metric: 20 track-item: olympic.00-00 track-item: banff.00-00 Not eligible, Reason: Path loops Root: camaro, Metric: 20 track-item: olympic.00-00 track-item: banff.00-00 Not eligible, Reason: Path loops camaro.00, Address 0x8d85a00 Primary next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Primary next-hop: ge-0/2/0.0, camaro, SNPA: 0:90:69:f:62:fa Root: camaro, Metric: 0 Not eligible, Reason: Primary next-hop link fate sharing Root: crater, Metric: 20 track-item: camaro.00-00 track-item: banff.00-00 Not eligible, Reason: Path loops Root: olympic, Metric: 20 track-item: camaro.00-00 track-item: banff.00-00 Not eligible, Reason: Path loops crater.00, Address 0x8d85000 Primary next-hop: so-0/1/2.0, crater Primary next-hop: so-0/1/2.0, crater Root: crater, Metric: 0 Not eligible, Reason: Primary next-hop link fate sharing Root: camaro, Metric: 20 track-item: crater.00-00 track-item: banff.00-00 Not eligible, Reason: Path loops Root: olympic, Metric: 20 track-item: crater.00-00 track-item: banff.00-00 Not eligible, Reason: Path loops 5 nodes 1842 Chapter 74: Operational Commands for Layer 3 Protocols show isis database Syntax Syntax (J-EX Series Switch) Release Information show isis database show isis database Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the entries in the Intermediate System-to-Intermediate System (IS-IS) link-state database, which contains data about PDU packets. Options none—Display standard information about IS-IS link-state database entries for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. instance instance-name—(Optional) Display entries for the specified routing instance. level (1 | 2)—(Optional) Display entries for the specified IS-IS level. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear isis database on page 1762 show isis database on page 1845 show isis database brief on page 1845 show isis database detail on page 1846 show isis database extensive on page 1847 show isis database extensive (CLNS) on page 1848 Table 223 on page 1844 describes the output fields for the show isis database command. Output fields are listed in the approximate order in which they appear. Fields that contain internal IS-IS information useful only in troubleshooting obscure problems are not described in the table. For more details about these fields, contact your customer support representative. 1843 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 223: show isis database Output Fields Field Name Field Description Level of Output Interface name Name of the interface on which the LSP has been received; always IS-IS for this command. All levels level Level of intermediate system: All levels • 1—Intermediate system routes within an area; when the destination is outside an area, it routes toward a Level 2 system. • 2—Intermediate system routes between areas and toward other ASs. LSP ID Link-state PDU identifier. All levels Sequence Sequence number of the link-state PDU. All levels Checksum Checksum value of the link-state PDU. All levels Lifetime (secs) Remaining lifetime of the link-state PDU, in seconds. All levels Attributes Attributes of the specified database: L1, L2, Overload, or Attached (L1 only). none brief # LSPs Total number of LSPs in the specified link-state database. none brief IP prefix Prefix advertised by this link-state PDU. detail extensive IS neighbor IS-IS neighbor of the advertising system. detail extensive ES neighbor (J Series routers only) An ES-IS neighbor of the advertising system. detail extensive IP prefix IPv4 prefix advertised by this link-state PDU. detail extensive V6 prefix IPv6 prefix advertised by this link-state PDU. detail extensive Metric Metric of the prefix or neighbor. detail extensive Header • LSP ID—Link state PDU identifier of the header. extensive • Length—Header length. • Allocated Length—Amount of length available for the header. • Router ID—Address of the local routing device. • Remaining Lifetime—Remaining lifetime of the link-state PDU, in seconds. 1844 Chapter 74: Operational Commands for Layer 3 Protocols Table 223: show isis database Output Fields (continued) Field Name Field Description Level of Output Packet • LSP ID—The identifier for the link-state packet. extensive • Length—Packet length. • Lifetime—Remaining lifetime, in seconds. • Checksum—The checksum of the LSP. • Sequence—The sequence number of the LSP. Every time the LSP is updated, this number increments. TLVs • Attributes—Packet attributes. • NLPID—Network layer protocol identifier. • Fixed length—Specifies the set length for the packet. • Area Address—Area addresses that the routing device can reach. • Speaks—Supported routing protocols. • IP router id—ID of the routing device (usually the IP address). • IP address—IPv4 address. • Hostname—Assigned name of the routing device. • IP prefix—IP prefix of the routing device. • Metric—IS-IS metric that measures the cost of the adjacency between the extensive originating routing device and the advertised routing device. • IP extended prefix—Extended IP prefix of the routing device. • IS neighbor—Directly attached neighbor’s name and metric. • IS extended neighbor—Directly attached neighbor’s name, metric, and IP address. show isis database user@host> show isis database IS-IS level 1 link-state database: LSP ID Sequence Checksum Lifetime Attributes kobuk.00-00 0x3 0x3167 1057 L1 L2 camaro.00-00 0x5 0x770e 1091 L1 L2 ranier.00-00 0x4 0xaa95 1091 L1 L2 glacier.00-00 0x4 0x206f 1089 L1 L2 glacier.02-00 0x1 0xd141 1089 L1 L2 badlands.00-00 0x3 0x87a2 1093 L1 L2 6 LSPs IS-IS level 2 link-state database: LSP ID Sequence Checksum Lifetime Attributes kobuk.00-00 0x6 0x8d6b 1096 L1 L2 camaro.00-00 0x9 0x877b 1101 L1 L2 ranier.00-00 0x8 0x855d 1103 L1 L2 glacier.00-00 0x7 0xf892 1098 L1 L2 glacier.02-00 0x1 0xd141 1089 L1 L2 badlands.00-00 0x6 0x562 1105 L1 L2 6 LSPs show isis database brief The output for the show isis database brief command is identical to that for the show isis database command. For sample output, see show isis database on page 1845. 1845 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis database detail user@host> show isis database detail IS-IS level 1 link-state database: kobuk.00-00 Sequence: 0x3, Checksum: 0x3167, Lifetime: 1048 secs IS neighbor: glacier.00 Metric: 10 IP prefix: 10.255.70.103/32 Metric: 0 Internal Up IP prefix: 43.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:70:103/128 Metric: 0 Internal Up camaro.00-00 Sequence: 0x5, Checksum: 0x770e, Lifetime: 1082 secs IS neighbor: ranier.00 Metric: 10 IS neighbor: glacier.02 Metric: 10 IP prefix: 10.255.71.52/32 Metric: 0 Internal Up IP prefix: 23.1.1.0/24 Metric: 10 Internal Up IP prefix: 34.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:71:52/128 Metric: 0 Internal Up ranier.00-00 Sequence: 0x4, Checksum: 0xaa95, Lifetime: 1082 secs IS neighbor: camaro.00 Metric: 10 IS neighbor: badlands.00 Metric: 10 IP prefix: 10.255.71.241/32 Metric: 0 Internal Up IP prefix: 11.1.1.0/24 Metric: 10 Internal Up IP prefix: 23.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:71:241/128 Metric: 0 Internal Up glacier.00-00 Sequence: 0x4, Checksum: 0x206f, Lifetime: 1080 secs IS neighbor: kobuk.00 Metric: 10 IS neighbor: glacier.02 Metric: 10 IP prefix: 10.255.71.242/32 Metric: 0 Internal Up IP prefix: 34.1.1.0/24 Metric: 10 Internal Up IP prefix: 43.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:71:242/128 Metric: 0 Internal Up glacier.02-00 Sequence: 0x1, Checksum: 0xd141, Lifetime: 1080 secs IS neighbor: camaro.00 Metric: 0 IS neighbor: glacier.00 Metric: 0 badlands.00-00 Sequence: 0x3, Checksum: 0x87a2, Lifetime: 1084 secs IS neighbor: ranier.00 Metric: 10 IP prefix: 10.255.71.244/32 Metric: 0 Internal Up IP prefix: 11.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:71:244/128 Metric: 0 Internal Up IS-IS level 2 link-state database: kobuk.00-00 Sequence: 0x6, Checksum: 0x8d6b, Lifetime: 1088 secs IS neighbor: glacier.00 Metric: 10 IP prefix: 10.255.70.103/32 Metric: 0 Internal Up IP prefix: 10.255.71.52/32 Metric: 20 Internal Up IP prefix: 10.255.71.241/32 Metric: 30 Internal Up IP prefix: 10.255.71.242/32 Metric: 10 Internal Up IP prefix: 10.255.71.244/32 Metric: 40 Internal Up IP prefix: 11.1.1.0/24 Metric: 40 Internal Up IP prefix: 23.1.1.0/24 Metric: 30 Internal Up IP prefix: 34.1.1.0/24 Metric: 20 Internal Up IP prefix: 43.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:70:103/128 Metric: 0 Internal Up camaro.00-00 Sequence: 0x9, Checksum: 0x877b, Lifetime: 1092 secs IS neighbor: ranier.00 Metric: 10 IS neighbor: glacier.02 Metric: 10 1846 Chapter 74: Operational Commands for Layer 3 Protocols IP IP IP IP IP IP IP IP IP V6 prefix: prefix: prefix: prefix: prefix: prefix: prefix: prefix: prefix: prefix: 10.255.70.103/32 10.255.71.52/32 10.255.71.241/32 10.255.71.242/32 10.255.71.244/32 11.1.1.0/24 23.1.1.0/24 34.1.1.0/24 43.1.1.0/24 abcd::10:255:71:52/128 Metric: Metric: Metric: Metric: Metric: Metric: Metric: Metric: Metric: Metric: 20 0 10 10 20 20 10 10 20 0 Internal Internal Internal Internal Internal Internal Internal Internal Internal Internal Up Up Up Up Up Up Up Up Up Up ranier.00-00 Sequence: 0x8, Checksum: 0x855d, Lifetime: 1094 secs IS neighbor: camaro.00 Metric: 10 IS neighbor: badlands.00 Metric: 10 IP prefix: 10.255.70.103/32 Metric: 30 Internal Up IP prefix: 10.255.71.52/32 Metric: 10 Internal Up IP prefix: 10.255.71.241/32 Metric: 0 Internal Up IP prefix: 10.255.71.242/32 Metric: 20 Internal Up IP prefix: 10.255.71.244/32 Metric: 10 Internal Up IP prefix: 11.1.1.0/24 Metric: 10 Internal Up IP prefix: 23.1.1.0/24 Metric: 10 Internal Up IP prefix: 34.1.1.0/24 Metric: 20 Internal Up IP prefix: 43.1.1.0/24 Metric: 30 Internal Up V6 prefix: abcd::10:255:71:241/128 Metric: 0 Internal Up glacier.00-00 Sequence: 0x7, Checksum: 0xf892, Lifetime: 1089 secs IS neighbor: kobuk.00 Metric: 10 IS neighbor: glacier.02 Metric: 10 IP prefix: 10.255.70.103/32 Metric: 10 Internal Up IP prefix: 10.255.71.52/32 Metric: 10 Internal Up IP prefix: 10.255.71.241/32 Metric: 20 Internal Up IP prefix: 10.255.71.242/32 Metric: 0 Internal Up IP prefix: 10.255.71.244/32 Metric: 30 Internal Up IP prefix: 11.1.1.0/24 Metric: 30 Internal Up IP prefix: 23.1.1.0/24 Metric: 20 Internal Up IP prefix: 34.1.1.0/24 Metric: 10 Internal Up IP prefix: 43.1.1.0/24 Metric: 10 Internal Up V6 prefix: abcd::10:255:71:242/128 Metric: 0 Internal Up glacier.02-00 Sequence: 0x1, Checksum: 0xd141, Lifetime: 1080 secs IS neighbor: camaro.00 Metric: 0 IS neighbor: glacier.00 Metric: 0 badlands.00-00 Sequence: 0x6, Checksum: 0x562, Lifetime: 1096 secs IS neighbor: ranier.00 Metric: 10 IP prefix: 10.255.70.103/32 Metric: 40 Internal Up IP prefix: 10.255.71.52/32 Metric: 20 Internal Up IP prefix: 10.255.71.241/32 Metric: 10 Internal Up IP prefix: 10.255.71.242/32 Metric: 30 Internal Up IP prefix: 10.255.71.244/32 Metric: 0 Internal Up IP prefix: 11.1.1.0/24 Metric: 10 Internal Up IP prefix: 23.1.1.0/24 Metric: 20 Internal Up IP prefix: 34.1.1.0/24 Metric: 30 Internal Up IP prefix: 43.1.1.0/24 Metric: 40 Internal Up V6 prefix: abcd::10:255:71:244/128 Metric: 0 Internal Up show isis database extensive user@host> show isis database extensive isis2 IS-IS level 1 link-state database: IS-IS level 2 link-state database: 1847 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS isis2.00-00 Sequence: 0x82, Checksum: 0x6cc3, Lifetime: 1126 secs IS neighbor: isis1.00 Metric: 10 IS neighbor: isis3.00 Metric: 10 IP prefix: 10.255.245.202/32 Metric: 0 Internal IP prefix: 192.168.36.0/29 Metric: 10 Internal IP prefix: 192.168.36.16/30 Metric: 10 Internal IP prefix: 192.168.36.24/30 Metric: 10 Internal Header: LSP ID: isis2.00-00, Length: 234 bytes Allocated length: 234 bytes, Router ID: 10.255.245.202 Remaining lifetime: 1126 secs, Level: 2,Interface: 4 Estimated free bytes: 0, Actual free bytes: 0 Aging timer expires in: 1126 secs Protocols: IP, IPv6 Packet: LSP ID: isis2.00-00, Length: 234 bytes, Checksum: 0x6cc3, Sequence: 0x82, Attributes: NLPID: 0x83, Fixed length: 27 bytes, Version: Packet type: 20, Packet version: 1, Max area: Lifetime : 1198 secs 0x3 1, Sysid length: 0 bytes 0 TLVs: Area address: 47.0005.80ff.f800.0000.0108.0001 (13) Speaks: IP Speaks: IPv6 IP router id: 10.255.245.202 IP address: 10.255.245.202 Hostname: isis2 IS neighbor: isis3.00, Internal, Metric: default 10 IS neighbor: isis1.00, Internal, Metric: default 10 IS neighbor: isis3.00, Metric: default 10 IP address: 192.168.36.25 Neighbor's IP address: 192.168.36.26 IS neighbor: isis1.00, Metric: default 10 IP address: 192.168.36.18 Neighbor's IP address: 192.168.36.17 IP prefix: 10.255.245.202/32, Internal, Metric: default 0 IP prefix: 192.168.36.0/29, Internal, Metric: default 10 IP prefix: 192.168.36.24/30, Internal, Metric: default 10 IP prefix: 192.168.36.16/30, Internal, Metric: default 10 IP prefix: 10.255.245.202/32 metric 0 up 6 bytes of subtlvs Administrative tag 1: 1000 IP prefix: 192.168.36.0/29 metric 10 up IP prefix: 192.168.36.24/30 metric 10 up IP prefix: 192.168.36.16/30 metric 10 up No queued transmissions show isis database extensive (CLNS) user@host> show isis database extensive IS-IS level 1 link-state database: isis2.00-00 Sequence: 0x1256, Checksum: 0x53da, Lifetime: 582 secs IS neighbor: pro1-a.02 Metric: 10 ES neighbor: toothache Metric: 0 ES neighbor: 1921.6800.4002 Metric: 10 IP prefix: 192.168.37.64/29 Metric: 10 Internal Up Header: LSP ID: toothache.00-00, Length: 140 bytes Allocated length: 284 bytes, Router ID: 0.0.0.0 Remaining lifetime: 582 secs, Level: 1,Interface: 66 Estimated free bytes: 144, Actual free bytes: 144 Aging timer expires in: 582 secs Protocols: IP, CLNS 1848 Chapter 74: Operational Commands for Layer 3 Protocols Packet: LSP ID: toothache.00-00, Length: 140 bytes, Lifetime : 1199 secs Checksum: 0x53da, Sequence: 0x1256, Attributes: 0xb NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes Packet type: 18, Packet version: 1, Max area: 0 TLVs: Area address: 47.0005.80ff.f800.0000.0108.0001 (13) Speaks: CLNP Speaks: IP Hostname: toothache IP address: 192.168.37.69 IP extended prefix: 192.168.37.64/29 metric 10 up IP prefix: 192.168.37.64/29, Internal, Metric: default 10, Up IS neighbor: pro1-a.02, Internal, Metric: default 10 IS extended neighbor: pro1-a.02, Metric: default 10 ES neighbor TLV: Internal, Metric: default 0 ES: toothache ES neighbor TLV: Internal, Metric: default 10 ES: 1921.6800.4002 No queued transmissions 1849 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis hostname Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis hostname show isis hostname Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Intermediate System-to-Intermediate System (IS-IS) hostname database information. none—Display IS-IS hostname database information. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show isis hostname on page 1850 Table 224 on page 1850 describes the output fields for the show isis hostname command. Output fields are listed in the approximate order in which they appear. Table 224: show isis hostname Output Fields Field Name Field Description System Id System identifier mapped to the hostname. Hostname Hostname mapped to the system identifier. Type Type of mapping between system identifier and hostname. • Dynamic—Hostname mapping determined as described in RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS. • show isis hostname 1850 Static—Hostname mapping configured by user. user@host> show isis hostname IS-IS hostname database: System Id Hostname 1921.6800.4201 isis1 1921.6800.4202 isis2 1921.6800.4203 isis3 Type Dynamic Static Dynamic Chapter 74: Operational Commands for Layer 3 Protocols show isis interface Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis interface show isis interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display status information about Intermediate System-to-Intermediate System (IS-IS)-enabled interfaces. none—Display standard information about all IS-IS-enabled interfaces. brief | detail | extensive—(Optional) Display the specified level of output. interface-name—(Optional) Display information about the specified interface only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show isis interface on page 1853 show isis interface brief on page 1853 show isis interface detail on page 1853 show isis interface extensive on page 1853 show isis interface extensive (with LDP) on page 1854 Table 225 on page 1851 describes the output fields for the show isis interface command. Output fields are listed in the approximate order in which they appear. Table 225: show isis interface Output Fields Field Name Field Description Level of Output interface-name Name of the interface. detail Designated router Routing device selected by other routers that is responsible for sending link-state advertisements that describe the network. Used only on broadcast networks. detail Index Interface index assigned by the Junos OS kernel. detail State Internal implementation information. detail Circuit id Circuit identifier. detail 1851 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 225: show isis interface Output Fields (continued) Field Name Field Description Level of Output Circuit type Circuit type: detail • 1—Level 1 only • 2—Level 2 only • 3—Level 1 and Level 2 LSP interval Interval between link-state PDUs sent from the interface. detail CSNP interval Interval between complete sequence number PDUs sent from the interface. detail extensive Sysid System identifier. detail Interface Interface through which the adjacency is made. none brief L or Level Level: All levels • 1—Level 1 only • 2—Level 2 only • 3—Level 1 and Level 2 CirID Circuit identifier. none brief Level 1 DR Level 1 designated intermediate system. none brief Level 2 DR Level 2 designated intermediate system. none brief L1/L2 Metric Interface's metric for Level 1 and Level 2. If there is no information, the metric is 0. none brief Adjacency advertisement: Advertise This routing device has signaled not to advertise this interface to its neighbors in their label-switched paths (LSPs). detail extensive Adjacency advertisement: Suppress This neighbor has signaled not to advertise this interface in the routing device’s outbound LSPs. detail extensive Adjacencies Number of adjacencies established on this interface. detail Priority Priority value for this interface. detail Metric Metric value for this interface. detail Hello(s) / Hello Interval Interface's hello interval. detail extensive Hold(s) / Hold Time Interface's hold time. detail extensive 1852 Chapter 74: Operational Commands for Layer 3 Protocols Table 225: show isis interface Output Fields (continued) Field Name Field Description Level of Output Designated Router Router responsible for sending network link-state advertisements, which describe all the routers attached to the network. detail Hello padding Type of hello padding: extensive • Adaptive—On point-to-point connections, the hello packets are padded from the initial detection of a new neighbor until the neighbor verifies the adjacency as Up in the adjacency state TLV. If the neighbor does not support the adjacency state TLV, then padding continues. On LAN connections, padding starts from the initial detection of a new neighbor until there is at least one active adjacency on the interface. • Loose—(Default) The hello packet is padded from the initial detection of a new neighbor until the adjacency transitions to the Up state. • Strict—Padding is performed on all interface types and for all adjacency states, and is continuous. LDP sync state Current LDP synchronization state: in sync, in holddown, or not supported. extensive reason Reason for being in the LDP sync state. extensive config holdtime Configured value of the hold timer. extensive remaining If the state is not in sync and the hold time is not infinity, then this field displays the number of seconds remaining. extensive show isis interface user@host> show isis interface IS-IS interface database: Interface L CirID Level 1 DR at-2/3/0.0 3 0x1 Point to Point lo0.0 0 0x1 Passive Level 2 DR Point to Point Passive L1/L2 Metric 10/10 0/0 show isis interface brief The output for the show isis interface brief command is identical to that for the show isis interface command. For sample output, see show isis interface on page 1853. show isis interface detail user@host> show isis interface detail IS-IS interface database: at-2/3/0.0 Index: 66, State: 0x6, Circuit id: 0x1, Circuit type: 3 LSP interval: 100 ms, CSNP interval: 5 s Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router 1 1 64 10 9.000 27 2 1 64 10 9.000 27 lo0.0 Index: 64, State: 0x6, Circuit id: 0x1, Circuit type: 0 LSP interval: 100 ms, CSNP interval: disabled Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router 1 0 64 0 Passive 2 0 64 0 Passive show isis interface extensive user@host> show isis interface extensive 1853 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS IS-IS interface database: at-2/3/0.0 Index: 66, State: 0x6, Circuit id: 0x1, Circuit type: 3 LSP interval: 100 ms, CSNP interval: 5 s, Loose Hello padding Level 1 Adjacencies: 1, Priority: 64, Metric: 10 Hello Interval: 9.000 s, Hold Time: 27 s Level 2 Adjacencies: 1, Priority: 64, Metric: 10 Hello Interval: 9.000 s, Hold Time: 27 s lo0.0 Index: 64, State: 0x6, Circuit id: 0x1, Circuit type: 0 LSP interval: 100 ms, CSNP interval: disabled, Loose Hello padding Level 1 Adjacencies: 0, Priority: 64, Metric: 0 Passive Level 2 Adjacencies: 0, Priority: 64, Metric: 0 Passive show isis interface extensive (with LDP) 1854 user@host> show isis interface extensive IS-IS interface database: so-1/1/2.0 Index: 114, State: 0x6, Circuit id: 0x1, Circuit type: 2 LSP interval: 100 ms, CSNP interval: 20 s, Loose Hello padding Adjacency advertisement: Advertise LDP sync state: in sync, for: 00:01:28, reason: LDP up during config config holdtime: 20 seconds Level 2 Adjacencies: 1, Priority: 64, Metric: 11 Hello Interval: 9.000 s, Hold Time: 27 s IPV4 MulticastMetric: 10 IPV6 UnicastMetric: 10 Chapter 74: Operational Commands for Layer 3 Protocols show isis overview Syntax Syntax (J-EX Series Switch) Release Information Description Options show isis overview show isis overview Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Intermediate System-to Intermediate System (IS-IS) overview information. none—Display standard overview information about IS-IS for all routing instances. instance instance-name—(Optional) Display overview information for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show isis overview on page 1856 Table 226 on page 1855 lists the output fields for the show isis overview command. Output fields are listed in the approximate order in which they appear. Table 226: show isis overview Output Fields Field Name Field Description instance The IS-IS routing intance. Router ID Router ID of the routing device. Adjacency holddown Adjacency holddown capability: enabled or disabled. Maximum Areas Maximum number of IS-IS areas advertised by the routing device. LSP life time Lifetime of the link-state PDU, in seconds. Attached bit evaluation Attached bit capability: enabled or disabled. SPF delay Delay before performing consecutive Shortest Path First calculations. SPF holddown Delay before performing additional Shortest Path First (SPF) calculations after the maximum number of consecutive SPF calculations is reached. SPF rapid runs Maximum number of Shortest Path First calculations that can be performed in succession before the holddown timer begins. 1855 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 226: show isis overview Output Fields (continued) Field Name Field Description Overload bit at startup is set Overload bit capability is enabled. Overload high metrics Overload high metrics capability: enabled or disabled. Overload timeout Time period after which overload is reset and the time that remains before the timer is set to expire. Traffic engineering Traffic engineering capability: enabled or disabled. Restart Graceful restart capability: enabled or disabled. Restart duration Time period for complete reacquisition of IS-IS neighbors. Helper mode Graceful restart helper capability: enalbed or disabled. Level IS-IS level: • 1—Level 1 information • 2—Level 2 information IPv4 is enabled IP Protocol version 4 capability is enabled. IPv6 is enabled IP Protocol version 6 capability is enabled. CLNS is enabled OSI CLNP Protocol capability is enabled. (J Series routers only) Internal route preference Preference value of internal routes. External route preference Preference value of external routes. Wide area metrics are enabled Wide area metrics capability is enabled. Narrow metrics is enabled Narrow metrics capability is enabled. show isis overview Sample Output 1856 user@host> show isis overview Instance: master Router ID: 192.168.1.220 Adjacency holddown: enabled Maximum Areas: 3 LSP life time: 65535 Attached bit evaluation: enabled SPF delay: 200 msec, SPF holddown: 5000 msec, SPF rapid runs: 3 Overload bit at startup is set Overload high metrics: disabled Chapter 74: Operational Commands for Layer 3 Protocols Overload timeout: 300 sec, expires in 295 seconds IPv4 is enabled, IPv6 is enabled Traffic engineering: enabled Restart: Enabled Restart duration: 210 sec Helper mode: Enabled Level 1 Internal route preference: 15 External route preference: 160 Wide metrics are enabled, Narrow metrics are enabled Level 2 Internal route preference: 18 External route preference: 165 Wide metrics are enabled 1857 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis route Syntax show isis route Syntax (J-EX Series Switch) show isis route Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the routes in the Intermediate System-to-Intermediate System (IS-IS) routing table. Options none—Display all routes in the IS-IS routing table for all supported address families for all routing instances. destination—(Optional) Destination address for the route. inet | inet6—(Optional) Display inet (IPv4) or inet6 (IPv6) routes, respectively. instance instance-name—(Optional) Display routes for the specified routing instance only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)—(Optional) Display routes for the specified topology only, or use unicast to display information, if available, for both IPv4 and IPv6 unicast topologies. Required Privilege Level List of Sample Output Output Fields 1858 view show isis route logical-system on page 1859 show isis route (CLNS) on page 1860 Table 227 on page 1859 describes the output fields for the show isis route command. Output fields are listed in the approximate order in which they appear. Chapter 74: Operational Commands for Layer 3 Protocols Table 227: show isis route Output Fields show isis route logical-system Field Name Field Description Current version Number of the current version of the IS-IS routing table. L1 Version of Level 1 SPF that was run. L2 Version of Level 2 SPF that was run. Prefix Destination of the route. L IS-IS level: • 1—Level 1 only • 2—Level 2 only • 3—Level 1 and Level 2 Version Version of SPF that generated the route. Metric Metric value associated with the route. Type Metric type: int (internal) or ext (external). Interface Interface to the next hop. Via System identifier of the next hop, displayed as a name if possible. ISO Routes ISO routing table entries. snpa MAC address. user@host> show isis route logical-system ls1 IS-IS routing table Current version: L1: 8 L2: 11 Prefix L Version Metric Type Interface Via 10.9.7.0/30 2 11 20 int gr-0/2/0.0 h 10.9.201.1/32 2 11 60 int gr-0/2/0.0 h IPV6 Unicast IS-IS routing table Current version: L1: 9 L2: 11 Prefix L Version Metric Type Interface Via 8009:3::a09:3200/126 2 11 20 int gr-0/2/0.0 h 1859 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis route (CLNS) 1860 user@host> show isis route IS-IS routing table Current version: L1: 10 L2: 8 IPv4/IPv6 Routes Prefix L Version Metric Type Interface Via 0.0.0.0/0 1 10 10 int fe-0/0/1.0 ISIS.0 ISO Routes Prefix L Version Metric Type Interface Via snpa 0/0 1 10 10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56 47.0005.80ff.f800.0000.0108.0001/104 1 10 0 int 47.0005.80ff.f800.0000.0108.0001.1921.6800.4001/152 1 10 10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56 47.0005.80ff.f800.0000.0108.0001.1921.6800.4002/152 1 10 20 int fe-0/0/1.0 isis.0 0:12:0:34:0:56 47.0005.80ff.f800.0000.0108.0002/104 1 10 0 int 47.0005.80ff.f800.0000.0108.0002.1921.6800.4001/152 1 10 10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56 Chapter 74: Operational Commands for Layer 3 Protocols show isis spf Syntax show isis spf (brief | log | results) Syntax (J-EX Series Switch) show isis spf (brief | log | results) Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Intermediate System-to-Intermediate System (IS-IS) shortest-path-first (SPF) calculations. brief—Display an overview of SPF calculations. log—Display the log of SPF calculations. results—Display the results of SPF calculations. instance instance instance-name—(Optional) Display SPF calculations for the specified routing instance. level (1 | 2)—(Optional) Display SPF calculations for the specified IS-IS level. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)—(Optional) Display SPF calculations for the specified topology only. Required Privilege Level List of Sample Output Output Fields view show isis spf brief on page 1862 show isis spf log on page 1863 show isis spf results on page 1864 show isis spf results (CLNS) on page 1865 Table 228 on page 1861 describes the output fields for the show isis spf command. Output fields are listed in the approximate order in which they appear. Table 228: show isis spf Output Fields Field Name Field Description Node System ID of a node. Metric Metric to the node. 1861 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 228: show isis spf Output Fields (continued) show isis spf brief Field Name Field Description Interface Interface of the next hop. Via System ID of the next hop. SNPA Subnetwork point of attachment (MAC address of the next hop). Start time (log option only) Time that the SPF computation started. Elapsed (secs) (log option only) Length of time, in seconds, required to complete the SPF computation. Count (log option only) Number of times the SPF was triggered. Reason (log option only) Reason that the SPF computation was completed. user@host> show isis spf brief logical-system ls1 IS-IS level 1 SPF results: Node Metric Interface scat.00 10 ge-1/1/0.0 fix.02 10 fix.00 0 3 nodes IS-IS level 2 SPF results: Node Metric skag.00 20 skag.02 20 h.00 10 fix.00 0 4 nodes Interface gr-0/2/0.0 gr-0/2/0.0 gr-0/2/0.0 IPV6 Unicast IS-IS level 1 SPF results: Node Metric Interface scat.00 10 ge-1/1/0.0 ge-1/1/0.0 fix.02 10 fix.00 0 3 nodes IPV6 Unicast IS-IS level 2 SPF results: Node Metric Interface skag.00 20 gr-0/2/0.0 gr-0/2/0.0 skag.02 20 gr-0/2/0.0 gr-0/2/0.0 h.00 10 gr-0/2/0.0 gr-0/2/0.0 fix.00 0 4 nodes Multicast IS-IS level 1 SPF results: Node Metric Interface scat.00 10 ge-1/1/0.0 1862 Via scat Via SNPA 0:90:69:a6:48:9d SNPA h h h Via scat scat Via SNPA 0:90:69:a6:48:9d 0:90:69:a6:48:9d SNPA h h h h h h Via scat SNPA 0:90:69:a6:48:9d Chapter 74: Operational Commands for Layer 3 Protocols fix.02 fix.00 3 nodes 10 0 Multicast IS-IS level 2 SPF results: Node Metric Interface skag.00 20 gr-0/2/0.0 skag.02 20 gr-0/2/0.0 h.00 10 gr-0/2/0.0 fix.00 0 4 nodes show isis spf log user@host> show isis spf log logical-system lsl IS-IS level 1 SPF log: Start time Elapsed (secs) Count Fri Oct 31 12:41:18 0.000069 1 Fri Oct 31 12:41:18 0.000107 3 Fri Oct 31 12:41:18 0.000050 3 Fri Oct 31 12:41:23 0.000033 1 Fri Oct 31 12:41:28 0.000178 5 Fri Oct 31 12:41:59 0.000060 1 Fri Oct 31 12:42:30 0.000161 2 Fri Oct 31 12:56:58 0.000198 1 Fri Oct 31 13:10:29 0.000209 1 IS-IS level 2 SPF log: Via SNPA h h h Reason Reconfig Updated LSP fix.00-00 Address change on so-1/2/2.0 Updated LSP fix.00-00 New adjacency scat on ge-1/1/0.0 Updated LSP fix.00-00 Multi area attachment change Periodic SPF Periodic SPF Start time Elapsed (secs) Count Fri Oct 31 12:41:18 0.000035 1 Fri Oct 31 12:41:18 0.000047 2 Fri Oct 31 12:41:18 0.000043 5 Fri Oct 31 12:41:23 0.000022 1 Fri Oct 31 12:41:59 0.000144 3 Fri Oct 31 12:42:30 0.000257 3 Fri Oct 31 12:54:37 0.000195 1 Fri Oct 31 12:55:50 0.000178 1 Fri Oct 31 12:55:55 0.000174 1 Fri Oct 31 12:55:58 0.000176 1 Fri Oct 31 13:08:14 0.000198 1 IPV6 Unicast IS-IS level 1 SPF log: Reason Reconfig Updated LSP fix.00-00 Address change on gr-0/2/0.0 Updated LSP fix.00-00 New adjacency h on gr-0/2/0.0 New LSP skag.00-00 Periodic SPF Updated LSP fix.00-00 Updated LSP h.00-00 Updated LSP skag.00-00 Periodic SPF Start time Elapsed (secs) Count Fri Oct 31 12:41:18 0.000028 1 Fri Oct 31 12:41:18 0.000043 3 Fri Oct 31 12:41:18 0.000112 4 Fri Oct 31 12:41:23 0.000059 1 Fri Oct 31 12:41:25 0.000041 1 Fri Oct 31 12:41:28 0.000103 5 Fri Oct 31 12:41:59 0.000040 1 Fri Oct 31 12:42:30 0.000118 2 Fri Oct 31 12:56:08 0.000289 1 Fri Oct 31 13:11:07 0.000214 1 IPV6 Unicast IS-IS level 2 SPF log: Reason Reconfig Updated LSP fix.00-00 Updated LSP fix.00-00 Updated LSP fix.00-00 Updated LSP fix.00-00 New adjacency scat on ge-1/1/0.0 Updated LSP fix.00-00 Multi area attachment change Periodic SPF Periodic SPF Start time Fri Oct 31 Fri Oct 31 Fri Oct 31 Fri Oct 31 Fri Oct 31 Fri Oct 31 Fri Oct 31 Reason Reconfig Updated LSP fix.00-00 Updated LSP fix.00-00 Updated LSP fix.00-00 Updated LSP fix.00-00 New adjacency h on gr-0/2/0.0 New LSP skag.00-00 12:41:18 12:41:18 12:41:18 12:41:23 12:41:25 12:41:59 12:42:30 Elapsed (secs) Count 0.000027 1 0.000039 2 0.000049 6 0.000025 1 0.000023 1 0.000087 3 0.000123 3 1863 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Fri Fri Fri Fri ... show isis spf results Oct Oct Oct Oct 31 31 31 31 12:55:50 12:55:55 12:55:58 13:09:46 0.000121 0.000121 0.000121 0.000201 1 1 1 1 Updated LSP fix.00-00 Updated LSP h.00-00 Updated LSP skag.00-00 Periodic SPF user@host> show isis spf results logical-system ls1 IS-IS level 1 SPF results: Node Metric Interface scat.00 10 ge-1/1/0.0 20 10.9.1.0/30 fix.02 10 fix.00 0 10 10.9.1.0/30 10 10.9.5.0/30 10 10.9.6.0/30 20 10.9.7.0/30 60 10.9.201.1/32 3 nodes IS-IS level 2 SPF results: Node Metric skag.00 20 30 skag.02 20 h.00 10 20 20 60 fix.00 0 10 10 10 4 nodes Interface gr-0/2/0.0 10.9.7.0/30 gr-0/2/0.0 gr-0/2/0.0 10.9.6.0/30 10.9.7.0/30 10.9.201.1/32 Via scat Via SNPA h h h 10.9.1.0/30 10.9.5.0/30 10.9.6.0/30 IPV6 Unicast IS-IS level 1 SPF results: Node Metric Interface Via scat.00 10 ge-1/1/0.0 scat ge-1/1/0.0 scat 20 8009:1::a09:1400/126 fix.02 10 fix.00 0 10 8009:1::a09:1400/126 10 8009:2::a09:1e00/126 20 8009:3::a09:3200/126 10 8009:4::a09:2800/126 3 nodes IPV6 Unicast IS-IS level 2 SPF results: Node Metric Interface Via skag.00 20 gr-0/2/0.0 h gr-0/2/0.0 h 30 8009:3::a09:3200/126 skag.02 20 gr-0/2/0.0 h gr-0/2/0.0 h h.00 10 gr-0/2/0.0 h gr-0/2/0.0 h 20 8009:3::a09:3200/126 20 8009:4::a09:2800/126 fix.00 0 10 8009:1::a09:1400/126 1864 SNPA 0:90:69:a6:48:9d SNPA 0:90:69:a6:48:9d 0:90:69:a6:48:9d SNPA Chapter 74: Operational Commands for Layer 3 Protocols 10 10 8009:2::a09:1e00/126 8009:4::a09:2800/126 4 nodes Multicast IS-IS level 1 SPF results: Node Metric Interface scat.00 10 ge-1/1/0.0 fix.02 10 fix.00 0 3 nodes Multicast IS-IS level 2 SPF results: Node Metric Interface skag.00 20 gr-0/2/0.0 skag.02 20 gr-0/2/0.0 h.00 10 gr-0/2/0.0 fix.00 0 4 nodes ... show isis spf results (CLNS) Via scat Via pro1-a.02 pro1-a.00 20 20 20 10 0 0 10 SNPA h h h user@host> show isis spf results IS-IS level 1 SPF results: Node Metric Interface Via skag.00 10 fe-0/0/1.0 toothache fe-0/0/1.0 toothache 20 192.168.37.64/29 10 1921.6800.4001 20 1921.6800.4002 pro1-a.02 10 pro1-a.00 0 0 10.255.245.1/32 10 192.168.37.64/29 0 1921.6800.4211 3 nodes IS-IS level 2 SPF results: Node Metric skag.00 10 SNPA 0:90:69:a6:48:9d SNPA 0:12:0:34:0:56 0:12:0:34:0:56 Interface Via SNPA fe-0/0/1.0 toothache 0:12:0:34:0:56 fe-0/0/1.0 toothache 0:12:0:34:0:56 10.255.245.1/32 192.168.37.64/29 47.0005.80ff.f800.0000.0109.0010/104 10.255.245.1/32 192.168.37.64/29 3 nodes 1865 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show isis statistics Syntax show isis statistics Syntax (J-EX Series Switch) show isis statistics Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display statistics about Intermediate System-to-Intermediate System (IS-IS) traffic. Options none—Display IS-IS traffic statistics for all routing instances. instance instance-name—(Optional) Display statistics for the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level view Related Documentation • List of Sample Output clear isis statistics on page 1766 show isis statistics on page 1867 Output Fields Table 229 on page 1866 describes the output fields for the show isis statistics command. Output fields are listed in the approximate order in which they appear. Table 229: show isis statistics Output Fields Field Name Field Description PDU type Protocol data unit type: • CSNP—Complete sequence number PDUs contain a complete list of all link-state PDUs in the IS-IS database. CSNPs are sent periodically on all links, and the receiving systems use the information in the CSNP to update and synchronize their link-state PDU databases. The designated router multicasts CSNPs on broadcast links in place of sending explicit acknowledgments for each link-state PDU. • IIH—IS-IS hello packets are broadcast to discover the identity of neighboring IS-IS systems and to determine whether the neighbors are Level 1 or Level 2 intermediate systems. • LSP—Link-state PDUs contain information about the state of adjacencies to neighboring IS-IS systems. Link-state PDUs are flooded periodically throughout an area. • PSNP—Partial sequence number PDUs are sent multicast by a receiver when it detects that it is missing a link-state PDU; that is, when its link-state PDU database is out of date. The receiver sends a PSNP to the system that transmitted the CSNP, effectively requesting that the missing link-state PDU be transmitted. That routing device, in turn, forwards the missing link-state PDU to the requesting routing device. • Received 1866 Unknown—The PDU type is unknown. Number of PDUs received since IS-IS started or since the statistics were set to zero. Chapter 74: Operational Commands for Layer 3 Protocols Table 229: show isis statistics Output Fields (continued) Field Name Field Description Processed Number of PDUs received less the number dropped. Drops Number of PDUs dropped. Sent Number of PDUs transmitted since IS-IS started or since the statistics were set to zero. Rexmit Number of PDUs retransmitted since IS-IS started or since the statistics were set to zero. Total packets received/sent Total number of PDUs received and transmitted since IS-IS started or since the statistics were set to zero. SNP queue length Number of CSPN and PSNP packets currently waiting in the queue for processing. This value is almost always 0. LSP queue length Number of link-state PDUs waiting in the queue for processing. This value is almost always 0. SPF runs Number of shortest-path-first (SPF) calculations that have been performed. If this number is incrementing rapidly, it indicates that the network is unstable. Fragments rebuilt Number of link-state link-state PDU fragments that the local system has computed. LSP regenerations Number of link-state PDUs that have been regenerated. A link state PDU is regenerated when it is nearing the end of its lifetime and it has not changed. Purges initiated Number of purges that the system initiated. A purge is initiated if the software decides that a link-state PDU must be removed from the network. show isis statistics user@host> show isis statistics IS-IS statistics for merino: PDU type LSP IIH CSNP PSNP Unknown Totals Received 12227 113808 198868 6985 0 331888 Processed 12227 113808 198868 6979 0 331882 Drops 0 0 0 6 0 6 Sent 8184 115817 198934 8274 0 331209 Rexmit 683 0 0 0 0 683 Total packets received: 331888 Sent: 331892 SNP queue length: LSP queue length: SPF runs: Fragments rebuilt: LSP regenerations: Purges initiated: 0 Drops: 0 Drops: 0 0 1014 1038 425 0 1867 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ospf3 database Syntax Syntax (J-EX Series Switch) Release Information show ospf3 database show ospf3 database Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the entries in the Open Shortest Path First version 3 (OSPFv3) link-state database, which contains data about link-state advertisement (LSA) packets. Options none—Display standard information about all entries in the OSPFv3 link-state database. brief | detail | extensive | summary—(Optional) Display the specified level of output. advertising-router (address | self)—(Optional) Display the LSAs advertised either by a particular routing device or by this routing device. area area-id—(Optional) Display the LSAs in a particular area. external—(Optional) Display external LSAs. 1868 Chapter 74: Operational Commands for Layer 3 Protocols instance instance-name—(Optional) Display all OSPF database information under the named routing instance. inter-area-prefix—(Optional) Display information about interarea-prefix LSAs. inter-area-router—(Optional) Display information about interarea-router LSAs. intra-area-prefix—(Optional) Display information about intra-area-prefix LSAs. link—(Optional) Display information about link LSAs. link-local—(Optional) Display information about link-local LSAs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. lsa-id lsa-id—(Optional) Display the LSA with the specified LSA identifier. network—(Optional) Display information about network LSAs. nssa—(Optional) Display information about not-so-stubby area (NSSA) LSAs. realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)—(Optional) Display information about the specified OSPFv3 realm, or address family. Use the realm option to specify an address family other than IPv6 unicast, which is the default. router—(Optional) Display information about router LSAs. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear (ospf | ospf3) database on page 1748 show ospf3 database brief on page 1874 show ospf3 database extensive on page 1874 show ospf3 database summary on page 1877 Table 230 on page 1869 lists the output fields for the show ospf3 database command. Output fields are listed in the approximate order in which they appear. Table 230: show ospf3 database Output Fields Field Name Field Description Level of Output OSPF link state database, area area-number Entries in the link-state database for this area. brief detail extensive OSPF AS SCOPE link state database Entries in the AS scope link-state database. brief detail extensive 1869 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 230: show ospf3 database Output Fields (continued) Field Name Field Description Level of Output OSPF Link-Local link state database, interface interface-name Entries in the link-local link-state database for this interface. brief detail extensive area Area number. Area 0.0.0.0 is the backbone area. All levels Type Type of link advertisement: Extern, InterArPfx, InterArRtr, IntraArPrx , Link, Network, NSSA, or Router. brief detail extensive ID Link identifier included in the advertisement. An asterisk (*) preceding the identifier marks database entries that originated from the local routing device. brief detail extensive Adv Rtr Address of the routing device that sent the advertisement. brief detail extensive Seq Link sequence number of the advertisement. brief detail extensive Age Time elapsed since the LSA was originated, in seconds. brief detail extensive Cksum Checksum value of the LSA. brief detail extensive Len Length of the advertisement, in bytes. brief detail extensive Router (Router Link-State Advertisements) bits Flags describing the routing device that generated the LSP. detail extensive Options Option bits carried in the router LSA. detail extensive For Each Router Link Type Type of interface. The value of all other output fields describing a routing device interface depends on the interface’s type: • PointToPoint (1)—Point-to-point connection to another routing device. • Transit (2)—Connection to a transit network. • Virtual (4)—Virtual link. detail extensive Loc-if-id Local interface ID assigned to the interface that uniquely identifies the interface with the routing device. detail extensive Nbr-if-id Interface ID of the neighbor's interface for this routing device link. detail extensive Nbr-rtr-id Router ID of the neighbor routing device (for type 2 interfaces, the attached link’s designated router). detail extensive Metric Cost of the router link. detail extensive Gen timer How long until the LSA is regenerated, in the format hours:minutes:seconds. extensive 1870 Chapter 74: Operational Commands for Layer 3 Protocols Table 230: show ospf3 database Output Fields (continued) Field Name Field Description Level of Output Aging timer How long until the LSA expires, in the format hours:minutes:seconds. extensive Installed nn:nn:nn ago How long ago the route was installed, in the format hours:minutes:seconds. extensive expires in nn:nn:nn How long until the route expires, in the format hours:minutes:seconds. extensive sent nn:nn:nn ago Time elapsed since the LSA was last transmitted or flooded to an adjacency or an interface, respectively, in the format hours:minutes:seconds. extensive Ours Indicates that this is a local advertisement. extensive Network (Network Link-State Advertisements) Options Option bits carried in the network LSA. detail extensive Attached Router Router IDs of each of the routing devices attached to the link. Only routing devices that are fully adjacent to the designated router are listed. The designated router includes itself in this list. detail extensive InterArPfx (Interarea-Prefix Link-State Advertisements) Prefix IPv6 address prefix. detail extensive Prefix-options Option bit associated with the prefix. detail extensive Metric Cost of this route. Expressed in the same units as the interface costs in the router LSAs. When the interarea-prefix LSA is describing a route to a range of addresses, the cost is set to the maximum cost to any reachable component of the address range. detail extensive Gen timer How long until the LSA is regenerated, in the format hours:minutes:seconds. extensive Aging timer How long until the LSA expires, in the format hours:minutes:seconds. extensive Installed nn:nn:nn ago How long ago the route was installed, in the format hours:minutes:seconds. extensive expires in nn:nn:nn How long until the route expires, in the format hours:minutes:seconds. extensive sent nn:nn:nn ago Time elapsed since the LSA was last transmitted or flooded to an adjacency or an interface, respectively, in the format hours:minutes:seconds. extensive Ours Indicates that this is a local advertisement. extensive InterArRtr (Interarea-Router Link-State Advertisements) Dest-router-id Router ID of the routing device described by the LSA. detail extensive options Optional capabilities supported by the routing device. detail extensive 1871 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 230: show ospf3 database Output Fields (continued) Field Name Field Description Level of Output Metric Cost of this route. Expressed in the same units as the interface costs in the router LSAs. When the interarea-prefix LSA is describing a route to a range of addresses, the cost is set to the maximum cost to any reachable component of the address range. detail extensive Prefix IPv6 address prefix. extensive Prefix-options Option bit associated with the prefix. extensive Extern (External Link-State Advertisements) Prefix IPv6 address prefix. detail extensive Prefix-options Option bit associated with the prefix. detail extensive Metric Cost of the route, which depends on the value of Type. detail extensive Type n Type of external metric: Type 1 or Type 2. detail extensive Aging timer How long until the LSA expires, in the format hours:minutes:seconds. extensive Installed nn:nn:nn ago How long ago the route was installed, in the format hours:minutes:seconds. extensive expires in nn:nn:nn How long until the route expires, in the format hours:minutes:seconds. extensive sent nn:nn:nn ago Time elapsed since the LSA was last transmitted or flooded to an adjacency or an interface, respectively, in the format hours:minutes:seconds. extensive Link (Link-State Advertisements) IPv6-Address IPv6 link-local address on the link for which this link LSA originated. detail extensive Options Option bits carried in the link LSA. detail extensive priority Router priority of the interface attaching the originating routing device to the link. detail extensive Prefix-count Number of IPv6 address prefixes contained in the LSA. The rest of the link LSA contains a list of IPv6 prefixes to be associated with the link. detail extensive Prefix IPv6 address prefix. detail extensive Prefix-options Option bit associated with the prefix. detail extensive Gen timer How long until the LSA is regenerated, in the format hours:minutes:seconds. extensive Aging timer How long until the LSA expires, in the format hours:minutes:seconds. extensive 1872 Chapter 74: Operational Commands for Layer 3 Protocols Table 230: show ospf3 database Output Fields (continued) Field Name Field Description Level of Output Installed nn:nn:nn ago How long ago the route was installed, in the format hours:minutes:seconds. extensive expires in nn:nn:nn How long until the route expires, in the format hours:minutes:seconds. extensive sent nn:nn:nn ago Time elapsed since the LSA was last transmitted or flooded to an adjacency or an interface, respectively, in the format hours:minutes:seconds. extensive Ours Indicates that this is a local advertisement. extensive IntraArPfx (Intra-Area-Prefix Link-State Advertisements) Ref-lsa-type LSA type of the referenced LSA. • Router—Address prefixes are associated with a router LSA. • Network—Address prefixes are associated with a network LSA. detail extensive Ref-lsa-id Link-state ID of the referenced LSA. detail extensive Ref-router-id Advertising router ID of the referenced LSA. detail extensive Prefix-count Number of IPv6 address prefixes contained in the LSA. The rest of the link LSA contains a list of IPv6 prefixes to be associated with the link. detail extensive Prefix IPv6 address prefix. detail extensive Prefix-options Option bit associated with the prefix. detail extensive Metric Cost of this prefix. Expressed in the same units as the interface costs in the router LSAs. detail extensive Gen timer How long until the LSA is regenerated, in the format hours:minutes:seconds. extensive Aging timer How long until the LSA expires, in the format hours:minutes:seconds. extensive Installed hh:mm:ss ago How long ago the route was installed, in the format hours:minutes:seconds. extensive expires in hh:mm:ss How long until the route expires, in the format hours:minutes:seconds. extensive sent hh:mm:ss ago Time elapsed since the LSA was last transmitted or flooded to an adjacency or an interface, respectively, in the format hours:minutes:seconds. extensive n Router LSAs Number of router LSAs in the link-state database. summary n Network LSAs Number of network LSAs in the link-state database. summary n InterArPfx LSAs Number of interarea-prefix LSAs in the link-state database. summary 1873 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 230: show ospf3 database Output Fields (continued) Field Name Field Description Level of Output n InterArRtr LSAs Number of interarea-router LSAs in the link-state database. summary n IntraArPfx LSAs Number of intra-area-prefix LSAs in the link-state database. summary Externals Display of the external LSA database. summary n Extern LSAs Number of external LSAs in the link-state database. summary Interface interface-name Name of the interface for which link-local LSA information is displayed. summary n Link LSAs Number of link LSAs in the link-state database. summary show ospf3 database brief show ospf3 database extensive 1874 user@host> show ospf3 database brief OSPF3 link state database, area 0.0.0.0 Type ID Adv Rtr Router 0.0.0.1 10.255.4.85 Router *0.0.0.1 10.255.4.93 InterArPfx *0.0.0.2 10.255.4.93 InterArRtr *0.0.0.1 10.255.4.93 IntraArPfx *0.0.0.1 10.255.4.93 Seq 0x80000003 0x80000002 0x80000001 0x80000001 0x80000002 Age 885 953 910 910 432 Cksum Len 0xa697 40 0xc677 40 0xb96f 44 0xe159 32 0x788f 72 OSPF3 link state database, area 0.0.0.1 Type ID Adv Rtr Router *0.0.0.1 10.255.4.93 Router 0.0.0.1 10.255.4.97 Network 0.0.0.2 10.255.4.97 InterArPfx *0.0.0.1 10.255.4.93 InterArPfx *0.0.0.2 10.255.4.93 NSSA 0.0.0.1 10.255.4.97 IntraArPfx 0.0.0.1 10.255.4.97 Seq 0x80000003 0x80000006 0x80000002 0x80000002 0x80000002 0x80000002 0x80000006 Age 916 851 916 117 62 362 851 Cksum Len 0xea40 40 0xc95b 40 0x4598 32 0xa980 44 0xd47e 44 0x45ee 44 0x2f77 52 OSPF3 AS SCOPE link state database Type ID Adv Rtr Extern 0.0.0.1 10.255.4.85 Extern *0.0.0.1 10.255.4.93 Seq 0x80000002 0x80000001 Age 63 910 Cksum Len 0x9b86 44 0x59c9 44 OSPF3 Link-Local link state database, interface ge-1/3/0.0 Type ID Adv Rtr Seq Age Link *0.0.0.2 10.255.4.93 0x80000003 916 Cksum Len 0x4dab 64 user@host> show ospf3 database extensive OSPF3 link state database, area 0.0.0.0 Type ID Adv Rtr Seq Age Cksum Len Router 0.0.0.1 10.255.4.85 0x80000003 1028 0xa697 40 bits 0x2, Options 0x13 Type PointToPoint (1), Metric 10 Loc-If-Id 2, Nbr-If-Id 3, Nbr-Rtr-Id 10.255.4.93 Aging timer 00:42:51 Installed 00:17:05 ago, expires in 00:42:52, sent 02:37:54 ago Router *0.0.0.1 10.255.4.93 0x80000002 1096 0xc677 40 bits 0x3, Options 0x13 Type PointToPoint (1), Metric 10 Chapter 74: Operational Commands for Layer 3 Protocols Loc-If-Id 3, Nbr-If-Id 2, Nbr-Rtr-Id 10.255.4.85 Gen timer 00:00:40 Aging timer 00:41:44 Installed 00:18:16 ago, expires in 00:41:44, sent 00:18:14 ago Ours InterArPfx *0.0.0.2 10.255.4.93 0x80000001 1053 0xb96f 44 Prefix feee::10:10:2:0/126 Prefix-options 0x0, Metric 10 Gen timer 00:17:02 Aging timer 00:42:26 Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago Ours InterArPfx *0.0.0.3 10.255.4.93 0x80000001 1053 0x71d3 44 Prefix feee::10:255:4:97/128 Prefix-options 0x0, Metric 10 Gen timer 00:21:07 Aging timer 00:42:26 Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago Ours InterArRtr *0.0.0.1 10.255.4.93 0x80000001 1053 0xe159 32 Dest-router-id 10.255.4.97, Options 0x19, Metric 10 Gen timer 00:29:18 Aging timer 00:42:26 Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago Ours IntraArPfx 0.0.0.1 10.255.4.85 0x80000002 1028 0x2403 72 Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.85 Prefix-count 2 Prefix feee::10:255:4:85/128 Prefix-options 0x2, Metric 0 Prefix feee::10:10:1:0/126 Prefix-options 0x0, Metric 10 Aging timer 00:42:51 Installed 00:17:05 ago, expires in 00:42:52, sent 02:37:54 ago IntraArPfx *0.0.0.1 10.255.4.93 0x80000002 575 0x788f 72 Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.93 Prefix-count 2 Prefix feee::10:255:4:93/128 Prefix-options 0x2, Metric 0 Prefix feee::10:10:1:0/126 Prefix-options 0x0, Metric 10 Gen timer 00:33:23 Aging timer 00:50:24 Installed 00:09:35 ago, expires in 00:50:25, sent 00:09:33 ago OSPF3 link state database, area 0.0.0.1 Type ID Adv Rtr Seq Age Cksum Len Router *0.0.0.1 10.255.4.93 0x80000003 1059 0xea40 40 bits 0x3, Options 0x19 Type Transit (2), Metric 10 Loc-If-Id 2, Nbr-If-Id 2, Nbr-Rtr-Id 10.255.4.97 Gen timer 00:08:51 Aging timer 00:42:20 Installed 00:17:39 ago, expires in 00:42:21, sent 00:17:37 ago Router 0.0.0.1 10.255.4.97 0x80000006 994 0xc95b 40 bits 0x2, Options 0x19 Type Transit (2), Metric 10 Loc-If-Id 2, Nbr-If-Id 2, Nbr-Rtr-Id 10.255.4.97 Aging timer 00:43:25 Installed 00:16:31 ago, expires in 00:43:26, sent 02:37:54 ago Network 0.0.0.2 10.255.4.97 0x80000002 1059 0x4598 32 Options 0x11 1875 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Attached router 10.255.4.97 Attached router 10.255.4.93 Aging timer 00:42:20 Installed 00:17:36 ago, expires in 00:42:21, sent 02:37:54 ago InterArPfx *0.0.0.1 10.255.4.93 0x80000002 260 0xa980 44 Prefix feee::10:10:1:0/126 Prefix-options 0x0, Metric 10 Gen timer 00:45:39 Aging timer 00:55:39 Installed 00:04:20 ago, expires in 00:55:40, sent 00:04:18 ago Ours InterArPfx *0.0.0.2 10.255.4.93 0x80000002 205 0xd47e 44 Prefix feee::10:255:4:93/128 Prefix-options 0x0, Metric 0 Gen timer 00:46:35 Aging timer 00:56:35 Installed 00:03:25 ago, expires in 00:56:35, sent 00:03:23 ago Ours InterArPfx *0.0.0.3 10.255.4.93 0x80000001 1089 0x9bbb 44 Prefix feee::10:255:4:85/128 Prefix-options 0x0, Metric 10 Gen timer 00:04:46 Aging timer 00:41:51 Installed 00:18:09 ago, expires in 00:41:51, sent 00:17:43 ago Ours NSSA 0.0.0.1 10.255.4.97 0x80000002 505 0x45ee 44 Prefix feee::200:200:1:0/124 Prefix-options 0x8, Metric 10, Type 2, Aging timer 00:51:35 Installed 00:08:22 ago, expires in 00:51:35, sent 02:37:54 ago IntraArPfx 0.0.0.1 10.255.4.97 0x80000006 994 0x2f77 52 Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.97 Prefix-count 1 Prefix feee::10:255:4:97/128 Prefix-options 0x2, Metric 0 Aging timer 00:43:25 Installed 00:16:31 ago, expires in 00:43:26, sent 02:37:54 ago IntraArPfx 0.0.0.3 10.255.4.97 0x80000002 1059 0x4446 52 Ref-lsa-type Network, Ref-lsa-id 0.0.0.2, Ref-router-id 10.255.4.97 Prefix-count 1 Prefix feee::10:10:2:0/126 Prefix-options 0x0, Metric 0 Aging timer 00:42:20 Installed 00:17:36 ago, expires in 00:42:21, sent 02:37:54 ago OSPF3 AS SCOPE link state database Type ID Adv Rtr Seq Age Cksum Len Extern 0.0.0.1 10.255.4.85 0x80000002 206 0x9b86 44 Prefix feee::100:100:1:0/124 Prefix-options 0x0, Metric 20, Type 2, Aging timer 00:56:34 Installed 00:03:23 ago, expires in 00:56:34, sent 02:37:54 ago Extern *0.0.0.1 10.255.4.93 0x80000001 1053 0x59c9 44 Prefix feee::200:200:1:0/124 Prefix-options 0x0, Metric 10, Type 2, Gen timer 00:25:12 Aging timer 00:42:26 Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago OSPF3 Link-Local link state database, interface ge-1/3/0.0 Type ID Adv Rtr Seq Age Link *0.0.0.2 10.255.4.93 0x80000003 1059 1876 Cksum Len 0x4dab 64 Chapter 74: Operational Commands for Layer 3 Protocols fe80::290:69ff:fe39:1cdb Options 0x11, priority 128 Prefix-count 1 Prefix feee::10:10:2:0/126 Prefix-options 0x0 Gen timer 00:12:56 Aging timer 00:42:20 Installed 00:17:39 ago, expires in 00:42:21, sent 00:17:37 ago Link 0.0.0.2 10.255.4.97 0x80000003 205 0xa87d fe80::290:69ff:fe38:883e Options 0x11, priority 128 Prefix-count 1 Prefix feee::10:10:2:0/126 Prefix-options 0x0 Aging timer 00:56:35 Installed 00:03:22 ago, expires in 00:56:35, sent 02:37:54 ago 64 OSPF3 Link-Local link state database, interface so-2/2/0.0 Type ID Adv Rtr Seq Age Cksum Len Link 0.0.0.2 10.255.4.85 0x80000002 506 0x42bb 64 fe80::280:42ff:fe10:f169 Options 0x13, priority 128 Prefix-count 1 Prefix feee::10:10:1:0/126 Prefix-options 0x0 Aging timer 00:51:34 Installed 00:08:23 ago, expires in 00:51:34, sent 02:37:54 ago Link *0.0.0.3 10.255.4.93 0x80000002 505 0x6b7a 64 fe80::280:42ff:fe10:f177 Options 0x13, priority 128 Prefix-count 1 Prefix feee::10:10:1:0/126 Prefix-options 0x0 Gen timer 00:37:28 Aging timer 00:51:35 Installed 00:08:25 ago, expires in 00:51:35, sent 00:08:23 ago Ours show ospf3 database summary user@host> show ospf3 database summary Area 0.0.0.0: 2 Router LSAs 1 InterArPfx LSAs 1 InterArRtr LSAs 1 IntraArPfx LSAs Area 0.0.0.1: 2 Router LSAs 1 Network LSAs 2 InterArPfx LSAs 1 NSSA LSAs 1 IntraArPfx LSAs Externals: 2 Extern LSAs Interface ge-1/3/0.0: 1 Link LSAs Interface lo0.0: Interface so-2/2/0.0: 1 Link LSAs 1877 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ospf database Syntax Syntax (J-EX Series Switch) Release Information show ospf database show ospf database Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the entries in the Open Shortest Path First version 2 (OSPFv2) link-state database, which contains data about link-state advertisement (LSA) packets. Options none—Display standard information about entries in the OSPFv2 link-state database for all routing instances. brief | detail | extensive | summary—(Optional) Display the specified level of output. advertising-router (address | self)—(Optional) Display the LSAs advertised either by a particular routing device or by this routing device. area area-id—(Optional) Display the LSAs in a particular area. asbrsummary—(Optional) Display summary AS boundary router LSA entries. external—(Optional) Display external LSAs. 1878 Chapter 74: Operational Commands for Layer 3 Protocols instance instance-name—(Optional) Display all OSPF database information under the named routing instance. link-local—(Optional) Display information about link-local LSAs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. lsa-id lsa-id—(Optional) Display the LSA with the specified LSA identifier. netsummary—(Optional) Display summary network LSAs. network—(Optional) Display information about network LSAs. nssa—(Optional) Display information about not-so-stubby area (NSSA) LSAs. opaque-area—(Optional) Display opaque area-scope LSAs. router—(Optional) Display information about router LSAs. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear (ospf | ospf3) database on page 1748 show ospf database on page 1880 show ospf database brief on page 1881 show ospf database detail on page 1881 show ospf database extensive on page 1882 show ospf database summary on page 1884 Table 231 on page 1879 describes the output fields for the show ospf database command. Output fields are listed in the approximate order in which they appear. Table 231: show ospf database Output Fields Field Name Field Description Level of Output area Area number. Area 0.0.0.0 is the backbone area. All levels Type Type of link advertisement: ASBRSum, Extern, Network, NSSA, OpaqArea, Router, or Summary. All levels ID LSA identifier included in the advertisement. An asterisk preceding the identifier marks database entries that originated from the local routing device. All levels Adv Rtr Address of the routing device that sent the advertisement. All levels Seq Link sequence number of the advertisement. All levels Age Time elapsed since the LSA was originated, in seconds. All levels Cksum Checksum value of the LSA. All levels 1879 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 231: show ospf database Output Fields (continued) Field Name Field Description Level of Output Len Length of the advertisement, in bytes. All levels Router Router link-state advertisement information: detail extensive • bits—Flags describing the routing device that generated the LSP. • link count—Number of links in the advertisement. • id—ID of a routing device or subnet on the link. • data—For stub networks, the subnet mask; otherwise, the IP address of the routing device that generated the LSP. Network Summary • type—Type of link. It can be PointToPoint, Transit, Stub, or Virtual. • TOS count—Number of type-of-service (ToS) entries in the advertisement. • TOS 0 metric—Metric for ToS 0. • TOS—Type-of-service (ToS) value. • metric—Metric for the ToS. Network link-state advertisement information: • mask—Network mask. • attached router—ID of the attached neighbor. detail extensive Summary link-state advertisement information: • mask—Network mask. • TOS—Type-of-service (ToS) value. • metric—Metric for the ToS. detail extensive Gen timer How long until the LSA is regenerated. extensive Aging time How long until the LSA expires. extensive Installed hh:mm:ss ago How long ago the route was installed. extensive expires in hh:mm:ss How long until the route expires. extensive Ours Indicates that this is a local advertisement. extensive Router LSAs Number of router link-state advertisements in the link-state database. summary Network LSAs Number of network link-state advertisements in the link-state database. summary Summary LSAs Number of summary link-state advertisements in the link-state database. summary show ospf database 1880 user@host> show ospf database OSPF link state database, Area 0.0.0.1 Type ID Adv Rtr Router 10.255.70.103 10.255.70.103 Router *10.255.71.242 10.255.71.242 Seq 0x80000002 0x80000002 Age 215 214 Opt Cksum Len 0x20 0x4112 48 0x20 0x11b1 48 Chapter 74: Operational Commands for Layer 3 Protocols Summary *23.1.1.0 Summary *24.1.1.0 NSSA *33.1.1.1 10.255.71.242 10.255.71.242 10.255.71.242 0x80000002 0x80000002 0x80000002 172 177 217 0x20 0x6d72 0x20 0x607e 0x28 0x73bd 28 28 36 OSPF link state database, Area 0.0.0.2 Type ID Adv Rtr Router 10.255.71.52 10.255.71.52 Router *10.255.71.242 10.255.71.242 Network *23.1.1.1 10.255.71.242 Summary *12.1.1.0 10.255.71.242 Summary *24.1.1.0 10.255.71.242 NSSA *33.1.1.1 10.255.71.242 Seq 0x80000004 0x80000003 0x80000002 0x80000001 0x80000002 0x80000001 Age 174 173 173 217 177 222 Opt 0x20 0x20 0x20 0x20 0x20 0x28 Cksum Len 0xd021 36 0xe191 36 0x9c76 32 0xfeec 28 0x607e 28 0xe047 36 OSPF link state database, Area 0.0.0.3 Type ID Adv Rtr Router 10.255.71.238 10.255.71.238 Router *10.255.71.242 10.255.71.242 Network *24.1.1.1 10.255.71.242 Summary *12.1.1.0 10.255.71.242 Summary *23.1.1.0 10.255.71.242 NSSA *33.1.1.1 10.255.71.242 Seq 0x80000003 0x80000003 0x80000002 0x80000001 0x80000002 0x80000001 Age 179 177 177 217 172 222 Opt 0x20 0x20 0x20 0x20 0x20 0x28 Cksum Len 0x3942 36 0xf37d 36 0xc591 32 0xfeec 28 0x6d72 28 0xeb3b 36 show ospf database brief The output for the show ospf database brief command is identical to that for the show ospf database command. For sample output, see show ospf database on page 1880. show ospf database detail user@host> show ospf database detail OSPF link state database, Area 0.0.0.1 Type ID Adv Rtr Seq Age Router 10.255.70.103 10.255.70.103 0x80000002 261 bits 0x0, link count 2 id 10.255.71.242, data 12.1.1.1, Type PointToPoint (1) TOS count 0, TOS 0 metric 1 id 12.1.1.0, data 255.255.255.0, Type Stub (3) TOS count 0, TOS 0 metric 1 Router *10.255.71.242 10.255.71.242 0x80000002 260 bits 0x3, link count 2 id 10.255.70.103, data 12.1.1.2, Type PointToPoint (1) TOS count 0, TOS 0 metric 1 id 12.1.1.0, data 255.255.255.0, Type Stub (3) TOS count 0, TOS 0 metric 1 Summary *23.1.1.0 10.255.71.242 0x80000002 218 mask 255.255.255.0 TOS 0x0, metric 1 Summary *24.1.1.0 10.255.71.242 0x80000002 223 mask 255.255.255.0 TOS 0x0, metric 1 NSSA *33.1.1.1 10.255.71.242 0x80000002 263 mask 255.255.255.255 Type 2, TOS 0x0, metric 0, fwd addr 12.1.1.2, tag 0.0.0.0 OSPF link state database, Area 0.0.0.2 Type ID Adv Rtr Router 10.255.71.52 10.255.71.52 bits 0x0, link count 1 id 23.1.1.1, data 23.1.1.2, Type Transit TOS count 0, TOS 0 metric 1 Router *10.255.71.242 10.255.71.242 bits 0x3, link count 1 id 23.1.1.1, data 23.1.1.1, Type Transit TOS count 0, TOS 0 metric 1 Seq 0x80000004 Opt Cksum Len 0x20 0x4112 48 0x20 0x11b1 48 0x20 0x6d72 28 0x20 0x607e 28 0x28 0x73bd 36 Age 220 Opt Cksum Len 0x20 0xd021 36 219 0x20 0xe191 (2) 0x80000003 36 (2) 1881 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Network *23.1.1.1 10.255.71.242 0x80000002 219 mask 255.255.255.0 attached router 10.255.71.242 attached router 10.255.71.52 Summary *12.1.1.0 10.255.71.242 0x80000001 263 mask 255.255.255.0 TOS 0x0, metric 1 Summary *24.1.1.0 10.255.71.242 0x80000002 223 mask 255.255.255.0 TOS 0x0, metric 1 NSSA *33.1.1.1 10.255.71.242 0x80000001 268 mask 255.255.255.255 Type 2, TOS 0x0, metric 0, fwd addr 23.1.1.1, tag 0.0.0.0 OSPF link state database, Area 0.0.0.3 Type ID Adv Rtr Seq Age Router 10.255.71.238 10.255.71.238 0x80000003 225 bits 0x0, link count 1 id 24.1.1.1, data 24.1.1.2, Type Transit (2) TOS count 0, TOS 0 metric 1 Router *10.255.71.242 10.255.71.242 0x80000003 223 bits 0x3, link count 1 id 24.1.1.1, data 24.1.1.1, Type Transit (2) TOS count 0, TOS 0 metric 1 Network *24.1.1.1 10.255.71.242 0x80000002 223 mask 255.255.255.0 attached router 10.255.71.242 attached router 10.255.71.238 Summary *12.1.1.0 10.255.71.242 0x80000001 263 mask 255.255.255.0 TOS 0x0, metric 1 Summary *23.1.1.0 10.255.71.242 0x80000002 218 mask 255.255.255.0 TOS 0x0, metric 1 NSSA *33.1.1.1 10.255.71.242 0x80000001 268 mask 255.255.255.255 Type 2, TOS 0x0, metric 0, fwd addr 24.1.1.1, tag 0.0.0.0 show ospf database extensive 1882 user@host> show ospf database extensive OSPF link state database, Area 0.0.0.1 Type ID Adv Rtr Seq Age Router 10.255.70.103 10.255.70.103 0x80000002 286 bits 0x0, link count 2 id 10.255.71.242, data 12.1.1.1, Type PointToPoint (1) TOS count 0, TOS 0 metric 1 id 12.1.1.0, data 255.255.255.0, Type Stub (3) TOS count 0, TOS 0 metric 1 Aging timer 00:55:14 Installed 00:04:43 ago, expires in 00:55:14 Last changed 00:04:43 ago, Change count: 2 Router *10.255.71.242 10.255.71.242 0x80000002 285 bits 0x3, link count 2 id 10.255.70.103, data 12.1.1.2, Type PointToPoint (1) TOS count 0, TOS 0 metric 1 id 12.1.1.0, data 255.255.255.0, Type Stub (3) TOS count 0, TOS 0 metric 1 Gen timer 00:45:15 Aging timer 00:55:15 Installed 00:04:45 ago, expires in 00:55:15, sent 00:04:43 Last changed 00:04:45 ago, Change count: 2, Ours Summary *23.1.1.0 10.255.71.242 0x80000002 243 0x20 0x9c76 32 0x20 0xfeec 28 0x20 0x607e 28 0x28 0xe047 36 Opt Cksum Len 0x20 0x3942 36 0x20 0xf37d 36 0x20 0xc591 32 0x20 0xfeec 28 0x20 0x6d72 28 0x28 0xeb3b 36 Opt Cksum Len 0x20 0x4112 48 0x20 0x11b1 48 ago 0x20 0x6d72 28 Chapter 74: Operational Commands for Layer 3 Protocols mask 255.255.255.0 TOS 0x0, metric 1 Gen timer 00:45:57 Aging timer 00:55:57 Installed 00:04:03 ago, expires in 00:55:57, sent 00:04:01 Last changed 00:04:48 ago, Change count: 1, Ours Summary *24.1.1.0 10.255.71.242 0x80000002 248 mask 255.255.255.0 TOS 0x0, metric 1 Gen timer 00:45:52 Aging timer 00:55:52 Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:06 Last changed 00:04:48 ago, Change count: 1, Ours NSSA *33.1.1.1 10.255.71.242 0x80000002 288 mask 255.255.255.255 Type 2, TOS 0x0, metric 0, fwd addr 12.1.1.2, tag 0.0.0.0 Gen timer 00:45:12 Aging timer 00:55:12 Installed 00:04:48 ago, expires in 00:55:12, sent 00:04:48 Last changed 00:04:48 ago, Change count: 2, Ours OSPF link state database, Area 0.0.0.2 Type ID Adv Rtr Seq Age Router 10.255.71.52 10.255.71.52 0x80000004 245 bits 0x0, link count 1 id 23.1.1.1, data 23.1.1.2, Type Transit (2) TOS count 0, TOS 0 metric 1 Aging timer 00:55:55 Installed 00:04:02 ago, expires in 00:55:55 Last changed 00:04:02 ago, Change count: 2 Router *10.255.71.242 10.255.71.242 0x80000003 244 bits 0x3, link count 1 id 23.1.1.1, data 23.1.1.1, Type Transit (2) TOS count 0, TOS 0 metric 1 Gen timer 00:45:56 Aging timer 00:55:56 Installed 00:04:04 ago, expires in 00:55:56, sent 00:04:02 Last changed 00:04:04 ago, Change count: 2, Ours Network *23.1.1.1 10.255.71.242 0x80000002 244 mask 255.255.255.0 attached router 10.255.71.242 attached router 10.255.71.52 Gen timer 00:45:56 Aging timer 00:55:56 Installed 00:04:04 ago, expires in 00:55:56, sent 00:04:02 Last changed 00:04:04 ago, Change count: 1, Ours Summary *12.1.1.0 10.255.71.242 0x80000001 288 mask 255.255.255.0 TOS 0x0, metric 1 Gen timer 00:45:12 Aging timer 00:55:12 Installed 00:04:48 ago, expires in 00:55:12, sent 00:04:04 Last changed 00:04:48 ago, Change count: 1, Ours Summary *24.1.1.0 10.255.71.242 0x80000002 248 mask 255.255.255.0 TOS 0x0, metric 1 Gen timer 00:45:52 Aging timer 00:55:52 Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:04 Last changed 00:04:48 ago, Change count: 1, Ours NSSA *33.1.1.1 10.255.71.242 0x80000001 293 ago 0x20 0x607e 28 ago 0x28 0x73bd 36 ago Opt Cksum Len 0x20 0xd021 36 0x20 0xe191 36 ago 0x20 0x9c76 32 ago 0x20 0xfeec 28 ago 0x20 0x607e 28 ago 0x28 0xe047 36 1883 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mask 255.255.255.255 Type 2, TOS 0x0, metric 0, fwd addr 23.1.1.1, tag 0.0.0.0 Gen timer 00:45:07 Aging timer 00:55:07 Installed 00:04:53 ago, expires in 00:55:07, sent 00:04:04 ago Last changed 00:04:53 ago, Change count: 1, Ours OSPF link state database, Area 0.0.0.3 Type ID Adv Rtr Seq Age Router 10.255.71.238 10.255.71.238 0x80000003 250 bits 0x0, link count 1 id 24.1.1.1, data 24.1.1.2, Type Transit (2) TOS count 0, TOS 0 metric 1 Aging timer 00:55:50 Installed 00:04:07 ago, expires in 00:55:50 Last changed 00:04:07 ago, Change count: 2 Router *10.255.71.242 10.255.71.242 0x80000003 248 bits 0x3, link count 1 id 24.1.1.1, data 24.1.1.1, Type Transit (2) TOS count 0, TOS 0 metric 1 Gen timer 00:45:52 Aging timer 00:55:52 Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:06 Last changed 00:04:08 ago, Change count: 2, Ours Network *24.1.1.1 10.255.71.242 0x80000002 248 mask 255.255.255.0 attached router 10.255.71.242 attached router 10.255.71.238 Gen timer 00:45:52 Aging timer 00:55:52 Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:06 Last changed 00:04:08 ago, Change count: 1, Ours Summary *12.1.1.0 10.255.71.242 0x80000001 288 mask 255.255.255.0 TOS 0x0, metric 1 Gen timer 00:45:12 Aging timer 00:55:12 Installed 00:04:48 ago, expires in 00:55:12, sent 00:04:13 Last changed 00:04:48 ago, Change count: 1, Ours Summary *23.1.1.0 10.255.71.242 0x80000002 243 mask 255.255.255.0 TOS 0x0, metric 1 Gen timer 00:45:57 Aging timer 00:55:57 Installed 00:04:03 ago, expires in 00:55:57, sent 00:04:01 Last changed 00:04:48 ago, Change count: 1, Ours NSSA *33.1.1.1 10.255.71.242 0x80000001 293 mask 255.255.255.255 Type 2, TOS 0x0, metric 0, fwd addr 24.1.1.1, tag 0.0.0.0 Gen timer 00:45:07 Aging timer 00:55:07 Installed 00:04:53 ago, expires in 00:55:07, sent 00:04:13 Last changed 00:04:53 ago, Change count: 1, Ours show ospf database summary 1884 user@host> show ospf database summary Area 0.0.0.1: 2 Router LSAs 2 Summary LSAs 1 NSSA LSAs Area 0.0.0.2: 2 Router LSAs Opt Cksum Len 0x20 0x3942 36 0x20 0xf37d 36 ago 0x20 0xc591 32 ago 0x20 0xfeec 28 ago 0x20 0x6d72 28 ago 0x28 0xeb3b ago 36 Chapter 74: Operational Commands for Layer 3 Protocols 1 Network LSAs 2 Summary LSAs 1 NSSA LSAs Area 0.0.0.3: 2 Router LSAs 1 Network LSAs 2 Summary LSAs 1 NSSA LSAs Externals: Interface fe-2/2/1.0: Interface ge-0/3/2.0: Interface so-0/1/2.0: Interface so-0/1/2.0: 1885 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show policy damping Syntax Syntax (J-EX Series Switch) Release Information Description Options show policy damping show policy damping Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Border Gateway Protocol (BGP) route flap damping parameters. none—Display information about BGP route flap damping parameters. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields In the output from this command, figure-of-merit values correlate to the probability of future instability of a routing device. Routes with higher figure-of-merit values are suppressed for longer periods of time. The figure-of-merit value decays exponentially over time. A figure-of-merit value of zero is assigned to each new route. The value is increased each time the route is withdrawn or readvertised, or when one of its path attributes changes. view • “Configuring BGP Flap Damping Parameters” in the Junos OS Policy Framework Configuration Guide • clear bgp damping on page 1755 • show route damping on page 1922 show policy damping on page 1887 Table 232 on page 1886 describes the output fields for the show policy damping command. Output fields are listed in the approximate order in which they appear. Table 232: show policy damping Output Fields Field Name Field Description Halflife Decay half-life, in minutes. The value represents the period during which the accumulated figure-of-merit value is reduced by half if the route remains stable. If a route has flapped, but then becomes stable, the figure-of-merit value for the route decays exponentially. For example, for a route with a figure-of-merit value of 1500, if no incidents occur, its figure-of-merit value is reduced to 750 after 15 minutes and to 375 after another 15 minutes. 1886 Chapter 74: Operational Commands for Layer 3 Protocols Table 232: show policy damping Output Fields (continued) Field Name Field Description Reuse merit Figure-of-merit value below which a suppressed route can be used again. A suppressed route becomes reusable when its figure-of-merit value decays to a value below a reuse threshold, and the route once again is considered usable and can be installed in the forwarding table and exported from the routing table. Suppress/cutoff merit Figure-of-merit value above which a route is suppressed for use or inclusion in advertisements. When a route's figure-of-merit value reaches a particular level, called the cutoff or suppression threshold, the route is suppressed. When a route is suppressed, the routing table no longer installs the route into the forwarding table and no longer exports this route to any of the routing protocols. Maximum suppress time Maximum hold-down time, in minutes. The value represents the maximum time that a route can be suppressed no matter how unstable it has been before this period of stability. Computed values • Merit ceiling—Maximum merit that a flapping route can collect. • Maximum decay—Maximum decay half-life, in minutes. show policy damping user@host> show policy damping Default damping information: Halflife: 15 minutes Reuse merit: 750 Suppress/cutoff merit: 3000 Maximum suppress time: 60 minutes Computed values: Merit ceiling: 12110 Maximum decay: 6193 Damping information for "standard-damping": Halflife: 10 minutes Reuse merit: 4000 Suppress/cutoff merit: 8000 Maximum suppress time: 30 minutes Computed values: Merit ceiling: 32120 Maximum decay: 12453 1887 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show rip general-statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show rip general-statistics show rip general-statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display brief Routing Information Protocol (RIP) statistics. none—Display brief RIP statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear rip general-statistics on page 1769 show rip general-statistics on page 1888 Table 233 on page 1888 lists the output fields for the show rip general-statistics command. Output fields are listed in the approximate order in which they appear. Table 233: show rip general-statistics Output Fields show rip general-statistics 1888 Field Name Field Description bad msgs Number of invalid messages received. no recv intf Number of packets received with no matching interface. curr memory Amount of memory currently used by RIP. max memory Most memory used by RIP. user@host> show rip general-statistics RIPv2 I/O info: bad msgs : 0 no recv intf : 0 curr memory : 0 max memory : 0 Chapter 74: Operational Commands for Layer 3 Protocols show rip neighbor Syntax Syntax (J-EX Series Switch) Release Information Description Options show rip neighbor show rip neighbor Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Routing Information Protocol (RIP) neighbors. none—Display information about all RIP neighbors for all instances. instance (all | instance-name)—(Optional) Display RIP neighbor information for all instances or for only the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. name—(Optional) Display detailed information about only the specified RIP neighbor. Required Privilege Level List of Sample Output Output Fields view show rip neighbor on page 1890 Table 234 on page 1889 lists the output fields for the show rip neighbor command. Output fields are listed in the approximate order in which they appear. Table 234: show rip neighbor Output Fields Field Name Field Description Neighbor Name of RIP neighbor. State State of the connection: Up or Dn (Down). Source Address Source address. Destination Address Destination address. Send Mode Send options: broadcast, multicast, none, or version 1. Receive Mode Type of packets to accept: both, none, version 1, or version 2. In Met Metric added to incoming routes when advertising into RIP routes that were learned from other protocols. 1889 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show rip neighbor user@host> show rip neighbor Neighbor -------ge-2/3/0.0 at-5/1/1.42 at-5/1/0.42 at-5/1/0.0 so-0/0/0.0 1890 State ----Up Dn Dn Up Up Source Address ------192.168.9.105 (null) (null) 20.0.0.1 192.168.9.97 Destination Address ----------192.168.9.107 (null) (null) 224.0.0.9 224.0.0.9 Send Mode ---bcast mcast mcast mcast mcast Receive Mode ------both v2 only both both both In Met --1 3 3 3 3 Chapter 74: Operational Commands for Layer 3 Protocols show rip statistics Syntax show rip statistics Syntax (J-EX Series Switch) show rip statistics Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display Routing Information Protocol (RIP) statistics about messages sent and received on an interface, as well as information received from advertisements from other routing devices. Options none—Display RIP statistics for all routing instances. instance (all | instance-name—(Optional) Display RIP statistics for all instances or for only the specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level view Related Documentation • List of Sample Output clear rip statistics on page 1770 show rip statistics on page 1892 Output Fields Table 235 on page 1891 lists the output fields for the show rip statistics command. Output fields are listed in the approximate order in which they appear. Table 235: show rip statistics Output Fields Field Name Field Description RIP info Information about RIP on the specified interface: • port—UDP port number used for RIP. • holddown—Hold-down interval, in seconds. • rts learned—Number of routes learned through RIP. • rts held down—Number of routes held down by RIP. • rqsts dropped—Number of received request packets that were dropped. • resps dropped—Number of received response packets that were dropped. • restart—Graceful restart status. Displayed when RIP is or has been in the process of graceful restart. 1891 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 235: show rip statistics Output Fields (continued) Field Name Field Description logical-interface Name of the logical interface and its statistics: Counter • routes learned—Number of routes learned on the logical interface. • routes advertised—Number of routes advertised by the logical interface. • timeout—Timeout interval, in seconds. • update interval—Number of seconds since last update. List of counter types: • Updates Sent—Number of update messages sent. • Triggered Updates Sent—Number of triggered update messages sent. • Responses Sent—Number of response messages sent. • Bad Messages—Number of invalid messages received. • RIPv1 Updates Received—Number of RIPv1 update messages received. • RIPv1 Bad Route Entries—Number of RIPv1 invalid route entry messages received. • RIPv1 Updates Ignored—Number of RIPv1 update messages ignored. • RIPv2 Updates Received—Number of RIPv2 update messages received. • RIPv2 Bad Route Entries—Number of RIPv2 invalid route entry messages received. • RIPv2 Updates Ignored—Number of RIPv2 update messages that were ignored. • Authentication Failures—Number of received update messages that failed authentication. • RIP Requests Received—Number of RIP request messages received. • RIP Requests Ignored—Number of RIP request messages ignored. Total Total number of packets for the selected counter. Last 5 min Number of packets for the selected counter in the most recent 5-minute period. Last minute Number of packets for the selected counter in the most recent 1-minute period. show rip statistics 1892 user@host> show rip statistics so-0/0/0.0 RIP info: port 520; update interval: 30s; holddown 180s; timeout 120s restart in progress: restart time 60s; restart will complete in 55s rts learned rts held down rqsts dropped resps dropped 0 0 0 0 so-0/0/0.0: 0 routes learned; 501 routes advertised Counter Total Last 5 min Last minute ----------------- ----------- ----------Updates Sent 0 0 0 Triggered Updates Sent 0 0 0 Responses Sent 0 0 0 Bad Messages 0 0 0 RIPv1 Updates Received 0 0 0 RIPv1 Bad Route Entries 0 0 0 RIPv1 Updates Ignored 0 0 0 RIPv2 Updates Received 0 0 0 RIPv2 Bad Route Entries 0 0 0 RIPv2 Updates Ignored 0 0 0 Authentication Failures 0 0 0 Chapter 74: Operational Commands for Layer 3 Protocols RIP Requests Received RIP Requests Ignored 0 0 0 0 0 0 1893 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ripng general-statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show ripng general-statistics show ripng general-statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display general Routing Information Protocol next-generation (RIPng) statistics. none—Display general RIPng statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear ripng general-statistics on page 1771 show ripng general-statistics on page 1894 Table 236 on page 1894 lists the output fields for the show ripng general-statistics command. Output fields are listed in the approximate order in which they appear. Table 236: show ripng general-statistics Output Fields show ripng general-statistics 1894 Field Name Field Description bad msgs Number of invalid messages received. no recv intf Number of packets received with no matching interface. curr memory Amount of memory currently used by RIPng. max memory Most memory used by RIPng. user@host> show ripng general-statistics RIPng I/O info: bad msgs : 0 no recv intf : 0 curr memory : 0 max memory : 0 Chapter 74: Operational Commands for Layer 3 Protocols show ripng neighbor Syntax Syntax (J-EX Series Switch) Release Information Description Options show ripng neighbor show ripng neighbor Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Routing Information Protocol next-generation (RIPng) neighbors. none—Display information about all RIPng neighbors. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. name—(Optional) Display detailed information about a specific RIPng neighbor. Required Privilege Level List of Sample Output Output Fields view show ripng neighbor on page 1895 Table 237 on page 1895 lists the output fields for the show ripng neighbor command. Output fields are listed in the approximate order in which they appear. Table 237: show ripng neighbor Output Fields show ripng neighbor Field Name Field Description Neighbor Name of RIPng neighbor. State State of the connection: Up or Dn (Down). Source Address Source address. Destination Address Destination address. Send Mode Send options: broadcast, multicast, none, version 1, or yes. Receive Mode Type of packets to accept: both, none, version 1, or yes. In Met Metric added to incoming routes when advertising into RIPng routes that were learned from other protocols. user@host> show ripng neighbor Source Neighbor State Address Dest Address In Send Recv Met 1895 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS -------fe-0/0/2.0 1896 ----Up ------fe80::290:69ff:fe68:b002 ------ff02::9 ---- ---- --yes yes 1 Chapter 74: Operational Commands for Layer 3 Protocols show ripng statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show ripng statistics show ripng statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Routing Information Protocol next generation (RIPng) statistics about messages sent and received on an interface, as well as information received from advertisements from other routing devices. none—Display RIPng statistics for all neighbors. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. name—(Optional) Display detailed information about a specific RIPng neighbor. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear ripng statistics on page 1772 show ripng statistics on page 1898 Table 238 on page 1897 lists the output fields for the show ripng statistics command. Output fields are listed in the approximate order in which they appear. Table 238: show ripng statistics Output Fields Field Name Field Description RIPng info Information about RIPng on the specified interface: • port—UDP port number used for RIP. • holddown—Hold-down interval, in seconds. • rts learned—Number of routes learned through RIP. • rts held down—Number of routes held down by RIP. • rqsts dropped—Number of received request packets that were dropped. • resps dropped—Number of received response packets that were dropped. • restart—Graceful restart status. Displayed when RIPng is or has been in the process of graceful restart. 1897 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 238: show ripng statistics Output Fields (continued) Field Name Field Description logical-interface Name of the logical interface and its statistics: Counter • routes learned—Number of routes learned on the logical interface. • routes advertised—Number of routes advertised by the logical interface. • timeout—Timeout interval, in seconds. • update interval—Number of seconds since last update. List of counter types: • Updates Sent—Number of update messages sent. • Triggered Updates Sent—Number of triggered update messages sent. • Responses Sent—Number of response messages sent. • Bad Messages—Number of invalid messages received. • Updates Received—Number of RIPng update messages received. • Bad Route Entries—Number of RIPng invalid route entry messages received. • Updates Ignored—Number of RIPng update messages ignored. • RIPng Requests Received—Number of RIPng request messages received. • RIPng Requests Ignored—Number of RIPng request messages ignored. Total Total number of packets for the selected counter. Last 5 min Number of packets for the selected counter in the most recent 5-minute period. Last minute Number of packets for the selected counter in the most recent 1-minute period. show ripng statistics user@host> show ripng statistics RIPng info: port 521; holddown 120s; rts learned rts held down rqsts dropped 0 0 0 resps dropped 0 so-0/1/3.0: 0 routes learned; 1 routes advertised; timeout 180s; update interval 20s Counter Total Last 5 min Last minute ----------------- ----------- ----------Updates Sent 934 16 4 Triggered Updates Sent 1 0 0 Responses Sent 0 0 0 Bad Messages 0 0 0 Updates Received 0 0 0 Bad Route Entries 0 0 0 Updates Ignored 0 0 0 RIPng Requests Received 0 0 0 RIPng Requests Ignored 0 0 0 1898 Chapter 74: Operational Commands for Layer 3 Protocols show route Syntax show route Syntax (J-EX Series Switch) show route Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the active entries in the routing tables. Options none—Display brief information about all active entries in the routing tables. all—(Optional) Display information about all routing tables, including private, or internal, routing tables. destination-prefix—(Optional) Display active entries for the specified address or range of addresses. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. private—(Optional) Display information only about all private, or internal, routing tables. Required Privilege Level view List of Sample Output show route on page 1902 show route destination-prefix on page 1902 Output Fields Table 239 on page 1899 describes the output fields for the show route command. Output fields are listed in the approximate order in which they appear. Table 239: show route Output Fields Field Name Field Description routing-table-name Name of the routing table (for example, inet.0). number destinations Number of destinations for which there are routes in the routing table. number routes Number of routes in the routing table and total number of routes in the following states: • active (routes that are active). • holddown (routes that are in the pending state before being declared inactive). • hidden (routes that are not used because of a routing policy). 1899 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 239: show route Output Fields (continued) Field Name Field Description destination-prefix Route destination (for example:10.0.0.1/24). Sometimes the route information is presented in another format, such as: • MPLS-label (for example, 80001). • interface-name (for example, ge-1/0/2). • neighbor-address:control-word-status:encapsulation type:vc-id :source (Layer 2 circuit only; for example, 10.1.1.195:NoCtrlWord:1:1:Local/96): • neighbor-address—Address of the neighbor. • control-word-status—Whether the use of the control word has been negotiated for this virtual circuit: NoCtrlWord or CtrlWord. • encapsulation type—Type of encapsulation, represented by a number: (1) Frame Relay DLCI, (2) ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet, (6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport. • • [ protocol, preference ] vc-id—Virtual circuit identifier. source—Source of the advertisement: Local or Remote. Protocol from which the route was learned and the preference value for the route. • +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table. • - —A hyphen indicates the last active route. • *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route. In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value. weeks:days hours:minutes:seconds How long the route been known (for example, 2w4d 13:11:14, or 2 weeks, 4 days, 13 hours, 11 minutes and 14 seconds). metric Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined by a preference value. localpref Local preference value included in the route. from Interface from which the route was received. 1900 Chapter 74: Operational Commands for Layer 3 Protocols Table 239: show route Output Fields (continued) Field Name Field Description AS path AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. When AS path numbers are included in the route, the format is as follows: • [ ]—Brackets enclose the local AS number associated with the AS path if more than one AS number is configured on the routing device, or if AS path prepending is configured. • { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order. • ( )—Parentheses enclose a confederation. • ( [ ] )—Parentheses and brackets enclose a confederation set. to Next hop to the destination. An angle bracket (>) indicates that the route is the selected route. via Interface used to reach the next hop. If there is more than one interface available to the next hop, the interface that is actually used is followed by the word Selected. This field can also contain the following information: • Weight—Value used to distinguish primary, secondary, and fast reroute backup routes. Weight information is available when Multiprotocol Label Switching (MPLS) label-switched path (LSP) link protection, node-link protection, or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight value is preferred. Among routes with the same weight value, load balancing is possible. • Balance—Balance coefficient indicating how traffic of unequal cost is distributed among next hops when a routing device is performing unequal-cost load balancing. This information is available when you enable Border Gateway Protocol (BGP) multipath load balancing. • lsp-path-name—Name of the label-switched path (LSP) used to reach the next hop. • label-action—MPLS label and operation occurring at the next hop. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label). 1901 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route user@host> show route inet.0: 10 destinations, 10 routes (9 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 0.0.0.0/0 *[Static/5] 1w5d 20:30:29 Discard 10.255.245.51/32 *[Direct/0] 2w4d 13:11:14 > via lo0.0 172.16.0.0/12 *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via fxp0.0 192.168.0.0/18 *[Static/5] 1w5d 20:30:29 > to 192.168.167.254 via fxp0.0 192.168.40.0/22 *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via fxp0.0 192.168.64.0/18 *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via fxp0.0 192.168.164.0/22 *[Direct/0] 2w4d 13:11:14 > via fxp0.0 192.168.164.51/32 *[Local/0] 2w4d 13:11:14 Local via fxp0.0 207.17.136.192/32 *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via fxp0.0 green.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 100.101.0.0/16 *[Direct/0] 1w5d 20:30:28 > via fe-0/0/3.0 100.101.2.3/32 *[Local/0] 1w5d 20:30:28 Local via fe-0/0/3.0 224.0.0.5/32 *[OSPF/10] 1w5d 20:30:29, metric 1 MultiRecv red.inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.10.10.10/32 *[Direct/0] 01:08:46 > via lo0.1 10.255.245.212/32 *[BGP/170] 00:01:40, localpref 100, from 10.255.245.204 AS path: 300 I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix 10.255.245.213/32 *[BGP/170] 00:40:47, localpref 100 AS path: 100 I > to 100.1.1.1 via so-0/0/1.0 show route destination-prefix user@host> show route 172.16.0.0/12 inet.0: 10 destinations, 10 routes (9 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 172.16.0.0/12 1902 *[Static/5] 2w4d 12:54:27 > to 192.168.167.254 via fxp0.0 Chapter 74: Operational Commands for Layer 3 Protocols show route active-path Syntax Syntax (J-EX Series Switch) Release Information Description Options show route active-path show route active-path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display all active routes for destinations. An active route is a route that is selected as the best path. Inactive routes are not displayed. none—Display all active routes. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route active-path view show route active-path on page 1903 show route active-path brief on page 1904 show route active-path detail on page 1904 show route active-path extensive on page 1905 show route active-path terse on page 1906 For information about output fields, see the output field tables for the show route command, the show route detail, the show route extensive, or the show route terse. user@host> show route active-path inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 10.255.70.19/32 10.255.71.50/32 100.1.2.0/24 100.1.2.2/32 192.168.64.0/21 192.168.70.19/32 *[Direct/0] 21:33:52 > via lo0.0 *[IS-IS/15] 00:18:13, metric 10 > to 100.1.2.1 via so-2/1/3.0 *[Direct/0] 00:18:36 > via so-2/1/3.0 *[Local/0] 00:18:41 Local via so-2/1/3.0 *[Direct/0] 21:33:52 > via fxp0.0 *[Local/0] 21:33:52 Local via fxp0.0 1903 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route active-path brief The output for the show route active-path brief command is identical to that for the show route active-path command. For sample output, see show route active-path on page 1903. show route active-path detail user@host> show route active-path detail inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden) 10.255.70.19/32 (1 entry, 1 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 3 Next hop: via lo0.0, selected State: ‹Active Int› Local AS: 200 Age: 21:37:10 Task: IF Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3 AS path: I 10.255.71.50/32 (1 entry, 1 announced) *IS-IS Preference: 15 Level: 1 Next hop type: Router, Next hop index: 397 Next-hop reference count: 4 Next hop: 100.1.2.1 via so-2/1/3.0, selected State: ‹Active Int› Local AS: 200 Age: 21:31 Metric: 10 Task: IS-IS Announcement bits (4): 0-KRT 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3 AS path: I 100.1.2.0/24 (1 entry, 1 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 3 Next hop: via so-2/1/3.0, selected State: ‹Active Int› Local AS: 200 Age: 21:54 Task: IF Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3 AS path: I 100.1.2.2/32 (1 entry, 1 announced) *Local Preference: 0 Next hop type: Local Next-hop reference count: 11 Interface: so-2/1/3.0 State: ‹Active NoReadvrt Int› Local AS: 200 Age: 21:59 Task: IF Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3 AS path: I 192.168.64.0/21 (1 entry, 1 announced) 1904 Chapter 74: Operational Commands for Layer 3 Protocols *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 3 Next hop: via fxp0.0, selected State: ‹Active Int› Local AS: 200 Age: 21:37:10 Task: IF Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3 AS path: I 192.168.70.19/32 (1 entry, 1 announced) *Local Preference: 0 Next hop type: Local Next-hop reference count: 11 Interface: fxp0.0 State: ‹Active NoReadvrt Int› Local AS: 200 Age: 21:37:10 Task: IF Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3 AS path: I show route active-path extensive user@host> show route active-path extensive inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden) 10.255.70.19/32 (1 entry, 1 announced) TSI: IS-IS level 1, LSP fragment 0 IS-IS level 2, LSP fragment 0 *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 3 Next hop: via lo0.0, selected State: ‹Active Int› Local AS: 200 Age: 21:39:47 Task: IF Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3 AS path: I 10.255.71.50/32 (1 entry, 1 announced) TSI: KRT in-kernel 10.255.71.50/32 -> {100.1.2.1} IS-IS level 2, LSP fragment 0 *IS-IS Preference: 15 Level: 1 Next hop type: Router, Next hop index: 397 Next-hop reference count: 4 Next hop: 100.1.2.1 via so-2/1/3.0, selected State: ‹Active Int› Local AS: 200 Age: 24:08 Metric: 10 Task: IS-IS Announcement bits (4): 0-KRT 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3 AS path: I 100.1.2.0/24 (1 entry, 1 announced) TSI: 1905 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS IS-IS level 1, LSP fragment 0 IS-IS level 2, LSP fragment 0 *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 3 Next hop: via so-2/1/3.0, selected State: ‹Active Int› Local AS: 200 Age: 24:31 Task: IF Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3 AS path: I 100.1.2.2/32 (1 entry, 1 announced) *Local Preference: 0 Next hop type: Local Next-hop reference count: 11 Interface: so-2/1/3.0 State: ‹Active NoReadvrt Int› Local AS: 200 Age: 24:36 Task: IF Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3 AS path: I 192.168.64.0/21 (1 entry, 1 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 3 Next hop: via fxp0.0, selected State: ‹Active Int› Local AS: 200 Age: 21:39:47 Task: IF Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3 AS path: I 192.168.70.19/32 (1 entry, 1 announced) *Local Preference: 0 Next hop type: Local Next-hop reference count: 11 Interface: fxp0.0 State: ‹Active NoReadvrt Int› Local AS: 200 Age: 21:39:47 Task: IF Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3 AS path: I show route active-path terse user@host> show route active-path terse inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A * * * * 1906 Destination 10.255.70.19/32 10.255.71.50/32 100.1.2.0/24 100.1.2.2/32 P Prf D 0 I 15 D 0 L 0 Metric 1 10 Metric 2 Next hop >lo0.0 >100.1.2.1 >so-2/1/3.0 Local AS path Chapter 74: Operational Commands for Layer 3 Protocols * 192.168.64.0/21 * 192.168.70.19/32 D L 0 0 >fxp0.0 Local 1907 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route all Syntax Syntax (J-EX Series Switch) Release Information Description Options show route all show route all Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about all routes in all routing tables, including private, or internal, tables. none—Display information about all routes in all routing tables, including private, or internal, tables. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output view show route all on page 1908 Output Fields The output fields for the show route all command display all routing tables, including private, or hidden, routing tables. The output field table of the show route command does not display entries for private, or hidden, routing tables. show route all The following example displays a snippet of output from the show route command and then displays the same snippet of output from the show route all command: user@host> show route mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 0 *[MPLS/0] 2d 02:24:39, metric 1 Receive 1 *[MPLS/0] 2d 02:24:39, metric 1 Receive 2 *[MPLS/0] 2d 02:24:39, metric 1 Receive 800017 *[VPLS/7] 1d 14:00:16 > via vt-3/2/0.32769, Pop 800018 *[VPLS/7] 1d 14:00:26 > via vt-3/2/0.32772, Pop user@host> show route all mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 0 *[MPLS/0] 2d 02:19:12, metric 1 Receive 1 *[MPLS/0] 2d 02:19:12, metric 1 Receive 2 *[MPLS/0] 2d 02:19:12, metric 1 1908 Chapter 74: Operational Commands for Layer 3 Protocols 800017 800018 vt-3/2/0.32769 vt-3/2/0.32772 Receive *[VPLS/7] 1d 13:54:49 > via vt-3/2/0.32769, Pop *[VPLS/7] 1d 13:54:59 > via vt-3/2/0.32772, Pop [VPLS/7] 1d 13:54:49 Unusable [VPLS/7] 1d 13:54:59 Unusable 1909 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route aspath-regex Syntax Syntax (J-EX Series Switch) Release Information Description Options show route aspath-regex regular-expression show route aspath-regex regular-expression Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the routing table that match the specified autonomous system (AS) path regular expression. regular-expression—Regular expression that matches an entire AS path. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information You can specify a regular expression as: • An individual AS number • A period wildcard used in place of an AS number • An AS path regular expression that is enclosed in parentheses You also can include the operators described in the table of AS path regular expression operators in the Junos OS Policy Framework Configuration Guide. The following list summarizes these operators: • {m,n}—At least m and at most n repetitions of the AS path term. • {m}—Exactly m repetitions of the AS path term. • {m,}—m or more repetitions of the AS path term. • *—Zero or more repetitions of an AS path term. • +—One or more repetitions of an AS path term. • ?—Zero or one repetition of an AS path term. • aspath_term | aspath_term—Match one of the two AS path terms. When you specify more than one AS number or path term, or when you include an operator in the regular expression, enclose the entire regular expression in quotation marks. For example, to match any path that contains AS number 234, specify the following command: show route aspath-regex ".* 234 .*" Required Privilege Level 1910 view Chapter 74: Operational Commands for Layer 3 Protocols List of Sample Output Output Fields show route aspath-regex (Matching a Specific AS Number) show route aspath-regex (Matching a Specific AS Number) on page 1911 show route aspath-regex (Matching Any Path with Two AS Numbers) on page 1911 For information about output fields, see the output field table for the show route command. user@host> show route aspath-regex 65477 inet.0: 46411 destinations, 46411 routes (46409 active, 0 holddown, 2 hidden) + = Active Route, - = Last Active, * = Both 111.222.1.0/25 111.222.1.128/25 *[BGP/170] 00:08:48, localpref 100, from 111.222.2.24 AS Path: [65477] ({65488 65535}) IGP to 111.222.18.225 via fpa0.0(111.222.18.233) *[IS-IS/15] 09:15:37, metric 37, tag 1 to 111.222.18.225 via fpa0.0(111.222.18.233) [BGP/170] 00:08:48, localpref 100, from 111.222.2.24 AS Path: [65477] ({65488 65535}) IGP to 111.222.18.225 via fpa0.0(111.222.18.233) ... show route aspath-regex (Matching Any Path with Two AS Numbers) user@host> show route aspath-regex ?.* 234 3561 .*? inet.0: 46351 destinations, 46351 routes (46349 active, 0 holddown, 2 hidden) + = Active Route, - = Last Active, * = Both 9.20.0.0/17 12.10.231.0/24 24.64.32.0/19 *[BGP/170] 01:35:00, localpref 100, from 131.103.20.49 AS Path: [666] 234 3561 2685 2686 Incomplete to 192.156.169.1 via 192.156.169.14(so-0/0/0) *[BGP/170] 01:35:00, localpref 100, from 131.103.20.49 AS Path: [666] 234 3561 5696 7369 IGP to 192.156.169.1 via 192.156.169.14(so-0/0/0) *[BGP/170] 01:34:59, localpref 100, from 131.103.20.49 AS Path: [666] 234 3561 6327 IGP to 192.156.169.1 via 192.156.169.14(so-0/0/0) ... 1911 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route best Syntax Syntax (J-EX Series Switch) Release Information Description Options show route best destination-prefix show route best destination-prefix Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the route in the routing table that is the best route to the specified address or range of addresses. The best route is the longest matching route. destination-prefix—Address or range of addresses. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route best view show route best on page 1912 show route best detail on page 1914 show route best extensive on page 1914 show route best terse on page 1915 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route best 10.255.70.103 inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.255.70.103/32 *[OSPF/10] 1d 13:19:20, metric 2 > to 10.31.1.6 via ge-3/1/0.0 via so-0/3/0.0 inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.255.70.103/32 *[RSVP/7] 1d 13:20:13, metric 2 > via so-0/3/0.0, label-switched-path green-r1-r3 private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.0/8 *[Direct/0] 2d 01:43:34 > via fxp2.0 1912 Chapter 74: Operational Commands for Layer 3 Protocols [Direct/0] 2d 01:43:34 > via fxp1.0 1913 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route best detail user@host> show route best 10.255.70.103 detail inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete 10.255.70.103/32 (1 entry, 1 announced) *OSPF Preference: 10 Next-hop reference count: 9 Next hop: 10.31.1.6 via ge-3/1/0.0, selected Next hop: via so-0/3/0.0 State: Local AS: 69 Age: 1d 13:20:06 Metric: 2 Area: 0.0.0.0 Task: OSPF Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103/32 (1 entry, 1 announced) State: *RSVP Preference: 7 Next-hop reference count: 5 Next hop: via so-0/3/0.0 weight 0x1, selected Label-switched-path green-r1-r3 Label operation: Push 100016 State: Local AS: 69 Age: 1d 13:20:59 Metric: 2 Task: RSVP Announcement bits (1): 1-Resolve tree 2 AS path: I private1__inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) 10.0.0.0/8 (2 entries, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via fxp2.0, selected State: Age: 2d 1:44:20 Task: IF AS path: I Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via fxp1.0, selected State: Inactive reason: No difference Age: 2d 1:44:20 Task: IF AS path: I show route best extensive 1914 The output for the show route best extensive command is identical to that for the show route best detail command. For sample output, see the show route best detail on page 1914. Chapter 74: Operational Commands for Layer 3 Protocols show route best terse user@host> show route best 10.255.70.103 terse inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both A Destination * 10.255.70.103/32 P Prf O 10 Metric 1 2 Metric 2 Next hop >10.31.1.6 so-0/3/0.0 AS path inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both A Destination * 10.255.70.103/32 P Prf R 7 Metric 1 2 Metric 2 Next hop >so-0/3/0.0 AS path private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A Destination * 10.0.0.0/8 P Prf D 0 D 0 Metric 1 Metric 2 Next hop >fxp2.0 >fxp1.0 AS path 1915 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route brief Syntax Syntax (J-EX Series Switch) Release Information Description Options show route brief show route brief Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display brief information about the active entries in the routing tables. none—Display all active entries in the routing table. destination-prefix—(Optional) Display active entries for the specified address or range of addresses. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route brief view show route brief on page 1916 For information about output fields, see the Output Field table of the show route command. user@host> show route brief inet.0: 10 destinations, 10 routes (9 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 0.0.0.0/0 10.255.245.51/32 172.16.0.0/12 192.168.0.0/18 192.168.40.0/22 192.168.64.0/18 192.168.164.0/22 192.168.164.51/32 207.17.136.192/32 1916 *[Static/5] 1w5d 20:30:29 Discard *[Direct/0] 2w4d 13:11:14 > via lo0.0 *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via *[Static/5] 1w5d 20:30:29 > to 192.168.167.254 via *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via *[Direct/0] 2w4d 13:11:14 > via fxp0.0 *[Local/0] 2w4d 13:11:14 Local via fxp0.0 *[Static/5] 2w4d 13:11:14 > to 192.168.167.254 via fxp0.0 fxp0.0 fxp0.0 fxp0.0 fxp0.0 Chapter 74: Operational Commands for Layer 3 Protocols green.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 100.101.0.0/16 *[Direct/0] 1w5d 20:30:28 > via fe-0/0/3.0 100.101.2.3/32 *[Local/0] 1w5d 20:30:28 Local via fe-0/0/3.0 224.0.0.5/32 *[OSPF/10] 1w5d 20:30:29, metric 1 MultiRecv 1917 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route community Syntax show route community as-number:community-value Syntax (J-EX Series Switch) show route community as-number:community-value Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the route entries in each routing table that are members of a Border Gateway Protocol (BGP) community. Options as-number:community-value—One or more community identifiers. as-number is the AS number, and community-value is the community identifier. When you specify more than one community identifier, enclose the identifiers in double quotation marks. Community identifiers can include wildcards. brief | detail | extensive | terse—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information Required Privilege Level Related Documentation List of Sample Output Specifying the community option displays all routes matching the community found within the routing table. The community option does not limit the output to only the routes being advertised to the neighbor after any egress routing policy. view • show route detail on page 1927 show route community on page 1918 Output Fields For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. show route community user@host> show route community 234:80 inet.0: 46511 destinations, 46511 routes (46509 active, 0 holddown, 2 hidden) + = Active Route, - = Last Active, * = Both 4.0.0.0/8 6.0.0.0/8 9.2.0.0/16 1918 *[BGP/170] 03:33:07, localpref 100, from 131.103.20.49 AS Path: {666} 234 2548 1 IGP to 192.156.169.1 via 192.156.169.14(so-0/0/0) *[BGP/170] 03:33:07, localpref 100, from 131.103.20.49 AS Path: {666} 234 2548 568 721 Incomplete to 192.156.169.1 via 192.156.169.14(so-0/0/0) *[BGP/170] 03:33:06, localpref 100, from 131.103.20.49 Chapter 74: Operational Commands for Layer 3 Protocols AS Path: {666} 234 2548 1673 1675 1747 IGP to 192.156.169.1 via 192.156.169.14(so-0/0/0) 1919 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route community-name Syntax show route community-name community-name Syntax (J-EX Series Switch) show route community-name community-name Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the route entries in each routing table that are members of a Border Gateway Protocol (BGP) community, specified by a community name. community-name—Name of the community. brief | detail | extensive | terse—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route community-name view show route community-name on page 1920 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route community-name red-com inet.0: 17 destinations, 17 routes (16 active, 0 holddown, 1 hidden) inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) instance1.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) red.inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.255.245.212/32 20.20.20.20/32 100.1.4.0/24 *[BGP/170] 00:04:40, localpref 100, from 10.255.245.204 AS path: 300 I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix *[BGP/170] 00:04:40, localpref 100, from 10.255.245.204 AS path: I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix *[BGP/170] 00:04:40, localpref 100, from 10.255.245.204 AS path: I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) 1920 Chapter 74: Operational Commands for Layer 3 Protocols + = Active Route, - = Last Active, * = Both 10.255.245.204:10:10.255.245.212/32 *[BGP/170] 00:06:40, localpref 100, from 10.255.245.204 AS path: 300 I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix 10.255.245.204:10:20.20.20.20/32 *[BGP/170] 00:36:02, localpref 100, from 10.255.245.204 AS path: I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix 10.255.245.204:10:100.1.4.0/24 *[BGP/170] 00:36:02, localpref 100, from 10.255.245.204 AS path: I > to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) instance1.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 1921 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route damping Syntax show route damping (decayed | history | suppressed) Syntax (J-EX Series Switch) show route damping (decayed | history | suppressed) Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the Border Gateway Protocol (BGP) routes for which updates might have been reduced because of route flap damping. Options brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. decayed—Display route damping entries that might no longer be valid, but are not suppressed. history—Display entries that have already been withdrawn, but have been logged. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. suppressed—Display entries that have been suppressed and are no longer being installed into the forwarding table or exported by routing protocols. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear bgp damping on page 1755 • show policy damping on page 1886 show route damping decayed detail on page 1925 show route damping history on page 1925 show route damping history detail on page 1926 Table 240 on page 1922 lists the output fields for the show route damping command. Output fields are listed in the approximate order in which they appear. Table 240: show route damping Output Fields Field Name Field Description Level of Output routing-table-name Name of the routing table—for example,inet.0. All levels destinations Number of destinations for which there are routes in the routing table. All levels 1922 Chapter 74: Operational Commands for Layer 3 Protocols Table 240: show route damping Output Fields (continued) Field Name Field Description Level of Output number routes Number of routes in the routing table and total number of routes in the following states: All levels • active • holddown (routes that are in a pending state before being declared inactive) • hidden (the routes are not used because of a routing policy) destination-prefix (entry, announced) Destination prefix. The entry value is the number of routes for this destination, and the announced value is the number of routes being announced for this destination. detail extensive [protocol, preference] Protocol from which the route was learned and the preference value for the route. All levels • +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table. • - —A hyphen indicates the last active route. • *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route. In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value. Next-hop reference count Number of references made to the next hop. detail extensive Source IP address of the route source. detail extensive Next hop Network layer address of the directly reachable neighboring system. detail extensive via Interface used to reach the next hop. If there is more than one interface available to the next hop, the interface that is actually used is followed by the word Selected. detail extensive Protocol next hop Network layer address of the remote routing device that advertised the prefix. This address is used to derive a forwarding next hop. detail extensive Indirect next hop Index designation used to specify the mapping between protocol next hops, tags, kernel export policy, and the forwarding next hops. detail extensive State Flags for this route. For a description of possible values for this field, see the output field table for the show route detail command. detail extensive Local AS AS number of the local routing device. detail extensive Peer AS AS number of the peer routing device. detail extensive 1923 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 240: show route damping Output Fields (continued) Field Name Field Description Level of Output Age How long the route has been known. detail extensive Metric Metric for the route. detail extensive Task Name of the protocol that has added the route. detail extensive Announcement bits List of protocols that announce this route. n-Resolve inet indicates that the route is used for route resolution for next hops found in the routing table. n is an index used by Dell Support only (see “Requesting Technical Support” on page lxxi). detail extensive AS path AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: All levels • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. When AS path numbers are included in the route, the format is as follows: • [ ]—Brackets enclose the local AS number associated with the AS path if more than one AS number is configured on the routing device or if AS path prepending is configured. • { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order. • ( )—Parentheses enclose a confederation. • ( [ ] )—Parentheses and brackets enclose a confederation set. to Next hop to the destination. An angle bracket (>) indicates that the route is the selected route. brief none via Interface used to reach the next hop. If there is more than one interface available to the next hop, the interface that is actually used is followed by the word Selected. brief none Communities Community path attribute for the route. See the output field table for the show route detail command. detail extensive Localpref Local preference value included in the route. All levels Router ID BGP router ID as advertised by the neighbor in the open message. detail extensive Merit (last update/now) Last updated and current figure-of-merit value. detail extensive damping-parameters Name that identifies the damping parameters used, which is defined in the damping statement at the [edit policy-options] hierarchy level. detail extensive Last update Time of most recent change in path attributes. detail extensive 1924 Chapter 74: Operational Commands for Layer 3 Protocols Table 240: show route damping Output Fields (continued) Field Name Field Description Level of Output First update Time of first change in path attributes, which started the route damping process. detail extensive Flaps Number of times the route has gone up or down or its path attributes have changed. detail extensive Suppressed (suppressed keyword only) This route is currently suppressed. A suppressed route does not appear in the forwarding table and routing protocols do not export it. All levels Reusable in (suppressed keyword only) Time when a suppressed route will again be available. All levels Preference will be (suppressed keyword only) Preference value that will be applied to the route when it is again active. All levels show route damping decayed detail user@host> show route damping decayed detail inet.0: 173319 destinations, 1533668 routes (172625 active, 4 holddown, 108083 hidden) 10.0.111.0/24 (7 entries, 1 announced) *BGP Preference: 170/-101 Next-hop reference count: 151973 Source: 172.23.2.129 Next hop: via so-1/2/0.0 Next hop: via so-5/1/0.0, selected Next hop: via so-6/0/0.0 Protocol next hop: 172.23.2.129 Indirect next hop: 89a1a00 264185 State: Local AS: 65000 Peer AS: 65490 Age: 3:28 Metric2: 0 Task: BGP_65490.172.23.2.129+179 Announcement bits (6): 0-KRT 1-RT 4-KRT 5-BGP.0.0.0.0+179 6-Resolve tree 2 7-Resolve tree 3 AS path: 65490 65520 65525 65525 65525 65525 I () Communities: 65501:390 65501:2000 65501:3000 65504:701 Localpref: 100 Router ID: 172.23.2.129 Merit (last update/now): 1934/1790 damping-parameters: damping-high Last update: 00:03:28 First update: 00:06:40 Flaps: 2 show route damping history user@host> show route damping history inet.0: 173320 destinations, 1533529 routes (172624 active, 6 holddown, 108122 hidden) + = Active Route, - = Last Active, * = Both 10.108.0.0/15 [BGP ] 2d 22:47:58, localpref 100 AS path: 65220 65501 65502 I > to 192.168.60.85 via so-3/1/0.0 1925 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route damping history detail 1926 user@host> show route damping history detail inet.0: 173319 destinations, 1533435 routes (172627 active, 2 holddown, 108105 hidden) 10.108.0.0/15 (3 entries, 1 announced) BGP /-101 Next-hop reference count: 69058 Source: 192.168.60.85 Next hop: 192.168.60.85 via so-3/1/0.0, selected State: Inactive reason: Unusable path Local AS: 65000 Peer AS: 65220 Age: 2d 22:48:10 Task: BGP_65220.192.168.60.85+179 AS path: 65220 65501 65502 I () Communities: 65501:390 65501:2000 65501:3000 65504:3561 Localpref: 100 Router ID: 192.168.80.25 Merit (last update/now): 1000/932 damping-parameters: set-normal Last update: 00:01:05 First update: 00:01:05 Flaps: 1 Chapter 74: Operational Commands for Layer 3 Protocols show route detail Syntax show route detail Syntax (J-EX Series Switch) show route detail Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display detailed information about the active entries in the routing tables. Options none—Display all active entries in the routing table on all systems. destination-prefix—(Optional) Display active entries for the specified address or range of addresses. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level view List of Sample Output show route detail on page 1935 Output Fields Table 241 on page 1927 describes the output fields for the show route detail command. Output fields are listed in the approximate order in which they appear. Table 241: show route detail Output Fields Field Name Field Description routing-table-name Name of the routing table (for example, inet.0). number destinations Number of destinations for which there are routes in the routing table. number routes Number of routes in the routing table and total number of routes in the following states: • active (routes that are active) • holddown (routes that are in the pending state before being declared inactive) • hidden (routes that are not used because of a routing policy) 1927 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 241: show route detail Output Fields (continued) Field Name Field Description route-destination (entry, announced) Route destination (for example:10.0.0.1/24). The entry value is the number of routes for this destination, and the announced value is the number of routes being announced for this destination. Sometimes the route destination is presented in another format, such as: • MPLS-label (for example, 80001). • interface-name (for example, ge-1/0/2). • neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example, 10.1.1.195:NoCtrlWord:1:1:Local/96). • neighbor-address—Address of the neighbor. • control-word-status—Whether the use of the control word has been negotiated for this virtual circuit: NoCtrlWord or CtrlWord. • encapsulation type—Type of encapsulation, represented by a number: (1) Frame Relay DLCI, (2) ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet, (6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport label stacking • vc-id—Virtual circuit identifier. • source—Source of the advertisement: Local or Remote. (Next-to-the-last-hop routing device for MPLS only) Depth of the Multiprotocol Label Switching (MPLS) label stack, where the label-popping operation is needed to remove one or more labels from the top of the stack. A pair of routes is displayed, because the pop operation is performed only when the stack depth is two or more labels. • S=0 route indicates that a packet with an incoming label stack depth of 2 or more exits this routing device with one fewer label (the label-popping operation is performed). • [protocol, preference] If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the label-popping operation is not performed). Protocol from which the route was learned and the preference value for the route. • +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table. • - —A hyphen indicates the last active route. • *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route. In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value. Level (IS-IS only). In IS-IS, a single AS can be divided into smaller groups called areas. Routing between areas is organized hierarchically, allowing a domain to be administratively divided into smaller areas. This organization is accomplished by configuring Level 1 and Level 2 intermediate systems. Level 1 systems route within an area; when the destination is outside an area, they route toward a Level 2 system. Level 2 intermediate systems route between areas and toward other ASs. Route Distinguisher IP subnet augmented with a 64-bit prefix. Next-hop type Type of next hop. For a description of possible values for this field, see Table 242 on page 1931. 1928 Chapter 74: Operational Commands for Layer 3 Protocols Table 241: show route detail Output Fields (continued) Field Name Field Description Next-hop reference count Number of references made to the next hop. Source IP address of the route source. Next hop Network layer address of the directly reachable neighboring system. via Interface used to reach the next hop. If there is more than one interface available to the next hop, the name of interface that is actually used is followed by the word Selected. This field can also contain the following information: • Weight—Value used to distinguish primary, secondary, and fast reroute backup routes. Weight information is available when Multiprotocol Label Switching (MPLS) label-switched path (LSP) link protection, node-link protection, or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight value is preferred. Among routes with the same weight value, load balancing is possible. • Balance—Balance coefficient indicating how traffic of unequal cost is distributed among next hops when a routing device is performing unequal-cost load balancing. This information is available when you enable Border Gateway Protocol (BGP) multipath load balancing. Label-switched-path lsp-path-name Name of the label-switched path (LSP) used to reach the next hop. Label operation MPLS label and operation occurring at this routing device. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label). Interface (Local only) Local interface name. Protocol next hop Network layer address of the remote routing device that advertised the prefix. This address is used to derive a forwarding next hop. Indirect next hop Index designation used to specify the mapping between protocol next hops, tags, kernel export policy, and the forwarding next hops. State State of the route (a route can be in more than one state). See Table 243 on page 1932. Local AS AS number of the local routing device. Age How long the route has been known. Metricn Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined by a preference value. MED-plus-IGP Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added. Task Name of the protocol that has added the route. 1929 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 241: show route detail Output Fields (continued) Field Name Field Description Announcement bits List of protocols that announce this route. n-Resolve inet indicates that the route is used for route resolution for next hops found in the routing table. n is an index used by Dell Support only (see “Requesting Technical Support” on page lxxi). AS path AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. When AS path numbers are included in the route, the format is as follows: • [ ]—Brackets enclose the number that precedes the AS path. This number represents the number of ASs present in the AS path, when calculated as defined in RFC 4271. This value is used in the AS-path merge process, as defined in RFC 4893. • [ ]—If more than one AS number is configured on the routing device, or if AS path prepending is configured, brackets enclose the local AS number associated with the AS path. • { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order. • ( )—Parentheses enclose a confederation. • ( [ ] )—Parentheses and brackets enclose a confederation set. VC Label MPLS label assigned to the Layer 2 circuit virtual connection. MTU Maximum transmission unit (MTU) of the Layer 2 circuit. VLAN ID VLAN identifier of the Layer 2 circuit. Prefixes bound to route Forwarding Equivalent Class (FEC) bound to this route. Applicable only to routes installed by LDP. Communities Community path attribute for the route. See Table 244 on page 1934 for all possible values for this field. Layer2-info: encaps Layer 2 encapsulation (for example, VPLS). control flags Control flags: none or Site Down. mtu Maximum transmission unit (MTU) information. Label-Base, range First label in a block of labels and label block size. A remote PE routing device uses this first label when sending traffic toward the advertising PE routing device. status vector Layer 2 VPN and VPLS network layer reachability information (NLRI). Localpref Local preference value included in the route. Router ID BGP router ID as advertised by the neighbor in the open message. 1930 Chapter 74: Operational Commands for Layer 3 Protocols Table 241: show route detail Output Fields (continued) Field Name Field Description Primary Routing Table In a routing table group, the name of the primary routing table in which the route resides. Secondary Tables In a routing table group, the name of one or more secondary tables in which the route resides. Table 242 on page 1931 describes all possible values for the Next-hop Types output field. Table 242: Next-Hop Types Output Field Values Next-Hop Type Description broadcast (bcast) Broadcast next hop. deny Deny next hop. hold Next hop is waiting to be resolved into a unicast or multicast type. indexed (idxd) Indexed next hop. indirect (indr) Indirect next hop. local (locl) Local address on an interface. routed multicast (mcrt) Regular multicast next hop. multicast (mcst) Wire multicast next hop (limited to the LAN). multicast discard (mdsc) Multicast discard. multicast group (mgrp) Multicast group member. receive (recv) Receive. reject (rjct) Discard. An ICMP unreachable message was sent. resolve (rslv) Resolving next hop. unicast (ucst) Unicast. unilist (ulst) List of unicast next hops. A packet sent to this next hop goes to any next hop in the list. 1931 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 243 on page 1932 describes all possible values for the State output field. A route can be in more than one state (for example, ). Table 243: State Output Field Values 1932 Value Description Accounting Route needs accounting. Active Route is active. Always Compare MED Path with a lower multiple exit discriminator (MED) is available. AS path Shorter AS path is available. Clone Route is a clone. Cisco Non-deterministic MED selection Cisco nondeterministic MED is enabled and a path with a lower MED is available. Cluster list length Length of cluster list sent by the route reflector. Delete Route has been deleted. Ex Exterior route. Ext BGP route received from an external BGP neighbor. FlashAll Forces all protocols to be notified of a change to any route, active or inactive, for a prefix. When not set, protocols are informed of a prefix only when the active route changes. Hidden Route not used because of routing policy. IfCheck Route needs forwarding RPF check. IGP metric Path through next hop with lower IGP metric is available. Local Preference Path with a higher local preference value is available. Inactive reason Flags for this route, which was not selected as best for a particular destination. Initial Route being added. Int Interior route. Int Ext BGP route received from an internal BGP peer or a BGP confederation peer. Chapter 74: Operational Commands for Layer 3 Protocols Table 243: State Output Field Values (continued) Value Description Interior > Exterior > Exterior via Interior Direct, static, IGP, or EBGP path is available. Martian Route is a martian (ignored because it is obviously invalid). MartianOK Route exempt from martian filtering. Next hop address Path with lower metric next hop is available. No difference Path from neighbor with lower IP address is available. NoReadvrt Route not to be advertised. NotBest Route not chosen because it does not have the lowest MED. Not Best in its group Incoming BGP AS is not the best of a group (only one AS can be the best). NotInstall Route not to be installed in the forwarding table. Number of gateways Path with greater number of next hops is available. Origin Path with lower origin code is available. Pending Route pending because of a hold-down configured on another route. Release Route scheduled for release. RIB preference Route from a higher-numbered routing table is available. Route Distinguisher 64-bit prefix added to IP subnets to make them unique. Route Metric or MED comparison Route with a lower metric or MED is available. Route Preference Route with lower preference value is available Router ID Path through neighbor with lower ID is available. Secondary Route not a primary route. Unusable path Path is not usable because of one of the following conditions: Update source • The route is damped. • The route is rejected by an import policy. • The route is unresolved. Last tiebreaker is the lowest IP address value. 1933 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 244 on page 1934 describes the possible values for the Communities output field. Table 244: Communities Output Field Values Value Description area-number 4 bytes, encoding a 32-bit area number. For AS-external routes, the value is 0. A nonzero value identifies the route as internal to the OSPF domain, and as within the identified area. Area numbers are relative to a particular OSPF domain. bandwidth: local AS number:link-bandwidth-number Link-bandwidth community value used for unequal-cost load balancing. When BGP has several candidate paths available for multipath purposes, it does not perform unequal-cost load balancing according to the link-bandwidth community unless all candidate paths have this attribute. domain-id Unique configurable number that identifies the OSPF domain. domain-id-vendor Unique configurable number that identifies the OSPF domain. link-bandwidth-number Link-bandwidth number: from 0 through 4,294,967,295 (bytes per second). local AS number Local AS number: from 1 through 65,535. options 1 byte. Currently this is only used if the route type is 5 or 7. Setting the least significant bit in the field indicates that the route carries a type 2 metric. origin (Used with VPNs) Identifies where the route came from. ospf-route-type 1 byte, encoded as 1 or 2 for intra-area routes (depending on whether the route came from a type 1 or a type 2 LSA); 3 for summary routes; 5 for external routes (area number must be 0); 7 for NSSA routes; or 129 for sham link endpoint addresses. rte-type Displays the area number, OSPF route type, and option of the route. This is configured using the BGP extended community attribute 0x0306. The format is area-number:ospf-route-type:options. route-type-vendor Displays the area number, OSPF route type, and option of the route. This is configured using the BGP extended community attribute 0x8000. The format is area-number:ospf-route-type:options. target Defines which VPN the route participates in; target has the format 32-bit IP address:16-bit number. For example, 10.19.0.0:100. unknown IANA Incoming IANA codes with a value between 0x1 and 0x7fff. This code of the BGP extended community attribute is accepted, but it is not recognized. unknown OSPF vendor community Incoming IANA codes with a value above 0x8000. This code of the BGP extended community attribute is accepted, but it is not recognized. 1934 Chapter 74: Operational Commands for Layer 3 Protocols show route detail user@host> show route detail inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 29 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 1:31:43 Task: RT Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I 10.31.1.0/30 (2 entries, 1 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 2 Next hop: via so-0/3/0.0, selected State: Local AS: 69 Age: 1:30:17 Task: IF Announcement bits (1): 3-Resolve tree 2 AS path: I OSPF Preference: 10 Next-hop reference count: 1 Next hop: via so-0/3/0.0, selected State: Inactive reason: Route Preference Local AS: 69 Age: 1:30:17 Metric: 1 Area: 0.0.0.0 Task: OSPF AS path: I 10.31.1.1/32 (1 entry, 1 announced) *Local Preference: 0 Next hop type: Local Next-hop reference count: 7 Interface: so-0/3/0.0 State: Local AS: 69 Age: 1:30:20 Task: IF Announcement bits (1): 3-Resolve tree 2 AS path: I ... 1935 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 10.31.2.0/30 (1 entry, 1 announced) *OSPF Preference: 10 Next-hop reference count: 9 Next hop: via so-0/3/0.0 Next hop: 10.31.1.6 via ge-3/1/0.0, selected State: Local AS: 69 Age: 1:29:56 Metric: 2 Area: 0.0.0.0 Task: OSPF Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I ... 224.0.0.2/32 (1 entry, 1 announced) *PIM Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:31:45 Task: PIM Recv Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I ... 224.0.0.22/32 (1 entry, 1 announced) *IGMP Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:31:43 Task: IGMP Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 10.255.70.103/32 (1 entry, 1 announced) State: *RSVP Preference: 7 Next-hop reference count: 6 Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected Label-switched-path green-r1-r3 Label operation: Push 100096 State: Local AS: 69 Age: 1:25:49 Metric: 2 Task: RSVP Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2 AS path: I 10.255.71.238/32 (1 entry, 1 announced) State: *RSVP Preference: 7 Next-hop reference count: 6 Next hop: via so-0/3/0.0 weight 0x1, selected Label-switched-path green-r1-r2 State: Local AS: 69 1936 Chapter 74: Operational Commands for Layer 3 Protocols Age: 1:25:49 Metric: 1 Task: RSVP Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2 AS path: I private__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Local AS: 69 Age: 1:31:44 Task: IF AS path: I mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) 0 (1 entry, 1 announced) *MPLS Preference: 0 Next hop type: Receive Next-hop reference count: 6 State: Local AS: 69 Age: 1:31:45 Metric: 1 Task: MPLS Announcement bits (1): 0-KRT AS path: I ... 800010 (1 entry, 1 announced) *VPLS Preference: 7 Next-hop reference count: 2 Next hop: via vt-3/2/0.32769, selected Label operation: Pop State: Age: 1:29:30 Task: Common L2 VC Announcement bits (1): 0-KRT AS path: I vt-3/2/0.32769 (1 entry, 1 announced) *VPLS Preference: 7 Next-hop reference count: 2 Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected Label-switched-path green-r1-r3 Label operation: Push 800012, Push 100096(top) Protocol next hop: 10.255.70.103 Push 800012 Indirect next hop: 87272e4 1048574 State: Age: 1:29:30 Metric2: 2 Task: Common L2 VC Announcement bits (2): 0-KRT 1-Common L2 VC AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 1937 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) abcd::10:255:71:52/128 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Local AS: 69 Age: 1:31:44 Task: IF AS path: I fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Local AS: 69 Age: 1:31:44 Task: IF AS path: I ff02::2/128 (1 entry, 1 announced) *PIM Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:31:45 Task: PIM Recv6 Announcement bits (1): 0-KRT AS path: I ff02::d/128 (1 entry, 1 announced) *PIM Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:31:45 Task: PIM Recv6 Announcement bits (1): 0-KRT AS path: I ff02::16/128 (1 entry, 1 announced) *MLD Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:31:43 Task: MLD Announcement bits (1): 0-KRT AS path: I private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 1938 Chapter 74: Operational Commands for Layer 3 Protocols Next hop: via lo0.16385, selected State: Age: 1:31:44 Task: IF AS path: I green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) 10.255.70.103:1:3:1/96 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.70.103:1 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 1:25:49 Metric2: 1 Task: BGP_69.10.255.70.103+179 Announcement bits (1): 0-green-l2vpn AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8 Localpref: 100 Router ID: 10.255.70.103 Primary Routing Table bgp.l2vpn.0 10.255.71.52:1:1:1/96 (1 entry, 1 announced) *L2VPN Preference: 170/-1 Next-hop reference count: 5 Protocol next hop: 10.255.71.52 Indirect next hop: 0 State: Age: 1:31:40 Metric2: 1 Task: green-l2vpn Announcement bits (1): 1-BGP.0.0.0.0+179 AS path: I Communities: Layer2-info: encaps:VPLS, control flags:Site-Down, mtu: 0 Label-base: 800016, range: 8, status-vector: 0x9F 10.255.71.52:1:5:1/96 (1 entry, 1 announced) *L2VPN Preference: 170/-101 Next-hop reference count: 5 Protocol next hop: 10.255.71.52 Indirect next hop: 0 State: Age: 1:31:40 Metric2: 1 Task: green-l2vpn Announcement bits (1): 1-BGP.0.0.0.0+179 AS path: I Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8, status-vector: 0x9F ... l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced) *L2CKT Preference: 7 Next hop: via so-1/1/2.0 weight 1, selected 1939 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Label-switched-path my-lsp Label operation: Push 100000[0] Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296 State: Local AS: 99 Age: 10:21 Task: l2 circuit Announcement bits (1): 0-LDP AS path: I VC Label 100000, MTU 1500, VLAN ID 512 1940 Chapter 74: Operational Commands for Layer 3 Protocols show route exact Syntax Syntax (J-EX Series Switch) Release Information show route exact destination-prefix show route exact destination-prefix Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display only the routes that exactly match the specified address or range of addresses. Options brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. destination-prefix—Address or range of addresses. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route exact view show route exact on page 1941 show route exact detail on page 1941 show route exact extensive on page 1943 show route exact terse on page 1943 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route exact 207.17.136.0/24 inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 207.17.136.0/24 *[Static/5] 2d 03:30:22 > to 192.168.71.254 via fxp0.0 show route exact detail user@host> show route exact 207.17.136.0/24 detail inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete 207.17.136.0/24 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 29 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2d 3:30:26 Task: RT 1941 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I 1942 Chapter 74: Operational Commands for Layer 3 Protocols show route exact extensive show route exact terse user@host> show route exact 207.17.136.0/24 extensive inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden) 207.17.136.0/24 (1 entry, 1 announced) TSI: KRT in-kernel 207.17.136.0/24 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 29 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 1:25:18 Task: RT Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I user@host> show route exact 207.17.136.0/24 terse inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A Destination P Prf Metric 1 Metric 2 Next hop AS path * 207.17.136.0/24 S 5 >192.168.71.254 1943 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route export Syntax show route export | routing-table-name> Syntax (J-EX Series Switch) show route export | routing-table-name> Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display policy-based route export information. Policy-based export simplifies the process of exchanging route information between routing instances. none—(Same as brief.) Display standard information about policy-based export for all instances and routing tables on all systems. brief | detail—(Optional) Display the specified level of output. instance —(Optional) Display a particular routing instance for which policy-based export is currently enabled. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. routing-table-name—(Optional) Display information about a particular routing table (for example, inet.0) for which policy-based export is currently enabled. (For information about the different types of routing tables, see the Junos OS Routing Protocols Configuration Guide.) Required Privilege Level List of Sample Output Output Fields view show route export on page 1945 show route export detail on page 1945 show route export instance detail on page 1945 Table 245 on page 1944 lists the output fields for the show route export command. Output fields are listed in the approximate order in which they appear. Table 245: show route export Output Fields Field Name Field Description Level of Output Table or table-name Name of the routing tables that either import or export routes. All levels Routes Number of routes exported from this table into other tables. If a particular route is exported to different tables, the counter will only increment by one. brief none Export Whether the table is currently exporting routes to other tables: Y or N (Yes or No). brief none 1944 Chapter 74: Operational Commands for Layer 3 Protocols Table 245: show route export Output Fields (continued) Field Name Field Description Level of Output Import Tables currently importing routes from the originator table. (Not displayed for tables that are not exporting any routes.) detail Flags (instance keyword only) Flags for this feature on this instance: detail • config auto-policy—The policy was deduced from the configured IGP export policies. Options • cleanup—Configuration information for this instance is no longer valid. • config—The instance was explicitly configured. (instance keyword only) Configured option displays the type of routing tables the feature handles: • unicast—Indicates instance.inet.0. • multicast—Indicates instance.inet.2. • unicast multicast—Indicates instance.inet.0 and instance.inet.2. detail Import policy (instance keyword only) Policy that route export uses to construct the import-export matrix. Not displayed if the instance type is vrf. detail Instance (instance keyword only) Name of the routing instance. detail Type (instance keyword only) Type of routing instance: forwarding, non-forwarding, or vrf. detail show route export show route export detail show route export instance detail user@host> show route export Table inet.0 black.inet.0 red.inet.0 user@host> show route export detail inet.0 black.inet.0 Import: [ inet.0 ] red.inet.0 Import: [ inet.0 ] Export N Y Y Routes 0 3 4 Routes: Routes: 0 3 Routes: 4 user@host> show route export instance detail Instance: master Type: forwarding Flags: Options: Import policy: [ (ospf-master-from-red || isis-master-from-black) ] Instance: black Type: non-forwarding Instance: red Type: non-forwarding 1945 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route extensive Syntax show route extensive Syntax (J-EX Series Switch) show route extensive Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display extensive information about the active entries in the routing tables. Options none—Display all active entries in the routing table. destination-prefix—(Optional) Display active entries for the specified address or range of addresses. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level view List of Sample Output show route extensive on page 1951 show route extensive (Access Route) on page 1957 show route extensive (Route Reflector) on page 1957 Output Fields Table 246 on page 1946 describes the output fields for the show route extensive command. Output fields are listed in the approximate order in which they appear. Table 246: show route extensive Output Fields Field Name Field Description routing-table-name Name of the routing table (for example, inet.0). number destinations Number of destinations for which there are routes in the routing table. number routes Number of routes in the routing table and total number of routes in the following states: 1946 • active (routes that are active). • holddown (routes that are in the pending state before being declared inactive). • hidden (routes that are not used because of a routing policy). Chapter 74: Operational Commands for Layer 3 Protocols Table 246: show route extensive Output Fields (continued) Field Name Field Description route-destination (entry, announced) Route destination (for example:10.0.0.1/24). The entry value is the number of route for this destination, and the announced value is the number of routes being announced for this destination. Sometimes the route destination is presented in another format, such as: • MPLS-label (for example, 80001 ). • interface-name (for example, ge-1/0/2 ). • neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example, 10.1.1.195:NoCtrlWord:1:1:Local/96). • neighbor-address—Address of the neighbor. • control-word-status—Whether the use of the control word has been negotiated for this virtual circuit: NoCtrlWord or CtrlWord. • encapsulation type—Type of encapsulation, represented by a number: (1) Frame Relay DLCI, (2) ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet, (6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport. • vc-id—Virtual circuit identifier. • source—Source of the advertisement: Local or Remote. TSI Protocol header information. label stacking (Next-to-the-last-hop routing device for MPLS only) Depth of the Multiprotocol Label Switching (MPLS) label stack, where the label-popping operation is needed to remove one or more labels from the top of the stack. A pair of routes is displayed, because the pop operation is performed only when the stack depth is two or more labels. • S=0 route indicates that a packet with an incoming label stack depth of two or more exits this router with one fewer label (the label-popping operation is performed). • [protocol, preference] If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the label-popping operation is not performed). Protocol from which the route was learned and the preference value for the route. • +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table. • - —A hyphen indicates the last active route. • *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route. In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value. Level (IS-IS only). In IS-IS, a single autonomous system (AS) can be divided into smaller groups called areas. Routing between areas is organized hierarchically, allowing a domain to be administratively divided into smaller areas. This organization is accomplished by configuring Level 1 and Level 2 intermediate systems. Level 1 systems route within an area; when the destination is outside an area, they route toward a Level 2 system. Level 2 intermediate systems route between areas and toward other ASs. 1947 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 246: show route extensive Output Fields (continued) Field Name Field Description Route Distinguisher IP subnet augmented with a 64-bit prefix. Next-hop type Type of next hop. For a description of possible values for this field, see the Output Field table in the show route detail command. Next-hop reference count Number of references made to the next hop. Source IP address of the route source. Next hop Network layer address of the directly reachable neighboring system. via Interface used to reach the next hop. If there is more than one interface available to the next hop, the name of the interface that is actually used is followed by the word Selected. This field can also contain the following information: • Weight—Value used to distinguish primary, secondary, and fast reroute backup routes. Weight information is available when Multiprotocol Label Switching (MPLS) label-switched path (LSP) link protection, node-link protection, or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight value is preferred. Among routes with the same weight value, load balancing is possible. • Balance—Balance coefficient indicating how traffic of unequal cost is distributed among next hops when a routing device is performing unequal-cost load balancing. This information is available when you enable Border Gateway Protocol (BGP) multipath load balancing. Label-switched-path lsp-path-name Name of the label-switched path (LSP) used to reach the next hop. Label operation MPLS label and operation occurring at this routing device. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label). Offset Whether the metric has been increased or decreased by an offset value. Interface (Local only) Local interface name. Protocol next hop Network layer address of the remote routing device that advertised the prefix. This address is used to recursively derive a forwarding next hop. label-operation MPLS label and operation occurring at this routing device. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label). Indirect next hops When present, a list of nodes that are used to resolve the path to the next-hop destination, in the order that they are resolved. State State of the route (a route can be in more than one state). See the Output Field table in the show route detail command. 1948 Chapter 74: Operational Commands for Layer 3 Protocols Table 246: show route extensive Output Fields (continued) Field Name Field Description Inactive reason If the route is inactive, the reason for its current state is indicated. Typical reasons include: • Active preferred—Currently active route was selected over this route. • Always compare MED—Path with a lower multiple exit discriminator (MED) is available. • AS path—Shorter AS path is available. • Cisco Non-deterministic MED selection—Cisco nondeterministic MED is enabled and a path with a lower MED is available. • Cluster list length—Path with a shorter cluster list length is available. • Forwarding use only—Path is only available for forwarding purposes. • IGP metric—Path through the next hop with a lower IGP metric is available. • IGP metric type—Path with a lower OSPF link-state advertisement type is available. • Interior > Exterior > Exterior via Interior—Direct, static, IGP, or EBGP path is available. • Local preference—Path with a higher local preference value is available. • Next hop address—Path with a lower metric next hop is available. • No difference—Path from a neighbor with a lower IP address is available. • Not Best in its group—Occurs when multiple peers of the same external AS advertise the same prefix and are grouped together in the selection process. When this reason is displayed, an additional reason is provided (typically one of the other reasons listed). • Number of gateways—Path with a higher number of next hops is available. • Origin—Path with a lower origin code is available. • OSPF version—Path does not support the indicated OSPF version. • RIB preference—Route from a higher-numbered routing table is available. • Route destinguisher—64-bit prefix added to IP subnets to make them unique. • Route metric or MED comparison—Route with a lower metric or MED is available. • Route preference—Route with a lower preference value is available. • Router ID—Path through a neighbor with a lower ID is available. • Unusable path—Path is not usable because of one of the following conditions: the route is damped, the route is rejected by an import policy, or the route is unresolved. • Update source—Last tiebreaker is the lowest IP address value. Local AS Autonomous system (AS) number of the local routing device. Age How long the route has been known. Metric Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined by a preference value. MED-plus-IGP Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added. Task Name of the protocol that has added the route. Announcement bits List of protocols that announce this route. n-Resolve inet indicates that the route is used for route resolution for next hops found in the routing table. n is an index used by Dell Support only (see “Requesting Technical Support” on page lxxi). 1949 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 246: show route extensive Output Fields (continued) Field Name Field Description AS path AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. When AS path numbers are included in the route, the format is as follows: • [ ]—Brackets enclose the local AS number associated with the AS path if more than one AS number is configured on the routing device, or if AS path prepending is configured. • { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order. • ( )—Parentheses enclose a confederation. • ( [ ] )—Parentheses and brackets enclose a confederation set. AS path: I (For route reflected output only) Originator ID attribute set by the route reflector. VC Label MPLS label assigned to the Layer 2 circuit virtual connection. MTU Maximum transmission unit (MTU) of the Layer 2 circuit. VLAN ID VLAN identifier of the Layer 2 circuit. Cluster list (For route reflected output only) Cluster ID sent by the route reflector. Originator ID (For route reflected output only) Address of router that originally sent the route to the route reflector. Prefixes bound to route Forwarding Equivalent Class (FEC) bound to this route. Applicable only to routes installed by LDP. Communities Community path attribute for the route. See the Output Field table in the show route detail command for all possible values for this field. Layer2-info: encaps Layer 2 encapsulation (for example, VPLS). control flags Control flags: none or Site Down. mtu Maximum transmission unit (MTU) information. Label-Base, range First label in a block of labels and label block size. A remote PE routing device uses this first label when sending traffic toward the advertising PE routing device. status vector Layer 2 VPN and VPLS network layer reachability information (NLRI). Localpref Local preference value included in the route. Router ID BGP router ID as advertised by the neighbor in the open message. 1950 Chapter 74: Operational Commands for Layer 3 Protocols Table 246: show route extensive Output Fields (continued) Field Name Field Description Primary Routing Table In a routing table group, the name of the primary routing table in which the route resides. Secondary Tables In a routing table group, the name of one or more secondary tables in which the route resides. Originating RIB Name of the routing table whose active route was used to determine the forwarding next-hop entry in the resolution database. For example, in the case of inet.0 resolving through inet.0 and inet.3, this field indicates which routing table, inet.0 or inet.3, provided the best path for a particular prefix. Node path count Number of nodes in the path. Forwarding nexthops Number of forwarding next hops. The forwarding next hop is the network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it. show route extensive user@host> show route extensive inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.10.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 29 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 1:34:06 Task: RT Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I 10.31.1.0/30 (2 entries, 1 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 2 Next hop: via so-0/3/0.0, selected State: Local AS: 69 Age: 1:32:40 Task: IF Announcement bits (1): 3-Resolve tree 2 AS path: I 1951 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS OSPF Preference: 10 Next-hop reference count: 1 Next hop: via so-0/3/0.0, selected State: Inactive reason: Route Preference Local AS: 69 Age: 1:32:40 Metric: 1 Area: 0.0.0.0 Task: OSPF AS path: I 10.31.1.1/32 (1 entry, 1 announced) *Local Preference: 0 Next hop type: Local Next-hop reference count: 7 Interface: so-0/3/0.0 State: Local AS: 69 Age: 1:32:43 Task: IF Announcement bits (1): 3-Resolve tree 2 AS path: I ... 10.31.2.0/30 (1 entry, 1 announced) TSI: KRT in-kernel 10.31.2.0/30 -> {10.31.1.6} *OSPF Preference: 10 Next-hop reference count: 9 Next hop: via so-0/3/0.0 Next hop: 10.31.1.6 via ge-3/1/0.0, selected State: Local AS: 69 Age: 1:32:19 Metric: 2 Area: 0.0.0.0 Task: OSPF Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I ... 224.0.0.2/32 (1 entry, 1 announced) TSI: KRT in-kernel 224.0.0.2/32 -> {} *PIM Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:34:08 Task: PIM Recv Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I ... 224.0.0.22/32 (1 entry, 1 announced) TSI: KRT in-kernel 224.0.0.22/32 -> {} *IGMP Preference: 0 Next-hop reference count: 18 1952 Chapter 74: Operational Commands for Layer 3 Protocols State: Local AS: 69 Age: 1:34:06 Task: IGMP Announcement bits (2): 0-KRT 3-Resolve tree 2 AS path: I inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 10.255.70.103/32 (1 entry, 1 announced) State: *RSVP Preference: 7 Next-hop reference count: 6 Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected Label-switched-path green-r1-r3 Label operation: Push 100096 State: Local AS: 69 Age: 1:28:12 Metric: 2 Task: RSVP Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2 AS path: I 10.255.71.238/32 (1 entry, 1 announced) State: *RSVP Preference: 7 Next-hop reference count: 6 Next hop: via so-0/3/0.0 weight 0x1, selected Label-switched-path green-r1-r2 State: Local AS: 69 Age: 1:28:12 Metric: 1 Task: RSVP Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2 AS path: I private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) ... iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Local AS: 69 Age: 1:34:07 Task: IF AS path: I mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) 0 (1 entry, 1 announced) TSI: KRT in-kernel 0 /36 -> {} *MPLS Preference: 0 Next hop type: Receive Next-hop reference count: 6 1953 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS State: Local AS: 69 Age: 1:34:08 Metric: 1 Task: MPLS Announcement bits (1): 0-KRT AS path: I ... 800010 (1 entry, 1 announced) TSI: KRT in-kernel 800010 /36 -> {vt-3/2/0.32769} *VPLS Preference: 7 Next-hop reference count: 2 Next hop: via vt-3/2/0.32769, selected Label operation: Pop State: Age: 1:31:53 Task: Common L2 VC Announcement bits (1): 0-KRT AS path: I vt-3/2/0.32769 (1 entry, 1 announced) TSI: KRT in-kernel vt-3/2/0.32769.0 /16 -> {indirect(1048574)} *VPLS Preference: 7 Next-hop reference count: 2 Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected Label-switched-path green-r1-r3 Label operation: Push 800012, Push 100096(top) Protocol next hop: 10.255.70.103 Push 800012 Indirect next hop: 87272e4 1048574 State: Age: 1:31:53 Metric2: 2 Task: Common L2 VC Announcement bits (2): 0-KRT 1-Common L2 VC AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Indirect next hops: 1 Protocol next hop: 10.255.70.103 Metric: 2 Push 800012 Indirect next hop: 87272e4 1048574 Indirect path forwarding next hops: 1 Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1 10.255.70.103/32 Originating RIB: inet.3 Metric: 2 Node path count: 1 Forwarding nexthops: 1 Nexthop: 10.31.1.6 via ge-3/1/0.0 inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) abcd::10:255:71:52/128 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Local AS: 69 1954 Chapter 74: Operational Commands for Layer 3 Protocols Age: 1:34:07 Task: IF AS path: I fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Local AS: 69 Age: 1:34:07 Task: IF AS path: I ff02::2/128 (1 entry, 1 announced) TSI: KRT in-kernel ff02::2/128 -> {} *PIM Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:34:08 Task: PIM Recv6 Announcement bits (1): 0-KRT AS path: I ff02::d/128 (1 entry, 1 announced) TSI: KRT in-kernel ff02::d/128 -> {} *PIM Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:34:08 Task: PIM Recv6 Announcement bits (1): 0-KRT AS path: I ff02::16/128 (1 entry, 1 announced) TSI: KRT in-kernel ff02::16/128 -> {} *MLD Preference: 0 Next-hop reference count: 18 State: Local AS: 69 Age: 1:34:06 Task: MLD Announcement bits (1): 0-KRT AS path: I private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.16385, selected State: Age: 1:34:07 Task: IF 1955 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS AS path: I green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) 10.255.70.103:1:3:1/96 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.70.103:1 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 1:28:12 Metric2: 1 Task: BGP_69.10.255.70.103+179 Announcement bits (1): 0-green-l2vpn AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8 Localpref: 100 Router ID: 10.255.70.103 Primary Routing Table bgp.l2vpn.0 10.255.71.52:1:1:1/96 (1 entry, 1 announced) TSI: Page 0 idx 0 Type 1 val 8699540 *L2VPN Preference: 170/-1 Next-hop reference count: 5 Protocol next hop: 10.255.71.52 Indirect next hop: 0 State: Age: 1:34:03 Metric2: 1 Task: green-l2vpn Announcement bits (1): 1-BGP.0.0.0.0+179 AS path: I Communities: Layer2-info: encaps:VPLS, control flags:Site-Down, mtu: 0 Label-base: 800016, range: 8, status-vector: 0x9F 10.255.71.52:1:5:1/96 (1 entry, 1 announced) TSI: Page 0 idx 0 Type 1 val 8699528 *L2VPN Preference: 170/-101 Next-hop reference count: 5 Protocol next hop: 10.255.71.52 Indirect next hop: 0 State: Age: 1:34:03 Metric2: 1 Task: green-l2vpn Announcement bits (1): 1-BGP.0.0.0.0+179 AS path: I Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8, status-vector: 0x9F ... l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) TSI: 1956 Chapter 74: Operational Commands for Layer 3 Protocols 10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced) *L2CKT Preference: 7 Next hop: via so-1/1/2.0 weight 1, selected Label-switched-path my-lsp Label operation: Push 100000[0] Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296 State: Local AS: 99 Age: 10:21 Task: l2 circuit Announcement bits (1): 0-LDP AS path: I VC Label 100000, MTU 1500, VLAN ID 512 show route extensive (Access Route) user@host> show route 13.160.0.102 extensive inet.0: 39256 destinations, 39258 routes (39255 active, 0 holddown, 1 hidden) 13.160.0.102/32 (1 entry, 1 announced) TSI: KRT in-kernel 13.160.0.102/32 -> {13.160.0.2} OSPF area : 0.0.0.0, LSA ID : 13.160.0.102, LSA type : Extern *Access Preference: 13 Next-hop reference count: 78472 Next hop: 13.160.0.2 via fe-0/0/0.0, selected State: Age: 12 Task: RPD Unix Domain Server./var/run/rpd_serv.local Announcement bits (2): 0-KRT 1-OSPFv2 AS path: I show route extensive (Route Reflector) user@host> show route extensive 1.0.0.0/8 (1 entry, 1 announced) TSI: KRT in-kernel 1.0.0.0/8 -> {indirect(40)} *BGP Preference: 170/-101 Source: 192.168.4.214 Protocol next hop: 207.17.136.192 Indirect next hop: 84ac908 40 State: Local AS: 10458 Peer AS: 10458 Age: 3:09 Metric: 0 Metric2: 0 Task: BGP_10458.192.168.4.214+1033 Announcement bits (2): 0-KRT 4-Resolve inet.0 AS path: 3944 7777 I Cluster list: 1.1.1.1 Originator ID: 10.255.245.88 Communities: 7777:7777 Localpref: 100 Router ID: 4.4.4.4 Indirect next hops: 1 Protocol next hop: 207.17.136.192 Metric: 0 Indirect next hop: 84ac908 40 Indirect path forwarding next hops: 0 Next hop type: Discard 1957 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route flow validation Syntax Syntax (J-EX Series Switch) Release Information Description Options show route flow validation
show route flow validation
Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display flow route information. none—Display flow route information. brief | detail—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. ip-prefix—(Optional) IP address for the flow route. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. table table-name—(Optional) Name of the flow route table. Required Privilege Level List of Sample Output Output Fields view show route flow validation on page 1959 Table 247 on page 1958 lists the output fields for the show route flow validation command. Output fields are listed in the approximate order in which they appear. Table 247: show route flow validation Output Fields Field Name Field Description Level of Output routing-table-name Name of the routing table (for example, inet.0). All levels prefix Route address. All levels Active unicast route Active route in the routing table. All levels Dependent flow destinations Number of flows for which there are routes in the routing table. All levels Origin Source of the route flow. All levels 1958 Chapter 74: Operational Commands for Layer 3 Protocols Table 247: show route flow validation Output Fields (continued) Field Name Field Description Level of Output Neighbor AS Autonomous system identifier of the neighbor. All levels Flow destination Number of entries and number of destinations that match the route flow. All levels Unicast best match Destination that is the best match for the route flow. All levels Flags Information about the route flow. All levels show route flow validation user@host> show route flow validation inet.0: 10.0.5.0/24Active unicast route Dependent flow destinations: 1 Origin: 192.168.224.218, Neighbor AS: 65001 Flow destination (3 entries, 1 match origin) Unicast best match: 10.0.5.0/24 Flags: SubtreeApex Consistent 1959 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route inactive-path Syntax Syntax (J-EX Series Switch) Release Information Description Options show route inactive-path show route inactive-path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display routes for destinations that have no active route. An inactive route is a route that was not selected as the best path. none—Display all inactive routes. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output view show route inactive-path on page 1960 show route inactive-path detail on page 1961 show route inactive-path extensive on page 1962 show route inactive-path terse on page 1962 Output Fields For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. show route inactive-path user@host> show route inactive-path inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.12.100.12/30 [OSPF/10] 03:57:28, metric 1 > via so-0/3/0.0 private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.0/8 [Direct/0] 04:39:56 > via fxp1.0 red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.12.80.0/30 1960 [BGP/170] 04:38:17, localpref 100 Chapter 74: Operational Commands for Layer 3 Protocols AS path: 100 I > to 10.12.80.1 via ge-6/3/2.0 iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete bgp.l3vpn.0: 3 destinations, 3 routes (0 active, 0 holddown, 3 hidden) Restart Complete inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) show route inactive-path detail user@host> show route inactive-path detail inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden) Restart Complete 10.12.100.12/30 (2 entries, 1 announced) OSPF Preference: 10 Next-hop reference count: 1 Next hop: via so-0/3/0.0, selected State: Inactive reason: Route Preference Local AS: 1 Age: 3:58:24 Metric: 1 Area: 0.0.0.0 Task: OSPF AS path: I private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) 10.0.0.0/8 (2 entries, 0 announced) Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via fxp1.0, selected State: Inactive reason: No difference Age: 4:40:52 Task: IF AS path: I red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden) Restart Complete 10.12.80.0/30 (2 entries, 1 announced) BGP Preference: 170/-101 Next-hop reference count: 6 Source: 10.12.80.1 Next hop: 10.12.80.1 via ge-6/3/2.0, selected State: Inactive reason: Route Preference Peer AS: 100 Age: 4:39:13 Task: BGP_100.10.12.80.1+179 AS path: 100 I 1961 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Localpref: 100 Router ID: 10.0.0.0 show route inactive-path extensive show route inactive-path terse The output for the show route inactive-path extensive command is identical to that of the show route inactive-path detail command. For sample output, see show route inactive-path detail on page 1961. user@host> show route inactive-path terse inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both A Destination 10.12.100.12/30 P Prf O 10 Metric 1 1 Metric 2 Next hop >so-0/3/0.0 AS path private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A Destination 10.0.0.0/8 P Prf D 0 Metric 1 Metric 2 Next hop >fxp1.0 AS path red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden) Restart Complete + = Active Route, - = Last Active, * = Both A Destination 10.12.80.0/30 P Prf B 170 Metric 1 100 Metric 2 Next hop >10.12.80.1 AS path 100 I iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete bgp.l3vpn.0: 3 destinations, 3 routes (0 active, 0 holddown, 3 hidden) Restart Complete inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 1962 Chapter 74: Operational Commands for Layer 3 Protocols show route inactive-prefix Syntax Syntax (J-EX Series Switch) Release Information Description Options show route inactive-prefix show route inactive-prefix Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display inactive route destinations in each routing table. none—Display all inactive route destination. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route inactive-prefix view show route inactive-prefix on page 1963 show route inactive-prefix detail on page 1963 show route inactive-prefix extensive on page 1964 show route inactive-prefix terse on page 1964 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route inactive-prefix inet.0: 14 destinations, 14 routes (13 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 127.0.0.1/32 show route inactive-prefix detail [Direct/0] 00:04:54 > via lo0.0 user@host> show route inactive-prefix detail inet.0: 14 destinations, 14 routes (13 active, 0 holddown, 1 hidden) 127.0.0.1/32 (1 entry, 0 announced) Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Age: 4:51 Task: IF 1963 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS AS path: I00:04:54 > via lo0.0 show route inactive-prefix extensive show route inactive-prefix terse The output for the show route inactive-prefix extensive command is identical to that of the show route inactive-path detail command. For sample output, see show route inactive-prefix detail on page 1963. user@host> show route inactive-prefix terse inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A Destination 127.0.0.1/32 1964 P Prf D 0 Metric 1 Metric 2 Next hop >lo0.0 AS path Chapter 74: Operational Commands for Layer 3 Protocols show route instance Syntax Syntax (J-EX Series Switch) Release Information Description Options show route instance show route instance Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display routing instance information. none—(Same as brief) Display standard information about all routing instances. brief | detail | summary—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. (These options are not available with the operational keyword.) instance-name—(Optional) Display information for a specified routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. operational—(Optional) Display operational routing instances. Required Privilege Level List of Sample Output Output Fields view show route instance on page 1966 show route instance detail (Graceful Restart Complete) on page 1967 show route instance detail (Graceful Restart Incomplete) on page 1968 show route instance detail (VPLS Routing Instance) on page 1970 show route instance operational on page 1970 show route instance summary on page 1970 Table 248 on page 1965 lists the output fields for the show route instance command. Output fields are listed in the approximate order in which they appear. Table 248: show route instance Output Fields Field Name Field Description Level of Output Instance or instance-name Name of the routing instance. All levels Operational Routing Instances (operational keyword only) Names of all operational routing instances. — Type Type of routing instance: forwarding, l2vpn, no-forwarding, vpls, or vrf. All levels 1965 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 248: show route instance Output Fields (continued) Field Name Field Description Level of Output State State of the routing instance: active or inactive. brief detail none Interfaces Name of interfaces belonging to this routing instance. brief detail none Restart State Status of graceful restart for this instance: Pending or Complete. detail Path selection timeout Maximum amount of time, in seconds, remaining until graceful restart is declared complete. The default is 300. detail Tables Tables (and number of routes) associated with this routing instance. none brief detail Route-distinguisher Unique route distinguisher associated with this routing instance. detail Vrf-import VPN routing and forwarding instance import policy name. detail Vrf-export VPN routing and forwarding instance export policy name. detail Vrf-import-target VPN routing and forwarding instance import target community name. detail Vrf-export-target VPN routing and forwarding instance export target community name. detail Fast-reroute-priority Fast reroute priority setting for a VPLS routing instance: high, medium, or low. The default is low. detail Restart State Restart state: detail • Pending:protocol-name—List of protocols that have not yet completed graceful restart for this routing table. • Complete—All protocols have restarted for this routing table. Primary rib Primary table for this routing instance. brief none summary Active/holddown/hidden Number of active, hold-down, and hidden routes. All levels show route instance 1966 user@host> show route instance Instance Type Primary RIB master forwarding inet.0 iso.0 mpls.0 inet6.0 l2circuit.0 __juniper_private1__ forwarding __juniper_private1__.inet.0 __juniper_private1__.inet6.0 Active/holddown/hidden 16/0/1 1/0/0 0/0/0 2/0/0 0/0/0 12/0/0 1/0/0 Chapter 74: Operational Commands for Layer 3 Protocols show route instance detail (Graceful Restart Complete) user@host> show route instance detail master: Router ID: 10.255.14.176 Type: forwarding State: Active Restart State: Complete Path selection timeout: 300 Tables: inet.0 : 17 routes (15 active, 0 holddown, Restart Complete inet.3 : 2 routes (2 active, 0 holddown, 0 Restart Complete iso.0 : 1 routes (1 active, 0 holddown, 0 Restart Complete mpls.0 : 19 routes (19 active, 0 holddown, Restart Complete bgp.l3vpn.0 : 10 routes (10 active, 0 holddown, Restart Complete inet6.0 : 2 routes (2 active, 0 holddown, 0 Restart Complete bgp.l2vpn.0 : 1 routes (1 active, 0 holddown, 0 Restart Complete BGP-INET: Router ID: 10.69.103.1 Type: vrf State: Active Restart State: Complete Path selection timeout: 300 Interfaces: t3-0/0/0.103 Route-distinguisher: 10.255.14.176:103 Vrf-import: [ BGP-INET-import ] Vrf-export: [ BGP-INET-export ] Tables: BGP-INET.inet.0 : 4 routes (4 active, 0 holddown, 0 Restart Complete BGP-L: Router ID: 10.69.104.1 Type: vrf State: Active Restart State: Complete Path selection timeout: 300 Interfaces: t3-0/0/0.104 Route-distinguisher: 10.255.14.176:104 Vrf-import: [ BGP-L-import ] Vrf-export: [ BGP-L-export ] Tables: BGP-L.inet.0 : 4 routes (4 active, 0 holddown, 0 Restart Complete BGP-L.mpls.0 : 3 routes (3 active, 0 holddown, 0 Restart Complete L2VPN: Router ID: 0.0.0.0 Type: l2vpn State: Active Restart State: Complete Path selection timeout: 300 Interfaces: t3-0/0/0.512 Route-distinguisher: 10.255.14.176:512 Vrf-import: [ L2VPN-import ] Vrf-export: [ L2VPN-export ] Tables: L2VPN.l2vpn.0 : 2 routes (2 active, 0 holddown, 0 Restart Complete LDP: Router ID: 10.69.105.1 Type: vrf State: Active 1 hidden) hidden) hidden) 0 hidden) 0 hidden) hidden) hidden) hidden) hidden) hidden) hidden) 1967 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Restart State: Complete Path selection Interfaces: t3-0/0/0.105 Route-distinguisher: 10.255.14.176:105 Vrf-import: [ LDP-import ] Vrf-export: [ LDP-export ] Tables: LDP.inet.0 : 5 routes (4 Restart Complete OSPF: Router ID: 10.69.101.1 Type: vrf State: Active Restart State: Complete Path selection Interfaces: t3-0/0/0.101 Route-distinguisher: 10.255.14.176:101 Vrf-import: [ OSPF-import ] Vrf-export: [ OSPF-export ] Vrf-import-target: [ target:11111 Tables: OSPF.inet.0 : 8 routes (7 Restart Complete RIP: Router ID: 10.69.102.1 Type: vrf State: Active Restart State: Complete Path selection Interfaces: t3-0/0/0.102 Route-distinguisher: 10.255.14.176:102 Vrf-import: [ RIP-import ] Vrf-export: [ RIP-export ] Tables: RIP.inet.0 : 6 routes (6 Restart Complete STATIC: Router ID: 10.69.100.1 Type: vrf State: Active Restart State: Complete Path selection Interfaces: t3-0/0/0.100 Route-distinguisher: 10.255.14.176:100 Vrf-import: [ STATIC-import ] Vrf-export: [ STATIC-export ] Tables: STATIC.inet.0 : 4 routes (4 Restart Complete show route instance detail (Graceful Restart Incomplete) 1968 timeout: 300 active, 0 holddown, 0 hidden) timeout: 300 active, 0 holddown, 0 hidden) timeout: 300 active, 0 holddown, 0 hidden) timeout: 300 active, 0 holddown, 0 hidden) user@host> show route instance detail master: Router ID: 10.255.14.176 Type: forwarding State: Active Restart State: Pending Path selection timeout: 300 Tables: inet.0 : 17 routes (15 active, 1 holddown, Restart Pending: OSPF LDP inet.3 : 2 routes (2 active, 0 holddown, 0 Restart Pending: OSPF LDP iso.0 : 1 routes (1 active, 0 holddown, 0 Restart Complete mpls.0 : 23 routes (23 active, 0 holddown, Restart Pending: LDP VPN 1 hidden) hidden) hidden) 0 hidden) Chapter 74: Operational Commands for Layer 3 Protocols bgp.l3vpn.0 : 10 routes (10 active, 0 holddown, Restart Pending: BGP VPN inet6.0 : 2 routes (2 active, 0 holddown, 0 Restart Complete bgp.l2vpn.0 : 1 routes (1 active, 0 holddown, 0 Restart Pending: BGP VPN BGP-INET: Router ID: 10.69.103.1 Type: vrf State: Active Restart State: Pending Path selection timeout: 300 Interfaces: t3-0/0/0.103 Route-distinguisher: 10.255.14.176:103 Vrf-import: [ BGP-INET-import ] Vrf-export: [ BGP-INET-export ] Tables: BGP-INET.inet.0 : 6 routes (5 active, 0 holddown, 0 Restart Pending: VPN BGP-L: Router ID: 10.69.104.1 Type: vrf State: Active Restart State: Pending Path selection timeout: 300 Interfaces: t3-0/0/0.104 Route-distinguisher: 10.255.14.176:104 Vrf-import: [ BGP-L-import ] Vrf-export: [ BGP-L-export ] Tables: BGP-L.inet.0 : 6 routes (5 active, 0 holddown, 0 Restart Pending: VPN BGP-L.mpls.0 : 2 routes (2 active, 0 holddown, 0 Restart Pending: VPN L2VPN: Router ID: 0.0.0.0 Type: l2vpn State: Active Restart State: Pending Path selection timeout: 300 Interfaces: t3-0/0/0.512 Route-distinguisher: 10.255.14.176:512 Vrf-import: [ L2VPN-import ] Vrf-export: [ L2VPN-export ] Tables: L2VPN.l2vpn.0 : 2 routes (2 active, 0 holddown, 0 Restart Pending: VPN L2VPN LDP: Router ID: 10.69.105.1 Type: vrf State: Active Restart State: Pending Path selection timeout: 300 Interfaces: t3-0/0/0.105 Route-distinguisher: 10.255.14.176:105 Vrf-import: [ LDP-import ] Vrf-export: [ LDP-export ] Tables: LDP.inet.0 : 5 routes (4 active, 1 holddown, 0 Restart Pending: OSPF LDP VPN OSPF: Router ID: 10.69.101.1 Type: vrf State: Active Restart State: Pending Path selection timeout: 300 Interfaces: 0 hidden) hidden) hidden) hidden) hidden) hidden) hidden) hidden) 1969 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS t3-0/0/0.101 Route-distinguisher: 10.255.14.176:101 Vrf-import: [ OSPF-import ] Vrf-export: [ OSPF-export ] Tables: OSPF.inet.0 : 8 routes (7 Restart Pending: OSPF VPN RIP: Router ID: 10.69.102.1 Type: vrf State: Active Restart State: Pending Path selection Interfaces: t3-0/0/0.102 Route-distinguisher: 10.255.14.176:102 Vrf-import: [ RIP-import ] Vrf-export: [ RIP-export ] Tables: RIP.inet.0 : 8 routes (6 Restart Pending: RIP VPN STATIC: Router ID: 10.69.100.1 Type: vrf State: Active Restart State: Pending Path selection Interfaces: t3-0/0/0.100 Route-distinguisher: 10.255.14.176:100 Vrf-import: [ STATIC-import ] Vrf-export: [ STATIC-export ] Tables: STATIC.inet.0 : 4 routes (4 Restart Pending: VPN show route instance detail (VPLS Routing Instance) show route instance operational active, 1 holddown, 0 hidden) timeout: 300 active, 2 holddown, 0 hidden) timeout: 300 active, 0 holddown, 0 hidden) user@host> show route instance detail test-vpls test-vpls: Router ID: 0.0.0.0 Type: vpls State: Active Interfaces: lsi.1048833 lsi.1048832 fe-0/1/0.513 Route-distinguisher: 10.255.37.65:1 Vrf-import: [ __vrf-import-test-vpls-internal__ ] Vrf-export: [ __vrf-export-test-vpls-internal__ ] Vrf-import-target: [ target:300:1 ] Vrf-export-target: [ target:300:1 ] Fast-reroute-priority: high Tables: test-vpls.l2vpn.0 : 3 routes (3 active, 0 holddown, 0 hidden) user@host> show route instance operational Operational Routing Instances: master default show route instance summary 1970 user@host> show route instance summary Instance Type Primary rib master forwarding inet.0 iso.0 Active/holddown/hidden 15/0/1 1/0/0 Chapter 74: Operational Commands for Layer 3 Protocols BGP-INET BGP-L L2VPN LDP OSPF RIP STATIC mpls.0 l3vpn.0 inet6.0 l2vpn.0 l2circuit.0 35/0/0 0/0/0 2/0/0 0/0/0 0/0/0 BGP-INET.inet.0 BGP-INET.iso.0 BGP-INET.inet6.0 5/0/0 0/0/0 0/0/0 BGP-L.inet.0 BGP-L.iso.0 BGP-L.mpls.0 BGP-L.inet6.0 5/0/0 0/0/0 4/0/0 0/0/0 L2VPN.inet.0 L2VPN.iso.0 L2VPN.inet6.0 L2VPN.l2vpn.0 0/0/0 0/0/0 0/0/0 2/0/0 LDP.inet.0 LDP.iso.0 LDP.mpls.0 LDP.inet6.0 LDP.l2circuit.0 4/0/0 0/0/0 0/0/0 0/0/0 0/0/0 OSPF.inet.0 OSPF.iso.0 OSPF.inet6.0 7/0/0 0/0/0 0/0/0 RIP.inet.0 RIP.iso.0 RIP.inet6.0 6/0/0 0/0/0 0/0/0 STATIC.inet.0 STATIC.iso.0 STATIC.inet6.0 4/0/0 0/0/0 0/0/0 vrf vrf l2vpn vrf vrf vrf vrf 1971 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route label Syntax Syntax (J-EX Series Switch) Release Information Description Options show route label label show route label label Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the routes based on a specified Multiprotocol Label Switching (MPLS) label value. label—Value of the MPLS label. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route label view show route label on page 1972 show route label detail on page 1973 show route label extensive on page 1973 show route label terse on page 1973 For information about output fields, see the output field table for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route label 100016 mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 100016 *[VPN/170] 03:25:41 > to 10.12.80.1 via ge-6/3/2.0, Pop 1972 Chapter 74: Operational Commands for Layer 3 Protocols show route label detail user@host> show route label 100016 detail mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete 100016 (1 entry, 1 announced) *VPN Preference: 170 Next-hop reference count: 2 Source: 10.12.80.1 Next hop: 10.12.80.1 via ge-6/3/2.0, selected Label operation: Pop State: Local AS: 1 Age: 3:23:31 Task: BGP.0.0.0.0+179 Announcement bits (1): 0-KRT AS path: 100 I Ref Cnt: 2 show route label extensive show route label terse The output for the show route label extensive command is identical to that of the show route label detail command. For sample output, see show route label detail on page 1973. user@host> show route label 100016 terse mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both A Destination * 100016 P Prf V 170 Metric 1 Metric 2 Next hop >10.12.80.1 AS path 1973 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route label-switched-path Syntax Syntax (J-EX Series Switch) Release Information Description Options show route label-switched-path path-name show route label-switched-path path-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the routes used in a Multiprotocol Label Switching (MPLS) label-switched path (LSP). brief | detail | extensive | terse—(Optional) Display the specified level of output. path-name—LSP tunnel name. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route label-switched-path view show route label-switched-path on page 1974 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route label-switched-path sf-to-ny inet.0: 29 destinations, 29 routes (29 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1.1.1.1/32 3.3.3.3/32 [MPLS/7] 00:00:06, metric 0 > to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny *[MPLS/7] 00:00:06, metric 0 > to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 2.2.2.2/32 4.4.4.4/32 111.222.1.9/32 *[MPLS/7] 00:00:06, metric 0 > to 111.222.1.9 via s0-0/0/0, *[MPLS/7] 00:00:06, metric 0 to 111.222.1.9 via s0-0/0/0, > to 111.222.1.9 via s0-0/0/0, to 111.222.1.9 via s0-0/0/0, [MPLS/7] 00:00:06, metric 0 > to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny label-switched-path abc label-switched-path xyz label-switched-path sf-to-ny label-switched-path sf-to-ny iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1974 Chapter 74: Operational Commands for Layer 3 Protocols mpls.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1975 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route martians Syntax Syntax (J-EX Series Switch) Release Information Description Options show route martians
show route martians
Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the martian (invalid and ignored) entries associated with each routing table. none—Display standard information about route martians for all routing tables. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. table routing-table-name—(Optional) Display only the martian entries associated with a particular routing table. Required Privilege Level List of Sample Output Output Fields view show route martians on page 1976 Table 249 on page 1976 lists the output fields for the show route martians command. Output fields are listed in the approximate order in which they appear Table 249: show route martians Output Fields show route martians Field Name Field Description table-name Name of the route table in which the route martians reside. destination-prefix Route destination. match value Route match parameter. status Status of the route: allowed or disallowed. user@host> show route martians inet.0: 0.0.0.0/0 exact -- allowed 0.0.0.0/8 orlonger -- disallowed 127.0.0.0/8 orlonger -- disallowed 128.0.0.0/16 orlonger -- disallowed 191.255.0.0/16 orlonger -- disallowed 192.0.0.0/24 orlonger -- disallowed 223.255.255.0/24 orlonger -- disallowed 240.0.0.0/4 orlonger -- disallowed 1976 Chapter 74: Operational Commands for Layer 3 Protocols inet.1: 0.0.0.0/0 exact -- allowed 0.0.0.0/8 orlonger -- disallowed 127.0.0.0/8 orlonger -- disallowed 128.0.0.0/16 orlonger -- disallowed 191.255.0.0/16 orlonger -- disallowed 192.0.0.0/24 orlonger -- disallowed 223.255.255.0/24 orlonger -- disallowed 240.0.0.0/4 orlonger -- disallowed .... 1977 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route next-hop Syntax Syntax (J-EX Series Switch) Release Information Description Options show route next-hop next-hop show route next-hop next-hop Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the routing table that are being sent to the specified next-hop address. brief | detail | extensive | terse—(Optional) Display the specified level of ouput. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. next-hop—Next-hop address. Required Privilege Level List of Sample Output Output Fields show route next-hop view show route next-hop on page 1978 show route next-hop detail on page 1979 show route next-hop extensive on page 1980 show route next-hop terse on page 1982 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route next-hop 192.168.71.254 inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.10.0.0/16 10.209.0.0/16 172.16.0.0/12 192.168.0.0/16 192.168.102.0/23 207.17.136.0/24 207.17.136.192/32 1978 *[Static/5] 06:26:25 > to 192.168.71.254 *[Static/5] 06:26:25 > to 192.168.71.254 *[Static/5] 06:26:25 > to 192.168.71.254 *[Static/5] 06:26:25 > to 192.168.71.254 *[Static/5] 06:26:25 > to 192.168.71.254 *[Static/5] 06:26:25 > to 192.168.71.254 *[Static/5] 06:26:25 > to 192.168.71.254 via fxp0.0 via fxp0.0 via fxp0.0 via fxp0.0 via fxp0.0 via fxp0.0 via fxp0.0 Chapter 74: Operational Commands for Layer 3 Protocols private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) red.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden) Restart Complete iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) show route next-hop detail user@host> show route next-hop 192.168.71.254 detail inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden) Restart Complete 10.10.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I 10.209.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I 172.16.0.0/12 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I 192.168.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT 1979 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I 192.168.102.0/23 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I 207.17.136.0/24 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I 207.17.136.192/32 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 36 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 1 Age: 6:27:41 Task: RT Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2 AS path: I private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) red.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden) Restart Complete iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) show route next-hop extensive user@host> show route next-hop 192.168.71.254 extensive inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.10.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected 1980 Chapter 74: Operational Commands for Layer 3 Protocols State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I 10.209.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.209.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I 172.16.0.0/12 (1 entry, 1 announced) TSI: KRT in-kernel 172.16.0.0/12 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I 192.168.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 192.168.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I 192.168.102.0/23 (1 entry, 1 announced) TSI: KRT in-kernel 192.168.102.0/23 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I 207.17.136.0/24 (1 entry, 1 announced) TSI: 1981 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS KRT in-kernel 207.17.136.0/24 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I 207.17.136.192/32 (1 entry, 1 announced) TSI: KRT in-kernel 207.17.136.192/32 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:02:28 Task: RT Announcement bits (1): 0-KRT AS path: I private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) green.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) red.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) show route next-hop terse user@host> show route next-hop 192.168.71.254 terse inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden) Restart Complete + = Active Route, - = Last Active, * = Both A * * * * * * * Destination 10.10.0.0/16 10.209.0.0/16 172.16.0.0/12 192.168.0.0/16 192.168.102.0/23 207.17.136.0/24 207.17.136.192/32 P Prf S 5 S 5 S 5 S 5 S 5 S 5 S 5 Metric 1 Metric 2 Next hop >192.168.71.254 >192.168.71.254 >192.168.71.254 >192.168.71.254 >192.168.71.254 >192.168.71.254 >192.168.71.254 AS path private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) red.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden) Restart Complete iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete 1982 Chapter 74: Operational Commands for Layer 3 Protocols mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 1983 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route no-community Syntax Syntax (J-EX Series Switch) Release Information Description Options show route no-community show route no-community Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the route entries in each routing table that are not associated with any community. none—(Same as brief) Display the route entries in each routing table that are not associated with any community. brief | detail | extensive | terse—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route no-community view show route no-community on page 1984 show route no-community detail on page 1985 show route no-community extensive on page 1985 show route no-community terse on page 1986 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route no-community inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 10.10.0.0/16 10.209.0.0/16 10.255.71.52/32 10.255.71.63/32 10.255.71.64/32 10.255.71.240/32 10.255.71.241/32 10.255.71.242/32 1984 *[Static/5] 00:36:27 > to 192.168.71.254 via fxp0.0 *[Static/5] 00:36:27 > to 192.168.71.254 via fxp0.0 *[Direct/0] 00:36:27 > via lo0.0 *[OSPF/10] 00:04:39, metric 1 > to 35.1.1.2 via ge-3/1/0.0 *[OSPF/10] 00:00:08, metric 2 > to 35.1.1.2 via ge-3/1/0.0 *[OSPF/10] 00:05:04, metric 2 via so-0/1/2.0 > via so-0/3/2.0 *[OSPF/10] 00:05:14, metric 1 > via so-0/1/2.0 *[OSPF/10] 00:05:19, metric 1 > via so-0/3/2.0 Chapter 74: Operational Commands for Layer 3 Protocols 12.1.1.0/24 14.1.1.0/24 16.1.1.0/24 *[OSPF/10] 00:05:14, metric 2 > via so-0/3/2.0 *[OSPF/10] 00:00:08, metric 3 > to 35.1.1.2 via ge-3/1/0.0 via so-0/1/2.0 via so-0/3/2.0 *[OSPF/10] 00:05:14, metric 2 > via so-0/1/2.0 ..... show route no-community detail user@host> show route no-community detail inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 38:08 Task: RT Announcement bits (1): 0-KRT AS path: I 10.209.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 38:08 Task: RT Announcement bits (1): 0-KRT AS path: I .... show route no-community extensive user@host> show route no-community extensive inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.10.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:03:33 Task: RT Announcement bits (1): 0-KRT AS path: I 10.209.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.209.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Local AS: 69 Age: 2:03:33 Task: RT Announcement bits (1): 0-KRT 1985 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS AS path: I show route no-community terse user@host> show route no-community terse inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A * * * * * * Destination 10.10.0.0/16 10.209.0.0/16 10.255.71.52/32 10.255.71.63/32 10.255.71.64/32 10.255.71.240/32 P Prf S 5 S 5 D 0 O 10 O 10 O 10 * * * * 10.255.71.241/32 10.255.71.242/32 12.1.1.0/24 14.1.1.0/24 O O O O 10 10 10 10 1 1 2 3 O 10 2 * 16.1.1.0/24 ... 1986 Metric 1 1 2 2 Metric 2 Next hop >192.168.71.254 >192.168.71.254 >lo0.0 >35.1.1.2 >35.1.1.2 so-0/1/2.0 >so-0/3/2.0 >so-0/1/2.0 >so-0/3/2.0 >so-0/3/2.0 >35.1.1.2 so-0/1/2.0 so-0/3/2.0 >so-0/1/2.0 AS path Chapter 74: Operational Commands for Layer 3 Protocols show route protocol Syntax Syntax (J-EX Series Switch) Release Information Description Options show route protocol protocol show route protocol protocol Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the route entries in the routing table that were learned from a particular protocol. protocol—Protocol from which the route was learned: • access—Access route for use by DHCP application • access-internal—Access-internal route for use by DHCP application • aggregate—Locally generated aggregate route • atmvpn—Asynchronous Transfer Mode virtual private network • bgp—Border Gateway Protocol • ccc—Circuit cross-connect • direct—Directly connected route • dvmrp—Distance Vector Multicast Routing Protocol • esis—End System-to-Intermediate System • flow—Locally defined flow-specification route. • isis—Intermediate System-to-Intermediate System • ldp—Label Distribution Protocol • l2circuit—Layer 2 circuit • l2vpn—Layer 2 virtual private network • local—Local address • mpls—Multiprotocol Label Switching • msdp—Multicast Source Discovery Protocol • ospf—Open Shortest Path First versions 2 and 3 • ospf2—Open Shortest Path First versions 2 only • ospf3—Open Shortest Path First version 3 only • pim—Protocol Independent Multicast • rip—Routing Information Protocol • ripng—Routing Information Protocol next generation 1987 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • rsvp—Resource Reservation Protocol • rtarget—Local route target virtual private network • static—Statically defined route • tunnel—Dynamic tunnel • vpn—Virtual private network NOTE: J-EX Series switches run a subset of these protocols. See the switch CLI for details. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route protocol access view show route protocol access on page 1988 show route protocol access-internal extensive on page 1989 show route protocol bgp on page 1989 show route protocol bgp detail on page 1989 show route protocol bgp extensive on page 1989 show route protocol bgp terse on page 1990 show route protocol direct on page 1990 show route protocol l2circuit detail on page 1990 show route protocol l2vpn extensive on page 1991 show route protocol ldp on page 1992 show route protocol ldp extensive on page 1992 show route protocol ospf (Layer 3 VPN) on page 1993 show route protocol ospf detail on page 1994 show route protocol rip on page 1994 show route protocol rip detail on page 1994 show route protocol ripng table inet6 on page 1994 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route protocol access inet.0: 30380 destinations, 30382 routes (30379 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 13.160.0.3/32 13.160.0.4/32 1988 *[Access/13] 00:00:09 > to 13.160.0.2 via fe-0/0/0.0 *[Access/13] 00:00:09 > to 13.160.0.2 via fe-0/0/0.0 Chapter 74: Operational Commands for Layer 3 Protocols 13.160.0.5/32 *[Access/13] 00:00:09 > to 13.160.0.2 via fe-0/0/0.0 show route protocol access-internal extensive user@host> show route protocol access-internal 13.160.0.19 extensive show route protocol bgp user@host> show route protocol bgp 192.168.64.0/21 inet.0: 100020 destinations, 100022 routes (100019 active, 0 holddown, 1 hidden) 13.160.0.19/32 (1 entry, 1 announced) TSI: KRT in-kernel 13.160.0.19/32 -> {13.160.0.2} *Access-internal Preference: 12 Next-hop reference count: 200000 Next hop: 13.160.0.2 via fe-0/0/0.0, selected State: Age: 36 Task: RPD Unix Domain Server./var/run/rpd_serv.local Announcement bits (1): 0-KRT AS path: I inet.0: 24 destinations, 32 routes (23 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 192.168.64.0/21 [BGP/170] 00:04:33, localpref 100 AS path: 10023 21 I > to 100.1.3.2 via ge-5/0/3.0, Push 100080 show route protocol bgp detail show route protocol bgp 66.117.63.0/24 exact detail inet.0: 227318 destinations, 227319 routes (227305 active, 0 holddown, 13 hidden) 66.117.63.0/24 (1 entry, 1 announced) *BGP Preference: 170/-101 Next hop type: Indirect Next-hop reference count: 681816 Source: 207.17.136.192 Next hop type: Router, Next hop index: 324 Next hop: 192.168.167.254 via fxp0.0, selected Protocol next hop: 207.17.136.29 Indirect next hop: 8c7b09c 342 State: show route protocol bgp 192.168.64.0/21 extensive inet.0: 24 destinations, 32 routes (23 active, 0 holddown, 1 hidden) 192.168.64.0/21 (2 entries, 1 announced) TSI: Page 0 idx 0 Type 1 val 86f50a8 BGP Preference: 170/-101 Next-hop reference count: 3 Source: 100.1.3.2 1989 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Next hop: 100.1.3.2 via ge-5/0/3.0, selected Label operation: Push 100080 State: Inactive reason: Route Preference Local AS: 21 Peer AS: 10023 Age: 4:43 Task: BGP_10023.100.1.3.2+4282 AS path: 10023 21 I Route Label: 100080 Localpref: 100 Router ID: 100.1.3.2 show route protocol bgp terse user@host> show route protocol bgp 192.168.64.0/21 terse inet.0: 24 destinations, 32 routes (23 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A Destination 192.168.64.0/21 show route protocol direct P Prf B 170 Metric 1 100 Metric 2 Next hop >100.1.3.2 AS path 10023 21 I user@host> show route protocol direct inet.0: 35 destinations, 35 routes (34 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 127.0.0.1/32 111.222.5.0/24 111.222.8.16/28 111.222.8.100/30 111.222.8.104/30 111.222.8.161/32 111.222.8.163/32 [Direct/0] 14:36:24 > via lo0.0 *[Direct/0] 14:36:24 > via fxp0.0 *[Direct/0] 14:36:24 > via at-5/3/0.0 *[Direct/0] 14:36:24 > via at-5/3/0.129 *[Direct/0] 14:36:24 > via at-5/3/0.128 *[Direct/0] 14:36:24 > via t3-5/2/0.0 *[Direct/0] 14:36:24 > via t3-5/2/1.0 ... iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 47.0005.80ff.f800.0000.0108.0001.1921.6800.5081.00/160 *[Direct/0] 14:36:24 > via lo0.0 show route protocol l2circuit detail user@host> show route protocol l2circuit detail mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) 100000 (1 entry, 1 announced) *L2CKT Preference: 7 Next hop: via ge-2/0/0.0, selected Label operation: Pop Offset: 4 State: Local AS: 99 Age: 9:52 Task: Common L2 VC Announcement bits (1): 0-KRT 1990 Chapter 74: Operational Commands for Layer 3 Protocols AS path: I ge-2/0/0.0 (1 entry, 1 announced) *L2CKT Preference: 7 Next hop: via so-1/1/2.0 weight 1, selected Label-switched-path my-lsp Label operation: Push 100000, Push 100000(top)[0] Offset: -4 Protocol next hop: 10.245.255.63 Push 100000 Offset: -4 Indirect next hop: 86af0c0 298 State: Local AS: 99 Age: 9:52 Task: Common L2 VC Announcement bits (2): 0-KRT 1-Common L2 VC AS path: I l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced) *L2CKT Preference: 7 Next hop: via so-1/1/2.0 weight 1, selected Label-switched-path my-lsp Label operation: Push 100000[0] Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296 State: Local AS: 99 Age: 10:21 Task: l2 circuit Announcement bits (1): 0-LDP AS path: I VC Label 100000, MTU 1500, VLAN ID 512 show route protocol l2vpn extensive user@host> show route protocol l2vpn extensive inet.0: 14 destinations, 15 routes (13 active, 0 holddown, 1 hidden) inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) mpls.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden) 800001 (1 entry, 1 announced) TSI: KRT in-kernel 800001 /36 -> {so-0/0/0.0} *L2VPN Preference: 7 Next hop: via so-0/0/0.0 weight 49087 balance 97%, selected Label operation: Pop Offset: 4 State: Local AS: 69 Age: 7:48 Task: Common L2 VC Announcement bits (1): 0-KRT AS path: I so-0/0/0.0 (1 entry, 1 announced) TSI: KRT in-kernel so-0/0/0.0.0 /16 -> {indirect(288)} *L2VPN Preference: 7 Next hop: via so-0/0/1.0, selected Label operation: Push 800000 Offset: -4 1991 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Protocol next hop: 10.255.14.220 Push 800000 Offset: -4 Indirect next hop: 85142a0 288 State: Local AS: 69 Age: 7:48 Task: Common L2 VC Announcement bits (2): 0-KRT 1-Common L2 VC AS path: I Communities: target:69:1 Layer2-info: encaps:PPP, control flags:2, mtu: 0 show route protocol ldp user@host> show route protocol ldp inet.0: 12 destinations, 13 routes (12 active, 0 holddown, 0 hidden) inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 192.168.16.1/32 192.168.17.1/32 *[LDP/9] 1d 23:03:35, metric 1 > via t1-4/0/0.0, Push 100000 *[LDP/9] 1d 23:03:35, metric 1 > via t1-4/0/0.0 private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 100064 100064(S=0) 100080 show route protocol ldp extensive *[LDP/9] 1d 23:03:35, metric 1 > via t1-4/0/0.0, Pop *[LDP/9] 1d 23:03:35, metric 1 > via t1-4/0/0.0, Pop *[LDP/9] 1d 23:03:35, metric 1 > via t1-4/0/0.0, Swap 100000 user@host> show route protocol ldp extensive 192.168.16.1/32 (1 entry, 1 announced) State: *LDP Preference: 9 Next-hop reference count: 3 Next hop: via t1-4/0/0.0, selected Label operation: Push 100000 State: Local AS: 65500 Age: 1d 23:03:58 Metric: 1 Task: LDP Announcement bits (2): 0-Resolve tree 1 2-Resolve tree 2 AS path: I 192.168.17.1/32 (1 entry, 1 announced) State: *LDP Preference: 9 Next-hop reference count: 3 Next hop: via t1-4/0/0.0, selected State: Local AS: 65500 Age: 1d 23:03:58 Metric: 1 Task: LDP Announcement bits (2): 0-Resolve tree 1 2-Resolve tree 2 AS path: I 1992 Chapter 74: Operational Commands for Layer 3 Protocols private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) 100064 (1 entry, 1 announced) TSI: KRT in-kernel 100064 /36 -> {t1-4/0/0.0} *LDP Preference: 9 Next-hop reference count: 2 Next hop: via t1-4/0/0.0, selected State: Local AS: 65500 Age: 1d 23:03:58 Metric: 1 Task: LDP Announcement bits (1): 0-KRT AS path: I Prefixes bound to route: 192.168.17.1/32 100064(S=0) (1 entry, 1 announced) TSI: KRT in-kernel 100064 /40 -> {t1-4/0/0.0} *LDP Preference: 9 Next-hop reference count: 2 Next hop: via t1-4/0/0.0, selected Label operation: Pop State: Local AS: 65500 Age: 1d 23:03:58 Metric: 1 Task: LDP Announcement bits (1): 0-KRT AS path: I 100080 (1 entry, 1 announced) TSI: KRT in-kernel 100080 /36 -> {t1-4/0/0.0} *LDP Preference: 9 Next-hop reference count: 2 Next hop: via t1-4/0/0.0, selected Label operation: Swap 100000 State: Local AS: 65500 Age: 1d 23:03:58 Metric: 1 Task: LDP Announcement bits (1): 0-KRT AS path: I Prefixes bound to route: 192.168.16.1/32 show route protocol ospf (Layer 3 VPN) user@host> show route protocol ospf inet.0: 40 destinations, 40 routes (39 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 10.39.1.4/30 10.39.1.8/30 10.255.14.171/32 10.255.14.179/32 224.0.0.5/32 *[OSPF/10] 00:05:18, > via t3-3/2/0.0 [OSPF/10] 00:05:18, > via t3-3/2/0.0 *[OSPF/10] 00:05:18, > via t3-3/2/0.0 *[OSPF/10] 00:05:18, > via t3-3/2/0.0 *[OSPF/10] 20:25:55, metric 4 metric 2 metric 4 metric 2 metric 1 1993 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.39.1.16/30 10.255.14.173/32 224.0.0.5/32 show route protocol ospf detail [OSPF/10] 00:05:43, metric 1 > via so-0/2/2.0 *[OSPF/10] 00:05:43, metric 1 > via so-0/2/2.0 *[OSPF/10] 20:26:20, metric 1 user@host> show route protocol ospf detail VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.39.1.16/30 (2 entries, 0 announced) OSPF Preference: 10 Nexthop: via so-0/2/2.0, selected State: Inactive reason: Route Preference Age: 6:25 Metric: 1 Area: 0.0.0.0 Task: VPN-AB-OSPF AS path: I Communities: Route-Type:0.0.0.0:1:0 ... show route protocol rip user@host> show route protocol rip inet.0: 26 destinations, 27 routes (25 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.255.14.177/32 *[RIP/100] 20:24:34, metric 2 > to 10.39.1.22 via t3-0/2/2.0 224.0.0.9/32 *[RIP/100] 00:03:59, metric 1 show route protocol rip detail user@host> show route protocol rip detail inet.0: 26 destinations, 27 routes (25 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.255.14.177/32 (1 entry, 1 announced) *RIP Preference: 100 Nexthop: 10.39.1.22 via t3-0/2/2.0, selected State: Age: 20:25:02 Metric: 2 Task: VPN-AB-RIPv2 Announcement bits (2): 0-KRT 2-BGP.0.0.0.0+179 AS path: I Route learned from 10.39.1.22 expires in 96 seconds show route protocol ripng table inet6 user@host> show route protocol ripng table inet6 inet6.0: 4215 destinations, 4215 routes (4214 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 1111::1/128 1111::2/128 1994 *[RIPng/100] 02:13:33, metric 2 > to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0 *[RIPng/100] 02:13:33, metric 2 > to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0 Chapter 74: Operational Commands for Layer 3 Protocols 1111::3/128 1111::4/128 1111::5/128 1111::6/128 *[RIPng/100] 02:13:33, metric 2 > to fe80::2a0:a5ff:fe3d:56 via *[RIPng/100] 02:13:33, metric 2 > to fe80::2a0:a5ff:fe3d:56 via *[RIPng/100] 02:13:33, metric 2 > to fe80::2a0:a5ff:fe3d:56 via *[RIPng/100] 02:13:33, metric 2 > to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0 t3-0/2/0.0 t3-0/2/0.0 t3-0/2/0.0 1995 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route range Syntax Syntax (J-EX Series Switch) Release Information Description Options show route range show route range Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display routing table entries using a prefix range. none—Display standard information about all routing table entries using a prefix range. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. destination-prefix—(Optional) Destination and prefix mask for the range. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route range view show route range on page 1996 show route range destination-prefix on page 1997 show route range detail on page 1997 show route range extensive on page 1998 show route range terse on page 1999 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route range inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 10.10.0.0/16 10.209.0.0/16 10.255.71.14/32 172.16.0.0/12 192.168.0.0/16 192.168.64.0/21 1996 *[Static/5] 00:30:01 > to 192.168.71.254 *[Static/5] 00:30:01 > to 192.168.71.254 *[Direct/0] 00:30:01 > via lo0.0 *[Static/5] 00:30:01 > to 192.168.71.254 *[Static/5] 00:30:01 > to 192.168.71.254 *[Direct/0] 00:30:01 via fxp0.0 via fxp0.0 via fxp0.0 via fxp0.0 Chapter 74: Operational Commands for Layer 3 Protocols 192.168.71.14/32 192.168.102.0/23 > via fxp0.0 *[Local/0] 00:30:01 Local via fxp0.0 *[Static/5] 00:30:01 > to 192.168.71.254 via fxp0.0 ... show route range destination-prefix user@host> show route range 192.168.0.0 inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 192.168.0.0/16 192.168.64.0/21 192.168.71.14/32 192.168.102.0/23 show route range detail *[Static/5] 00:31:14 > to 192.168.71.254 via fxp0.0 *[Direct/0] 00:31:14 > via fxp0.0 *[Local/0] 00:31:14 Local via fxp0.0 *[Static/5] 00:31:14 > to 192.168.71.254 via fxp0.0 user@host> show route range detail inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 30:05 Task: RT Announcement bits (1): 0-KRT AS path: I 10.209.0.0/16 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 30:05 Task: RT Announcement bits (1): 0-KRT AS path: I 10.255.71.14/32 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Age: 30:05 Task: IF AS path: I 172.16.0.0/12 (1 entry, 1 announced) *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 30:05 Task: RT 1997 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Announcement bits (1): 0-KRT AS path: I ... show route range extensive user@host> show route range extensive inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden) 10.10.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.10.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 30:17 Task: RT Announcement bits (1): 0-KRT AS path: I 10.209.0.0/16 (1 entry, 1 announced) TSI: KRT in-kernel 10.209.0.0/16 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 30:17 Task: RT Announcement bits (1): 0-KRT AS path: I 10.255.71.14/32 (1 entry, 0 announced) *Direct Preference: 0 Next hop type: Interface Next-hop reference count: 1 Next hop: via lo0.0, selected State: Age: 30:17 Task: IF AS path: I 172.16.0.0/12 (1 entry, 1 announced) TSI: KRT in-kernel 172.16.0.0/12 -> {192.168.71.254} *Static Preference: 5 Next-hop reference count: 22 Next hop: 192.168.71.254 via fxp0.0, selected State: Age: 30:17 Task: RT Announcement bits (1): 0-KRT AS path: I ... 1998 Chapter 74: Operational Commands for Layer 3 Protocols show route range terse user@host> show route range terse inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A * * * * * * * * * * Destination 10.10.0.0/16 10.209.0.0/16 10.255.71.14/32 172.16.0.0/12 192.168.0.0/16 192.168.64.0/21 192.168.71.14/32 192.168.102.0/23 207.17.136.0/24 207.17.136.192/32 P Prf S 5 S 5 D 0 S 5 S 5 D 0 L 0 S 5 S 5 S 5 Metric 1 Metric 2 Next hop >192.168.71.254 >192.168.71.254 >lo0.0 >192.168.71.254 >192.168.71.254 >fxp0.0 Local >192.168.71.254 >192.168.71.254 >192.168.71.254 AS path __juniper_private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A Destination * 10.0.0.0/8 * 10.0.0.4/32 P Prf D 0 D 0 L 0 Metric 1 Metric 2 Next hop >fxp2.0 >fxp1.0 Local iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A Destination P Prf Metric 1 Metric 2 Next hop 47.0005.80ff.f800.0000.0108.0001.0102.5507.1014/152 * D 0 >lo0.0 AS path AS path inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A Destination P Prf Metric 1 abcd::10:255:71:14/128 * D 0 fe80::280:42ff:fe11:226f/128 * D 0 Metric 2 Next hop AS path >lo0.0 >lo0.0 __juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A Destination P Prf Metric 1 fe80::280:42ff:fe11:226f/128 * D 0 Metric 2 Next hop AS path >lo0.16385 1999 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route receive-protocol Syntax show route receive-protocol protocol neighbor-address Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the routing information as it was received through a particular neighbor using a particular dynamic routing protocol. brief | detail | extensive | terse—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. protocol neighbor-address—Protocol transmitting the route (bgp, dvmrp, msdp, pim, rip, or ripng) and address of the neighboring router from which the route entry was received. Additional Information Required Privilege Level List of Sample Output Output Fields The output displays the selected routes and the attributes with which they were received, but does not show the effects of import policy on the routing attributes. view show route receive-protocol bgp on page 2002 show route receive-protocol bgp extensive on page 2002 show route receive-protocol bgp extensive on page 2003 show route receive-protocol bgp detail (Layer 2 VPN) on page 2004 show route receive-protocol bgp extensive (Layer 2 VPN) on page 2004 show route receive-protocol bgp (Layer 3 VPN) on page 2005 show route receive-protocol bgp detail (Layer 3 VPN) on page 2005 show route receive-protocol bgp extensive (Layer 3 VPN) on page 2006 Table 250 on page 2000 describes the output fields for the show route receive-protocol command. Output fields are listed in the approximate order in which they appear. Table 250: show route receive-protocol Output Fields Field Name Field Description Level of Output routing-table-name Name of the routing table—for example, inet.0. All levels number destinations Number of destinations for which there are routes in the routing table. All levels 2000 Chapter 74: Operational Commands for Layer 3 Protocols Table 250: show route receive-protocol Output Fields (continued) Field Name Field Description Level of Output number routes Number of routes in the routing table and total number of routes in the following states: All levels • active • holddown (routes in that are pending state before being declared inactive) • hidden (the routes are not used because of a routing policy) Prefix Destination prefix. none brief MED Multiple exit discriminator value included in the route. none brief destination-prefix (entry, announced) Destination prefix. The entry value is the number of routes for this destination, and the announced value is the number of routes being announced for this destination. detail extensive Route Distinguisher 64-bit prefix added to IP subnets to make them unique. detail extensive Label-Base, range First label in a block of labels and label block size. A remote PE routing device uses this first label when sending traffic toward the advertising PE routing device. detail extensive VPN Label Virtual private network (VPN) label. Packets are sent between CE and PE routing devices by advertising VPN labels. VPN labels transit over either a Resource Reservation Protocol (RSVP) or a Label Distribution Protocol (LDP) label-switched path (LSP) tunnel. detail extensive Next hop Next hop to the destination. An angle bracket (>) indicates that the route is the selected route. All levels Localpref or Lclpref Local preference value included in the route. All levels 2001 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 250: show route receive-protocol Output Fields (continued) Field Name Field Description Level of Output AS path Autonomous system (AS) path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: All levels • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. When AS path numbers are included in the route, the format is as follows: • [ ]—Brackets enclose the number that precedes the AS path. This number represents the number of ASs present in the AS path, when calculated as defined in RFC 4271. This value is used the AS-path merge process, as defined in RFC 4893. • [ ]—If more than one AS number is configured on the router, or if AS path prepending is configured, brackets enclose the local AS number associated with the AS path. • { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order. • ( )—Parentheses enclose a confederation. • ( [ ] )—Parentheses and brackets enclose a confederation set. Cluster list (For route reflected output only) Cluster ID sent by the route reflector. detail extensive Originator ID (For route reflected output only) Address of routing device that originally sent the route to the route reflector. detail extensive Communities Community path attribute for the route. See the Output Field table in the show route detail command for all possible values for this field. detail extensive Attrset AS Number, local preference, and path of the AS that originated the route. These values are stored in the Attrset attribute at the originating routing device. detail extensive Layer2-info: encaps Layer 2 encapsulation (for example, VPLS). detail extensive control flags Control flags: none or Site Down. detail extensive mtu Maximum transmission unit (MTU) of the Layer 2 circuit. detail extensive show route receive-protocol bgp user@host> show route receive-protocol bgp 10.255.245.215 inet.0: 28 destinations, Prefix 10.22.1.0/24 10.22.2.0/24 show route receive-protocol bgp extensive 2002 33 routes (27 active, 0 holddown, 1 hidden) Next hop MED Lclpref AS path 10.255.245.215 0 100 I 10.255.245.215 0 100 I user@host> show route receive-protocol bgp 10.255.245.63 extensive inet.0: 244 destinations, 244 routes (243 active, 0 holddown, 1 hidden) Prefix Next hop MED Lclpref AS path 1.1.1.0/24 (1 entry, 1 announced) Chapter 74: Operational Commands for Layer 3 Protocols Next hop: 10.0.50.3 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.45 165.3.0.0/16 (1 entry, 1 announced) Next hop: 111.222.5.254 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.68 165.4.0.0/16 (1 entry, 1 announced) Next hop: 111.222.5.254 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.45 195.1.2.0/24 (1 entry, 1 announced) Next hop: 111.222.5.254 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.68 inet.2: 63 destinations, 63 routes (63 active, 0 holddown, 0 hidden) Prefix Next hop MED Lclpref AS path inet.3: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden) Prefix Next hop MED Lclpref AS path iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Next hop MED Lclpref AS path mpls.0: 48 destinations, 48 routes (48 active, 0 holddown, 0 hidden) show route receive-protocol bgp extensive user@host> show route receive–protocol bgp 207.17.136.192 table inet.0 66.117.68.0/24 extensive inet.0: 227315 destinations, 227316 routes (227302 active, 0 holddown, 13 hidden) * 66.117.63.0/24 (1 entry, 1 announced) Nexthop: 207.17.136.29 Localpref: 100 AS path: AS2 PA[6]: 14203 2914 3356 29748 33437 AS_TRANS AS path: AS4 PA[2]: 33437 393219 AS path: Merged[6]: 14203 2914 3356 29748 33437 393219 I Communities: 2914:420 2003 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route receive-protocol bgp detail (Layer 2 VPN) user@host> show route receive-protocol bgp 10.255.14.171 detail inet.0: 68 destinations, 68 routes (67 active, 0 holddown, 1 hidden) Prefix Nexthop MED Lclpref AS path inet.3: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path mpls.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path frame-vpn.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.245.35:1:5:1/96 (1 entry, 1 announced) Route Distinguisher: 10.255.245.35:1 Label-base : 800000, range : 4, status-vector : 0x0 Nexthop: 10.255.245.35 Localpref: 100 AS path: I Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY, control flags: 0, mtu: 0 bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.245.35:1:5:1/96 (1 entry, 0 announced) Route Distinguisher: 10.255.245.35:1 Label-base : 800000, range : 4, status-vector : 0x0 Nexthop: 10.255.245.35 Localpref: 100 AS path: I Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY, control flags:0, mtu: 0 show route receive-protocol bgp extensive (Layer 2 VPN) user@host> show route receive-protocol bgp 10.255.14.171 extensive inet.0: 68 destinations, 68 routes (67 active, 0 holddown, 1 hidden) Prefix Nexthop MED Lclpref AS path inet.3: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path mpls.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path frame-vpn.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.245.35:1:5:1/96 (1 entry, 1 announced) Route Distinguisher: 10.255.245.35:1 Label-base : 800000, range : 4, status-vector : 0x0 Nexthop: 10.255.245.35 Localpref: 100 AS path: I Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY, control flags:0, mtu: 0 bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.245.35:1:5:1/96 (1 entry, 0 announced) Route Distinguisher: 10.255.245.35:1 Label-base : 800000, range : 4, status-vector : 0x0 Nexthop: 10.255.245.35 Localpref: 100 AS path: I Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY, control flags:0, mtu: 0 2004 Chapter 74: Operational Commands for Layer 3 Protocols show route receive-protocol bgp (Layer 3 VPN) user@host> show route receive-protocol bgp 10.255.14.171 inet.0: 33 destinations, 33 routes (32 active, 0 holddown, 1 hidden) Prefix Nexthop MED Lclpref AS path inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path VPN-A.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.14.175/32 10.255.14.171 100 2 I 10.255.14.179/32 10.255.14.171 2 100 I VPN-B.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.14.175/32 10.255.14.171 100 2 I 10.255.14.177/32 10.255.14.171 100 I iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path mpls.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path 10.255.14.171:300:10.255.14.177/32 10.255.14.171 100 I 10.255.14.171:100:10.255.14.179/32 10.255.14.171 2 100 I 10.255.14.171:200:10.255.14.175/32 10.255.14.171 100 2 I show route receive-protocol bgp detail (Layer 3 VPN) user@host> show route receive-protocol bgp 10.255.14.174 detail inet.0: 16 destinations, 17 routes (15 active, 0 holddown, 1 hidden) inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) vpna.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) * 10.49.0.0/30 (1 entry, 1 announced) Route Distinguisher: 10.255.14.176:2 VPN Label: 101264 Nexthop: 10.255.14.174 Localpref: 100 AS path: I Communities: target:200:100 AttrSet AS: 100 Localpref: 100 AS path: I * 10.255.14.172/32 (1 entry, 1 announced) Route Distinguisher: 10.255.14.176:2 VPN Label: 101280 Nexthop: 10.255.14.174 Localpref: 100 AS path: I Communities: target:200:100 AttrSet AS: 100 Localpref: 100 AS path: I iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) * 10.255.14.174:2:10.49.0.0/30 (1 entry, 0 announced) Route Distinguisher: 10.255.14.174:2 VPN Label: 101264 Nexthop: 10.255.14.174 Localpref: 100 AS path: I Communities: target:200:100 2005 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS AttrSet AS: 100 Localpref: 100 AS path: I * 10.255.14.174:2:10.255.14.172/32 (1 entry, 0 announced) Route Distinguisher: 10.255.14.174:2 VPN Label: 101280 Nexthop: 10.255.14.174 Localpref: 100 AS path: I Communities: target:200:100 AttrSet AS: 100 Localpref: 100 AS path: I inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) show route receive-protocol bgp extensive (Layer 3 VPN) 2006 user@host> show route receive-protocol bgp 10.255.245.63 extensive inet.0: 244 destinations, 244 routes (243 active, 0 holddown, 1 hidden) Prefix Nexthop MED Lclpref AS path 1.1.1.0/24 (1 entry, 1 announced) Nexthop: 10.0.50.3 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.45 165.3.0.0/16 (1 entry, 1 announced) Nexthop: 111.222.5.254 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.68 165.4.0.0/16 (1 entry, 1 announced) Nexthop: 111.222.5.254 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.45 195.1.2.0/24 (1 entry, 1 announced) Nexthop: 111.222.5.254 Localpref: 100 AS path: I Cluster list: 10.2.3.1 Originator ID: 10.255.245.68 inet.2: 63 destinations, 63 routes (63 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path inet.3: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path mpls.0: 48 destinations, 48 routes (48 active, 0 holddown, 0 hidden) Chapter 74: Operational Commands for Layer 3 Protocols show route resolution Syntax Syntax (J-EX Series Switch) Release Information Description Options show route resolution
show route resolution
Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the next-hop resolution database. This database provides for recursive resolution of next hops through other prefixes in the routing table. none—Display standard information about all entries in the next-hop resolution database. brief | detail | extensive | summary—(Optional) Display the specified level of output. index index—(Optional) Show the index of the resolution tree. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. prefix network/destination-prefix—(Optional) Display database entries for the specified address. table routing-table-name—(Optional) Display information about a particular routing table (for example, inet.0) where policy-based export is currently enabled. (For information about the different types of routing tables, see the Junos OS Routing Protocols Configuration Guide.) unresolved—(Optional) Display routes that could not be resolved. Required Privilege Level List of Sample Output view show route resolution detail on page 2008 show route resolution summary on page 2009 show route resolution unresolved on page 2009 2007 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output Fields Table 251 on page 2008 describes the output fields for the show route resolution command. Output fields are listed in the approximate order in which they appear. Table 251: show route resolution Output Fields show route resolution detail 2008 Field Name Field Description routing-table-name Name of the routing table whose prefixes are resolved using the entries in the route resolution database. For routing table groups, this is the name of the primary routing table whose prefixes are resolved using the entries in the route resolution database. Tree index Tree index identifier. Nodes Number of nodes in the tree. Reference count Number of references made to the next hop. Contributing routing tables Routing tables used for next-hop resolution. Originating RIB Name of the routing table whose active route was used to determine the forwarding next-hop entry in the resolution database. For example, in the case of inet.0 resolving via inet.0 and inet.3, this field indicates which routing table, inet.0 or inet.3, provided the best path for a particular prefix. Metric Metric associated with the forwarding next hop. Node path count Number of nodes in the path. Forwarding next hops Number of forwarding next hops. The forwarding next hop is the network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it. user@host> show route resolution detail Tree Index: 1, Nodes 0, Reference Count 1 Contributing routing tables: inet.3 Tree Index: 2, Nodes 23, Reference Count 1 Contributing routing tables: inet.0 inet.3 10.10.0.0/16 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 10.31.1.0/30 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 10.31.1.1/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 0 10.31.1.4/30 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 10.31.1.5/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 0 10.31.2.0/30 Originating RIB: inet.0 Chapter 74: Operational Commands for Layer 3 Protocols Metric: 2 Node path count: 1 Forwarding nexthops: 2 10.31.11.0/24 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 show route resolution summary user@host> show route resolution summary Tree Index: 1, Nodes 24, Reference Count 1 Contributing routing tables: :voice.inet.0 :voice.inet.3 Tree Index: 2, Nodes 2, Reference Count 1 Contributing routing tables: inet.3 Tree Index: 3, Nodes 43, Reference Count 1 Contributing routing tables: inet.0 inet.3 show route resolution unresolved user@host> show route resolution unresolved Tree Index 1 vt-3/2/0.32769.0 /16 Protocol Nexthop: 10.255.71.238 Push 800000 Indirect nexthop: 0 vt-3/2/0.32772.0 /16 Protocol Nexthop: 10.255.70.103 Push 800008 Indirect nexthop: 0 Tree Index 2 2009 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route snooping Syntax Release Information Description Options show route snooping
Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the routing table that were learned from snooping. none—Display the entries in the routing table that were learned from snooping. brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. all—(Optional) Display all entries, including hidden entries. best address/prefix—(Optional) Display the longest match for the provided address and optional prefix. exact address/prefix—(Optional) Display exact matches for the provided address and optional prefix. range prefix-range—(Optional) Display information for the provided address range. summary—(Optional) Display route snooping summary statisitics. table table-name—(Optional) Display information for the named table. Required Privilege Level List of Sample Output Output Fields show route snooping detail 2010 view show route snooping detail on page 2010 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route snooping detail __+domainAll__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 224.0.0.2/32 (1 entry, 1 announced) *IGMP Preference: 0 Next hop type: MultiRecv Next-hop reference count: 4 State: Age: 2:24 Task: IGMP Announcement bits (1): 0-KRT AS path: I Chapter 74: Operational Commands for Layer 3 Protocols 224.0.0.22/32 (1 entry, 1 announced) *IGMP Preference: 0 Next hop type: MultiRecv Next-hop reference count: 4 State: Age: 2:24 Task: IGMP Announcement bits (1): 0-KRT AS path: I __+domainAll__.inet.1: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden) 224.0.0.0.0.0.0.0/24 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4), Next hop index: 1048584 Next-hop reference count: 4 State: Age: 2:24 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.2.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:13 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.3.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.4.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:17 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.5.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 1:58 Task: MC Announcement bits (1): 0-KRT AS path: I 2011 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 225.0.0.6.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:14 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.7.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:12 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.9.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:13 Task: MC Announcement bits (1): 0-KRT AS path: I 225.0.0.10.11.11.11.100.3.9.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 226.0.0.1.11.11.11.100.3.10.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:09 Task: MC Announcement bits (1): 0-KRT AS path: I 226.0.0.2.11.11.11.100.3.10.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 8 Task: MC Announcement bits (1): 0-KRT AS path: I 2012 Chapter 74: Operational Commands for Layer 3 Protocols 226.0.0.4.11.11.11.100.3.10.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:10 Task: MC Announcement bits (1): 0-KRT AS path: I 226.0.0.8.11.11.11.100.3.10.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:12 Task: MC Announcement bits (1): 0-KRT AS path: I 226.0.0.10.11.11.11.100.3.10.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 1:56 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.1.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:10 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.2.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:13 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.3.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:16 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.4.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) 2013 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.5.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 1:57 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.7.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 1:57 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.8.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:10 Task: MC Announcement bits (1): 0-KRT AS path: I 227.0.0.10.11.11.11.100.3.11.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 228.0.0.1.11.11.11.100.3.12.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:09 Task: MC Announcement bits (1): 0-KRT AS path: I 228.0.0.2.11.11.11.100.3.12.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 2014 Chapter 74: Operational Commands for Layer 3 Protocols Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:18 Task: MC Announcement bits (1): 0-KRT AS path: I 228.0.0.7.11.11.11.100.3.12.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:11 Task: MC Announcement bits (1): 0-KRT AS path: I 228.0.0.8.11.11.11.100.3.12.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:17 Task: MC Announcement bits (1): 0-KRT AS path: I 228.0.0.9.11.11.11.100.3.12.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 8 Task: MC Announcement bits (1): 0-KRT AS path: I 228.0.0.10.11.11.11.100.3.12.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:12 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.3.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:09 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.4.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) 2015 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Next-hop reference count: 113 State: Age: 2:12 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.5.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 9 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.6.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.7.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.8.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:15 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.9.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 State: Age: 2:14 Task: MC Announcement bits (1): 0-KRT AS path: I 229.0.0.10.11.11.11.100.3.13.0.0/80 (1 entry, 1 announced) *Multicast Preference: 180 Next hop type: Multicast (IPv4) Next-hop reference count: 113 2016 Chapter 74: Operational Commands for Layer 3 Protocols State: Age: 2:13 Task: MC Announcement bits (1): 0-KRT AS path: I 2017 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route source-gateway Syntax Syntax (J-EX Series Switch) Release Information show route source-gateway address show route source-gateway address Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the entries in the routing table that were learned from a particular address. The Source field in the show route detail command output lists the source for each route, if known. Options brief | detail | extensive | terse—(Optional) Display the specified level of output. If you do not specify a level of output, the system defaults to brief. address—IP address of the system. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields show route source-gateway view show route source-gateway on page 2018 show route source-gateway detail on page 2019 show route source-gateway extensive on page 2021 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> show route source-gateway 10.255.70.103 inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden) Restart Complete inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) Restart Complete private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 2018 Chapter 74: Operational Commands for Layer 3 Protocols green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.255.70.103:1:3:1/96 *[BGP/170] 12:12:24, localpref 100, from 10.255.70.103 AS path: I > via so-0/3/0.0, label-switched-path green-r1-r3 red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.255.70.103:2:3:1/96 *[BGP/170] 12:12:24, localpref 0, from 10.255.70.103 AS path: I > via so-0/3/0.0, label-switched-path green-r1-r3 bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 10.255.70.103:1:3:1/96 *[BGP/170] 12:12:24, localpref 100, from 10.255.70.103 AS path: I > via so-0/3/0.0, label-switched-path green-r1-r3 10.255.70.103:2:3:1/96 *[BGP/170] 12:12:24, localpref 0, from 10.255.70.103 AS path: I > via so-0/3/0.0, label-switched-path green-r1-r3 show route source-gateway detail user@host> show route source-gateway 10.255.70.103 detail inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden) Restart Complete inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) Restart Complete green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103:1:3:1/96 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.70.103:1 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 2019 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Age: 12:14:00 Metric2: 1 Task: BGP_69.10.255.70.103+179 Announcement bits (1): 0-green-l2vpn AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8 Localpref: 100 Router ID: 10.255.70.103 Primary Routing Table bgp.l2vpn.0 red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103:2:3:1/96 (1 entry, 1 announced) *BGP Preference: 170/-1 Route Distinguisher: 10.255.70.103:2 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:14:00 Metric2: 1 Task: BGP_69.10.255.70.103+179 Announcement bits (1): 0-red-l2vpn AS path: I Communities: target:11111:2 Layer2-info: encaps:VPLS, control flags:Site-Down, mtu: 0 Label-base: 800016, range: 8 Localpref: 0 Router ID: 10.255.70.103 Primary Routing Table bgp.l2vpn.0 bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103:1:3:1/96 (1 entry, 0 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.70.103:1 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:14:00 Metric2: 1 Task: BGP_69.10.255.70.103+179 AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8 Localpref: 100 Router ID: 10.255.70.103 Secondary Tables: green.l2vpn.0 10.255.70.103:2:3:1/96 (1 entry, 0 announced) *BGP Preference: 170/-1 Route Distinguisher: 10.255.70.103:2 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 2020 Chapter 74: Operational Commands for Layer 3 Protocols Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:14:00 Metric2: 1 Task: BGP_69.10.255.70.103+179 AS path: I Communities: target:11111:2 Layer2-info: encaps:VPLS, control flags:Site-Down, mtu: 0 Label-base: 800016, range: 8 Localpref: 0 Router ID: 10.255.70.103 Secondary Tables: red.l2vpn.0 show route source-gateway extensive user@host> show route source-gateway 10.255.70.103 extensive inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden) Restart Complete inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) Restart Complete green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103:1:3:1/96 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.70.103:1 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:15:24 Metric2: 1 Task: BGP_69.10.255.70.103+179 Announcement bits (1): 0-green-l2vpn AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8 Localpref: 100 Router ID: 10.255.70.103 Primary Routing Table bgp.l2vpn.0 red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103:2:3:1/96 (1 entry, 1 announced) *BGP Preference: 170/-1 Route Distinguisher: 10.255.70.103:2 Next-hop reference count: 7 2021 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:15:24 Metric2: 1 Task: BGP_69.10.255.70.103+179 Announcement bits (1): 0-red-l2vpn AS path: I Communities: target:11111:2 Layer2-info: encaps:VPLS, control flags:Site-Down, mtu: 0 Label-base: 800016, range: 8 Localpref: 0 Router ID: 10.255.70.103 Primary Routing Table bgp.l2vpn.0 bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete 10.255.70.103:1:3:1/96 (1 entry, 0 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.70.103:1 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:15:24 Metric2: 1 Task: BGP_69.10.255.70.103+179 AS path: I Communities: target:11111:1 Layer2-info: encaps:VPLS, control flags:, mtu: 0 Label-base: 800008, range: 8 Localpref: 100 Router ID: 10.255.70.103 Secondary Tables: green.l2vpn.0 Indirect next hops: 1 Protocol next hop: 10.255.70.103 Metric: 2 Indirect next hop: 2 no-forward Indirect path forwarding next hops: 1 Next hop: via so-0/3/0.0 weight 0x1 10.255.70.103/32 Originating RIB: inet.3 Metric: 2 Node path count: 1 Forwarding nexthops: 1 Nexthop: via so-0/3/0.0 10.255.70.103:2:3:1/96 (1 entry, 0 announced) *BGP Preference: 170/-1 Route Distinguisher: 10.255.70.103:2 Next-hop reference count: 7 Source: 10.255.70.103 Protocol next hop: 10.255.70.103 Indirect next hop: 2 no-forward State: Local AS: 69 Peer AS: 69 Age: 12:15:24 Metric2: 1 Task: BGP_69.10.255.70.103+179 AS path: I Communities: target:11111:2 Layer2-info: encaps:VPLS, control flags:Site-Down, 2022 Chapter 74: Operational Commands for Layer 3 Protocols mtu: 0 Label-base: 800016, range: 8 Localpref: 0 Router ID: 10.255.70.103 Secondary Tables: red.l2vpn.0 Indirect next hops: 1 Protocol next hop: 10.255.70.103 Metric: 2 Indirect next hop: 2 no-forward Indirect path forwarding next hops: 1 Next hop: via so-0/3/0.0 weight 0x1 10.255.70.103/32 Originating RIB: inet.3 Metric: 2 Node path count: 1 Forwarding nexthops: 1 Nexthop: via so-0/3/0.0 2023 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route summary Syntax Syntax (J-EX Series Switch) Release Information Description Options show route summary show route summary Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display summary statistics about the entries in the routing table. none—Display summary statistics about the entries in the routing table. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show route summary on page 2025 Table 252 on page 2024 lists the output fields for the show route summary command. Output fields are listed in the approximate order in which they appear. Table 252: show route summary Output Fields Field Name Field Description routing-table-name Name of the routing table (for example, inet.0). destinations Number of destinations for which there are routes in the routing table. routes Number of routes in the routing table: • active—Number of routes that are active. • holddown—Number of routes that are in the hold-down state before being declared inactive. • 2024 hidden—Number of routes not used because of routing policy. Direct Routes on the directly connected network. Local Local routes. protocol-name Name of the protocol from which the route was learned. For example, OSPF, RSVP, and Static. Chapter 74: Operational Commands for Layer 3 Protocols show route summary user@host> show route summary Autonomous system number: 69 Router ID: 10.255.71.52 Maximum-ECMP: 32 inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden) Restart Complete Direct: 6 routes, 5 active Local: 4 routes, 4 active OSPF: 5 routes, 4 active Static: 7 routes, 7 active IGMP: 1 routes, 1 active PIM: 2 routes, 2 active inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Restart Complete RSVP: 2 routes, 2 active iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete Direct: 1 routes, 1 active mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden) Restart Complete MPLS: 3 routes, 3 active VPLS: 4 routes, 2 active inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) Restart Complete Direct: 2 routes, 2 active PIM: 2 routes, 2 active MLD: 1 routes, 1 active green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete BGP: 2 routes, 2 active L2VPN: 2 routes, 2 active red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) Restart Complete BGP: 2 routes, 2 active L2VPN: 1 routes, 1 active bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) Restart Complete BGP: 4 routes, 4 active 2025 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show route table Syntax Syntax (J-EX Series Switch) Release Information Description Options show route table routing-table-name show route table routing-table-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the route entries in a particular routing table. brief | detail | extensive | terse—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. routing-table-name—Display information about a particular routing table (for example, inet.0) where policy-based export is currently enabled. (For information about the different types of routing tables, see the Junos OS Routing Protocols Configuration Guide.) Required Privilege Level Related Documentation List of Sample Output Output Fields 2026 view • show route summary on page 2024 show route table bgp.l2.vpn on page 2027 show route table bgp.l3vpn.0 on page 2027 show route table bgp.l3vpn.0 detail on page 2027 show route table inet.0 on page 2028 show route table inet6.0 on page 2029 show route table inet6.3 on page 2029 show route table l2circuit.0 on page 2029 show route table mpls on page 2030 show route table mpls extensive on page 2030 show route table mpls.0 on page 2030 show route table vpls_1 detail on page 2031 show route table vpn-a on page 2031 show route table vpn-a.mdt.0 on page 2031 show route table VPN-AB.inet.0 on page 2031 show route table VPN_blue.mvpn-inet6.0 on page 2032 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. Chapter 74: Operational Commands for Layer 3 Protocols show route table bgp.l2.vpn user@host> show route table bgp.l2.vpn bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 192.168.24.1:1:4:1/96 *[BGP/170] 01:08:58, localpref 100, from 192.168.24.1 AS path: I > to 10.0.16.2 via fe-0/0/1.0, label-switched-path am show route table bgp.l3vpn.0 user@host> show route table bgp.l3vpn.0 bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.255.71.15:100:10.255.71.17/32 *[BGP/170] 00:03:59, MED 1, localpref 100, from 10.255.71.15 AS path: I > via so-2/1/0.0, Push 100020, Push 100011(top) 10.255.71.15:200:10.255.71.18/32 *[BGP/170] 00:03:59, MED 1, localpref 100, from 10.255.71.15 AS path: I > via so-2/1/0.0, Push 100021, Push 100011(top) show route table bgp.l3vpn.0 detail user@host> show route table bgp.l3vpn.0 detail bgp.l3vpn.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden) 10.255.245.12:1:4.0.0.0/8 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.245.12:1 Source: 10.255.245.12 Next hop: 192.168.208.66 via fe-0/0/0.0, selected Label operation: Push 182449 Protocol next hop: 10.255.245.12 Push 182449 Indirect next hop: 863a630 297 State: Local AS: 35 Peer AS: 35 Age: 12:19 Metric2: 1 Task: BGP_35.10.255.245.12+179 Announcement bits (1): 0-BGP.0.0.0.0+179 AS path: 30 10458 14203 2914 3356 I (Atomic) Aggregator: 3356 4.68.0.11 Communities: 2914:420 target:11111:1 origin:56:78 VPN Label: 182449 Localpref: 100 Router ID: 10.255.245.12 10.255.245.12:1:4.17.225.0/24 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.245.12:1 Source: 10.255.245.12 Next hop: 192.168.208.66 via fe-0/0/0.0, selected Label operation: Push 182465 Protocol next hop: 10.255.245.12 Push 182465 Indirect next hop: 863a8f0 305 State: Local AS: 35 Peer AS: 35 Age: 12:19 Metric2: 1 2027 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Task: BGP_35.10.255.245.12+179 Announcement bits (1): 0-BGP.0.0.0.0+179 AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 6496 I Communities: 2914:410 target:12:34 target:11111:1 origin:12:34 VPN Label: 182465 Localpref: 100 Router ID: 10.255.245.12 10.255.245.12:1:4.17.226.0/23 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.245.12:1 Source: 10.255.245.12 Next hop: 192.168.208.66 via fe-0/0/0.0, selected Label operation: Push 182465 Protocol next hop: 10.255.245.12 Push 182465 Indirect next hop: 86bd210 330 State: Local AS: 35 Peer AS: 35 Age: 12:19 Metric2: 1 Task: BGP_35.10.255.245.12+179 Announcement bits (1): 0-BGP.0.0.0.0+179 AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 6496 I Communities: 2914:410 target:12:34 target:11111:1 origin:12:34 VPN Label: 182465 Localpref: 100 Router ID: 10.255.245.12 10.255.245.12:1:4.17.251.0/24 (1 entry, 1 announced) *BGP Preference: 170/-101 Route Distinguisher: 10.255.245.12:1 Source: 10.255.245.12 Next hop: 192.168.208.66 via fe-0/0/0.0, selected Label operation: Push 182465 Protocol next hop: 10.255.245.12 Push 182465 Indirect next hop: 86bd210 330 State: Local AS: 35 Peer AS: 35 Age: 12:19 Metric2: 1 Task: BGP_35.10.255.245.12+179 Announcement bits (1): 0-BGP.0.0.0.0+179 AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 6496 I Communities: 2914:410 target:12:34 target:11111:1 origin:12:34 VPN Label: 182465 Localpref: 100 show route table inet.0 user@host> show route table inet.0 inet.0: 12 destinations, 12 routes (11 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 0.0.0.0/0 1.0.0.1/32 1.0.0.2/32 2028 *[Static/5] 00:51:57 > to 111.222.5.254 via fxp0.0 *[Direct/0] 00:51:58 > via at-5/3/0.0 *[Local/0] 00:51:58 Local Chapter 74: Operational Commands for Layer 3 Protocols 12.12.12.21/32 13.13.13.13/32 13.13.13.14/32 13.13.13.21/32 13.13.13.22/32 127.0.0.1/32 111.222.5.0/24 111.222.5.81/32 show route table inet6.0 *[Local/0] 00:51:57 Reject *[Direct/0] 00:51:58 > via t3-5/2/1.0 *[Local/0] 00:51:58 Local *[Local/0] 00:51:58 Local *[Direct/0] 00:33:59 > via t3-5/2/0.0 [Direct/0] 00:51:58 > via lo0.0 *[Direct/0] 00:51:58 > via fxp0.0 *[Local/0] 00:51:58 Local user@host> show route table inet6.0 inet6.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Route, * = Both fec0:0:0:3::/64 *[Direct/0] 00:01:34 >via fe-0/1/0.0 fec0:0:0:3::/128 *[Local/0] 00:01:34 >Local fec0:0:0:4::/64 *[Static/5] 00:01:34 >to fec0:0:0:3::ffff via fe-0/1/0.0 show route table inet6.3 user@router> show route table inet6.3 inet6.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both ::10.255.245.195/128 *[LDP/9] 00:00:22, metric 1 > via so-1/0/0.0 ::10.255.245.196/128 *[LDP/9] 00:00:08, metric 1 > via so-1/0/0.0, Push 100008 show route table l2circuit.0 user@host> show route table l2circuit.0 l2circuit.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.1.1.195:NoCtrlWord:1:1:Local/96 *[L2CKT/7] 00:50:47 > via so-0/1/2.0, Push via so-0/1/3.0, Push 10.1.1.195:NoCtrlWord:1:1:Remote/96 *[LDP/9] 00:50:14 Discard 10.1.1.195:CtrlWord:1:2:Local/96 *[L2CKT/7] 00:50:47 > via so-0/1/2.0, Push via so-0/1/3.0, Push 10.1.1.195:CtrlWord:1:2:Remote/96 100049 100049 100049 100049 2029 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS *[LDP/9] 00:50:14 Discard show route table mpls user@host> show route table mpls mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0 1 2 1024 show route table mpls extensive show route table mpls.0 user@host> show route table mpls extensive 100000 (1 entry, 1 announced) TSI: KRT in-kernel 100000 /36 -> {so-1/0/0.0} *LDP Preference: 9 Next hop: via so-1/0/0.0, selected Pop State: Age: 29:50 Metric: 1 Task: LDP Announcement bits (1): 0-KRT AS path: I Prefixes bound to route: 10.0.0.194/32 user@host> show route table mpls.0 mpls.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0 1 2 100000 100001 100002 100002(S=0) 100003 100004 so-0/1/0.1 so-0/1/0.2 2030 *[MPLS/0] 00:13:55, metric 1 Receive *[MPLS/0] 00:13:55, metric 1 Receive *[MPLS/0] 00:13:55, metric 1 Receive *[VPN/0] 00:04:18 to table red.inet.0, Pop *[MPLS/0] 00:45:09, metric 1 Receive *[MPLS/0] 00:45:09, metric 1 Receive *[MPLS/0] 00:45:09, metric 1 Receive *[L2VPN/7] 00:43:04 > via so-0/1/0.1, Pop *[L2VPN/7] 00:43:03 > via so-0/1/0.2, Pop Offset: 4 *[LDP/9] 00:43:22, metric 1 via so-0/1/2.0, Pop > via so-0/1/3.0, Pop *[LDP/9] 00:43:22, metric 1 via so-0/1/2.0, Pop > via so-0/1/3.0, Pop *[LDP/9] 00:43:22, metric 1 > via so-0/1/2.0, Swap 100002 via so-0/1/3.0, Swap 100002 *[LDP/9] 00:43:16, metric 1 via so-0/1/2.0, Swap 100049 > via so-0/1/3.0, Swap 100049 *[L2VPN/7] 00:43:04 > via so-0/1/2.0, Push 100001, Push 100049(top) via so-0/1/3.0, Push 100001, Push 100049(top) *[L2VPN/7] 00:43:03 Chapter 74: Operational Commands for Layer 3 Protocols via so-0/1/2.0, Push 100000, Push 100049(top) Offset: -4 > via so-0/1/3.0, Push 100000, Push 100049(top) Offset: -4 show route table vpls_1 detail user@host> show route table vpls_1 detail vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete 1.1.1.11:1000:1:1/96 (1 entry, 1 announced) *L2VPN Preference: 170/-1 Receive table: vpls_1.l2vpn.0 Next-hop reference count: 2 State: Age: 4:29:47 Metric2: 1 Task: vpls_1-l2vpn Announcement bits (1): 1-BGP.0.0.0.0+179 AS path: I Communities: Layer2-info: encaps:VPLS, control flags:Site-Down Label-base: 800000, range: 8, status-vector: 0xFF show route table vpn-a user@host> show route table vpn-a vpn-a.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 192.168.16.1:1:1:1/96 *[VPN/7] 05:48:27 Discard 192.168.24.1:1:2:1/96 *[BGP/170] 00:02:53, localpref 100, from 192.168.24.1 AS path: I > to 10.0.16.2 via fe-0/0/1.0, label-switched-path am 192.168.24.1:1:3:1/96 *[BGP/170] 00:02:53, localpref 100, from 192.168.24.1 AS path: I > to 10.0.16.2 via fe-0/0/1.0, label-switched-path am show route table vpn-a.mdt.0 user@host> show route table vpn-a.mdt.0 vpn-a.mdt.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1:1:0:10.255.14.216:232.1.1.1/144 *[MVPN/70] 01:23:05, metric2 1 Indirect 1:1:1:10.255.14.218:232.1.1.1/144 *[BGP/170] 00:57:49, localpref 100, from 10.255.14.218 AS path: I > via so-0/0/0.0, label-switched-path r0e-to-r1 1:1:2:10.255.14.217:232.1.1.1/144 *[BGP/170] 00:57:49, localpref 100, from 10.255.14.217 AS path: I > via so-0/0/1.0, label-switched-path r0-to-r2 show route table VPN-AB.inet.0 user@host> show route table VPN-AB.inet.0 VPN-AB.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.39.1.0/30 10.39.1.4/30 10.39.1.6/32 *[OSPF/10] 00:07:24, metric 1 > via so-7/3/1.0 *[Direct/0] 00:08:42 > via so-5/1/0.0 *[Local/0] 00:08:46 2031 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 10.255.71.16/32 10.255.71.17/32 10.255.71.15 10.255.71.18/32 10.255.71.15 10.255.245.245/32 10.255.245.246/32 show route table VPN_blue.mvpn-inet6.0 Local *[Static/5] 00:07:24 > via so-2/0/0.0 *[BGP/170] 00:07:24, MED 1, localpref 100, from AS path: I > via so-2/1/0.0, Push 100020, Push 100011(top) *[BGP/170] 00:07:24, MED 1, localpref 100, from AS path: I > via so-2/1/0.0, Push 100021, Push 100011(top) *[BGP/170] 00:08:35, localpref 100 AS path: 2 I > to 10.39.1.5 via so-5/1/0.0 *[OSPF/10] 00:07:24, metric 1 > via so-7/3/1.0 user@host> show route table VPN_blue.mvpn-inet6.0 vpn_blue.mvpn-inet6.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1:10.255.2.202:65535:10.255.2.202/432 *[BGP/170] 00:02:37, localpref 100, from 10.255.2.202 AS path: I > via so-0/1/3.0 1:10.255.2.203:65535:10.255.2.203/432 *[BGP/170] 00:02:37, localpref 100, from 10.255.2.203 AS path: I > via so-0/1/0.0 1:10.255.2.204:65535:10.255.2.204/432 *[MVPN/70] 00:57:23, metric2 1 Indirect 5:10.255.2.202:65535:128:::192.168.90.2:128:ffff::1/432 *[BGP/170] 00:02:37, localpref 100, from 10.255.2.202 AS path: I > via so-0/1/3.0 6:10.255.2.203:65535:65000:128:::10.12.53.12:128:ffff::1/432 *[PIM/105] 00:02:37 Multicast (IPv6) 7:10.255.2.202:65535:65000:128:::192.168.90.2:128:ffff::1/432 *[MVPN/70] 00:02:37, metric2 1 Indirect 2032 Chapter 74: Operational Commands for Layer 3 Protocols show route terse Syntax show route terse Syntax (J-EX Series Switch) show route terse Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display a high-level summary of the routes in the routing table. Options none—Display a high-level summary of the routes in the routing table. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level view List of Sample Output show route terse on page 2035 Output Fields Table 253 on page 2033 describes the output fields for the show route terse command. Output fields are listed in the approximate order in which they appear. Table 253: show route terse Output Fields Field Name Field Description routing-table-name Name of the routing table (for example, inet.0). number destinations Number of destinations for which there are routes in the routing table. number routes Number of routes in the routing table and total number of routes in the following states: route key • active (routes that are active) • holddown (routes that are in the pending state before being declared inactive) • hidden (routes that are not used because of a routing policy) Key for the state of the route: • +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table. • - —A hyphen indicates the last active route. • *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route. A Active route. An asterisk (*) indicates this is the active route. Destination Destination of the route. 2033 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 253: show route terse Output Fields (continued) Field Name Field Description P Protocol through which the route was learned: • A—Aggregate • B—BGP • C—CCC • D—Direct • G—GMPLS • I—IS-IS • L—L2CKT, L2VPN, LDP, Local • K—Kernel • M—MPLS, MSDP • O—OSPF • P—PIM • R—RIP, RIPng • S—Static • T—Tunnel Prf Preference value of the route. In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because if has a higher LocalPref value and a lower Preference2 value. Metric 1 First metric value in the route. For routes learned from BGP, this is the MED metric. Metric 2 Second metric value in the route. For routes learned from BGP, this is the IGP metric. Next hop Next hop to the destination. An angle bracket (>) indicates that the route is the selected route. AS path AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated: 2034 • I—IGP. • E—EGP. • ?—Incomplete; typically, the AS path was aggregated. Chapter 74: Operational Commands for Layer 3 Protocols show route terse user@host> show route terse inet.0: 12 destinations, 12 routes (11 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both A * * * * * * * * Destination 0.0.0.0/0 1.0.0.1/32 1.0.0.2/32 12.12.12.21/32 13.13.13.13/32 13.13.13.14/32 13.13.13.21/32 13.13.13.22/32 127.0.0.1/32 * 111.222.5.0/24 * 111.222.5.81/32 * 224.0.0.5/32 P Prf Metric 1 Metric 2 S 5 D 0 L 0 L 0 D 0 L 0 L 0 D 0 D 0 D 0 L 0 O 10 1 Next hop >111.222.5.254 >at-5/3/0.0 Local Reject >t3-5/2/1.0 Local Local >t3-5/2/0.0 >lo0.0 >fxp0.0 Local MultiRecv AS path 2035 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show vrrp Syntax Release Information Description Options show vrrp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information and status about VRRP groups. none—(Same as brief) Display brief status information about all VRRP interfaces. brief | detail | extensive | summary—(Optional) Display the specified level of output. interface interface-name —(Optional) Display information and status about the specified VRRP interface. track interfaces—(Optional) Display information and status about VRRP track interfaces. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Configuring VRRP for IPv6 (CLI Procedure) on page 1452 show vrrp on page 2041 show vrrp brief on page 2041 show vrrp detail (IPv6) on page 2041 show vrrp detail (Route Track) on page 2041 show vrrp extensive on page 2041 show vrrp interface on page 2043 show vrrp summary on page 2044 show vrrp track detail on page 2044 show vrrp track summary on page 2044 Table 254 on page 2036 lists the output fields for the show vrrp command. Output fields are listed in the approximate order in which they appear. Table 254: show vrrp Output Fields Field Name Field Description Level of Output Interface Name of the logical interface. none, brief, extensive, summary Interface index Physical interface index number, which reflects its initialization sequence. extensive Groups Total number of VRRP groups configured on the interface. extensive Active Total number of VRRP groups that are active (that is, whose interface state is either up or down). extensive 2036 Chapter 74: Operational Commands for Layer 3 Protocols Table 254: show vrrp Output Fields (continued) Field Name Field Description Level of Output Interface VRRP PDU statistics Nonerrored statistics for the logical interface: extensive • Advertisement sent—Number of VRRP advertisement protocol data units (PDUs) that the interface has transmitted. • Advertisement received—Number of VRRP advertisement PDUs received by the interface. • Packets received—Number of VRRP packets received for VRRP groups on the interface. • No group match received—Number of VRRP packets received for VRRP groups that do not exist on the interface. Interface VRRP PDU error statistics Errored statistics for the logical interface: • extensive Invalid IPAH next type received—Number of packets received that use the IP Authentication Header protocol (IPAH) and that do not encapsulate VRRP packets. • Invalid VRRP ttl value received—Number of packets received whose IP time- to-live (TTL) value is not 255. • Invalid VRRP version received—Number of packets received whose VRRP version is not 2. • Invalid VRRP pdu type received—Number of packets received whose VRRP PDU type is not 1. • Invalid VRRP authentication type received—Number of packets received whose VRRP authentication is not none, simple, or md5. • Invalid VRRP IP count received—Number of packets received whose VRRP IP count exceeds 8. • Invalid VRRP checksum received—Number of packets received whose VRRP checksum does not match the calculated value. Physical interface Name of the physical interface. detail, extensive Unit Logical unit number. All levels Address Address of the physical interface. none, brief, detail, extensive Index Physical interface index number, which reflects its initialization sequence. detail, extensive SNMP ifIndex SNMP index number for the physical interface. detail, extensive VRRP-Traps Status of VRRP traps: Enabled or Disabled. detail, extensive Type and Address Identifier for the address and the address itself: none, brief, summary • lcl—Configured local interface address. • mas—Address of the master virtual router. This address is displayed only when the local interface is acting as a backup router. • vip—Configured virtual IP addresses. 2037 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 254: show vrrp Output Fields (continued) Field Name Field Description Level of Output Interface state or Int state State of the physical interface: none, brief, extensive, summary • down—The device is present and the link is unavailable. • not present—The interface is configured, but no physical device is present. • unknown—The VRRP process has not had time to query the kernel about the state of the interface. • up—The device is present and the link is established. Group VRRP group number. none, brief, extensive, summary State VRRP state: extensive • backup—The interface is acting as the backup router interface. • bringup—VRRP is just starting, and the physical device is not yet present. • idle—VRRP is configured on the interface and is disabled. This can occur when VRRP is first enabled on an interface whose link is established. • initializing—VRRP is initializing. • master—The interface is acting as the master router interface. • transition—The interface is changing between being the backup and being the master router. Priority Configured VRRP priority for the interface. detail, extensive Advertisement interval Configured VRRP advertisement interval. detail, extensive Authentication type Configured VRRP authentication type: none, simple, or md5. detail, extensive Preempt Whether preemption is allowed on the interface: yes or no. detail, extensive Accept-data mode Whether the interface is configured to accept packets destined for the virtual IP address: yes or no. detail, extensive VIP count Number of virtual IP addresses that have been configured on the interface. detail, extensive VIP List of virtual IP addresses configured on the interface. detail, extensive Advertisement timer Time until the advertisement timer expires. detail, extensive Master router IP address of the interface that is acting as the master. If the VRRP interface is down, the output is N/A. detail, extensive Virtual router uptime Time that the virtual router has been up. detail, extensive Master router uptime Time that the master router has been up. detail, extensive 2038 Chapter 74: Operational Commands for Layer 3 Protocols Table 254: show vrrp Output Fields (continued) Field Name Field Description Level of Output Virtual MAC MAC address associated with the virtual IP address. detail, extensive Tracking Whether tracking is enabled or disabled. detail, extensive Current priority Current operational priority for being the VRRP master. detail, extensive Configured priority Configured base priority for being the VRRP master. detail, extensive Priority hold-time Minimum time interval, in seconds, between successive changes to the current priority. Disabled indicates no minimum interval. detail, extensive Remaining-time (track option only) Displays the time remaining in the priority hold-time interval. detail Interface tracking Whether interface tracking is enabled or disabled. When enabled, the output also displays the number of tracked interfaces. detail extensive Interface/Tracked interface Name of the tracked interface. detail extensive Int state/Interface state Current operational state of the tracked interface: up or down. detail, extensive Int speed/Speed Current operational speed, in bits per second, of the tracked interface. detail, extensive Incurred priority cost Operational priority cost incurred due to the state and speed of this tracked interface. This cost is applied to the configured priority to obtain the current priority. detail, extensive Threshold Speed below which the corresponding priority cost is incurred. In other words, when the speed of the interface drops below the threshold speed, the corresponding priority cost is incurred. detail, extensive An entry of down means that the corresponding priority cost is incurred when the interface is down. Route tracking Whether route tracking is enabled or disabled. When enabled, the output also displays the number of tracked routes. detail, extensive Route count The number of routes being tracked. detail, extensive Route The IP address of the route being tracked. detail, extensive VRF name The VPN routing and forwarding (VRF) routing instance that the tracked route is in. detail, extensive Route state The state of the route being tracked: up, down, or unknown. detail, extensive Priority cost Configured priority cost. This value is incurred when the interface speed drops below the corresponding threshold or when the tracked route goes down. detail, extensive 2039 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 254: show vrrp Output Fields (continued) Field Name Field Description Level of Output Active Whether the threshold is active (*). If the threshold is active, the corresponding priority cost is incurred. detail, extensive Group VRRP PDU statistics Number of VRRP advertisements sent and received by the group. extensive Group VRRP PDU error statistics Errored statistics for the VRRP group: extensive • Bad authentication type received—Number of VRRP PDUs received with an invalid authentication type. The received authentication can be none, simple, or md5 and must be the same for all routers in the VRRP group. • Bad password received—Number of VRRP PDUs received with an invalid key (password). The password for simple authentication must be the same for all routers in the VRRP group • Bad MD5 digest received—Number of VRRP PDUs received for which the MD5 digest computed from the VRRP PDU differs from the digest expected by the VRRP instance configured on the router. • Bad advertisement timer received—Number of VRRP PDUs received with an advertisement time interval that is inconsistent with the one in use among the routers in the VRRP group. • Bad VIP count received—Number of VRRP PDUs whose virtual IP address counts differ from the count that has been configured on the VRRP instance. • Bad VIPADDR received—Number of VRRP PDUs whose virtual IP addresses differ from the list of virtual IP addresses configured on the VRRP instance. Group state transition statistics State transition statistics for the VRRP group: • extensive Idle to master transitions—Number of times that the VRRP instance transitioned from the idle state to the master state. • Idle to backup transitions—Number of times that the VRRP instance transitioned from the idle state to the backup state. • Backup to master transitions—Number of times that the VRRP instance transitioned from the backup state to the master state. • Master to backup transitions—Number of times that the VRRP instance transitioned from the master state to the backup state. VR state VRRP information: • backup—The interface is acting as the backup router interface. • bringup—VRRP is just starting, and the physical device is not yet present. • idle—VRRP is configured on the interface and is disabled. This can occur when none, brief VRRP is first enabled on an interface whose link is established. • initializing—VRRP is initializing. • master—The interface is acting as the master router interface. • transition—The interface is changing between being the backup and being the master router. Timer 2040 VRRP timer information: • A—Time, in seconds, until the advertisement timer expires. • D—Time, in seconds, until the Master is Dead timer expires. none, brief Chapter 74: Operational Commands for Layer 3 Protocols show vrrp user@host> show vrrp Interface State ge-0/0/0.121 up ge-0/0/2.131 up Group 1 1 VR state master master Timer A 1.052 A 0.364 Type lcl Address gec0::12:1:1:1 vip ge80::12:1:1:99 vip lcl gec0::12:1:1:99 gec0::13:1:1:1 vip ge80::13:1:1:99 vip gec0::13:1:1:99 show vrrp brief The output for the show vrrp brief command is identical to that for the show vrrp command. For sample output, see show vrrp on page 2041. show vrrp detail (IPv6) user@host> show vrrp detail Physical interface: ge-0/0/0, Unit: 121, Vlan-id: 212, Address: gec0::12:1:1:1/120 Index: 67, SNMP ifIndex: 45, VRRP-Traps: enabled Interface state: up, Group: 1, State: master Priority: 200, Advertisement interval: 1, Authentication type: none Preempt: yes, Accept-data mode: no, VIP count: 2, VIP: ge80::12:1:1:99, gec0::12:1:1:99 Advertisement timer: 1.121s, Master router: ge80::12:1:1:1 Virtual router uptime: 00:03:47, Master router uptime: 00:03:41 Virtual MAC: 00:00:5e:00:02:01 Tracking: disabled Physical interface: ge-0/0/2, Unit: 131, Vlan-id: 213, Address: gec0::13:1:1:1/120 Index: 69, SNMP ifIndex: 47, VRRP-Traps: enabled Interface state: up, Group: 1, State: master Priority: 200, Advertisement interval: 1, Authentication type: none Preempt: yes, Accept-data mode: no, VIP count: 2, VIP: ge80::13:1:1:99, gec0::13:1:1:99 Advertisement timer: 0.327s, Master router: ge80::13:1:1:1 Virtual router uptime: 00:03:47, Master router uptime: 00:03:41 Virtual MAC: 00:00:5e:00:02:01 Tracking: disabled show vrrp detail (Route Track) show vrrp extensive user@host> show vrrp detail Physical interface: ge-1/1/0, Unit: 0, Address: 30.30.30.30/24 Index: 67, SNMP ifIndex: 379, VRRP-Traps: enabled Interface state: up, Group: 100, State: master Priority: 150, Advertisement interval: 1, Authentication type: none Preempt: yes, Accept-data mode: no, VIP count: 1, VIP: 30.30.30.100 Advertisement timer: 1.218s, Master router: 30.30.30.30 Virtual router uptime: 00:04:28, Master router uptime: 00:00:13 Virtual MAC: 00:00:5e:00:01:64 Tracking: enabled Current priority: 150, Configured priority: 150 Priority hold-time: disabled Interface tracking: disabled Route tracking: enabled, Route count: 1 Route VRF name Route state Priority cost 192.168.40.0/22 default up 30 user@host> show vrrp extensive 2041 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Interface: ge-0/0/0.121, Interface index: 67, Groups: 1, Active : 1 Interface VRRP PDU statistics Advertisement sent : 188 Advertisement received : 0 Packets received : 0 No group match received : 0 Interface VRRP PDU error statistics Invalid IPAH next type received : 0 Invalid VRRP TTL value received : 0 Invalid VRRP version received : 0 Invalid VRRP PDU type received : 0 Invalid VRRP authentication type received: 0 Invalid VRRP IP count received : 0 Invalid VRRP checksum received : 0 Physical interface: ge-0/0/0, Unit: 121, Vlan-id: 212, Address: gec0::12:1:1:1/120 Index: 67, SNMP ifIndex: 45, VRRP-Traps: enabled Interface state: up, Group: 1, State: master Priority: 200, Advertisement interval: 1, Authentication type: none Preempt: yes, Accept-data mode: no, VIP count: 2, VIP: ge80::12:1:1:99, gec0::12:1:1:99 Advertisement timer: 1.034s, Master router: ge80::12:1:1:1 Virtual router uptime: 00:04:04, Master router uptime: 00:03:58 Virtual MAC: 00:00:5e:00:02:01 Tracking: disabled Group VRRP PDU statistics Advertisement sent : 188 Advertisement received : 0 Group VRRP PDU error statistics Bad authentication type received: 0 Bad password received : 0 Bad MD5 digest received : 0 Bad advertisement timer received: 0 Bad VIP count received : 0 Bad VIPADDR received : 0 Group state transition statistics Idle to master transitions : 0 Idle to backup transitions : 1 Backup to master transitions : 1 Master to backup transitions : 0 Interface: ge-0/0/2.131, Interface index: 69, Groups: 1, Active : 1 Interface VRRP PDU statistics Advertisement sent : 186 Advertisement received : 0 Packets received : 0 No group match received : 0 Interface VRRP PDU error statistics Invalid IPAH next type received : 0 Invalid VRRP TTL value received : 0 Invalid VRRP version received : 0 Invalid VRRP PDU type received : 0 Invalid VRRP authentication type received: 0 Invalid VRRP IP count received : 0 Invalid VRRP checksum received : 0 Physical interface: ge-0/0/2, Unit: 131, Vlan-id: 213, Address: gec0::13:1:1:1/120 Index: 69, SNMP ifIndex: 47, VRRP-Traps: enabled Interface state: up, Group: 1, State: master 2042 Chapter 74: Operational Commands for Layer 3 Protocols Priority: 200, Advertisement interval: 1, Authentication type: none Preempt: yes, Accept-data mode: no, VIP count: 2, VIP: ge80::13:1:1:99, gec0::13:1:1:99 Advertisement timer: 0.396s, Master router: ge80::13:1:1:1 Virtual router uptime: 00:04:04, Master router uptime: 00:03:58 Virtual MAC: 00:00:5e:00:02:01 Tracking: disabled Group VRRP PDU statistics Advertisement sent : 186 Advertisement received : 0 Group VRRP PDU error statistics Bad authentication type received: 0 Bad password received : 0 Bad MD5 digest received : 0 Bad advertisement timer received: 0 Bad VIP count received : 0 Bad VIPADDR received : 0 Group state transition statistics Idle to master transitions : 0 Idle to backup transitions : 1 Backup to master transitions : 1 Master to backup transitions : 0 show vrrp interface user@host> show vrrp interface Interface: ge-0/0/0.121, Interface index: 67, Groups: 1, Active : 1 Interface VRRP PDU statistics Advertisement sent : 205 Advertisement received : 0 Packets received : 0 No group match received : 0 Interface VRRP PDU error statistics Invalid IPAH next type received : 0 Invalid VRRP TTL value received : 0 Invalid VRRP version received : 0 Invalid VRRP PDU type received : 0 Invalid VRRP authentication type received: 0 Invalid VRRP IP count received : 0 Invalid VRRP checksum received : 0 Physical interface: ge-0/0/0, Unit: 121, Vlan-id: 212, Address: gec0::12:1:1:1/120 Index: 67, SNMP ifIndex: 45, VRRP-Traps: enabled Interface state: up, Group: 1, State: master Priority: 200, Advertisement interval: 1, Authentication type: none Preempt: yes, Accept-data mode: no, VIP count: 2, VIP: ge80::12:1:1:99, gec0::12:1:1:99 Advertisement timer: 0.789s, Master router: ge80::12:1:1:1 Virtual router uptime: 00:04:26, Master router uptime: 00:04:20 Virtual MAC: 00:00:5e:00:02:01 Tracking: disabled Group VRRP PDU statistics Advertisement sent : 205 Advertisement received : 0 Group VRRP PDU error statistics Bad authentication type received: 0 Bad password received : 0 Bad MD5 digest received : 0 Bad advertisement timer received: 0 Bad VIP count received : 0 Bad VIPADDR received : 0 Group state transition statistics 2043 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Idle to master transitions Idle to backup transitions Backup to master transitions Master to backup transitions show vrrp summary show vrrp track detail show vrrp track summary 2044 user@host> show vrrp summary Interface State Group ge-4/1/0.0 up 1 : : : : VR state backup 0 1 1 0 Type lcl vip Address 10.57.0.2 10.57.0.100 user@host> show vrrp track detail Tracked interface: ae1.211 State: up, Speed: 400m Incurred priority cost: 0 Threshold Priority cost Active 400m 10 300m 60 200m 110 100m 160 down 190 Tracking VRRP interface: ae0.210, Group: 1 VR State: master Current priority: 200, Configured priority: 200 Priority hold-time: disabled, Remaining-time: 50.351 user@host> show vrrp track summary Track if State Speed ae1.211 up 400m VRRP if ae0.210 Group 1 VR State master Current priority 200 PART 16 IGMP Snooping and Multicast • Understanding IGMP Snooping and Multicast on page 2047 • Examples: IGMP Snooping and Multicast Configuration on page 2055 • Configuring IGMP Snooping and Multicast on page 2063 • Verifying IGMP Snooping and Multicast on page 2069 • Configuration Statements for IGMP Snooping and Multicast on page 2073 • Operational Mode Commands for IGMP Snooping and Multicast on page 2143 2045 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2046 CHAPTER 75 Understanding IGMP Snooping and Multicast • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding Multicast VLAN Registration on J-EX Series Switches on page 2052 IGMP Snooping on J-EX Series Switches Overview Internet Group Management Protocol (IGMP) snooping regulates multicast traffic in a switched network. With IGMP snooping enabled, a LAN switch monitors the IGMP transmissions between a host (a network device) and a multicast router, keeping track of the multicast groups and associated member interfaces. The switch uses that information to make intelligent multicast-forwarding decisions and forward traffic to the intended destination interfaces. J-EX Series Switches support IGMPv1, IGMPv2, and IGMPv3. For details on IGMPv1, IGMPv2, and IGMPv3, see the following standards: • For IGMPv1, see RFC 1112, Host extensions for IP multicasting at http://www.faqs.org/rfcs/rfc1112.html. • For IGMPv2, see RFC 2236, Internet Group Management Protocol, Version 2 at http://www.faqs.org/rfcs/rfc2236.html. • For IGMPv3, see RFC 3376, Internet Group Management Protocol, Version 3 at http://www.faqs.org/rfcs/rfc3376.html. This IGMP snooping topic covers: • How IGMP Snooping Works on page 2047 • How IGMP Snooping Works with Routed VLAN Interfaces on page 2048 • How Hosts Join and Leave Multicast Groups on page 2051 • IGMP Snooping Support for IGMPv3 on page 2051 How IGMP Snooping Works A J-EX Series switch usually learns unicast media access control (MAC) addresses by checking the source address field of the frames it receives. However, a multicast MAC 2047 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS address can never be the source address for a packet. As a result, the switch floods multicast traffic on the VLAN, consuming significant amounts of bandwidth. IGMP snooping regulates multicast traffic on a VLAN to avoid flooding. When IGMP snooping is enabled, the switch intercepts IGMP packets and uses the content of the packets to build a multicast cache table. The cache table is a database of multicast groups and their corresponding member ports. The cache table is then used to regulate multicast traffic on the VLAN. When the switch receives multicast packets, it uses the cache table to selectively forward the packets only to the ports that are members of the destination multicast group. Figure 41 on page 2048 shows an example of IGMP traffic flow with IGMP snooping enabled. Figure 41: IGMP Traffic Flow with IGMP Snooping Enabled How IGMP Snooping Works with Routed VLAN Interfaces Switches send traffic to hosts that are part of the same broadcast domain, but routers are needed to route traffic from one broadcast domain to another. Switches use a routed 2048 Chapter 75: Understanding IGMP Snooping and Multicast VLAN interface (RVI) to perform these routing functions. IGMP snooping works with Layer 2 interfaces and RVIs to regulate multicast traffic in a switched network. When a switch receives a multicast packet, the Packet Forwarding Engines in the switch perform an IP multicast lookup on the multicast packet to determine how to forward the packet to its local ports. From the results of the IP multicast lookup, each Packet Forwarding Engine extracts a list of Layer 3 interfaces (which can include VLAN interfaces) that have ports local to the Packet Forwarding Engine. If an RVI is part of this list, the switch provides a bridge multicast group ID for each RVI to the Packet Forwarding Engine. A bridge multicast ID is assigned to direct Layer 3 interfaces and to RVIs. For VLANs that include multicast receivers, the bridge multicast ID includes a sub-next-hop ID. The sub-next-hop ID identifies the multicast Layer 2 interfaces in that VLAN that are interested in receiving the multicast stream. The switch ultimately assigns a next hop after it does a route lookup. The next hop includes all direct Layer 3 interfaces and RVIs. The Packet Forwarding Engine then forwards multicast traffic to the bridge multicast ID that includes all Layer 3 interfaces and RVIs that are multicast receivers for a given multicast group. Figure 42 on page 2050 shows how multicast traffic is forwarded on a multilayer switch. In this illustration, multicast traffic is coming in through the xe-0/1/0.0 interface. A multicast group has been formed by the Layer 3 interface ge-0/0/2.0, vlan.0, and vlan.1. The ge-2/0/0.0 interface is a common trunk interface that belongs to both vlan.0 and vlan.1. The letter “R” next to an interface name in the illustration indicates that a multicast receiver host is associated with that interface. NOTE: Traffic sent to an access interface is untagged; traffic sent to a trunk interface is tagged. For more information on VLAN tagging, see “Understanding Bridging and VLANs on J-EX Series Switches” on page 1041. 2049 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 42: IGMP Traffic Flow with Routed VLAN Interfaces Table 255 on page 2050 shows the bridge multicast IDs and next hops that are created. The term subnh refers to a sub-next hop. The Packet Forwarding Engine will forward multicast traffic to bridge multicast ID9. Table 255: Bridge Multicast IDs and Next Hops ID Number Type of Next Hop Next Hop Tag Information ID1 RHN_UNICAST ge-0/0/0.0 tag=off ID2 RHN_UNICAST ge-2/0/0.0 tag=on ID3 RHN_FLOOD [ID1, ID2] ID4 RHN_UNICAST ge-0/0/1.0 ID5 RHN_FLOOD [ID4, ID2] ID6 RHN_UNICAST vlan.0 subnh=ID3 ID7 RHN_UNICAST VLAN.1 subnh=ID5 ID8 RHN_UNICAST ge-0/0/2.0 ID9 RHN_FLOOD [ID6, ID7, ID8] 2050 tag=off Chapter 75: Understanding IGMP Snooping and Multicast How Hosts Join and Leave Multicast Groups Hosts can join multicast groups in either of two ways: • By sending an unsolicited IGMP join message to a multicast router that specifies the IP multicast group that the host is attempting to join. • By sending an IGMP join message in response to a general query from a multicast router. A multicast router continues to forward multicast traffic to a VLAN provided that at least one host on that VLAN responds to the periodic general IGMP queries. For a host to remain a member of a multicast group, therefore, it must continue to respond to the periodic general IGMP queries. To leave a multicast group, a host can either not respond to the periodic general IGMP queries, which results in a “silent leave” (the only leave option for hosts connected to switches running IGMPv1), or send a group-specific IGMPv2 leave message. NOTE: A host does not leave a group if its link goes down—for example, if a user disconnects from the port. The host remains a member of the group until group membership times out and a silent leave occurs. This means that if another user connects to the port before the silent leave occurs, the host resumes receiving the group multicast traffic until the silent leave, even though it never sent an IGMP join message. IGMP Snooping Support for IGMPv3 IGMPv3 allows IGMP snooping to filter multicast streams based on the source address of the multicast stream. Junos OS for J-EX Series switches supports IGMPv3 packets that are in INCLUDE or EXCLUDE mode. When a host sends an IGMPv3 INCLUDE report through a switch interface to indicate that it wants to receive a multicast stream from a source address, the switch adds the source address to the source list. In INCLUDE mode, the switch requests that packets be sent to the specified multicast address only from those IP source addresses listed in the source-list parameter. However, because J-EX Series switches do not support forwarding on a per-source basis, the switch merges all IGMPv3 reports for a VLAN to create a (*,G,V) route with the appropriate next hop. This next hop contains all the interfaces on the VLAN that are interested in group G. When IGMP snooping for IGMPv3 is used with an RVI, the same (*,G,V) route is added to the snooping information in the RVI’s output interface list (olist). When a host sends an IGMPv3 EXCLUDE report, the host indicates that it wants to join a multicast group and receive packets for that group except from those IP source addresses in the source-list parameter. However, because J-EX Series switches do not support forwarding on a per-source basis, the switch ignores the source information and creates a (*,G,V) route. A host can also send an EXCLUDE report in which the source-list parameter is empty, which is known as an EXCLUDE NULL report. An EXCLUDE NULL 2051 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS report indicates that the host wants to join the multicast group and receive packets from all sources. The switch creates a (*, G,V) route in this case also. Related Documentation • Understanding Multicast VLAN Registration on J-EX Series Switches on page 2052 • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 • RFC 3171, IANA Guidelines for IPv4 Multicast Address Assignments at http://tools.ietf.org/html/rfc3171 Understanding Multicast VLAN Registration on J-EX Series Switches Multicast VLAN registration (MVR) allows you to efficiently distribute IPTV multicast streams across an Ethernet ring-based Layer 2 network and reduce the amount of bandwidth consumed by this multicast traffic. In a standard Layer 2 network, a multicast stream received on one VLAN is never distributed to interfaces outside that VLAN. If hosts in multiple VLANs request the same multicast stream, a separate copy of that multicast stream is distributed to the requesting VLANs. MVR introduces the concept of a multicast source VLAN (MVLAN), which is created by MVR and becomes the only VLAN over which IPTV multicast traffic flows throughout the Layer 2 network. The J-EX Series Switch that is enabled for MVR selectively forward IPTV multicast traffic from interfaces on the MVLAN (source interfaces) to hosts that are connected to interfaces that are not part of the MVLAN. These interfaces are known as MVR receiver ports. The MVR receiver ports can receive traffic from a port on the MVLAN but cannot send traffic onto the MVLAN, and they remain in their own VLANs for bandwidth and security reasons. This topic includes: • How MVR Works on page 2052 How MVR Works In many ways, MVR is similar to IGMP snooping. Both monitor IGMP join and leave messages and build forwarding tables based on the media access control (MAC) addresses of the hosts sending those IGMP messages. Whereas IGMP snooping operates within a given VLAN to regulate multicast traffic, MVR can operate with hosts on different VLANs in a Layer 2 network to selectively deliver IPTV multicast traffic to requesting hosts, thereby reducing the amount of bandwidth needed to forward multicast traffic. When you configure an MVLAN, you assign a range of multicast group addresses to it. You then configure other VLANs to be MVR receiver VLANs, which receive multicast streams from the MVLAN. The MVR receiver ports comprise all the interfaces that exist on any of the MVR receiver VLANs. Interfaces that are on the MVLAN itself cannot be MVR receiver ports for that MVLAN. 2052 Chapter 75: Understanding IGMP Snooping and Multicast NOTE: MVR is supported on VLANs running IGMP version 2 (IGMPv2) only. MVR Modes MVR operates in two modes: MVR transparent mode and MVR proxy mode. Both modes allow MVR to forward only one copy of a multicast stream to the Layer 2 network. • MVR Transparent Mode on page 2053 • MVR Proxy Mode on page 2053 MVR Transparent Mode In MVR transparent mode (the default mode), the switch receives one copy of each IPTV multicast stream and then replicates the stream only to those hosts that want to receive it, while forwarding all other types of multicast traffic without modification. Transparent mode is the default mode. The switch handles IGMP packets destined for both the multicast source VLAN and multicast receiver VLANs in the same way that it handles them when MVR is not being used. That is, when a host on a VLAN sends IGMP join and leave messages, the switch floods the messages to all router interfaces in the VLAN. Similarly, when a VLAN receives IGMP queries from its router interfaces, it floods the queries to all interfaces in the VLAN. If a host on a multicast receiver port joins an MVR group on the multicast receiver VLAN, the appropriate bridging entry is added and the MVLAN forwards that group’s IPTV multicast traffic on that port (even though that port is not in the MVLAN). Likewise, if a host on a multicast receiver port leaves an MVR group on the multicast receiver VLAN, the appropriate bridging entry is deleted and the MVLAN stops forwarding that group’s IPTV multicast traffic on that port. In addition, you can configure the switch to statically install the bridging entries on the multicast receiver VLAN. MVR Proxy Mode When you use MVR in proxy mode, the switch acts as a proxy for any MVR group in both the upstream and downstream directions. In the downstream direction, the switch acts as the querier for the groups in the MVR receiver VLANs. In the upstream direction, the switch originates the IGMP reports and leaves and answers IGMP queries from multicast routers. When the MVR receiver VLANs receive IGMP joins and leaves, the switch creates bridging entries on the MVLAN as needed, as it does in MVR transparent mode. In addition, the switch sends out IGMP joins and leaves on the MVLAN based on these bridging entries. Configuring MVR proxy mode on the MVLAN automatically enables IGMP snooping proxy mode on all MVR receiver VLANs as well as on the MVLAN. Related Documentation • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 2053 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2054 CHAPTER 76 Examples: IGMP Snooping and Multicast Configuration • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 Example: Configuring IGMP Snooping on J-EX Series Switches IGMP snooping regulates multicast traffic in a switched network. With IGMP snooping enabled, a LAN switch monitors the IGMP transmissions between a host (a network device) and a multicast router, keeping track of the multicast groups and associated member ports. The switch uses that information to make intelligent multicast-forwarding decisions and forward traffic to the intended destination interfaces. Configure IGMP snooping on one or more VLANs to allow the switch to examine IGMP packets and make forwarding decisions based on packet content. By default, IGMP snooping is enabled on J-EX Series switches. This example describes how to configure IGMP snooping: • Requirements on page 2055 • Overview and Topology on page 2056 • Configuration on page 2056 Requirements This example uses the following software and hardware components: • One J-EX4200-24T switch Before you configure IGMP snooping, be sure you have: • Configured the employee-vlan VLAN on the switch • Assigned interfaces ge-0/0/1, ge-0/0/2, and ge-0/0/3 to employee-vlan See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. 2055 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Overview and Topology IGMP snooping controls multicast traffic in a switched network. With IGMP snooping enabled, a J-EX Series switch monitors the IGMP transmissions between a host and a multicast router to keep track of the multicast groups and associated member ports. The switch uses this information to make intelligent decisions and forward multicast traffic to the intended destination interfaces. You can configure IGMP snooping on all interfaces in a VLAN or on individual interfaces. This example shows how to configure IGMP snooping on a J-EX Series switch. The configuration setup for this example includes the VLAN employee-vlan on the switch. Table 256 on page 2056 shows the components of the topology for this example. Table 256: Components of the IGMP Snooping Topology Properties Settings Switch hardware One J-EX4200-24T switch VLAN name employee-vlan, tag 20 Interfaces in employee-vlan ge-0/0/1, ge-0/0/2, ge-0/0/3 Multicast IP address for employee-vlan 225.100.100.100 In this example, the switch is initially configured as follows: • IGMP snooping is disabled on the VLAN. Configuration To configure basic IGMP snooping on a switch: CLI Quick Configuration To quickly configure IGMP snooping, copy the following commands and paste them into the switch terminal window: [edit protocols] set igmp-snooping vlan employee-vlan set igmp-snooping vlan employee-vlan interface ge-0/0/1 group-limit 50 set igmp-snooping vlan employee-vlan immediate-leave set igmp-snooping vlan employee-vlan interface ge-0/0/3 static group 225.100.100.100 set igmp-snooping vlan employee-vlan interface ge-0/0/2 multicast-router-interface set igmp-snooping vlan employee-vlan robust-count 4 Step-by-Step Procedure Configure IGMP snooping: 1. Enable and configure IGMP snooping on the VLAN employee-vlan: [edit protocols] user@switch# set igmp-snooping vlan employee-vlan 2. 2056 Configure the limit for the number of multicast groups allowed on the ge-0/0/1 interface to 50. Chapter 76: Examples: IGMP Snooping and Multicast Configuration [edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/1 group-limit 50 3. Configure the switch to immediately remove a group membership from an interface when it receives a leave message from that interface without waiting for any other IGMP messages to be exchanged (IGMPv2 only): [edit protocols] user@switch# set igmp-snooping vlan employee-vlan immediate-leave 4. Statically configure IGMP group membership on a port: [edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/3.0 static group 225.100.100.100 5. Statically configure an interface as a switching interface toward a multicast router (the interface to receive multicast traffic): [edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/2 multicast-router-interface 6. Change the number of timeout intervals the switch waits before timing out a multicast group to 4: [edit protocols] user@switch# set igmp-snooping vlan employee-vlan robust-count 4 Results Check the results of the configuration: user@switch# show protocols igmp-snooping vlan employee-vlan { robust-count 4; immediate-leave; interface ge-0/0/1 { group-limit 50; } interface ge-0/0/2 { multicast-router-interface; } interface ge-0/0/3 { static { group 255.100.100.100 } } } Related Documentation • Configuring IGMP Snooping (CLI Procedure) on page 2063 • [edit protocols] Configuration Statement Hierarchy on page 48 2057 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Example: Configuring Multicast VLAN Registration on J-EX Series Switches Multicast VLAN registration (MVR) allows hosts that are not part of a multicast VLAN (MVLAN) to receive multicast streams from the MVLAN, allowing the MVLAN to be shared across the Layer 2 network and eliminating the need to send duplicate multicast streams to each requesting VLAN in the network. Hosts remain in their own VLANs for bandwidth and security reasons. This example describes how to configure MVR on J-EX Series switches: • Requirements on page 2058 • Overview and Topology on page 2058 • Configuration on page 2061 Requirements This example uses the following hardware and software components: • One J-EX Series switch Before you configure MVR, be sure you have: • Configured two or more VLANs on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. • Connected the J-EX Series switch to a network that can transmit IPTV multicast streams from a video server. • Connected a host that is capable of receiving IPTV multicast streams to an interface in one of the VLANs. Overview and Topology In a standard Layer 2 network, a multicast stream received on one VLAN is never distributed to interfaces outside that VLAN. If hosts in multiple VLANs request the same multicast stream, a separate copy of that multicast stream is distributed to the requesting VLANs. MVR introduces the concept of a multicast source VLAN (MVLAN), which is created by MVR and becomes the only VLAN over which multicast traffic flows throughout the Layer 2 network. Multicast traffic can then be selectively forwarded from interfaces on the MVLAN (source ports) to hosts that are connected to interfaces (multicast receiver ports) that are not part of the multicast source VLAN. When you configure an MVLAN, you assign a range of multicast group addresses to it. You then configure other VLANs to be MVR receiver VLANs, which receive multicast streams from the MVLAN. The MVR receiver ports comprise all the interfaces that exist on any of the MVR receiver VLANs. You can configure MVR to operate in one of two modes: transparent mode (the default mode) or proxy mode. Both modes allow MVR to forward only one copy of a multicast stream to the Layer 2 network. 2058 Chapter 76: Examples: IGMP Snooping and Multicast Configuration In transparent mode, the switch receives one copy of each IPTV multicast stream and then replicates the stream only to those hosts that want to receive it, while forwarding all other types of multicast traffic without modification. Figure 1 shows how MVR operates in transparent mode. In proxy mode, the switch acts as a proxy for the IGMP multicast router in the MVLAN for MVR group memberships established in the MVR receiver VLANs and generates and sends IGMP packets into the MVLAN as needed. Figure 2 shows how MVR operates in proxy mode. This example shows how to configure MVR in both transparent mode and proxy mode on a J-EX Series switch. The topology includes a video server that is connected to a multicast router, which in turn forwards the IPTV multicast traffic in the MVLAN to the Layer 2 network. Figure 43 on page 2060 shows the MVR topology in transparent mode. Interfaces P1 and P2 on Switch C belong to service VLAN s0 and MVLAN mv0. Interface P4 of Switch C also belongs to service VLAN s0. In the upstream direction of the network, only non-IPTV traffic is being carried in individual customer VLANs of service VLAN s0. VLAN c0 is an example of this type of customer VLAN. IPTV traffic is being carried on MVLAN mv0. If any host on any customer VLAN connected to port P4 requests an MVR stream, switch C takes the stream from VLAN mv0 and replicates that stream onto port P4 with tag mv0. IPTV traffic, along with other network traffic, flows form port P4 out to the Digital Subscriber Line Access Multiplexer (DSLAM) D1. 2059 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 43: MVR Topology in Transparent Mode Figure 44 on page 2061 shows the MVR topology in proxy mode. Interfaces P1 and P2 on switch C belong to MVLAN mv0 and customer VLAN c0. Interface P4 on switch C is an access port of customer VLAN c0. In the upstream direction of the network, only non-IPTV traffic is being carried on customer VLAN c0. Any IPTV traffic requested by hosts on VLAN c0 is replicated untagged to port P4 based on streams received in MVLAN mv0. IPTV traffic flows from port P4 out to an IPTV-enabled device in Host 1. Other traffic, such as data and voice traffic, also flows from port P4 to other network devices in Host 1. 2060 Chapter 76: Examples: IGMP Snooping and Multicast Configuration Figure 44: MVR Topology in Proxy Mode For information on VLAN tagging, see “Understanding Bridging and VLANs on J-EX Series Switches” on page 1041. Configuration To configure MVR perform these tasks: CLI Quick Configuration To quickly configure MVR in proxy mode, copy the following commands and paste them into the switch terminal window. To quickly configure MVR in transparent mode (the default mode), do not copy and paste the final command line in the following block of lines: [edit protocols igmp-snooping] set vlan mv0 data-forwarding source groups 225.10.0.0/16 set vlan v2 data-forwarding receiver source-vlans mv0 set vlan v2 data-forwarding receiver install set vlan mv0 proxy source-address 10.1.1.1 2061 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure MVR, perform these tasks: 1. Configure mv0 to be an MVLAN: [edit protocols igmp-snooping] user@switch# set vlan mv0 data-forwarding source groups 225.10.0.0/16 2. Configure v2 to be a multicast receiver VLAN with mv0 as its source: [edit protocols igmp-snooping] user@switch# set vlan v2 data-forwarding receiver source-vlans mv0 3. (Optional) Install forwarding entries in the multicast receiver VLAN v2: [edit protocols igmp-snooping] user@switch# set vlan v2 data-forwarding receiver install 4. (Optional) Configure MVR in proxy mode: [edit protocols igmp-snooping] user@switch# set vlan mv0 proxy source-address 10.1.1.1 Results Check the results of the configuration: [edit protocols igmp-snooping] user@switch# show vlan mv0 { proxy { source-address 10.1.1.1; } data-forwarding { source { groups 225.10.0.0/16; } } } vlan v2 { data-forwarding { receiver { source-vlans mv0; install; } } } Related Documentation 2062 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 • Understanding Multicast VLAN Registration on J-EX Series Switches on page 2052 CHAPTER 77 Configuring IGMP Snooping and Multicast • Configuring IGMP Snooping (CLI Procedure) on page 2063 • Configuring IGMP Snooping (J-Web Procedure) on page 2064 • Changing the IGMP Snooping Group Query Membership Timeout Value (CLI Procedure) on page 2067 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 Configuring IGMP Snooping (CLI Procedure) IGMP snooping regulates multicast traffic in a switched network. With IGMP snooping enabled, a LAN switch monitors the IGMP transmissions between a host (a network device) and a multicast router, keeping track of the multicast groups and associated member ports. The switch uses that information to make intelligent multicast-forwarding decisions and forward traffic to the intended destination interfaces. You can configure IGMP snooping on one or more VLANs to allow the switch to examine IGMP packets and make forwarding decisions based on packet content. By default, IGMP snooping is enabled on J-EX Series switches. NOTE: You cannot configure IGMP snooping on a secondary VLAN. To enable IGMP snooping and configure individual options as needed for your network by using the CLI: 1. Enable IGMP snooping on a VLAN: [edit protocols] user@switch# set igmp-snooping vlan employee-vlan 2. Configure the limit for the number of multicast groups allowed on the ge-0/0/1 interface to 50. [edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/1 group-limit 50 3. Configure the switch to immediately remove a group membership from an interface when it receives a leave message from that interface without waiting for any other IGMP messages to be exchanged (IGMPv2 only): 2063 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit protocols] user@switch# set igmp-snooping vlan employee-vlan immediate-leave 4. Statically configure IGMP group membership on a port: [edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/3.0 static group 225.100.100.100 5. Statically configure an interface as a switching interface toward a multicast router (the interface to receive multicast traffic): [edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/2.0 multicast-router-interface 6. Change the number of timeout intervals the switch waits before timing out a multicast group to 4: [edit protocols] user@switch# set igmp-snooping vlan employee-vlan robust-count 4 Related Documentation • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Changing the IGMP Snooping Group Query Membership Timeout Value (CLI Procedure) on page 2067 • show igmp-snooping membership on page 2181 • show igmp-snooping route on page 2183 • show igmp-snooping statistics on page 2185 • show igmp-snooping vlans on page 2187 • IGMP Snooping on J-EX Series Switches Overview on page 2047 Configuring IGMP Snooping (J-Web Procedure) IGMP snooping regulates multicast traffic in a switched network. With IGMP snooping enabled, the J-EX Series switch monitors the IGMP transmissions between a host (a network device) and a multicast router, keeping track of the multicast groups and associated member interfaces. The switch uses that information to make intelligent multicast-forwarding decisions and forward traffic to the intended destination interfaces. You can configure IGMP snooping on one or more VLANs to allow the switch to examine IGMP packets and make forwarding decisions based on packet content. By default, IGMP snooping is enabled on J-EX Series switches. To enable IGMP snooping and configure individual options using the J-Web interface: 1. 2064 Select Configure > Switching > IGMP Snooping. Chapter 77: Configuring IGMP Snooping and Multicast 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 334 for details about all commit options. 2. Click one: • Add—Creates an IGMP snooping configuration for the VLAN. • Edit—Modifies an IGMP snooping configuration for the VLAN. • Delete—Deletes a selected VLAN from the IGMP snooping configuration. When you are adding or editing an IGMP snooping configuration, enter information as described in Table 257 on page 2065 3. Click OK to apply changes to the configuration or click Cancel to cancel without saving changes. To disable IGMP snooping on a VLAN, select the VLAN from the list and click Disable. Table 257: IGMP Snooping Configuration Fields Field Function Your Action VLAN Name Specifies the VLAN on which to enable IGMP snooping. Select a VLAN from the list to add it to the snooping configuration. Immediate Leave Immediately removes a multicast group membership from an interface when it receives a leave message from that interface without waiting for any other IGMP messages to be exchanged (IGMPv2 only). To enable the option, select the check box. Specifies the number of timeout intervals the switch waits before timing out a multicast group. Type a value. Robust Count To disable the option, clear the check box. 2065 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 257: IGMP Snooping Configuration Fields (continued) Field Function Your Action Interfaces List Statically configures an interface as a switching interface toward a multicast router (the interface to receive multicast traffic). Click one: • Add—Adds an interface to the IGMP snooping configuration. 1. Select an interface from the list. 2. Select Multicast Router Interface. 3. Type the maximum number of groups an interface can join. 4. In Static, choose one: Related Documentation 2066 • Click Add, type a group IP address, and click OK. • Select a group and click Remove to remove the group membership. • Edit—Edits the interface settings for the IGMP snooping configuration. • Remove—Deletes an interface configured for IGMP snooping. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 • Changing the IGMP Snooping Group Query Membership Timeout Value (CLI Procedure) on page 2067 • IGMP Snooping on J-EX Series Switches Overview on page 2047 Chapter 77: Configuring IGMP Snooping and Multicast Changing the IGMP Snooping Group Query Membership Timeout Value (CLI Procedure) Generally, you do not need to explicitly set the group membership timeout value for IGMP snooping groups on a J-EX Series switch. The group membership timeout value, which determines how long the switch waits before removing an IGMP snooping group from its multicast cache table. is implicitly set to 260 seconds when you configure IGMP snooping. When you enable IGMP snooping on a switch, the query-interval and query-response-interval values are set to their default values and are applied to all VLANs created on the switch. The default values are: • query-interval—125 seconds • query-response-interval—10 seconds The software automatically calculates the group membership timeout value for an IGMP snooping-enabled switch by multiplying the query-interval value by 2 and then adding the query-response-interval value. For example, using the default values: (125 x 2) + 10) = 260. If you need to explicitly set the group membership timeout value, you reset the query-interval and query-response-interval values at the [edit protocols igmp] hierarchy level. (Notice that you are not resetting the values at the [edit protocols igmp-snooping] hierarchy level.) When you reset these values, the IGMP snooping configuration inherits the new values and recalculates the group membership timeout value accordingly. For more information on changing these values, see the Junos OS Multicast Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. To change the IGMP snooping group membership timeout value to 350: 1. Configure the query-interval value to be 150: [edit protocols] user@switch# set igmp query-interval 150 2. Configure the query-response-interval value to be 50: [edit protocols] user@switch# set igmp query-response-interval 50 Related Documentation • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Verifying That the IGMP Snooping Group Query Timeout Value Has Been Changed Correctly on page 2070 • Configuring IGMP Snooping (CLI Procedure) on page 2063 • Configuring IGMP Snooping (J-Web Procedure) on page 2064 2067 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Multicast VLAN Registration (CLI Procedure) Multicast VLAN registration (MVR) allows hosts that are not part of a multicast source VLAN (MVLAN) to still receive multicast streams from the MVLAN, allowing an MVLAN to be shared across a Layer 2 network. Hosts remain in their own VLANs for bandwidth and security reasons but are able to receive multicast streams from the MVLAN. You can configure one or more VLANs on a switch to be MVLANs or MVR receiver VLANs. By default, MVR is not configured on J-EX Series switches. NOTE: MVR is supported on VLANs running IGMP version 2 (IGMPv2) only. NOTE: When configuring MVR, the following restrictions apply: • You cannot enable multicast protocols on VLAN interfaces that are members of MVLANs. • If you configure an MVLAN in proxy mode, IGMP snooping proxy mode will be automatically enabled on all MVR receiver VLANs of this MVLAN. If a VLAN is an MVR receiver VLAN for multiple MVLANs, all of the MVLANs must have proxy mode enabled or all must have proxy mode disabled. You can enable proxy mode only on VLANs that are configured as MVR source VLANs and that are not configured for Q-in-Q tunneling. • After you configure a VLAN as an MVLAN, that VLAN is no longer available for other uses. To configure MVR: 1. Configure the VLAN named mv0 to be an MVLAN: [edit protocols] user@switch# set igmp-snooping vlan mv0 data-forwarding source groups 225.10.0.0/16 2. Configure the MVLAN mv0 to be a proxy VLAN: [edit protocols] user@switch# set igmp-snooping vlan mv0 proxy source–address 10.0.0.1 3. Configure the VLAN named v2 to be an MVR receiver VLAN: [edit protocols] user@switch# set igmp-snooping vlan v2 data-forwarding receiver source-vlans mv0 4. Install forwarding entries in the MVR receiver VLAN: [edit protocols] user@switch# set igmp-snooping vlan mv0 data-forwarding receiver install Related Documentation 2068 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Understanding Multicast VLAN Registration on J-EX Series Switches on page 2052 CHAPTER 78 Verifying IGMP Snooping and Multicast • Monitoring IGMP Snooping on page 2069 • Verifying That the IGMP Snooping Group Query Timeout Value Has Been Changed Correctly on page 2070 Monitoring IGMP Snooping Purpose Action Use the monitoring feature to view status and information about IGMP snooping configuration on your J-EX Series switch. To display IGMP snooping details in the J-Web interface, select Monitor > Switching > IGMP Snooping. To display IGMP snooping details in the CLI, enter the following commands: Meaning • show igmp-snooping vlans • show igmp-snooping statistics • show igmp-snooping route Table 258 on page 2069 summarizes the IGMP snooping details displayed. Table 258: Summary of IGMP Snooping Output Fields Field Values IGMP Snooping Monitor VLAN The VLAN for which IGMP snooping is enabled. Interfaces Indicates the interfaces configured as switching interfaces that are associated with the multicast router. Groups Indicates the number of the multicast groups learned by the VLAN. MRouters Specifies the multicast router. Receivers Specifies the multicast receiver. IGMP Route Information 2069 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 258: Summary of IGMP Snooping Output Fields (continued) Field Values VLAN The VLAN for which IGMP snooping is enabled. Group Indicates the multicast groups learned by the VLAN. Next-Hop Specifies the next hop assigned by the switch after performing the route lookup. Related Documentation • show igmp-snooping vlans on page 2187 • show igmp-snooping statistics on page 2185 • show igmp-snooping route on page 2183 • Configuring IGMP Snooping (CLI Procedure) on page 2063 • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 Verifying That the IGMP Snooping Group Query Timeout Value Has Been Changed Correctly Purpose Action Verify that the IGMP snooping group query timeout value has been changed correctly from its default value. Display the IGMP protocol information: user@switch> show configuration protocols igmp query-interval 150; query-response-interval 50; accounting; interface vlan.43 { version 2; } Display the IGMP snooping membership information, which contains the group query timeout value that was derived from the IGMP configuration: user@switch> show show igmp-snooping membership detail VLAN: v43 Tag: 43 (Index: 4) Group: 225.0.0.1 Receiver count: 1, Flags: ge-0/0/15.0 Uptime: 00:00:05 timeout: 350 Meaning When you enable IGMP snooping on a switch, the query-interval and query-response-interval values are set to their default values and are applied to all VLANs created on the switch. The IGMP snooping group timeout value is derived from these default settings. Based on the default values, the initial IGMP snooping group query timeout value is 260. To change the group query timeout value, change the query-interval and query-response-interval values at the [edit protocols igmp] hierarchy level. The IGMP snooping group query timeout value is then recalculated based on the new IGMP configuration settings. 2070 Chapter 78: Verifying IGMP Snooping and Multicast The output from the show protocols igmp command shows the revised IGMP configuration settings for query-interval and query-response-interval. You know that these values have been revised because they are different from the default values. The output from the show igmp-snooping membership detail command shows the revised group query timeout value, 350, which was derived from the new IGMP configuration settings. Related Documentation • Changing the IGMP Snooping Group Query Membership Timeout Value (CLI Procedure) on page 2067 2071 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2072 CHAPTER 79 Configuration Statements for IGMP Snooping and Multicast • [edit protocols] Configuration Statement Hierarchy on page 2073 [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; 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); } } gvrp { 2073 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ; interface (all | [interface-name]) { disable; } join-timer millseconds; leave-timer milliseconds; leaveall-timer milliseconds; } 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 { 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; } traceoptions { file filename ; flag flag (detail | disable | receive | send); } } lldp-med { 2074 Chapter 79: Configuration Statements for IGMP Snooping and Multicast 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } 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; 2075 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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); loss-threshold number; } mep mep-id { auto-discovery; direction down; interface interface-name; remote-mep mep-id { action-profile profile-name; } } } } } link-fault-management { 2076 Chapter 79: Configuration Statements for IGMP Snooping and Multicast 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; 2077 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } sflow { agent-id collector { ip-address; udp-port port-number; } disable; interfaces interface-name { disable; polling-interval seconds; sample-rate number; } polling-interval seconds; sample-rate number; source-ip } stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; } 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 { alarm; block; } cost cost; 2078 Chapter 79: Configuration Statements for IGMP Snooping and Multicast disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } } Related Documentation • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding MAC RADIUS Authentication on J-EX Series Switches • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Ethernet OAM Connectivity Fault Management for a J-EX Series Switch on page 3463 • Understanding Ethernet OAM Link Fault Management for a J-EX Series Switch on page 3427 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding How to Use sFlow Technology for Network Monitoring on a J-EX Series Switch on page 3283 • Understanding VSTP for J-EX Series Switches on page 1281 2079 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS accounting (Per Interface) Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation (accounting | no-accounting); [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable or disable the collection of IGMP join and leave event statistics for an interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Recording IGMP Join and Leave Events accounting (Protocol) Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 2080 accounting; [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the collection of IGMP join and leave event statistics on the system. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Recording IGMP Join and Leave Events Chapter 79: Configuration Statements for IGMP Snooping and Multicast address (Anycast RPs) Syntax Hierarchy Level Release Information Description Options address address ; [edit logical-systems logical-system-name protocols pim rp local (inet | inet6) anycast-pim rp-set], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp local (inet | inet6) anycast-pim rp-set], [edit protocols pim rp local (inet | inet6) anycast-pim rp-set], [edit routing-instances routing-instance-name protocols pim rp local (inet | inet6) anycast-pim rp-set] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the anycast rendezvous point (RP) addresses in the RP set. Multiple addresses can be configured in an RP set. If the RP has peer Multicast Source Discovery Protocol (MSDP) connections, then the RP must forward MSDP source active (SA) messages. address—RP address in an RP set. forward-msdp-sa—(Optional) Forward MSDP SAs to this address. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. address (Local RPs) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation address address; [edit logical-systems logical-system-name protocols pim rp local family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp local family (inet | inet6)], [edit protocols pim rp local family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the local rendezvous point (RP) address. address—Local RP address. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Local PIM RPs 2081 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS anycast-pim Syntax Hierarchy Level Release Information Description anycast-pim { rp-set { address address ; } [edit logical-systems logical-system-name protocols pim rp local family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp local family (inet | inet6)], [edit protocols pim rp local family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure properties for anycast RP using PIM. The remaining statements are explained separately. Required Privilege Level Related Documentation 2082 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring PIM Anycast with MSDP Chapter 79: Configuration Statements for IGMP Snooping and Multicast assert-timeout Syntax Hierarchy Level Release Information Description Options assert-timeout seconds; [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Multicast routing devices running PIM sparse mode often forward the same stream of multicast packets onto the same LAN through the rendezvous-point tree (RPT) and shortest-path tree (SPT). PIM assert messages help routing devices determine which routing device forwards the traffic and prunes the RPT for this group. By default, routing devices enter an assert cycle every 180 seconds. You can configure this assert timeout to be between 5 and 210 seconds. seconds—Time for routing device to wait before another assert message cycle. Range: 5 through 210 seconds Default: 180 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the PIM Assert Timeout 2083 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS auto-rp Syntax Hierarchy Level Release Information Description Options auto-rp { (announce | discovery | mapping); (mapping-agent-election | no-mapping-agent-election); } [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure automatic RP announcement and discovery. announce—Configures the routing device to listen only for mapping packets and also to advertise itself if it is an RP. discovery—Configures the routing device to listen only for mapping packets. mapping—Configures the routing device to announce, listens for and generates mapping packets, and announces that the routing device is eligible to be an RP. The remaining statement is explained separately. Required Privilege Level Related Documentation 2084 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Auto-RP Chapter 79: Configuration Statements for IGMP Snooping and Multicast bootstrap Syntax Hierarchy Level Release Information Description bootstrap { family (inet | inet6) { export [ policy-names ]; import [ policy-names ]; priority number; } } [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure parameters to control bootstrap routers and messages. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties bootstrap-export Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation bootstrap-export [ policy-names ]; [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more export policies to control outgoing PIM bootstrap messages. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties • bootstrap-import on page 2086 2085 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS bootstrap-import Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation bootstrap-import [ policy-names ]; [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more import policies to control incoming PIM bootstrap messages. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties • bootstrap-export on page 2085 bootstrap-priority Syntax Hierarchy Level Release Information bootstrap-priority number; [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure whether this routing device is eligible to be a bootstrap router. In the case of a tie, the routing device with the highest IP address is elected to be the bootstrap router. Options number—Priority for becoming the bootstrap router. A value of 0 means that the routing device is not eligible to be the bootstrap router. Range: 0 through 255 Default: 0 Required Privilege Level Related Documentation 2086 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Junos OS Multicast Protocols Configuration Guide Chapter 79: Configuration Statements for IGMP Snooping and Multicast data-forwarding Syntax Hierarchy Level Release Information Description data-forwarding { source { groups group-prefix; } receiver { source-vlans vlan-list; install; } } [edit protocols igmp-snooping vlan vlan-id | vlan-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the VLAN to be a multicast source VLAN (MVLAN) or a multicast VLAN registration (MVR) receiver VLAN. Each data-forwarding VLAN, which can be a multicast source VLAN (MVLAN) or a multicast receiver VLAN, must have exactly one source statement or exactly one receiver statement. A data-forwarding VLAN can operate only in IGMPv2 mode. The remaining statements are explained separately. Default Required Privilege Level Related Documentation Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 2087 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dense-groups Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation dense-groups { addresses; } [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure which groups are operating in dense mode. addresses—Address of groups operating in dense mode. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Sparse-Dense Mode Properties disable Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation 2088 disable { interface interface-name } [edit protocols igmp-snooping vlan vlan-id | vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable IGMP snooping on all interfaces in a VLAN or on a specific VLAN interface. If you do not specify an interface, all interfaces in the given VLAN are disabled. interface-name —Name of the interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 Chapter 79: Configuration Statements for IGMP Snooping and Multicast disable (PIM) Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation disable; [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name protocols pim family (inet | inet6)], [edit logical-systems logical-system-name protocols pim interface interface-name], [edit logical-systems logical-system-name protocols pim rp local family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp local family (inet | inet6)], [edit protocols pim], [edit protocols pim family (inet | inet6)], [edit protocols pim interface interface-name], [edit protocols pim rp local family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim], [edit routing-instances routing-instance-name protocols pim family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim interface interface-name], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Explicitly disable PIM at the protocol, interface or family hierarchy levels. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling PIM • family (Disable PIM) disable Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation disable; [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable IGMP on the system. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Disabling IGMP 2089 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dr-election-on-p2p Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation dr-election-on-p2p; [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable PIM designated router (DR) election on point-to-point (P2P) links. No PIM DR election is performed on P2P links. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Designated Router Election on Point-to-Point Links dr-register-policy Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2090 dr-register-policy [ policy-names ]; [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to control outgoing PIM register messages. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Register Message Filtering on a PIM RP or DR • rp-register-policy on page 2125 Chapter 79: Configuration Statements for IGMP Snooping and Multicast embedded-rp Syntax Hierarchy Level Release Information Description embedded-rp { group-ranges { destination-ip-prefix; } maximum-rps limit; } [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure properties for embedded IP version 6 (IPv6) RPs. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Embedded RP for IPv6 export (Bootstrap) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation export [ policy-names ]; [edit logical-systems logical-system-name protocols pim rp bootstrap family (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp bootstrap family (inet | inet6)], [edit protocols pim rp bootstrap family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp bootstrap family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more export policies to control outgoing PIM bootstrap messages. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties • import (Bootstrap) on page 2103 2091 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS family (Bootstrap) Syntax Hierarchy Level Release Information Description Options family (inet | inet6) { export [ policy-names ]; number; [ policy-names ]; } [edit logical-systems logical-system-name protocols pim rp bootstrap], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp bootstrap], [edit protocols pim rp bootstrap], [edit routing-instances routing-instance-name protocols pim rp bootstrap] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure which IP protocol type bootstrap properties to apply. inet—Apply IP version 4 (IPv4) local RP properties. inet6—Apply IPv6 local RP properties. The remaining statements are explained separately. Required Privilege Level Related Documentation 2092 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties Chapter 79: Configuration Statements for IGMP Snooping and Multicast family (Local RP) Syntax Hierarchy Level Release Information Description Options family (inet | inet6) { disable; address address; anycast-pim { local-address address; rp-set { address address ; } } group-ranges { destination-ip-prefix; } hold-time seconds; priority number; } [edit logical-systems logical-system-name protocols pim rp local], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp local], [edit protocols pim rp local], [edit routing-instances routing-instance-name protocols pim rp local] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure which IP protocol type local RP properties to apply. inet—Apply IP version 4 (IPv4) local RP properties. inet6—Apply IPv6 local RP properties. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Junos OS Multicast Protocols Configuration Guide 2093 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS graceful-restart Syntax Hierarchy Level Release Information Description graceful-restart { disable; restart-duration seconds; } [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure PIM sparse mode graceful restart. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Sparse Mode Graceful Restart group Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation 2094 group ip-address; [edit protocols igmp-snooping vlan vlan-id | vlan-name interface interface-name static] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a static multicast group using a valid IP multicast address. None. ip-address —IP address of the multicast group receiving data on an interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 Chapter 79: Configuration Statements for IGMP Snooping and Multicast group Syntax Hierarchy Level Release Information Description group multicast-group-address { exclude; group-count number; group-increment increment; source ip-address { source-count number; source-increment increment; } } [edit logical-systems logical-system-name protocols igmp interface interface-name static], [edit protocols igmp interface interface-name static] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the IGMP multicast group address and (optionally) the source address for the multicast group being statically configured on an interface. NOTE: You must specify a unique address for each group. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling IGMP Static Group Membership 2095 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS group-limit Syntax Hierarchy Level Release Information Description Default Options group-limit limit; [edit protocols igmp-snooping vlan vlan-id | vlan-number interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a limit for the number of multicast groups allowed on the specified interface. After this limit is reached, new reports are ignored and related flows are not flooded on the interface. No group limits are configured. limit —Number that represents the maximum number of multicast groups allowed on the specified interface. Range: 0 through 65535 Required Privilege Level Related Documentation 2096 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 • Configuring IGMP Snooping (J-Web Procedure) on page 2064 • group on page 2094 Chapter 79: Configuration Statements for IGMP Snooping and Multicast group-ranges Syntax Hierarchy Level Release Information Description Default Options group-ranges { destination-ip-prefix; } [edit logical-systems logical-system-name protocols pim rp embedded-rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp embedded-rp], [edit protocols pim rp embedded-rp], [edit protocols pim rp local family (inet | inet6)], [edit protocols pim rp static address address], [edit routing-instances routing-instance-name protocols pim rp embedded-rp], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp static address address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the address ranges of the multicast groups for which this routing device can be an RP. The routing device is eligible to be the RP for all IPv4 or IPv6 groups (224.0.0.0/4 or FF70::/12 to FFF0::/12). destination-mask—Addresses or address ranges for which this routing device can be an RP. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Local PIM RPs • Configuring PIM Embedded RP for IPv6 2097 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS groups Syntax Hierarchy Level Release Information Description Default Options groups group-prefix; [edit protocols igmp-snooping vlan vlan-id | vlan-number data-forwarding source] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the IP address range of the multicast VLAN (MVLAN) source interfaces. Disabled. group-prefix—IP address range of the source group. Each MVLAN must have exactly one groups statement. If there are multiple MVLANs on the switch, their group ranges must be unique. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 hello-interval Syntax Hierarchy Level Release Information Description Options hello-interval seconds; [edit logical-systems logical-system-name protocols pim interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name], [edit protocols pim interface interface-name], [edit routing-instances routing-instance-name protocols pim interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how often the router sends PIM hello packets out of an interface. seconds—Length of time between PIM hello packets. Range: 0 through 255 Default: 30 seconds Required Privilege Level Related Documentation 2098 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Modifying the PIM Hello Interval • hold-time on page 2099 Chapter 79: Configuration Statements for IGMP Snooping and Multicast hold-time Syntax Hierarchy Level Release Information Description Options hold-time seconds; [edit protocols pim rp local family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the time period for which a neighbor is to consider the sending routing device (this routing device) to be operative (up). seconds—Hold time. Range: 0 through 255 Default: 0 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Local PIM RPs 2099 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS igmp-snooping Syntax Hierarchy Level Release Information Description igmp-snooping { traceoptions { file filename ; flag flag (detail | disable | receive | send); } vlan vlan-id | vlan-name { 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 { group ip-address; } } proxy ; query-interval seconds; query-last-member-interval seconds; query-response-interval seconds; robust-count number; } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable and configure IGMP snooping on J-EX Series switches. The remaining statements are explained separately. Default Required Privilege Level Related Documentation 2100 IGMP snooping is enabled by default. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 Chapter 79: Configuration Statements for IGMP Snooping and Multicast immediate-leave Syntax Hierarchy Level Release Information Description immediate-leave; [edit protocols igmp-snooping vlan vlan-id | vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. (Applies only to switches running IGMPv2.) After the switch receives a leave group membership message from a host, immediately remove the group membership from the interface without waiting for any other IGMP messages to be exchanged. NOTE: When configuring this statement, ensure that the IGMP interface has only one IGMP host connected. If more than one IGMPv2 host is connected to the switch through the same interface and one of the hosts sends a leave message, the switch removes all hosts on the interface from the multicast group. The switch loses contact with the hosts in the multicast group that did not send a leave message until they send join requests in response to the next general multicast listener query from the router. Default Required Privilege Level Related Documentation The immediate-leave feature is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 2101 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS immediate-leave Syntax Hierarchy Level Release Information Description immediate-leave; [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. When this statement is enabled on a routing device running IGMP version 2 (IGMPv2), after the routing device receives a leave group membership message from a host associated with the interface, the routing device immediately removes the group membership from the interface and suppresses the sending of any group-specific queries for the multicast group. When this statement is enabled on a routing device running IGMP version 3 (IGMPv3), after the routing device receives a report with the type BLOCK_OLD_SOURCES, the routing device suppresses the sending of group-and-source queries but relies on the Junos OS-supported host tracking mechanism to determine whether or not it removes a particular source group membership from the interface. NOTE: When issuing this command on IGMPv2 interfaces, ensure that the IGMP interface has only one IGMP host connected. If more than one IGMPv2 host is connected to a LAN through the same interface, and one host sends a done message, the routing device removes all hosts on the interface from the multicast group. The routing device loses contact with the hosts that properly remain in the multicast group until they send join requests in response to the next general multicast listener query from the router. Required Privilege Level Related Documentation 2102 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Specifying Immediate-Leave Host Removal for IGMP Chapter 79: Configuration Statements for IGMP Snooping and Multicast import (Bootstrap) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation import [ policy-names ]; [edit logical-systems logical-system-name protocols pim rp bootstrap (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp bootstrap (inet | inet6)], [edit protocols pim rp bootstrap (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp bootstrap (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more import policies to control incoming PIM bootstrap messages. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties • export (Bootstrap) on page 2091 import (PIM) Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation import [ policy-names ]; [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to routes being imported into the routing table from PIM. Use the import statement to filter PIM join messages from entering the network. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Filtering Incoming PIM Join Messages 2103 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS infinity Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation infinity [ policy-names ]; [edit logical-systems logical-system-name protocols pim spt-threshold], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim spt-threshold], [edit protocols pim spt-threshold], [edit routing-instances routing-instance-name protocols pim spt-threshold] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to set the SPT threshold to infinity for a source-group address pair. Use the infinity statement to prevent the last-hop routing device from transitioning from the RPT rooted at the RP to an SPT rooted at the source for that source-group address pair. policy-names—Name of one or more policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the PIM SPT Threshold Policy install Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 2104 install; [edit protocols igmp-snooping vlan vlan-id | vlan-number data-forwarding receiver] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Install forwarding entries in the multicast receiver VLAN. By default, only the multicast VLAN (MVLAN) installs forwarding entries for MVLAN groups. Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 Chapter 79: Configuration Statements for IGMP Snooping and Multicast interface Syntax Hierarchy Level Release Information Description Options interface (all | interface-name) { accept-remote-source; disable; bfd-liveness-detection { authentication { algorithmalgorithm-name; key-chainkey-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; multiplier number; version (0 | 1 | automatic); } family (inet | inet6) { disable; } hello-interval seconds; mode (dense | sparse | sparse-dense); neighbor-policy [ policy-names ]; override-interval milliseconds; priority number; propagation-delay milliseconds; reset-tracking-bit; version version; } [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable PIM on an interface and configure interface-specific properties. interface-name—Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all. For details about specifying interfaces, see the Junos OS Network Interfaces Configuration Guide. The remaining statements are explained separately. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 2105 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Junos OS Multicast Protocols Configuration Guide interface Syntax Hierarchy Level Release Information Description interface interface-name { group-limit limit; multicast-router-interface; static { group ip-address; } } [edit protocols igmp-snooping vlan vlan-id | vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable IGMP snooping on an interface and configure interface-specific properties. The remaining statements are explained separately. Default Options Required Privilege Level Related Documentation 2106 None. interface-name—Name of the interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show igmp-snooping vlans on page 2187 • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 Chapter 79: Configuration Statements for IGMP Snooping and Multicast interface Syntax Hierarchy Level Release Information Description Options interface interface-name { disable; (accounting | no-accounting); group-policy [ policy-names ]; immediate-leave; oif-map map-name; passive; promiscuous-mode; ssm-map ssm-map-name; static { group multicast-group-address { exclude; group-count number; group-increment increment; source ip-address { source-count number; source-increment increment; } } } version version; } [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable IGMP on an interface and configure interface-specific properties. interface-name—Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all. For details about specifying interfaces, see the Junos OS Network Interfaces Configuration Guide. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling IGMP 2107 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS join-load-balance Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 2108 join-load-balance; [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable load balancing of PIM join messages across interfaces and routing devices. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Join Load Balancing • clear pim join-distribution in the Protocols Command Reference Chapter 79: Configuration Statements for IGMP Snooping and Multicast local Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation local { disable; address address; family (inet | inet6) { disable; address address; anycast-pim { local-address address; rp-set { address address ; } } group-ranges { destination-ip-prefix; } hold-time seconds; priority number; } group-ranges { destination-ip-prefix; } hold-time seconds; priority number; } [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. The remaining statements are explained separately. Configure the routing device’s RP properties. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Local PIM RPs 2109 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS local-address Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2110 local-address address; [edit logical-systems logical-system-name protocols pim rp local family (inet | inet6) anycast-pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp local family (inet | inet6) anycast-pim], [edit protocols pim rp local family (inet | inet6) anycast-pim], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6) anycast-pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the routing device’s local address for anycast rendezvous point (RP). If this statement is omitted, the router ID is used as this address. address—Anycast RP IPv4 or IPv6 address, depending on family configuration. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring PIM Anycast with MSDP Chapter 79: Configuration Statements for IGMP Snooping and Multicast mapping-agent-election Syntax Hierarchy Level (mapping-agent-election | no-mapping-agent-election); [edit logical-systems logical-system-name protocols pim rp auto-rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp auto-rp], [edit protocols pim rp auto-rp], [edit routing-instances routing-instance-name protocols pim rp auto-rp] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the routing device’s mapping announcements as a mapping agent. Options mapping-agent-election—Mapping agents do not announce mappings when receiving mapping messages from a higher-addressed mapping agent. no-mapping-agent-election—Mapping agents always announce mappings and do not perform mapping agent election. Default: mapping-agent-election Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Auto-RP maximum-rps Syntax Hierarchy Level Release Information Description Options maximum-rps limit; [edit logical-systems logical-system-name protocols pim rp embedded-rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp embedded-rp], [edit protocols pim rp embedded-rp], [edit routing-instances routing-instance-name protocols pim rp embedded-rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Limit the number of RPs that the routing device acknowledges. limit—Number of RPs. Range: 1 through 500 Default: 100 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Embedded RP for IPv6 2111 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mode Syntax Hierarchy Level Release Information Description Options mode (dense | sparse | sparse-dense); [edit logical-systems logical-system-name protocols pim interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name], [edit protocols pim interface interface-name], [edit routing-instances routing-instance-name protocols pim interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure PIM to operate in sparse, dense, or sparse-dense mode. dense—Operate in dense mode. sparse—Operate in sparse mode. sparse-dense—Operate in sparse-dense mode. Default: sparse Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Dense Mode Properties • Configuring PIM Sparse-Dense Mode Properties • Junos OS Multicast Protocols Configuration Guide multicast-router-interface Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 2112 multicast-router-interface; [edit protocols igmp-snooping vlan vlan-id | vlan-name interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Statically configure an interface as a switching interface toward a multicast router (the interface to receive multicast traffic). Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 Chapter 79: Configuration Statements for IGMP Snooping and Multicast neighbor-policy Syntax Hierarchy Level Release Information Description Options neighbor-policy [ policy-names ]; [edit logical-systems logical-system-name protocols pim interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name], [edit protocols pim interface interface-name], [edit routing-instances routing-instance-name protocols pim interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a PIM interface-level policy to filter neighbor IP addresses. policy-name—Name of the policy that filters neighbor IP addresses. For details about configuring policy statements, see the Junos OS Policy Framework Configuration Guide. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Interface-Level PIM Neighbor Policies 2113 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS pim Syntax 2114 pim { disable; assert-timeout seconds; dense-groups { addresses; } dr-election-on-p2p; export; family (inet | inet6) { disable; } graceful-restart { disable; restart-duration seconds; } import [ policy-names ]; interface interface-name { accept-remote-source; disable; bfd-liveness-detection { authentication { algorithm algorithm-name; key-chain key-chain-name; loose-check; } detection-time { threshold milliseconds; } minimum-interval milliseconds; minimum-receive-interval milliseconds; multiplier number; version (0 | 1 | automatic); } family (inet | inet6) { disable; } hello-interval seconds; mode (dense | sparse | sparse-dense); neighbor-policy [ policy-names ]; override-interval milliseconds; priority number; propagation-delay milliseconds; reset-tracking-bit; version version; } join-load-balance; join-prune-timeout; nonstop-routing; override-interval milliseconds; propagation-delay milliseconds; reset-tracking-bit; rib-group group-name; Chapter 79: Configuration Statements for IGMP Snooping and Multicast rp { auto-rp { (announce | discovery | mapping); (mapping-agent-election | no-mapping-agent-election); } bootstrap { family (inet | inet6) { export [ policy-names ]; import [ policy-names ]; priority number; } } bootstrap-import [ policy-names ]; bootstrap-export [ policy-names ]; bootstrap-priority number; dr-register-policy [ policy-names ]; embedded-rp { group-ranges { destination-ip-prefix; } maximum-rps limit; } local { family (inet | inet6) { address address; anycast-pim { rp-set { address address ; } disable; local-address address; } group-ranges { destination-ip-prefix; } hold-time seconds; priority number; } } rp-register-policy [ policy-names ]; spt-threshold { infinity [ policy-names ]; } static { address address { version version; group-ranges { destination-ip-prefix; } } } } traceoptions { file filename ; flag flag ; } 2115 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS tunnel-devices [ mt-fpc/pic/port ]; } Hierarchy Level Release Information Description [edit logical-systems logical-system-name protocols], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols], [edit protocols], [edit routing-instances routing-instance-name protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable PIM on the routing device. The statements are explained separately. Default Required Privilege Level Related Documentation PIM is disabled on the routing device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Dense Mode Properties • Configuring PIM Dense Mode Properties • Junos OS Multicast Protocols Configuration Guide priority (Bootstrap) Syntax Hierarchy Level Release Information Description Options priority number; [edit logical-systems logical-system-name protocols pim rp bootstrap (inet | inet6)], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp bootstrap (inet | inet6)], [edit protocols pim rp bootstrap (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp bootstrap (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the routing device’s likelihood to be elected as the bootstrap router. number—Routing device’s priority for becoming the bootstrap router. A higher value corresponds to a higher priority. Range: 0 through a 32-bit number Default: 0 (The routing device has the least likelihood of becoming the bootstrap router and sends packets with a priority of 0.) Required Privilege Level Related Documentation 2116 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Bootstrap Properties • bootstrap-priority on page 2086 Chapter 79: Configuration Statements for IGMP Snooping and Multicast priority (PIM Interfaces) Syntax Hierarchy Level Release Information Description Options priority number; [edit logical-systems logical-system-name protocols pim interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name], [edit protocols pim interface interface-name], [edit routing-instances routing-instance-name protocols pim interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the routing device’s likelihood to be elected as the designated router. number—Routing device’s priority for becoming the designated router. A higher value corresponds to a higher priority. Range: 1 through a 32-bit number Default: 1 (The routing device has the least likelihood of becoming the designated router.) Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Interface Priority to Become the PIM Designated Router 2117 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS priority (PIM RPs) Syntax Hierarchy Level Release Information Description Options priority number; [edit protocols pim rp local family (inet | inet6)], [edit routing-instances routing-instance-name protocols pim rp local family (inet | inet6)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure this routing device’s priority for becoming an RP. The bootstrap router uses this field when selecting the list of candidate RPs to send in the bootstrap message. A smaller number increases the likelihood that the routing device becomes the RP for local multicast groups. A priority value of 0 means that bootstrap router can override the group range being advertised by the candidate RP. number—Routing device’s priority for becoming an RP. A lower value corresponds to a higher priority. Range: 0 through 255 Default: 1 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Local PIM RPs promiscuous-mode Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 2118 promiscuous-mode; [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify that the interface accepts IGMP reports from hosts on any subnetwork. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Accepting IGMP Messages from Remote Subnetworks Chapter 79: Configuration Statements for IGMP Snooping and Multicast proxy Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation proxy source-address source-address; [edit protocols igmp-snooping vlan vlan-id | vlan-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify that the VLAN operates in proxy mode. The proxy option is only accepted for a VLAN acting as a data-forwarding source. Disabled. source-address source-address—IP address of the source VLAN to act as proxy. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 query-interval Syntax Hierarchy Level Release Information Description Options query-interval seconds; [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how often the querier router sends general host-query messages. seconds—Time interval. Range: 1 through 1024 Default: 125 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Modifying the IGMP Host-Query Message Interval • query-last-member-interval on page 2120 • query-response-interval on page 2120 2119 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS query-last-member-interval Syntax Hierarchy Level Release Information Description Options query-last-member-interval seconds; [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how often the querier router sends group-specific query messages. seconds—Time interval, in fractions of a second or seconds. Range: 0.1 through 0.9, then in 1-second intervals 1 through 1024 Default: 1 second Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Modifying the IGMP Last-Member Query Interval • query-interval on page 2119 • query-response-interval on page 2120 query-response-interval Syntax Hierarchy Level Release Information Description Options query-response-interval seconds; [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long the querier router waits to receive a response to a host-query message from a host. seconds—The query response interval must be less than the query interval. Range: 1 through 1024 Default: 10 seconds Required Privilege Level Related Documentation 2120 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Modifying the IGMP Query Response Interval • query-interval on page 2119 • query-last-member-interval on page 2120 Chapter 79: Configuration Statements for IGMP Snooping and Multicast receiver Syntax Hierarchy Level Release Information Description receiver { source-vlans vlan-list; install; } [edit protocols igmp-snooping vlan vlan-id | vlan-number data-forwarding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a VLAN as a multicast receiver VLAN of the multicast VLAN (MVLAN). The remaining statements are explained separately. Default Required Privilege Level Related Documentation Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 restart-duration Syntax Hierarchy Level Release Information Description Options restart-duration seconds; [edit logical-systems logical-system-name protocols pim graceful-restart], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim graceful-restart], [edit protocols pim graceful-restart], [edit routing-instances routing-instance-name protocols pim graceful-restart] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the duration of the graceful restart interval. seconds—Time the routing device waits (in seconds) to complete PIM sparse mode graceful restart. Range: 30 through 300 Default: 60 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring PIM Sparse Mode Graceful Restart 2121 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rib-group Syntax Hierarchy Level Release Information Description Options rib-group group-name; [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate a routing table group with PIM. group-name—Name of the routing table group. The name must be one that you defined with the rib-group statement at the [edit routing-options] hierarchy level. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring a PIM RPF Routing Table robust-count Syntax Hierarchy Level Release Information Description Default Options robust-count number; [edit protocols igmp-snooping vlan vlan-id | vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the number of intervals the switch waits before removing a multicast group from the multicast forwarding table. The length of each interval is configured using the query-interval statement. 2 number —Number of intervals the switch waits before timing out a multicast group. Range: 2 through 10 Required Privilege Level Related Documentation 2122 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 Chapter 79: Configuration Statements for IGMP Snooping and Multicast robust-count Syntax Hierarchy Level Release Information Description Options robust-count number; [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Tune the expected packet loss on a subnet. This factor is used to calculate the group member interval, other querier present interval, and last-member query count. number—Robustness variable. Range: 2 through 10 Default: 2 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Modifying the IGMP Robustness Variable 2123 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rp Syntax Hierarchy Level 2124 rp { auto-rp { (announce | discovery | mapping); (mapping-agent-election | no-mapping-agent-election); } bootstrap { family (inet | inet6) { export [ policy-names ]; import [ policy-names ]; priority number; } } bootstrap-export [ policy-names ]; bootstrap-import [ policy-names ]; bootstrap-priority number; dr-register-policy [ policy-names ]; embedded-rp { group-ranges { destination-ip-prefix; } maximum-rps limit; } local { family (inet | inet6) { disable; address address; anycast-pim { rp-set { address address ; } local-address address; } group-ranges { destination-ip-prefix; } hold-time seconds; priority number; } } rp-register-policy [ policy-names ]; static { address address { version version; group-ranges { destination-ip-prefix; } } } } [edit logical-systems logical-system-name protocols pim], Chapter 79: Configuration Statements for IGMP Snooping and Multicast [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Release Information Description Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the routing device as an actual or potential RP. A routing device can be an RP for more than one group. The remaining statements are explained separately. Default Required Privilege Level Related Documentation If you do not include the rp statement, the routing device can never become the RP. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Junos OS Multicast Protocols Configuration Guide rp-register-policy Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation rp-register-policy [ policy-names ]; [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply one or more policies to control incoming PIM register messages. policy-names—Name of one or more import policies. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Register Message Filtering on a PIM RP or DR • dr-register-policy on page 2090 2125 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS rp-set Syntax Hierarchy Level Release Information Description rp-set { address address ; } [edit logical-systems logical-system-name protocols pim local family (inet | inet6) anycast-pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim local family (inet | inet6) anycast-pim], [edit protocols pim local family (inet | inet6) anycast-pim], [edit routing-instances routing-instance-name protocols pim local family (inet | inet6) anycast-pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a set of rendezvous point (RP) addresses for anycast RP. You can configure up to 15 RPs. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring PIM Anycast with MSDP source Syntax Hierarchy Level Release Information Description source { groups group-prefix; } [edit protocols igmp-snooping vlan vlan-number data-forwarding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a VLAN to be a multicast source VLAN (MVLAN). The remaining statement is explained separately. Default Required Privilege Level Related Documentation 2126 Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 Chapter 79: Configuration Statements for IGMP Snooping and Multicast source Syntax Hierarchy Level Release Information Description Options source ip-address { source-count number; source-increment increment; } [edit logical-systems logical-system-name protocols igmp interface interface-name static group multicast-group-address], [edit protocols igmp interface interface-name static group multicast-group-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the IP version 4 (IPv4) unicast source address for the multicast group being statically configured on an interface. ip-address—IPv4 unicast address. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Enabling IGMP Static Group Membership source-vlans Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation source-vlans vlan-list; [edit protocols igmp-snooping vlan vlan-id | vlan-number data-forwarding receiver] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a list of multicast VLANs (MVLANs) from which this multicast receiver VLAN receives multicast traffic. Either all of these MVLANs must be in proxy mode or none of them can be in proxy mode. Disabled. vlan-list—Names of the MVLANs. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • [edit protocols] Configuration Statement Hierarchy on page 48 • Example: Configuring Multicast VLAN Registration on J-EX Series Switches on page 2058 • Configuring Multicast VLAN Registration (CLI Procedure) on page 2068 2127 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS spt-threshold Syntax Hierarchy Level Release Information Description spt-threshold { infinity [ policy-names ]; } [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the SPT threshold to infinity for a source-group address pair. Last-hop multicast routing devices running PIM sparse mode can forward the same stream of multicast packets onto the same LAN through an RPT rooted at the RP or an SPT rooted at the source. By default, last-hop routing devices transition to a direct SPT to the source. You can configure this routing device to set the SPT transition value to infinity to prevent this transition for any source-group address pair. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring the PIM SPT Threshold Policy ssm-map Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2128 ssm-map ssm-map-name; [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply an SSM map to an IGMP interface. ssm-map-name—Name of SSM map. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring SSM Mapping Chapter 79: Configuration Statements for IGMP Snooping and Multicast static Syntax Hierarchy Level Release Information Description static { address address { group-ranges { destination-ip-prefix; } version version; } } [edit logical-systems logical-system-name protocols pim rp], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp], [edit protocols pim rp], [edit routing-instances routing-instance-name protocols pim rp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure static RP addresses. The default static RP address is 224.0.0.0/4. To configure other addresses, include one or more address statements. You can configure a static RP in a logical system only if the logical system is not directly connected to a source. For each static RP address, you can optionally specify the PIM version and the groups for which this address can be the RP. The default PIM version is version 1. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static PIM RPs 2129 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS static (IGMP Snooping) Syntax Hierarchy Level Release Information Description static { group ip-address; } [edit protocols igmp-snooping vlan vlan-id | vlan-name interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Statically define multicast groups on an interface. The remaining statement is explained separately. Default Required Privilege Level Related Documentation No multicast groups are statically defined. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping on J-EX Series Switches (CLI Procedure) on page 2063 static Syntax Hierarchy Level Release Information Description static { group multicast-group-address { exclude; group-count number; group-increment increment; source ip-address { source-count number; source-increment increment; } } } [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Test multicast forwarding on an interface without a receiver host. The remaining statements are explained separately. Required Privilege Level Related Documentation 2130 routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • Enabling IGMP Static Group Membership Chapter 79: Configuration Statements for IGMP Snooping and Multicast traceoptions Syntax Hierarchy Level Release Information Description traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name protocols pim], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim], [edit protocols pim], [edit routing-instances routing-instance-name protocols pim] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure PIM tracing options. To specify more than one tracing operation, include multiple flag statements. Default Options The default PIM trace options are those inherited from the routing protocol's traceoptions statement included at the [edit routing-options] hierarchy level. disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place tracing output in the pim-log file. 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 include the size statement to specify the maximum file size. Range: 2 through 1000 files Default: 2 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. PIM Tracing Flags • assert—Assert messages • bootstrap—Bootstrap messages • cache—Packets in the PIM sparse mode routing cache 2131 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • graft—Graft and graft acknowledgment messages • hello—Hello packets • join—Join messages • mt—Multicast tunnel messages • nsr-synchronization—Nonstop active routing (NSR) synchronization messages • packets—All PIM packets • prune—Prune messages • register—Register and register stop messages • rp—Candidate RP advertisements • all—All tracing operations • general—A combination of the normal and route trace operations • normal—All normal operations Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions • route—Routing table changes • state—State transitions • task—Interface transactions and processing • timer—Timer usage flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: • detail—Detailed trace information • receive—Packets being received • send—Packets being transmitted no-stamp—(Optional) Do not place timestamp information at the beginning of each line in the trace file. Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output. no-world-readable—(Optional) Do not allow users to read the log file. 2132 Chapter 79: Configuration Statements for IGMP Snooping and Multicast replace—(Optional) Replace an existing trace file if there is one. Default: If you do not include this option, tracing output is appended to an existing trace file. 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 trace-file again reaches this 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 must also include the files statement to specify the maximum number of trace files. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 0 KB through the maximum file size supported on your system Default: 1 MB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level Related Documentation routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • Configuring PIM Trace Options • Tracing DVMRP Protocol Traffic • Tracing MSDP Protocol Traffic • Configuring PIM Trace Options 2133 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions Syntax Hierarchy Level Release Information Description Default Options traceoptions { file filename ; flag flag (detail | disable | receive | send); } [edit protocols igmp-snooping] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for IGMP snooping. The traceoptions feature is disabled by default. file filename —Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. 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 ( xk to specify KB, xm to specify MB, or xg to specify gigabytes), at which point the oldest trace file is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the size option. Range: 2 through 1000 Default: 3 files flag flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: 2134 • all—All tracing operations. • general—Trace general IGMP snooping protocol events. • leave—Trace leave group messages (IGMPv2 only). • normal—Trace normal IGMP snooping protocol events. • packets—Trace all IGMP packets. • policy—Trace policy processing. • query—Trace IGMP membership query messages. • report—Trace membership report messages. • route—Trace routing information. • state—Trace IGMP state transitions. • task—Trace routing protocol task processing. • timer—Trace routing protocol timer processing. Chapter 79: Configuration Statements for IGMP Snooping and Multicast match regex —(Optional) Refine the output to include lines that contain the regular expression. no-world-readable—(Optional) Restricted file access to the user who created the file. 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 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 also must specify a maximum file size with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify gigabytes Range: 10 KB through 1 gigabytes Default: 128 KB world-readable—(Optional) Enable unrestricted file access. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IGMP Snooping on J-EX Series Switches on page 2055 • Configuring IGMP Snooping (CLI Procedure) on page 2063 2135 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions Syntax Hierarchy Level Release Information Description traceoptions { file filename ; flag flag ; } [edit logical-systems logical-system-name protocols igmp], [edit protocols igmp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure IGMP tracing options. To specify more than one tracing operation, include multiple flag statements. To trace the paths of multicast packets, use the mtrace command, as described in the Junos OS System Basics and Services Command Reference. Default Options The default IGMP trace options are those inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level. disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place tracing output in the file igmp-log. 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 include the size statement to specify the maximum file size. Range: 2 through 1000 files Default: 2 files flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. IGMP Tracing Flags 2136 • leave—Leave group messages (for IGMP version 2 only). • mtrace—Mtrace packets. Use the mtrace command to troubleshoot the software. • packets—All IGMP packets. Chapter 79: Configuration Statements for IGMP Snooping and Multicast • query—IGMP membership query messages, including general and group-specific queries. • report—Membership report messages. Global Tracing Flags • all—All tracing operations • general—A combination of the normal and route trace operations • normal—All normal operations Default: If you do not specify this option, only unusual or abnormal operations are traced. • policy—Policy operations and actions • route—Routing table changes • state—State transitions • task—Interface transactions and processing • timer—Timer usage flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers: • detail—Detailed trace information • receive—Packets being received • send—Packets being transmitted no-stamp—(Optional) Do not place timestamp information at the beginning of each line in the trace file. Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output. no-world-readable—(Optional) Do not allow users to read the log file. replace—(Optional) Replace an existing trace file if there is one. Default: If you do not include this option, tracing output is appended to an existing trace file. 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 trace-file again reaches this 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. 2137 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS If you specify a maximum file size, you must also include the files statement to specify the maximum number of trace files. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB Range: 10 KB through the maximum file size supported on your system Default: 1 MB world-readable—(Optional) Allow any user to read the log file. Required Privilege Level Related Documentation routing and trace—To view this statement in the configuration. routing-control and trace-control—To add this statement to the configuration. • Tracing IGMP Protocol Traffic version Syntax Hierarchy Level Release Information Description Options version version; [edit logical-systems logical-system-name protocols igmp interface interface-name], [edit protocols igmp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the version of IGMP. version—IGMP version number. Range: 1, 2, or 3 Default: IGMP version 2 Required Privilege Level Related Documentation 2138 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Changing the IGMP Version Chapter 79: Configuration Statements for IGMP Snooping and Multicast version (PIM) Syntax Hierarchy Level Release Information Description Options version version; [edit logical-systems logical-system-name protocols pim interface interface-name], [edit logical-systems logical-system-name protocols pim rp static address address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim rp static address address], [edit protocols pim interface interface-name], [edit protocols pim rp static address address], [edit routing-instances routing-instance-name protocols pim interface interface-name], [edit routing-instances routing-instance-name protocols pim rp static address address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the version of PIM. version—PIM version number. Range: 1 or 2 Default: PIM version 2 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Changing the PIM Version 2139 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan Syntax Hierarchy Level Release Information Description vlan (vlan-id | vlan-name) { 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 { group ip-address; } } proxy ; query-interval seconds; query-last-member-interval seconds; query-response-interval seconds; robust-count number; } [edit protocols igmp-snooping] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure IGMP snooping parameters for a VLAN. The remaining statements are explained separately. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. For IGMP snooping, secondary private VLANs are not listed. Default Options IGMP snooping options apply to the specified VLAN. vlan-id—Numeric tag for a VLAN. Range: 0 through 4095. Tags 0 and 4095 are reserved by the Junos OS, and you should not configure them. vlan-name—Name of a VLAN. 2140 Chapter 79: Configuration Statements for IGMP Snooping and Multicast Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring IGMP Snooping (CLI Procedure) on page 2063 • IGMP Snooping on J-EX Series Switches Overview on page 2047 2141 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2142 CHAPTER 80 Operational Mode Commands for IGMP Snooping and Multicast 2143 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear igmp membership Syntax Syntax (J-EX Series Switch) Release Information Description Options clear igmp membership clear igmp membership Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Internet Group Management Protocol (IGMP) group members. none—Clear all IGMP members on all interfaces and for all address ranges. group address-range—(Optional) Clear all IGMP members that are in a particular address range. An example of a range is 224.2/16. If you omit the destination prefix length, the default is /32. interface interface-name—(Optional) Clear all IGMP group members on an interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear igmp membership clear • show igmp group on page 2171 • show igmp interface on page 2175 clear igmp membership on page 2144 clear igmp membership interface on page 2145 clear igmp membership group on page 2145 See show igmp group for an explanation of output fields. The following sample output displays IGMP group information before and after the clear igmp membership command is entered: user@host> show igmp group Interface Group so-0/0/0 224.2.127.253 so-0/0/0 224.2.127.254 so-0/0/0 239.255.255.255 so-0/0/0 224.1.127.255 local 224.0.0.6 local 224.0.0.5 local 224.2.127.254 local 239.255.255.255 local 224.0.0.2 2144 Last Reported 10.1.128.1 10.1.128.1 10.1.128.1 10.1.128.1 (null) (null) (null) (null) (null) Timeout 186 186 187 188 0 0 0 0 0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast local 224.0.0.13 (null) 0 user@host> clear igmp membership Clearing Group Membership Info for so-0/0/0 Clearing Group Membership Info for so-1/0/0 Clearing Group Membership Info for so-2/0/0 user@host> show igmp group Interface Group local 224.0.0.6 local 224.0.0.5 local 224.2.127.254 local 239.255.255.255 local 224.0.0.2 local 224.0.0.13 clear igmp membership interface Last Reported (null) (null) (null) (null) (null) (null) Timeout 0 0 0 0 0 0 The following sample output displays IGMP group information before and after the clear igmp membership interface command is issued: user@host> show igmp group Interface Group so-0/0/0 224.2.127.253 so-0/0/0 239.255.255.255 so-0/0/0 224.1.127.255 so-0/0/0 224.2.127.254 local 224.0.0.6 local 224.0.0.5 local 224.2.127.254 local 239.255.255.255 local 224.0.0.2 local 224.0.0.13 Last Reported 10.1.128.1 10.1.128.1 10.1.128.1 10.1.128.1 (null) (null) (null) (null) (null) (null) Timeout 210 210 215 216 0 0 0 0 0 0 user@host> clear igmp membership interface so-0/0/0 Clearing Group Membership Info for so-0/0/0 user@host> show igmp group Interface Group local 224.0.0.6 local 224.0.0.5 local 224.2.127.254 local 239.255.255.255 local 224.0.0.2 local 224.0.0.13 clear igmp membership group Last Reported (null) (null) (null) (null) (null) (null) Timeout 0 0 0 0 0 0 The following sample output displays IGMP group information before and after the clear igmp membership group command is entered: user@host> show igmp group Interface Group so-0/0/0 224.2.127.253 so-0/0/0 239.255.255.255 so-0/0/0 224.1.127.255 so-0/0/0 224.2.127.254 local 224.0.0.6 local 224.0.0.5 local 224.2.127.254 local 239.255.255.255 Last Reported 10.1.128.1 10.1.128.1 10.1.128.1 10.1.128.1 (null) (null) (null) (null) Timeout 210 210 215 216 0 0 0 0 2145 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS local local 224.0.0.2 224.0.0.13 (null) (null) 0 0 user@host> clear igmp membership group 239.225/16 Clearing Group Membership Range 239.225.0.0/16 on so-0/0/0 Clearing Group Membership Range 239.225.0.0/16 on so-1/0/0 Clearing Group Membership Range 239.225.0.0/16 on so-2/0/0 2146 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast user@host> show igmp group Interface Group so-0/0/0 224.1.127.255 so-0/0/0 224.2.127.254 so-0/0/0 224.2.127.253 local 224.0.0.6 local 224.0.0.5 local 224.2.127.254 local 239.255.255.255 local 224.0.0.2 local 224.0.0.13 Last Reported 10.1.128.1 10.1.128.1 10.1.128.1 (null) (null) (null) (null) (null) (null) Timeout 231 233 236 0 0 0 0 0 0 2147 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear igmp statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear igmp statistics clear igmp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Internet Group Management Protocol (IGMP) statistics. none—Clear IGMP statistics on all interfaces. interface interface-name—(Optional) Clear IGMP statistics for the specified interface only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear igmp statistics clear • show igmp statistics on page 2178 clear igmp statistics on page 2148 See show igmp statistics for an explanation of output fields. The following sample output displays IGMP statistics information before and after the clear igmp statistics command is entered: user@host> show igmp statistics IGMP packet statistics for all interfaces IGMP Message type Received Sent Membership Query 8883 459 V1 Membership Report 0 0 DVMRP 19784 35476 PIM V1 18310 0 Cisco Trace 0 0 V2 Membership Report 0 0 Group Leave 0 0 Mtrace Response 0 0 Mtrace Request 0 0 Domain Wide Report 0 0 V3 Membership Report 0 0 Other Unknown types IGMP v3 unsupported type IGMP v3 source required for SSM IGMP v3 mode not applicable for SSM IGMP Global Statistics Bad Length Bad Checksum 2148 0 0 Rx errors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Bad Receive If Rx non-local 0 1227 user@host> clear igmp statistics user@host> show igmp statistics IGMP packet statistics for all interfaces IGMP Message type Received Sent Membership Query 0 0 V1 Membership Report 0 0 DVMRP 0 0 PIM V1 0 0 Cisco Trace 0 0 V2 Membership Report 0 0 Group Leave 0 0 Mtrace Response 0 0 Mtrace Request 0 0 Domain Wide Report 0 0 V3 Membership Report 0 0 Other Unknown types IGMP v3 unsupported type IGMP v3 source required for SSM IGMP v3 mode not applicable for SSM IGMP Global Statistics Bad Length 0 Bad Checksum 0 Bad Receive If 0 Rx non-local 0 Rx errors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2149 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear igmp-snooping membership Syntax Release Information Description Options clear igmp-snooping membership Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IGMP snooping membership information. vlan vlan-id —Numeric tag identifier of the VLAN. vlan vlan-name —Name of the VLAN. Required Privilege Level Related Documentation List of Sample Output clear igmp-snooping membership 2150 view • show igmp-snooping membership on page 2181 clear igmp-snooping membership on page 2150 user@switch> clear igmp-snooping membership vlan employee-vlan Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast clear igmp-snooping statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output clear igmp-snooping statistics clear igmp-snooping statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IGMP snooping statistics. view • show igmp-snooping statistics on page 2185 clear igmp-snooping statistics on page 2151 user@switch> clear igmp-snooping statistics 2151 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear multicast bandwidth-admission Syntax Release Information Description Options clear multicast bandwidth-admission Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reapply IP multicast bandwidth admissions. none—Reapply multicast bandwidth admissions for all IPv4 forwarding entries in the master routing instance. group group-address—(Optional) Reapply multicast bandwidth admissions for the specified group. inet—(Optional) Reapply multicast bandwidth admission settings for IPv4 flows. inet6—(Optional) Reapply multicast bandwidth admission settings for IPv6 flows. instance instance-name—(Optional) Reapply multicast bandwidth admission settings for the specified instance. If you do not specify an instance, the command applies to the master routing instance. interface interface-name—(Optional) Examines the corresponding outbound interface in the relevant entries and acts as follows: • If the interface is congested, and it was admitted previously, it is removed. • If the interface was rejected previously, the clear multicast bandwidth-admission command enables the interface to be admitted as long as enough bandwidth exists on the interface. • If you do not specify an interface, issuing the clear multicast bandwidth-admission command readmits any previously rejected interface for the relevant entries as long as enough bandwidth exists on the interface. To manually reject previously admitted outbound interfaces, you must specify the interface. source source-address—(Optional) Use with the group option to reapply multicast bandwidth admission settings for the specified (source, group) entry. Required Privilege Level Related Documentation List of Sample Output 2152 clear • show multicast interface on page 2191 clear multicast bandwidth-admission on page 2153 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Output Fields clear multicast bandwidth-admission When you enter this command, you are provided feedback on the status of your request. user@host> clear multicast bandwidth-admission 2153 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear multicast scope Syntax Syntax (J-EX Series Switch) Release Information Description Options clear multicast scope clear multicast scope Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IP multicast scope statistics. none—(Same as logical-system all) Clear multicast scope statistics. inet—(Optional) Clear multicast scope statistics for IPv4 family addresses. inet6—(Optional) Clear multicast scope statistics for IPv6 family addresses. interface interface-name—(Optional) Clear multicast scope statistics on a specific interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear multicast scope 2154 clear • show multicast scope on page 2207 clear multicast scope on page 2154 When you enter this command, you are provided feedback on the status of your request. user@host> clear multicast scope Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast clear multicast sessions Syntax Syntax (J-EX Series Switch) Release Information Description Options clear multicast sessions clear multicast sessions Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IP multicast sessions. none—(Same as logical-system all) Clear multicast sessions. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. regular-expression—(Optional) Clear only multicast sessions that contain the specified regular expression. Required Privilege Level Related Documentation List of Sample Output Output Fields clear multicast sessions clear • show multicast sessions on page 2209 clear multicast sessions on page 2155 When you enter this command, you are provided feedback on the status of your request. user@host> clear multicast sessions 2155 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear multicast statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear multicast statistics clear multicast statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear IP multicast statistics. none—Clear multicast statistics for all supported address families on all interfaces. inet—(Optional) Clear multicast statistics for IPv4 family addresses. inet6—(Optional) Clear multicast statistics for IPv6 family addresses. instance instance-name—(Optional) Clear multicast statistics for the specified instance. interface interface-name—(Optional) Clear multicast statistics on a specific interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear multicast statistics 2156 clear • show multicast statistics clear multicast statistics on page 2156 When you enter this command, you are provided feedback on the status of your request. user@host> clear multicast statistics Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast clear pim join Syntax Syntax (J-EX Series Switch) Release Information Description Options clear pim join clear pim join Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear the Protocol Independent Multicast (PIM) join and prune states. none—Clear the PIM join and prune states for all groups, family addresses, and instances. group-address—(Optional) Clear the PIM join and prune states for a group address. inet | inet6—(Optional) Clear the PIM join and prune states for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Clear the join and prune states for a specific PIM-enabled routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information Required Privilege Level Related Documentation List of Sample Output The clear pim join command cannot be used to clear the PIM join and prune state on a backup Routing Engine when nonstop active routing is enabled. clear • show pim join on page 2219 clear pim join on page 2157 Output Fields When you enter this command, you are provided feedback on the status of your request. clear pim join user@host> clear pim join 2157 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear pim register Syntax Syntax (J-EX Series Switch) Release Information Description Options clear pim register clear pim register Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Protocol Independent Multicast (PIM) register message counters. none—Clear PIM register message counters for all family addresses, instances, and interfaces. inet | inet6—(Optional) Clear PIM register message counters for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Clear register message counters for a specific PIM-enabled routing instance. interface interface-name—(Optional) Clear PIM register message counters for a specific interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields clear pim register 2158 The clear pim register command cannot be used to clear the PIM register state on a backup Routing Engine when nonstop active routing is enabled. clear • show pim statistics on page 2235 clear pim register on page 2158 When you enter this command, you are provided feedback on the status of your request. user@host> clear pim register Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast clear pim statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear pim statistics clear pim statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Protocol Independent Multicast (PIM) statistics. none—Clear PIM statistics for all family addresses, instances, and interfaces. inet | inet6—(Optional) Clear PIM statistics for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Clear statistics for a specific PIM-enabled routing instance. interface interface-name—(Optional) Clear PIM statistics for a specific interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields clear pim statistics The clear pim statistics command cannot be used to clear the PIM statistics on a backup Routing Engine when nonstop active routing is enabled. clear • show pim statistics on page 2235 clear pim statistics on page 2159 See show pim statistics for an explanation of output fields. The following sample output displays PIM statistics before and after the clear pim statistics command is entered: user@host> show pim statistics PIM statistics on all interfaces: PIM Message type Received Hello 0 Register 0 Register Stop 0 Join Prune 0 Bootstrap 0 Sent 0 0 0 0 0 Rx errors 0 0 0 0 0 2159 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Assert 0 0 Graft 0 0 Graft Ack 0 0 Candidate RP 0 0 V1 Query 2111 4222 V1 Register 0 0 V1 Register Stop 0 0 V1 Join Prune 14200 13115 V1 RP Reachability 0 0 V1 Assert 0 0 V1 Graft 0 0 V1 Graft Ack 0 0 PIM statistics summary for all interfaces: Unknown type 0 V1 Unknown type 0 Unknown Version 0 Neighbor unknown 0 Bad Length 0 Bad Checksum 0 Bad Receive If 0 Rx Intf disabled 2007 Rx V1 Require V2 0 Rx Register not RP 0 RP Filtered Source 0 Unknown Reg Stop 0 Rx Join/Prune no state 1040 Rx Graft/Graft Ack no state 0 ... user@host> clear pim statistics user@host> show pim statistics PIM statistics on all interfaces: PIM Message type Received Hello 0 Register 0 Register Stop 0 Join Prune 0 Bootstrap 0 Assert 0 Graft 0 Graft Ack 0 Candidate RP 0 V1 Query 1 V1 Register 0 ... 2160 Sent 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Rx errors 0 0 0 0 0 0 0 0 0 0 0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast mtrace Syntax Release Information Description Options mtrace source Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display trace information about an IP multicast path. source—Source hostname or address. routing-instance routing-instance-name—(Optional) Trace a particular routing instance. Additional Information Required Privilege Level List of Sample Output Output Fields The mtrace command for multicast traffic is similar to the traceroute command used for unicast traffic. Unlike traceroute, mtrace traces traffic backwards, from the receiver to the source. view mtrace source on page 2162 Table 259 on page 2161 describes the output fields for the mtrace command. Output fields are listed in the approximate order in which they appear. Table 259: mtrace Output Fields Field Name Field Description Mtrace from IP address of the receiver. to IP address of the source. via group IP address of the multicast group (if any). Querying full reverse path Indicates the full reverse path query has begun. number-of-hops Number of hops from the source to the named router or switch. router-name Name of the router or switch for this hop. address Address of the router or switch for this hop. protocol Protocol used (for example, PIM). Round trip time Average round-trip time, in milliseconds (ms). total ttl of Time-to-live (TTL) threshold. 2161 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mtrace source 2162 user@host> mtrace 192.1.4.2 Mtrace from 192.1.4.2 to 192.1.1.2 via group 0.0.0.0 Querying full reverse path... * * 0 routerA.lab.mycompany.net (192.1.1.2) -1 routerB.lab.mycompany.net (192.1.2.2) PIM thresh^ 1 -2 routerC.lab.mycompany.net (192.1.3.2) PIM thresh^ 1 -3 hostA.lab.mycompany.net (192.1.4.2) Round trip time 2 ms; total ttl of 2 required. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast mtrace from-source Syntax Release Information Description Options mtrace from-source source source Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display trace information about an IP multicast path from a source to this router or switch. If you specify a group address with this command, the Junos OS returns additional information, such as packet rates and losses. brief | detail—(Optional) Display the specified level of output. extra-hops extra-hops—(Optional) Number of hops to take after reaching a nonresponsive router. You can specify a number between 0 and 255. group group—(Optional) Group address for which to trace the path. The default group address is 0.0.0.0. interval interval—(Optional) Number of seconds to wait before gathering statistics again. The default value is 10 seconds. loop—(Optional) Loop indefinitely, displaying rate and loss statistics. max-hops max-hops—(Optional) Maximum hops to trace toward source. The range of values is 0 through 255. The default value is 32 hops. max-queries max-queries—(Optional) Maximum number of query attempts for any hop. The range of values is 1 through 32. The default is 3. multicast-response—(Optional) Always request the response using multicast. no-resolve—(Optional) Do not attempt to display addresses symbolically. no-router-alert—(Optional) Do not use the router-alert IP option. response response—(Optional) Send trace response to a host or multicast address. routing-instance routing-instance-name—(Optional) Trace a particular routing instance. 2163 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS source source—Source hostname or address. ttl ttl—(Optional) IP time-to-live (TTL) value. You can specify a number between 0 and 255. Local queries to the multicast group use a value of 1. Otherwise, the default value is 127. unicast-response—(Optional) Always request the response using unicast. wait-time wait-time—(Optional) Number of seconds to wait for a response. The default value is 3. Required Privilege Level List of Sample Output Output Fields view mtrace from-source on page 2165 Table 260 on page 2164 describes the output fields for the mtrace from-source command. Output fields are listed in the approximate order in which they appear. Table 260: mtrace from-source Output Fields 2164 Field Name Field Description Mtrace from IP address of the receiver. to IP address of the source. via group IP address of the multicast group (if any). Querying full reverse path Indicates the full reverse path query has begun. number-of-hops Number of hops from the source to the named router or switch. router-name Name of the router or switch for this hop. address Address of the router or switch for this hop. protocol Protocol used (for example, PIM). Round trip time Average round-trip time, in milliseconds (ms). total ttl of Time-to-live (TTL) threshold. source Source address. Response Dest Response destination address. Overall Average packet rate for all traffic at each hop. Packet Statistics for Traffic From Number of packets lost, number of packets sent, percentage of packets lost, and average packet rate at each hop. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 260: mtrace from-source Output Fields (continued) mtrace from-source Field Name Field Description Receiver IP address receiving the multicast. Query source IP address sending the mtrace query. user@host> mtrace from-source source 192.1.4.2 group 225.1.1.1 Mtrace from 192.1.4.2 to 192.1.1.2 via group 225.1.1.1 Querying full reverse path... * * 0 routerA.lab.mycompany.net (192.1.1.2) -1 routerB.lab.mycompany.net (192.1.2.2) PIM thresh^ 1 -2 routerC.lab.mycompany.net (192.1.3.2) PIM thresh^ 1 -3 hostA.lab.mycompany.net (192.1.4.2) Round trip time 2 ms; total ttl of 2 required. Waiting to accumulate statistics...Results after 10 seconds: Source Response Dest Overall Packet Statistics For Traffic From 192.1.4.2 192.1.1.2 Packet 192.1.4.2 To 225.1.1.1 v __/ rtt 2 ms Rate Lost/Sent = Pct Rate 192.1.2.1 192.1.3.2 routerC.lab.mycompany.net v ^ ttl 2 0/0 = -0 pps 192.1.4.1 192.1.2.2 routerB.lab.mycompany.net v \__ ttl 3 ?/0 0 pps 192.1.1.2 192.1.1.2 Receiver Query Source 2165 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mtrace monitor Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields mtrace monitor Command introduced before Junos OS Release 10.2 for J-EX Series switches. Listen passively for IP multicast responses.To exit mtrace monitor, type Ctrl+c. none—Trace the master instance. view mtrace monitor on page 2167 Table 261 on page 2166 describes the output fields for the mtrace monitor command. Output fields are listed in the approximate order in which they appear. Table 261: mtrace monitor Output Fields 2166 Field Name Field Description Mtrace query at Date and time of the query. by Address of the host issuing the query. resp to Response destination. qid Query ID number. packet from...to IP address of the query source and default group destination. from...to IP address of the multicast source and the response address. via group IP address of the group to trace. mxhop Maximum hop setting. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast mtrace monitor user@host> mtrace monitor Mtrace query at Oct 22 13:36:14 by 192.1.3.2, resp to 224.0.1.32, qid 74a5b8 packet from 192.1.3.2 to 224.0.0.2 from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60) Mtrace query at Oct 22 13:36:17 by 192.1.3.2, resp to 224.0.1.32, qid 1d07ba packet from 192.1.3.2 to 224.0.0.2 from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60) Mtrace query at Oct 22 13:36:20 by 192.1.3.2, resp to same, qid 2fea1d packet from 192.1.3.2 to 224.0.0.2 from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60) Mtrace query at Oct 22 13:36:30 by 192.1.3.2, resp to same, qid 7c88ad packet from 192.1.3.2 to 224.0.0.2 from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60) 2167 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mtrace to-gateway Syntax Release Information Description Options mtrace to-gateway gateway gateway Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display trace information about a multicast path from this router or switch to a gateway router or switch. gateway gateway—Send the trace query to a gateway multicast address. brief | detail—(Optional) Display the specified level of output. extra-hops extra-hops—(Optional) Number of hops to take after reaching a nonresponsive router or switch. You can specify a number between 0 and 255. group group—(Optional) Group address for which to trace the path. The default group address is 0.0.0.0. interface interface-name—(Optional) Source address for sending the trace query. interval interval—(Optional) Number of seconds to wait before gathering statistics again. The default value is 10. loop—(Optional) Loop indefinitely, displaying rate and loss statistics. max-hops max-hops—(Optional) Maximum hops to trace toward the source. You can specify a number between 0 and 255.. The default value is 32. max-queries max-queries—(Optional) Maximum number of query attempts for any hop. You can specify a number between 0 and 255.. The default value is 3. multicast-response—(Optional) Always request the response using multicast. no-resolve—(Optional) Do not attempt to display addresses symbolically. no-router-alert—(Optional) Do not use the router-alert IP option. 2168 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast response response—(Optional) Send trace response to a host or multicast address. routing-instance routing-instance-name—(Optional) Trace a particular routing instance. ttl ttl—(Optional) IP time-to-live value. You can specify a number between 0 and 225. Local queries to the multicast group use TTL 1. Otherwise, the default value is 127. unicast-response—(Optional) Always request the response using unicast. wait-time wait-time—(Optional) Number of seconds to wait for a response. The default value is 3. Required Privilege Level List of Sample Output Output Fields view mtrace to-gateway on page 2169 Table 262 on page 2169 describes the output fields for the mtrace to-gateway command. Output fields are listed in the approximate order in which they appear. Table 262: mtrace to-gateway Output Fields mtrace to-gateway Field Name Field Description Mtrace from IP address of the receiver. to IP address of the source. via group IP address of the multicast group (if any). Querying full reverse path Indicates the full reverse path query has begun. number-of-hops Number of hops from the source to the named router or switch. router-name Name of the router or switch for this hop. address Address of the router or switch for this hop. protocol Protocol used (for example, PIM). Round trip time Average round-trip time, in milliseconds (ms). total ttl of Time-to-live (TTL) threshold. user@host> mtrace to-gateway gateway 192.1.3.2 group 225.1.1.1 interface 192.1.1.73 brief Mrace from 192.1.1.73 to 192.1.1.2 via group 225.1.1.1 Querying full reverse path... * * 0 routerA.lab.mycompany.net (192.1.1.2) -1 routerA.lab.mycompany.net (192.1.1.2) PIM thresh^ 1 -2 routerB.lab.mycompany.net (192.1.2.2) PIM thresh^ 1 2169 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS -3 routerC.lab.mycompany.net (192.1.3.2) PIM Round trip time 2 ms; total ttl of 3 required. 2170 thresh^ 1 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp group Syntax Syntax (J-EX Series Switch) Release Information Description Options show igmp group show igmp group Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Internet Group Management Protocol (IGMP) group membership information. none—Display standard information about membership for all IGMP groups. brief | detail—(Optional) Display the specified level of output. group-name—(Optional) Display group membership for the specified IP address only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear igmp membership on page 2144 show igmp group (Include Mode) on page 2172 show igmp group (Exclude Mode) on page 2173 show igmp group brief on page 2173 show igmp group detail on page 2173 Table 263 on page 2171 describes the output fields for the show igmp group command. Output fields are listed in the approximate order in which they appear. Table 263: show igmp group Output Fields Field Name Field Description Level of Output Interface Name of the interface that received the IGMP membership report. A name of local indicates that the local routing device joined the group itself. All levels Group Group address. All levels Group Mode Mode the SSM group is operating in: Include or Exclude. All levels Source Source address. All levels 2171 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 263: show igmp group Output Fields (continued) Field Name Field Description Level of Output Source timeout Time remaining until the group traffic is no longer forwarded. The timer is refreshed when a listener in include mode sends a report. A group in exclude mode or configured as a static group displays a zero timer. detail Last reported by Address of the host that last reported membership in this group. All levels Timeout Time remaining until the group membership is removed. brief none Group timeout Time remaining until a group in exclude mode moves to include mode. The timer is refreshed when a listener in exclude mode sends a report. A group in include mode or configured as a static group displays a zero timer. detail Type Type of group membership: All levels • Dynamic—Host reported the membership. • Static—Membership is configured. show igmp group (Include Mode) 2172 user@host> show igmp group Interface: t1-0/1/0.0 Group: 232.1.1.1 Group mode: Include Source: 10.0.0.2 Last reported by: 10.9.5.2 Timeout: 24 Type: Dynamic Group: 232.1.1.1 Group mode: Include Source: 10.0.0.3 Last reported by: 10.9.5.2 Timeout: 24 Type: Dynamic Group: 232.1.1.1 Group mode: Include Source: 10.0.0.4 Last reported by: 10.9.5.2 Timeout: 24 Type: Dynamic Group: 232.1.1.2 Group mode: Include Source: 10.0.0.4 Last reported by: 10.9.5.2 Timeout: 24 Type: Dynamic Interface: t1-0/1/1.0 Interface: ge-0/2/2.0 Interface: ge-0/2/0.0 Interface: local Group: 224.0.0.2 Source: 0.0.0.0 Last reported by: Local Timeout: 0 Type: Dynamic Group: 224.0.0.22 Source: 0.0.0.0 Last reported by: Local Timeout: 0 Type: Dynamic Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp group (Exclude Mode) user@host> show igmp group Interface: t1-0/1/0.0 Interface: t1-0/1/1.0 Interface: ge-0/2/2.0 Interface: ge-0/2/0.0 Interface: local Group: 224.0.0.2 Source: 0.0.0.0 Last reported by: Local Timeout: 0 Type: Dynamic Group: 224.0.0.22 Source: 0.0.0.0 Last reported by: Local Timeout: 0 Type: Dynamic show igmp group brief The output for the show igmp group brief command is identical to that for the show igmp group command. show igmp group detail user@host> show igmp group detail Interface: t1-0/1/0.0 Group: 232.1.1.1 Group mode: Include Source: 10.0.0.2 Source timeout: 12 Last reported by: 10.9.5.2 Group timeout: 0 Type: Group: 232.1.1.1 Group mode: Include Source: 10.0.0.3 Source timeout: 12 Last reported by: 10.9.5.2 Group timeout: 0 Type: Group: 232.1.1.1 Group mode: Include Source: 10.0.0.4 Source timeout: 12 Last reported by: 10.9.5.2 Group timeout: 0 Type: Group: 232.1.1.2 Group mode: Include Source: 10.0.0.4 Source timeout: 12 Last reported by: 10.9.5.2 Group timeout: 0 Type: Interface: t1-0/1/1.0 Interface: ge-0/2/2.0 Interface: ge-0/2/0.0 Interface: local Group: 224.0.0.2 Group mode: Exclude Source: 0.0.0.0 Source timeout: 0 Last reported by: Local Group timeout: 0 Type: Group: 224.0.0.22 Group mode: Exclude Source: 0.0.0.0 Source timeout: 0 Dynamic Dynamic Dynamic Dynamic Dynamic 2173 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Last reported by: Local Group timeout: 0 Type: Dynamic 2174 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp interface Syntax Syntax (J-EX Series Switch) Release Information Description Options show igmp interface show igmp interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Internet Group Management Protocol (IGMP)-enabled interfaces. none—Display standard information about all IGMP-enabled interfaces. brief | detail—(Optional) Display the specified level of output. interface-name—(Optional) Display information about the specified IGMP-enabled interface only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear igmp membership on page 2144 show igmp interface on page 2177 show igmp interface brief on page 2177 show igmp interface detail on page 2177 Table 264 on page 2175 describes the output fields for the show igmp interface command. Output fields are listed in the approximate order in which they appear. Table 264: show igmp interface Output Fields Field Name Field Description Level of Output Interface Name of the interface. All levels State State of the interface: Up or Down. All levels Querier Address of the routing device that has been elected to send membership queries. All levels Timeout How long until the IGMP querier is declared to be unreachable, in seconds. All levels Version IGMP version being used on the interface: 1 , 2 , or 3. All levels 2175 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 264: show igmp interface Output Fields (continued) Field Name Field Description Level of Output Groups Number of groups on the interface. All levels Immediate Leave State of the immediate leave option: All levels • On—Indicates that the router removes a host from the multicast group as soon as the router receives a leave group message from a host associated with the interface. • Off—Indicates that after receiving a leave group message, instead of removing a host from the multicast group immediately, the router sends a group query to determine if another receiver responds. Promiscuous Mode State of the promiscuous mode option: • All levels On—Indicates that the router can accept IGMP reports from subnetworks that are not associated with its interfaces. • Off—Indicates that the router can accept IGMP reports only from subnetworks that are associated with its interfaces. Passive State of the passive mode option: • All levels On—Indicates that the router can run IGMP on the interface but not send or receive control traffic such as IGMP reports, queries, and leaves. • Off—Indicates that the router can run IGMP on the interface and send or receive control traffic such as IGMP reports, queries, and leaves. The passive statement enables you to selectively activate up to two out of a possible three available query or control traffic options. When enabled, the following options appear after the on state declaration: • send-general-query—The interface sends general queries. • send-group-query—The interface sends group-specific and group-source-specific queries. • allow-receive—The interface receives control traffic OIF map Name of the OIF map associated to the interface. All levels SSM map Name of the source-specific multicast (SSM) map (if configured) used on the interface. All levels Configured Parameters Information configured by the user: All levels • IGMP Query Interval—Interval (in seconds) at which this router sends membership queries when it is the querier. • IGMP Query Response Interval—Time (in seconds) that the router waits for a report in response to a general query. • IGMP Last Member Query Interval—Time (in seconds) that the router waits for a report in response to a group-specific query. • 2176 IGMP Robustness Count—Number of times the router retries a query. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 264: show igmp interface Output Fields (continued) Field Name Field Description Level of Output Derived Parameters Derived information: All levels • IGMP Membership Timeout—Timeout period (in seconds) for group membership. If no report is received for these groups before the timeout expires, the group membership is removed. • IGMP Other Querier Present Timeout—Time (in seconds) that the router waits for the IGMP querier to send a query. show igmp interface user@host> show igmp interface Interface: at-0/3/1.0 Querier: 10.111.30.1 State: Up Timeout: Interface: so-1/0/0.0 Querier: 10.111.10.1 State: Up Timeout: Interface: so-1/0/1.0 Querier: 10.111.20.1 State: Up Timeout: Immediate Leave: On Promiscuous Mode: Off None Version: 2 Groups: 4 None Version: 2 Groups: 2 None Version: 2 Groups: 4 Configured Parameters: IGMP Query Interval: 125.0 IGMP Query Response Interval: 10.0 IGMP Last Member Query Interval: 1.0 IGMP Robustness Count: 2 Derived Parameters: IGMP Membership Timeout: 260.0 IGMP Other Querier Present Timeout: 255.0 show igmp interface brief The output for the show igmp interface brief command is identical to that for the show igmp interface command. For sample output, see show igmp interface on page 2177. show igmp interface detail The output for the show igmp interface detail command is identical to that for the show igmp interface command. For sample output, see show igmp interface on page 2177. 2177 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show igmp statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show igmp statistics show igmp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Internet Group Management Protocol (IGMP) statistics. none—Display IGMP statistics for all interfaces. brief | detail—(Optional) Display the specified level of output. interface interface-name—(Optional) Display IGMP statistics about the specified interface only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear igmp statistics on page 2148 show igmp statistics on page 2179 show igmp statistics interface on page 2180 Table 265 on page 2178 describes the output fields for the show igmp statistics command. Output fields are listed in the approximate order in which they appear. Table 265: show igmp statistics Output Fields Field Name Field Description IGMP packet statistics Heading for IGMP packet statistics for all interfaces or for the specified interface name. 2178 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 265: show igmp statistics Output Fields (continued) Field Name Field Description IGMP Message type Summary of IGMP statistics: • Membership Query—Number of membership queries sent and received. • V1 Membership Report—Number of version 1 membership reports sent and received. • DVMRP—Number of DVMRP messages sent or received. • PIM V1—Number of PIM version 1 messages sent or received. • Cisco Trace—Number of Cisco trace messages sent or received. • V2 Membership Report—Number of version 2 membership reports sent or received. • Group Leave—Number of group leave messages sent or received. • Mtrace Response—Number of Mtrace response messages sent or received. • Mtrace Request—Number of Mtrace request messages sent or received. • Domain Wide Report—Number of domain-wide reports sent or received. • V3 Membership Report—Number of version 3 membership reports sent or received. • Other Unknown types—Number of unknown message types received. • IGMP v3 unsupported type—Number of messages received with unknown and unsupported IGMP version 3 message types. • IGMP v3 source required for SSM—Number of IGMP version 3 messages received that contained no source. • IGMP v3 mode not applicable for SSM—Number of IGMP version 3 messages received that did not contain a mode applicable for source-specific multicast (SSM). Received Number of messages received. Sent Number of messages sent. Rx errors Number of received packets that contained errors. IGMP Global Statistics Summary of IGMP statistics for all interfaces. • Bad Length—Number of messages received with length errors so severe that further classification could not occur. • Bad Checksum—Number of messages received with a bad IP checksum. No further classification was performed. show igmp statistics • Bad Receive If—Number of messages received on an interface not enabled for IGMP. • Rx non-local—Number of messages received from senders that are not local. • Timed out—Number of groups that timed out as a result of not receiving an explicit leave message. • Rejected Report—Number of reports dropped because of the IGMP group policy. • Total Interfaces—Number of interfaces configured to support IGMP. user@host> show igmp statistics IGMP packet statistics for all interfaces IGMP Message type Received Sent Membership Query 8883 459 V1 Membership Report 0 0 DVMRP 0 0 PIM V1 0 0 Cisco Trace 0 0 V2 Membership Report 0 0 Rx errors 0 0 0 0 0 0 2179 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Group Leave 0 Mtrace Response 0 Mtrace Request 0 Domain Wide Report 0 V3 Membership Report 0 Other Unknown types IGMP v3 unsupported type IGMP v3 source required for SSM IGMP v3 mode not applicable for SSM IGMP Global Statistics Bad Length Bad Checksum Bad Receive If Rx non-local Timed out Rejected Report Total Interfaces show igmp statistics interface 2180 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1227 0 0 2 user@host> show igmp statistics interface fe-1/0/1.0 IGMP interface packet statistics for fe-1/0/1.0 IGMP Message type Received Sent Rx errors Membership Query 0 230 0 V1 Membership Report 0 0 0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp-snooping membership Syntax Release Information Description Options show igmp-snooping membership Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display IGMP snooping membership information. none—Display general parameters. brief | detail—(Optional) Display the specified level of output. interface interface-name—(Optional) Display IGMP snooping information for the specified interface. vlan vlan-id | vlan-name—(Optional) Display IGMP snooping information for the specified VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show igmp-snooping route on page 2183 • show igmp-snooping statistics on page 2185 • show igmp-snooping vlans on page 2187 • Monitoring IGMP Snooping on page 2069 • Configuring IGMP Snooping (CLI Procedure) on page 2063 • Configuring IGMP Snooping (J-Web Procedure) on page 2064 show igmp-snooping membership on page 2182 show igmp-snooping membership detail on page 2182 Table 266 on page 2181 lists the output fields for the show igmp-snooping membership command. Output fields are listed in the approximate order in which they appear. Table 266: show igmp-snooping membership Output Fields Field Name Field Description Level of Output VLAN Name of the VLAN. All Interfaces Interfaces that are members of the listed multicast group. All Tag Numerical identifier of the VLAN. detail 2181 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 266: show igmp-snooping membership Output Fields (continued) Field Name Field Description Level of Output Router interfaces List of information about multicast router interfaces: detail • Name of the multicast router interface. • static or dynamic—Whether the multicast router interface is static or dynamic. • Uptime—For static interfaces, amount of time since the interface was configured as a multicast router interface. For dynamic interfaces, amount of time since the first query was received on interface. • Group timeout—Query timeout in seconds. IP multicast address of the multicast group. detail The following information is provided for the multicast group: • Name of the interface belonging to the multicast group. • timeout—Time (in seconds) left until the entry for the multicast group is removed. • Last reporter—Last host to report membership for the multicast group. • Receiver count—Number of interfaces that have membership in a multicast group. • Flags—IGMP version of the host sending a join message. • Include source—Source addresses from which multicast streams are allowed based on IGMPv3 reports. Shown only for IGMPv3 joins. show igmp-snooping membership user@switch> show igmp-snooping membership VLAN: vlan24 224.1.1.1 * Interfaces: ge-0/0/0.0 224.1.1.100 * Interfaces: ge-0/0/0.0 225.1.1.100 * Interfaces: ge-0/0/0.0 show igmp-snooping membership detail user@switch> show igmp-snooping membership detail VLAN: vlan24 Tag: 24 (Index: 3) Router interfaces: ge-0/0/8.0 dynamic Uptime: 00:08:35 timeout: 254 Group: 224.1.1.1 ge-0/0/0.0 timeout: 223 Receiver count: 1, Flags: Group: 224.1.1.100 ge-0/0/0.0 timeout: 170 Last reporter: 10.10.1.10 Receiver count: 1, Flags: Group: 225.1.1.100 ge-0/0/0.0 timeout: 168 Last reporter: 10.10.1.10 Receiver count: 1, Flags: 2182 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp-snooping route Syntax Release Information Description Options show igmp-snooping route > > Command introduced before Junos OS Release 10.2 for J-EX Series switches. Option inet enhanced to support IPv6 multicast groups in Junos OS Release 10.2 for J-EX Series switches. Display IGMP snooping route information. none—Display general parameters. brief | detail—(Optional) Display the specified level of output. ethernet-switching—(Optional) Display Ethernet switching information. inet—(Optional) Display inet information for IPv4 and IPv6 multicast groups. For Layer 3 IPv6 multicast routes, display information about the routing table, the routing next hop, and the Layer 2 next hop. vlan vlan-id | vlan-name—(Optional) Display route information for the specified VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show igmp-snooping statistics on page 2185 • show igmp-snooping vlans on page 2187 show igmp-snooping route on page 2184 show igmp-snooping route inet detail (IPv6 Multicast Route) on page 2184 show igmp-snooping route vlan v1 on page 2184 Table 267 on page 2183 lists the output fields for the show igmp-snooping route command. Output fields are listed in the approximate order in which they appear. Table 267: show igmp-snooping route Output Fields Field Name Field Description Table (For internal use only. Value is always 0.) Routing Table (For internal use only. Value is always 0.) VLAN Name of the VLAN on which IGMP snooping is enabled. Group Multicast IPv4 or IPv6 group address. 2183 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 267: show igmp-snooping route Output Fields (continued) Field Name Field Description Next-hop ID associated with the next-hop device. Routing next-hop ID associated with the Layer 3 next-hop device. Interface or Interfaces Name of the interface or interfaces in the VLAN associated with the multicast group. Layer 2 next-hop ID associated with the Layer 2 next-hop device. show igmp-snooping route show igmp-snooping route inet detail (IPv6 Multicast Route) show igmp-snooping route vlan v1 2184 user@switch> show igmp-snooping route VLAN Group Next-hop V11 224.1.1.1, * 533 Interfaces: ge-0/0/13.0, ge-0/0/1.0 VLAN Group Next-hop v12 224.1.1.3, * 534 Interfaces: ge-0/0/13.0, ge-0/0/0.0 user@switch> show igmp-snooping route inet detail Routing table: 0 Group: ff0e::1:ff05:1a3d, 2001::ee0:81ff:ee05:1a2e Routing next-hop: 587 vlan.42 Interface: vlan.42, VLAN: v42, Layer 2 next-hop: 506 user@switch> show igmp-snooping route vlan v1 Table: 0 VLAN Group Next-hop v1 224.1.1.1, * 1266 Interfaces: ge-0/0/0.0 v1 224.1.1.3, * 1266 Interfaces: ge-0/0/0.0 v1 224.1.1.5, * 1266 Interfaces: ge-0/0/0.0 v1 224.1.1.7, * 1266 Interfaces: ge-0/0/0.0 v1 224.1.1.9, * 1266 Interfaces: ge-0/0/0.0 v1 224.1.1.11, * 1266 Interfaces: ge-0/0/0.0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp-snooping statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show igmp-snooping statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display IGMP snooping statistics. view • show igmp-snooping route on page 2183 • show igmp-snooping vlans on page 2187 show igmp-snooping statistics on page 2185 Table 268 on page 2185 lists the output fields for the show igmp-snooping statistics command. Output fields are listed in the approximate order in which they appear. Table 268: show igmp-snooping statistics Output Fields Field Name Field Description Bad length IGMP packet has illegal or bad length. Bad checksum IGMP or IP checksum is incorrect. Invalid interface Packet was received through an invalid interface. Receive unknown Unknown IGMP type. Timed out Number of timeouts for all multicast groups. IGMP Type Type of IGMP message (Query, Report, Leave, or Other). Received Number of IGMP packets received. Transmitted Number of IGMP packets transmitted. Recv Errors Number of general receive errors. show igmp-snooping statistics user@switch> show igmp-snooping statistics Bad length: 0 Bad checksum: 0 Invalid interface: 0 Not local: 0 Receive unknown: 0 Timed out: 58 IGMP Type Queries: Reports: Received 74295 18148423 Transmitted 0 0 Recv Errors 0 16333523 2185 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Leaves: Other: 2186 0 0 0 0 0 0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show igmp-snooping vlans Syntax Release Information Description Options show igmp-snooping vlans Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display IGMP snooping VLAN information. none—Display general parameters. brief | detail—(Optional) Display the specified level of output. vlan vlan-id | vlan vlan-number—(Optional) Display VLAN information for the specified VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show igmp-snooping route on page 2183 • show igmp-snooping statistics on page 2185 show igmp-snooping vlans on page 2188 show igmp-snooping vlans vlan v10 on page 2188 show igmp-snooping vlans vlan v10 detail on page 2188 Table 269 on page 2187 lists the output fields for the show igmp-snooping vlans command. Output fields are listed in the approximate order in which they appear. Table 269: show igmp-snooping vlans Output Fields Field Name Field Description Level of Output VLAN Name of the VLAN. All levels Interfaces Number of interfaces in the VLAN. All levels Groups Number of groups in the VLAN All levels MRouters Number of multicast routers associated with the VLAN. All levels Receivers Number of host receivers in the VLAN. All levels Tag Numerical identifier of the VLAN. Detail vlan-interface Internal VLAN interface identifier. Detail Membership timeout Membership timeout value. Detail 2187 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 269: show igmp-snooping vlans Output Fields (continued) Field Name Field Description Level of Output Querier timeout Timeout value for interfaces dynamically marked as router interfaces (interfaces that receive queries). When the querier timeout is reached, the switch marks the interface as a host interface. Detail Interface Name of the interface. Detail Reporters Number of dynamic groups on an interface. Detail show igmp-snooping vlans user@switch> show igmp-snooping vlans VLAN Interfaces Groups MRouters Receivers default v1 v10 v11 v180 v181 v182 0 11 1 1 3 3 3 0 50 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 show igmp-snooping vlans vlan v10 user@switch> show igmp-snooping vlans vlan v10 user@switch> show igmp-snooping vlans vlan v10 VLAN Interfaces Groups MRouters Receivers v10 1 0 0 0 show igmp-snooping vlans vlan v10 detail user@switch> show igmp-snooping vlans vlan v10 detail VLAN: v10, Tag: 10, vlan-interface: vlan.10 Membership timeout: 260, Querier timeout: 255 Interface: ge-0/0/10.0, tagged, Groups: 0, Reporters: 0 2188 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast flow-map Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast flow-map show multicast flow-map Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display configuration information about IP multicast flow maps. none—Display configuration information about IP multicast flow maps on all systems. brief | detail—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast flow-map on page 2190 show multicast flow-map detail on page 2190 Table 270 on page 2189 describes the output fields for the show multicast flow-map command. Output fields are listed in the approximate order in which they appear. Table 270: show multicast flow-map Output Fields Field Name Field Description Levels of Output Name Name of the flow map. All levels Policy Name of the policy associated with the flow map. All levels Cache-timeout Cache timeout value assigned to the flow map. All levels Bandwidth Bandwidth setting associated to the flow map. All levels Adaptive Whether or not adaptive mode is enabled for the flow map. none Flow-map Name of the flow map. detail Adaptive Bandwidth Whether or not adaptive mode is enabled for the flow map. detail Redundant Sources Redundant sources defined for the same destination group. detail 2189 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast flow-map show multicast flow-map detail 2190 user@host> show multicast flow-map Instance: master Name Policy map2 policy2 map1 policy1 user@host> show multicast flow-map detail Instance: master Flow-map: map1 Policy: policy1 Cache Timeout: 600 seconds Bandwidth: 2000000 Adaptive Bandwidth: yes Redundant Sources: 11.11.11.11 Redundant Sources: 11.11.11.12 Redundant Sources: 11.11.11.13 Cache timeout never 60 seconds Bandwidth Adaptive 2000000 no 2000000 no Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast interface Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast interface show multicast interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display bandwidth information about IP multicast interfaces. none—Display all interfaces that have multicast configured. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast interface on page 2192 Table 271 on page 2191 describes the output fields for the show multicast interface command. Output fields are listed in the approximate order in which they appear. Table 271: show multicast interface Output Fields Field Name Field Description Interface Name of the multicast interface. Maximum bandwidth (bps) Maximum bandwidth setting, in bits per second, for this interface. Remaining bandwidth (bps) Amount of bandwidth, in bits per second, remaining on the interface. Mapped bandwidth deduction (bps) Amount of bandwidth, in bits per second, used by any flows that are mapped to the interface. NOTE: Adding the mapped bandwidth deduction value to the local bandwidth deduction value results in the total deduction value for the interface. This field does not appear in the output when the no QoS adjustment feature is disabled. Local bandwidth deduction (bps) Amount of bandwidth, in bits per second, used by any mapped flows that are traversing the interface. NOTE: Adding the mapped bandwidth deduction value to the local bandwidth deduction value results in the total deduction value for the interface. This field does not appear in the output when the no QoS adjustment feature is disabled. 2191 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 271: show multicast interface Output Fields (continued) Field Name Field Description Reverse OIF mapping State of the reverse OIF mapping feature (on or off). NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled. Reverse OIF mapping no QoS adjustment State of the no QoS adjustment feature (on or off) for interfaces that are using reverse OIF mapping. NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled. Leave timer Amount of time a mapped interface remains active after the last mapping ends. NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled. No QoS adjustment State (on) of the no QoS adjustment feature when this feature is enabled. NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled. show multicast interface 2192 user@host> show multicast interface Interface Maximum bandwidth (bps) Remaining bandwidth (bps) fe-0/0/3 10000000 0 fe-0/0/3.210 10000000 –2000000 fe-0/0/3.220 100000000 100000000 fe-0/0/3.230 20000000 18000000 fe-0/0/2.200 100000000 100000000 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast mrinfo Syntax show multicast mrinfo Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display configuration information about IP multicast networks, including neighboring multicast router addresses. Options none—Display configuration information about all multicast networks. host—(Optional) Display configuration information about a particular host. Replace host with a hostname or IP address. Required Privilege Level view List of Sample Output show multicast mrinfo on page 2194 Output Fields Table 272 on page 2193 describes the output fields for the show multicast mrinfo command. Output fields are listed in the approximate order in which they appear. Table 272: show multicast mrinfo Output Fields Field Name Field Description source-address Query address, hostname (DNS name or IP address of the source address), and multicast protocol version or the software version of another vendor. ip-address-1--->ip-address-2 Queried router interface address and directly attached neighbor interface address, respectively. (name or ip-address) Name or IP address of neighbor. [metric/threshold/type/ flags] Neighbor's multicast profile: • metric—Always has a value of 1, because mrinfo queries the directly connected interfaces of a device. • threshold—Multicast threshold time-to-live (TTL). The range of values is 0 through 255. • type—Multicast connection type: pim or tunnel. • flags—Flags for this route: • querier—Queried router is the designated router for the neighboring session. • leaf—Link is a leaf in the multicast network. • down—Link status indicator. 2193 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast mrinfo 2194 user@host> show multicast mrinfo 10.35.4.1 10.35.4.1 (10.35.4.1) [version 12.0]: 192.168.195.166 -> 0.0.0.0 (local) [1/0/pim/querier/leaf] 10.38.20.1 -> 0.0.0.0 (local) [1/0/pim/querier/leaf] 10.47.1.1 -> 10.47.1.2 (10.47.1.2) [1/5/pim] 0.0.0.0 -> 0.0.0.0 (local) [1/0/pim/down] Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast next-hops Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast next-hops show multicast next-hops Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the IP multicast next-hop table. none—Display standard information about all entries in the multicast next-hop table for all supported address families. brief | detail—(Optional) Display the specified level of output. identifier-number—(Optional) Show a particular next hop by ID number. The range of values is 1 through 65,535. inet | inet6—(Optional) Display entries for IPv4 or IPv6 family addresses, respectively. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast next-hops on page 2196 show multicast next-hops brief on page 2196 show multicast next-hops detail on page 2196 Table 273 on page 2195 describes the output fields for the show multicast next-hops command. Output fields are listed in the approximate order in which they appear. Table 273: show multicast next-hops Output Fields Field Name Field Description ID Next-hop identifier of the prefix. The identifier is returned by the routing device's Packet Forwarding Engine. Refcnt Number of cache entries that are using this next hop. KRefcount Kernel reference count for the next hop. Downstream interface Interface names associated with each multicast next-hop ID. 2195 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast next-hops user@host> show multicast next-hops Family: INET ID Refcount KRefcount Downstream interface 262142 4 2 so-1/0/0.0 262143 2 1 mt-1/1/0.49152 262148 2 1 mt-1/1/0.32769 Family: INET6 2196 show multicast next-hops brief The output for the show multicast next-hops brief command is identical to that for the show multicast next-hops command. For sample output, see show multicast next-hops on page 2196. show multicast next-hops detail The output for the show multicast next-hops detail command is identical to that for the show multicast next-hops command. For sample output, see show multicast next-hops on page 2196. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast pim-to-igmp-proxy Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast pim-to-igmp-proxy show multicast pim-to-igmp-proxy Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display configuration information about PIM-to-IGMP message translation, also known as PIM-to-IGMP proxy. none—Display configuration information about PIM-to-IGMP message translation. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast pim-to-igmp-proxy on page 2197 Table 274 on page 2197 describes the output fields for the show multicast pim-to-igmp-proxy command. Output fields are listed in the order in which they appear. Table 274: show multicast pim-to-igmp-proxy Output Fields show multicast pim-to-igmp-proxy Field Name Field Description Proxy state State of PIM-to-IGMP message translation, also known as PIM-to-IGMP proxy, on the configured upstream interfaces: enabled or disabled. interface-name Name of upstream interface (no more than two allowed) on which PIM-to-IGMP message translation is configured. user@host> show multicast pim-to-igmp-proxy Proxy state: enabled ge-0/1/0.1 ge-0/1/0.2 2197 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast pim-to-mld-proxy Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast pim-to-mld-proxy show multicast pim-to-mld-proxy Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display configuration information about PIM-to-MLD message translation, also known as PIM-to-MLD proxy. none—Display configuration information about PIM-to-MLD message translation. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast pim-to-mld-proxy on page 2198 Table 275 on page 2198 describes the output fields for the show multicast pim-to-mld-proxy command. Output fields are listed in the order in which they appear. Table 275: show multicast pim-to-mld-proxy Output Fields show multicast pim-to-mld-proxy 2198 Field Name Field Description Proxy state State of PIM-to-MLD message translation, also known as PIM-to-MLD proxy, on the configured upstream interfaces: enabled or disabled. interface-name Name of upstream interface (no more than two allowed) on which PIM-to-MLD message translation is configured. user@host> show multicast pim-to-mld-proxy Proxy state: enabled ge-0/5/0.1 ge-0/5/0.2 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast route Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast route show multicast route Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the entries in the IP multicast forwarding table. You can display similar information with the show route table inet.1 command. none—Display standard information about all entries in the multicast forwarding table for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. active | all | inactive—(Optional) Display all active entries, all entries, or all inactive entries, respectively, in the multicast forwarding table. group group—(Optional) Display the cache entries for a particular group. inet | inet6—(Optional) Display multicast forwarding table entries for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display entries in the multicast forwarding table for a specific multicast instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. regular-expression—(Optional) Display information about the multicast forwarding table entries that match a UNIX-style regular expression. source-prefix source-prefix—(Optional) Display the cache entries for a particular source prefix. 2199 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Required Privilege Level List of Sample Output Output Fields view show multicast route on page 2201 show multicast route brief on page 2201 show multicast route detail on page 2201 show multicast route extensive on page 2202 Table 276 on page 2200 describes the output fields for the show multicast route command. Output fields are listed in the approximate order in which they appear. Table 276: show multicast route Output Fields Field Name Field Description Level of Output Address family IPv4 address family (INET) or IPv6 address family (INET6). All levels Group Group address. All levels Source Prefix and length of the source as it is in the multicast forwarding table. All levels Upstream interface Name of the interface on which the packet with this source prefix is expected to arrive. All levels Downstream interface list List of interface names to which the packet with this source prefix is forwarded. All levels Session description Name of the multicast session. detail extensive Statistics Rate at which packets are being forwarded for this source and group entry (in Kbps and pps), and number of packets that have been forwarded to this prefix. If one or more of the kilobits per second packet forwarding statistic queries fails or times out, the statistics field displays Forwarding statistics are not available. detail extensive Next-hop ID Next-hop identifier of the prefix. The identifier is returned by the routing device’s Packet Forwarding Engine and is also displayed in the output of the show multicast nexthops command. detail extensive Upstream protocol Protocol running on the interface on which the packet with this source prefix is expected to arrive. detail extensive Route state Whether the group is Active or Inactive. extensive Forwarding state Whether the prefix is pruned or forwarding. extensive Cache lifetime/timeout Number of seconds until the prefix is removed from the multicast forwarding table. A value of never indicates a permanent forwarding entry. extensive Wrong incoming interface notifications Number of times that the upstream interface was not available. extensive 2200 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast route user@host> show multicast route Family: INET Group: 228.0.0.0 Source: 10.255.14.144/32 Upstream interface: local Downstream interface list: so-1/0/0.0 Group: 239.1.1.1 Source: 10.255.14.144/32 Upstream interface: local Downstream interface list: so-1/0/0.0 Group: 239.1.1.1 Source: 10.255.70.15/32 Upstream interface: so-1/0/0.0 Downstream interface list: mt-1/1/0.49152 Family: INET6 show multicast route brief The output for the show multicast route brief command is identical to that for the show multicast route command. For sample output, see show multicast route on page 2201. show multicast route detail user@host> show multicast route detail Family: INET Group: 228.0.0.0 Source: 10.255.14.144/32 Upstream interface: local Downstream interface list: so-1/0/0.0 Session description: Unknown Statistics: 8 kBps, 100 pps, 45272 packets Next-hop ID: 262142 Upstream protocol: PIM Group: 239.1.1.1 Source: 10.255.14.144/32 Upstream interface: local Downstream interface list: so-1/0/0.0 Session description: Administratively Scoped Statistics: 0 kBps, 0 pps, 13404 packets Next-hop ID: 262142 Upstream protocol: PIM Group: 239.1.1.1 Source: 10.255.70.15/32 Upstream interface: so-1/0/0.0 Downstream interface list: mt-1/1/0.49152 Session description: Administratively Scoped Statistics: 0 kBps, 0 pps, 38 packets Next-hop ID: 262143 Upstream protocol: PIM Family: INET6 2201 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast route extensive user@host> show multicast route extensive Family: INET Group: 228.0.0.0 Source: 10.255.14.144/32 Upstream interface: local Downstream interface list: so-1/0/0.0 Session description: Unknown Statistics: 8 kBps, 100 pps, 46454 packets Next-hop ID: 262142 Upstream protocol: PIM Route state: Active Forwarding state: Forwarding Cache lifetime/timeout: 360 seconds Wrong incoming interface notifications: 0 Group: 239.1.1.1 Source: 10.255.14.144/32 Upstream interface: local Downstream interface list: so-1/0/0.0 Session description: Administratively Scoped Statistics: 0 kBps, 0 pps, 13404 packets Next-hop ID: 262142 Upstream protocol: PIM Route state: Active Forwarding state: Forwarding Cache lifetime/timeout: 348 seconds Wrong incoming interface notifications: 0 Group: 239.1.1.1 Source: 10.255.70.15/32 Upstream interface: so-1/0/0.0 Downstream interface list: mt-1/1/0.49152 Session description: Administratively Scoped Statistics: 0 kBps, 0 pps, 40 packets Next-hop ID: 262143 Upstream protocol: PIM Route state: Active Forwarding state: Forwarding Cache lifetime/timeout: 360 seconds Wrong incoming interface notifications: 1 Family: INET6 2202 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast rpf Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast rpf show multicast rpf Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about multicast reverse-path-forwarding (RPF) calculations. none—Display RPF calculation information for all supported address families. inet | inet6—(Optional) Display the RPF calculation information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about multicast RPF calculations for a specific multicast instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. prefix—(Optional) Display the RPF calculation information for the specified prefix. summary—(Optional) Display summary of all multicast RPF information. Required Privilege Level List of Sample Output view show multicast rpf on page 2204 show multicast rpf inet6 on page 2205 show multicast rpf prefix on page 2206 show multicast rpf summary on page 2206 2203 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Output Fields Table 277 on page 2204 describes the output fields for the show multicast rpf command. Output fields are listed in the approximate order in which they appear. Table 277: show multicast rpf Output Fields show multicast rpf Field Name Field Description Instance Name of the routing instance. (Displayed when multicast is configured within a routing instance.) Source prefix Prefix and length of the source as it exists in the multicast forwarding table. Protocol How the route was learned. Interface Upstream RPF interface. Neighbor Upstream RPF neighbor. user@host> show multicast rpf Multicast RPF table: inet.0, 12 entries 0.0.0.0/0 Protocol: Static 10.255.14.132/32 Protocol: Direct Interface: lo0.0 10.255.245.91/32 Protocol: IS-IS Interface: so-1/1/1.0 Neighbor: 192.168.195.21 127.0.0.1/32 Inactive172.16.0.0/12 Protocol: Static Interface: fxp0.0 Neighbor: 192.168.14.254 192.168.0.0/16 Protocol: Static Interface: fxp0.0 Neighbor: 192.168.14.254 192.168.14.0/24 Protocol: Direct Interface: fxp0.0 192.168.14.132/32 Protocol: Local 192.168.195.20/30 Protocol: Direct Interface: so-1/1/1.0 2204 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast 192.168.195.22/32 Protocol: Local 192.168.195.36/30 Protocol: IS-IS Interface: so-1/1/1.0 Neighbor: 192.168.195.21 show multicast rpf inet6 user@host> show multicast rpf inet6 Multicast RPF table: inet6.0, 12 entries ::10.255.14.132/128 Protocol: Direct Interface: lo0.0 ::10.255.245.91/128 Protocol: IS-IS Interface: so-1/1/1.0 Neighbor: fe80::2a0:a5ff:fe28:2e8c ::192.168.195.20/126 Protocol: Direct Interface: so-1/1/1.0 ::192.168.195.22/128 Protocol: Local ::192.168.195.36/126 Protocol: IS-IS Interface: so-1/1/1.0 Neighbor: fe80::2a0:a5ff:fe28:2e8c ::192.168.195.76/126 Protocol: Direct Interface: fe-2/2/0.0 ::192.168.195.77/128 Protocol: Local fe80::/64 Protocol: Direct Interface: so-1/1/1.0 fe80::290:69ff:fe0c:993a/128 Protocol: Local fe80::2a0:a5ff:fe12:84f/128 Protocol: Direct Interface: lo0.0 ff02::2/128 Protocol: PIM ff02::d/128 Protocol: PIM 2205 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast rpf prefix user@host> show multicast rpf ff02::/16 Multicast RPF table: inet6.0, 13 entries ff02::2/128 Protocol: PIM ff02::d/128 Protocol: PIM ... show multicast rpf summary user@host> show multicast rpf summary Multicast RPF table: inet.0, 16 entries Multicast RPF table: inet6.0, 12 entries 2206 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast scope Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast scope show multicast scope Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display administratively scoped IP multicast information. none—Display standard information about administratively scoped multicast information for all supported address families in all routing instances. inet | inet6—(Optional) Display scoped multicast information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display administratively scoped information for a specific multicast instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast scope on page 2208 show multicast scope inet on page 2208 show multicast scope inet6 on page 2208 Table 278 on page 2207 describes the output fields for the show multicast scope command. Output fields are listed in the approximate order in which they appear. Table 278: show multicast scope Output Fields Field Name Field Description Scope name Name of the multicast scope. Group Prefix Range of multicast groups that are scoped. Interface Interface that is the boundary of the administrative scope. Resolve Rejects Number of kernel resolve rejects. 2207 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast scope user@host> show multicast scope Scope name 232-net local local larry show multicast scope inet Resolve Rejects 0 0 0 0 Group Prefix 232.232.0.0/16 239.255.0.0/16 Interface fe-0/0/0.1 fe-0/0/0.1 Resolve Rejects 0 0 Interface fe-0/0/0.1 fe-0/0/0.1 Resolve Rejects 0 0 user@host> show multicast scope inet6 Scope name local larry 2208 Interface fe-0/0/0.1 fe-0/0/0.1 fe-0/0/0.1 fe-0/0/0.1 user@host> show multicast scope inet Scope name 232-net local show multicast scope inet6 Group Prefix 232.232.0.0/16 239.255.0.0/16 ff05::/16 ff05::1234/128 Group Prefix ff05::/16 ff05::1234/128 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast sessions Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast sessions show multicast sessions Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about announced IP multicast sessions. none—Display standard information about all multicast sessions for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. regular-expression—(Optional) Display information about announced sessions that match a UNIX-style regular expression. Required Privilege Level List of Sample Output Output Fields view show multicast sessions on page 2210 show multicast sessions regular-expression detail on page 2210 Table 279 on page 2209 describes the output fields for the show multicast sessions command. Output fields are listed in the approximate order in which they appear. Table 279: show multicast sessions Output Fields Field Name Field Description session-name Name of the known announced multicast sessions. 2209 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show multicast sessions show multicast sessions regular-expression detail user@host> show multicast sessions 1-Department of Biological Sciences, LSU ... Monterey Bay - DockCam Monterey Bay - JettyCam Monterey Bay - StandCam Monterey DockCam Monterey DockCam / ROV cam ... NASA TV (MPEG-1) ... UO Broadcast - NASA Videos - 25 Years of Progress UO Broadcast - NASA Videos - Journey through the Solar System UO Broadcast - NASA Videos - Life in the Universe UO Broadcast - NASA Videos - Nasa and the Airplane UO Broadcasts OPB's Oregon Story UO DOD News Clips UO Medical Management of Biological Casualties (1) UO Medical Management of Biological Casualties (2) UO Medical Management of Biological Casualties (3) ... 376 active sessions. user@host> show multicast sessions "NASA TV" detail SDP Version: 0 Originated by: -@128.223.83.33 Session: NASA TV (MPEG-1) Description: NASA television in MPEG-1 format, provided by Private University. Please contact the UO if you have problems with this feed. Email: Your Name Here Phone: Your Name Here <888/555-1212> Bandwidth: AS:1000 Start time: permanent Stop time: none Attribute: type:broadcast Attribute: tool:IP/TV Content Manager 3.4.14 Attribute: live:capture:1 Attribute: x-iptv-capture:mp1s Media: video 54302 RTP/AVP 32 31 96 97 Connection Data: 224.2.231.45 ttl 127 Attribute: quality:8 Attribute: framerate:30 Attribute: rtpmap:96 WBIH/90000 Attribute: rtpmap:97 MP4V-ES/90000 Attribute: x-iptv-svr:video 128.223.91.191 live Attribute: fmtp:32 type=mpeg1 Media: audio 28848 RTP/AVP 14 0 96 3 5 97 98 99 100 101 102 10 11 103 104 105 106 Connection Data: 224.2.145.37 ttl 127 Attribute: rtpmap:96 X-WAVE/8000 Attribute: rtpmap:97 L8/8000/2 Attribute: rtpmap:98 L8/8000 Attribute: rtpmap:99 L8/22050/2 Attribute: rtpmap:100 L8/22050 Attribute: rtpmap:101 L8/11025/2 Attribute: rtpmap:102 L8/11025 Attribute: rtpmap:103 L16/22050/2 Attribute: rtpmap:104 L16/22050 1 matching sessions. 2210 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show multicast usage Syntax Syntax (J-EX Series Switch) Release Information Description Options show multicast usage show multicast usage Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display usage information about the 10 most active Distance Vector Multicast Routing Protocol (DVMRP) or Protocol Independent Multicast (PIM) groups. none—Display multicast usage information for all supported address families for all routing instances. brief | detail—(Optional) Display the specified level of output. inet | inet6—(Optional) Display usage information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about the most active DVMRP or PIM groups for a specific multicast instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show multicast usage on page 2212 show multicast usage brief on page 2212 show multicast usage instance on page 2212 show multicast usage detail on page 2212 Table 280 on page 2211 describes the output fields for the show multicast usage command. Output fields are listed in the approximate order in which they appear. Table 280: show multicast usage Output Fields Field Name Field Description Instance Name of the routing instance. (Displayed when multicast is configured within a routing instance.) Group Group address. 2211 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 280: show multicast usage Output Fields (continued) show multicast usage Field Name Field Description Sources Number of sources. Packets Number of packets that have been forwarded to this prefix. If one or more of the packets forwarded statistic queries fails or times out, the packets field displays unavailable. Bytes Number of bytes that have been forwarded to this prefix. If one or more of the packets forwarded statistic queries fails or times out, the bytes field displays unavailable. Prefix IP address. /len Prefix length. Groups Number of multicast groups. user@host> show multicast usage Group Sources Packets 228.0.0.0 1 52847 239.1.1.1 2 13450 Prefix 10.255.14.144 10.255.70.15 /len Groups Packets /32 2 66254 /32 1 43 Bytes 4439148 1125530 Bytes 5561304 3374... show multicast usage brief The output for the show multicast usage brief command is identical to that for the show multicast usage command. For sample output, see show multicast usage on page 2212. show multicast usage instance user@host> show multicast usage instance VPN-A Group Sources Packets 224.2.127.254 1 5538 224.0.1.39 1 13 224.0.1.40 1 13 Prefix 192.168.195.34 10.255.14.30 10.255.245.91 ... show multicast usage detail Groups 1 1 1 Packets 5538 13 13 Bytes 509496 624 624 user@host> show multicast usage detail Group Sources Packets Bytes 228.0.0.0 1 53159 4465356 Source: 10.255.14.144 /32 Packets: 53159 Bytes: 4465356 239.1.1.1 2 13450 1125530 Source: 10.255.14.144 /32 Packets: 13407 Bytes: 1122156 Source: 10.255.70.15 /32 Packets: 43 Bytes: 3374 Prefix 2212 /len /32 /32 /32 Bytes 509496 624 624 /len Groups Packets Bytes Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast 10.255.14.144 /32 2 Group: 228.0.0.0 Group: 239.1.1.1 10.255.70.15 /32 1 Group: 239.1.1.1 66566 5587512 Packets: 53159 Bytes: 4465356 Packets: 13407 Bytes: 1122156 43 3374 Packets: 43 Bytes: 3374 2213 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pim bootstrap Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim bootstrap show pim bootstrap Command introduced before Junos OS Release 10.2 for J-EX Series switches. For sparse mode only, display information about Protocol Independent Multicast (PIM) bootstrap routers. none—Display PIM bootstrap router information for all routing instances. instance instance-name—(Optional) Display information about bootstrap routers for a specific PIM-enabled routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show pim bootstrap on page 2215 show pim bootstrap instance on page 2215 Table 281 on page 2214 describes the output fields for the show pim bootstrap command. Output fields are listed in the approximate order in which they appear. Table 281: show pim bootstrap Output Fields 2214 Field Name Field Description Instance Name of the routing instance. BSR Bootstrap router. Pri Priority of the routing device to be elected to be the bootstrap router. Local address Local routing device’s address. Pri Local routing device’s address priority to be elected as the bootstrap router. State Local routing device’s election state: Candidate, Elected, or Ineligible. Timeout How long until the local routing device declares the bootstrap router to be unreachable, in seconds. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show pim bootstrap user@host> show pim bootstrap Instance: PIM.master BSR Pri Local address Pri State Timeout None 0 10.255.71.46 0 InEligible 0 feco:1:1:1:1:0:aff:785c 34 feco:1:1:1:1:0:aff:7c12 0 InEligible 0 show pim bootstrap instance user@host> show pim bootstrap instance VPN-A Instance: PIM.VPN-A BSR None Pri Local address Pri State Timeout 0 192.168.196.105 0 InEligible 0 2215 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pim interfaces Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim interfaces show pim interfaces Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the interfaces on which Protocol Independent Multicast (PIM) is configured. none—Display interface information for all family addresses for all routing instances. inet | inet6—(Optional) Display interface information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about interfaces for a specific PIM-enabled routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show pim interfaces on page 2217 show pim interfaces inet on page 2218 show pim interfaces inet6 on page 2218 Table 282 on page 2216 describes the output fields for the show pim interfaces command. Output fields are listed in the approximate order in which they appear. Table 282: show pim interfaces Output Fields Field Name Field Description Instance Name of the routing instance. Name Interface name. State State of the interface. The state also is displayed in the show interfaces command. 2216 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 282: show pim interfaces Output Fields (continued) Field Name Field Description Mode PIM mode running on the interface: • Sparse—In sparse mode, routing devices must join and leave multicast groups explicitly. Upstream routing devices do not forward multicast traffic to this routing device unless this device has sent an explicit request (using a join message) to receive multicast traffic. • Dense—Unlike sparse mode, where data is forwarded only to routing devices sending an explicit request, dense mode implements a flood-and-prune mechanism, similar to DVMRP (the first multicast protocol used to support the multicast backbone). • Sparse-Dense—Sparse-dense mode allows the interface to operate on a per-group basis in either sparse or dense mode. A group specified as dense is not mapped to a rendezvous point (RP). Instead, data packets destined for that group are forwarded using PIM-Dense Mode (PIM-DM) rules. A group specified as sparse is mapped to an RP, and data packets are forwarded using PIM-Sparse Mode (PIM-SM) rules. IP Version number of the address family on the interface: 4 (IPv4) or 6 (IPv6). V PIM version running on the interface: 1 or 2. State State of PIM on the interface: • DR—Designated router. • NotDR—Not the designated router. • P2P—Point to point. NbrCnt Number of neighbors that have been seen on the interface. JoinCnt(sg) Number of (s,g) join messages that have been seen on the interface. JointCnt(*g) Number of (*,g) join messages that have been seen on the interface. DR address Address of the designated router. show pim interfaces user@host> show pim interfaces Instance: PIM.master Name Stat address fe-0/0/0.0 Up 10.10.10.2 fe-0/0/3.0 Up 20.20.20.2 lo0.0 Up 10.255.72.54 pe-1/2/0.32769 Up t1-0/1/0.0 Up lo0.0 Up fe80::2a0:a5ff:fe5e:209 Mode IP V State NbrCnt JoinCnt(sg) JointCnt(*g) DR Sparse 4 2 DR 1 1 3 Sparse 4 2 DR 1 1 3 Sparse 4 2 DR 0 0 0 Sparse Sparse Sparse 4 2 P2P 4 2 P2P 6 2 DR 0 1 0 0 0 0 0 0 0 2217 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pim interfaces inet user@host> show pim interfaces inet Instance: PIM.master Name address fe-0/0/0.0 10.10.10.2 fe-0/0/3.0 20.20.20.2 lo0.0 10.255.72.54 pe-1/2/0.32769 t1-0/1/0.0 show pim interfaces inet6 Stat Mode Up Sparse 4 2 DR 1 1 3 Up Sparse 4 2 DR 1 1 3 Up Sparse 4 2 DR 0 0 0 Up Up Sparse Sparse 4 2 P2P 4 2 P2P 0 1 0 0 0 0 user@host> show pim interfaces inet6 Instance: PIM.master Name Stat Mode address lo0.0 Up Sparse fe80::2a0:a5ff:fe5e:209 2218 IP V State NbrCnt JoinCnt(sg) JointCnt(*g) DR IP V State NbrCnt JoinCnt(sg) JointCnt(*g) DR 6 2 DR 0 0 0 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show pim join Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim join show pim join Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Protocol Independent Multicast (PIM) groups. none—Display the standard information about PIM groups for all supported family addresses for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. inet | inet6—(Optional) Display PIM group information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about groups for the specified PIM-enabled routing instance only. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. range—(Optional) Address range of the group, specified as prefix/prefix-length. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear pim join on page 2157 show pim join on page 2221 show pim join instance on page 2221 show pim join detail on page 2222 show pim join extensive on page 2222 show pim join instance extensive on page 2223 Table 283 on page 2220 describes the output fields for the show pim join command. Output fields are listed in the approximate order in which they appear. 2219 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 283: show pim join Output Fields Field Name Field Description Instance Name of the routing instance. Family Name of the address family: inet (IPv4) or inet6 (IPv6). R Rendezvous Point Tree S Sparse W Wildcard Group Group address. Source Multicast source: • * (wildcard value) • ipv4-address • ipv6-address RP Rendezvous point for the PIM group. Flags PIM flags: • dense—Dense mode entry. • rptree—Entry is on the rendezvous point tree. • sparse—Sparse mode entry. • spt—Entry is on the shortest-path tree for the source. • wildcard—Entry is on the shared tree. Upstream interface RPF interface toward the source address for the source-specific state (S, G) or toward the rendezvous point (RP) address for the non-source-specific state (*, G). Upstream neighbor Information about the upstream neighbor: Direct, Local, Unknown, or a specific IP address. Upstream state Information about the upstream interface: • Join to RP—Sending a join to the rendezvous point. • Join to Source—Sending a join to the source. • Local RP—Sending neither joins nor prunes toward the RP, because this router is the rendezvous point. • Local Source—Sending neither joins nor prunes toward the source, because the source is locally attached to this routing device. 2220 • Prune to RP—Sending a prune to the rendezvous point. • Prune to Source—Sending a prune to the source. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 283: show pim join Output Fields (continued) Field Name Field Description Downstream neighbors Information about downstream interfaces: • Interface—Interface name for the downstream neighbor. NOTE: A pseudo PIM-SM interface appears for all IGMP-only interfaces. show pim join • Interface address—Address of the downstream neighbor. • State—Information about the downstream neighbor: join or prune. • Flags—PIM join flags: R (RPtree),S (Sparse), W (Wildcard), or zero. Assert Timeout Length of time between assert cycles on downstream interface. Not displayed if assert timer is null. Timeout Time remaining until the downstream join state is updated (in seconds). If the downstream join state is not updated before this keepalive timer reaches zero, the entry is deleted. If there is a directly connected host, Timeout is Infinity. user@host> show pim join Instance: PIM.master Family: INET R = Rendezvous Point Tree, S = Sparse, W = Wildcard Group: 239.1.1.1 Source: * RP: 10.255.14.144 Flags: sparse,rptree,wildcard Upstream interface: Local Group: 239.1.1.1 Source: 10.255.14.144 Flags: sparse,spt Upstream interface: Local Group: 239.1.1.1 Source: 10.255.70.15 Flags: sparse,spt Upstream interface: so-1/0/0.0 Instance: PIM.master Family: INET6 R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join instance user@host> show pim join instance VPN-A Instance: PIM.VPN-A Family: INET R = Rendezvous Point Tree, S = Sparse, W = Wildcard Group: 235.1.1.2 Source: * RP: 10.10.47.100 Flags: sparse,rptree,wildcard Upstream interface: Local Group: 235.1.1.2 Source: 192.168.195.74 Flags: sparse,spt Upstream interface: at-0/3/1.0 2221 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Group: 235.1.1.2 Source: 192.168.195.169 Flags: sparse Upstream interface: so-1/0/1.0 Instance: PIM.VPN-A Family: INET6 R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join detail user@host> show pim join detail Instance: PIM.master Family: INET R = Rendezvous Point Tree, S = Sparse, W = Wildcard Group: 239.1.1.1 Source: * RP: 10.255.14.144 Flags: sparse,rptree,wildcard Upstream interface: Local Group: 239.1.1.1 Source: 10.255.14.144 Flags: sparse,spt Upstream interface: Local Group: 239.1.1.1 Source: 10.255.70.15 Flags: sparse,spt Upstream interface: so-1/0/0.0 Instance: PIM.master Family: INET6 R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive user@host> show pim join extensive Instance: PIM.master Family: INET R = Rendezvous Point Tree, S = Sparse, W = Wildcard Group: 239.1.1.1 Source: * RP: 10.255.14.144 Flags: sparse,rptree,wildcard Upstream interface: Local Upstream neighbor: Local Upstream state: Local RP Downstream neighbors: Interface: so-1/0/0.0 10.111.10.2 State: Join Flags: SRW Timeout: 174 Interface: mt-1/1/0.32768 10.10.47.100 State: Join Flags: SRW Timeout: Infinity Group: 239.1.1.1 Source: 10.255.14.144 Flags: sparse,spt Upstream interface: Local Upstream neighbor: Local Upstream state: Local Source, Local RP Keepalive timeout: 344 Downstream neighbors: Interface: so-1/0/0.0 10.111.10.2 State: Join Flags: S Timeout: 174 Interface: mt-1/1/0.32768 10.10.47.100 State: Join Flags: S Timeout: Infinity 2222 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Group: 239.1.1.1 Source: 10.255.70.15 Flags: sparse,spt Upstream interface: so-1/0/0.0 Upstream neighbor: 10.111.10.2 Upstream state: Local RP, Join to Source Keepalive timeout: 344 Downstream neighbors: Interface: Pseudo-GMP fe-0/0/0.0 fe-0/0/1.0 fe-0/0/3.0 Interface: so-1/0/0.0 (pruned) 10.111.10.2 State: Prune Flags: SR Timeout: 174 Interface: mt-1/1/0.32768 10.10.47.100 State: Join Flags: S Timeout: Infinity Instance: PIM.master Family: INET6 R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join instance extensive user@host> show pim join instance VPN-A extensive Instance: PIM.VPN-A Family: INET R = Rendezvous Point Tree, S = Sparse, W = Wildcard Group: 235.1.1.2 Source: * RP: 10.10.47.100 Flags: sparse,rptree,wildcard Upstream interface: Local Upstream neighbor: Local Upstream state: Local RP Downstream neighbors: Interface: mt-1/1/0.32768 10.10.47.101 State: Join Flags: SRW Timeout: 156 Group: 235.1.1.2 Source: 192.168.195.74 Flags: sparse,spt Upstream interface: at-0/3/1.0 Upstream neighbor: 10.111.30.2 Upstream state: Local RP, Join to Source Keepalive timeout: 156 Group: 235.1.1.2 Source: 192.168.195.169 Flags: sparse Upstream interface: so-1/0/1.0 Upstream neighbor: 10.111.20.2 Upstream state: Local RP, Join to Source Keepalive timeout: 156 2223 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pim neighbors Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim neighbors show pim neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Protocol Independent Multicast (PIM) neighbors. none—(Same as brief) Display standard information about PIM neighbors for all supported family addresses for all routing instances. brief | detail—(Optional) Display the specified level of output. inet | inet6—(Optional) Display information about PIM neighbors for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about neighbors for the specified PIM-enabled routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show pim neighbors on page 2226 show pim neighbors brief on page 2226 show pim neighbors instance on page 2226 show pim neighbors detail on page 2226 show pim neighbors detail (with BFD) on page 2226 Table 284 on page 2224 describes the output fields for the show pim neighbors command. Output fields are listed in the approximate order in which they appear. Table 284: show pim neighbors Output Fields Field Name Field Description Level of Output Instance Name of the routing instance. All levels Interface Interface through which the neighbor is reachable. All levels Neighbor addr Address of the neighboring PIM routing device. All levels 2224 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 284: show pim neighbors Output Fields (continued) Field Name Field Description Level of Output IP IP version: 4 or 6. All levels V PIM version running on the neighbor: 1 or 2. All levels Mode PIM mode of the neighbor: Sparse, Dense, SparseDense, or Unknown. When the neighbor is running PIM version 2, this mode is always Unknown. All levels Option Can be one or more of the following: brief none • B—Bidirectional Capable. • H—Hello Option Holdtime. • G—Generation Identifier. • P—Hello Option DR Priority. • L—Hello Option LAN Prune Delay. Uptime Time the neighbor has been operational since the PIM process was last initialized, in the format dd:hh:mm:ss ago for less than a week and nwnd:hh:mm:ss ago for more than a week. All levels Address Address of the neighboring PIM router. detail BFD Status and operational state of the Bidirectional Forwarding Detection (BFD) protocol on the interface: Enabled, Operational state is up, or Disabled. detail Hello Option Holdtime Time for which the neighbor is available, in seconds. The range of values is 0 through 65,535. detail Hello Default Holdtime Default holdtime and the time remaining if the holdtime option is not in the received hello message. detail Hello Option DR Priority Designated router election priority. The range of values is 0 through 255. detail Hello Option Generation ID 9- or 10-digit number used to tag hello messages. detail Hello Option LAN Prune Delay Time to wait before the neighbor receives prune messages, in the format delay nnn ms override nnnn ms. detail Join Suppression supported Neighbor is capable of join suppression. detail Rx Join Information about joins received from the neighbor. detail • Group—Group addresses in the join message. • Source—Address of the source in the join message. • Timeout—Time for which the join is valid. 2225 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pim neighbors user@host> show pim neighbors Instance: PIM.master B = Bidirectional Capable, G = Generation Identifier, H = Hello Option Holdtime, L = Hello Option LAN Prune Delay, P = Hello Option DR Priority Interface so-1/0/0.0 IP V Mode 4 2 Option HPLG Uptime Neighbor addr 00:07:10 10.111.10.2 show pim neighbors brief The output for the show pim neighbors brief command is identical to that for the show pim neighbors command. For sample output, see show pim neighbors on page 2226. show pim neighbors instance user@host> show pim neighbors instance VPN-A Instance: PIM.VPN-A B = Bidirectional Capable, G = Generation Identifier, H = Hello Option Holdtime, L = Hello Option LAN Prune Delay, P = Hello Option DR Priority Interface at-0/3/1.0 mt-1/1/0.32768 so-1/0/1.0 IP 4 4 4 V Mode 2 2 2 Option HPLG HPLG HPLG Uptime 00:07:54 00:07:22 00:07:50 Neighbor addr 10.111.30.2 10.10.47.101 10.111.20.2 show pim neighbors detail user@host> show pim neighbors detail Instance: PIM.master Interface: fe-3/0/2.0 Address: 192.168.195.37, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 1 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Join Suppression supported Rx Join: Group Source Timeout 225.1.1.1 192.168.195.78 0 225.1.1.1 0 Interface: lo0.0 Address: 10.255.245.91, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 1 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Join Suppression supported Interface: pd-6/0/0.32768 Address: 0.0.0.0, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 0 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Join Suppression supported show pim neighbors detail (with BFD) user@host> show pim neighbors detail Instance: PIM.master Interface: fe-1/0/0.0 Address: 192.168.11.1, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 1 Hello Option Generation ID: 836607909 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Address: 192.168.11.2, IPv4, PIM v2 BFD: Enabled, Operational state is up Hello Default Holdtime: 105 seconds 104 remaining 2226 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Hello Option DR Priority: 1 Hello Option Generation ID: 1907549685 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Interface: fe-1/0/1.0 Address: 192.168.12.1, IPv4, PIM v2 BFD: Disabled Hello Default Holdtime: 105 seconds 80 remaining Hello Option DR Priority: 1 Hello Option Generation ID: 1971554705 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms 2227 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pim rps Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim rps show pim rps Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Protocol Independent Multicast (PIM) rendezvous points (RPs). none—Display standard information about PIM RPs for all groups and family addresses for all routing instances. brief | detail | extensive—(Optional) Display the specified level of output. group-address—(Optional) Display the RPs for a particular group. If you specify a group address, the output lists the routing device that is the RP for that group. inet | inet6—(Optional) Display information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about RPs for a specific PIM-enabled routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show pim rps on page 2230 show pim rps brief on page 2230 show pim rps instance on page 2230 show pim rps extensive on page 2231 show pim rps extensive (PIM Anycast RP in Use) on page 2231 Table 285 on page 2228 describes the output fields for the show pim rps command. Output fields are listed in the approximate order in which they appear. Table 285: show pim rps Output Fields Field Name Field Description Level of Output Instance Name of the routing instance. All levels 2228 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 285: show pim rps Output Fields (continued) Field Name Field Description Level of Output Family Name of the address family: inet (IPv4) or inet6 (IPv6). All levels RP address Address of the rendezvous point. All levels Type Type of RP: brief none • auto-rp—Address of the RP known through the Auto-RP protocol. • bootstrap—Address of the RP known through the bootstrap router protocol (BSR). • embedded—Address of the RP known through an embedded RP (IPv6). • static—Address of RP known through static configuration. Holdtime How long to keep the RP active, with time remaining, in seconds. All levels Timeout How long until the local routing device determines the RP to be unreachable, in seconds. All levels Groups Number of groups currently using this RP. All levels Group prefixes Addresses of groups that this RP can span. brief none Learned via Address and method by which the RP was learned. detail extensive Time Active How long the RP has been active, in the format hh:mm:ss. detail extensive Device Index Index value of the order in which the Junos OS finds and initializes the interface. detail extensive Subunit Logical unit number of the interface. detail extensive Interface Either the encapsulation or the de-encapsulation logical interface, depending on whether this routing device is a designated router (DR) facing an RP router, or is the local RP, respectively. detail extensive Group Ranges Addresses of groups that this RP spans. detail extensive Active groups using RP Number of groups currently using this RP. detail extensive total Total number of active groups for this RP. detail extensive 2229 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 285: show pim rps Output Fields (continued) Field Name Field Description Level of Output Register State for RP Current register state for each group: extensive • Group—Multicast group address. • Source—Multicast source address for which the PIM register is sent or received, depending on whether this router is a designated router facing an RP router, or is the local RP, respectively: • First Hop—PIM-designated routing device that sent the Register message (the source address in the IP header). • RP Address—RP to which the Register message was sent (the destination address in the IP header). • State: On the designated router: • Send—Sending Register messages. • Probe—Sent a null register. If a Register-Stop message does not arrive in 5 seconds, the designated router resumes sending Register messages. • • Suppress—Received a Register-Stop message. The designated router is waiting for the timer to resume before changing to Probe state. On the RP: • Receive—Receiving Register messages. Anycast-PIM rpset If anycast RP is configured, the addresses of the RPs in the set. extensive Anycast-PIM local address used If anycast RP is configured, the local address used by the RP. extensive Anycast-PIM Register State If anycast RP is configured, the current register state for each group: extensive • Group—Multicast group address. • Source—Multicast source address for which the PIM register is sent or received, depending on whether this routing device is a designated router facing an RP router, or is the local RP, respectively. • Origin—How the information was obtained: • DIRECT—From a local attachment • MSDP—From the Multicast Source Discovery Protocol (MSDP) • DR—From the designated router show pim rps user@host> show pim rps Instance: PIM.master Address family INET RP address 10.255.14.144 Type static Holdtime Timeout Groups Group prefixes 0 None 1 224.0.0.0/4 Address family INET6 show pim rps brief show pim rps instance 2230 The output for the show pim rps brief command is identical to that for the show pim rps command. For sample output, see show pim rps on page 2230. user@host> show pim rps instance VPN-A Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Instance: PIM.VPN-A Address family INET RP address 10.10.47.100 Type static Holdtime Timeout Groups Group prefixes 0 None 1 224.0.0.0/4 Address family INET6 show pim rps extensive user@host> show pim rps extensive Instance: PIM.master Family: INET RP: 10.255.245.91 Learned via: static configuration Time Active: 00:05:48 Holdtime: 45 with 36 remaining Device Index: 122 Subunit: 32768 Interface: pd-6/0/0.32768 Group Ranges: 224.0.0.0/4, 36s remaining Active groups using RP: 225.1.1.1 total 1 groups active Register State for RP: Group Source 225.1.1.1 192.168.195.78 show pim rps extensive (PIM Anycast RP in Use) FirstHop 10.255.14.132 RP Address 10.255.245.91 State Receive Timeout 0 user@host> show pim rps extensive Instance: PIM.master Family: INET RP: 10.10.10.2 Learned via: static configuration Time Active: 00:54:52 Holdtime: 0 Device Index: 130 Subunit: 32769 Interface: pimd.32769 Group Ranges: 224.0.0.0/4 Active groups using RP: 224.10.10.10 total 1 groups active Anycast-PIM rpset: 10.100.111.34 10.100.111.17 10.100.111.55 Anycast-PIM local address used: 10.100.111.1 Anycast-PIM Register State: Group Source 224.1.1.1 10.10.95.2 224.1.1.2 10.10.95.2 224.10.10.10 10.10.70.1 224.10.10.11 10.10.70.1 224.20.20.1 10.10.71.1 Origin DIRECT DIRECT MSDP MSDP DR 2231 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Address family INET6 Anycast-PIM rpset: ab::1 ab::2 Anycast-PIM local address used: cd::1 Anycast-PIM Register State: Group Source ::224.1.1.1 ::10.10.95.2 ::224.1.1.2 ::10.10.95.2 ::224.20.20.1 ::10.10.71.1 2232 Origin DIRECT DIRECT DR Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show pim source Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim source show pim source Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the Protocol Independent Multicast (PIM) source reverse path forwarding (RPF) state. none—Display standard information about the PIM RPF state for all supported family addresses for all routing instances. brief | detail—(Optional) Display the specified level of output. inet | inet6—(Optional) Display information for IPv4 or IPv6 family addresses, respectively. instance instance-name—(Optional) Display information about the RPF state for a specific PIM-enabled routing instance. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. source-prefix—(Optional) Display the state for source RPF states in the given range. Required Privilege Level List of Sample Output Output Fields view show pim source on page 2234 show pim source brief on page 2234 show pim source detail on page 2234 Table 286 on page 2233 describes the output fields for the show pim source command. Output fields are listed in the approximate order in which they appear. Table 286: show pim source Output Fields Field Name Field Description Instance Name of the routing instance. RPF Address Address of the source or reverse path. 2233 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 286: show pim source Output Fields (continued) show pim source Field Name Field Description Prefix/length Prefix and prefix length for the route used to reach the RPF address. Upstream interface RPF interface toward the source address. Neighbor address Address of the RPF neighbor used to reach the source address. user@host> show pim source Instance: PIM.master Family: INET Source 10.255.14.144 Prefix 10.255.14.144/32 Upstream interface Local Upstream neighbor Local Source 10.255.70.15 Prefix 10.255.70.15/32 Upstream interface so-1/0/0.0 Upstream neighbor 10.111.10.2 Instance: PIM.master Family: INET6 show pim source brief show pim source detail The output for the show pim source brief command is identical to that for the show pim source command. For sample output, see show pim source on page 2234. user@host> show pim source detail Instance: PIM.master Family: INET Source 10.255.14.144 Prefix 10.255.14.144/32 Upstream interface Local Upstream neighbor Local Active groups:228.0.0.0 239.1.1.1 239.1.1.1 Source 10.255.70.15 Prefix 10.255.70.15/32 Upstream interface so-1/0/0.0 Upstream neighbor 10.111.10.2 Active groups:239.1.1.1 Instance: PIM.master Family: INET6 2234 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast show pim statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options show pim statistics show pim statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Protocol Independent Multicast (PIM) statistics. none—Display PIM statistics. inet | inet6—(Optional) Display IPv4 or IPv6 PIM statistics. instance instance-name—(Optional) Display statistics for a specific routing instance enabled by Protocol Independent Multicast (PIM). interface interface-name—(Optional) Display statistics about the specified interface. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear pim statistics on page 2159 show pim statistics on page 2240 Table 287 on page 2235 describes the output fields for the show pim statistics command. Output fields are listed in the approximate order in which they appear. Table 287: show pim statistics Output Fields Field Name Field Description PIM statistics PIM statistics for all interfaces or for the specified interface. PIM message type Message type for which statistics are displayed. Received Number of received statistics. Sent Number of messages sent of a certain type. 2235 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 287: show pim statistics Output Fields (continued) 2236 Field Name Field Description Rx errors Number of received packets that contained errors. V2 Hello PIM version 2 hello packets. V2 Register PIM version 2 register packets. V2 Register Stop PIM version 2 register stop packets. V2 Join Prune PIM version 2 join and prune packets. V2 Bootstrap PIM version 2 bootstrap packets. V2 Assert PIM version 2 assert packets. V2 Graft PIM version 2 graft packets. V2 Graft Ack PIM version 2 graft acknowledgement packets. V2 Candidate RP PIM version 2 candidate RP packets. V1 Query PIM version 1 query packets. V1 Register PIM version 1 register packets. V1 Register Stop PIM version 1 register stop packets. V1 Join Prune PIM version 1 join and prune packets. V1 RP Reachability PIM version 1 RP reachability packets. V1 Assert PIM version 1 assert packets. V1 Graft PIM version 1 graft packets. V1 Graft Ack PIM version 1 graft acknowledgement packets. AutoRP Announce Auto-RP announce packets. AutoRP Mapping Auto-RP mapping packets. AutoRP Unknown type Auto-RP packets with an unknown type. Anycast Register Auto-RP announce packets. Anycast Register Stop Auto-RP announce packets. Global Statistics Summary of PIM statistics for all interfaces. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 287: show pim statistics Output Fields (continued) Field Name Field Description Hello dropped on neighbor policy Number of hello packets dropped because of a configured neighbor policy. Unknown type Number of PIM control packets received with an unknown type. V1 Unknown type Number of PIM version 1 control packets received with an unknown type. Unknown Version Number of PIM control packets received with an unknown version. The version is not version 1 or version 2. Neighbor unknown Number of PIM control packets received (excluding PIM hello) without first receiving the hello packet. Bad Length Number of PIM control packets received for which the packet size does not match the PIM length field in the packet. Bad Checksum Number of PIM control packets received for which the calculated checksum does not match the checksum field in the packet. Bad Receive If Number of PIM control packets received on an interface that does not have PIM configured. Rx Bad Data Number of PIM control packets received that contain data for TCP. Bad register packets. Rx Intf disabled Number of PIM control packets received on an interface that has PIM disabled. Rx V1 Require V2 Number of PIM version 1 control packets received on an interface configured for PIM version 2. Rx V2 Require V1 Number of PIM version 2 control packets received on an interface configured for PIM version 1. Rx Register not RP Number of PIM register packets received when the router is not the RP for the group. Rx Register no route Number of PIM register packets received when the RP does not have a unicast route back to source. Rx Register no decap if Number of PIM register packets received when the RP does not have a de-encapsulation interface. Null Register Timeout Number of NULL register timeout packets. RP Filtered Source Number of PIM packets received when the router has a source address filter configured for the RP. 2237 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 287: show pim statistics Output Fields (continued) 2238 Field Name Field Description Rx Unknown Reg Stop Number of register stop messages with an unknown type. Rx Join/Prune no state Number of join and prune messages received for which the router has no state. Rx Join/Prune on upstream if Number of join and prune messages received on the interface used to reach the upstream router, toward the RP. Rx Join/Prune messages dropped Number of join and prune messages received and dropped. Rx sparse join for dense group Number of PIM sparse mode join messages received for a group that is configured for dense mode. Rx Graft/Graft Ack no state Number of graft and graft acknowledgement messages received for which the router has no state. Rx Graft on upstream if Number of graft messages received on the interface used to reach the upstream router, toward the RP. Rx CRP not BSR Number of BSR messages received in which the PIM message type is Candidate-RP-Advertisement, not Bootstrap. Rx BSR when BSR Number of BSR messages received in which the PIM message type is Bootstrap. Rx BSR not RPF if Number of BSR messages received on an interface that is not the RPF interface. Rx unknown hello opt Number of PIM hello packets received with options that Junos OS does not support. Rx data no state Number of PIM control packets received for which the router has no state for the data type. Rx RP no state Number of PIM control packets received for which the router has no state for the RP. Rx aggregate Number of PIM aggregate MDT packets received. Rx malformed packet Number of PIM control packets received with a malformed IP unicast or multicast address family. No RP Number of PIM control packets received with no RP address. No register encap if Number of PIM register packets received when the first-hop router does not have an encapsulation interface. Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Table 287: show pim statistics Output Fields (continued) Field Name Field Description No route upstream Number of PIM control packets received when the router does not have a unicast route to the the interface used to reach the upstream router, toward the RP. Nexthop Unusable Number of PIM control packets with an unusable nexthop. A path can be unusable if the route is hidden or the link is down. RP mismatch Number of PIM control packets received for which the router has an RP mismatch. RPF neighbor unknown Number of PIM control packets received for which the router has an unknown RPF neighbor for the source. Rx Joins/Prunes filtered The number of join and prune messages filtered because of configured route filters and source address filters. Tx Joins/Prunes filtered The number of join and prune messages filtered because of configured route filters and source address filters. Embedded-RP invalid addr Number of packets received with an invalid embedded RP address in PIM join messages and other types of messages sent between routing domains. Embedded-RP limit exceed Number of times the limit configure with the maximum-rps statement is exceeded. The maximum-rps statement limits the number of embedded RPs created in a specific routing instance. The range is from 1 through 500. The default is 100. Embedded-RP added Number of packets in which the embedded RP for IPv6 is added. The following receive events trigger extraction of an IPv6 embedded RP address on the router: • Multicast Listener Discovery (MLD) report for an embedded RP multicast group address • PIM join message with an embedded RP multicast group address • Static embedded RP multicast group address associated with an interface • Packets sent to an embedded RP multicast group address received on the DR An embedded RP node discovered through these receive events is added if it does not already exist on the routing platform. Embedded-RP removed Number of packets in which the embedded RP for IPv6 is removed. The embedded RP is removed whenever all PIM join states using this RP are removed or the configuration changes to remove the embedded RP feature. Rx Register msgs filtering drop Number of register messages dropped because of a filter configured for PIM register messages. 2239 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 287: show pim statistics Output Fields (continued) show pim statistics Field Name Field Description Tx Register msgs filtering drop Number of register messages dropped because of a filter configured for PIM register messages. user@host> show pim statistics PIM Message type Received Sent Rx errors 15 32 0 0 362 0 483 0 0 18 518 0 V2 Bootstrap 0 0 0 V2 Assert 0 0 0 V2 Graft 0 0 0 V2 Graft Ack 0 0 0 V2 Candidate RP 0 0 0 V1 Query 0 0 0 V1 Register 0 0 0 V1 Register Stop 0 0 0 V1 Join Prune 0 0 0 V1 RP Reachability 0 0 0 V1 Assert 0 0 0 V1 Graft 0 0 0 V1 Graft Ack 0 0 0 AutoRP Announce 0 0 0 AutoRP Mapping 0 0 0 AutoRP Unknown type 0 Anycast Register 0 0 0 Anycast Register Stop 0 0 0 V2 Hello V2 Register V2 Register Stop V2 Join Prune Global Statistics 2240 Chapter 80: Operational Mode Commands for IGMP Snooping and Multicast Hello dropped on neighbor policy 0 Unknown type 0 V1 Unknown type 0 Unknown Version 0 Neighbor unknown 5 Bad Length 0 Bad Checksum 0 Bad Receive If 0 Rx Bad Data 0 Rx Intf disabled 0 Rx V1 Require V2 0 Rx V2 Require V1 0 Rx Register not RP 0 Rx Register no route 0 Rx Register no decap if 0 Null Register Timeout 0 RP Filtered Source 0 Rx Unknown Reg Stop 0 Rx Join/Prune no state 0 Rx Join/Prune on upstream if 0 Rx Join/Prune messages dropped 0 Rx sparse join for dense group 0 Rx Graft/Graft Ack no state 0 Rx Graft on upstream if 0 Rx CRP not BSR 0 Rx BSR when BSR 0 Rx BSR not RPF if 0 Rx unknown hello opt 0 Rx data no state 0 Rx RP no state 0 2241 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2242 Rx aggregate 0 Rx malformed packet 0 No RP 0 No register encap if 0 No route upstream 0 Nexthop Unusable 0 RP mismatch 0 RPF neighbor unknown 0 Rx Joins/Prunes filtered 0 Embedded-RP invalid addr 0 Embedded-RP limit exceed 0 Embedded-RP added 0 Embedded-RP removed 0 Rx Register msgs filtering drop 0 Tx Register msgs filtering drop 0 PART 17 Access Control • 802.1X and MAC RADIUS Authentication Overview on page 2245 • Examples: Access Control Configuration on page 2267 • Configuring Access Control on page 2329 • Verifying 802.1X and MAC RADIUS Authentication on page 2355 • Configuration Statements for Access Control on page 2359 • Operational Commands for 802.1X on page 2465 2243 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2244 CHAPTER 81 802.1X and MAC RADIUS Authentication Overview • Security Features for J-EX Series Switches Overview on page 2245 • Understanding Authentication on J-EX Series Switches on page 2248 • 802.1X for J-EX Series Switches Overview on page 2253 • Authentication Process Flow for EX Series Switches on page 2255 • Understanding Server Fail Fallback and Authentication on J-EX Series Switches on page 2258 • Understanding Dynamic VLANs for 802.1X on J-EX Series Switches on page 2259 • Understanding Guest VLANs for 802.1X on J-EX Series Switches on page 2259 • Understanding 802.1X and RADIUS Accounting on J-EX Series Switches on page 2260 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding 802.1X and VSAs on J-EX Series Switches on page 2266 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 Ethernet 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. 2245 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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. 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: 2246 • 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. • 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 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 Chapter 81: 802.1X and MAC RADIUS Authentication Overview 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 • 802.1X for J-EX Series Switches Overview on page 2253 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding Proxy ARP on J-EX Series Switches on page 1059 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding the Use of Policers in Firewall Filters on page 2752 2247 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Authentication on J-EX Series Switches You can control access to your network through a J-EX Series Switch using several different authentication methods—802.1X, MAC RADIUS, or captive portal. Authentication prevents unauthorized devices and users from gaining access to your LAN. For 802.1X and MAC RADIUS authentication, end devices must be authenticated before they receive an IP address from a DHCP server. For captive portal authentication, the switch allows the devices to get an IP address, and allows DHCP, DNS and ARP packets. You can allow end devices to access the network without authentication by including the MAC address of the end device in the static MAC bypass list or, for captive portal, by including the MAC address of the end device in the authentication whitelist. You can configure 802.1X, MAC RADIUS, and captive portal on the same interface and in any combination, except that you cannot configure MAC RADIUS and captive portal on an interface without also configuring 802.1X. If you configure multiple authentication methods on a single interface, the switch falls back to another method if the first method is unsuccessful. For a description of the process flow when multiple authentication methods are configured on an interface, see “Authentication Process Flow for EX Series Switches” on page 2255. This topic covers: • A Basic Authentication Topology on page 2248 • 802.1X Authentication on page 2250 • MAC RADIUS Authentication on page 2250 • Captive Portal Authentication on page 2251 • Static MAC Bypass of Authentication on page 2252 • Fallback of Authentication Methods on page 2252 A Basic Authentication Topology Figure 45 on page 2249 illustrates a basic deployment topology for authentication on a J-EX Series switch: 2248 Chapter 81: 802.1X and MAC RADIUS Authentication Overview Figure 45: Example Authentication Topology 2249 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 802.1X Authentication 802.1X is an IEEE standard for port-based network access control (PNAC). It provides an authentication mechanism to allow devices to access a LAN. The 802.1X authentication feature on a J-EX Series switch is based upon the IEEE 802.1D standard Port-Based Network Access Control. The communication protocol between the end device and the switch is Extensible Authentication Protocol Over LAN (EAPOL). EAPOL is a version of EAP designed to work with Ethernet networks. The communication protocol between the authentication server and the switch is RADIUS. During the authentication process, the switch completes multiple message exchanges between the end device and the authentication server. While 802.1X authentication is in process, only 802.1X traffic is allowed. Other traffic, such as DHCP and HTTP, is blocked at the data link layer. NOTE: You can configure both the maximum number of times an EAPOL request packet is retransmitted and the timeout period between attempts. For information, see “Configuring 802.1X Interface Settings (CLI Procedure)” on page 2331. An 802.1X authentication configuration for a LAN contains three basic components: • Supplicant (also called end device)—Supplicant is the IEEE term for an end device that requests to join the network. The device can be responsive or nonresponsive. A responsive device is 802.1X-enabled and provides authentication credentials—specifically, a username and password for EAP MD5, or a username and client certificates for EAP-TLS, EAP-TTLS, and EAP-PEAP. A nonresponsive device is not 802.1X-enabled, but can be authenticated through a MAC-based authentication method. • Authenticator port access entity—The IEEE term for the authenticator. The J-EX Series switch is the authenticator, and it controls access by blocking all traffic to and from end devices until they are authenticated. • Authentication server—The authentication server contains the backend database that makes authentication decisions. It contains credential information for each end device that is allowed to connect to the network. The authenticator forwards credentials supplied by the end device to the authentication server. If the credentials forwarded by the authenticator match the credentials in the authentication server database, access is granted. If the credentials forwarded do not match, access is denied. The J-EX Series switches support RADIUS authentication servers. MAC RADIUS Authentication You can configure MAC RADIUS authentication on interfaces that are connected to end devices that are not 802.1X-enabled but that you want to allow to access the LAN. 2250 Chapter 81: 802.1X and MAC RADIUS Authentication Overview The EAP method supported for MAC RADIUS authentication on J-EX Series switches is EAP-MD5. If both 802.1X-enabled end-devices and end devices that are not 802.1X-enabled connect to an interface, you can configure both 802.1X and MAC RADIUS authentication methods on the interface. In this case, the switch will first attempt to authenticate using 802.1X, and if that method fails, it will attempt to authenticate the end device using MAC RADIUS authentication. If you know that only non-802.1X-enabled end devices will connect on that interface, you can eliminate the delay that occurs while the switch determines that the end device is not non-802.1X-enabled by configuring the mac-radius restrict option. When this option is configured, the switch will not attempt to authenticate the end device through 802.1X but instead immediately sends a request to the RADIUS server for authentication of the MAC address of the end device. If the MAC address of an end device is configured as permitted on the RADIUS server, the switch opens LAN access to the end device on the interface to which it is connected. This option is useful when no other 802.1X authentication methods, such as guest VLAN, are needed on the interface. When you configure mac-radius restrict on an interface to eliminate this delay, the switch drops all 802.1X packets. Captive Portal Authentication Captive portal authentication (hereafter referred to as captive portal) allows you to authenticate users on J-EX Series switches by redirecting Web browser requests to a login page that requires users to input a username and password before they are allowed access to the network. Captive portal controls network access by requiring users to provide information that is authenticated against a RADIUS server database using EAP-MD5. You can also use captive portal to display an acceptable-use policy to users before they access your network. Junos OS for J-EX Series switches provides a template that allows you to easily design and modify the look of the captive portal login page. You enable specific interfaces for captive portal. The first time an end device connected to a captive portal interface attempts to access a web page, the switch presents the captive portal login page. Upon successful authentication, the user is allowed access to the network and to continue to the original page requested. NOTE: If Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) is enabled, Hypertext Transfer Protocol (HTTP) requests are redirected to an HTTPS connection for the captive portal authentication process. After authentication, the end device is returned to the HTTP connection. If there are end devices that are not HTTP-enabled connected to the captive portal interface, you can allow them to bypass captive portal authentication by adding their MAC address to an authentication whitelist. When the user is authenticated by the RADIUS server, any per-user policies (attributes) associated with that user are also sent to the switch. 2251 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Captive portal on J-EX Series switches has the following limitations: • The captive portal interface must be configured for family ethernet-switching and set to port mode access. • Captive portal does not support dynamic assignment of VLANs downloaded from the RADIUS server. • If the user is idle for more than about 5 minutes and there is no traffic passed, the user must log back in to the captive portal. Static MAC Bypass of Authentication You can allow end devices to access the LAN without authentication on a RADIUS server by including their MAC addresses in the static MAC bypass list (also known as the exclusion list). You might choose to include a device in the bypass list to: • Allow non-802.1X-enabled devices access to the LAN. • Eliminate the delay that occurs while the switch determines that a connected device is a non-802.1X-enabled host. When you configure static MAC on the switch, the MAC address of the end device is first checked in a local database (a user-configured list of MAC addresses). If a match is found, the end device is successfully authenticated and the interface is opened up for it. No further authentication is done for that end device. If a match is not found and 802.1X authentication is enabled on the switch, the switch attempts to authenticate the end device through the RADIUS server. For each MAC address, you can also configure the VLAN to which the end device is moved or the interfaces on which the host connects. Fallback of Authentication Methods You can configure one or more authentication methods on a single interface and thus enable fallback to the next method if the first or second method fails. If an interface is configured in multiple supplicant mode, all end devices connecting through the interface must use either captive portal or a combination of 802.1X and MAC RADIUS, captive portal cannot be mixed with 802.1X or MAC RADIUS. Therefore, if there is already an end device on the interface that was authenticated through 802.1X or MAC RADIUS authentication, then additional end devices authenticating do not fall back to captive portal. If only 802.1X authentication or MAC RADIUS authentication is configured, some end devices can be authenticated using 802.1X and others can still be authenticated using MAC RADIUS. Fallback of authentication methods occurs in the following order: 1. 2252 802.1X authentication—If 802.1X is configured on the interface, the switch sends EAPOL requests to the end device and attempts to authenticate the end device through 802.1X authentication. If the end device does not respond to the EAP requests, the switch checks whether MAC RADIUS authentication is configured on the interface. Chapter 81: 802.1X and MAC RADIUS Authentication Overview 2. MAC RADIUS authentication—If MAC RADIUS authentication is configured on the interface, the switch sends the MAC RADIUS address of the end device to the authentication server. If MAC RADIUS authentication is not configured, the switch checks whether captive portal is configured on the interface. 3. Captive portal authentication—If captive portal is configured on the interface, the switch attempts to authenticate using this method after attempting any other configured authentication methods. If an end device is authenticated on the interface using captive portal, this becomes the active authentication method on the interface. When captive portal is the active authentication method, the switch falls back to 802.1X authentication if there are no sessions in the authenticated state and if the interface receives an EAP packet. Related Documentation • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 • Configuring Static MAC Bypass of Authentication (CLI Procedure) on page 2334 • Authentication Process Flow for J-EX Series Switches on page 2255 802.1X for J-EX Series Switches Overview IEEE 802.1X provides network edge security, protecting Ethernet LANs from unauthorized user access. How 802.1X Authentication Works 802.1X authentication works by using an Authenticator Port Access Entity (the switch) to block all traffic to and from a supplicant (end device) at the port until the supplicant's credentials are presented and matched on the Authentication server (a RADIUS server). When authenticated, the switch stops blocking traffic and opens the port to the supplicant. The end device is authenticated in either single mode, single-secure mode, or multiple mode: • single—Authenticates only the first end device. All other end devices that connect later to the port are allowed full access without any further authentication. They effectively “piggyback” on the end devices’ authentication. • single-secure—Allows only one end device to connect to the port. No other end device is allowed to connect until the first logs out. • multiple—Allows multiple end devices to connect to the port. Each end device will be authenticated individually. 2253 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Network access can be further defined using VLANs and firewall filters, which both act as filters to separate and match groups of end devices to the areas of the LAN they require. 802.1X Features Overview 802.1X features on J-EX Series Switches are: • Guest VLAN—Provides limited access to a LAN, typically just to the Internet, for supplicants that fail 802.1X authentication. • Server-reject VLAN—Provides limited access to a LAN, typically just to the Internet, for end devices that fail MAC RADIUS authentication. • Dynamic VLAN—Enables a supplicant, after authentication, to be a member of a VLAN dynamically. • Private VLAN—Enables configuration of 802.1X authentication on interfaces that are members of private VLANs (PVLANs). • Dynamic changes to a user session—Allows the switch administrator to terminate an already authenticated session. This feature is based on support of the RADIUS Disconnect Message defined in RFC 3576. • Support for VoIP—Supports IP telephones. If the phone is 802.1X-enabled, it is authenticated like any other supplicant. If the phone is not 802.1X-enabled, but has another 802.1X-compatible device connected to its data port, that device is authenticated, and then VoIP traffic can flow to and from the phone (providing that the interface is configured in single mode and not in single-secure mode). NOTE: Configuring a VoIP VLAN on private VLAN (PVLAN) interfaces is not supported. • RADIUS accounting—Sends accounting information to the RADIUS accounting server. Accounting information is sent to the server whenever a subscriber logs in or logs out and whenever a subscriber activates or deactivates a subscription. • Vendor Specific Attributes (VSAs)—Supports the Juniper-Switching-Filter attribute on the RADIUS authentication server that can be used further define a supplicant's access during the 802.1X authentication process. Centrally configuring VSAs on the authentication server does away with the need to configure these same attributes in the form of firewall filters on every switch in the LAN to which the supplicant may connect to the LAN. This feature is based on RLI 4583, AAA RADIUS BRAS VSA Support. Supported Features Related to 802.1X Authentication 802.1X does not replace other security technologies. 802.1X works together with port security features, such as DHCP snooping, dynamic ARP inspection (DAI), and MAC limiting, to guard against spoofing. 2254 Chapter 81: 802.1X and MAC RADIUS Authentication Overview Supported features related to authentication include: Related Documentation • Static MAC bypass—Provides a bypass mechanism to authenticate devices that are not 802.1X-enabled (such as printers). Static MAC bypass connects these devices to 802.1X-enabled ports, bypassing 802.1X authentication. • MAC RADIUS authentication—Provides a means to enable or disable MAC authentication independently of whether 802.1X authentication is enabled. • Understanding Authentication on J-EX Series Switches on page 2248 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding 802.1X and RADIUS Accounting on J-EX Series Switches on page 2260 • Understanding Guest VLANs for 802.1X on J-EX Series Switches on page 2259 • Understanding 802.1X and VSAs on J-EX Series Switches on page 2266 • Understanding Server Fail Fallback and Authentication on J-EX Series Switches on page 2258 Authentication Process Flow for EX Series Switches You can control access to your network through a J-EX Series switch by using several different authentication methods—802.1X, MAC RADIUS, or captive portal. Figure 46 on page 2256 illustrates the authentication process: 2255 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 46: Authentication Process Flow for a J-EX Series Switch The basic authentication process works like this: 1. Authentication is initiated by an end device sending an EAP request or a data packet. 2. If the MAC address of the end device is in the static MAC bypass list or the authentication whitelist, the switch accepts the end device without querying the authentication server and allows the end device to access the LAN. 3. If the MAC address is not in the static MAC bypass list or the authentication whitelist, the switch checks whether an authenticator statement is configured on the interface. If an authenticator is not configured, the switch checks for captive portal configuration—skip to Step 6. If an authenticator is configured: a. The switch checks whether the mac-radius restrict statement is configured on the interface. If mac-radius restrict is configured, the switch does not attempt 802.1X authentication—skip to Step 5. If it is configured, go on to Step 2. b. The switch sends either an EAP request (if the end device initiated contact with a data packet) or an EAP response (if the end device initiated contact with an EAPOL-start message). c. If there is no response, the switch tries sending an EAP request two more times. 2256 Chapter 81: 802.1X and MAC RADIUS Authentication Overview NOTE: You can configure both the maximum number of times an EAPOL request packet is retransmitted and the timeout period between attempts. See “Configuring 802.1X Interface Settings (CLI Procedure)” on page 2331. d. If the end device does not respond to the EAP messages sent by the switch, the switch checks for MAC RADIUS configuration—skip to Step 4. If it does respond, go on to step 5. e. When an EAP request is received from the end device, the switch sends an authentication request message to the authentication server. If the authentication server does not respond, the switch checks whether there is a server fail VLAN configured. If there is a server fail VLAN, the switch performs the configured server fail fallback operation. If there is no server fail VLAN, skip to Step 6. f. The authentication server sends an access-accept or access-reject message. If the authentication server sends an access-reject message, skip to Step 8. 4. If the end device does not respond to the EAP messages, the switch checks whether MAC RADIUS authentication is configured on the interface. If it is not configured, skip to Step 6. 5. If MAC RADIUS authentication is configured on the interface: a. The switch sends a MAC RADIUS authentication request to the authentication server. The switch sends only one such request. If the authentication server does not respond, the switch checks whether there is a server fail VLAN configured on the switch. If there is a server fail VLAN, the switch performs the configured server fail fallback operation. If there is no server fail VLAN, skip to Step 8. b. The authentication server sends an access-accept or access-reject message. If the authentication server sends an access-reject message, go on to Step 6. 6. If MAC RADIUS authentication is not configured on the interface or if the authentication server responds with an access-reject message for MAC RADIUS authentication, the switch checks whether captive portal is configured on the interface. If captive portal is not configured on the interface, skip to Step 8. 7. If captive portal authentication is configured on the interface: a. The switch sends a request to the user on the end device for captive portal authentication information. b. The switch sends the captive portal authentication information to the authentication server. c. The authentication server sends an access-accept or access-reject message. If the server sends an access-reject message, go on to Step 8. 2257 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: If an end device is authenticated on the interface using captive portal, this becomes the active authentication method on the interface. When captive portal is the active authentication method, the switch falls back to 802.1X authentication if there are no sessions in the authenticated state and if the interface receives an EAP packet. 8. The switch checks whether there is a guest VLAN configured on the switch. If a guest VLAN is configured, the switch allows the end device limited access to the LAN. Related Documentation • Configuring Server Fail Fallback (CLI Procedure) on page 2337 • Understanding Server Fail Fallback and Authentication on J-EX Series Switches on page 2258 • Understanding Guest VLANs for 802.1X on J-EX Series Switches on page 2259 • Understanding Authentication onJ-EX Series Switches on page 2248 • Understanding Dynamic VLANs for 802.1X on J-EX Series Switches on page 2259 Understanding Server Fail Fallback and Authentication on J-EX Series Switches Server fail fallback allows you to specify how end devices connected to the switch are supported if the RADIUS authentication server becomes unavailable or sends an Extensible Authentication Protocol Over LAN (EAPOL) access-reject message. J-EX Series Switches use authentication to implement access control in an enterprise network. If 802.1X, MAC RADIUS, or captive portal authentication are configured on the interface, end devices are evaluated at the initial connection by an authentication (RADIUS) server. If the end device is configured on the authentication server, the device is granted access to the LAN and the J-EX Series switch opens the interface to permit access. A RADIUS server timeout occurs if no RADIUS authentication servers are reachable when a supplicant logs in and attempts to access the LAN. Server fail fallback allows you to specify one of four actions to be taken towards end devices awaiting authentication when the server is timed out: 2258 • Permit authentication, allowing traffic to flow from the end device through the interface as if the end device were successfully authenticated by the RADIUS server. • Deny authentication, preventing traffic from flowing from the end device through the interface. This is the default. • Move the end device to a specified VLAN. (The VLAN must already exist on the switch.) • Sustain authenticated end devices that already have LAN access and deny unauthenticated end devices. If the RADIUS servers time out during reauthentication, previously authenticated end devices are reauthenticated and new users are denied LAN access. Chapter 81: 802.1X and MAC RADIUS Authentication Overview Server fail fallback is triggered most often during reauthentication when the already configured and in-use RADIUS server becomes inaccessible. However, server fail fallback can also be triggered by an end device’s first attempt at authentication through the RADIUS server. Server fail fallback allows you to specify that an end device be moved to a specified VLAN if the switch receives an EAPOL accept-reject message. The configured VLAN name overrides any attributes sent by the server. Related Documentation • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configuring 802.1X Authentication Options When the RADIUS Server is Unavailable to a J-EX Series Switch on page 2271 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 Understanding Dynamic VLANs for 802.1X on J-EX Series Switches Dynamic VLANs, in conjunction with the 802.1X authentication process, provide secure access to the LAN for supplicants belonging to different VLANs on a single port. When this feature is configured, a supplicant becomes a member of a VLAN dynamically after 802.1X authentication is successful. Successful authentication requires that the VLAN ID or VLAN name exist on the switch and match the VLAN ID or VLAN name sent by the RADIUS server during authentication. If the VLAN does not exist, the supplicant is unauthenticated. If a guest VLAN is established, the unauthenticated supplicant is automatically moved to the guest VLAN. Related Documentation • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Understanding Guest VLANs for 802.1X on J-EX Series Switches on page 2259 Understanding Guest VLANs for 802.1X on J-EX Series Switches Guest VLANs, in conjunction with 802.1X authentication, provide secure access to the LAN for corporate guests and for supplicants who fail the 802.1X authentication process. When a corporate visitor attempts to authenticate on the LAN, and authentication fails, the visitor is moved to a guest VLAN. A guest VLAN typically provides access only to the Internet. A guest VLAN can also provide limited access to the LAN in cases when authentication fails for supplicants that are not visitors. When authentication fails, the switch receives an Access-Reject message for the client, and checks if a guest VLAN is configured on that port. If so, it moves that user alone to the guest VLAN. If the Access-reject message 2259 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS contains optional VLAN information, then the user is moved to the VLAN specified by the RADIUS server and not to the locally configured guest-VLAN. Authentication can fail for many reasons: • The host device does not have supplicant software on it (for example, the host is not 802.1X-enabled, such as a printer). • The supplicant provided invalid credentials—a username or password that were not authenticated by the authentication server. For hosts that are not 802.1X-enabled, the guest VLAN could allow limited access to a server from which the non-802.1X-enabled host can download the supplicant software and attempt authentication again. Related Documentation • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Understanding Dynamic VLANs for 802.1X on J-EX Series Switches on page 2259 Understanding 802.1X and RADIUS Accounting on J-EX Series Switches J-EX Series Switches support IETF RFC 2866, RADIUS Accounting. Configuring RADIUS accounting on a J-EX Series switch permits statistical data about users logging onto or off a LAN to be collected and sent to a RADIUS accounting server. The statistical data gathered can be used for general network monitoring, to analyze and track usage patterns, or to bill a user based upon the amount of time or type of services accessed. To configure RADIUS accounting, specify one or more RADIUS accounting servers to receive the statistical data from the switch, and select the type of accounting data to be collected. The RADIUS accounting server you specify can be the same server used for RADIUS authentication, or it can be a separate RADIUS server. You can specify a list of RADIUS accounting servers. In the event that the primary server (the first one configured) is unavailable, each RADIUS server in the list is tried in the order in which they are configured in the Junos OS. The RADIUS accounting process between a switch and a RADIUS server works like this: 1. A RADIUS accounting server listens for User Datagram Protocol (UDP) packets on a specific port. For example, on FreeRADIUS, the default port is 1813. 2. The switch forwards an accounting-request packet containing an event record to the accounting server. For example, a supplicant is authenticated through 802.1X authentication and connected to the LAN. The event record associated with this supplicant contains an Acct-Status-Type attribute whose value indicates the beginning of user service for this supplicant. When the supplicant's session ends, the accounting request will contain an Acct-Status-Type attribute value indicating the end of user service. The RADIUS accounting server records this as a stop-accounting record containing session information and the length of the session. 2260 Chapter 81: 802.1X and MAC RADIUS Authentication Overview 3. The RADIUS accounting server logs these events as start-accounting or stop-accounting records. The records are in a file. On FreeRADIUS, the file name is the server's address; for example, 122.69.1.250. 4. The accounting server sends an accounting-response packet back to the switch confirming it has received the accounting request. 5. If the switch does not receive a response from the server, it continues to send accounting requests until an accounting response is returned from the accounting server. The statistics collected through this process can be displayed from the RADIUS server; to see those statistics, the user accesses the log file configured to receive them. Related Documentation • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • 802.1X for J-EX Series Switches Overview on page 2253 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches J-EX Series Switches use Link Layer Discovery Protocol (LLDP) and Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) to learn and distribute device information on network links. The information allows the switch to quickly identify a variety of devices, resulting in a LAN that interoperates smoothly and efficiently. LLDP-capable devices transmit information in type, length, and value (TLV) messages to neighbor devices. Device information can include specifics, such as chassis and port identification and system name and system capabilities. The TLVs leverage this information from parameters that have already been configured in the Junos OS. LLDP-MED goes one step further, exchanging IP-telephony messages between the switch and the IP telephone. These TLV messages provide detailed information on PoE policy. The PoE Management TLVs let the switch ports advertise the power level and power priority needed. The switch also uses these protocols to ensure that voice traffic gets tagged and prioritized with the correct values at the source itself. For example, 802.1p CoS and 802.1Q tag information can be sent to the IP telephone. J-EX Series switches support the following basic TLVs: • Chassis Identifier—The MAC address associated with the local system. • Port identifier—The port identification for the specified port in the local system. • Port Description—The user-configured port description. The port description can be a maximum of 256 characters. • System Name—The user-configured name of the local system. The system name can be a maximum of 256 characters. 2261 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • System Description—The system description containing information about the software and current image running on the system. This information is not configurable, but taken from the software. • System Capabilities—The primary function performed by the system. The capabilities that system supports; for example, bridge or router. This information is not configurable, but based on the model of the product. • Management Address—The IP management address of the local system. J-EX Series switches support the following 802.3 TLVs: • Power via MDI—A TLV that advertises MDI power support, PSE power pair, and power class information. • MAC/PHY Configuration Status—A TLV that advertises information about the physical interface, such as autonegotiation status and support and MAU type. The information is not configurable, but based on the physical interface structure. • Link Aggregation—A TLV that advertises if the port is aggregated and its aggregated port ID. • Maximum Frame Size—A TLV that advertises the Maximum Transmission Unit (MTU) of the interface sending LLDP frames. • Port Vlan—A TLV that advertises the VLAN name configured on the interface. J-EX Series switches support the following LLDP-MED TLVs: • LLDP MED Capabilities—A TLV that advertises the primary function of the port. The capabilities values range 0 through 15: • 2262 • 0—Capabilities • 1—Network Policy • 2—Location Identification • 3—Extended Power via MDI-PSE • 4—Inventory • 5–15—Reserved LLDP-MED Device Class Values: • 0—Class not defined. • 1—Class 1 Device. • 2—Class 2 Device. • 3—Class 3 Device. • 4—Network Connectivity Device • 5–255—Reserved. Chapter 81: 802.1X and MAC RADIUS Authentication Overview • Network Policy—A TLV that advertises the port VLAN configuration and associated Layer 2 and Layer 3 attributes. Attributes include the policy identifier, application types, such as voice or streaming video, 802.1Q VLAN tagging, and 802.1p priority bits and Diffserv code points. • Endpoint Location—A TLV that advertises the physical location of the endpoint. • Extended Power via MDI—A TLV that advertises the power type, power source, power priority, and power value of the port. It is the responsibility of the PSE device (network connectivity device) to advertise the power priority on a port. Related Documentation • Understanding Layer 2 Protocol Tunneling on J-EX Series Switches on page 1056 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Configuring LLDP (CLI Procedure) on page 2344 Understanding 802.1X and VoIP on J-EX Series Switches When you use Voice over IP (VoIP), you can connect IP telephones to the switch and configure IEEE 802.1X authentication for 802.1X-compatible IP telephones. The 802.1X authentication provides network edge security, protecting Ethernet LANs from unauthorized user access. VoIP is a protocol used for the transmission of voice through packet-switched networks. VoIP transmits voice calls using a network connection instead of an analog phone line. When VoIP is used with 802.1X, the RADIUS server authenticates the phone, and Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) provides the class-of-service (CoS) parameters to the phone. You can configure 802.1X authentication to work with VoIP in multiple supplicant or single supplicant mode. In multiple-supplicant mode, the 802.1X process allows multiple supplicants to connect to the interface. Each supplicant will be authenticated individually. For an example of a VoIP multiple supplicant topology, see Figure 47 on page 2264. 2263 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 47: VoIP Multiple Supplicant Topology If an 802.1X-compatible IP telephone does not have an 802.1X host but has another 802.1X-compatible device connected to its data port, you can connect the phone to an interface in single-supplicant mode. In single-supplicant mode, the 802.1X process authenticates only the first supplicant. All other supplicants who connect later to the interface are allowed full access without any further authentication. They effectively “piggyback” on the first supplicant’s authentication. For an example of a VoIP single supplicant topology, see Figure 48 on page 2265 . 2264 Chapter 81: 802.1X and MAC RADIUS Authentication Overview Figure 48: VoIP Single Supplicant Topology If an IP telephone does not support 802.1X, you can configure VoIP to bypass 802.1X and LLDP-MED and have the packets forwarded to a VoIP VLAN, Related Documentation • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 2265 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding 802.1X and VSAs on J-EX Series Switches J-EX Series Switches support the configuration of RADIUS server attributes specific to Juniper Networks. These attributes are known as vendor-specific attributes (VSAs) and are described in RFC 2138, Remote Authentication Dial In User Service (RADIUS). Through VSAs, you can configure port-filtering attributes on the RADIUS server. VSAs are clear text fields sent from the RADIUS server to the switch as a result of the 802.1X authentication success or failure. The 802.1X authentication prevents unauthorized user access by blocking a supplicant at the port until the supplicant is authenticated by the RADIUS server. The VSA attributes are interpreted by the switch during authentication, and the switch takes appropriate actions. Implementing port-filtering attributes with 802.1X authentication on the RADIUS server provides a central location for controlling LAN access for supplicants. These port-filtering attributes specific to Juniper Networks are encapsulated in a RADIUS server VSA with the vendor ID set to the Juniper Networks ID number, 2636. As well as configuring port-filtering attributes through VSAs, you can apply a port firewall filter that has already been configured on the switch directly to the RADIUS server. Like port-filtering attributes, the filter is applied during the 802.1X authentication process, and its actions are applied at the switch port. Adding a port firewall filter to a RADIUS server eliminates the need to add the filter to multiple ports and switches. For more information, see “Example: Applying a Firewall Filter to 802.1X-Authenticated Supplicants Using RADIUS Server Attributes on a J-EX Series Switch” on page 2296. VSAs are only supported for 802.1X single-supplicant configurations and multiple-supplicant configurations. Related Documentation 2266 • Understanding Authentication onJ-EX Series Switches on page 2248 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Configuring Firewall Filters (CLI Procedure) on page 2779 • VSA Match Conditions and Actions for J-EX Series Switches on page 2348 CHAPTER 82 Examples: Access Control Configuration • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Example: Configuring 802.1X Authentication Options When the RADIUS Server is Unavailable to a J-EX Series Switch on page 2271 • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Applying a Firewall Filter to 802.1X-Authenticated Supplicants Using RADIUS Server Attributes on a J-EX Series Switch on page 2296 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 • Example: Applying Firewall Filters to Multiple Supplicants on Interfaces Enabled for 802.1X or MAC RADIUS Authentication on page 2318 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch 802.1X is the IEEE standard for Port-Based Network Access Control (PNAC). You use 802.1X to control network access. Only users and devices providing credentials that have been verified against a user database are allowed access to the network. You can use a RADIUS server as the user database for 802.1X authentication, as well as for MAC RADIUS authentication. 2267 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to connect a RADIUS server to a J-EX Series switch, and configure it for 802.1X: • Requirements on page 2268 • Overview and Topology on page 2268 • Configuration on page 2270 • Verification on page 2271 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The ports on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • One RADIUS authentication server that supports 802.1X. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you connect the server to the switch, be sure you have: • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Configured users on the RADIUS authentication server. Overview and Topology The J-EX Series switch acts as an authenticator Port Access Entity (PAE). It blocks all traffic and acts as a control gate until the supplicant (client) is authenticated by the server. All other users and devices are denied access. Figure 49 on page 2269 shows one J-EX4200 switch that is connected to the devices listed in Table 288 on page 2270. 2268 Chapter 82: Examples: Access Control Configuration Figure 49: Topology for Configuration 2269 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 288: Components of the Topology Property Settings Switch hardware J-EX4200 access switch, 24 Gigabit Ethernet ports: 8 PoE ports (ge-0/0/0 through ge-0/0/7) and 16 non-PoE ports (ge-0/0/8 through ge-0/0/23) VLAN name default One RADIUS server Backend database with an address of 10.0.0.100 connected to the switch at port ge-0/0/10 In this example, connect the RADIUS server to access port ge-0/0/10 on the J-EX4200 switch. The switch acts as the authenticator and forwards credentials from the supplicant to the user database on the RADIUS server. You must configure connectivity between the J-EX4200 and the RADIUS server by specifying the address of the server and configuring the secret password. This information is configured in an access profile on the switch. NOTE: For more information about authentication, authorization, and accounting (AAA) services, please see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Configuration CLI Quick Configuration To quickly connect the RADIUS server to the switch, copy the following commands and paste them into the switch terminal window: [edit] set access radius-server 10.0.0.100 secret juniper set access profile profile1 authentication-order radius set access profile profile1 radius authentication-server 10.0.0.100 10.2.14.200 Step-by-Step Procedure To connect the RADIUS server to the switch: 1. Define the address of the server, and configure the secret password. The secret password on the switch must match the secret password on the server: [edit access] user@switch# set radius-server 10.0.0.100 secret juniper 2. Configure the authentication order, making radius the first method of authentication: [edit access profile] user@switch# set profile1 authentication-order radius 3. Configure a list of server IP addresses to be tried in order to authenticate the supplicant: [edit access profile] user@switch# set profile1 radius authentication-server 10.0.0.100 10.2.14.200 Results Display the results of the configuration: user@switch> show configuration access 2270 Chapter 82: Examples: Access Control Configuration radius-server { 10.0.0.100 port 1812; secret "$9$qPT3ApBSrv69rvWLVb.P5"; ## SECRET-DATA } } profile profile1{ authentication-order radius; radius { authentication-server 10.0.0.100 10.2.14.200; } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verify That the Switch and RADIUS Server are Properly Connected on page 2271 Verify That the Switch and RADIUS Server are Properly Connected Purpose Action Verify that the RADIUS server is connected to the switch on the specified port. Ping the RADIUS server to verify the connection between the switch and the server: user@switch> ping 10.0.0.100 PING 10.0.0.100 (10.0.0.100): 56 data bytes 64 bytes from 10.93.15.218: icmp_seq=0 ttl=64 time=9.734 ms 64 bytes from 10.93.15.218: icmp_seq=1 ttl=64 time=0.228 ms Meaning Related Documentation ICMP echo request packets are sent from the switch to the target server at 10.0.0.100 to test whether it is reachable across the IP network. ICMP echo responses are being returned from the server, verifying that the switch and the server are connected. • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 Example: Configuring 802.1X Authentication Options When the RADIUS Server is Unavailable to a J-EX Series Switch Server fail fallback allows you to specify how 802.1X supplicants connected to the switch are supported if the RADIUS authentication server becomes unavailable or sends an EAP Access-Reject message. 2271 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS You use 802.1X to control network access. Only users and devices (supplicants) providing credentials that have been verified against a user database are allowed access to the network. You use a RADIUS server as the user database. This example describes how to configure an interface to move a supplicant to a VLAN in the event of a RADIUS server timeout: • Requirements on page 2272 • Overview and Topology on page 2272 • Configuration on page 2274 • Verification on page 2275 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The ports on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • One RADIUS authentication server that supports 802.1X. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you connect the server to the switch, be sure you have: • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Set up a connection between the switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Disable firewall filters on the interface. Firewall filters interfere with server fail fallback operation. • Configured users on the authentication server. Overview and Topology A RADIUS server timeout occurs if no authentication RADIUS servers are reachable when a supplicant logs in and attempts to access the LAN. Using server fail fallback, configure alternative options for supplicants attempting LAN access. You can configure the switch to accept or deny access to supplicants or to maintain the access already granted towards supplicants before the RADIUS server timeout. Additionally, you can configure the switch to move supplicants to a specific VLAN if a RADIUS timeout occurs or if the RADIUS server sends an EAP Access-Reject message. Figure 50 on page 2273 shows the topology used for this example. The RADIUS server is connected to the J-EX4200 switch on access port ge-0/0/10. The switch acts as the authenticator Port Access Entity (PAE) and forwards credentials from the supplicant to the user database on the RADIUS server. The switch blocks all traffic and acts as a control gate until the supplicant is authenticated by the authentication server. A supplicant is connected to the switch through interface ge-0/0/1. 2272 Chapter 82: Examples: Access Control Configuration Figure 50: Topology for Configuration Table 289 on page 2273 describes the components in this topology. Table 289: Components of the Topology Property Settings Switch hardware J-EX4200 access switch, 24 Gigabit Ethernet ports: 8 PoE ports. VLAN names default VLAN vlan-sf VLAN Supplicant Supplicant attempting access on interface ge-0/0/1 One RADIUS server Backend database with an address of 10.0.0.100 connected to the switch at port ge-0/0/10 In this example, configure interface ge-0/0/1 to move a supplicant attempting access to the LAN during a RADIUS timeout to another VLAN. A RADIUS timeout prevents the normal exchange of EAP messages that carry information from the RADIUS server to the switch and permit the authentication of a supplicant. The default VLAN is configured on 2273 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface ge-0/0/1. When a RADIUS timeout occurs, supplicants on the interface will be moved from the default VLAN to the VLAN named vlan-sf. NOTE: For more information about authentication, authorization, and accounting (AAA) services, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Configuration To configure server fail fallback on the switch: CLI Quick Configuration To quickly configure server fail fallback on the switch, copy the following commands and paste them into the switch terminal window: [edit protocols dot1x authenticator] set interface ge-0/0/1 server-fail vlan-name vlan-sf Step-by-Step Procedure To configure an interface to divert supplicants to a specific VLAN when a RADIUS timeout occurs (here, the VLAN is vlan-sf): 1. Define the VLAN to which supplicants are diverted: [edit protocols dot1x authenticator] user@switch# set interface server-fail vlan-name vlan-sf Results Display the results of the configuration: user@switch> show configuration interfaces { ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members default; } } } } protocols { dot1x { authenticator { authentication-profile-name profile52; interface { ge-0/0/1.0 { server-fail vlan-name vlan-sf; } } } } } } 2274 Chapter 82: Examples: Access Control Configuration Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That the Supplicants Are Moved to an Alternative VLAN During a RADIUS Timeout on page 2275 Verifying That the Supplicants Are Moved to an Alternative VLAN During a RADIUS Timeout Purpose Action Verify that the interface moves supplicants to an alternative VLAN during a RADIUS timeout. Display the VLANs configured on the switch; the interface ge-0/0/1.0 is a member of the default VLAN: user@switch> show vlans Name Tag Interfaces default ge-0/0/0.0, ge-0/0/1.0*, ge-0/0/5.0*, ge-0/0/10.0, ge-0/0/12.0*, ge-0/0/14.0*, ge-0/0/15.0, ge-0/0/20.0 v2 77 None vlan—sf 50 None mgmt me0.0* Display 802.1X protocol information on the switch to view supplicants that are authenticated on interface ge-0/0/1.0: user@switch> show dot1x interface brief 802.1X Information: Interface Role State ge-0/0/1.0 Authenticator Authenticated ge-0/0/10.0 Authenticator Initialize ge-0/0/14.0 Authenticator Connecting ge-0/0/15.0 Authenticator Initialize ge-0/0/20.0 Authenticator Initialize MAC address 00:00:00:00:00:01 User abc A RADIUS server timeout occurs. Display the Ethernet switching table to show that the supplicant with the MAC address 00:00:00:00:00:01 previously accessing the LAN through the default VLAN is now being learned on the VLAN named vlan-sf: user@switch> show ethernet-switching table Ethernet-switching table: 3 entries, 1 learned VLAN MAC address Type v1 * Flood vlan—sf 00:00:00:00:00:01 Learn default * Flood Age 1:07 - Interfaces All-members ge-0/0/1.0 All-members Display 802.1X protocol information to show that interface ge-0/0/1.0 is connecting and will open LAN access to supplicants: user@switch> show dot1x interface brief 2275 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 802.1X Information: Interface Role ge-0/0/1.0 Authenticator ge-0/0/10.0 Authenticator ge-0/0/14.0 Authenticator ge-0/0/15.0 Authenticator ge-0/0/20.0 Authenticator Meaning Related Documentation State Connecting Initialize Connecting Initialize Initialize MAC address User The command show vlans displays interface ge-0/0/1.0 as a member of the default VLAN. The command show dot1x interface brief shows that a supplicant (abc) is authenticated on interface ge-0/0/1.0 and has the MAC address 00:00:00:00:00:01. A RADIUS server timeout occurs, and the authentication server cannot be reached by the switch. The command show-ethernet-switching table shows that MAC address 00:00:00:00:00:01 is learned on VLAN vlan-sf. The supplicant has been moved from the default VLAN to the vlan-sf VLAN. The supplicant is then connected to the LAN through the VLAN named vlan-sf. • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Understanding Server Fail Fallback and Authentication on J-EX Series Switches on page 2258 Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch 802.1X on J-EX Series switches provides LAN access to users who do not have credentials in the RADIUS database. These users, referred to as guests, are authenticated and typically provided with access to the Internet. This example describes how to create a guest VLAN and configure 802.1X authentication for it. • Requirements on page 2276 • Overview and Topology on page 2277 • Configuration of a Guest VLAN That Includes 802.1X Authentication on page 2279 • Verification on page 2280 Requirements This example uses the following hardware and software components: • 2276 One J-EX Series switch acting as an authenticator interface access entity (PAE). The interfaces on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. Chapter 82: Examples: Access Control Configuration • One RADIUS authentication server that supports 802.1X. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you configure guest VLAN authentication, be sure you have: • Installed your J-EX Series switch. See Installing and Connecting a J-EX4200 Switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. Overview and Topology As part of IEEE 802.1X Port-Based Network Access Control (PNAC), you can provide limited network access to supplicants who do not belong to a VLAN authentication group by configuring authentication to a guest VLAN. Typically, guest VLAN access is used to provide Internet access to visitors to a corporate site. However, you can also use the guest VLAN feature to provide supplicants that fail 802.1X authentication to a corporate LAN with access to a VLAN with limited resources. Figure 51 on page 2278 shows the conference room connected to the switch at interface ge-0/0/1. 2277 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 51: Topology for Guest VLAN Example 2278 Chapter 82: Examples: Access Control Configuration Table 290: Components of the Guest VLAN Topology Property Settings Switch hardware J-EX4200 switch, 24 Gigabit Ethernet interfaces: 8 PoE interfaces (ge-0/0/0 through ge-0/0/7) and 16 non-PoE interfaces (ge-0/0/8 through ge-0/0/23) VLAN names and tag IDs sales, tag 100 support, tag 200 guest-vlan, tag 300 One RADIUS server Backend database connected to the switch through interface ge-0/0/10 In this example, access interface ge-0/0/1 provides LAN connectivity in the conference room. Configure this access interface to provide LAN connectivity to visitors in the conference room who are not authenticated by the corporate VLAN. Configuration of a Guest VLAN That Includes 802.1X Authentication To create a guest VLAN and configure 802.1X authentication, perform these tasks: CLI Quick Configuration To quickly configure a guest VLAN, with 802.1X authentication, copy the following commands and paste them into the switch terminal window: [edit] set vlans guest-vlan vlan-id 300 set protocols dot1x authenticator interface all guest-vlan guest-vlan Step-by-Step Procedure To configure a guest VLAN that includes 802.1X authentication on a J-EX Series switch: 1. Configure the VLAN ID for the guest VLAN: [edit] user@switch# set vlans guest-vlan vlan-id 300 2. Configure the guest VLAN under dot1x protocols: [edit] user@switch# set protocols dot1x authenticator interface all guest-vlan guest-vlan Results Check the results of the configuration: user@switch> show configuration protocols { dot1x { authenticator { interface { all { guest-vlan { guest-vlan; } } } } } 2279 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } vlans { guest-vlan { vlan-id 300; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That the Guest VLAN is Configured on page 2280 Verifying That the Guest VLAN is Configured Purpose Action Verify that the guest VLAN is created and that an interface has failed authentication and been moved to the guest VLAN. Use the operational mode commands: user@switch> show vlans Name default Tag dynamic 40 guest 30 guest—vlan 300 Interfaces ge-0/0/3.0* None None ge-0/0/1.0* vlan_dyn None user@switch> show dot1x interface ge-0/0/1.0 detail ge-0/0/1.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Enabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: guest-vlan Number of connected supplicants: 1 Supplicant: user1, 00:00:00:00:13:23 Operational state: Authenticated Authentication method: Radius Authenticated VLAN: vo11 Dynamic Filter: match source-dot1q-tag 10 action deny 2280 Chapter 82: Examples: Access Control Configuration Session Reauth interval: 60 seconds Reauthentication due in 50 seconds Meaning The output from the show vlans command shows guest-vlan as the the name of the VLAN and the VLAN ID as 300. The output from the show dot1x interface ge-0/0/1.0 detail command displays the Guest VLAN membership field, indicating that a supplicant at this interface failed 802.1X authentication and was passed through to the guest-vlan. Related Documentation • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch To allow devices to access your LAN through 802.1X-configured interfaces without authentication, you can configure a static MAC bypass list on the J-EX Series switch. The static MAC bypass list, also known as the exclusion list, specifies MAC addresses that are allowed on the switch without a request to an authentication server. You can use static MAC bypass of authentication to allow connection for devices that are not 802.1X-enabled, such as printers. If a host's MAC address is compared and matched against the static MAC address list, the nonresponsive host is authenticated and an interface opened for it. This example describes how to configure static MAC bypass of authentication for two printers: • Requirements on page 2281 • Overview and Topology on page 2282 • Configuration on page 2284 • Verification on page 2285 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The ports on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. Before you configure static MAC authentication, be sure you have: 2281 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. Overview and Topology To permit printers access to the LAN, add them to the static MAC bypass list. The MAC addresses on this list are permitted access without authentication from the RADIUS server. Figure 52 on page 2283 shows the two printers connected to the J-EX4200. 2282 Chapter 82: Examples: Access Control Configuration Figure 52: Topology for Static MAC Authentication Configuration The interfaces shown in Table 291 on page 2284 will be configured for static MAC authentication. 2283 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 291: Components of the Static MAC Authentication Configuration Topology Property Settings Switch hardware J-EX4200, 24 Gigabit Ethernet ports: 8 PoE ports (ge-0/0/0 through ge-0/0/23) VLAN name default Connections to integrated printer/fax/copier machines (no PoE required) ge-0/0/19, MAC address 00:04:0f:fd:ac:fe ge-0/0/20, MAC address 00:04:ae:cd:23:5f The printer with the MAC address 00:04:0f:fd:ac:fe is connected to access interface ge-0/0/19. A second printer with the MAC address 00:04:ae:cd:23:5f is connected to access interface ge-0/0/20. Both printers will be added to the static list and bypass 802.1X authentication. Configuration To configure static MAC authentication, perform these tasks: CLI Quick Configuration To quickly configure static MAC authentication, copy the following commands and paste them into the switch terminal window: [edit] set protocols dot1x authenticator authenticaton-profile-name profile1 set protocols dot1x authenticator static [00:04:0f:fd:ac:fe 00:04:ae:cd:23:5f] set protocols dot1x interface all supplicant multiple Step-by-Step Procedure Configure static MAC authentication: 1. Configure the authentication profile name (access profile name) to use for authentication: [edit protocols] user@switch# set dot1x authenticator authentication-profile-name profile1 2. Configure MAC addresses 00:04:0f:fd:ac:fe and 00:04:ae:cd:23:5f as static MAC addresses: [edit protocols] user@switch# set dot1x authenticator static [00:04:0f:fd:ac:fe 00:04:ae:cd:23:5f] 3. Configure the 802.1X authentication method: [edit protocols] user@switch# set dot1x interface all supplicant multiple Results Display the results of the configuration: user@switch> show interfaces { ge-0/0/19 { unit 0 { family ethernet-switching { vlan members default; } } 2284 Chapter 82: Examples: Access Control Configuration } ge-0/0/20 { unit 0 { family ethernet-switching { vlan members default; } } } } protocols { dot1x { authenticator { authentication-profile-name profile1 static [00:04:0f:fd:ac:fe 00:04:ae:cd:23:5f]; interface { all { supplicant multiple; } } } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying Static MAC Bypass of Authentication on page 2285 Verifying Static MAC Bypass of Authentication Purpose Action Verify that the MAC address for both printers is configured and associated with the correct interfaces. Use the operational mode command: user@switch> show dot1x static-mac-address MAC address 00:04:0f:fd:ac:fe 00:04:ae:cd:23:5f Meaning VLAN-Assignment default default Interface ge-0/0/19.0 ge-0/0/20.0 The output field MAC address shows the MAC addresses of the two printers. The output field Interface shows that the MAC address 00:04:0f:fd:ac:fe can connect to the LAN through interface ge-0/0/19.0 and that the MAC address 00:04:ae:cd:23:5f can connect to the LAN through interface ge-0/0/20.0. Related Documentation • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring Static MAC Bypass of Authentication (CLI Procedure) on page 2334 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Understanding MAC RADIUS Authentication on J-EX Series Switches 2285 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch To permit hosts that are not 802.1X-enabled to access the LAN, you can configure MAC RADIUS authentication on the switch interfaces to which the non-802.1X-enabled hosts are connected. When MAC RADIUS authentication is configured, the switch will attempt to authenticate the host with the RADIUS server using the host’s MAC address. This example describes how to configure MAC RADIUS authentication for two non-802.1X-enabled hosts: • Requirements on page 2286 • Overview and Topology on page 2286 • Configuration on page 2288 • Verification on page 2289 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The ports on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • One RADIUS authentication server. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you configure MAC RADIUS authentication, be sure you have: • Configured basic access between the J-EX Series switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Performed basic 802.1X configuration. See “Configuring 802.1X Interface Settings (CLI Procedure)” on page 2331. Overview and Topology IEEE 802.1X Port-Based Network Access Control (PNAC) authenticates and permits devices access to a LAN if the devices can communicate with the switch using the 802.1X protocol (are 802.1X-enabled). To permit non-802.1X-enabled hosts to access the LAN, you can configure MAC RADIUS authentication on the interfaces to which the hosts are connected. When the MAC address of the non-802.1X-enabled host appears on the interface, the switch consults the RADIUS server to check whether it is a permitted MAC address. If the MAC address of the host is configured as permitted on the RADIUS server, the switch opens LAN access to the nonresponsive host. You can configure both MAC RADIUS authentication and 802.1X authentication methods on a single interface configured for multiple supplicants. Additionally, if an interface is 2286 Chapter 82: Examples: Access Control Configuration only connected to a non-802.1X-enabled host, you can enable MAC RADIUS and not enable 802.1X authentication using the mac-radius restrict option, and thus avoid the delay that occurs while the switch determines that the device is does not respond to EAP messages. Figure 53 on page 2287 shows the two printers connected to the switch. Figure 53: Topology for MAC RADIUS Authentication Configuration Table 292 on page 2287 shows the components in the example for MAC RADIUS authentication. Table 292: Components of the MAC RADIUS Authentication Configuration Topology Property Settings Switch hardware J-EX4200 ports (ge-0/0/0 through ge-0/0/23) VLAN name default 2287 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 292: Components of the MAC RADIUS Authentication Configuration Topology (continued) Property Settings Connections to printers (no PoE required) ge-0/0/19, MAC address 00040ffdacfe ge-0/0/20, MAC address 0004aecd235f RADIUS server Connected to the switch on interface ge-0/0/10 The printer with the MAC address 00040ffdacfe is connected to access interface ge-0/0/19. A second printer with the MAC address 0004aecd235f is connected to access interface ge-0/0/20. In this example, both interfaces are configured for MAC RADIUS authentication on the switch, and the MAC addresses (without colons) of both printers are configured on the RADIUS server. Interface ge-0/0/20 is configured to eliminate the normal delay while the switch attempts 802.1X authentication; MAC RADIUS authentication is enabled and 802.1X authentication is disabled using the mac-radius restrict option. Configuration To configure MAC RADIUS authentication on the switch, perform these tasks: CLI Quick Configuration To quickly configure MAC RADIUS authentication, copy the following commands and paste them into the switch terminal window: [edit] set protocols dot1x authenticator interface ge-0/0/19 mac-radius set protocols dot1x authenticator interface ge-0/0/20 mac-radius restrict NOTE: You must also configure the two MAC addresses as usernames and passwords on the RADIUS server, as is done in Step 2 of the step-by-step procedure. Step-by-Step Procedure Configure MAC RADIUS authentication on the switch and on the RADIUS server: 1. On the switch, configure the interfaces to which the printers are attached for MAC RADIUS authentication, and configure interface ge-0/0/20, so that only MAC RADIUS authentication is used: [edit] user@switch# set protocols dot1x authenticator interface ge-0/0/19 mac-radius user@switch# set protocols dot1x authenticator interface ge-0/0/20 mac-radius restrict 2. On the RADIUS server, configure the MAC addresses 00040ffdacfe and 0004aecd235f as usernames and passwords: [root@freeradius]# edit /etc/raddb vi users 00040ffdacfe Auth-type:=EAP, User-Password = "00040ffdacfe" 0004aecd235f Auth-type:=EAP, User-Password = "0004aecd235f" Results 2288 Display the results of the configuration on the switch: Chapter 82: Examples: Access Control Configuration user@switch> show configuration protocols { dot1x { authenticator { authentication-profile-name profile52; interface { ge-0/0/19.0 { mac-radius; } ge-0/0/20.0 { mac-radius { restrict; } } } } } } Verification Verify that the supplicants are authenticated: • Verifying That the Supplicants Are Authenticated on page 2289 Verifying That the Supplicants Are Authenticated Purpose Action After supplicants are configured for MAC RADIUS authentication on the switch and on the RADIUS server, verify that they are authenticated and display the method of authentication: Display information about 802.1X-configured interfaces ge-0/0/19 and ge-0/0/20: user@switch> show dot1x interface ge-0/0/19.0 detail ge-0/0/19.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Enabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 1 Supplicant: user101, 00:04:0f:fd:ac:fe Operational state: Authenticated Authentication method: Radius Authenticated VLAN: vo11 Dynamic Filter: match source-dot1q-tag 10 action deny 2289 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Session Reauth interval: 60 seconds Reauthentication due in 50 seconds user@switch> show dot1x interface ge-0/0/20.0 detail ge-0/0/20.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Enabled Mac Radius Restrict: Enabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 1 Supplicant: user102, 00:04:ae:cd:23:5f Operational state: Authenticated Authentcation method: Radius Authenticated VLAN: vo11 Dynamic Filter: match source-dot1q-tag 10 action deny Session Reauth interval: 60 seconds Reauthentication due in 50 seconds Meaning Related Documentation The sample output from the show dot1x interface detail command displays the MAC address of the connected host in the Supplicant field. On interface ge-0/0/19, the MAC address is 00:04:0f:fd:ac:fe, which is the MAC address of the first printer configured for MAC RADIUS authentication. The Authentication method field displays the authentication method as MAC Radius. On interface ge-0/0/20, the MAC address is 00:04:ae:cd:23:5f, which is the MAC address of the second printer configured for MAC RADIUS authentication. The Authentication method field displays the authentication method as MAC Radius. • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Understanding MAC RADIUS Authentication on J-EX Series Switches Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch 802.1x Port-Based Network Access Control (PNAC) authentication on J-EX Series switches provides three types of authentication to meet the access needs of your enterprise LAN: 2290 • Authenticate the first host (supplicant) on an authenticator port, and allow all others also connecting to have access. • Authenticate only one supplicant on an authenticator port at one time. Chapter 82: Examples: Access Control Configuration • Authenticate multiple supplicants on an authenticator port. Multiple supplicant mode is used in VoIP configurations. This example configures a J-EX4200 switch to use IEEE 802.1X to authenticate supplicants that use three different administrative modes: • Requirements on page 2291 • Overview and Topology on page 2291 • Configuration of 802.1X to Support Multiple Supplicant Modes on page 2293 • Verification on page 2294 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The ports on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • One RADIUS authentication server that supports 802.1X. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you configure the ports for 802.1X authentication, be sure you have: • Installed your J-EX Series switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Configured users on the authentication server. Overview and Topology As shown in Figure 54 on page 2292, the topology contains a J-EX4200 access switch connected to the authentication server on port ge-0/0/10. Interfaces ge-0/0/8, ge-0/0/9, and ge-0/0/11 will be configured for three different administrative modes. 2291 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 54: Topology for Configuring Supplicant Modes 2292 Chapter 82: Examples: Access Control Configuration Table 293: Components of the Supplicant Mode Configuration Topology Property Settings Switch hardware J-EX4200 switch, 24 Gigabit Ethernet ports: 8 PoE ports (ge-0/0/0 through ge-0/0/7) and 16 non-PoE ports (ge-0/0/8 through ge-0/0/23) Connections to Avaya phones—with integrated hub, to connect phone and desktop PC to a single port; (requires PoE) ge-0/0/8, ge-0/0/9, and ge-0/0/11 To configure the administrative modes to support supplicants in different areas of the Enterprise network: • Configure access port ge-0/0/8 for single supplicant mode authentication. • Configure access port ge-0/0/9 for single secure supplicant mode authentication. • Configure access port ge-0/0/11 for multiple supplicant mode authentication. Single supplicant mode authenticates only the first supplicant that connects to an authenticator port. All other supplicants connecting to the authenticator port after the first supplicant has connected successfully, whether they are 802.1X-enabled or not, are permitted free access to the port without further authentication. If the first authenticated supplicant logs out, all other supplicants are locked out until a supplicant authenticates. Single-secure supplicant mode authenticates only one supplicant to connect to an authenticator port. No other supplicant can connect to the authenticator port until the first supplicant logs out. Multiple supplicant mode authenticates multiple supplicants individually on one authenticator port. If you configure a maximum number of devices that can be connected to a port through port security, the lesser of the configured values is used to determine the maximum number of supplicants allowed per port. Configuration of 802.1X to Support Multiple Supplicant Modes To configure 802.1X authentication to support multiple supplicants, perform these tasks: CLI Quick Configuration To quickly configure the ports with different 802.1X authentication modes, copy the following commands and paste them into the switch terminal window: [edit] set protocols dot1x authenticator interface ge-0/0/8 supplicant single set protocols dot1x authenticator interface ge-0/0/9 supplicant single-secure set protocols dot1x authenticator interface ge-0/0/11 supplicant multiple Step-by-Step Procedure Configure the administrative mode on the interfaces: 1. Configure the supplicant mode as single on interface ge-0/0/8: [edit protocols] user@switch# set dot1x authenticator interface ge-0/0/8 supplicant single 2. Configure the supplicant mode as single secure on interface ge-0/0/9: 2293 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit protocols] user@switch# set dot1x authenticator interface ge-0/0/9 supplicant single-secure 3. Configure multiple supplicant mode on interface ge-0/0/11: [edit protocols] user@switch# set dot1x authenticator interface ge-0/0/11 supplicant multiple Results Check the results of the configuration: [edit] user@access-switch> show configuration protocols { dot1x { authenticator { interface { ge-0/0/8.0 { supplicant single; ) ge-0/0/9.0 { supplicant single-secure; ) ge-0/0/11.0 { supplicant multiple; ) } } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying the 802.1X Configuration on page 2294 Verifying the 802.1X Configuration Purpose Action Verify the 802.1X configuration on interfaces ge-0/0/8, ge-0/0/9, and ge-0/0/5. Verify the 802.1X configuration with the operational mode command show dot1x interface: user@switch> show dot1x interface ge-0/0/8.0 detail ge-0/0/8.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Disabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds 2294 Chapter 82: Examples: Access Control Configuration Maximum EAPOL requests: 2 Guest VLAN member: user@switch> show dot1x interface ge-0/0/9.0 detail ge-0/0/9.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single-Secure Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Disabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 0 user@switch> show dot1x interface ge-0/0/11.0 detail ge-0/0/11.0 Role: Authenticator Administrative state: Auto Supplicant mode: Multiple Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Disabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 0 Meaning Related Documentation The Supplicant mode output field displays the configured administrative mode for each interface. Interface ge-0/0/8.0 displays Single supplicant mode. Interface ge-0/0/9.0 displays Single Secure supplicant mode. Interface ge-0/0/11.0 displays Multiple supplicant mode. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Understanding Authentication onJ-EX Series Switches on page 2248 2295 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Example: Applying a Firewall Filter to 802.1X-Authenticated Supplicants Using RADIUS Server Attributes on a J-EX Series Switch You can use RADIUS server attributes and a port-based firewall filter to centrally apply terms to multiple supplicants connected to a J-EX Series switch in your enterprise. Terms are applied following a supplicant’s successful authentication through 802.1X. J-EX Series switches support port-based firewall filters. Port firewall filters are configured on a single J-EX Series switch, but in order for them to operate throughout an enterprise, they have to be configured on multiple switches. To reduce the need to configure the same port firewall filter on multiple switches, you can instead apply the filter centrally on the RADIUS server using RADIUS server attributes. The following example uses FreeRADIUS to apply a port firewall filter on a RADIUS server. For specifics on configuring your server, consult the documentation that was included with your RADIUS server. This example describes how to configure a port firewall filter with terms, create counters to count packets for the supplicants, apply the filter to user profiles on the RADIUS server, and display the counters to verify the configuration: • Requirements on page 2296 • Overview and Topology on page 2297 • Configuring the Port Firewall Filter and Counters on page 2299 • Applying the Port Firewall Filter to the Supplicant User Profiles on the RADIUS Server on page 2300 • Verification on page 2301 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The ports on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • One RADIUS authentication server. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you connect the server to the switch, be sure you have: 2296 • Set up a connection between the switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Configured 802.1X authentication on the switch, with the authentication mode for interface ge-0/0/2 set to multiple. See “Configuring 802.1X Interface Settings (CLI Procedure)” on page 2331 and “Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch” on page 2290. Chapter 82: Examples: Access Control Configuration • Configured users on the RADIUS authentication server (in this example, the user profiles for Supplicant 1 and Supplicant 2 in the topology are modified on the RADIUS server). Overview and Topology When the 802.1X configuration on an interface is set to multiple supplicant mode, you can apply a single port firewall filter configured through the Junos OS CLI on the J-EX Series switch to any number of users (supplicants) on one interface by adding the filter centrally to the RADIUS server. Only a single filter can be applied to an interface; however, the filter can contain multiple terms for separate supplicants. For more information about firewall filters, see “Firewall Filters for J-EX Series Switches Overview” on page 2721. RADIUS server attributes are applied to supplicants after the supplicants are successfully authenticated using 802.1X. To authenticate the supplicants, the switch forwards a supplicant’s credentials to the RADIUS server. The RADIUS server matches the credentials forwarded by the switch against preconfigured information about the supplicant located in the supplicant’s user profile on the RADIUS server. If a match is made, the RADIUS server instructs the switch to open an interface to the supplicant. Traffic then flows from and to the supplicant on the LAN. Further instructions configured in the port firewall filter and added to the supplicant’s user profile using a RADIUS server attribute further define the access that the supplicant is granted. Filtering terms configured in the port firewall filter are applied to the supplicant after 802.1X authentication is complete. Figure 55 on page 2298 shows the topology used for this example. The RADIUS server is connected to the J-EX4200 switch on access port ge-0/0/10. Two supplicants are accessing the LAN on interface ge-0/0/2. Supplicant 1 has a MAC address of 00:50:8b:6f:60:3a. Supplicant 2 has a MAC address of 00:50:8b:6f:60:3b. 2297 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 55: Topology for Firewall Filter and RADIUS Server Attributes Configuration Table 294 on page 2298 describes the components in this topology. Table 294: Components of the Firewall Filter and RADIUS Server Attributes Topology Property Settings Switch hardware J-EX4200 access switch, 24 Gigabit Ethernet ports, 8 PoE ports. One RADIUS server Backend database with an address of 10.0.0.100 connected to the switch at port ge-0/0/10. 802.1X supplicants connected to the switch on interface ge-0/0/2 • Supplicant 1 has MAC address 00:50:8b:6f:60:3a. • Supplicant 2 has MAC address 00:50:8b:6f:60:3b. 2298 Chapter 82: Examples: Access Control Configuration Table 294: Components of the Firewall Filter and RADIUS Server Attributes Topology (continued) Property Settings Port firewall filter to be applied on the RADIUS server filter1 Counters counter1 counts packets from Supplicant 1, and counter2 counts packets from Supplicant 2. User profiles on the RADIUS server • Supplicant 1 has the user profile supplicant1. • Supplicant 2 has the user profile supplicant2. In this example, you configure a port firewall filter named filter1. The filter contains terms that will be applied to the supplicants based on the MAC addresses of the supplicants. When you configure the filter, you also configure the counters called counter1 and counter2. Packets from each supplicant will be counted, helping you verify that the configuration is working. Then, you check to see that the RADIUS server attribute is available on the RADIUS server and apply the filter to the user profiles of each supplicant on the RADIUS server. Finally, you verify the configuration by displaying output for the two counters. NOTE: For more information about authentication, authorization, and accounting (AAA) services, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Configuring the Port Firewall Filter and Counters Configure a port firewall filter and counters: CLI Quick Configuration To quickly configure a port firewall filter with terms for Supplicant 1 and Supplicant 2 and create parallel counters for each supplicant, copy the following commands and paste them into the switch terminal window: [edit] set firewall family ethernet-switching filter filter1 term supplicant1 from source-mac-address 00:50:8b:6f:60:3a set firewall family ethernet-switching filter filter1 term supplicant2 from source-mac-address 00:50:8b:6f:60:3b set firewall family ethernet-switching filter filter1 term supplicant1 then count counter1 set firewall family ethernet-switching filter filter1 term supplicant2 then count counter2 Step-by-Step Procedure To configure a port firewall filter and counters on the switch: 1. Configure a port firewall filter (here, filter1) with terms for each supplicant based upon the MAC address of each supplicant: [edit firewall family ethernet-switching] user@switch# set filter filter1 term supplicant1 from source-mac-address 00:50:8b:6f:60:3a user@switch# set filter filter1 term supplicant2 from source-mac-address 00:50:8b:6f:60:3b 2. Create two counters that will count packets for each supplicant: 2299 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit firewall family ethernet-switching] user@switch# set filter filter1 term supplicant1 then count counter1 user@switch# set filter filter1 term supplicant2 then count counter2 user@switch# set filter filter1 term supplicant2 then count counter2 Results Display the results of the configuration: user@switch> show configuration firewall { family ethernet-switching { filter filter1 { term supplicant1 { from { source-mac-address { 00:50:8b:6f:60:3a; } } then count counter1; then policer p1; } term supplicant2 { from { source-mac-address { 00:50:8b:6f:60:3b; } } then count counter2; } } } } policer p1 { if-exceeding { bandwidth-limit 1m; burst-size-limit 1k; } then discard; } Applying the Port Firewall Filter to the Supplicant User Profiles on the RADIUS Server Verify that the RADIUS server attribute needed to apply a filter on the RADIUS server is on the server and apply the port firewall filter to each supplicant’s user profile on the RADIUS server: Step-by-Step Procedure To verify that the RADIUS server attribute Filter-ID is on the RADIUS server and to apply the filter to the user profiles: 1. Display the dictionary dictionary.rfc2865 on the RADIUS server, and verify that the attribute Filter-ID is in the dictionary: [root@freeradius]# cd usr/share/freeradius/dictionary.rfc2865 2. 2300 Close the dictionary file. Chapter 82: Examples: Access Control Configuration 3. Display the local user profiles of the supplicants to which you want to apply the filter (here, the user profiles are called supplicant1 and supplicant2): [root@freeradius]# cat /usr/local/etc/raddb/users The output shows: supplicant1 Auth-Type := EAP, User-Password == "supplicant1" Tunnel-Type = VLAN, Tunnel-Medium-Type = IEEE-802, Tunnel-Private-Group-Id = "1005" supplicant2 Auth-Type := EAP, User-Password == "supplicant2" Tunnel-Type = VLAN, Tunnel-Medium-Type = IEEE-802, Tunnel-Private-Group-Id = "1005" 4. Apply the filter to both user profiles by adding the line Filter-Id = “filter1” to each profile, and then close the file: [root@freeradius]# cat /usr/local/etc/raddb/users After you paste the line into the files, the files look like this: supplicant1 Auth-Type := EAP, User-Password == "supplicant1" Tunnel-Type = VLAN, Tunnel-Medium-Type = IEEE-802, Tunnel-Private-Group-Id = "1005", Filter-Id = "filter1" supplicant2 Auth-Type := EAP, User-Password == "supplicant2" Tunnel-Type = VLAN, Tunnel-Medium-Type = IEEE-802, Tunnel-Private-Group-Id = "1005", Filter-Id = "filter1" Verification Verify that the filter has been applied to the supplicants: • Verifying That the Filter Has Been Applied to the Supplicants on page 2301 Verifying That the Filter Has Been Applied to the Supplicants Purpose Action After supplicants are authenticated, verify that the filter configured on the switch and added to each supplicant’s user profile on the RADIUS server has been applied: Display information about firewall filter filter1: user@switch> show firewall filter filter1 Filter: filter1 Counters: Name counter1 counter2 Bytes 128 64 Packets 2 1 2301 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning Related Documentation The output of the command show firewall filter filter1 displays counter1 and counter2. Packets from Supplicant 1 are counted using counter1, and packets from Supplicant 2 are counted using counter2. The output from the command displays packets incrementing for both counters. The filter has been applied to both supplicants. • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Understanding Authentication onJ-EX Series Switches on page 2248 • Understanding 802.1X and VSAs on J-EX Series Switches on page 2266 Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch You can configure voice over IP (VoIP) on a J-EX Series switch to support IP telephones. The Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) protocol forwards VoIP parameters from the switch to the phone. You also configure 802.1X authentication to allow the telephone access to the LAN. Authentication is done through a backend RADIUS server. This example describes how to configure VoIP on a J-EX Series switch to support an Avaya IP phone, as well as the LLDP-MED protocol and 802.1X authentication: • Requirements on page 2302 • Overview and Topology on page 2303 • Configuration on page 2305 • Verification on page 2307 Requirements This example uses the following hardware and software components: • One J-EX Series switch acting as an authenticator port access entity (PAE). The interfaces on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • An Avaya 9620 IP telephone that supports LLDP-MED and 802.1X Before you configure VoIP, be sure you have: 2302 • Installed your J-EX Series switch. See Installing and Connecting a J-EX4200 Switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. Chapter 82: Examples: Access Control Configuration • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Configured the RADIUS server for 802.1X authentication and set up the access profile. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • (Optional) Configured interface ge-0/0/2 for Power over Ethernet (PoE). The PoE configuration is not necessary if the VoIP supplicant is using a power adapter. For information about configuring PoE, see “Configuring PoE (CLI Procedure)” on page 3021. NOTE: If the IP address isn't configured on the Avaya IP phone, the phone exchanges LLDP-MED information to get the VLAN ID for the voice VLAN. You must configure the voip statement on the interface to designate the interface as a VoIP interface and allow the switch to forward the VLAN name and VLAN ID for the voice VLAN to the IP telephone. The IP telephone then uses the voice VLAN (that is, it references the voice VLAN’s ID) to send a DHCP discover request and exchange information with the DHCP server (voice gateway). Overview and Topology Instead of using a regular telephone, you connect an IP telephone directly to the switch. An IP phone has all the hardware and software needed to handle VoIP. You also can power an IP telephone by connecting it to one of the Power over Ethernet (PoE) interfaces on the switch. In this example, the access interface ge-0/0/2 on the J-EX4200 switch is connected to an Avaya 9620 IP telephone. Avaya phones have a built-in bridge that allows you to connect a desktop PC to the phone, so the desktop and phone in a single office require only one interface on the switch. The J-EX Series switch is connected to a RADIUS server on interface ge-0/0/10 (see Figure 56 on page 2304). 2303 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 56: VoIP Topology In this example, you configure VoIP parameters and specify the forwarding class assured-forward for voice traffic to provide the highest quality of service. Table 295 on page 2304 describes the components used in this VoIP configuration example. Table 295: Components of the VoIP Configuration Topology Property Settings Switch hardware J-EX4200 switch 2304 Chapter 82: Examples: Access Control Configuration Table 295: Components of the VoIP Configuration Topology (continued) Property Settings VLAN names data-vlan voice-vlan Connection to Avaya phone—with integrated hub, to connect phone and desktop PC to a single interface (requires PoE) ge-0/0/2 One RADIUS server Provides backend database connected to the switch through interface ge-0/0/10. As well as configuring a VoIP for interface ge-0/0/2, you configure: • 802.1X authentication. Authentication is set to multiple supplicant to support more than one supplicant's access to the LAN through interface ge-0/0/2. • LLDP-MED protocol information. The switch uses LLDP-MED to forward VoIP parameters to the phone. Using LLDP-MED ensures that voice traffic gets tagged and prioritized with the correct values at the source itself. For example, 802.1p class of service and 802.1Q tag information can be sent to the IP telephone. NOTE: A PoE configuration is not necessary if an IP telephone is using a power adapter. Configuration To configure VoIP, LLDP-MED, and 802.1X authentication: CLI Quick Configuration To quickly configure VoIP, LLDP-MED, and 802.1X, copy the following commands and paste them into the switch terminal window: [edit] set vlans data-vlan vlan-id 77 set vlans voice-vlan vlan-id 99 set vlans data-vlan interface ge-0/0/2.0 set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members data-vlan set interfaces ge-0/0/2 unit 0 family ethernet-switching port-mode access set ethernet-switching-options voip interface ge-0/0/2.0 vlan voice-vlan set ethernet-switching-options voip interface ge-0/0/2.0 forwarding-class assured-forwarding set protocols lldp-med interface ge-0/0/2.0 set protocols dot1x authenticator interface ge-0/0/2.0 supplicant multiple Step-by-Step Procedure To configure VoIP with LLDP-MED and 802.1X: 1. Configure the VLANs for voice and data: [edit vlans] user@switch# set data-vlan vlan-id 77 user@switch# set voice-vlan vlan-id 99 2. Associate the VLAN data-vlan with the interface: [edit vlans] user@switch# set data-vlan interface ge-0/0/2.0 2305 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3. Configure the interface as an access interface, configure support for Ethernet switching, and add the data-vlan VLAN: [edit interfaces] user@switch# set ge-0/0/2 unit 0 family ethernet-switching vlan members data-vlan user@switch# set ge-0/0/2 unit 0 family ethernet-switching port-mode access 4. Configure VoIP on the interface and specify the assured-forwarding forwarding class to provide the most dependable class of service: [edit ethernet—switching—options] user@switch# set voip interface ge-0/0/2.0 vlan voice-vlan user@switch# set voip interface ge-0/0/2.0 forwarding-class assured-forwarding 5. Configure LLDP-MED protocol support: [edit protocols] user@switch# set lldp-med interface ge-0/0/2.0 6. To authenticate an IP phone and a PC connected to the IP phone on the interface, configure 802.1X authentication support and specify multiple supplicant mode: NOTE: If you do not want to authenticate any device, skip the 802.1X configuration on this interface. [edit protocols] user@switch# set dot1x authenticator interface ge-0/0/2.0 supplicant multiple Results Display the results of the configuration: [edit] user@switch# show configuration interfaces { ge-0/0/2 { unit 0 { family ethernet-switching { port-mode access; vlan { members data-vlan; } } } } } protocols { lldp-med { interface ge-0/0/2.0; } dot1x { authenticator { interface { ge-0/0/2.0 { supplicant multiple; } } 2306 Chapter 82: Examples: Access Control Configuration } } } vlans { data-vlan { vlan-id 77; interface { ge-0/0/2.0; } } voice-vlan { vlan-id 99; } } ethernet-switching options { voip { interface ge-0/0/2.0 { vlan voice-vlan; forwarding-class assured-forwarding; } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying LLDP-MED Configuration on page 2307 • Verifying 802.1X Authentication for IP Phone and Desktop PC on page 2308 • Verifying the VLAN Association with the Interface on page 2309 Verifying LLDP-MED Configuration Purpose Action Verify that LLDP-MED is enabled on the interface. user@switch> show lldp detail LLDP : Enabled Advertisement interval : 30 Second(s) Transmit delay : 2 Second(s) Hold timer : 2 Second(s) Config Trap Interval : 300 Second(s) Connection Hold timer : 60 Second(s) LLDP MED MED fast start count Interface all ge-0/0/2.0 Interface ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/3.0 LLDP Enabled VLAN-id 0 0 0 99 0 : Enabled : 3 Packet(s) LLDP-MED Enabled Neighbor count 0 0 VLAN-name default employee-vlan data-vlan voice-vlan employee-vlan 2307 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/8.0 ge-0/0/10.0 ge-0/0/11.0 ge-0/0/23.0 0 0 20 0 employee-vlan default employee-vlan default LLDP basic TLVs supported: Chassis identifier, Port identifier, Port description, System name, System description, System capabilities, Management address. LLDP 802 TLVs supported: Power via MDI, Link aggregation, Maximum frame size, Port VLAN tag, Port VLAN name. LLDP MED TLVs supported: LLDP MED capabilities, Network policy, Endpoint location, Extended power Via MDI. Meaning The show lldp detail output shows that both LLDP and LLDP-MED are configured on the ge-0/0/2.0 interface. The end of the output shows the list of supported LLDP basic TLVs, 802.3 TLVs, and LLDP-MED TLVs that are supported. Verifying 802.1X Authentication for IP Phone and Desktop PC Purpose Action Meaning 2308 Display the 802.1X configuration to confirm that the VoIP interface has access to the LAN. user@switch> show dot1x interface ge/0/0/2.0 detail ge-0/0/2.0 Role: Authenticator Administrative state: Auto Supplicant mode: Multiple Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Disabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 1 Supplicant: user101, 00:04:0f:fd:ac:fe Operational state: Authenticated Authentication method: Radius Authenticated VLAN: vo11 Dynamic Filter: match source-dot1q-tag 10 action deny Session Reauth interval: 60 seconds Reauthentication due in 50 seconds The field Role shows that the ge-0/0/2.0 interface is in the authenticator state. The Supplicant field shows that the interface is configured in multiple supplicant mode, permitting multiple supplicants to be authenticated on this interface. The MAC addresses of the supplicants currently connected are displayed at the bottom of the output. Chapter 82: Examples: Access Control Configuration Verifying the VLAN Association with the Interface Purpose Action Display the interface state and VLAN membership. user@switch> show ethernet-switching interfaces Ethernet-switching table: 0 entries, 0 learned user@switch> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/0.0 down default unblocked ge-0/0/1.0 down employee-vlan unblocked ge-0/0/5.0 down employee-vlan unblocked ge-0/0/3.0 down employee-vlan unblocked ge-0/0/8.0 down employee-vlan unblocked ge-0/0/10.0 down default unblocked ge-0/0/11.0 down employee-vlan unblocked ge-0/0/23.0 down default unblocked ge-0/0/2.0 up voice-vlan unblocked data-vlan unblocked Meaning Related Documentation The field VLAN members shows that the ge-0/0/2.0 interface supports both the data-vlan VLAN and voice-vlan VLAN. The State field shows that the interface is up. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 • Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Configuring LLDP-MED (CLI Procedure) on page 2346 Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication You can configure voice over IP (VoIP) on a J-EX Series switch to support IP telephones. To configure VoIP on a J-EX Series switch to support an IP phone that does not support 802.1X authentication, you must either add the MAC address of the phone to the static MAC bypass list or enable MAC RADIUS authentication on the switch. This example describes how to configure VoIP on a J-EX Series switch without 802.1X authentication using static MAC bypass of authentication: • Requirements on page 2310 • Overview on page 2310 • Configuration on page 2310 • Verification on page 2313 2309 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example uses the following hardware and software components: • An IP telephone Before you configure VoIP, be sure you have: • Installed your J-EX Series switch. See Installing and Connecting a J-EX4200 Switch. • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163. • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Configured the RADIUS server for 802.1X authentication and set up the access profile. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • (Optional) Configured interface ge-0/0/2 for Power over Ethernet (PoE). The PoE configuration is not necessary if the VoIP supplicant is using a power adapter. For information about configuring PoE, see “Configuring PoE (CLI Procedure)” on page 3021. NOTE: If the IP address isn't configured on the Avaya IP phone, the phone exchanges LLDP-MED information to get the VLAN ID for the voice VLAN. You must configure the voip statement on the interface to designate the interface as a VoIP interface and allow the switch to forward the VLAN name and VLAN ID for the voice VLAN to the IP telephone. The IP telephone then uses the voice VLAN (that is, it references the voice VLAN’s ID) to send a DHCP discover request and exchange information with the DHCP server (voice gateway). Overview Instead of using a regular telephone, you connect an IP telephone directly to the switch. An IP phone has all the hardware and software needed to handle VoIP. You also can power an IP telephone by connecting it to one of the Power over Ethernet (PoE) interfaces on the switch. In this example, the access interface ge-0/0/2 on the J-EX4200 switch is connected to a non-802.1X IP phone. To configure VoIP on a J-EX Series switch to support an IP phone that does not support 802.1X authentication, add the MAC address of the phone as a static entry in the authenticator database and set the supplicant mode to multiple. Configuration To configure VoIP without 802.1X authentication: 2310 Chapter 82: Examples: Access Control Configuration CLI Quick Configuration To quickly configure VoIP, copy the following commands and paste them into the switch terminal window: [edit] set vlans data-vlan vlan-id 77 set vlans voice-vlan vlan-id 99 set vlans data-vlan interface ge-0/0/2.0 set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members data-vlan set interfaces ge-0/0/2 unit 0 family ethernet-switching port-mode access set ethernet-switching-options voip interface ge-0/0/2.0 vlan voice-vlan set ethernet-switching-options voip interface ge-0/0/2.0 forwarding-class assured-forwarding set protocols lldp-med interface ge-0/0/2.0 set protocols dot1x authenticator authentication-profile-name auth-profile set protocols dot1x authenticator static 00:04:f2:11:aa:a7 set protocols dot1x authenticator interface ge-0/0/2.0 supplicant multiple Step-by-Step Procedure To configure VoIP without 802.1X: 1. Configure the VLANs for voice and data: [edit vlans] user@switch# set data-vlan vlan-id 77 user@switch# set voice-vlan vlan-id 99 2. Associate the VLAN data-vlan with the interface: [edit vlans] user@switch# set data-vlan interface ge-0/0/2.0 3. Configure the interface as an access interface, configure support for Ethernet switching, and add the data-vlan VLAN: [edit interfaces] user@switch# set ge-0/0/2 unit 0 family ethernet-switching vlan members data-vlan user@switch# set ge-0/0/2 unit 0 family ethernet-switching port-mode access 4. Configure VoIP on the interface and specify the assured-forwarding forwarding class to provide the most dependable class of service: [edit ethernet-switching-options] user@switch# set voip interface ge-0/0/2.0 vlan voice-vlan user@switch# set voip interface ge-0/0/2.0 forwarding-class assured-forwarding 5. Configure LLDP-MED protocol support: [edit protocols] user@switch# set lldp-med interface ge-0/0/2.0 6. Set the authentication profile (see “Configuring 802.1X Interface Settings (CLI Procedure)” on page 2331 and “Configuring 802.1X RADIUS Accounting (CLI Procedure)” on page 2339): [edit protocols] set dot1x authenticator authentication-profile-name auth-profile 7. Add the MAC address of the phone to the static MAC bypass list: [edit protocols] set dot1x authenticator static 00:04:f2:11:aa:a7 8. Set the supplicant mode to multiple: 2311 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit protocols] set dot1x authenticator interface ge-0/0/2.0 supplicant multiple Results Display the results of the configuration: [edit] user@switch# show configuration interfaces { ge-0/0/2 { unit 0 { family ethernet-switching { port-mode access; vlan { members data-vlan; } } } } } protocols { lldp-med { interface ge-0/0/2.0; } dot1x { authenticator { authentication-profile-name auth-profile; static { 00:04:f2:11:aa:a7; } } interface { ge-0/0/2.0 { supplicant multiple; } } } } vlans { data-vlan { vlan-id 77; interface { ge-0/0/2.0; } } voice-vlan { vlan-id 99; } } ethernet-switching options { voip { interface ge-0/0/2.0 { vlan voice-vlan; forwarding-class assured-forwarding; } } 2312 Chapter 82: Examples: Access Control Configuration } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying LLDP-MED Configuration on page 2313 • Verifying Authentication for the Desktop PC on page 2314 • Verifying the VLAN Association with the Interface on page 2314 Verifying LLDP-MED Configuration Purpose Action Verify that LLDP-MED is enabled on the interface. user@switch> show lldp detail LLDP : Enabled Advertisement interval : 30 Second(s) Transmit delay : 2 Second(s) Hold timer : 2 Second(s) Config Trap Interval : 300 Second(s) Connection Hold timer : 60 Second(s) LLDP MED MED fast start count Interface all ge-0/0/2.0 Interface ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/8.0 ge-0/0/10.0 ge-0/0/11.0 ge-0/0/23.0 LLDP Enabled VLAN-id 0 0 0 99 0 0 0 20 0 : Enabled : 3 Packet(s) LLDP-MED Enabled Neighbor count 0 0 VLAN-name default employee-vlan data-vlan voice-vlan employee-vlan employee-vlan default employee-vlan default LLDP basic TLVs supported: Chassis identifier, Port identifier, Port description, System name, System description, System capabilities, Management address. LLDP 802 TLVs supported: Power via MDI, Link aggregation, Maximum frame size, Port VLAN tag, Port VLAN name. LLDP MED TLVs supported: LLDP MED capabilities, Network policy, Endpoint location, Extended power Via MDI. Meaning The show lldp detail output shows that both LLDP and LLDP-MED are configured on the ge-0/0/2.0 interface. The end of the output shows the list of supported LLDP basic TLVs, 802.3 TLVs, and LLDP-MED TLVs that are supported. 2313 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verifying Authentication for the Desktop PC Purpose Action Meaning Display the 802.1X configuration for the desktop PC connected to the VoIP interface through the IP phone. user@switch> show dot1x interface ge/0/0/2.0 detail ge-0/0/2.0 Role: Authenticator Administrative state: Auto Supplicant mode: Multiple Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Disabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 1 Supplicant: user101, 00:04:0f:fd:ac:fe Operational state: Authenticated Authentication method: Radius Authenticated VLAN: vo11 Dynamic Filter: match source-dot1q-tag 10 action deny Session Reauth interval: 60 seconds Reauthentication due in 50 seconds The field Role shows that the ge-0/0/2.0 interface is in the authenticator state. The Supplicant field shows that the interface is configured in multiple supplicant mode, permitting multiple supplicants to be authenticated on this interface. The MAC addresses of the supplicants currently connected are displayed at the bottom of the output. Verifying the VLAN Association with the Interface Purpose Action Display the interface state and VLAN membership. user@switch> show ethernet-switching interfaces Ethernet-switching table: 0 entries, 0 learned user@switch> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/0.0 down default unblocked ge-0/0/1.0 down employee-vlan unblocked ge-0/0/5.0 down employee-vlan unblocked ge-0/0/3.0 down employee-vlan unblocked ge-0/0/8.0 down employee-vlan unblocked ge-0/0/10.0 down default unblocked ge-0/0/11.0 down employee-vlan unblocked ge-0/0/23.0 down default unblocked ge-0/0/2.0 up voice-vlan unblocked data-vlan unblocked 2314 Chapter 82: Examples: Access Control Configuration Meaning Related Documentation The field VLAN members shows that the ge-0/0/2.0 interface supports both the data-vlan VLAN and voice-vlan VLAN. The State field shows that the interface is up. • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support You can configure voice over IP (VoIP) on a J-EX Series switch to support IP telephones. The Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) protocol is sometimes used with IP phones to forward VoIP parameters from the switch to the phone. Not all IP phones support LLDP-MED, however. This example describes how to configure VoIP on a J-EX Series switch without LLDP-MED and without 802.1X: • Requirements on page 2315 • Overview on page 2316 • Configuration on page 2316 • Verification on page 2317 Requirements This example uses the following hardware and software components: • One J-EX4200 switch acting as an authenticator port access entity (PAE). The interfaces on the authenticator PAE form a control gate that blocks all traffic to and from supplicants until they are authenticated. • A IP phone that does not support LLDP-MED. Before you configure VoIP, be sure you have: • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Configured the IP phone as a member of the voice VLAN. • (Optional) Configured interface ge-0/0/2 for Power over Ethernet (PoE). The PoE configuration is not necessary if the VoIP supplicant is using a power adapter. See “Configuring PoE (CLI Procedure)” on page 3021. 2315 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Overview Instead of using a regular telephone, you connect an IP telephone directly to the switch. An IP phone has all the hardware and software needed to handle VoIP. You also can power an IP telephone by connecting it to one of the Power over Ethernet (PoE) interfaces on the switch. To configure VoIP on a J-EX Series switch to support an IP phone that does not support LLDP-MED, add the port to which you want to connect the IP phone as a member of the voice VLAN and configure the data VLAN as the native VLAN on the J-EX Series switch. This configuration ensures that the voice traffic and data traffic do not affect each other. In this example, the interface ge-0/0/2 on the J-EX4200 switch is connected to a non-LLDP-MED IP phone. NOTE: The implementation of a voice VLAN on an IP telephone is vendor-specific. Consult the documentation that came with your IP telephone for instructions on configuring a voice VLAN. For example, on an Avaya phone, you can ensure that the phone gets the correct VoIP VLAN ID even in the absence of LLDP-MED by enabling DHCP option 176. Configuration To configure VoIP without LLDP-MED or 802.1X authentication: CLI Quick Configuration To quickly configure VoIP, copy the following commands and paste them into the switch terminal window: [edit] set vlans data-vlan vlan-id 77 set vlans voice-vlan vlan-id 99 set vlans data-vlan interface ge-0/0/2.0 set ethernet-switching-options voip interface ge-0/0/2.0 vlan voice-vlan set ethernet-switching-options voip interface ge-0/0/2.0 forwarding-class assured-forwarding set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members voice-vlan set interfaces ge-0/0/2 unit 0 family ethernet-switching native-vlan-id data-vlan Step-by-Step Procedure Configure VoIP: 1. Configure the VLANs for data and voice: [edit vlans] user@switch# set data-vlan vlan-id 77 user@switch# set voice-vlan vlan-id 99 2. Configure the VLAN data-vlan on the interface: [edit vlans] user@switch# set data-vlan interface ge-0/0/2.0 3. Configure VoIP on the interface and specify the assured-forwarding forwarding class to provide the most dependable class of service: [edit ethernet-switching-options] user@switch# set voip interface ge-0/0/2.0 vlan voice-vlan 2316 Chapter 82: Examples: Access Control Configuration user@switch# set voip interface ge-0/0/2.0 forwarding-class assured-forwarding 4. Add the interface as a member of the voice VLAN: [edit interfaces] set ge-0/0/2 unit 0 family ethernet-switching vlan members voice-vlan 5. Configure data-vlan as native to this trunk interface: [edit interfaces] user@switch# set ge-0/0/2 unit 0 family ethernet-switching native-vlan-id data-vlan Results Display the results of the configuration: [edit] user@switch# show configuration interfaces { ge-0/0/2 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members voice-vlan; } native-vlan-id data-vlan; } } } } vlans { data-vlan { vlan-id 77; interface { ge-0/0/2.0; } } voice-vlan { vlan-id 99; } } ethernet-switching options { voip { interface ge-0/0/2.0 { vlan voice-vlan; forwarding-class assured-forwarding; } } } Verification To confirm that the configuration is working properly, perform the following task: • Verifying the VLAN Association With the Interface on page 2318 2317 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verifying the VLAN Association With the Interface Purpose Action Display the interface state and VLAN membership. user@switch> show ethernet-switching interfaces Ethernet-switching table: 0 entries, 0 learned user@switch> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/0.0 down default unblocked ge-0/0/1.0 down employee-vlan unblocked ge-0/0/5.0 down employee-vlan unblocked ge-0/0/3.0 down employee-vlan unblocked ge-0/0/8.0 down employee-vlan unblocked ge-0/0/10.0 down default unblocked ge-0/0/11.0 down employee-vlan unblocked ge-0/0/23.0 down default unblocked ge-0/0/2.0 up voice-vlan unblocked data-vlan unblocked Meaning Related Documentation The field VLAN members shows that the ge-0/0/2.0 interface supports both the data-vlan VLAN and voice-vlan VLAN. The State field shows that the interface is up. • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Example: Applying Firewall Filters to Multiple Supplicants on Interfaces Enabled for 802.1X or MAC RADIUS Authentication On J-EX Series switches, firewall filters that you apply to interfaces enabled for 802.1X or MAC RADIUS authentication are dynamically combined with the per-user policies sent to the switch from the RADIUS server. The switch uses internal logic to dynamically combine the interface firewall filter with the user policies from the RADIUS server and create an individualized policy for each of the multiple users or nonresponsive hosts that are authenticated on the interface. This example describes how dynamic firewall filters are created for multiple supplicants on an 802.1X-enabled interface (the same principles shown in this example apply to interfaces enabled for MAC RADIUS authentication): 2318 • Requirements on page 2319 • Overview and Topology on page 2319 • Configuration on page 2321 • Verification on page 2322 Chapter 82: Examples: Access Control Configuration Requirements This example uses the following hardware and software components: • One J-EX Series switch • One RADIUS authentication server. The authentication server acts as the backend database and contains credential information for hosts (supplicants) that have permission to connect to the network. Before you apply firewall filters to an interface for use with multiple supplicants, be sure you have: • Set up a connection between the switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Configured 802.1X authentication on the switch, with the authentication mode for interface ge-0/0/2 set to multiple. See “Configuring 802.1X Interface Settings (CLI Procedure)” on page 2331 and “Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch” on page 2290. • Configured users on the RADIUS authentication server. Overview and Topology When the 802.1X configuration on an interface is set to multiple supplicant mode, the system dynamically combines interface firewall filter with the user policies sent to the switch from the RADIUS server during authentication and creates separate terms for each user. Because there are separate terms for each user authenticated on the interface, you can, as shown in this example, use counters to view the activities of individual users that are authenticated on the same interface. When a new user (or an nonresponsive host) is authenticated on an interface, the system adds a term to the firewall filter associated with the interface, and the term (policy) for each user is associated with the MAC address of the user. The term for each user is based on the user-specific filters set on the RADIUS server and the filters configured on the interface. For example, as shown in Figure 57 on page 2320, when User1 is authenticated by the J-EX Series switch, the system creates the firewall filter dynamic-filter-example. When User2 is authenticated, another term is added to the firewall filter, and so on. 2319 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 57: Conceptual Model: Dynamic Filter Updated for Each New User This is a conceptual model of the internal process—you cannot access or view the dynamic filter. NOTE: If the firewall filter on the interface is modified after the user (or nonresponsive host) is authenticated, the modifications are not reflected in the dynamic filter unless the user is reauthenticated. In this example, you configure a firewall filter to count the requests made by each endpoint authenticated on interface ge-0/0/2 to the file server, which is located on subnet 192.0.2.16/28. Figure 58 on page 2321 shows the network topology for this example. 2320 Chapter 82: Examples: Access Control Configuration Figure 58: Multiple Supplicants on an 802.1X-Enabled Interface Connecting to a File Server Configuration To configure firewall filters for multiple supplicants on 802.1X-enabled interfaces: • Configuring Firewall Filters on Interfaces with Multiple Supplicants on page 2321 Configuring Firewall Filters on Interfaces with Multiple Supplicants CLI Quick Configuration To quickly configure firewall filters on an interface enabled for multiple supplicants, copy the following commands and paste them into the switch terminal window: [edit] set protocols dot1x authenticator interface ge-0/0/2 supplicant multiple set firewall family ethernet-switching filter filter1 term term1 from destination-address 192.0.2.16/28 set firewall family ethernet-switching filter filter1 term term1 then count counter1 Step-by-Step Procedure To configure firewall filters on an interface enabled for multiple supplicants: 1. Configure interface ge-0/0/2 for multiple supplicant mode authentication: [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/2 supplicant multiple 2. Configure a firewall filter to count packets from each user. As each new user is authenticated on this multiple supplicant interface, this filter term will be included in the dynamically created term for the user: 2321 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit firewall family ethernet-switching] user@switch# set filter filter1 term term1 from destination-address 192.0.2.16/28 user@switch# set filter filter1 term term1 then count counter1 user@switch# set filter filter1 term term2 then policer p1 Results Check the results of the configuration: user@switch> show configuration firewall { family ethernet-switching { filter filter1 { term term1 { from { destination-address { 192.0.2.16/28; } } then count counter1; term term2 { from { destination-address { 192.0.2.16/28; } } then policer p1; } } } policer p1 { if-exceeding { bandwidth-limit 1m; burst-size-limit 1k; } then discard; } } protocols { dot1x { authenticator interface ge-0/0/2 { supplicant multiple; } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying Firewall Filters on Interfaces with Multiple Supplicants on page 2322 Verifying Firewall Filters on Interfaces with Multiple Supplicants Purpose 2322 Verify that firewall filters are functioning on the interface with multiple supplicants. Chapter 82: Examples: Access Control Configuration Action 1. Check the results with one user authenticated on the interface. In this case, the user is authenticated on ge-0/0/2: user@switch> show dot1x firewall Filter: dot1x_ge-0/0/2 Counters counter1_dot1x_ge-0/0/2_user1 100 2. When a second user, User2, is authenticated on the same interface, ge-0/0/2, you can verify that the filter includes the results for both of the users authenticated on the interface: user@switch> show dot1x firewall Filter: dot1x-filter-ge-0/0/0 Counters counter1_dot1x_ge-0/0/2_user1 100 counter1_dot1x_ge-0/0/2_user2 400 Meaning Related Documentation The results displayed by the show dot1x firewall output reflect the dynamic filter created with the authentication of each new user. User1 accessed the file server located at the specified destination address 100 times, while User2 accessed the same file server 400 times. • Example: Applying a Firewall Filter to 802.1X-Authenticated Supplicants Using RADIUS Server Attributes on a J-EX Series Switch on page 2296 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 Example: Setting Up Captive Portal Authentication on a J-EX Series Switch You can set up captive portal authentication (hereafter referred to as captive portal) on a switch to redirect Web browser requests to a login page that requires the user to input a username and password. Upon successful authentication, the user is allowed to continue with the original page request and subsequent access to the network. This example describes how to set up captive portal on a J-EX Series switch: • Requirements on page 2324 • Overview and Topology on page 2324 • Configuration on page 2324 • Verification on page 2326 • Troubleshooting on page 2327 2323 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example uses the following hardware and software components: • A J-EX4200 Series switch Before you begin, be sure you have: • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Generated an SSL certificate and installed it on the switch. See “Generating SSL Certificates to Be Used for Secure Web Access” on page 398. • Configured basic access between the J-EX Series switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Designed your captive portal login page. See “Designing and Modifying a Captive Portal Authentication Login Page on a J-EX Series Switch” on page 2351. Overview and Topology This example shows the configuration required on the switch to enable captive portal on an interface. To permit a printer connected to the captive portal interface to access the LAN, add its MAC address to the authentication whitelist. The MAC addresses on this list are permitted access on the interface without captive portal authentication. The topology for this example consists of one J-EX Series switch connected to a RADIUS authentication server. One interface on the switch is configured for captive portal. In this example, the interface is configured in single supplicant mode. Configuration To configure captive portal on your switch: CLI Quick Configuration To quickly configure captive portal on the switch after completing the tasks in the Requirements section, copy the following commands and paste them into the switch terminal window: [edit] set system services web-management https local-certificate my-signed-cert set services captive-portal secure-authentication https set services captive-portal interface ge-0/0/10.0 set ethernet-switching-options authentication-whitelist 00:10:12:e0:28:22 set custom-options post-authentication-url http://www.my-home-page.com Step-by-Step Procedure To configure captive portal on the switch: 1. To create a secure channel for Web access to the switch, configure captive portal for HTTPS: a. Associate the security certificate with the Web server and enable HTTPS on the switch: [edit] user@switch# set system services web-management https local-certificate my-signed-cert 2324 Chapter 82: Examples: Access Control Configuration NOTE: You can enable HTTP instead of HTTPS, but we recommend HTTPS for security purposes. b. Configure captive portal to use HTTPS: [edit] user@switch# set services captive-portal secure-authentication https 2. Enable an interface for captive portal: [edit] user@switch# set services captive-portal interface ge-0/0/10 3. (Optional) Allow specific clients to bypass captive portal authentication: [edit] user@switch# set ethernet-switching-options authentication-whitelist 00:10:12:e0:28:22 NOTE: Optionally, you can use set ethernet-switching-options authentication-whitelist 00:10:12:e0:28:22 interface ge-0/0/10.0 to limit the scope to the interface. If the MAC address has already been learned on the interface, you must clear it using the clear captive-portal interface interface-name) before adding it to the whitelist. Otherwise the new entry for the MAC address will not be added to the ethernet switching table and the authentication bypass will not be allowed. 4. (Optional) To redirect clients to a specified page rather than the page they originally requested, configure the post-authentication URL: [edit services captive-portal] user@switch# set custom-options post-authentication-url http://www.my-home-page.com Results Display the results of the configuration: [edit] user@switch# show system { services { web-management { https { local-certificate my-signed-cert; } } } } security { certificates { local { my-signed-cert { 2325 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS "-----BEGIN RSA PRIVATE KEY-----\nMIICXwIBAAKBgQDk8sUggnXdDUmr7T vLv63yJq/LRpDASfIDZlX3z9ZDe1Kfk5C9\nr/tkyvzv ... Pt5YmvWDoGo0mSjoE/liH0BqYdh9YGqv3T2IEUfflSTQQHEOShS0ogWDHF\ nnyOb1O/vQtjk20X9NVQg JHBwidssY9eRp\n-----END CERTIFICATE-----\n"; ## SECRET-DATA } } } } services { captive-portal { interface { ge-0/0/10.0; } secure-authentication https; } } ethernet-switching-options { authentication-whitelist { 00:10:12:e0:28:22/48; } } Verification To confirm that captive portal authentication is configured and working properly, perform these tasks: • Verifying That Captive Portal Is Enabled on the Interface on page 2326 • Verify That Captive Portal Is Working Correctly on page 2326 Verifying That Captive Portal Is Enabled on the Interface Purpose Action Verify that captive portal is configured on interface ge-0/0/10. Use the operational mode command show captive-portal interface interface-name detail: user@switch> show captive-portal interface ge-0/0/10.0 detail ge-0/0/10.0 Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Configured CP session timeout: 3600 seconds Server timeout: 15 seconds Meaning The output confirms that captive portal is configured on interface ge-0/0/10 with the default settings for number of retries, quiet period, CP session timeout, and server timeout. Verify That Captive Portal Is Working Correctly Purpose Action 2326 Verify that captive portal is working on the switch. Connect a client to interface ge-0/0/10. From the client, open a Web browser and request a webpage. The captive portal login page that you designed should be displayed. After Chapter 82: Examples: Access Control Configuration you enter your login information and are authenticated against the RADIUS server, the Web browser should display either the page you requested or the post-authentication URL that you configured. Troubleshooting To troubleshoot captive portal, perform these tasks: Troubleshooting Captive Portal Problem The switch does not return the captive portal login page when a user connected to a captive portal interface on the switch requests a Web page. Solution You can examine the ARP, DHCP, HTTPS, and DNS counters—if one or more of these counters are not incrementing, this provides an indication of where the problem lies. For example, if the client cannot get an IP address, you might check the switch interface to determine whether the DHCP counter is incrementing—if the counter increments, the DHCP packet was received by the switch. user@switch> show captive-portal firewall ge-0/0/10.0 ge-0/0/10.0 Filter name: dot1x_ge-0/0/10 Counters: Name Bytes Packets dot1x_ge-0/0/10_CP_arp 7616 119 dot1x_ge-0/0/10_CP_dhcp 0 0 dot1x_ge-0/0/10_CP_http 0 0 dot1x_ge-0/0/10_CP_https 0 0 dot1x_ge-0/0/10_CP_t_dns 0 0 dot1x_ge-0/0/10_CP_u_dns 0 0 Related Documentation • Configuring Captive Portal Authentication (CLI Procedure) on page 2350Configuring • Designing a Captive Portal Authentication Login Page on a J-EX Series Switch on page 2351 2327 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2328 CHAPTER 83 Configuring Access Control • Specifying RADIUS Server Connections on a J-EX Series Switch (CLI Procedure) on page 2330 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring Static MAC Bypass of Authentication (CLI Procedure) on page 2334 • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Configuring LLDP (CLI Procedure) on page 2344 • Configuring LLDP (J-Web Procedure) on page 2345 • Configuring LLDP-MED (CLI Procedure) on page 2346 • VSA Match Conditions and Actions for J-EX Series Switches on page 2348 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 • Designing a Captive Portal Authentication Login Page on a J-EX Series Switch on page 2351 2329 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Specifying RADIUS Server Connections on a J-EX Series Switch (CLI Procedure) IEEE 802.1X and MAC RADIUS authentication both provide network edge security, protecting Ethernet LANs from unauthorized user access by blocking all traffic to and from devices at the interface until the supplicant's credentials or MAC address are presented and matched on the authentication server (a RADIUS server). When the supplicant is authenticated, the switch stops blocking access and opens the interface to the supplicant. To use 802.1X or MAC RADIUS authentication, you must specify the connections on the switch for each RADIUS server to which you will connect. To configure a RADIUS server on the switch: 1. Define the IP address of the RADIUS server, the RADIUS server authentication port number, and the secret password. You can define more than one RADIUS server. The secret password on the switch must match the secret password on the server: [edit access] user@switch# set radius-server 10.0.0.100 port 1812 secret abc NOTE: Specifying the authentication port is optional, and port 1812 is the default. However, we recommend that you configure it in order to avoid confusion as some RADIUS servers might refer to an older default. 2. (Optional) Specify the IP address by which the switch is identified by the RADIUS server. If you do not specify this, the RADIUS server uses the address of the interface sending the RADIUS request. We recommend that you specify this IP address because if the request gets diverted on an alternate route to the RADIUS server, the interface relaying the request might not be an interface on the switch. [edit access] user@switch# set access radius-erver source-address 10.93.14.100 3. Configure the authentication order, making radius the first method of authentication: [edit access] user@switch# set profile profile1 authentication-order radius 4. Create a profile and specify the list of RADIUS servers to be associated with the profile. For example, you might choose to group your RADIUS servers geographically by city. This feature enables easy modification whenever you want to change to a different sent of authentication servers. [edit access profile] user@switch# set atlanta radius authentication-server 10.0.0.100 10.2.14.200 5. Specify the group of servers to be used for 802.1X or MAC RADIUS authentication by identifying the profile name: [edit access profile] user@switch# set protocols dot1x authenticator authentication-profile-name denver 2330 Chapter 83: Configuring Access Control 6. Configure the IP address of the J-EX Series switch in the list of clients on the RADIUS server. For specifics on configuring the RADIUS server, consult the documentation for your server. Related Documentation • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 Configuring 802.1X Interface Settings (CLI Procedure) IEEE 802.1X authentication provides network edge security, protecting Ethernet LANs from unauthorized user access by blocking all traffic to and from a supplicant (client) at the interface until the supplicant's credentials are presented and matched on the authentication server (a RADIUS server). When the supplicant is authenticated, the switch stops blocking access and opens the interface to the supplicant. NOTE: You can also specify an 802.1X exclusion list to specify supplicants can that can bypass authentication and be automatically connected to the LAN. See “Configuring Static MAC Bypass of Authentication (CLI Procedure)” on page 2334. Before you begin, specify the RADIUS server or servers to be used as the authentication server. See “Specifying RADIUS Server Connections on a J-EX Series Switch (CLI Procedure)” on page 2330. To configure 802.1X on an interface: 1. Configure the supplicant mode as single (authenticates the first supplicant), single-secure (authenticates only one supplicant), or multiple (authenticates multiple supplicants): [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/5 supplicant multiple 2. Enable reauthentication and specify the reauthentication interval: [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/5/0 reauthentication interval 5 3. Configure the interface timeout value for the response from the supplicant: [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/5 supplicant-timeout 5 4. Configure the timeout for the interface before it resends an authentication request to the RADIUS server: [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/5 server-timeout 5 2331 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 5. Configure how long, in seconds, the interface waits before retransmitting the initial EAPOL PDUs to the supplicant: [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/5 transmit-period 60 6. Configure the maximum number of times an EAPOL request packet is retransmitted to the supplicant before the authentication session times out: [edit protocols dot1x] user@switch# set authenticator interface ge-0/0/5 maximum-requests 5 Related Documentation • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Monitoring 802.1X Authentication on page 2355 • Verifying 802.1X Authentication on page 2356 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding Authentication onJ-EX Series Switches on page 2248 Configuring 802.1X Authentication (J-Web Procedure) To configure 802.1X settings on a J-EX Series switch using the J-Web interface: 1. Select Configure > Security > 802.1X. The 802.1X screen displays a list of interfaces, whether 802.1X security has been enabled, and the assigned port role. When you select an interface, the Details of 802.1x configuration on port section displays 802.1X details for that interface. 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 334 for details about all commit options. 2. Click one: 2332 • RADIUS Servers—Specifies the RADIUS server to be used for authentication. Select the check box to specify a server. Click Add or Edit to add or modify the RADIUS server settings. Enter information as specified in Table 296 on page 2333. • Exclusion List—Excludes hosts from the 802.1X authentication list by specifying the MAC address. Click Add or Edit in the Exclusion list screen to include or modify the MAC addresses. Enter information as specified in Table 297 on page 2333. • Edit—Specifies 802.1X settings for the selected interface Chapter 83: Configuring Access Control • • Apply 802.1X Profile—Applies an 802.1X profile based on the port role. If a message appears asking whether you want to configure a RADIUS server, click Yes. • 802.1X Configuration—Configures custom 802.1X settings for the selected interface. If a message appears asking if you want to configure a RADIUS server, click Yes. Enter information as specified in Table 296 on page 2333. To configure 802.1X settings, enter information as specified in Table 298 on page 2333. Delete—Deletes 802.1X authentication configuration on the selected interface. Table 296: RADIUS Server Settings Field Function Your Action IP Address Specifies the IP address of the server. Enter the IP address in dotted decimal notation. Password Specifies the login password. Enter the password. Confirm Password Verifies the login password for the server. Reenter the password. Server Port Number Specifies the port with which the server is associated. Type the port number. Source Address Specifies the source address of the switch using which the switch can communicate with the server. Type the IP address in dotted decimal notation. Retry Attempts Specifies the number of login retries allowed after a login failure. Type the number. Timeout Specifies the time interval to wait before the connection to the server is closed. Type the interval in seconds. Table 297: 802.1X Exclusion List Field Function Your Action MAC Address Specifies the MAC address to be excluded from 802.1X authentication. Enter the MAC address. Exclude if connected through the port Specifies that the host can bypass authentication if it is connected through a particular interface. Select to enable the option. Select the port through which the host is connected. Move the host to the VLAN Specifies moving the host to a specific VLAN once the host is authenticated. Select to enable the option. Select the VLAN from the list. Table 298: 802.1X Port Settings Field Function Your Action Supplicant Mode 2333 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 298: 802.1X Port Settings (continued) Field Function Your Action Supplicant Mode Specifies the mode to be adopted for supplicants: Select a mode. • Single—allows only one host for authentication. • Multiple—allows multiple hosts for authentication. Each host is checked before being admitted to the network. • Single authentication for multiple hosts—Allows multiple hosts but only the first is authenticated. Authentication Enable re-authentication Specifies enabling reauthentication on the selected interface. 1. Action on authentication failure Specifies the action to be taken in case the host does not respond, leading to an authentication failure. Select one: Timeouts Specifies timeout values for each action. Related Documentation Select to enable reauthentication. 2. Enter the timeout for reauthentication in seconds. • Move to the Guest VLAN—Select the VLAN to move the interface to. • Deny—The host is not permitted access. Enter the value in seconds for: • Port waiting time after an authentication failure • EAPOL retransmitting interval • Max. EAPOL requests • Maximum number of retries • Port timeout value for the response from the supplicant • Port timeout value for the response from the RADIUS server • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Understanding Authentication onJ-EX Series Switches on page 2248 Configuring Static MAC Bypass of Authentication (CLI Procedure) You can configure a static MAC bypass list (sometimes called the exclusion list) on the switch to specify MAC addresses of devices allowed access to the LAN without 802.1X or MAC RADIUS authentication requests to the RADIUS server. To configure the static MAC bypass list: • 2334 Specify a MAC address to bypass authentication: Chapter 83: Configuring Access Control [edit protocols dot1x] user@switch# set authenticator static 00:04:0f:fd:ac:fe • Configure a supplicant to bypass authentication if connected through a particular interface: [edit protocols dot1x] user@switch# set authenticator static 00:04:0f:fd:ac:fe interface ge-0/0/5 • You can configure a supplicant to be moved to a specific VLAN after it is authenticated: [edit protocols dot1x] user@switch# set authenticator static 00:04:0f:fd:ac:fe interface ge-0/0/5 vlan-assignment default-vlan Related Documentation • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 Configuring MAC RADIUS Authentication (CLI Procedure) You can permit devices that are not 802.1X-enabled LAN access by configuring MAC RADIUS authentication on the J-EX Series switch interfaces to which the hosts are connected. NOTE: You can also allow non-802.1X-enabled devices to access the LAN by configuring their MAC address for static MAC bypass of authentication. You can configure MAC RADIUS authentication on an interface that also allows 802.1X authentication, or you can configure either authentication method alone. If both MAC RADIUS and 802.1X authentication are enabled on the interface, the switch first sends the host three EAPOL requests to the host. If there is no response from the host, the switch sends the host’s MAC address to the RADIUS server to check whether it is a permitted MAC address. If the MAC address is configured as permitted on the RADIUS server, the RADIUS server sends a message to the switch that the MAC address is a permitted address, and the switch opens LAN access to the nonresponsive host on the interface to which it is connected. If MAC RADIUS authentication is configured on the interface but 802.1X authentication is not (by using the mac-radius restrict option), the switch attempts to authenticate the MAC address with the RADIUS server without delaying by attempting 802.1X authentication first. Before you configure MAC RADIUS authentication, be sure you have: 2335 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configured basic access between the J-EX Series switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. To configure MAC RADIUS authentication using the CLI: • On the switch, configure the interfaces to which the nonresponsive hosts are attached for MAC RADIUS authentication, and add the restrict qualifier for interface ge-0/0/20 to have it use only MAC RADIUS authentication: [edit] user@switch# set protocols dot1x authenticator interface ge-0/0/19 mac-radius user@switch# set protocols dot1x authenticator interface ge-0/0/20 mac-radius restrict • On a RADIUS authentication server, create user profiles for each nonresponsive host using the MAC address (without colons) of the nonresponsive host as the username and password (here, the MAC addresses are 00:04:0f:fd:ac:fe and 00:04:ae:cd:23:5f): [root@freeradius]# edit /etc/raddb vi users 00040ffdacfe Auth-type:=Local, User-Password = "00040ffdacfe" 0004aecd235f Auth-type:=Local, User-Password = "0004aecd235f" Related Documentation 2336 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Verifying 802.1X Authentication on page 2356 • Understanding MAC RADIUS Authentication on J-EX Series Switches Chapter 83: Configuring Access Control Configuring Server Fail Fallback (CLI Procedure) Server fail fallback allows you to specify how end devices connected to the switch are supported if the RADIUS authentication server becomes unavailable or sends an Extensible Authentication Protocol Over LAN (EAPOL) access-reject message. 802.1X user authentication works by using an authenticator port access entity (the J-EX Series switch) to block all traffic to and from an end device at the interface until the end device's credentials are presented and matched on the authentication server (a RADIUS server). When the end device has been authenticated, the switch stops blocking and opens the interface to the end device. When you set up 802.1X or MAC RADIUS authentication on the switch, you specify a primary authentication server and one or more backup authentication servers. If the primary authentication server cannot be reached by the switch and the secondary authentication servers are also unreachable, a RADIUS server timeout occurs. Because the authentication server grants or denies access to the end devices awaiting authentication, the switch does not receive access instructions for end devices attempting access to the LAN and normal authentication cannot be completed. Server fail fallback allows you to configure authentication alternatives that permit the switch to take appropriate actions toward end devices awaiting authentication or reauthentication. 2337 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To configure basic server fail fallback options using the CLI: • Configure an interface to allow traffic to flow from a supplicant to the LAN if a RADIUS server timeout occurs (as if the supplicant had been successfully authenticated by a RADIUS server): [edit protocols dot1x authenticator] user@switch# set interface ge-0/0/1 server-fail permit • Configure an interface to prevent traffic flow from an end device to the LAN (as if the end device had failed authentication and had been rejected by the RADIUS server): [edit protocols dot1x authenticator] user@switch# set interface ge-0/0/1 server-fail deny • Configure an interface to move an end device to a specified VLAN if a RADIUS server timeout occurs (in this case, the VLAN name is vlan1): [edit protocols dot1x authenticator] user@switch# set interface ge-0/0/1 server-fail vlan-name vlan1 • Configure an interface to recognize already connected end devices as reauthenticated if there is a RADIUS timeout during reauthentication (new users will be denied access): [edit protocols dot1x authenticator] user@switch# set interface ge-0/0/1 server-fail use-cache • Configure an interface that receives an EAPOL access-reject message from the authentication server to move end devices attempting LAN access on the interface to a specified VLAN already configured on the switch (in this case, the VLAN name is vlan-sf): [edit protocols dot1x authenticator] user@switch# set interface ge-0/0/1 server-reject-vlan vlan-sf Related Documentation 2338 • Example: Configuring 802.1X Authentication Options When the RADIUS Server is Unavailable to a J-EX Series Switch on page 2271 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Monitoring 802.1X Authentication on page 2355 • Understanding Server Fail Fallback and Authentication on J-EX Series Switches on page 2258 Chapter 83: Configuring Access Control Configuring 802.1X RADIUS Accounting (CLI Procedure) RADIUS accounting permits statistical data about users logging onto or off a LAN to be collected and sent to a RADIUS accounting server. The statistical data gathered can be used for general network monitoring, to analyze and track usage patterns, or to bill a user based upon the amount of time or type of services accessed. To configure basic RADIUS accounting using the CLI: 1. Specify the accounting servers to which the switch will forward accounting statistics: [edit access] user@switch# set profile profile1 radius accounting-server [122.69.1.250 122.69.1.252] 2. Define the RADIUS accounting servers: [edit access] user@switch# set radius-server 122.69.1.250 secret juniper user@switch# set radius-server 122.69.1.252 secret juniper1 3. Enable accounting for an access profile: [edit access] user@switch# set profile profile1 accounting 4. Configure the RADIUS servers to use while sending accounting messages and updates: [edit access] user@switch# set profile profile1 accounting order radius none 5. Configure the statistics to be collected on the switch and forwarded to the accounting server: [edit access] user@switch# set profile profile1 accounting order accounting-stop-on-access-deny user@switch# set profile profile1 accounting order accounting-stop-on-failure 6. Display accounting statistics collected on the switch: user@switch> show network-access aaa statistics accounting Accounting module statistics Requests received: 1 Accounting Response failures: 0 Accounting Response Success: 1 Requests timedout: 0 7. Open an accounting log on the RADIUS accounting server using the server's address, and view accounting statistics: [root@freeradius]# cd /usr/local/var/log/radius/radacct/122.69.1.250 [root@freeradius 122.69.1.250]# ls detail-20071214 [root@freeradius 122.69.1.250]# vi details-20071214 2339 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS User-Name = "000347e1bab9" NAS-Port = 67 Acct-Status-Type = Stop Acct-Session-Id = "8O2.1x811912" Acct-Input-Octets = 17454 Acct-Output-Octets = 4245 Acct-Session-Time = 1221041249 Acct-Input-Packets = 72 Acct-Output-Packets = 53 Acct-Terminate-Cause = Lost-Carrier Acct-Input-Gigawords = 0 Acct-Output-Gigawords = 0 Called-Station-Id = "00-19-e2-50-52-60" Calling-Station-Id = "00-03-47-e1-ba-b9" Event-Timestamp = "Sep 10 2008 16:52:39 PDT" NAS-Identifier = "esp48t-1b-01" NAS-Port-Type = Virtual User-Name = "000347e1bab9" NAS-Port = 67 Acct-Status-Type = Start Acct-Session-Id = "8O2.1x811219" Called-Station-Id = "00-19-e2-50-52-60" Calling-Station-Id = "00-03-47-e1-ba-b9" Event-Timestamp = "Sep 10 2008 18:58:52 PDT" NAS-Identifier = "esp48t-1b-01" NAS-Port-Type = Virtual Related Documentation • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Understanding 802.1X and RADIUS Accounting on J-EX Series Switches on page 2260 Filtering 802.1X Supplicants Using RADIUS Server Attributes There are two ways to configure the RADIUS server with port firewall filters: • Include a match statement and corresponding action in the Juniper-Firewall-Filter attribute. The Juniper-Firewall-Filter attribute is a vendor-specific attribute (VSA) in the Juniper dictionary on the RADIUS server. Use this attribute to configure simple filter conditions for authenticated users. Nothing needs to be configured on the switch; all of the configuration is on the RADIUS server. • Apply a local firewall filter to users authenticated through the RADIUS server. Use this method for more complex filters. The firewall filter must be configured on each switch. This example describes using FreeRADIUS software to configure VSAs. For specifics on configuring your server, consult the AAA documentation that was included with your server. This topic includes the following tasks: 1. Configuring Match Statements on the RADIUS Server on page 2341 2. Applying a Port Firewall Filter from the RADIUS Server on page 2343 2340 Chapter 83: Configuring Access Control Configuring Match Statements on the RADIUS Server You can configure simple filter conditions using the Juniper-Switching-Filter attribute in the Juniper dictionary on the RADIUS server. These filters are then sent to a switch whenever a new user is authenticated successfully. The filters are created and applied on all J-EX Series switches that authenticate users through that RADIUS server without the need to configure anything on each individual switch. To configure the Juniper-Switching-Filter attribute, enter one or more match conditions and a resulting action using the CLI for the RADIUS server. Enter the match statement plus an action statement enclosed within quotes (" ") using the following syntax: match } action [allow | deny] } See “VSA Match Conditions and Actions for J-EX Series Switches” on page 2348 for definitions of match statement options. To configure match conditions on the RADIUS server: 1. Verify that the Juniper dictionary is loaded on your RADIUS server and includes the filtering attribute Juniper-Switching-Filter, attribute ID 48: [root@freeradius]# cat /usr/local/share/freeradius/dictionary.juniper # dictionary.juniper # # Version: $Id: dictionary.juniper,v 1.2.6.1 2005/11/30 22:17:25 aland Exp $ # VENDOR Juniper 2636 BEGIN-VENDOR Juniper ATTRIBUTE Juniper-Local-User-Name 1 string ATTRIBUTE Juniper-Allow-Commands 2 string ATTRIBUTE Juniper-Deny-Commands 3 string ATTRIBUTE Juniper-Allow-Configuration 4 string ATTRIBUTE Juniper-Deny-Configuration 5 string ATTRIBUTE Juniper-Switching-Filter 48 string <— 2. Enter the match conditions and actions. For example: • To deny authentication based on the 802.1Q tag (here, the 802.1Q tag is 10): [root@freeradius]# cd /usr/local/etc/raddb vi users For each relevant user, add the Juniper-Switching-Filter attribute: Juniper-Switching-Filter = "match source-dot1q-tag 10 action deny" 2341 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • To deny access based on a destination IP address: [root@freeradius]# cd /usr/local/etc/raddb vi users For each relevant user, add the Juniper-Switching-Filter attribute: Juniper-Switching-Filter = “match destination-ip 192.168.1.0/31 action deny” • To set the packet loss priority (PLP) to high based on a destination MAC address and the IP protocol: [root@freeradius]# cd /usr/local/etc/raddb vi users For each relevant user, add the Juniper-Switching-Filter attribute: Juniper-Switching-Filter = "match destination-mac 00:04:0f:fd:ac:fe, ip-protocol 2, forwarding-class high, action loss-priority high" NOTE: For the forwarding-class option to be applied, the forwarding class must be configured on the switch. If it is not configured on the switch, this option is ignored. You must specify both the forwarding class and the packet loss priority. 3. Stop and restart the RADIUS process to activate the configuration. 2342 Chapter 83: Configuring Access Control Applying a Port Firewall Filter from the RADIUS Server You can apply a firewall filter to user policies on the RADIUS server. The RADIUS server can then specify the firewall filters that are to be applied to each user that requests to authenticate. Use this method when the firewall filter has more extensive conditions or you want to use different conditions for the same filter on different switches. The firewall filters must be configured on each switch. For more information about firewall filters, see “Firewall Filters for J-EX Series Switches Overview” on page 2721. To apply a port firewall filter centrally from the RADIUS server: NOTE: If port firewall filters are also configured locally for the interface, then VSAs take precedence if they conflict with the filters. If the VSAs and the local port firewall filters do not conflict, they are merged. 1. Create the firewall filter on the local switch. In this example, the filter is called filter1. 2. Open the users file on the RADIUS server: [root@freeradius]# cd /usr/local/pool/raddb vi users 3. For each relevant user, add the filter (here, the filter ID is filter1): Filter-Id = "filter1" NOTE: Multiple filters are not supported on a single interface. However, you can support multiple filters for multiple users that are connected to the switch on the same interface by configuring a single filter with policies for each of those users. 4. Stop and restart the RADIUS process to activate the configuration. Related Documentation • Example: Applying a Firewall Filter to 802.1X-Authenticated Supplicants Using RADIUS Server Attributes on a J-EX Series Switch on page 2296 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Understanding 802.1X and VSAs on J-EX Series Switches on page 2266 2343 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring LLDP (CLI Procedure) J-EX Series switches use Link Layer Discovery Protocol (LLDP) and Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) to learn and distribute device information on network links. The information allows the switch to quickly identify a variety of devices, resulting in a LAN that interoperates smoothly and efficiently. This topic describes: • Enabling LLDP on Interfaces on page 2344 • Configuring for Fast Start on page 2344 • Adjusting LLDP Advertisement Settings on page 2344 • Adjusting SNMP Notification Settings of LLDP Changes on page 2345 • Specifying a Management Address for the LLDP Management TLV on page 2345 Enabling LLDP on Interfaces LLDP is enabled on all interfaces by default. If it is disabled, you can enable LLDP by configuring it on all interfaces or specific interfaces. To configure LLDP on all interfaces or on a specific interface: [edit protocols lldp] user@switch# set interface all Configuring for Fast Start You can specify the number of LLDP-MED advertisements sent from the switch in the first second after it has detected an LLDP-capable device. The default is 3; to set it to another value: [edit protocols lldp] user@switch# set fast-start 8 Adjusting LLDP Advertisement Settings You can adjust the following settings for LLDP advertisements for troubleshooting or verification purposes. For normal operations, we recommend that you do not adjust these settings from the default values. • To specify the frequency at which LLDP advertisements are sent (in seconds): [edit protocols lldp] user@switch# set advertisement-interval 45 • To determine the length of time LLDP information is held before it is discarded (the multiplier value is used in combination with the advertisement-interval value): [edit protocols lldp] user@switch# set hold-multiplier 5 2344 Chapter 83: Configuring Access Control Adjusting SNMP Notification Settings of LLDP Changes You can adjust the following settings for SNMP notifications of LLDP changes. If the values are not specified or the interval values are set to 0, the notifications are disabled. • To specify the frequency at which LLDP database changes are sent (in seconds): [edit protocols lldp] user@switch# set lldp-configuration-notification-interval 600 • To specify the frequency at which changes in topology global statistics are sent (in seconds): [edit protocols lldp] user@switch# set ptopo-configuration-trap-interval 600 • To specify the holding time (used in combination with the ptopo-configuration-trap-interval value) to determine the length of time that topology global statistics are held before they are is discarded (in seconds): [edit protocols lldp] user@switch# set ptopo-configuration-maximum-hold-time 2147483647 Specifying a Management Address for the LLDP Management TLV You can configure an IP management address to be used in the LLDP Management type, length, and value (TLV). To configure the management address: [edit protocols lldp] user@switch# set management-address 192.168.0.0 Related Documentation • Configuring LLDP (J-Web Procedure) on page 2345 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Configuring LLDP (J-Web Procedure) Use the LLDP Configuration page to configure LLDP global and port settings for a J-EX Series switch on the J-Web interface. To configure LLDP: 1. Select Configure > Switching > LLDP. The LLDP Configuration page displays LLDP Global Settings and Port Settings. The second half of the screen displays operational details for the selected port. 2345 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 334 for details about all commit options. 2. To modify LLDP Global Settings, click Global Settings. Enter information as described in Table 299 on page 2346. 3. To modify Port Settings, click Edit in the Port Settings section. Enter information as described in Table 300 on page 2346. Table 299: Global Settings Field Function Your Action Advertising interval Specifies the frequency of outbound LLDP advertisements. You can increase or decrease this interval. Type the number of seconds. Hold multiplier Specifies the multiplier factor to be used by an LLDP-enabled switch to calculate the time-to-live (TTL) value for the LLDP advertisements it generates and transmits to LLDP neighbors. Type the required number in the field. Fast start count Specifies the number of LLDP advertisements sent in the first second after the device connects. The default is 3. Increasing this number results in the port initially advertising LLDP–MED at a faster rate for a limited time. Type the Fast start count. Table 300: Edit Port Settings Field Function Your Action LLDP Status Specifies whether LLDP has been enabled on the port. Select one: Enabled, Disabled, or None. LLDP-MED Status Specifies whether LLDP–MED has been enabled on the port. Select Enable from the list. Related Documentation • Configuring LLDP (CLI Procedure) on page 2344 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Configuring LLDP-MED (CLI Procedure) Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) is an extension of LLDP. The J-EX Series switch uses LLDP-MED to support device discovery of VoIP telephones and to create location databases for these telephone locations. 2346 Chapter 83: Configuring Access Control LLDP-MED is turned on by default on J-EX Series switches. This topic describes: • Enabling LLDP-MED on Interfaces on page 2347 • Configuring Location Information Advertised by the Switch on page 2347 • Configuring for Fast Start on page 2347 Enabling LLDP-MED on Interfaces LLDP-MED is enabled on all interfaces by default. If it is disabled, you can enable LLDP-MED by configuring it on all interfaces or on specific interfaces. To configure LLDP-MED on all interfaces or on a specific interface: [edit protocols lldp-med] user@switch# set interface ge-0/0/2.0 Configuring Location Information Advertised by the Switch You can configure the location information that is advertised from the switch to the LLDP-MED device. You can specify a civic-based location (geographic location) or a location based on an elin (emergency location identification string): • To specify a location by geography: [edit protocols lldp-med] user@switch# set interface ge-0/0/2.0 location civic-based country-code US user@switch# set interface ge-0/0/2.0 location civic-based ca-type 1 ca-value “El Dorado County” user@switch# set interface ge-0/0/2.0 location civic-based ca-type 2 ca-value CA user@switch# set interface ge-0/0/2.0 location civic-based ca-type 3 ca-value Somerset user@switch# set interface ge-0/0/2.0 location civic-based ca-type 6 ca-value “Mount Aukum Road” user@switch# set interface ge-0/0/2.0 location civic-based ca-type 19 ca-value 6450 user@switch# set interface ge-0/0/2.0 location civic-based ca-type 21 ca-value “Holiday Market” • To specify a location using an elin string: [edit protocols lldp-med] user@switch# set interface ge-0/0/2.0 location elin 4085551212 Configuring for Fast Start You can specify the number of LLDP-MED advertisements sent from the switch in the first second after it has detected an LLDP-MED device. The default is 3; to set it to another value: [edit protocols lldp-med] user@switch# set fast-start 6 2347 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Configuring LLDP (J-Web Procedure) on page 2345 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 VSA Match Conditions and Actions for J-EX Series Switches J-EX Series switches support the configuration of RADIUS server attributes specific to Juniper Networks. These attributes are known as vendor-specific attributes (VSAs). They are configured on RADIUS servers and work in combination with 802.1X authentication. Using VSAs, you can apply port firewall filter attributes as a subset of match conditions and actions sent from the RADIUS server to the switch as a result of 802.1X authentication success. Each term in a VSA configured through the RADIUS server consists of match conditions and an action. Match conditions are the values or fields that the packet must contain. You can define single, multiple, or no match conditions. If no match conditions are specified for the term, the packet is accepted by default. The action is the action that the switch takes if a packet matches the match conditions for the specific term. Allowed actions are accept a packet or discard a packet. The following guidelines apply when you specify match conditions and actions for VSAs: • Both match and action statements are mandatory. • Any or all options (separated by commas) may be included in each match and action statement. • Fields separated by commas will be ANDed if they are of a different type. The same types cannot be repeated. • For OR cases (for example, match 10.1.1.0/24 OR 11.1.1.0/24), apply multiple VSAs to the 802.1X supplicant. • In order for the forwarding-class option to be applied, the forwarding class must be configured on the switch. If it is not configured on the switch, this option is ignored. Table 301 on page 2348 describes the match conditions you can specify when configuring a VSA using the match command on the RADIUS server. The string that defines a match condition is called a match statement. Table 301: Match Conditions Option Description destination-mac mac-address Destination media access control (MAC) address of the packet. source-vlan source-vlan Name of the source VLAN. 2348 Chapter 83: Configuring Access Control Table 301: Match Conditions (continued) Option Description source-dot1q-tag tag Tag value in the dot1q header, in the range 0 through 4095. destination-ip ip-address Address of the final destination node. ip-protocol protocol-id IPv4 protocol value. In place of the numeric value, you can specify one of the following text synonyms: ah, egp (8), esp (50, gre (47), icmp (1), igmp (2), ipip (4), ipv6 (41), ospf (89), pim (103), rsvp (46), tcp (6), or udp (17) source-port port TCP or User Datagram Protocol (UDP) source port field. Normally, you specify this match statement in conjunction with the ip-protocol match statement to determine which protocol is being used on the port. In place of the numeric field, you can specify one of the text options listed under destination-port. destination-port port TCP or UDP destination port field. Normally, you specify this match in conjunction with the ip-protocol match statement to determine which protocol is being used on the port. In place of the numeric value, you can specify one of the following text synonyms (the port numbers are also listed): afs (1483), bgp (179), biff (512), bootpc (68), bootps (67), cvspserver (2401), cmd (514), dhcp (67), domain (53), eklogin (2105), ekshell (2106), exec (512), finger (79), ftp (21), ftp-data (20), http (80), https (443), ident (113), imap (143), kerberos-sec (88), klogin (543), kpasswd (761), krb-prop (754), krbupdate (760), kshell (544), ldap (389), login (513), mobileip-agent (434), mobilip-mn (435), msdp (639), netbios-dgm (138), netbios-ns (137), netbios-ssn (139), nfsd (2049), nntp (119), ntalk (518), ntp (123), pop3 (110), pptp (1723), printer (515), radacct (1813), radius (1812), rip (520), rkinit (2108), smtp (25), snmp (161), snmptrap (162), snpp (444), socks (1080), ssh (22), sunrpc (111), syslog (514), telnet (23), tacacs-ds (65), talk (517), tftp (69), timed (525), who (513), xdmcp (177), zephyr-clt (2103), zephyr-hm (2104) When you define one or more terms that specify the filtering criteria, you also define the action to take if the packet matches all criteria. Table 302 on page 2349 shows the actions that you can specify in a term. Table 302: Actions for VSAs Option Description (allow | deny) Accept a packet or discard a packet silently without sending an Internet Control Message Protocol (ICMP) message. forwarding-class class-of-service (Optional) Classify the packet in one of the following forwarding classes: • assured-forwarding • best-effort • expedited-forwarding • network-control 2349 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 302: Actions for VSAs (continued) Option Description loss-priority (low | medium | high) (Optional) Set the packet loss priority (PLP) to low, medium, or high. Specify both the forwarding class and loss priority. Related Documentation • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Understanding 802.1X and VSAs on J-EX Series Switches on page 2266 Configuring Captive Portal Authentication (CLI Procedure) Configure captive portal authentication (hereafter referred to as captive portal) on a J-EX Series switch so that users connected to the switch are authenticated before being allowed to access the network. When the user requests a webpage, a login page is displayed that requires the user to input a username and password. Upon successful authentication, the user is allowed to continue with the original page request and subsequent access to the network. Before you begin, be sure you have: • Performed basic bridging and VLAN configuration on the switch. See “Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch” on page 1063. • Generated an SSL certificate and installed it on the switch. See “Generating SSL Certificates to Be Used for Secure Web Access” on page 398. • Configured basic access between the J-EX Series switch and the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Designed your captive portal login page. See “Designing a Captive Portal Authentication Login Page on a J-EX Series Switch” on page 2351. This topic includes the following tasks: • Configuring Secure Access for Captive Portal on page 2350 • Enabling an Interface for Captive Portal on page 2351 • Configuring Bypass of Captive Portal Authentication on page 2351 Configuring Secure Access for Captive Portal To configure secure access for captive portal: 1. Associate the security certificate with the Web server and enable HTTPS on the switch: [edit] user@switch# set system services web-management https local-certificate my-signed-cert 2350 Chapter 83: Configuring Access Control NOTE: You can enable HTTP instead of HTTPS, but we recommend HTTPS for security purposes. 2. Configure captive portal to use HTTPS: [edit] user@switch# set services captive-portal secure-authentication https Enabling an Interface for Captive Portal To enable an interface for use with captive portal authentication: [edit] user@switch# set services captive-portal interface ge-0/0/10 Configuring Bypass of Captive Portal Authentication You can allow specific clients to bypass captive portal authentication: [edit] user@switch# set ethernet-switching-options authentication-whitelist 00:10:12:e0:28:22 NOTE: Optionally, you can use set ethernet-switching-options authentication-whitelist 00:10:12:e0:28:22 interface ge-0/0/10.0 to limit the scope to the interface. If the MAC address of the client that you want to configure for authentication bypass has already been learned on the interface, you must clear it using the clear captive-portal interface interface-namebefore adding it to the whitelist. Otherwise the new entry for the MAC address will not be added to the ethernet switching table and the authentication bypass will not be allowed. Related Documentation • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Understanding Captive Portal Authentication Designing a Captive Portal Authentication Login Page on a J-EX Series Switch You can set up captive portal authentication on your switch to redirect all Web browser requests to a login page that requires the user to input a username and password before they are allowed access. Upon successful authentication, the user is allowed access to the network and to continue to the original page requested. The Junos OS provides a customizable template for the captive portal window that allows you to easily design and modify the look of the captive portal login page. You can modify the design elements in the template to change the look of your captive portal login page and to add instructions or information to the page. You can also modify any of the design elements of an existing captive portal login page. Figure 59 on page 2352 shows an example of a captive portal login page: 2351 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 59: Example of a Captive Portal Login Page Table 303 on page 2352 summarizes the configurable elements of a captive portal login page. Table 303: Configurable Elements of a Captive Portal Login Page Element CLI Statement Description Banner message banner-message text-string The first screen displayed before the captive portal login page is displayed (not shown). The page header says “Terms and Conditions of Use: Please read the following terms of use and disclaimers carefully before using this network.” The configurable banner message appears in the body of the page. The default text is “Terms and Conditions.” A button labeled Agree gives the user access to the captive portal login page. Footer background color footer-bgcolor hex-color The HTML hexadecimal code for the background color of the captive portal login page footer. Footer message footer-message text-string For example, you can include copyright information and links to additional information such as help instructions, legal notices, or a privacy policy. Form header background color form-header-bgcolor hex-color The HTML hexadecimal code for the background color of the header bar across the top of the form area of the captive portal login page. Form header message form-header-message text-string Text displayed in the header bar across the top of the form area of the captive portal login page. For example, Welcome to My Cafe. The default text is Captive Portal User Authentication. Form reset button label 2352 form-reset-label label-name Label appearing in the button that the user can select to clear the username and password fields on the form, for example, Reset or Clear. Chapter 83: Configuring Access Control Table 303: Configurable Elements of a Captive Portal Login Page (continued) Element CLI Statement Description Form submit button label form-submit-label label-name Label appearing in the button that user selects to submit their login information—for example, Log In or OK. Header background color header-bgcolor hex-color The HTML hexadecimal code for the background color of the captive portal login page header. Header logo header-logo filename Filename of the file containing the image of the logo that you want to appear at the top of the captive portal login page. The image file can be in GIF, JPEG, or PNG format. You can upload a logo image file to the switch. Copy the logo to the /var/tmp directory on the switch (during the commit the files are saved to persistent locations). Header message header-message text-string Text displayed in the page header. The default text is User Authentication. Post-authentication URL post-authentication-url url URL to which the users are directed upon successful authentication. The default is to redirect users to the page they had originally requested. To design the captive portal login page: 1. (Optional) Upload your logo image file to the switch: user@switch> file copy ftp://username:prompt@ftp.hostname.net/var/tmp/my-logo.jpeg 2. Configure the custom options to specify the background colors and text displayed in the captive portal page: [edit system services captive-portal] user@switch# set custom-options header-bgcolor #006600 set custom-options header-message “Welcome to Our Network” set custom-options banner-message “Please enter your username and password:” set custom-options footer-message “Copyright ©2009, Our Network” NOTE: For the custom options that you do not specify, the value is taken from the standard template. Related Documentation • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 2353 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2354 CHAPTER 84 Verifying 802.1X and MAC RADIUS Authentication • Monitoring 802.1X Authentication on page 2355 • Verifying 802.1X Authentication on page 2356 Monitoring 802.1X Authentication Purpose Action Use the monitoring feature to display details of authenticated users and users who have failed authentication. To display authentication details in the J-Web interface, select Monitoring > Security > 802.1X. To display authentication details in the CLI, enter the following commands: Meaning • show dot1x interface detail | display xml • show dot1x interface detail | display xml • show dot1x auth-failed-users The details displayed include: • A list of authenticated users. • The total number of users connected. • A list of users who have failed authentication You can also specify an interface for which the details must be displayed. Related Documentation • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 2355 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verifying 802.1X Authentication Purpose Action Verify that supplicants are being authenticated on an interface on a J-EX Series switch with the interface configured for 802.1X authentication, and display the method of authentication being used. Display detailed information about an interface configured for 802.1X (here, the interface is ge-0/0/16): user@switch> show dot1x interface ge-0/0/16.0 detail ge-0/0/16.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Enabled Mac Radius Strict: Disabled Reauthentication: Enabled Reauthentication interval: 40 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 1 Guest VLAN member: Number of connected supplicants: 1 Supplicant: user5, 00:30:48:8C:66:BD Operational state: Authenticated Authentication method: Radius Authenticated VLAN: v200 Reauthentication due in 17 seconds Meaning The sample output from the show dot1x interface detail command shows that the Number of connected supplicants is 1. The supplicant that was authenticated and is now connected to the LAN is known as user5 on the RADIUS server and has the MAC address 00:30:48:8C:66:BD. The supplicant was authenticated by means of the 802.1X authentication method called Radius authentication. When the Radius authentication method is used, the supplicant is configured on the RADIUS server, the RADIUS server communicates this to the switch, and the switch opens LAN access on the interface to which the supplicant is connected. The sample output also shows that the supplicant is connected to VLAN v200. Other 802.1X authentication methods supported on J-EX Series switches in addition to the RADIUS method are: • Guest VLAN—A nonresponsive host is granted Guest-VLAN access. • MAC Radius—A nonresponsive host is authenticated based on its MAC address. The MAC address is configured as permitted on the RADIUS server, the RADIUS server lets the switch know that the MAC address is a permitted address, and the switch opens LAN access to the nonresponsive host on the interface to which it is connected. • Server-fail deny—If the RADIUS servers time out, all supplicants are denied access to the LAN, preventing traffic from flowing from the supplicant through the interface. This is the default. 2356 Chapter 84: Verifying 802.1X and MAC RADIUS Authentication • Server-fail permit—When the RADIUS server is unavailable, a supplicant is still permitted access to the LAN as if the supplicant had been successfully authenticated by the RADIUS server. • Server-fail use-cache—If the RADIUS servers time out during reauthentication, previously authenticated supplicants are granted access, but new supplicants are denied LAN access. • Server-fail VLAN—A supplicant is configured to be moved to a specified VLAN if the RADIUS server is unavailable to reauthenticate the supplicant. (The VLAN must already exist on the switch.) Related Documentation • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 2357 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2358 CHAPTER 85 Configuration Statements for Access Control • [edit access] Configuration Statement Hierarchy on page 2359 • [edit ethernet-switching-options] Configuration Statement Hierarchy on page 2359 • [edit protocols] Configuration Statement Hierarchy on page 2362 [edit access] Configuration Statement Hierarchy access { profileprofile-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 ]; } } } Related Documentation • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 [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); } 2359 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS egress { interface (all | interface-name); } output { interface interface-name; 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 name { interface interface-name ; } } secure-access-port { 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 ); 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 ); dhcp-option82 { circuit-id { prefix hostname; use-interface-description; use-vlan-id; 2360 Chapter 85: Configuration Statements for Access Control } remote-id { prefix hostname | mac | none; use-interface-description; use-string string; } vendor-id [string]; } (examine-dhcp | no-examine-dhcp ); (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-unknown-unicast; } } 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 ; } } } Related Documentation • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 2361 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [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; 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); } } gvrp { ; interface (all | [interface-name]) { disable; } join-timer millseconds; leave-timer milliseconds; leaveall-timer milliseconds; } igmp-snooping { traceoptions { file filename ; flag flag (detail | disable | receive | send); } vlan (vlan-id | vlan-number) { data-forwarding { source { 2362 Chapter 85: Configuration Statements for Access Control 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 { 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; } lldp-configuration-notification-interval seconds; management-address ip-management-address; ptopo-configuration-maximum-hold-time seconds; ptopo-configuration-trap-interval seconds; traceoptions { file filename ; flag flag (detail | disable | receive | send); } } 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; } 2363 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } } } } 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } 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; 2364 Chapter 85: Configuration Statements for Access Control 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); 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; } 2365 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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; alarm; } 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 { 2366 Chapter 85: Configuration Statements for Access Control 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; } traceoptions { file filename ; flag flag; } 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 { alarm; block; } cost cost; disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; 2367 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions { file filename ; flag flag; } } } } Related Documentation 2368 • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding MAC RADIUS Authentication on J-EX Series Switches • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Ethernet OAM Connectivity Fault Management for a J-EX Series Switch on page 3463 • Understanding Ethernet OAM Link Fault Management for a J-EX Series Switch on page 3427 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding How to Use sFlow Technology for Network Monitoring on a J-EX Series Switch on page 3283 • Understanding VSTP for J-EX Series Switches on page 1281 Chapter 85: Configuration Statements for Access Control access Syntax Hierarchy Level Release Information Description access { profile profile-name { authentication-order [ldap radius | none]; accounting { order [radius | none]; accounting-stop-on-access-deny; accounting-stop-on-failure; } radius { accounting-server [server-addresses]; authentication-server [server-addresses]; } } } [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure authentication, authorization, and accounting (AAA) services. The statements are explained separately. Default Required Privilege Level Related Documentation Not enabled admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 2369 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS accounting Syntax Hierarchy Level Release Information Description Default Options accounting { order radius | none; accounting-stop-on-access-deny; accounting-stop-on-failure; } } [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the authentication order for authentication, authorization, and accounting (AAA) services. Not enabled none—Use no authentication for specified subscribers. radius—Use RADIUS authentication for specified subscribers. The remaining statements are explained separately. Required Privilege Level Related Documentation 2370 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Understanding 802.1X and RADIUS Accounting on J-EX Series Switches on page 2260 Chapter 85: Configuration Statements for Access Control accounting (Access Profile) Syntax Hierarchy Level Release Information Description accounting { accounting-stop-on-access-deny; accounting-stop-on-failure; coa-immediate-update; immediate-update; order [ accounting-method ]; statistics (time | volume-time); update-interval minutes; } [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS accounting parameters and enable RADIUS accounting for an access profile. The remaining statements are explained separately. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Authentication and Accounting Parameters for Subscriber Access • Configuring How Accounting Statistics Are Collected for Subscriber Access 2371 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS accounting Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2372 accounting { events [ login change-log interactive-commands ]; destination { radius { server { server-address { accounting-port port-number; secret password; source-address address; retry number; timeout seconds; } } } tacplus { server { server-address { port port-number; secret password; single-connection; timeout seconds; } } } } } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure audit of TACACS+ or RADIUS authentication events, configuration changes, and interactive commands. The remaining statements are explained separately. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS System Accounting • Configuring TACACS+ System Accounting Chapter 85: Configuration Statements for Access Control accounting-port Syntax Hierarchy Level Release Information Description Options accounting-port port-number; [edit system accounting destination radius server server-address], [edit system radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the accounting port number on which to contact the RADIUS server. number—Port number on which to contact the RADIUS server. Default: 1813 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication • Configuring RADIUS System Accounting accounting-server Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation accounting-server [server-addresses]; [edit access profile profile-name radius] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Remote Authentication Dial-In User Service (RADIUS) server for authentication. To configure multiple RADIUS servers, include multiple server addresses. The servers are tried in order and in a round-robin fashion until a valid response is received from one of the servers or until all the configured retry limits are reached. Not enabled server-addresses—One or more addresses of RADIUS authentication servers. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • show network-access aaa statistics authentication on page 2506 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Understanding 802.1X and RADIUS Accounting on J-EX Series Switches on page 2260 2373 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS accounting-session-id-format Syntax Hierarchy Level Release Information Description Default Options accounting-session-id-format (decimal | description); [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the format the router or switch uses to identify the accounting session. decimal decimal—Use the decimal format. description—Use the generic format, in the form: jnpr interface-specifier:subscriber-session-id. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring Authentication and Accounting Parameters for Subscriber Access accounting-stop-on-access-deny Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 2374 accounting-stop-on-access-deny; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configures the authentication order for authentication, authorization, and accounting (AAA) services to send an Acct-Stop message if the AAA server denies access to a supplicant. Not enabled admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • show network-access aaa statistics authentication on page 2506 Chapter 85: Configuration Statements for Access Control accounting-stop-on-access-deny Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation accounting-stop-on-access-deny; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS accounting to send an Acct-Stop message when the AAA server refuses a client request for access. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Authentication and Accounting Parameters for Subscriber Access accounting-stop-on-failure Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation accounting-stop-on-failure; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure authentication order for authentication, authorization, and accounting (AAA) services to send an Acct-Stop message if a supplicant fails AAA authorization, but the RADIUS server grants access. For example, a supplicant might fail AAA authentication due to an internal error such as a timeout. Not enabled admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Understanding 802.1X and RADIUS Accounting on J-EX Series Switches on page 2260 2375 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS accounting-stop-on-failure Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation accounting-stop-on-failure; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS accounting to send an Acct-Stop message when client access fails AAA but the AAA server grants access. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Authentication and Accounting Parameters for Subscriber Access address Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2376 address address-or-prefix; [edit access address-pool pool-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the IP address or prefix value for clients. address-or-prefix—An address or prefix value. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Address Pool for L2TP Network Server IP Address Allocation Chapter 85: Configuration Statements for Access Control address-pool Syntax Hierarchy Level Release Information Description Options address-pool pool-name { address address-or-prefix; address-range ; } [edit access] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Allocate IP addresses for clients. pool-name—Name assigned to an address pool. The remaining statements are explained separately. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Address Pool for L2TP Network Server IP Address Allocation address-range Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation address-range ; [edit access address-pool pool-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the address range. • high upper-limit—Upper limit of an address range. • low lower-limit—Lower limit of an address range. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Address Pool for L2TP Network Server IP Address Allocation 2377 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS advertisement-interval Syntax Hierarchy Level Release Information Description Default Options advertisement-interval seconds; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For switches configured for Link Layer Discovery Protocol, configure the frequency at which LLDP advertisements are sent. Disabled. seconds—(Optional) The number of seconds. Range: 5 through 32,768 seconds Default: 30 seconds Required Privilege Level Related Documentation 2378 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Chapter 85: Configuration Statements for Access Control attributes Syntax Hierarchy Level Release Information Description attributes { exclude { accounting-authentic [ accounting-on | accounting-off ]; accounting-delay-time [ accounting-on | accounting-off ]; accounting-session-id [ access-request | accounting-on | accounting-off | accounting-stop ]; accounting-terminate-cause [ accounting-off ]; called-station-id [ access-request | accounting-start | accounting-stop ]; calling-station-id [ access-request | accounting-start | accounting-stop ]; class [ accounting-start | accounting-stop ]; dhcp-gi-address [ access-request | accounting-start | accounting-stop ]; dhcp-mac-address [ access-request | accounting-start | accounting-stop ]; output-filter [ accounting-start | accounting-stop ]; event-timestamp [ accounting-on | accounting-off | accounting-start | accounting-stop ]; framed-ip-address [ accounting-start | accounting-stop ]; framed-ip-netmask [ accounting-start | accounting-stop ]; input-filter [ accounting-start | accounting-stop ]; input-gigapackets [ accounting-stop ]; input-gigawords [ accounting-stop ]; interface-description [ access-request | accounting-start | accounting-stop ]; nas-identifier [ access-request | accounting-on | accounting-off | accounting-start | accounting-stop ]; nas-port [ access-request | accounting-start | accounting-stop ]; nas-port-id [ access-request | accounting-start | accounting-stop ]; nas-port-type [ access-request | accounting-start | accounting-stop ]; output-gigapackets [ accounting-stop ]; output-gigawords [ accounting-stop ]; } ignore { framed-ip-netmask; input-filter; logical-system-routing-instance; output-filter; } } [edit access profile profile-name radius] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how the router or switch processes RADIUS attributes. The statements are explained separately. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring How RADIUS Attributes Are Used for Subscriber Access 2379 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-order Syntax Hierarchy Level Release Information Description Default Options authentication-order [ldap radius | none]; [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the order of authentication, authorization, and accounting (AAA) servers to use while sending authentication messages. Not enabled ldap—Lightweight Directory Access Protocol. none—No authentication for specified subscribers. radius—Remote Authentication Dial-In User Service authentication. Required Privilege Level Related Documentation 2380 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 Chapter 85: Configuration Statements for Access Control authentication-order Syntax Hierarchy Level Release Information Description Default Options authentication-order [ authentication-methods ]; [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the order in which the Junos OS tries different authentication methods when verifying that a client can access the router or switch. For each login attempt, the software tries the authentication methods in order, from first to last. password password—Verify the client using the information configured at the [edit access profile profile-name client client-name] hierarchy level. radius—Verify the client using RADIUS authentication services. NOTE: For subscriber access management, you must always specify the radius method. Subscriber access management does not support the password keyword (the default), and authentication fails when no method is specified. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Specifying the Authentication and Accounting Methods for Subscriber Access • Configuring Access Profiles for L2TP or PPP Parameters • Example: Configuring CHAP Authentication with RADIUS 2381 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-profile-name Syntax Hierarchy Level Release Information Description Default Options authentication-profile-name access-profile-name; [edit protocols dot1x authenticator], [edit services captive-portal] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the name of the access profile to be used for 802.1X, MAC RADIUS, or captive portal authentication. No access profile is specified. access-profile-name—Name of the access profile. The access profile is configured at the [edit access profile] hierarchy level and contains the RADIUS server IP address and other information used for authentication. Required Privilege Level Related Documentation 2382 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 Chapter 85: Configuration Statements for Access Control authentication-server Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation authentication-server [server-addresses]; [edit access profile profile-name radius] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Remote Authentication Dial-In User Service (RADIUS) server for authentication. To configure multiple RADIUS servers, include multiple server addresses. The servers are tried in order and in a round-robin fashion until a valid response is received from one of the servers or until all the configured retry limits are reached. Not enabled server-addresses —Configure one or more RADIUS server addresses. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • show network-access aaa statistics authentication on page 2506 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 authentication-whitelist Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation authentication-whitelist { mac-address { interface interface-name; vlan-assignment ( vlan-id |vlan-name); } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure MAC addresses for which RADIUS authentication is to be bypassed. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 2383 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authenticator Syntax Hierarchy Level Release Information Description authenticator { authentication-profile-name access-profile-name; interface (all | [ interface-names ]) { disable; guest-vlan ( vlan-id | vlan-name); mac-radius ; maximum-requests number; no-reauthentication; quiet-period seconds; 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 (single | single-secure | multiple); supplicant-timeout seconds; transmit-period seconds; } static mac-address { interface interface-name; vlan-assignment vlan-identifier; } } [edit protocols dot1x] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an authenticator for 802.1X authentication. The statements are explained separately. Default Required Privilege Level Related Documentation 2384 No static MAC address or VLAN is configured. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Specifying RADIUS Server Connections on a J-EX Series Switch (CLI Procedure) on page 2330 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Understanding Static MAC Bypass of Authentication on J-EX Series Switches Chapter 85: Configuration Statements for Access Control captive-portal Syntax Hierarchy Level Release Information Description captive-portal { authentication-profile-name authentication-profile-name custom-options { banner-message string; footer-bgcolor color; footer-message string; form-header-bgcolor color; form-header-message string; form-reset-label label name; form-submit-label label name; header-bgcolor color; header-logo filename; header-message string; post-authentication-url url-string; } interface (all | [interface-names]) { quiet-period seconds; retries number-of-retries; server-timeout seconds; reauthentication-timeout seconds; supplicant (multiple | single | single-secure); } secure-authentication (http | https); } [edit services] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure captive portal to authenticate clients connected to the switch for access to the network. The remaining statements are explained separately. Default Required Privilege Level Related Documentation Captive portal is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Designing a Captive Portal Authentication Login Page on a J-EX Series Switch on page 2351 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 2385 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ca-type Syntax Hierarchy Level Release Information Description ca-type { number { ca-value value; } } [edit protocols lldp-med interface (all | interface-name location civic-based)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Device (LLDP-MED), configure the address elements. These elements are included in the location information to be advertised from the switch to the MED. This information is used during emergency calls to identify the location of the MED. For further information about the values that can be used to comprise the location,, refer to RFC 4776, Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information. A subset of those values is provided below. The ca-value statement is explained separately. Default Options Required Privilege Level Related Documentation 2386 Disabled. value—Civic address elements that represent the civic or postal address. Values are: • 0—A code that specifies the language used to describe the location. • 16—The leading-street direction, such as “N”. • 17—A trailing street suffix, such as “SW”. • 18—A street suffix or type, such as “Ave” or “Platz”. • 19—A house number, such as “6450”. • 20—A house-number suffix, such as “A” or “1/2”. • 21—A landmark, such as “Stanford University”. • 22—Additional location information, such as “South Wing”. • 23—The name and occupant of a location, such as “Carrillo's Holiday Market”. • 24—A house-number suffix, such as “95684”. • 25—A building structure, such as “East Library”. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 Chapter 85: Configuration Statements for Access Control • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 ca-value Syntax Hierarchy Level Release Information Description ca-value value; [edit protocols lldp-med interface (all | interface-name ) location civic-based ca-type number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Device (LLDP-MED), configure location information, such as street address and city, that is indexed by the ca-type code. This information is advertised from the switch to the MED and is used during emergency calls to identify the location of the MED. Default Disabled. Options value—Specify a value that correlates to the ca-type. See ca-type for a list of codes and suggested values. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 2387 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS civic-based Syntax Hierarchy Level Release Information Description civic-based { what number; country-code code; ca-type { number { ca-value value; } } } [edit protocols lldp-med interface (all | interface-name) location] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED), configure the geographic location to be advertised from the switch to the MED. This information is used during emergency calls to identify the location of the MED. The statements are explained separately. Default Required Privilege Level Related Documentation 2388 Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 Chapter 85: Configuration Statements for Access Control country-code Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation country-code code; [edit protocols lldp-med interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Device (LLDP-MED), configure the two-letter country code to include in the location information. Location information is advertised from the switch to the MED, and is used during emergency calls to identify the location of the MED. The country code is required when configuring LLDP-MED based on location. Disabled. code—Two-letter ISO 3166 country code in capital ASCII letters; for example, US or DE. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 2389 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS custom-options Syntax Hierarchy Level Release Information Description Options custom-options { banner-message string; footer-bgcolor color; footer-message string; form-header-bgcolor color; form-header-message string; form-reset-label label name; form-submit-label label name; header-bgcolor color; header-logo filename; header-message string; post-authentication-url url-string; } [edit services captive-portal] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the design elements of a captive portal login page. banner-message—The first screen displayed before the captive portal login page is displayed—for example, a disclaimer message. Range: 1–2047 characters footer-bgcolor —The hexadecimal color code for the color of the footer bar across the bottom of the captive portal login page—for example, #2E8B57 (sea green). Values: # symbol followed by six characters. footer-message—Text message displayed in the footer bar across the bottom of the captive portal login page. Range: 1–2047 characters form-header-bgcolor —The hexadecimal color code for the background color of the header bar across the top of the form area of the captive portal login page. Values: # symbol followed by six characters. form-header-message—Text message displayed in the header bar across the top of the form area of the captive portal login page. Range: 1–255 characters Default: Captive Portal User Authentication form-reset-label—Label displayed in the button that the user can select to clear the username and password fields on the form. Range: 1–255 characters Default: Reset form-submit-label —Label displayed in the button that the user selects to submit their login information—for example, Log In or OK. 2390 Chapter 85: Configuration Statements for Access Control Range: 1–255 characters Default: Log In header-bgcolor—The hexadecimal color code for the color of the header bar across the top of the captive portal login page. Values: # symbol followed by six characters. header-logo—Filename of the file containing the image of the logo displayed at the top of the captive portal login page. The image file can be in GIF, JPEG, or PNG format. header-message—Text displayed in the header bar across the bottom of the captive portal login page. Range: 1–2047 characters Default: User Authentication post-authentication-url—URL to which the users are directed upon successful authentication—for example www.mycafe.com. Range: 1–255 characters Default: The page originally requested by the user. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Designing a Captive Portal Authentication Login Page on a J-EX Series Switch on page 2351 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 2391 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS destination Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2392 destination { radius { server { server-address { accounting-port port-number; secret password; source-address address; retry number; timeout seconds; } } } tacplus { server { server-address { port port-number; secret password; single-connection; timeout seconds; } } } } [edit system accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the authentication server. The remaining statements are explained separately. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS System Accounting • Configuring TACACS+ System Accounting Chapter 85: Configuration Statements for Access Control disable Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation disable; [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable 802.1X authentication on a specified interface or all interfaces. 802.1X authentication is disabled on all interfaces. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 2393 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation disable; [edit protocols lldp], [edit protocols interface lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the LLDP configuration on the switch or on one or more interfaces. If you do not configure LLDP, it is disabled on the switch and on specific switch interfaces. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 disable Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 2394 disable; [edit protocols lldp-med], [edit protocols lldp-med interface] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the LLDP-MED configuration on the switch or on one or more interfaces. If you do not configure LLDP-MED, it is disabled on the switch and on specific switch interfaces. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Chapter 85: Configuration Statements for Access Control dot1x Syntax Hierarchy Level Release Information Description dot1x { authenticator { authentication-profile-name access-profile-name; interface (all | [ interface-names ]) { disable; guest-vlan (vlan-id | vlan-name); mac-radius ; maximum-requests number; no-reauthentication; quiet-period seconds; 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 (single | single-secure | multiple); supplicant-timeout seconds; transmit-period seconds; } static mac-address { interface interface-names; vlan-assignment (vlan-id |vlan-name); } } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure 802.1X authentication for Port-Based Network Access Control. 802.1X authentication is supported on interfaces that are members of private VLANs (PVLANs). The remaining statements are explained separately. Default Required Privilege Level Related Documentation 802.1X is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 2395 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 elin Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation 2396 elin number; [edit protocols lldp-med interface (all | interface-name location)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED), configure the Emergency Line Identification Number (ELIN) as location information. Location information is advertised from the switch to the MED device and is used during emergency calls to identify the location of the MED device. Disabled. number—Configure a 10-digit number (area code and telephone number). routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 Chapter 85: Configuration Statements for Access Control ethernet-port-type-virtual Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation ethernet-port-type-virtual; [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the physical port type the router or switch uses to authenticate clients. The router or switch passes a port type of ethernet in RADIUS attribute 61 (NAS-Port-Type) by default. This statement specifies a port type of virtual. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring RADIUS Server Parameters for Subscriber Access 2397 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ethernet-switching-options Syntax 2398 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; 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 name { interface interface-name ; interface interface-name; } } secure-access-port { dhcp-snooping-file { location local_pathname | remote_URL; timeout seconds; write-interval seconds; } interface (all | interface-name) { allowed-mac { mac-address-list; } Chapter 85: Configuration Statements for Access Control (dhcp-trusted | no-dhcp-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); 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); (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-unknown-unicast; } } 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 ; } } } 2399 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Hierarchy Level Release Information Description [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Ethernet switching options. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 events Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2400 events [events ]; [edit system accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the types of events to track and log. events—Event types; can be one or more of the following: • change-log—Audit configuration changes. • interactive-commands—Audit interactive commands (any command-line input). • login—Audit logins. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring TACACS+ System Accounting Chapter 85: Configuration Statements for Access Control exclude Syntax Hierarchy Level Release Information Description exclude { accounting-authentic [ accounting-on | accounting-off ]; accounting-delay-time [ accounting-on | accounting-off ]; accounting-session-id [ access-request | accounting-on | accounting-off | accounting-stop ]; accounting-terminate-cause [ accounting-off ]; called-station-id [ access-request | accounting-start | accounting-stop ]; calling-station-id [ access-request | accounting-start | accounting-stop ]; class [ accounting-start | accounting-stop ]; dhcp-gi-address [ access-request | accounting-start | accounting-stop ]; dhcp-mac-address [ access-request | accounting-start | accounting-stop ]; output-filter [ accounting-start | accounting-stop ]; event-timestamp [ accounting-on | accounting-off | accounting-start | accounting-stop ]; framed-ip-address [ accounting-start | accounting-stop ]; framed-ip-netmask [ accounting-start | accounting-stop ]; input-filter [ accounting-start | accounting-stop ]; input-gigapackets [ accounting-stop ]; input-gigawords [ accounting-stop ]; interface-description [ access-request | accounting-start | accounting-stop ]; nas-identifier [ access-request | accounting-on | accounting-off | accounting-start | accounting-stop ]; nas-port [ access-request | accounting-start | accounting-stop ]; nas-port-id [ access-request | accounting-start | accounting-stop ]; nas-port-type [ access-request | accounting-start | accounting-stop ]; output-gigapackets [ accounting-stop ]; output-gigawords [ accounting-stop ]; } [edit access profile profile-name radius attributes] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to exclude the specified attributes from the specified type of RADIUS message. Not all attributes are available in all types of RADIUS messages. By default, the router or switch includes the specified attributes in RADIUS Access-Request, Acct-On, Acct-Off, Acct-Start, and Acct-Stop messages. Options RADIUS attribute type—RADIUS attribute or Juniper Networks VSA number and name. • accounting-authentic—RADIUS attribute 45, Acct-Authentic. • accounting-delay-time—RADIUS attribute 41, Acct-Delay-Time. • accounting-session-id—RADIUS attribute 44, Acct-Session-Id. • accounting-terminate-cause—RADIUS attribute 49, Acct-Terminate-Cause. • called-station-id—RADIUS attribute 30, Called-Station-Id. • calling-station-id—RADIUS attribute 31, Calling-Station-Id. 2401 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • class—RADIUS attribute 25, Class. • dhcp-gi-address—Juniper VSA 26-57, DHCP-GI-Address. • dhcp-mac-address—Juniper VSA 26-56, DHCP-MAC-Address. • event-timestamp—RADIUS attribute 55, Event-Timestamp. • framed-ip-address—RADIUS attribute 8, Framed-IP-Address. • framed-ip-netmask—RADIUS attribute 9, Framed-IP-Netmask. • input-filter—Juniper VSA 26-10, Ingress-Policy-Name. • input-gigapackets—Juniper VSA 26-42, Acct-Input-Gigapackets. • input-gigawords—RADIUS attribute 52, Acct-Input-Gigawords. • interface-description—Juniper VSA 26-53, Interface-Desc. • nas-identifier—RADIUS attribute 32, NAS-Identifier. • nas-port—RADIUS attribute 5, NAS-Port. • nas-port-id—RADIUS attribute 87, NAS-Port-Id. • nas-port-type—RADIUS attribute 61, NAS-Port-Type. • output-filter—Juniper VSA 26-11, Egress-Policy-Name. • output-gigapackets—Juniper VSA 25-43, Acct-Output-Gigapackets. • output-gigawords—RADIUS attribute 53, Acct-Output-Gigawords. RADIUS message type Required Privilege Level Related Documentation 2402 • access-request—RADIUS Access-Accept messages. • accounting-off—RADIUS Accounting-Off messages. • accounting-on—RADIUS Accounting-On messages. • accounting-start—RADIUS Accounting-Start messages. • accounting-stop—RADIUS Accounting-Stop messages. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Parameters for Subscriber Access Chapter 85: Configuration Statements for Access Control fast-start Syntax Hierarchy Level Release Information Description Options fast-start count; [edit protocols lldp-med] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the number of Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) advertisements sent from the switch in the first second after it has detected an LLDP-MED device (such as an IP telephone). count—Number of advertisements. Range: 1 through 10 Default: 3 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 2403 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS forwarding-class Syntax Hierarchy Level Release Information Description forwarding-class < assured-forwarding | best-effort | expedited-forwarding |network-control >; [edit ethernet-switching-options voip interface Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches, configure the forwarding class used to handle packets on the VoIP interface. Default Disabled. Options class—Forwarding class: • assured-forwarding— Assured forwarding (AF)—Provides a group of values you can define and includes four subclasses: AF1, AF2, AF3, and AF4, each with three drop probabilities: low, medium, and high. • best-effort—Provides no service profile. For the best effort forwarding class, loss priority is typically not carried in a class-of-service (CoS) value, and random early detection (RED) drop profiles are more aggressive. • expedited-forwading—Provides a low loss, low latency, low jitter, assured bandwidth, end-to-end service. • Required Privilege Level Related Documentation 2404 network-control—Provides a typically high priority because it supports protocol control. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 Chapter 85: Configuration Statements for Access Control guest-vlan Syntax Hierarchy Level Release Information Description Default Options guest-vlan (vlan-id | vlan-name); [edit protocols dot1x authenticator interface (all | [interface-names ])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the VLAN to which an interface is moved when no 802.1X supplicants are connected on the interface. The VLAN specified must already exist on the switch. None vlan-id—VLAN tag identifier of the guest VLAN. vlan-name—Name of the guest VLAN. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Understanding Guest VLANs for 802.1X on J-EX Series Switches on page 2259 2405 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS hold-multiplier Syntax Hierarchy Level Release Information Description Default Options hold-multiplier number; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the multiplier used in combination with the advertisement-interval value to determine the length of time LLDP information is held before it is discarded. The default value is 4 (or 120 seconds). Disabled. number—A number used as a multiplier. Range: 2 through 10 Default: 4 (or 120 seconds) Required Privilege Level Related Documentation 2406 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Chapter 85: Configuration Statements for Access Control ignore Syntax Hierarchy Level Release Information Description Options ignore { framed-ip-netmask; input-filter; logical-system-routing-instance; output-filter; } [edit access profile profile-name radius attributes] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to ignore the specified attributes in RADIUS Access-Accept messages. By default, the router or switch processes the attributes it receives from the external server. framed-ip-netmask—Framed-IP-Netmask (RADIUS attribute 9). input-filter—Ingress-Policy-Name (VSA 26-10). logical-system-routing-instance—Virtual-Router (VSA 26-1). output-filter—Egress-Policy-Name (VSA 26-11). Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Parameters for Subscriber Access immediate-update Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation immediate-update; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to send an Acct-Update message to the RADIUS accounting server on receipt of a response (for example, an ACK or timeout) to the Acct-Start message. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Parameters for Subscriber Access • Configuring How Accounting Statistics Are Collected for Subscriber Access 2407 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Options interface (all | [ interface-names ]) { disable; guest-vlan (vlan-name | vlan-id); mac-radius ; maximum-requests number; no-reauthentication; quiet-period seconds; 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 (single | single-secure | multiple); supplicant-timeout seconds; transmit-period seconds; } [edit protocols dot1x authenticator] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure 802.1X authentication for Port-Based Network Access Control for all interfaces or for specific interfaces. all—Configure all interfaces for 802.1X authentication. [ interface-names ]— List of names of interfaces to configure for 802.1X authentication. The remaining statements are explained separately. Required Privilege Level Related Documentation 2408 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on a J-EX Series Switch on page 2276 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 Chapter 85: Configuration Statements for Access Control interface-description-format Syntax Hierarchy Level Release Information Description Options interface-description-format (adapter | sub-interface ); [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the information that is included in or omitted from the interface description that the router or switch passes to RADIUS for inclusion in the RADIUS attribute 87 (NAS-Port-Id). By default, the router or switch includes both the subinterface and the adapter in the interface description. adapter—Include only the adapter in the interface description. sub-interface—Include only the subinterface in the interface description. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring RADIUS Server Parameters for Subscriber Access 2409 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface (Captive Portal) Syntax Hierarchy Level Release Information Description Options interface (all | [interface-names]) { quiet-period seconds; reauthentication-timeout seconds; retries number-of-retries; server-timeout seconds; supplicant ( multiple | single | single-secure); } [edit service captive-portal] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure captive portal authentication for all interfaces or for specific interfaces. all—All interfaces to be configured for captive portal authentication. [interface-names]—List of names of interfaces to be configured for captive portal authentication. The remaining statements are explained separately. Required Privilege Level Related Documentation 2410 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 Chapter 85: Configuration Statements for Access Control interface Syntax Hierarchy Level Release Information Description Default Options interface (all | interface-name) { disable; } [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Link Layer Discovery Protocol (LLDP) on all interfaces or on a specific interface. None all—All interfaces on the switch. interface-name—Name of a specific interface. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 2411 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Default Options interface (all | interface-name) { disable; location { elin number; civic-based { what number; country-code code; ca-type { number { ca-value value; } } } } } [edit protocols lldp-med] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) on all interfaces or on a specific interface. Not enabled all—All interfaces on the switch. interface-name—Name of a specific interface. The remaining statements are explained separately. Required Privilege Level Related Documentation 2412 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Chapter 85: Configuration Statements for Access Control interface Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation interface [interface-names]; [edit protocols dot1x authenticator authentication-profile-name static mac-address], [edit ethernet-switching-options authentication-whitelist ] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure interfaces on which the specified MAC addresses are allowed to bypass RADIUS authentication and allowed to connect to the LAN without authentication. interface-names—List of interfaces. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x static-mac-address on page 2484 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Understanding Static MAC Bypass of Authentication on J-EX Series Switches • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 2413 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Options interface (all | [interface-name] | access-ports) { vlan vlan-name ); forwarding-class ; } [edit ethernet-switching-options voip] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable voice over IP (VoIP) for all interfaces or specific interfaces. all | interface-name | access-ports—Enable VoIP on all interfaces, on a specific interface, or on all access ports. Required Privilege Level Related Documentation 2414 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 Chapter 85: Configuration Statements for Access Control lldp Syntax Hierarchy Level Release Information Description lldp { disable; advertisement-interval seconds; fast-start number; hold-multiplier number; interface (all | [interface-name]) { disable; } lldp-configuration-notification-interval seconds; management-address ip-management-address; ptopo-configuration-maximum-hold-time seconds; ptopo-configuration-trap-interval seconds; traceoptions { file filename ; flag flag (detail | disable | receive | send); } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Link Layer Discovery Protocol (LLDP). The switch uses LLDP to advertise its identity and capabilities on a LAN, as well as receive information about other network devices. LLDP is defined in the IEEE standard 802.1AB-2005. The statements are explained separately. Default Required Privilege Level Related Documentation LLDP is enabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 2415 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS lldp-configuration-notification-interval Syntax Hierarchy Level Release Information Description Default Options lldp-configuration-notification-interval seconds; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how often SNMP trap notifications are generated as a result of LLDP database changes. If the interval value is 0, trap notifications of database changes are disabled. SNMP trap notifications of LLDP database changes are disabled. seconds—Interval between trap notifications about LLDP database changes. Range: 0 through 3600 Required Privilege Level Related Documentation 2416 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 Chapter 85: Configuration Statements for Access Control lldp-med Syntax Hierarchy Level Release Information Description 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; } } } } } } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Link Layer Discovery Protocol–Media Endpoint Discovery. LLDP-MED is an extension of LLDP. The switch uses LLDP-MED to support device discovery of VoIP telephones and to create location databases for these telephone locations for emergency services. LLDP-MED is defined in the standard ANSI/TIA-1057 by the Telecommunications Industry Association (TIA). The statements are explained separately. Default Required Privilege Level Related Documentation Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 2417 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS location Syntax Hierarchy Level Release Information Description location { elin number; civic-based { what number; country-code code; ca-type{ number { ca-value value; } } } } [edit protocols lldp-med interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED), configure the location information. Location information is advertised from the switch to the MED. This information is used during emergency calls to identify the location of the MED. The statements are explained separately. Default Required Privilege Level Related Documentation 2418 Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 Chapter 85: Configuration Statements for Access Control mac-radius Syntax Hierarchy Level Release Information Description mac-radius ; [edit protocols dot1x authenticator interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure MAC RADIUS authentication for specific interfaces. MAC RADIUS authentication allows LAN access to permitted MAC addresses. When a new MAC address appears on an interface, the switch consults the RADIUS server to check whether the MAC address is a permitted address. If the MAC address is configured on the RADIUS server, the device is allowed access to the LAN. If MAC RADIUS is configured, the switch first tries to get a response from the host for 802.1X authentication. If the host is unresponsive, the switch attempts to authenticate using MAC RADIUS. To restrict authentication to MAC RADIUS only, use the restrict option. In restrictive mode, all 802.1X packets are eliminated and the attached device on the interface is considered a nonresponsive host. Options flap-on-disconnect—(Optional) When the RADIUS server sends a disconnect message to a supplicant, the switch resets the interface on which the supplicant is authenticated. If the interface is configured for multiple supplicant mode, the switch resets all the supplicants on the specified interface. This option takes effect only when the restrict option is also set. restrict—(Optional) Restricts authentication to MAC RADIUS only. When mac-radius restrict is configured the switch drops all 802.1X packets. This option is useful when no other 802.1X authentication methods, such as guest VLAN, are needed on the interface, and eliminates the delay that occurs while the switch determines that a connected device is a non-802.1X-enabled host. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Configuring MAC RADIUS Authentication (CLI Procedure) on page 2335 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Understanding MAC RADIUS Authentication on J-EX Series Switches 2419 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS management-address Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation management-address ip-management-address; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the management address of the switch to be used in the LLDP Management type, length, and value (TLV) . LLDP Management TLV uses the IP address of the switch's management Ethernet interface (me0) or the IP address of the virtual management Ethernet (VME) interface if the switch is a Virtual Chassis. ip-management-address—Management address for the switch. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • J-EX Series Switches Interfaces Overview on page 863 maximum-requests Syntax Hierarchy Level Release Information Description Default Options maximum-requests number; [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, configure the maximum number of times an EAPOL request packet is retransmitted to the supplicant before the authentication session times out. Two retransmission attempts number—Number of retransmission attempts. Range: 1 through 10 Default: 2 Required Privilege Level Related Documentation 2420 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 Chapter 85: Configuration Statements for Access Control nas-identifier Syntax Hierarchy Level Release Information Description Options nas-identifier identifier-value; [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the value for the client RADIUS attribute 32 (NAS-Identifier). This attribute is used for authentication and accounting requests. identifier-value—String to use for authentication and accounting requests. Range: 1 to 64 characters Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin–control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring RADIUS Server Parameters for Subscriber Access 2421 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS nas-port-extended-format Syntax Hierarchy Level Release Information Description Options nas-port-extended-format { adapter-width width; port-width width; slot-width width; stacked-vlan-width width; vlan-width width; } [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the RADIUS client to use the extended format for RADIUS attribute 5 (NAS-Port) and specify the width of the fields in the NAS-Port attribute. adapter-width width—Number of bits in the adapter field. port-width width—Number of bits in the port field. slot-width width—Number of bits in the slot field. stacked-vlan-width width—Number of bits in the SVLAN ID field. vlan-width width—Number of bits in the VLAN ID field. Required Privilege Level Related Documentation 2422 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring RADIUS Server Parameters for Subscriber Access Chapter 85: Configuration Statements for Access Control no-reauthentication Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation no-reauthentication; [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, disables reauthentication. Not disabled routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Understanding Authentication onJ-EX Series Switches on page 2248 2423 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS options Syntax Hierarchy Level Release Information Description options { accounting-session-id-format (decimal | description); client-accounting-algorithm (direct | round-robin); client-authentication-algorithm (direct | round-robin); ethernet-port-type-virtual; interface-description-format [sub-interface | adapter]; nas-identifier identifier-value; nas-port-extended-format { adapter-width width; port-width width; slot-width width; stacked-vlan-width width; vlan-width width; } revert-interval interval; vlan-nas-port-stacked-format; } [edit access profile profile-name radius] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the options used by RADIUS authentication and accounting servers. The statements are explained separately. Required Privilege Level Related Documentation 2424 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Parameters for Subscriber Access • RADIUS Server Options for Subscriber Access Chapter 85: Configuration Statements for Access Control order Syntax Hierarchy Level Release Information Description Default Options order [radius | none]; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the order of authentication, authorization, and accounting (AAA) servers to use while sending accounting messages and updates. Not enabled none—No accounting for specified subscribers. radius—Remote Authentication Dial-In User Service accounting for specified subscribers. [ radius | none ]— Use multiple types of accounting in the order specified. RADIUS accounting is initially used. However, if RADIUS servers are not available, no accounting is done. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 order Syntax Hierarchy Level Release Information order [ accounting-method ]; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Set the order in which the Junos OS tries different accounting methods for client activity. When a client logs in, the software tries the accounting methods in the specified order. Options accounting-method—One or more accounting methods. When a client logs in, the software tries the accounting methods in the following order, from first to last. The only valid value is radius for RADIUS accounting. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Authentication and Accounting Parameters for Subscriber Access 2425 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS port Syntax Hierarchy Level Release Information port port-number; [edit access radius-server server-address], [edit access profile profile-name radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the port number on which to contact the RADIUS server. Options port-number—Port number on which to contact the RADIUS server. Default: 1812 (as specified in RFC 2865) Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring Router or Switch Interaction with RADIUS Servers • Configuring Authentication and Accounting Parameters for Subscriber Access port (RADIUS Server) Syntax Hierarchy Level Release Information Description Options port port-number; [edit system radius-server address], [edit system accounting destination radius server address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the port number on which to contact the RADIUS server. number—Port number on which to contact the RADIUS server. Default: 1812 (as specified in RFC 2865) Required Privilege Level Related Documentation 2426 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication Chapter 85: Configuration Statements for Access Control port (TACACS+ Server) Syntax Hierarchy Level Release Information Description Options port port-number; [edit system accounting destination tacplus server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the port number on which to contact the TACACS+ server. number—Port number on which to contact the TACACS+ server. Default: 49 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring TACACS+ System Accounting 2427 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS profile Syntax Hierarchy Level Release Information Description Default Options profile profile-name { accounting { order [radius | none]; accounting-stop-on-access-deny; accounting-stop-on-failure; } authentication-order [authentication-method]; radius { accounting-server [server-addresses]; authentication-server [server-addresses]; } } [edit access] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an access profile. The access profile contains the entire authentication, authorization, and accounting (AAA) configuration that aids in handling AAA requests, including the authentication method and order, AAA server addresses, and AAA accounting. Not enabled profile-name —Profile name of up to 32 characters. The remaining statements are explained separately. Required Privilege Level Related Documentation 2428 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 Chapter 85: Configuration Statements for Access Control ptopo-configuration-maximum-hold-time Syntax Hierarchy Level Release Information Description Options ptopo-configuration-maximum-hold-time seconds; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure how long to maintain the physical topology database entries. The physical topology identifies the devices on the network and their physical interconnections. seconds—Time to maintain physical topology database entries. Default: 300 Range: 1 through 2147483647 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 ptopo-configuration-trap-interval Syntax Hierarchy Level Release Information Description Default Options ptopo-configuration-trap-interval seconds; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how often SNMP trap notifications are sent regarding changes in physical topology global statistics. SNMP trap notifications of changes in physical topology global statistics are disabled. seconds—Interval between SNMP trap notifications about physical topology global statistics. Range: 0 through 3600 Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 2429 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS quiet-period Syntax Hierarchy Level Release Information Description Default Options quiet-period seconds; [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, configure the number of seconds the interface remains in the wait state following a failed authentication attempt by a supplicant before reattempting authentication. 60 seconds seconds—Number of seconds the interface remains in the wait state. Range: 0 through 65,535 seconds Default: 60 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show network-access aaa statistics authentication on page 2506 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 quiet-period (Captive Portal) Syntax Hierarchy Level Release Information Description Options quiet-period seconds; [edit services captive-portal interface (all | interface-names)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure time, in seconds, after a user exceeds the maximum number of retries before they can attempt to authenticate. seconds—Number of seconds. Range: 1–65535 Default: 60 Required Privilege Level Related Documentation 2430 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 Chapter 85: Configuration Statements for Access Control radius Syntax Hierarchy Level Release Information Description radius { accounting-server [server-addresses]; authentication-server [server-addresses]; } [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Remote Authentication Dial-In User Service (RADIUS) servers for authentication and for accounting. To configure multiple RADIUS servers, include multiple radiusstatements. The servers are tried in order and in a round-robin fashion until a valid response is received from one of the servers or until all the configured retry limits are reached. The statements are explained separately. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 2431 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS radius (Access Profile) Syntax 2432 radius { accounting-server [ ip-address ]; attributes { exclude accounting-authentic [ accounting-on | accounting-off ]; accounting-delay-time [ accounting-on | accounting-off ]; accounting-session-id [ access-request | accounting-on | accounting-off | accounting-stop ]; accounting-terminate-cause [ accounting-off ]; called-station-id [ access-request | accounting-start | accounting-stop ]; calling-station-id [ access-request | accounting-start | accounting-stop ]; class [ accounting-start | accounting-stop ]; dhcp-gi-address [ access-request | accounting-start | accounting-stop ]; dhcp-mac-address [ access-request | accounting-start | accounting-stop ]; output-filter [ accounting-start | accounting-stop ]; event-timestamp [ accounting-on | accounting-off | accounting-start | accounting-stop ]; framed-ip-address [ accounting-start | accounting-stop ]; framed-ip-netmask [ accounting-start | accounting-stop ]; input-filter [ accounting-start | accounting-stop ]; input-gigapackets [ accounting-stop ]; input-gigawords [ accounting-stop ]; interface-description [ access-request | accounting-start | accounting-stop ]; nas-identifier [ access-request | accounting-on | accounting-off | accounting-start | accounting-stop ]; nas-port [ access-request | accounting-start | accounting-stop ]; nas-port-id [ access-request | accounting-start | accounting-stop ]; nas-port-type [ access-request | accounting-start | accounting-stop ]; output-gigapackets [ accounting-stop ]; output-gigawords [ accounting-stop ]; } ignore { framed-ip-netmask; input-filter; logical-system-routing-instance; output-filter; } } authentication-server [ ip-address ]; options { accounting-session-id-format (decimal | description); client-accounting-algorithm (direct | round-robin); client-authentication-algorithm (direct | round-robin); ethernet-port-type-virtual; interface-description-format [sub-interface | adapter]; nas-identifier identifier-value; nas-port-extended-format { adapter-width width; port-width width; slot-width width; stacked-vlan-width width; vlan-width width; Chapter 85: Configuration Statements for Access Control } revert-interval interval; vlan-nas-port-stacked-format; } } Hierarchy Level Release Information Description [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the RADIUS parameters that the router uses for AAA authentication and accounting for subscribers. The statements are explained separately. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Parameters for Subscriber Access • RADIUS Server Options for Subscriber Access radius Syntax Hierarchy Level Release Information Description Options radius { server { server-address { accounting-port port-number; secret password; source-address address; retry number; timeout seconds; } } } [edit system accounting destination] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the RADIUS accounting server. server-address—Address of the RADIUS accounting server. 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 RADIUS System Accounting 2433 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS radius-server Syntax Hierarchy Level Release Information Description radius-server server-address { accounting-port port-number; port port-number; retry attempts; routing-instance routing-instance-name; secret password; source-address source-address; timeout seconds; } [edit access], [edit access profile profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS for subscriber access management, L2TP, or PPP. To configure multiple RADIUS servers, include multiple radius-server statements. The servers are tried in order and in a round-robin fashion until a valid response is received from one of the servers or until all the configured retry limits are reached. Options server-address—Address of the RADIUS authentication server. The remaining statements are explained separately. Required Privilege Level Related Documentation 2434 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication for L2TP • Configuring the PPP Authentication Protocol • Configuring RADIUS Authentication • Configuring Authentication and Accounting Parameters for Subscriber Access Chapter 85: Configuration Statements for Access Control reauthentication Syntax Hierarchy Level Release Information Description Default Options reauthentication { interval seconds; } [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, specify reauthentication parameters. 3600 seconds. disable—Disables the periodic reauthentication of the supplicant. interval seconds —Sets the periodic reauthentication time interval. The range is 1 through 65,535 seconds. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Understanding Authentication on J-EX Series Switches on page 2248 2435 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS retries Syntax Hierarchy Level Release Information Description Default Options retries number; [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, configure the number of times the switch attempts to authenticate the port after an initial failure. The port remains in a wait state during the quiet period after the authentication attempt. 3 retries number —Number of retries. Range: 1 through 10 Default: 3 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Understanding Authentication on J-EX Series Switches on page 2248 retries (Captive Portal) Syntax Hierarchy Level Release Information Description Options retries number-of-tries; [edit services captive-portal interface (all | interface-names)] ] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the number of times the user can attempt to submit authentication information. number-of-tries—Number of authentication attempts by user. Range: 1–65535 Default: 3 Required Privilege Level Related Documentation 2436 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 Chapter 85: Configuration Statements for Access Control retry Syntax Hierarchy Level Release Information retry attempts; [edit access radius-server server-address], [edit access profile profile-name radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Specify the number of times that the router or switch is allowed to attempt to contact a RADIUS authentication or accounting server. Options attempts—Number of times that the router is allowed to attempt to contact a RADIUS server. Range: 1 through 10 Default: 3 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring Authentication and Accounting Parameters for Subscriber Access • Configuring Router or Switch Interaction with RADIUS Servers • Example: Configuring CHAP Authentication with RADIUS • Configuring RADIUS Authentication for L2TP • timeout on page 2454 2437 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS retry Syntax Hierarchy Level Release Information Description Options retry number; [edit system radius-server server-address], [edit system accounting destination radius server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Number of times the router or switch is allowed to try to contact a RADIUS authentication or accounting server. number—Number of retries allowed for contacting a RADIUS server. Range: 1 through 10 Default: 3 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication • Configuring RADIUS System Accounting • timeout on page 2453 revert-interval Syntax Hierarchy Level Release Information Description Options revert-interval interval; [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the amount of time the router or switch waits after a server has become unreachable. The router or switch rechecks the connection to the server when the specified interval expires. If the server is then reachable, it is used in accordance with the order of the server list. interval—Amount of time to wait. Range: 0 through 4294967295 seconds Default: 60 seconds Required Privilege Level Related Documentation 2438 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring Authentication and Accounting Parameters for Subscriber Access Chapter 85: Configuration Statements for Access Control routing-instance Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation routing-instance routing-instance-name; [edit access radius-server server-address], [edit access profile profile-name radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the routing instance used to send RADIUS packets to the RADIUS server. routing-instance-name—Routing instance name. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the PPP Authentication Protocol • Configuring Authentication and Accounting Parameters for Subscriber Access secret Syntax Hierarchy Level Release Information Description Options secret password; [edit access profile profile-name radius-server server-address], [edit access radius-disconnect client-address], [edit access radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the password to use with the RADIUS server. The secret password used by the local router or switch must match that used by the server. password—Password to use; it can include spaces if the character string is enclosed 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 Authentication and Accounting Parameters for Subscriber Access • Configuring Router or Switch Interaction with RADIUS Servers • Example: Configuring CHAP Authentication with RADIUS • Configuring RADIUS Authentication for L2TP • Configuring the RADIUS Disconnect Server for L2TP 2439 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS secret Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation secret password; [edit system accounting destination radius server server-address], [edit system accounting destination tacplus server server-address], [edit system radius-server server-address], [edit system tacplus-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the password to use with the RADIUS or TACACS+ server. The secret password used by the local router or switch must match that used by the server. password—Password to use; can include spaces included in quotation marks. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication • Configuring TACACS+ Authentication • Configuring TACACS+ System Accounting • Configuring RADIUS System Accounting secure-authentication Syntax Hierarchy Level Release Information Description Default Options secure-authentication (http | https); [edit services captive-portal] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable HTTP or HTTPS access on the captive portal interface. http http—Enables HTTP access on the captive portal interface. https—Enables HTTPS access on the captive portal interface. HTTPS is recommended. Required Privilege Level Related Documentation 2440 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 Chapter 85: Configuration Statements for Access Control server (RADIUS Accounting) Syntax Hierarchy Level Release Information Description server { server-address { accounting-port port-number; retry number secret password; source-address address; timeout seconds; } } [edit system accounting destination radius] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS logging. 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 RADIUS System Accounting server (TACACS+ Accounting) Syntax Hierarchy Level Release Information Description server { server-address { port port-number; secret password; single-connection; timeout seconds; } } [edit system accounting destination tacplus] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure TACACS+ logging. 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 TACACS+ System Accounting 2441 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS server-fail Syntax Hierarchy Level Release Information Description server-fail (deny | permit | use-cache | vlan-id | vlan-name); [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches configured for 802.1X authentication, specify the server fail fallback action the switch takes when all RADIUS authentication servers are unreachable. When you specify the action vlan-name or vlan-id, the VLAN must already be configured on the switch. Default Options Authentication is denied. deny—Force fail the supplicant authentication. No traffic will flow through the interface. permit—Force succeed the supplicant authentication. Traffic will flow through the interface as if it were successfully authenticated by the RADIUS server. use-cache—Force succeed the supplicant authentication only if it was previously authenticated successfully. This action ensures that already authenticated supplicants are not affected. vlan-id—Move supplicant on the interface to the VLAN specified by this numeric identifier. This action is allowed only if it is the first supplicant connecting to the interface. If an authenticated supplicant is already connected, then the supplicant is not moved to the VLAN and is not authenticated. vlan-name—Move supplicant on the interface to the VLAN specified by this name. This action is allowed only if it is the first supplicant connecting to an interface. If an authenticated supplicant is already connected, then the supplicant is not moved to the VLAN and is not authenticated. Required Privilege Level Related Documentation 2442 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • Example: Configuring 802.1X Authentication Options When the RADIUS Server is Unavailable to a J-EX Series Switch on page 2271 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 Chapter 85: Configuration Statements for Access Control server-reject-vlan Syntax Hierarchy Level Release Information Description server-reject-vlan (vlan-id | vlan-name); [edit protocols dot1x authenticator interface (all | [interface-names])] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches configured for 802.1X authentication, specify that when the switch receives an Extensible Authentication Protocol Over LAN (EAPOL) Access-Reject message during the authentication process between the switch and the RADIUS authentication server, supplicants attempting access to the LAN are granted access and moved to a specific VLAN. Any VLAN name or VLAN ID sent by a RADIUS server as part of the EAPOL Access-Reject message is ignored. When you specify the VLAN ID or VLAN name, the VLAN must already be configured on the switch. Default Options None vlan-id —Numeric identifier of the VLAN to which the supplicant is moved. vlan-name—Name of the VLAN to which the supplicant is moved. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Configuring Server Fail Fallback (CLI Procedure) on page 2337 • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 2443 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS server-timeout Syntax Hierarchy Level Release Information Description Default Options server-timeout seconds; [edit protocols dot1x authenticator interface (all | [interface-name]) Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, configure the amount of time a port will wait for a reply when relaying a response from the supplicant to the authentication server before timing out and invoking the server-fail action. 30 seconds seconds —Number of seconds. Range: 1 through 60 seconds Default: 30 seconds Required Privilege Level Related Documentation 2444 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x on page 2477 • clear dot1x on page 2468 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • 802.1X for J-EX Series Switches Overview on page 2253 Chapter 85: Configuration Statements for Access Control server-timeout (Captive Portal) Syntax Hierarchy Level Release Information Description Options server-timeout seconds; [edit services captive-portal interface (all | interface-names)] ] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the time in seconds an interface will wait for a reply when relaying a response from the client to the authentication server before timing out and invoking the server-fail action. seconds—Number of seconds. Range: 1–65535 Default: 20 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 session-expiry Syntax Hierarchy Level Release Information Description Options session-expiry seconds; [edit services captive-portal interface (all | interface-names)] ] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the maximum duration in seconds of a session. seconds—Duration of session. Range: 1 through 65535 Default: 3600 Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 2445 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS single-connection Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation single-connection; [edit system accounting destination tacplus-server server-address] [edit system tacplus-server server-address], Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Optimize attempts to connect to a TACACS+ server. The software maintains one open TCP connection to the server for multiple requests rather than opening a connection for each connection attempt. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring TACACS+ Authentication • Configuring TACACS+ System Accounting source-address Syntax Hierarchy Level Release Information Description Options source-address source-address; [edit access radius-server server-address], [edit access profile profile-name radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a source address for each configured RADIUS server. Each RADIUS request sent to a RADIUS server uses the specified source address. source-address—A valid IPv4 address configured on one of the router or switch interfaces. On M Series routers only, the source address can be an IPv6 address and the UDP source port is 514. Required Privilege Level Related Documentation 2446 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Router or Switch Interaction with RADIUS Servers • Configuring Authentication and Accounting Parameters for Subscriber Access • Example: Configuring CHAP Authentication with RADIUS • Configuring RADIUS Authentication for L2TP Chapter 85: Configuration Statements for Access Control source-address (NTP, RADIUS, System Logging, or TACACS+) Syntax Hierarchy Level Release Information Description Options source-address source-address; [edit system accounting destination radius server server-address], [edit system accounting destination tacplus server server-address], [edit system ntp], [edit system radius-server server-address], [edit system syslog], [edit system tacplus-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a source address for each configured TACACS+ server, RADIUS server, NTP server, or the source address to record in system log messages that are directed to a remote machine. source-address—A valid IP address configured on one of the router or switch interfaces. For system logging, the address is recorded as the message source in messages sent to the remote machines specified in all host hostname statements at the [edit system syslog] hierarchy level, but not for messages directed to the other Routing Engine.. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication • Synchronizing and Coordinating Time Distribution Using NTP • Specifying an Alternative Source Address for System Log Messages 2447 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS static Syntax Hierarchy Level Release Information Description static mac-address { interface interface-names; vlan-assignment (vlan-id |vlan-name ); } [edit protocols dot1x authenticator authentication-profile-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure MAC addresses to exclude from 802.1X authentication. The static MAC list provides an authentication bypass mechanism for supplicants connecting to a port, permitting devices such as printers that are not 802.1X-enabled to be connected to the network on 802.1X-enabled ports. Using this 802.1X authentication-bypass mechanism, the supplicant connected to the MAC address is assumed to be successfully authenticated and the port is opened for it. No further authentication is done for the supplicant. You can optionally configure the VLAN that the supplicant is moved to or the interfaces on which the MAC address can gain access from. Options mac-address —The MAC address of the device for which 802.1X authentication should be bypassed and the device permitted access to the port. The remaining statements are explained separately. Required Privilege Level Related Documentation 2448 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x static-mac-address on page 2484 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Configuring 802.1X Authentication (J-Web Procedure) on page 2332 • Understanding Static MAC Bypass of Authentication on J-EX Series Switches Chapter 85: Configuration Statements for Access Control statistics Syntax Hierarchy Level Release Information Description Options statistics (time | volume-time); [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to collect time statistics, or both volume and time statistics, for the sessions being managed by AAA. time—Collect uptime statistics only. volume-time—Collect both volume and uptime statistics. This option is not available for Mobile IP. Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Mobile IP Home Agent Elements and Behavior • Configuring Authentication and Accounting Parameters for Subscriber Access 2449 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS supplicant Syntax Hierarchy Level Release Information Description Default Options supplicant (multiple | single | single-secure); [edit protocols dot1x authenticator interface (all | [interface-names])], [edit services captive-portal interface (all | interface-names)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the method used to authenticate clients for 802.1X or captive portal authentication. single single—Authenticates only the first client that connects to an authenticator port. All other clients connecting to the authenticator port after the first are permitted free access to the port without further authentication. If the first authenticated client logs out, all other supplicants are locked out until a client authenticates again. single-secure—Authenticates only one client to connect to an authenticator port. The host must be directly connected to the switch. multiple—Authenticates multiple clients individually on one authenticator port. You can configure the number of clients per port. If you also configure a maximum number of devices that can be connected to a port through port security settings, the lower of the configured values is used to determine the maximum number of clients allowed per port. Required Privilege Level Related Documentation 2450 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Understanding Authentication on J-EX Series Switches on page 2248 • Understanding Captive Portal Authentication • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 Chapter 85: Configuration Statements for Access Control supplicant-timeout Syntax Hierarchy Level Release Information Description Default Options supplicant-timeout seconds; [edit protocols dot1x authenticator interface (all | [interface-name]) Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, configure how long the port waits for a response when relaying a request from the authentication server to the supplicant before resending the request. 30 seconds seconds —Number of seconds. Range: 1 through 60 seconds Default: 30 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • supplicant on page 2450 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Understanding Authentication on J-EX Series Switches on page 2248 2451 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS tacplus Syntax Hierarchy Level Release Information Description Options tacplus { server { server-address { port port-number; secret password; single-connection; timeout seconds; } } } [edit system accounting destination] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Terminal Access Controller Access Control System Plus (TACACS+). server-address—Address of the TACACS+ authentication server. The remaining statements are explained separately. Required Privilege Level Related Documentation 2452 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring TACACS+ System Accounting Chapter 85: Configuration Statements for Access Control timeout Syntax Hierarchy Level Release Information Description Options timeout seconds; [edit system radius-server server-address], [edit system tacplus-server server-address], [edit system accounting destination radius server server-address], [edit system accounting destination tacplus server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the amount of time that the local router or switch waits to receive a response from a RADIUS or TACACS+ server. seconds—Amount of time to wait. Range: 1 through 90 seconds Default: 3 seconds Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring RADIUS Authentication • Configuring TACACS+ Authentication • retry on page 2438 2453 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS timeout (RADIUS) Syntax Hierarchy Level Release Information Description Options timeout seconds; [edit access radius-server server-address], [edit access profile profile-name radius-server server-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the amount of time that the local router or switch waits to receive a response from a RADIUS server. seconds—Amount of time to wait. Range: 1 through 90 seconds Default: 3 seconds Required Privilege Level Related Documentation 2454 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring Router or Switch Interaction with RADIUS Servers • Configuring Authentication and Accounting Parameters for Subscriber Access • Example: Configuring CHAP Authentication with RADIUS • Configuring RADIUS Authentication for L2TP Chapter 85: Configuration Statements for Access Control traceoptions Syntax Hierarchy Level Release Information Description Default Options traceoptions { file filename ; flag flag ; } [edit protocols dot1x] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for the 802.1X protocol. Tracing operations are disabled. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. file 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 xk to specify KB, xm to specify MB, or xg to specify gigabytes number of trace files is reached. Then the oldest trace file is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the sizeoption. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—All tracing operations. • config-internal—Trace internal configuration operations. • general—Trace general operations. • normal—Trace normal operations. • parse—Trace reading of the configuration. • regex-parse—Trace regular-expression parsing operations. • state—Trace protocol state changes. • task—Trace protocol task operations. • timer—Trace protocol timer operations. match regex—(Optional) Refine the output to include lines that contain the regular expression. no-world-readable—(Optional) Restricted file access to the user who created the file. 2455 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes. 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 also must specify a maximum file size with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify gigabyte Range: 10 KB through 1gigabyte Default: 128 KB world-readable—(Optional) Enable unrestricted file access. Required Privilege Level Related Documentation 2456 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • 802.1X for J-EX Series Switches Overview on page 2253 Chapter 85: Configuration Statements for Access Control traceoptions Syntax Hierarchy Level Release Information Description Default Options traceoptions { file filename ; flag flag (detail | disable | receive | send); } [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define tracing operations for the LLDP protocol. Tracing operations are disabled. file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. 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 xk to specify KB, xm to specify MB, or xg to specify GB number of trace files is reached. Then the oldest trace file is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the size option. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: • all—All tracing operations. • config—Trace configuration operations. • packet—Trace packet events. • rtsock—Trace routing socket operations. match regex—(Optional) Refine the output to include lines that contain the regular expression. no-world-readable—(Optional) Restrict file access to the user who created the file. 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 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 also must specify a maximum file size with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB 2457 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Range: 10 KB through 1 GB Default: 128 KB world-readable—(Optional) Enable unrestricted file access. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 transmit-delay Syntax Hierarchy Level Release Information Description Default Options transmit-delay seconds; [edit protocols lldp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the delay between 2 successive LLDP advertisements. Disabled. seconds—Number of seconds between two successive LLDP advertisements. Range: 1 through 8192 seconds Default: 2 Required Privilege Level Related Documentation 2458 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 Chapter 85: Configuration Statements for Access Control transmit-period Syntax Hierarchy Level Release Information Description transmit-period seconds; [edit protocols dot1x authenticator interface (all | [interface-name]) Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For 802.1X authentication, how long the port waits before retransmitting the initial EAPOL PDUs to the supplicant. Default 30 seconds Options seconds—Number of seconds the port waits before retransmitting the initial EAPOL PDUs to the supplicant. Range: 1 through 65,535 seconds Default: 30 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • 802.1X for J-EX Series Switches Overview on page 2253 update-interval Syntax Hierarchy Level Release Information Description Options update-interval minutes; [edit access profile profile-name accounting] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the amount of time that the router or switch waits before sending a new accounting update. minutes—Amount of time between updates, in minutes. Range: 10 through 1440 minutes Default: No updates Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring Authentication and Accounting Parameters for Subscriber Access 2459 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan-assignment Syntax Hierarchy Level Release Information vlan-assignment (vlan-id | vlan-name); [edit protocols dot1x authenticator authentication-profile-name static mac-address], [edit ethernet-switching-options authentication-whitelist] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the VLAN that is associated with the list of MAC addresses that are excluded from RADIUS authentication. Options vlan-id | vlan-name—The name of the VLAN or the VLAN tag identifier to associate with the device. The VLAN already exists on the switch. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show dot1x static-mac-address on page 2484 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Understanding Static MAC Bypass of Authentication on J-EX Series Switches • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 vlan-nas-port-stacked-format Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 2460 vlan-nas-port-stacked-format; [edit access profile profile-name radius options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure RADIUS attribute 5 (NAS-Port) to include the S-VLAN ID, in addition to the VLAN ID, for subscribers on Ethernet interfaces. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring RADIUS Server Options for Subscriber Access • Configuring Authentication and Accounting Parameters for Subscriber Access Chapter 85: Configuration Statements for Access Control vlan Syntax Hierarchy Level Release Information Description Options vlan (vlan-id | vlan-name | untagged); [edit ethernet-switching-options voip interface (all | [interface-name | access-ports]) Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For J-EX Series switches, specify the VLAN name or VLAN tag identifier associated with the VLAN to be sent from the authenticating server to the IP phone. vlan-name—Name of a VLAN. vlan-id—The VLAN tag identifier. Range: 0 through 4095. Tags 0 and 4095 are reserved by the Junos OS, and you should not configure them. untagged—Allow untagged VLAN traffic. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 2461 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS voip Syntax Hierarchy Level Release Information Description voip { interface (all | [interface-name | access-ports]) { vlan vlan-name ); forwarding-class ; } } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure voice over IP (VoIP) interfaces. The statements are explained separately. Required Privilege Level Related Documentation 2462 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring VoIP on a J-EX Series Switch Without Including 802.1X Authentication on page 2309 • Example: Configuring VoIP on a J-EX Series Switch Without Including LLDP-MED Support on page 2315 Chapter 85: Configuration Statements for Access Control what Syntax Hierarchy Level Release Information Description what number; [edit protocols lldp-med interface (all | interface-name) location civic-based] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For Link Layer Discovery Protocol–Media Endpoint Device (LLDP-MED), configure the location to which the DHCP entry refers. This information is advertised, along with other location information, from the switch to the MED. It is used during emergency calls to identify the location of the MED. Options 0 and 1 should not be used unless it is known that the DHCP client is in close physical proximity to the server or network element. Default Options Required Privilege Level Related Documentation 1 number—Location: • 0—Location of the DHCP server. • 1—Location of a network element believed to be closest to the client. • 2—Location of the client. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show lldp on page 2489 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring LLDP-MED (CLI Procedure) on page 2346 2463 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2464 CHAPTER 86 Operational Commands for 802.1X 2465 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear captive-portal Syntax Release Information clear captive-portal (firewall [interface-names] | interface (all | [interface-names]) | mac-address [mac-addresses]) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Reset the authentication state of a captive portal interface or captive-portal firewall statistics on one or more interfaces. Options firewall [interface-names]—Resets captive portal statistics on all interfaces or on the specified interface. interface (all | interface-names)—Resets the authentication state of users connected to all interfaces or the specified interfaces. mac-address mac-addresses—Resets the authentication state for the specified MAC addresses. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show captive-portal authentication-failed-users on page 2471 • show captive-portal interface on page 2474 • show captive-portal firewall on page 2472 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 clear captive-portal interface on page 2467 clear captive-portal interface on page 2467 clear captive-portal mac-address on page 2467 clear captive-portal firewall on page 2467 Table 304 on page 2466 lists the output fields for the clear captive-portal interface command. (The clear captive-portal firewall and clear captive-portal mac-address commands have no output). Output fields are listed in the approximate order in which they appear. Table 304: clear captive-portal interface Output Fields Field Name Field Description Interface Interface on which captive portal has been configured. 2466 Chapter 86: Operational Commands for 802.1X Table 304: clear captive-portal interface Output Fields (continued) Field Name Field Description State The state of the port: • Authenticated—The client has been authenticated through the RADIUS server or has been permitted access through server fail fallback. • Authenticating—The client is authenticating through the RADIUS server. • Connecting—Switch is attempting to contact the RADIUS server. • Initialize—The interface link is down. • Held—An action has been triggered through server fail fallback during a RADIUS server timeout. A supplicant is denied access, permitted access through a specified VLAN, or maintains the authenticated state granted to it before the RADIUS server timeout occurred. MAC address The MAC address of the connected client on the interface. User Users connected to the captive portal interface. clear captive-portal interface user@switch> clear captive-portal interface ge-0/0/3.0 clear captive-portal interface user@switch> clear captive-portal interface Captive Portal Information: Interface State MAC address ge-0/0/3.0 Authenticated 00:03:47:e1:ba:b9 ge-0/0/5.0 Connecting ge-0/0/7.0 Connecting ge-0/0/9.0 Connecting User aclallow clear captive-portal mac-address user@switch> clear captive-portal mac-address 00:03:47:e1:ba:b9 clear captive-portal firewall user@switch> clear captive-portal firewall This command has no output. This command has no output. 2467 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear dot1x Syntax Release Information Description clear dot1x (interface (all | [interface-names]) | mac-address [mac-addresses]) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reset the authentication state of a port. When you reset a port, reauthentication on the port is also triggered. The switch sends out a multicast message on the port to restart the authentication of all connected supplicants. If a MAC address is reset, then the switch sends out a unicast message to that specific MAC address to restart authentication. If a supplicant is sending traffic when the clear dot1x interface command is issued, the authenticator immediately initiates reauthenticataion. This process happens very quickly, and it may seem that reauthentication did not occur. To verify that reauthentication has happened, issue the operational mode command show dot1x interface detail. The value for Reauthentication due and Reauthentication interval will be about the same. Options all—(Optional) Clears all ports, or specific ports or specific MAC addresses. interface interface-names—(Optional) Resets the authentication state of all supplicants connected to the specified ports (when the port is an authenticator) or for itself (when the port is a supplicant). mac-address mac-addresses—Resets the authentication state only for the specified MAC addresses. Required Privilege Level Related Documentation List of Sample Output clear dot1x interface clear dot1x mac-address 2468 view • show dot1x on page 2477 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 clear dot1x interface on page 2468 clear dot1x mac-address on page 2468 user@switch> clear dot1x interface ge-1/0/0 ge-2/0/0 ge-2/0/0 ge5/0/0] user@switch> clear dot1x mac—address 00:04:ae:cd:23:5f Chapter 86: Operational Commands for 802.1X clear lldp neighbors Syntax Release Information Description Options clear lldp neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear the learned remote neighbor information on all or selected interfaces. none—Clear the remote neighbor information on all interfaces. interface interface—(Optional) Clear the remote neighbor information from one or more selected interfaces. Required Privilege Level Related Documentation List of Sample Output view • show lldp on page 2489 • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 clear lldp neighbors on page 2469 clear lldp neighbors interface ge-0/1/1.0 on page 2469 clear lldp neighbors user@switch> clear lldp neighbors clear lldp neighbors interface ge-0/1/1.0 user@switch> clear lldp neighbors interface ge-0/1/1.0 2469 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear lldp statistics Syntax Release Information Description Options clear lldp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear LLDP statistics on one or more interfaces. none—Clears LLDP statistics on all interfaces. interface interface-names—(Optional) Clear LLDP statistics on one or more interfaces. Required Privilege Level Related Documentation List of Sample Output clear lldp statistics clear lldp statistics interface ge-0/1/1.0 2470 view • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 clear lldp statistics on page 2470 clear lldp statistics interface ge-0/1/1.0 on page 2470 user@switch> clear lldp statistics user@switch> clear lldp statistics interface ge-0/1/1.0 Chapter 86: Operational Commands for 802.1X show captive-portal authentication-failed-users Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show captive-portal authentication-failed-users Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the users that have failed captive portal authentication. view • show captive-portal interface on page 2474 • show captive-portal firewall on page 2472 • clear captive-portal on page 2466 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 show captive-portal authentication-failed-users on page 2471 Table 305 on page 2471 lists the output fields for the show captive-portal authentication-failed-users command. Output fields are listed in the approximate order in which they appear. Table 305: show captive-portal authentication-failed-users Output Fields show captive-portal authentication-failed-users Field Name Field Description Level of Output Interface The MAC address configured to bypass captive portal authentication. all MAC address The MAC address configured statically on the interface. all User Name of the user that has failed captive portal authentication. all user@switch> show captive-portal authentication-failed-users Interface ge-0/0/10.0 MAC address 00:00:00:10:00:02 User md5user02 2471 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show captive-portal firewall Syntax Release Information Description Options show captive-portal firewall Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the firewall filters for each user that is authenticated on each captive portal interface. none—Display all the firewall filters on all captive portal interfaces. brief | detail—(Optional) Display the specified level of output. interface-name—(Optional) Display all the terms of the firewall filters for the specified interface. interface-name detail—(Optional) Display all of the terms of the firewall filters for the specified interface. Required Privilege Level Related Documentation List of Sample Output Output Fields show captive-portal firewall brief show captive-portal firewall ge-0/0/10.0 2472 view • show captive-portal authentication-failed-users on page 2471 • show captive-portal interface on page 2474 • clear captive-portal on page 2466 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 show captive-portal firewall brief on page 2472 show captive-portal firewall ge-0/0/10.0 on page 2472 show captive-portal firewall on page 2473 Output fields for the show captive-portal firewall command include any action modifier specified in firewall filters except policers. Policers are not supported in the terms of the internally generated dynamic firewall filters that are created when multiple supplicants authenticate on 802.1X-enabled interfaces. user@switch> show captive-portal firewall brief Captive Portal Information: Interface State MAC address ge-0/0/1.0 Connecting ge-0/0/10.0 Connecting 00:30:48:8c:66:bd user@switch> show captive-portal firewall ge-0/0/10.0 Filter name: dot1x_ge-0/0/10 Counters: User No User Chapter 86: Operational Commands for 802.1X Name dot1x_ge-0/0/10_CP_arp dot1x_ge-0/0/10_CP_dhcp dot1x_ge-0/0/10_CP_http dot1x_ge-0/0/10_CP_https dot1x_ge-0/0/10_CP_t_dns dot1x_ge-0/0/10_CP_u_dns show captive-portal firewall Bytes 7616 0 0 0 0 0 user@switch> show captive-portal firewall Filter name: dot1x_ge-0/0/0 Counters: Name Bytes dot1x_ge-0/0/0_CP_arp 0 dot1x_ge-0/0/0_CP_dhcp 0 dot1x_ge-0/0/0_CP_http 0 dot1x_ge-0/0/0_CP_https 0 dot1x_ge-0/0/0_CP_t_dns 0 dot1x_ge-0/0/0_CP_u_dns 0 Filter name: dot1x_ge-0/0/1 Counters: Name Bytes dot1x_ge-0/0/1_CP_arp 0 dot1x_ge-0/0/1_CP_dhcp 0 dot1x_ge-0/0/1_CP_http 0 dot1x_ge-0/0/1_CP_https 0 dot1x_ge-0/0/1_CP_t_dns 0 dot1x_ge-0/0/1_CP_u_dns 0 Filter name: dot1x_ge-0/0/10 Counters: Name Bytes dot1x_ge-0/0/10_CP_arp 7616 dot1x_ge-0/0/10_CP_dhcp 0 dot1x_ge-0/0/10_CP_http 0 dot1x_ge-0/0/10_CP_https 0 dot1x_ge-0/0/10_CP_t_dns 0 dot1x_ge-0/0/10_CP_u_dns 0 Filter name: dot1x_ge-0/0/11 Packets 119 0 0 0 0 0 Packets 0 0 0 0 0 0 Packets 0 0 0 0 0 0 Packets 119 0 0 0 0 0 2473 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show captive-portal interface Syntax Release Information Description Options show captive-portal interface detail Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the current operational state of all captive portal interfaces with the list of connected users and the configured values of captive portal attributes on the interfaces. none—Display all captive portal interfaces. interface-name—(Optional) Display the state for the specified captive portal interface and lists the MAC address and user names of any clients authenticated on the interface. interface-name detail—(Optional) Displays the configured values of captive portal attributes on the specified captive portal interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show captive-portal authentication-failed-users on page 2471 • show captive-portal firewall on page 2472 • captive-portal on page 2385 • clear captive-portal on page 2466 • Example: Setting Up Captive Portal Authentication on a J-EX Series Switch on page 2323 • Configuring Captive Portal Authentication (CLI Procedure) on page 2350 show captive-portal interface on page 2475 show captive-portal interface detail on page 2476 Table 306 on page 2474 lists the output fields for the show captive-portal interface command. Output fields are listed in the approximate order in which they appear. Table 306: show captive-portal interface Output Fields Field Name Field Description Level of Output Interface Interface on which captive portal has been configured. All levels 2474 Chapter 86: Operational Commands for 802.1X Table 306: show captive-portal interface Output Fields (continued) Field Name Field Description Level of Output State The state of the interface: All levels • Authenticated—The client has been authenticated through the RADIUS server or has been permitted access through server fail fallback. • Authenticating—The client is authenticating through the RADIUS server. • Connecting—Switch is attempting to contact the RADIUS server. • Initialize—The interface link is down. • Held—An action has been triggered through server fail fallback during a RADIUS server timeout. A supplicant is denied access, permitted access through a specified VLAN, or maintains the authenticated state granted to it before the RADIUS server timeout occurred. MAC address The MAC address of the connected client on the interface.. brief User Users connected to the captive portal interface. brief Supplicant mode Mode used to authenticate clients—multiple, single, or single-supplicant. detail Number of retries Number of times the user can attempt to submit authentication information. detail Quiet period Time, in seconds, after a user exceeds the maximum number of retries before they can attempt to authenticate. detail Configured CP session timeout Time, in seconds, that a client can be idle before the session expires. detail Server timeout Time, in seconds, that an interface will wait for a reply when relaying a response from the client to the authentication server before timing out and invoking the server-fail action. detail Number of connected supplicants Number of users connecting through the captive portal interface. Information for each user includes: detail • Supplicant—User name and MAC address. • Operational state—See State (above). • Dynamic CP session timeout—Timeout value dynamically downloaded from the RADIUS server for this user, if any. • CP Session expiration due in—Time remaining in session. show captive-portal interface user@switch> show captive-portal interface Captive Portal Information: Interface State MAC address User 2475 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/1.0 ge-0/0/10.0 show captive-portal interface detail 2476 Connecting Connecting 00:30:48:8c:66:bd user@switch> show captive-portal interface detail ge-0/0/1.0 Supplicant mode: Multiple Number of retries: 10 Quiet period: 60 seconds Configured CP session timeout: 3600 seconds Server timeout: 15 seconds Number of connected supplicants: 0 ge-0/0/10.0 Supplicant mode: Multiple Number of retries: 10 Quiet period: 60 seconds Configured CP session timeout: 3600 seconds Server timeout: 15 seconds Number of connected supplicants: 1 Supplicant: No User, 00:30:48:8c:66:bd Operational state: Connecting Dynamic CP Session Timeout: 0 seconds CP Session Expiration due in: 0 seconds No User Chapter 86: Operational Commands for 802.1X show dot1x Syntax Release Information Description Options show dot1x Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the current operational state of all ports with the list of connected users. none—Display information for all authenticator ports. brief | detail—(Optional) Display the specified level of output. interface interface-names—Display information for the specified port with a list of connected supplicants. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear dot1x on page 2468 • Example: Setting Up 802.1X for Single Supplicant or Multiple Supplicant Configurations on a J-EX Series Switch on page 2290 • Example: Configuring 802.1X Authentication Options When the RADIUS Server is Unavailable to a J-EX Series Switch on page 2271 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 • Example: Configuring MAC RADIUS Authentication on a J-EX Series Switch on page 2286 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 • Filtering 802.1X Supplicants Using RADIUS Server Attributes on page 2340 • Verifying 802.1X Authentication on page 2356 show dot1x interface brief on page 2480 show dot1x interface detail on page 2480 Table 307 on page 2477 lists the output fields for the show dot1x command. Output fields are listed in the approximate order in which they appear. Table 307: show dot1x Output Fields Field Name Field Description Level of Output Interface Name of a port. All levels MAC address The MAC address of the connected supplicant on the port. All levels 2477 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 307: show dot1x Output Fields (continued) Field Name Field Description Level of Output Role The 802.1X authentication role of the interface. When 802.1X is enabled on an interface, the role is Authenticator. As Authenticator, the interface blocks LAN access until a supplicant is authenticated through 802.1X or MAC RADIUS authentication. brief, detail State The state of the port: brief • Authenticated—The supplicant has been authenticated through the RADIUS server or has been permitted access through server fail fallback. • Authenticating—The supplicant is authenticating through the RADIUS server. • Held—An action has been triggered through server fail fallback during a RADIUS server timeout. A supplicant is denied access, permitted access through a specified VLAN, or maintains the authenticated state granted to it before the RADIUS server timeout occurred. Administrative state The administrative state of the port: • detail auto—Traffic is allowed through the port based on the authentication result. (Default) • force-authorize—All traffic flows through the port irrespective of the authentication result. This state is not allowed on an interface whose VLAN membership has been set to dynamic. • force-unauthorize—All traffic drops on the port irrespective of the authentication result. This state is not allowed on an interface whose VLAN membership has been set to dynamic. Supplicant The mode for the supplicant: • detail single—Authenticates only the first supplicant. All other supplicants who connect later to the port are allowed full access without any further authentication. They effectively “piggyback” on the first supplicant’s authentication. • single-secure—Allows only one supplicant to connect to the port. No other supplicant is allowed to connect until the first supplicant logs out. • multiple—Allows multiple supplicants to connect to the port. Each supplicant is authenticated individually. Quiet period The number of seconds the port remains in the wait state following a failed authentication exchange with the supplicant before reattempting the authentication. The default value is 60 seconds. The range is 0 through 65,535 seconds. detail Transmit period The number of seconds the port waits before retransmitting the initial EAPOL PDUs to the supplicant. The default value is 30 seconds. The range is 1 through 65,535 seconds. detail MAC radius MAC RADIUS authentication: detail • enabled—The switch sends an EAPOL request to the connecting host to attempt 802.1X authentication and if the connecting host is unresponsive, the switch tries to authenticate using the MAC address. • disabled—The default. The switch will not attempt to authenticate the MAC address of the connecting host. 2478 Chapter 86: Operational Commands for 802.1X Table 307: show dot1x Output Fields (continued) Field Name Field Description Level of Output MAC radius restrict The authentication method is restricted to MAC RADIUS only. 802.1X authentication is not enabled. detail Reauthentication The reauthentication state: detail • disable—Periodic reauthentication of the client is disabled. • interval—Sets the periodic reauthentication time interval. The default value is 3600 seconds. The range is 1 through 65,535 seconds. Supplicant timeout The number of seconds the port waits for a response when relaying a request from the authentication server to the supplicant before resending the request. The default value is 30 seconds. The range is 1 through 60 seconds. detail Server timeout The number of seconds the port waits for a reply when relaying a response from the supplicant to the authentication server before timing out. The default value is 30 seconds. The range is 1 through 60 seconds. detail Maximum EAPOL requests The maximum number of retransmission times of an EAPOL request packet to the supplicant before the authentication session times out. The default value is 2. The range is 1 through 10. detail Number of clients bypassed because of authentication The number of non-802.1X clients granted access to the LAN by means of static MAC bypass. The following fields are displayed: detail • Client—MAC address of the client. • vlan —The name of the VLAN to which the client is connected. Guest VLAN member The VLAN to which a supplicant is connected when the supplicant is authenticated using a guest VLAN. If a guest VLAN is not configured on the interface, this field displays . detail Number of connected supplicants The number of supplicants connected to a port. detail Supplicant The user name and MAC address of the connected supplicant. detail 2479 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 307: show dot1x Output Fields (continued) Field Name Field Description Level of Output Authentication method The 802.1X authentication method used for a supplicant: detail • Guest VLAN—A supplicant is connected to the LAN through the guest VLAN. • MAC Radius—A nonresponsive host is authenticated based on its MAC address. The MAC address is configured as permitted on the RADIUS server, the RADIUS server lets the switch know that the MAC address is a permitted address, and the switch opens LAN access to the nonresponsive host on the interface to which it is connected. • Radius—A supplicant is configured on the RADIUS server, the RADIUS server communicates this to the switch, and the switch opens LAN access on the interface to which the supplicant is connected. • Server-fail deny—If the RADIUS servers time out, all supplicants are denied access to the LAN, preventing traffic from flowing from the supplicant through the interface. This is the default. • Server-fail permit—When the RADIUS server is unavailable, a supplicant is still permitted access to the LAN as if the supplicant had been successfully authenticated by the RADIUS server. • Server-fail use-cache—If the RADIUS servers time out during reauthentication, previously authenticated supplicants are reauthenticated, but new supplicants are denied LAN access. • Server-fail VLAN—A supplicant is configured to be moved to a specified VLAN if the RADIUS server is unavailable to reauthenticate the supplicant. (The VLAN must already exist on the switch.) Authenticated VLAN The VLAN to which the supplicant is connected. detail Dynamic filter User policy filter sent by the RADIUS server. detail Session Reauth interval The configured reauthentication interval. detail Reauthentication due in The number of seconds in which reauthentication will occur again for the connected supplicant. detail show dot1x interface brief user@switch> show dot1x interface [ge-0/0/1 ge-0/0/2 ge0/0/3] brief Interface Role State --------- -------ge-0/0/1 Authenticator Authenticated Authenticating ge-0/0/2 Authenticator Connecting ge-0/0/3 Supplicant Authenticated show dot1x interface detail user@switch> show dot1x interface ge-0/0/16.0 detail ge-0/0/16.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds 2480 MAC address -----------------00:a0:d2:18:1a:c8 00:a0:e5:32:97:af 00:a6:55:f2:94:ae Chapter 86: Operational Commands for 802.1X Mac Radius: Enabled Mac Radius Strict: Disabled Reauthentication: Enabled Reauthentication interval: 40 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 1 Guest VLAN member: Number of connected supplicants: 1 Supplicant: abc, 00:30:48:8C:66:BD Operational state: Authenticated Authentication method: Radius Authenticated VLAN: v200 Reauthentication due in 17 seconds 2481 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show dot1x authentication-failed-users Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show dot1x authentication-failed-users Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays supplicants (users) that have failed 802.1X authentication. view • clear dot1x on page 2468 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 show dot1x authentication-failed-users on page 2482 Table 308 on page 2482 lists the output fields for the show dot1x authentication-failed-users command. Output fields are listed in the approximate order in which they appear. Table 308: show dot1x authentication-failed-users Output Fields Field Name Field Description Level of Output Interface The MAC address configured to bypass 802.1X authentication. all MAC address The MAC address configured statically on the interface. all User The user that is configured on the RADIUS server and that has failed 802.1X authentication. all show dot1x authentication-failed-users user@switch> show dot1x authentication-failed-users Interface ge-0/0/0.0 2482 MAC address 00:00:00:10:00:02 User md5user02 Chapter 86: Operational Commands for 802.1X show dot1x firewall Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show dot1x firewall show dot1x firewall Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays information about the firewall filters for each user or nonresponsive host that is authenticated on each 802.1X-enabled interface that is configured for multiple supplicants. For example, if the firewall filter is configured with a term for counters, the command shows the count for each user. interface interface-names—(Optional) Display information for the specified interface. view • clear dot1x on page 2468 • Example: Applying Firewall Filters to Multiple Supplicants on 802.1X-Enabled Interfaces on page 2318 show dot1x firewall on page 2483 show dot1x firewall on page 2483 Output fields include any action modifier that is specified in firewall filters. (Showing counter action) user@switch> show dot1x firewall Filter: dot1x-filter-ge-0/0/3 Counters counter1_dot1x_ge-0/0/3_user1 counter1_dot1x_ge-0/0/3_user2 show dot1x firewall 342 857 (Showing policer action) user@switch> show dot1x firewall Filter: dot1x_ge-0/0/0 Counters p1-t1 494946 2483 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show dot1x static-mac-address Syntax Release Information Description Options show dot1x static-mac-address <(interface [interface-name])> Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays all the static MAC addresses that are configured to bypass 802.1X authentication on the switch. interface [ interface-name ]—(Optional) Display static MAC addresses for a specific interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear dot1x on page 2468 • Example: Configuring Static MAC Bypass of Authentication on a J-EX Series Switch on page 2281 • Configuring 802.1X Interface Settings (CLI Procedure) on page 2331 • Understanding Static MAC Bypass of Authentication on J-EX Series Switches show dot1x static-mac-address on page 2484 show dot1x static-mac-address interface ge-0/0/0.1 on page 2484 Table 309 on page 2484 lists the output fields for the show dot1x static-mac-address command. Output fields are listed in the approximate order in which they appear. Table 309: show dot1x static-mac-address Output Fields Field Name Field Description Level of Output MAC address The MAC address of the device that is configured to bypass 802.1X authentication. all VLAN-Assignment The name of the VLAN to which the device is assigned. all Interface The name of the interface on which authentication is bypassed for a given MAC address. all show dot1x static-mac-address user@switch> show dot1x static-mac-address MAC address 00:00:00:11:22:33 00:00:00:00:12:12 00:00:00:02:34:56 show dot1x static-mac-address interface ge-0/0/0.1 2484 VLAN-Assignment facilities Interface ge-0/0/3.0 ge-0/0/1.0 user@switch> show dot1x static-mac-address interface ge-0/0/0.1 MAC address VLAN-Assignment Interface Chapter 86: Operational Commands for 802.1X 00:00:00:12:24:12 00:00:00:72:30:58 support support ge-0/0/1.0 ge-0/0/1.0 2485 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching interfaces Syntax Release Information Description Options show ethernet-switching interfaces Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about switched Ethernet interfaces. none—(Optional) Display brief information for Ethernet switching interfaces. brief | detail | summary—(Optional) Display the specified level of output. interface interface-name—(Optional) Display Ethernet switching information for a specific interface. Required Privilege Level Related Documentation view • show ethernet-switching mac-learning-log on page 1241 • show ethernet-switching table on page 1249 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 List of Sample Output show ethernet-switching interfaces on page 2487 show ethernet-switching interfaces ge-0/0/15 brief on page 2488 show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) on page 2488 show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) on page 2488 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) on page 2488 show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) on page 2488 Output Fields Table 310 on page 2486 lists the output fields for the show ethernet-switching interfaces command. Output fields are listed in the approximate order in which they appear. Table 310: show ethernet-switching interfaces Output Fields Field Name Field Description Level of Output Interface Name of a switching interface. All levels State Interface state. Values are up and down. none, brief, detail, summary VLAN members Name of a VLAN. none, brief, detail, summary Tag 2486 Number of the 802.1Q-tag. All levels Chapter 86: Operational Commands for 802.1X Table 310: show ethernet-switching interfaces Output Fields (continued) Field Name Field Description Level of Output Tagging Specifies whether the interface forwards 802.1Q-tagged or untagged traffic. All levels Blocking The forwarding state of the interface: none, brief, detail, summary • unblocked—Traffic is forwarded on the interface. • blocked—Traffic is not being forwarded on the interface. • Disabled by bpdu control—The interface is disabled due to receiving BPDUs on a protected interface. If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. • blocked by RTG—The specified redundant trunk group is disabled. • blocked by STP—The interface is disabled due to a spanning tree protocol error. • MAC limit exceeded—The interface is temporarily disabled due to a MAC limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • MAC move limit exceeded—The interface is temporarily disabled due to a MAC move limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • Storm control in effect—The interface is temporarily disabled due to a storm control error. The disabled interface is automatically restored to service when the disable timeout expires. Index The VLAN index internal to the Junos OS. detail mapping The C-VLAN to S-VLAN mapping information: detail • dot1q-tunneled—The interface maps all traffic to the S-VLAN (all-in-one bundling). • native—The interface maps untagged and priority tagged packets to the S-VLAN. • push—The interface maps packets to a firewall filter to an S-VLAN. • policy-mapped—The interface maps packets to a specifically defined S-VLAN. • integer—The interface maps packets to the specified S-VLAN. show ethernet-switching interfaces user@switch> show ethernet-switching interfaces Interface State ae0.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 ge-0/0/6.0 ge-0/0/7.0 ge-0/0/13.0 ge-0/0/14.0 up up up down down down down up up ge-0/0/15.0 up VLAN members default vlan300 default default default default default default vlan100 vlan200 vlan100 vlan200 Tag 300 100 200 100 200 Tagging Blocking untagged unblocked untagged blocked by RTG (rtggroup) blocked by STP MAC limit exceeded MAC move limit exceeded Storm control in effect unblocked untagged unblocked tagged unblocked tagged unblocked tagged blocked by STP tagged blocked by STP 2487 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/16.0 ge-0/0/17.0 show ethernet-switching interfaces ge-0/0/15 brief show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) down down default vlan100 100 untagged unblocked tagged Disabled by bpdu-control vlan200 200 tagged Disabled by bpdu-control user@switch> show ethernet-switching interfaces ge-0/0/15 brief Interface State VLAN members Tag Tagging Blocking ge-0/0/15.0 up vlan100 vlan200 100 200 tagged tagged blocked by STP blocked by STP user@switch> show ethernet-switching interfaces ge-0/0/2 detail Interface: ge-0/0/2.0, Index: 65, State: up, Port mode: Access VLAN membership: vlan300, 802.1Q Tag: 300, untagged, msti-id: 0, blocked by RTG(rtggroup) Number of MACs learned on IFL: 0 user@switch> show ethernet-switching interfaces ge-0/0/15 detail Interface: ge-0/0/15.0, Index: 70, State: up, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 0, blocked by STP vlan200, 802.1Q Tag: 200, tagged, msti-id: 0, blocked by STP Number of MACs learned on IFL: 0 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) user@switch> show ethernet-switching interfaces ge-0/0/17 detail show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) user@switch>show ethernet-switching interfaces ge-0/0/6.0 detail Interface: ge-0/0/6.0, Index: 73, State: up, Port mode: Access VLAN membership: map, 802.1Q Tag: 134, Mapped Tag: native, push, dot1q-tunneled, unblocked map, 802.1Q Tag: 134, Mapped Tag: 20, push, dot1q-tunneled, unblocked 2488 Interface: ge-0/0/17.0, Index: 71, State: down, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 1, Disabled by bpdu-control vlan200, 802.1Q Tag: 200, tagged, msti-id: 2, Disabled by bpdu-control Number of MACs learned on IFL: 0 Chapter 86: Operational Commands for 802.1X show lldp Syntax Release Information Description Options show lldp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Link Layer Discovery Protocol (LLDP) and Link Level Discovery Protocol–Media Endpoint Discovery (LLDP-MED) configuration and capabilities on the switch. LLDP and LLDP-MED are used to learn about and to distribute device information on network links. none—Display LLDP information for all interfaces. detail—(Optional) Display detailed LLDP information for all interfaces. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Configuring LLDP (CLI Procedure) on page 2344 • Configuring LLDP-MED (CLI Procedure) on page 2346 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 show lldp on page 2492 show lldp (detail) on page 2492 Table 311 on page 2489 lists the output fields for the show lldp command. Output fields are listed in the approximate order in which they appear. Table 311: show lldp Output Fields Field Name Field Description Level of Output LLDP LLDP operating state. The state can be enabled or disabled. All levels NOTE: If a VLAN that has been configured for untagged packets on an interface also has Layer 2 protocol tunneling (L2PT) enabled for LLDP, the LLDP operating state for that interface is displayed as disabled. Advertisement interval Frequency, in seconds, at which LLDP advertisements are sent. All levels This value is set by the advertisement-interval configuration statement. Transmit delay Delay between two successive LLDP advertisements. The delay is set to 2 seconds. All levels Hold timer Multiplier used in combination with the advertisement-interval value to determine the length of time LLDP information is held before it is discarded. All levels This value is set by the hold-multiplier configuration statement. 2489 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 311: show lldp Output Fields (continued) Field Name Field Description Level of Output Notification interval How often LLDP trap notifications are generated as a result of LLDP database changes. If the interval value is 0, LLDP trap notifications of database changes are disabled. All levels This value is set by the lldp-configuration-notification-interval configuration statement. Config Trap Interval How often LLDP trap notifications are generated as a result of changes in topology—for example, when an endpoint connects or disconnects. If the interval value is 0, LLDP trap notifications of topology changes are disabled. All levels This value is set by the ptopo-configuration-trap-interval configuration statement. Connection Hold timer Amount of time the system maintains dynamic topology entries. All levels This value is set by the ptopo-configuration-maximum-hold-time configuration statement. LLDP-MED LLDP-MED operating state. The state can be enabled or disabled. All levels LLDP-MED fast start count Number of advertisements sent from a switch to a device, such as a VoIP telephone, when the device is first detected by the switch. These increased advertisements are temporary. After a device and a switch exchange information and can communicate, advertisements are reduced to one per second. All levels This value is set by the fast-start configuration statement. Interface Name of the interface for which LLDP configuration information is being reported. All levels Parent Interface Name of the aggregated Ethernet interface, if any, to which the interface belongs. All levels LLDP LLDP operating state. The state can be enabled or disabled. All levels LLDP-MED LLDP–MED operating state. The state can be enabled or disabled. All levels Neighbor count Total number of new LLDP neighbors detected since the last switch reboot. detail Interface Name of the interface that is advertising VLAN information. All levels Vlan-id VLAN tag associated with the interface sending LLDP frames. If the interface is not a member of a VLAN, the VLAN ID is advertised as 0. detail Vlan-name VLAN name associated with the VLAN ID. detail 2490 Chapter 86: Operational Commands for 802.1X Table 311: show lldp Output Fields (continued) Field Name Field Description Level of Output LLDP basic TLVs supported Basic TLVs supported on the switch: detail • Chassis identifier—TLV that advertises the MAC address associated with the local system. • Port identifier—TLV that advertises the port identification for the specified port in the local system. • Port description—TLV that advertises the user-configured port description. • System name—TLV that advertises the user-configured name of the local system. • System description—TLV that advertises the system description containing information about the software and current image running on the system. This information is taken from the software and is not configurable. • System capabilities—TLV that advertises the primary functions performed by the system—for example, bridge or router. • Management address—TLV that advertises the IP management address of the local system. Supported LLDP 802 TLVs 802.3 TLVs supported on the switch: • detail Power via MDI—TLV that advertises MDI power support, PSE power pair, and power class information. • Link aggregation—TLV that advertises if the interface is aggregated and its aggregated interface ID. • Maximum frame size—TLV that advertises the maximum transmission unit (MTU) of the interface sending LLDP frames. • Port VLAN tag—TLV that advertises the VLAN tag configured on the interface. • Port VLAN name—TLV that advertises the VLAN name configured on the interface. Supported LLDP MED TLVs LLDP-MED TLVs supported on the switch: • detail LLDP MED capabilities—TLV that advertises the primary function of the port. The capabilities values range from 0 through 15: • • 0—Capabilities • 1—Network Policy • 2—Location Identification • 3—Extended Power via MDI-PSE • 4—Inventory • 5–15—Reserved Network policy—TLV that advertises the port VLAN configuration and associated Layer 2 and Layer 3 attributes. Attributes include the policy identifier, application types—such as voice or streaming video—802.1Q VLAN tagging, and 802.1p priority bits and DiffServ code points. • Endpoint location—TLV that advertises the physical location of the endpoint. • Extended power Via MDI—TLV that advertises the power type, power source, power priority, and power value of the port. It is the responsibility of the PSE device (network connectivity device) to advertise the power priority on a port. 2491 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show lldp user@switch> show lldp LLDP Advertisement interval Transmit delay Hold timer Notification interval Config Trap Interval Connection Hold timer : : : : : : : LLDP MED MED fast start count : Disabled : 3 Packets Interface all me0.0 show lldp (detail) Enabled 30 seconds 2 seconds 4 seconds 0 Second(s) 0 seconds 300 seconds Parent Interface - LLDP Enabled Disabled LLDP-MED - user@switch> show lldp detail LLDP Advertisement interval Transmit delay Hold timer Notification interval Config Trap Interval Connection Hold timer : : : : : : : Enabled 30 seconds 2 seconds 4 seconds 0 Second(s) 0 seconds 300 seconds LLDP MED MED fast start count : Disabled : 3 Packets Interface all me0.0 Parent Interface - LLDP Enabled Disabled LLDP-MED - Interface xe-3/0/0.0 xe-3/0/0.0 xe-3/0/0.0 xe-3/0/1.0 xe-3/0/1.0 xe-3/0/1.0 xe-3/0/2.0 xe-3/0/2.0 xe-3/0/2.0 Parent Interface ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 Vlan-id 100 101 4000 100 101 4000 100 101 4000 Vlan-name v100 v101 v4000 v100 v101 v4000 v100 v101 v4000 Neighbor count 8 0 LLDP basic TLVs supported: Chassis identifier, Port identifier, Port description, System name, System description, System capabilities, Management address. Supported LLDP 802 TLVs: Power via MDI, Link aggregation, Maximum frame size, Port VLAN tag, Port VLAN name. Supported LLDP MED TLVs: LLDP MED capabilities, Network policy, Endpoint location, Extended power Via MDI. 2492 Chapter 86: Operational Commands for 802.1X show lldp local-information Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show lldp local-information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays the information that the switch provides in Link Layer Discovery Protocol (LLDP) advertisements to its neighbors. view • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 show lldp local-information on page 2494 Table 312 on page 2493 lists the output fields for the show lldp local-information command. Output fields are listed in the approximate order in which they appear. Table 312: show lldp local-information Output Fields Field Name Field Description LLDP Local Information details Information about the local system (the switch): • Chassis ID—MAC address associated with the switch. • System name—User-configured name of the switch. • System descr—System description containing information about the switch model and the current software image running on the switch. This information is taken from the software and is not configurable. System Capabilities Capabilities (such as bridge or router) that are supported or enabled on the system. Management Information Details of the management information: Port Name, Port Address (such as 10.204.34.35), Address Type (such as ipv4 or ipv6), Port ID (SNMP interface index), Subtype, and Interface Subtype. Interface Name Name of the local interface. Parent Interface Name of the aggregated Ethernet interface, if any, to which the local interface belongs. Interface ID SNMP interface index. Interface description User-configured port description. Status Administrative status of the interface: either up or down. Tunneling Status of tunneling on the interface: either enabled or disabled. 2493 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show lldp local-information user@switch> show lldp local-information LLDP Local Information details Chassis ID : 00:1d:b5:aa:b9:f0 System name : switch System descr : Juniper Networks, Inc. ex8208 , version 10.3I0 [builder] Build date: 2010-03-24 12:38:30 UTC System Capabilities Supported : Bridge Router Enabled : Bridge Router Management Information Port Name : Port Address : 10.93.54.6 Address Type : IPv4 Port ID : 34 Port ID Subtype : local(7) Port Subtype : ifIndex(1) Interface name me0.0 xe-3/0/0.0 xe-3/0/1.0 xe-3/0/2.0 xe-3/0/3.0 xe-3/0/4.0 xe-3/0/5.0 xe-3/0/6.0 xe-3/0/7.0 2494 Parent Interface ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 Interface ID Interface description 34 769 xe-3/0/0.0 770 xe-3/0/1.0 771 xe-3/0/2.0 772 xe-3/0/3.0 577 xe-3/0/4.0 578 xe-3/0/5.0 579 xe-3/0/6.0 581 xe-3/0/7.0 Status Down Up Up Up Up Up Up Up Up Tunneling Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Chapter 86: Operational Commands for 802.1X show lldp neighbors Syntax Release Information Description Options show lldp neighbors Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the information about neighboring devices learned by the switch by using the Link Layer Discovery Protocol (LLDP). none—Display LLDP neighbor information for all interfaces. interface interface—(Optional) Display LLDP neighbor information for a selected interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 show lldp neighbors on page 2497 show lldp neighbors interface xe-3/0/4.0 on page 2497 show lldp neighbors interface (for a VoIP Avaya Telephone with LLDP-MED Support) on page 2498 Table 313 on page 2495 lists the output fields for the show lldp neighbors command. Output fields are listed in the approximate order in which they appear. Table 313: show lldp neighbors Output Fields Field Name Field Description Local Interface List of local interfaces for which neighbor information is available. Parent Interface List of aggregated Ethernet interfaces, if any, to which the local interfaces belong. Chassis ID List of chassis identifiers for neighbors. Port info List of port information gathered from neighbors. This could be the port identifier or port description. System name List of system names gathered from neighbors. LLDP Neighbor Information Information about both the local system (the switch) and a neighbor system on the interface (appears when the interface option is used). Local Information Information about the local system (appears when the interface option is used). Index Local interface index (appears when the interface option is used). 2495 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 313: show lldp neighbors Output Fields (continued) 2496 Field Name Field Description Time mark Date and timestamp of information (appears when the interface option is used). Time to live Number of seconds for which this information is valid (appears when the interface option is used). Local Interface Name of the local physical interface (appears when the interface option is used). Parent Interface Name of the aggregated Ethernet interface, if any, to which the interface belongs (appears when the interface option is used). Local Port ID Local interface SNMP index (appears when the interface option is used). Ageout Count Number of times the complete set of information advertised by the neighbor has been deleted from LLDP neighbor information maintained by the local system because the information timeliness interval has expired (appears when the interface option is used). Neighbor Information Information about a neighbor system on the interface (appears when the interface option is used). Chassis type Type of chassis identifier supplied, such as MAC address (appears when the interface option is used). Chassis ID Chassis identifier of the chassis type listed (appears when the interface option is used). Port type Type of port identifier supplied, such as locally assigned (appears when the interface option is used). Port ID Port identifier of the port type listed (appears when the interface option is used). Port description Port description (appears when the interface option is used). System name Name supplied by the system on the interface (appears when the interface option is used). System Description Description supplied by the system on the interface (appears when the interface option is used). System capabilities Capabilities (such as Bridge, Router, and Telephone) that are supported or enabled by the system on the interface (appears when the interface option is used). Management Info Details of management information: Address Type (such as ipv4 or ipv6), Address (such as 10.204.34.35), Port ID, Subtype, Interface Subtype, and organization identifier (OID) (appears when the interface option is used). Chapter 86: Operational Commands for 802.1X Table 313: show lldp neighbors Output Fields (continued) show lldp neighbors Field Name Field Description Media Info Additional details about the endpoint device appear when a device that supports LLDP-MED is attached to the interface. The specific details depend upon the capabilities of the device. Details may include: Media endpoint class (such as Class 3 for communication devices such as IP phones), MED Hardware revision, MED Firmware revision, MED Software revision, MED Serial number, MED Manufacturer name, MED Model name. Organization Info One or more entries listing remote information by organizationally unique identifier (OUI), Subtype, Index, and Info (appears when the interface option is used). user@switch> show lldp neighbors Local Interface xe-3/0/4.0 xe-3/0/5.0 xe-3/0/6.0 xe-3/0/7.0 xe-3/0/0.0 xe-3/0/1.0 xe-3/0/2.0 xe-3/0/3.0 show lldp neighbors interface xe-3/0/4.0 Parent Interface ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 Chassis Id b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 b0:c6:9a:63:80:40 Port info xe-0/0/0.0 xe-0/0/1.0 xe-0/0/2.0 xe-0/0/3.0 xe-0/1/0.0 xe-0/1/1.0 xe-0/1/2.0 xe-0/1/3.0 System Name newyork31 newyork31 newyork31 newyork31 newyork31 newyork31 newyork31 newyork31 user@switch>show lldp neighbors interface xe-3/0/4.0 LLDP Neighbor Information: Local Information: Index: 488 Time to live: 120 Time mark: Tue Mar 30 23:33:28 2010 Age: 30 secs Local Interface : xe-3/0/4.0 Parent Interface : ae31.0 Local Port ID : 577 Ageout Count : 10 Neighbour Information: Chassis type : Mac address Chassis ID : b0:c6:9a:63:80:40 Port type : Locally assigned Port ID : 503 Port description : xe-0/0/0.0 System name : newyork31 System Description : Juniper Networks, Inc. ex4500-40f , version 10.2I0 Build date: 2010-03-26 00:17:34 UTC System capabilities Supported : Bridge Router Enabled : Bridge Router Management Info Type Address Port ID Subtype Interface Subtype : : : : : IPv4 10.10.200.84 34 1 2 2497 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS OID show lldp neighbors interface (for a VoIP Avaya Telephone with LLDP-MED Support) : 1.3.6.1.2.1.31.1.1.1.1.34 Organization Info OUI : Subtype : Index : Info : 0.18.15 1 1 0000010000 Organization Info OUI : Subtype : Index : Info : 0.18.15 3 2 0300000207 Organization Info OUI : Subtype : Index : Info : 0.18.15 4 3 05EA Organization Info OUI : Subtype : Index : Info : 0.18.15 1 4 444530323039343530333438 Organization Info OUI : Subtype : Index : Info : 0.18.15 3 5 00640476313030 Organization Info OUI : Subtype : Index : Info : 0.18.15 3 6 00650476313031 Organization Info OUI : Subtype : Index : Info : 0.18.15 3 7 0FA0057634303030 user@switch>show lldp neighbors interface ge-0/0/0.0 LLDP Neighbor Information: Local Information: Index: 20 Time to live: 120 Time mark: Thu Apr 15 22:26:22 2010 Age: 16 secs Local Interface : ge-0/0/0.0 Parent Interface : Local Port ID : 517 Ageout Count : 0 Neighbour Information: Chassis type : Network address Chassis ID : 0.0.0.0 Port type : Mac address Port ID : 00:04:0d:fc:55:48 System name : AVAFC5548 2498 Chapter 86: Operational Commands for 802.1X System capabilities Supported : Bridge Telephone Enabled : Bridge Management Info Type : Address : Port ID : Subtype : Interface Subtype : OID : Media endpoint class: Class MED MED MED MED MED MED Hardware revision Firmware revision Software revision Serial number Manufacturer name Model name : : : : : : IPv4 0.0.0.0 1 1 2 1.3.6.1.2.1.31.1.1.1.1.1 III Device 4610D01A b10d01b2_9.bin a10d01b2_9.bin 07N510103424 Avaya 4610 Organization Info OUI : Subtype : Index : Info : 0.18.15 1 1 036CA00010 Organization Info OUI : Subtype : Index : Info : 0.18.15 1 2 002303 Organization Info OUI : Subtype : Index : Info : 0.18.15 2 3 014001AE Organization Info OUI : Subtype : Index : Info : 0.18.15 5 4 3436313044303141 Organization Info OUI : Subtype : Index : Info : 0.18.15 6 5 62313064303162325F392E62696E Organization Info OUI : Subtype : Index : Info : 0.18.15 7 6 61313064303162325F392E62696E Organization Info OUI : Subtype : Index : Info : 0.18.15 8 7 30374E353130313033343234 2499 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2500 Organization Info OUI : Subtype : Index : Info : 0.18.15 9 8 4176617961 Organization Info OUI : Subtype : Index : Info : 0.18.15 10 9 34363130 Organization Info OUI : Subtype : Index : Info : 0.18.15 1 10 000028003C Organization Info OUI : Subtype : Index : Info : 0.18.15 3 11 00000000 Organization Info OUI : Subtype : Index : Info : 0.18.15 4 12 000000000000000000000000 Organization Info OUI : Subtype : Index : Info : 0.18.15 5 13 00000000 Organization Info OUI : Subtype : Index : Info : 0.18.15 6 14 00000000 Organization Info OUI : Subtype : Index : Info : 0.18.15 7 15 01 Chapter 86: Operational Commands for 802.1X show lldp remote-global-statistics Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show lldp remote-global-statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display remote Link Layer Discovery Protocol (LLDP) global statistics. This command has no options. view • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 show lldp remote-global-statistics on page 2502 Table 314 on page 2501 describes the output fields for the show lldp remote-global-statistics command. Output fields are listed in the approximate order in which they appear. Table 314: show lldp remote-global-statistics Output Fields Field Name Field Description LLDP Remote Database Table Counters Information about remote database table counters. LastchangeTime Time elapsed between LLDP agent startup and the last change to the remote database table information. Inserts Number of insertions made in the remote database table. Deletes Number of deletions made in the remote database table. Drops Number of LLDP frames dropped from the remote database table because of errors. Ageouts Number of remote database table entries that have aged out of the table. 2501 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show lldp remote-global-statistics 2502 user@host> show lldp remote-global-statistics user@host> show lldp remote-global-statistics LLDP Remote Database Table Counters LastchangeTime Inserts Deletes 00:00:76 (76 sec) 192 0 Drops 0 Ageouts 0 Chapter 86: Operational Commands for 802.1X show lldp statistics Syntax Release Information Description Options show lldp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display LLDP statistics for all interfaces or for the specified interface. none—Display LLDP statistics for all interfaces. interface interface—(Optional) Display LLDP statistics for the specified interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Configuring LLDP (CLI Procedure) on page 2344 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 show lldp statistics on page 2504 show lldp statistics interface xe-3/0/0.0 on page 2504 Table 315 on page 2503 lists the output fields for the show lldp statistics command. Output fields are listed in the approximate order in which they appear. Table 315: show lldp statistics Output Fields Field Name Field Description Interface Name of the interface. Parent Interface Name of the aggregated Ethernet interface, if any, to which the interface belongs. NOTE: Because LLDP packets are transmitted and received on member interfaces only, statistics are available only for the member interfaces, not for the aggregated interface. Received Total number of LLDP frames received on an interface. Unknown TLVs Number of unrecognized LLDP TLVs received on an interface. With Errors Number of invalid LLDP TLVs received on an interface. Discarded Number of LLDP TLVs received and then discarded on an interface. Transmitted Total number of LLDP frames that were transmitted on an interface. Untransmitted Total number of LLDP frames that were untransmitted on an interface. 2503 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show lldp statistics user@switch> show lldp statistics Interface xe-3/0/0.0 xe-3/0/1.0 xe-3/0/2.0 xe-3/0/3.0 xe-3/0/4.0 xe-3/0/5.0 xe-3/0/6.0 xe-3/0/7.0 xe-5/0/6.0 xe-5/0/7.0 Parent Interface ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 ae31.0 - Discarded TLVs 0 0 0 0 0 0 0 0 0 0 show lldp statistics interface xe-3/0/0.0 Unknown TLVs 0 0 0 0 0 0 0 0 0 0 With Errors 0 0 0 0 0 0 0 0 0 0 Untransmitted 1 1 1 1 1 1 1 1 0 0 user@switch> show lldp statistics interface xe-3/0/0.0 Interface xe-3/0/0.0 Parent Interface ae31.0 Discarded TLVs 0 2504 Transmitted 3044 3044 3044 3044 3075 3075 3075 3075 17312 17312 Received 1564 1564 1565 1566 1598 1598 1596 1597 0 0 Transmitted 3046 Received 1566 Unknown TLVs 0 Untransmitted 1 With Errors 0 Chapter 86: Operational Commands for 802.1X show network-access aaa statistics accounting Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show network-access aaa statistics accounting Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Display authentication, authorization, and accounting (AAA) accounting statistics. view • accounting-server on page 2373 • accounting-stop-on-access-deny on page 2374 • Configuring 802.1X RADIUS Accounting (CLI Procedure) on page 2339 show network-access aaa statistics accounting on page 2505 Table 316 on page 2505 lists the output fields for the show network-access aaa statistics accounting command. Output fields are listed in the approximate order in which they appear. Table 316: show network-access aaa statistics accounting Output Fields Field Name Field Description Requests received The number of accounting-request packets sent from a switch to a RADIUS accounting server. Accounting Response failures The number of accounting-response failure packets sent from the RADIUS accounting server to the switch. Accounting Response Success The number of accounting-response success packets sent from the RADIUS accounting server to the switch. Requests timedout The number of requests-timedout packets sent from the RADIUS accounting server to the switch. show network-access aaa statistics accounting user@switch> show network-access aaa statistics accounting Accounting module statistics Requests received: 1 Accounting Response failures: 0 Accounting Response Success: 1 Requests timedout: 0 2505 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show network-access aaa statistics authentication Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show network-access aaa statistics authentication Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Display authentication, authorization, and accounting (AAA) authentication statistics. view • authentication-server on page 2383 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 show network-access aaa statistics authentication on page 2506 Table 317 on page 2506 lists the output fields for the show network-access aaa statistics authentication command. Output fields are listed in the approximate order in which they appear. Table 317: show network-access aaa statistics authentication Output Fields Field Name Field Description Requests received The number of authentication requests received by the switch. Accepts The number of authentication accepts received by the RADIUS server. Rejects The number authentication rejects sent by the RADIUS server. Challenges The number of authentication challenges sent by the RADIUS server. show network-access aaa statistics authentication 2506 user@switch> show network-access aaa statistics authentication Authentication module statistics Requests received: 2 Accepts: 1 Rejects: 0 Challenges: 1 Chapter 86: Operational Commands for 802.1X show network-access aaa statistics dynamic-requests Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show network-access aaa statistics dynamic-requests; Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Display authentication, authorization, and accounting (AAA) authentication statistics for disconnects. view • authentication-server on page 2383 • Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch on page 2267 show network-access aaa statistics authentication on page 2507 Table 318 on page 2507 lists the output fields for the show network-access aaa statistics dynamic-requests command. Output fields are listed in the approximate order in which they appear. Table 318: show network-access aaa statistics dynamic-requests Output Fields Field Name Field Description Requests received The number of dynamic requests received by the RADIUS server. Processed successfully The number of dynamic requests successfully processed by the RADIUS server. Errors during processing The number of errors that occurred while the RADIUS server was processing the dynamic request. Silently dropped The number of silently dropped requests. show network-access aaa statistics authentication user@switch> show network-access aaa statistics dynamic-requests Dynamic-requests module statistics Requests received: 0 Processed successfully: 0 Errors during processing: 0 Silently dropped: 0 2507 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2508 PART 18 Rate Limiting • Rate Limiting Overview on page 2511 • Example: Rate Limiting Configuration on page 2513 • Configuring Rate Limiting on page 2515 • Verifying Rate Limiting Configuration on page 2517 • Configuration Statements for Rate Limiting on page 2519 • Operational Mode Commands for Rate Limiting on page 2535 2509 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2510 CHAPTER 87 Rate Limiting Overview • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 Understanding Storm Control on J-EX Series Switches A traffic storm is generated when messages are broadcast on a network and each message prompts a receiving node to respond by broadcasting its own messages on the network. This, in turn, prompts further responses, creating a snowball effect. The LAN is suddenly flooded with packets, creating unnecessary traffic that leads to poor network performance or even a complete loss of network service. Storm control enables the switch to monitor traffic levels and to drop broadcast and unknown unicast packets when a specified traffic level—called the storm control level—is exceeded, thus preventing packets from proliferating and degrading the LAN. As an alternative to having the switch drop packets, you can configure it to shut down interfaces or temporarily disable interfaces (see the action-shutdown statement or the port-error-disable statement) when the storm control level is exceeded. The factory default configuration enables storm control on all switch interfaces, with the storm control level set to 80 percent of the combined broadcast and unknown unicast streams. You can change the storm control level for an interface by specifying a bandwidth value for the combined broadcast and unknown unicast traffic streams. You can also selectively disable storm control on the broadcast stream or on the unknown unicast stream. Broadcast, multicast, and unicast packets are part of normal LAN operation, so to recognize a storm, you must be able to identify when traffic has reached a level that is abnormal for your LAN. Suspect a storm when operations begin timing out and network response times slow down. As more packets flood the LAN, network users might be unable to access servers or e-mail. Monitor the level of broadcast and unknown unicast traffic in the LAN when it is operating normally. Use this data as a benchmark to determine when traffic levels are too high. Then configure storm control to set the level at which you want to drop broadcast traffic, unknown unicast traffic, or both. 2511 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: When you configure storm control bandwidth on an aggregated Ethernet interface, the storm control level for each member of the aggregated Ethernet interface is set to that bandwidth. For example, if you configure a storm control bandwidth of 15000 Kbps on ae1, and ae1 has two members, ge-0/0/0 and ge-0/0/1, each member has a storm control level of 15000 Kbps. Thus, the storm control level on ae1 allows a traffic rate of up to 30000 Kbps of combined broadcast and unknown unicast traffic. Related Documentation • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 Understanding Unknown Unicast Forwarding on J-EX Series Switches Unknown unicast traffic consists of unicast packets with unknown destination MAC addresses. By default, the switch floods these unicast packets that are traveling in a VLAN to all interfaces that are members of the VLAN. Forwarding this type of traffic to interfaces on the switch can trigger a security issue. The LAN is suddenly flooded with packets, creating unnecessary traffic that leads to poor network performance or even a complete loss of network service. This is known as a traffic storm. To prevent a storm, you can disable the flooding of unknown unicast packets to all interfaces by configuring one VLAN or all VLANs to forward and unknown unicast traffic to a specific trunk interface. This channels the unknown unicast traffic to a single interface. Related Documentation 2512 • Understanding Storm Control on J-EX Series Switches on page 2511 • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Configuring Unknown Unicast Forwarding (CLI Procedure) on page 2515 CHAPTER 88 Example: Rate Limiting Configuration • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches Storm control enables you to prevent network outages caused by broadcast storms on the LAN. You can configure storm control on the J-EX Series switch to rate limit broadcast traffic and unknown unicast traffic at a specified level and to drop packets when the specified traffic level is exceeded, thus preventing packets from proliferating and degrading the LAN. This example shows how to configure storm control on a single J-EX Series switch: • Requirements on page 2513 • Overview and Topology on page 2513 • Configuration on page 2514 Requirements This example uses the following hardware and software components: • One J-EX Series switch Overview and Topology A storm is generated when messages are broadcast on a network and each message prompts a receiving node to respond by broadcasting its own messages on the network. This, in turn, prompts further responses, creating a snowball effect and resulting in a broadcast storm that can cause network outages. You can use storm control to prevent broadcast storms by specifying the amount, also known as the storm control level, of broadcast traffic and unknown unicast traffic to be allowed on an interface. You specify the storm control level as the traffic rate in kilobits per second of the combined broadcast and unknown unicast streams. 2513 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: The factory default configuration enables storm control on all interfaces at 80 percent of the combined broadcast and unknown unicast streams. Storm control monitors the incoming broadcast traffic and unknown unicast traffic and compares it with the level that you specify. If broadcast traffic and unknown unicast traffic exceed the specified level, the switch drops packets for the controlled traffic types. As an alternative to having the switch drop packets, you can configure it to shut down interfaces or temporarily disable interfaces (see theaction-shutdown statement or the port-error-disable statement) when the storm control level is exceeded. The topology used in this example consists of one J-EX Series switch with 24 ports. The switch is connected to various network devices. This example shows how to configure the storm control level on interface ge-0/0/0 by setting the level to a traffic rate of 15000 Kbps, based on the traffic rate of the combined broadcast and unknown unicast streams. If broadcast traffic and unknown unicast traffic exceeds this level, the switch drops packets for the controlled traffic types to prevent a network outage. Configuration CLI Quick Configuration To quickly configure storm control based on the traffic rate in kilobits per second of the combined broadcast and unknown unicast streams, copy the following command and paste it into the switch terminal window: [edit] set ethernet-switching-options storm-control interface ge-0/0/0 bandwidth 15000 Step-by-Step Procedure To configure storm control: 1. Specify the traffic rate in kilobits per second of the combined broadcast and unknown unicast streams on a specific interface: [edit ethernet-switching-options] user@switch# set storm-control interface ge-0/0/0 bandwidth 15000 Results Display the results of the configuration: [edit ethernet-switching-options] user@switch# show storm-control interface ge-0/0/0.0 { bandwidth 15000; } Related Documentation 2514 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Understanding Storm Control on J-EX Series Switches on page 2511 CHAPTER 89 Configuring Rate Limiting • Configuring Unknown Unicast Forwarding (CLI Procedure) on page 2515 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 Configuring Unknown Unicast Forwarding (CLI Procedure) Unknown unicast traffic consists of packets with unknown destination MAC addresses. By default, the switch floods these packets to all interfaces associated with a VLAN. Forwarding such traffic to interfaces on the switch can create a security issue. To prevent flooding unknown unicast traffic across the switch, configure unknown unicast forwarding to direct all unknown unicast packets within a VLAN out to a specific trunk interface. From there, the destination MAC address can be learned and added to the Ethernet switching table. You can configure each VLAN to divert unknown unicast traffic to different trunk interfaces or use one trunk interface for multiple VLANs. To configure unknown unicast forwarding options using the CLI: NOTE: Before you can configure unknown unicast forwarding within a VLAN, you must first configure that VLAN. 1. Configure unknown unicast forwarding for a specific VLAN (here, the VLAN name is employee): [edit ethernet-switching-options] user@switch# set unknown-unicast-forwarding vlan employee 2. Specify the trunk interface to which all unknown unicast traffic will be forwarded: [edit ethernet-switching-options ] user@switch# set unknown-unicast-forwarding vlan employee interface ge-0/0/3.0 Related Documentation • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Configuring VLANs for J-EX Series Switches (CLI Procedure) on page 1136 • Configuring VLANs for J-EX Series Switches (J-Web Procedure) on page 1133 2515 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Verifying That Unknown Unicast Packets Are Forwarded to a Trunk Interface on page 2517 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding Storm Control on J-EX Series Switches on page 2511 Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) An Ethernet switching access interface on a J-EX Series switch might shut down or be disabled as a result of one of the following port-security or storm-control configurations: • MAC limiting—mac-limit statement is configured with action shutdown. • MAC move limiting—mac-move-limit statement is configured with action shutdown. • Storm control—storm-control statement is configured with the action shutdown. You can configure the switch to automatically restore the disabled interfaces to service after a specified period of time. Autorecovery applies to all the interfaces that have been disabled due to MAC limiting, MAC move limiting, or storm control errors. NOTE: You must specify the disable timeout value for the interfaces to recover automatically. There is no default disable timeout. If you do not specify a timeout value, you need to use the clear ethernet-switching port-error command to clear the errors and restore the interfaces or the specified interface to service. To configure autorecovery from the disabled state due to MAC limiting, MAC move limiting, or storm control shutdown actions: [edit ethernet-switching-options] user@switch# set port-error-disable disable-timeout 60 Related Documentation 2516 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 • Understanding Storm Control on J-EX Series Switches on page 2511 CHAPTER 90 Verifying Rate Limiting Configuration • Verifying That Unknown Unicast Packets Are Forwarded to a Trunk Interface on page 2517 • Verifying That the Port Error Disable Setting Is Working Correctly on page 2518 Verifying That Unknown Unicast Packets Are Forwarded to a Trunk Interface Purpose Action Verify that a VLAN is forwarding all unknown unicast packets (those with unknown destination MAC addresses) to a single trunk interface instead of flooding unknown unicast packets across all interfaces that are members of the same VLAN. Display the forwarding interface for unknown unicast packets for a VLAN (here, the VLAN name is v1): user@switch> show configuration ethernet-switching-options unknown-unicast-forwarding { vlan v1 { interface ge-0/0/7.0; } } Display the Ethernet switching table: user@switch> show ethernet-switching table vlan v1 Ethernet-switching table: 3 unicast entries VLAN MAC address Type v1 * Flood v1 00:01:09:00:00:00 Learn v1 00:11:09:00:01:00 Learn Meaning Age 24 37 Interfaces All-members ge-0/0/7.0 ge-0/0/3.0 The sample output from the show configuration ethernet-switching-options command shows that the unknown unicast forwarding interface for VLAN v1 is interface ge-0/0/7. The show ethernet-switching table command shows that an unknown unicast packet is received on interface ge-0/0/3 with the destination MAC address (DMAC) 00:01:09:00:00:00 and the source MAC address (SMAC) of 00:11:09:00:01:00. This shows that the SMAC of the packet is learned in the normal way (through the interface ge-0/0/3.0), while the DMAC is learned on interface ge-0/0/7. 2517 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Configuring Unknown Unicast Forwarding (CLI Procedure) on page 2515 Verifying That the Port Error Disable Setting Is Working Correctly Purpose Action Verify that the port error disable setting is working as expected on MAC limited, MAC move limited and rate-limited interfaces on a J-EX Series switch. Display information about interfaces: user@switch> show ethernet-switching interfaces Interface State VLAN members ge-0/0/0.0 up T1122 ge-0/0/1.0 down default ge-0/0/2.0 down default ge-0/0/3.0 down default ge-0/0/4.0 down default ge-0/0/5.0 down default ge-0/0/6.0 down default ge-0/0/7.0 down default ge-0/0/8.0 down default ge-0/0/9.0 up T111 ge-0/0/10.0 down default ge-0/0/11.0 down default ge-0/0/12.0 down default ge-0/0/13.0 down default ge-0/0/14.0 down default ge-0/0/15.0 down default ge-0/0/16.0 down default ge-0/0/17.0 down default ge-0/0/18.0 down default ge-0/0/19.0 up T111 ge-0/1/0.0 down default ge-0/1/1.0 down default ge-0/1/2.0 down default ge-0/1/3.0 down default Meaning Blocking unblocked MAC limit exceeded MAC move limit exceeded Storm control in effect unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked The sample output from the show ethernet-switching interfaces command shows that three of the down interfaces specify the reason that the interface is disabled: • MAC limit exceeded—The interface is temporarily disabled due to a mac-limit error. The disabled interface is automatically restored to service when the disable-timeout expires. • MAC move limit exceeded—The interface is temporarily disabled due to a mac-move-limit error. The disabled interface is automatically restored to service when the disable-timeout expires. • Storm control in efffect —The interface is temporarily disabled due to a storm-control error. The disabled interface is automatically restored to service when the disable-timeout expires. Related Documentation 2518 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 CHAPTER 91 Configuration Statements for Rate Limiting • [edit ethernet-switching-options] Configuration Statement Hierarchy on page 2519 [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; 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; 2519 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } redundant-trunk-group { group-name name { interface interface-name ; } } secure-access-port { 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 ); 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 ); 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 ); (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-unknown-unicast; } } traceoptions { file filename ; flag flag ; 2520 Chapter 91: Configuration Statements for Rate Limiting } unknown-unicast-forwarding { vlan (all | vlan-name) { interface interface-name; } } voip { interface (all | [interface-name | access-ports]) { vlan vlan-name ; forwarding-class ; } } } Related Documentation • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 2521 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS action-shutdown Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 2522 action-shutdown; [edit ethernet-switching-options storm-control] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Shut down or disable interfaces when the storm control level is exceeded, as follows: • If you set both the action-shutdown and the port-error-disable statements, the interfaces are disabled temporarily and recover automatically when the disable timeout expires. • If you set the action-shutdown statement and do not the specify the port-error-disable statement, the interfaces that are enabled for storm control are shut down when the storm control level is exceeded and they do not recover automatically from that port-error condition. You must issue the clear ethernet-switching port-error command to clear the port error and restore the interfaces to service. The action-shutdown option is not enabled. When the storm control level is exceeded, the switch drops unknown unicast and broadcast messages on the specified interfaces. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • port-error-disable on page 2531 • disable-timeout on page 2524 • clear ethernet-switching port-error • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Understanding Storm Control on J-EX Series Switches on page 2511 Chapter 91: Configuration Statements for Rate Limiting bandwidth Syntax bandwidth bandwidth; Hierarchy Level [edit ethernet-switching-options storm-control interface (all | interface-name)] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the storm control level as the bandwidth in kilobits per second of the combined broadcast and unknown unicast streams. NOTE: When you configure storm control bandwidth on an aggregated Ethernet interface, the storm control level for each member of the aggregated Ethernet interface is set to that bandwidth. For example, if you configure a storm control bandwidth of 15000 Kbps on ae1, and ae1 has two members, ge-0/0/0 and ge-0/0/1, each member has a storm control level of 15000 Kbps. Thus, the storm control level on ae1 allows a traffic rate of up to 30000 Kbps of combined broadcast and unknown unicast traffic. Default If you omit the bandwidth statement when you configure storm control on an interface, the storm control level defaults to 80 percent of the combined broadcast and unknown unicast streams. Options bandwidth—Traffic rate in kilobits per second of the combined broadcast and unknown unicast streams. Range: 100 through 10000000 Default: None Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding Storm Control on J-EX Series Switches on page 2511 2523 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable-timeout Syntax Hierarchy Level Release Information Description Default Options disable-timeout timeout; [edit ethernet-switching-options port-error-disable] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long the Ethernet-switching interfaces remain in a disabled state due to the MAC limiting, MAC move liming, or storm control errors. The disable timeout is not enabled. timeout —Amount of time, in seconds, that the disabled state remains in effect. The disabled interface is automatically restored to service when the specified timeout is reached. Range: 10 through 3600 seconds Required Privilege Level Related Documentation 2524 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Port Security (CLI Procedure) on page 2626 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 Chapter 91: Configuration Statements for Rate Limiting ethernet-switching-options Syntax 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; 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 name { interface interface-name ; interface interface-name; } } secure-access-port { dhcp-snooping-file { location local_pathname | remote_URL; timeout seconds; write-interval seconds; } interface (all | interface-name) { allowed-mac { mac-address-list; } 2525 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS (dhcp-trusted | no-dhcp-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); 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); (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-unknown-unicast; } } 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 ; } } } 2526 Chapter 91: Configuration Statements for Rate Limiting Hierarchy Level Release Information Description [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Ethernet switching options. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 2527 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description interface (all | interface-name) { bandwidth bandwidth; no-broadcast; no-unknown-unicast; } [edit ethernet-switching-options storm-control] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable and configure storm control on all interfaces or on the specified interface. If you do not include the bandwidth statement, the storm control level defaults to 80 percent of the combined broadcast and unknown unicast streams. Default The factory default configuration enables storm control on all switch interfaces at the default level of 80 percent of the combined broadcast and unknown unicast streams. Options all—All interfaces. The storm control settings configured with the all option affect only those interfaces that have not been individually configured for storm control. interface-name—Name of an interface. The storm control settings configured with the interface-name option override any settings configured with the all option. The remaining statements are explained separately. Required Privilege Level Related Documentation 2528 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding Storm Control on J-EX Series Switches on page 2511 Chapter 91: Configuration Statements for Rate Limiting interface Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation interface interface-name; [edit ethernet-switching-options unknown-unicast-forwarding vlan(all|vlan-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the interface to which unknown unicast packets will be forwarded. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • show ethernet-switching table on page 1249 • Configuring Unknown Unicast Forwarding (CLI Procedure) on page 2515 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 no-broadcast Syntax no-broadcast; Hierarchy Level [edit ethernet-switching-options storm-control interface (all | interface-name)] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Default Required Privilege Level Related Documentation Disable storm control for broadcast traffic for the specified interface or for all interaces. Storm control is enabled for both unknown unicast traffic and broadcast traffic. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding Storm Control on J-EX Series Switches on page 2511 2529 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-unknown-unicast Syntax no-unknown-unicast; Hierarchy Level [edit ethernet-switching-options storm-control interface (all | interface-name)] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Default Required Privilege Level Related Documentation 2530 Disable storm control for unknown unicast traffic for the specified interface or for all interfaces. Storm control is enabled for both unknown unicast traffic and broadcast traffic. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding Storm Control on J-EX Series Switches on page 2511 Chapter 91: Configuration Statements for Rate Limiting port-error-disable Syntax Hierarchy Level Release Information Description port-error-disable { disable-timeout timeout ; } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable rather than block an interface when enforcing MAC limiting, MAC move limiting, and rate-limiting configuration options for shutting down the interface; and allow the interface to recovery automatically from the error condition after a specified period of time: NOTE: The port-error-disable configuration does not apply to pre-existing error conditions. It impacts only error conditions that are detected after port-error-disable has been enabled and committed. To clear a pre-existing error condition and restore the interface to service, use the clear ethernet-switching port-error command. Default Required Privilege Level Related Documentation • If you have enabled mac-limit with the shutdown option and enable port-error-disable, the switch disables (rather than shuts down) the interface when the MAC address limit is reached. • If you have enabled mac-move-limit with the shutdown option and you enable port-error-disable, the switch disables (rather than shuts down) the interface when the maximum number of moves to a new interface is reached. • If you have enabled storm-control with the action-shutdown option and you enable port-error-disable, the switch disables (rather than shuts down) the interface when broadcast traffic and unknown unicast traffic exceeds the specified levels. Not enabled. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Configuring Port Security (CLI Procedure) on page 2626 • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 2531 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS storm-control Syntax storm-control { action-shutdown; interface (all | interface-name) { bandwidth bandwidth; no-broadcast; no-unknown-unicast; } } Hierarchy Level [edit ethernet-switching-options] Release Information Description Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure storm control on the switch. The remaining statements are explained separately. Required Privilege Level Related Documentation 2532 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding Storm Control on J-EX Series Switches on page 2511 Chapter 91: Configuration Statements for Rate Limiting unknown-unicast-forwarding Syntax Hierarchy Level Release Information Description unknown-unicast-forwarding { vlan (all | vlan-name){ interface interface-name; } } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the switch to forward all unknown unicast packets in a VLAN or on all VLANs to a particular interface. NOTE: Before you can configure unknown unicast forwarding within a VLAN, you must first configure that VLAN. The remaining statements are explained separately. Default Required Privilege Level Related Documentation Unknown unicast packets are flooded to all interfaces that belong to the same VLAN. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • show ethernet-switching table on page 1249 • Configuring Unknown Unicast Forwarding (CLI Procedure) on page 2515 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 2533 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan Syntax Hierarchy Level Release Information Description vlan (all | vlan-name) { interface interface-name; } [edit ethernet-switching-options unknown-unicast-forwarding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a VLAN from which unknown unicast packets will be forwarded or specify that the packets will be forwarded from all VLANS. Unknown unicast packets are forwarded from a VLAN to a specific trunk interface. The interface statement is explained separately. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Options all—All VLANs. vlan-name—Name of a VLAN. Required Privilege Level Related Documentation 2534 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • show vlans on page 1263 • show ethernet-switching table on page 1249 • Configuring Unknown Unicast Forwarding (CLI Procedure) on page 2515 • Verifying That Unknown Unicast Packets Are Forwarded to a Trunk Interface on page 2517 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 CHAPTER 92 Operational Mode Commands for Rate Limiting 2535 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching interfaces Syntax Release Information Description Options show ethernet-switching interfaces Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about switched Ethernet interfaces. none—(Optional) Display brief information for Ethernet switching interfaces. brief | detail | summary—(Optional) Display the specified level of output. interface interface-name—(Optional) Display Ethernet switching information for a specific interface. Required Privilege Level Related Documentation view • show ethernet-switching mac-learning-log on page 1241 • show ethernet-switching table on page 1249 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 List of Sample Output show ethernet-switching interfaces on page 2537 show ethernet-switching interfaces ge-0/0/15 brief on page 2538 show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) on page 2538 show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) on page 2538 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) on page 2538 show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) on page 2538 Output Fields Table 319 on page 2536 lists the output fields for the show ethernet-switching interfaces command. Output fields are listed in the approximate order in which they appear. Table 319: show ethernet-switching interfaces Output Fields Field Name Field Description Level of Output Interface Name of a switching interface. All levels State Interface state. Values are up and down. none, brief, detail, summary VLAN members Name of a VLAN. none, brief, detail, summary Tag 2536 Number of the 802.1Q-tag. All levels Chapter 92: Operational Mode Commands for Rate Limiting Table 319: show ethernet-switching interfaces Output Fields (continued) Field Name Field Description Level of Output Tagging Specifies whether the interface forwards 802.1Q-tagged or untagged traffic. All levels Blocking The forwarding state of the interface: none, brief, detail, summary • unblocked—Traffic is forwarded on the interface. • blocked—Traffic is not being forwarded on the interface. • Disabled by bpdu control—The interface is disabled due to receiving BPDUs on a protected interface. If the disable-timeout statement has been included in the BPDU configuration, the interface automatically returns to service after the timer expires. • blocked by RTG—The specified redundant trunk group is disabled. • blocked by STP—The interface is disabled due to a spanning tree protocol error. • MAC limit exceeded—The interface is temporarily disabled due to a MAC limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • MAC move limit exceeded—The interface is temporarily disabled due to a MAC move limiting error. The disabled interface is automatically restored to service when the disable timeout expires. • Storm control in effect—The interface is temporarily disabled due to a storm control error. The disabled interface is automatically restored to service when the disable timeout expires. Index The VLAN index internal to the Junos OS. detail mapping The C-VLAN to S-VLAN mapping information: detail • dot1q-tunneled—The interface maps all traffic to the S-VLAN (all-in-one bundling). • native—The interface maps untagged and priority tagged packets to the S-VLAN. • push—The interface maps packets to a firewall filter to an S-VLAN. • policy-mapped—The interface maps packets to a specifically defined S-VLAN. • integer—The interface maps packets to the specified S-VLAN. show ethernet-switching interfaces user@switch> show ethernet-switching interfaces Interface State ae0.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 ge-0/0/6.0 ge-0/0/7.0 ge-0/0/13.0 ge-0/0/14.0 up up up down down down down up up ge-0/0/15.0 up VLAN members default vlan300 default default default default default default vlan100 vlan200 vlan100 vlan200 Tag 300 100 200 100 200 Tagging Blocking untagged unblocked untagged blocked by RTG (rtggroup) blocked by STP MAC limit exceeded MAC move limit exceeded Storm control in effect unblocked untagged unblocked tagged unblocked tagged unblocked tagged blocked by STP tagged blocked by STP 2537 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/16.0 ge-0/0/17.0 show ethernet-switching interfaces ge-0/0/15 brief show ethernet-switching interfaces ge-0/0/2 detail (Blocked by RTG rtggroup) show ethernet-switching interfaces ge-0/0/15 detail (Blocked by STP) down down default vlan100 100 untagged unblocked tagged Disabled by bpdu-control vlan200 200 tagged Disabled by bpdu-control user@switch> show ethernet-switching interfaces ge-0/0/15 brief Interface State VLAN members Tag Tagging Blocking ge-0/0/15.0 up vlan100 vlan200 100 200 tagged tagged blocked by STP blocked by STP user@switch> show ethernet-switching interfaces ge-0/0/2 detail Interface: ge-0/0/2.0, Index: 65, State: up, Port mode: Access VLAN membership: vlan300, 802.1Q Tag: 300, untagged, msti-id: 0, blocked by RTG(rtggroup) Number of MACs learned on IFL: 0 user@switch> show ethernet-switching interfaces ge-0/0/15 detail Interface: ge-0/0/15.0, Index: 70, State: up, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 0, blocked by STP vlan200, 802.1Q Tag: 200, tagged, msti-id: 0, blocked by STP Number of MACs learned on IFL: 0 show ethernet-switching interfaces ge-0/0/17 detail (Disabled by bpdu-control) user@switch> show ethernet-switching interfaces ge-0/0/17 detail show ethernet-switching interfaces detail (C-VLAN to S-VLAN Mapping) user@switch>show ethernet-switching interfaces ge-0/0/6.0 detail Interface: ge-0/0/6.0, Index: 73, State: up, Port mode: Access VLAN membership: map, 802.1Q Tag: 134, Mapped Tag: native, push, dot1q-tunneled, unblocked map, 802.1Q Tag: 134, Mapped Tag: 20, push, dot1q-tunneled, unblocked 2538 Interface: ge-0/0/17.0, Index: 71, State: down, Port mode: Trunk VLAN membership: vlan100, 802.1Q Tag: 100, tagged, msti-id: 1, Disabled by bpdu-control vlan200, 802.1Q Tag: 200, tagged, msti-id: 2, Disabled by bpdu-control Number of MACs learned on IFL: 0 Chapter 92: Operational Mode Commands for Rate Limiting show ethernet-switching table Syntax Release Information Description Options show ethernet-switching table Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays the Ethernet switching table. none—(Optional) Display brief information about the Ethernet switching table. brief | detail | extensive | summary—(Optional) Display the specified level of output. management-vlan—(Optional) Display the Ethernet switching table for a management VLAN. interface-name—(Optional) Display the Ethernet switching table for a specific interface. sort-by (name | tag)—(Optional) Display VLANs in ascending order of VLAN IDs or VLAN names. vlan vlan-name—(Optional) Display the Ethernet switching table for a specific VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 show ethernet-switching table on page 2540 show ethernet-switching table brief on page 2541 show ethernet-switching table detail on page 2541 show ethernet-switching table extensive on page 2542 show ethernet-switching table interface ge-0/0/1 on page 2542 Table 320 on page 2539 lists the output fields for the show ethernet-switching table command. Output fields are listed in the approximate order in which they appear. Table 320: show ethernet-switching table Output Fields Field Name Field Description Level of Output VLAN The name of a VLAN. All levels 2539 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 320: show ethernet-switching table Output Fields (continued) Field Name Field Description Level of Output Tag The VLAN ID tag name or number. extensive MAC or MAC address The MAC address associated with the VLAN. All levels Type The type of MAC address. Values are: All levels • static—The MAC address is manually created. • learn—The MAC address is learned dynamically from a packet's source MAC address. • flood—The MAC address is unknown and flooded to all members. Age The time remaining before the entry ages out and is removed from the Ethernet switching table. All levels Interfaces Interface associated with learned MAC addresses or All-members (flood entry). All levels Learned For learned entries, the time which the entry was added to the Ethernet-switching table. detail, extensive Nexthop index The nexthop index number. detail, extensive show ethernet-switching table 2540 user@switch> show ethernet-switching table Ethernet-switching table: 57 entries, 17 learned VLAN MAC address Type F2 * Flood F2 00:00:05:00:00:03 Learn F2 00:19:e2:50:7d:e0 Static Linux * Flood Linux 00:19:e2:50:7d:e0 Static Linux 00:30:48:90:54:89 Learn T1 * Flood T1 00:00:05:00:00:01 Learn T1 00:00:5e:00:01:00 Static T1 00:19:e2:50:63:e0 Learn T1 00:19:e2:50:7d:e0 Static T10 * Flood T10 00:00:5e:00:01:09 Static T10 00:19:e2:50:63:e0 Learn T10 00:19:e2:50:7d:e0 Static T111 * Flood T111 00:19:e2:50:63:e0 Learn T111 00:19:e2:50:7d:e0 Static T111 00:19:e2:50:ac:00 Learn T2 * Flood T2 00:00:5e:00:01:01 Static T2 00:19:e2:50:63:e0 Learn T2 00:19:e2:50:7d:e0 Static T3 * Flood T3 00:00:5e:00:01:02 Static T3 00:19:e2:50:63:e0 Learn T3 00:19:e2:50:7d:e0 Static T4 * Flood Age 0 0 0 0 0 0 0 0 0 - Interfaces All-members ge-0/0/44.0 Router All-members Router ge-0/0/47.0 All-members ge-0/0/46.0 Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members ge-0/0/15.0 Router ge-0/0/15.0 All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members Chapter 92: Operational Mode Commands for Rate Limiting T4 T4 [output truncated] 00:00:5e:00:01:03 Static 00:19:e2:50:63:e0 Learn - Router 0 ge-0/0/46.0 show ethernet-switching table brief user@switch> show ethernet-switching table brief Ethernet-switching table: 57 entries, 17 learned VLAN MAC address Type F2 * Flood F2 00:00:05:00:00:03 Learn F2 00:19:e2:50:7d:e0 Static Linux * Flood Linux 00:19:e2:50:7d:e0 Static Linux 00:30:48:90:54:89 Learn T1 * Flood T1 00:00:05:00:00:01 Learn T1 00:00:5e:00:01:00 Static T1 00:19:e2:50:63:e0 Learn T1 00:19:e2:50:7d:e0 Static T10 * Flood T10 00:00:5e:00:01:09 Static T10 00:19:e2:50:63:e0 Learn T10 00:19:e2:50:7d:e0 Static T111 * Flood T111 00:19:e2:50:63:e0 Learn T111 00:19:e2:50:7d:e0 Static T111 00:19:e2:50:ac:00 Learn T2 * Flood T2 00:00:5e:00:01:01 Static T2 00:19:e2:50:63:e0 Learn T2 00:19:e2:50:7d:e0 Static T3 * Flood T3 00:00:5e:00:01:02 Static T3 00:19:e2:50:63:e0 Learn T3 00:19:e2:50:7d:e0 Static T4 * Flood T4 00:00:5e:00:01:03 Static T4 00:19:e2:50:63:e0 Learn [output truncated] show ethernet-switching table detail user@switch> show ethernet-switching table detail Ethernet-switching table: 5 entries, 2 learned VLAN: default, Tag: 0, MAC: *, Interface: All-members Interfaces: ge-0/0/11.0, ge-0/0/20.0, ge-0/0/30.0, ge-0/0/36.0, ge-0/0/3.0 Type: Flood Nexthop index: 1307 Age 0 0 0 0 0 0 0 0 0 0 Interfaces All-members ge-0/0/44.0 Router All-members Router ge-0/0/47.0 All-members ge-0/0/46.0 Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members ge-0/0/15.0 Router ge-0/0/15.0 All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 VLAN: default, Tag: 0, MAC: 00:1f:12:30:b8:83, Interface: ge-0/0/3.0 Type: Learn, Age: 0, Learned: 20:09:26 Nexthop index: 1315 VLAN: v1, Tag: 101, MAC: *, Interface: All-members Interfaces: ge-0/0/31.0 Type: Flood Nexthop index: 1313 VLAN: v1, Tag: 101, MAC: 00:1f:12:30:b8:89, Interface: ge-0/0/31.0 Type: Learn, Age: 0, Learned: 20:09:25 Nexthop index: 1312 2541 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS VLAN: v2, Tag: 102, MAC: *, Interface: All-members Interfaces: ae0.0 Type: Flood Nexthop index: 1317 show ethernet-switching table extensive user@switch> show ethernet-switching table extensive Ethernet-switching table: 3 entries, 1 learned VLAN: v1, Tag: 10, MAC: *, Interface: All-members Interfaces: ge-0/0/14.0, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0, ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/8.0, ge-0/0/10.0, ge-0/0/0.0 Type: Flood Nexthop index: 567 VLAN: v1, Tag: 10, MAC: 00:21:59:c6:93:22, Interface: Router Type: Static Nexthop index: 0 VLAN: v1, Tag: 10, MAC: 00:21:59:c9:9a:4e, Interface: ge-0/0/14.0 Type: Learn, Age: 0, Learned: 18:40:50 Nexthop index: 564 show ethernet-switching table interface ge-0/0/1 2542 user@switch> show ethernet-switching table interface ge-0/0/1 Ethernet-switching table: 1 unicast entries VLAN MAC address Type Age Interfaces V1 * Flood - All-members V1 00:00:05:00:00:05 Learn 0 ge-0/0/1.0 PART 19 Port Security • Port Security Overview on page 2545 • Examples: Port Security Configuration on page 2569 • Configuring Port Security on page 2625 • Verifying Port Security on page 2653 • Troubleshooting Port Security on page 2665 • Configuration Statements for Port Security on page 2667 • Operational Mode Commands for Port Security on page 2705 2543 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2544 CHAPTER 93 Port Security Overview • Port Security for J-EX Series Switches Overview on page 2545 • Understanding How to Protect Access Ports on J-EX Series Switches from Common Attacks on page 2546 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 • Understanding DAI for Port Security on J-EX Series Switches on page 2555 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 • Understanding Trusted DHCP Servers for Port Security on J-EX Series Switches on page 2559 • Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560 • Understanding IP Source Guard for Port Security on J-EX Series Switches on page 2563 • Understanding Proxy ARP on J-EX Series Switches on page 2566 Port Security for J-EX Series Switches Overview Ethernet LANs are vulnerable to attacks such as address spoofing (forging) and Layer 2 denial of service (DoS) on network devices. Port security features help protect the access ports on your switch against the losses of information and productivity that can result from such attacks. The Junos OS on J-EX Series Switches provides features to help secure ports on the switch. The ports can be categorized as either trusted or untrusted. You apply policies appropriate to those categories to protect against various types of attacks. Port security features can be turned on to obtain the most robust port security level. Basic port security features are enabled in the switch's default configuration. You can configure additional features with minimal configuration steps. Port security features on J-EX Series switches are: • 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). You enable this feature on VLANs. • Dynamic ARP inspection (DAI)—Prevents ARP spoofing attacks. ARP requests and replies are compared against entries in the DHCP snooping database, and filtering 2545 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS decisions are made based on the results of those comparisons. You enable this feature on VLANs. Related Documentation • MAC limiting—Protects against flooding of the Ethernet switching table (also known as the MAC forwarding table or Layer 2 forwarding table). You enable this feature on access interfaces (ports). • MAC move limiting—Detects MAC movement and MAC spoofing on access ports. You enable this feature on VLANs. • Trusted DHCP server—With a DHCP server on a trusted port, protects against rogue DHCP servers sending leases. You enable this feature on interfaces (ports). By default, access ports are untrusted and trunk ports are trusted. (Access ports are the switch ports that connect to Ethernet endpoints such as user PCs and laptops, servers, and printers. Trunk ports are the switch ports that connect to other Ethernet switches or to routers.) • IP source guard—Mitigates the effects of IP address spoofing attacks on the Ethernet LAN. You enable this feature on VLANs. With IP source guard enabled, 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 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. • Security Features for J-EX Series Switches Overview on page 16 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 • Understanding DAI for Port Security on J-EX Series Switches on page 2555 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 • Understanding IP Source Guard for Port Security on J-EX Series Switches on page 2563 • Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560 • Understanding How to Protect Access Ports on J-EX Series Switches from Common Attacks on page 2546 Understanding How to Protect Access Ports on J-EX Series Switches from Common Attacks Port security features can protect the J-EX Series Switch against various types of attacks. Protection methods against some common attacks are: 2546 • Mitigation of Ethernet Switching Table Overflow Attacks on page 2547 • Mitigation of Rogue DHCP Server Attacks on page 2547 Chapter 93: Port Security Overview • Protection Against ARP Spoofing Attacks on page 2548 • Protection Against DHCP Snooping Database Alteration Attacks on page 2548 • Protection Against DHCP Starvation Attacks on page 2548 Mitigation of Ethernet Switching Table Overflow Attacks In an overflow attack on the Ethernet switching table, an intruder sends so many requests from new MAC addresses that the table cannot learn all the addresses. When the switch can no longer use information in the table to forward traffic, it is forced to broadcast messages. Traffic flow on the switch is disrupted, and packets are sent to all hosts on the network. In addition to overloading the network with traffic, the attacker might also be able to sniff that broadcast traffic. To mitigate such attacks, configure both a MAC limit for learned MAC addresses and some specific allowed MAC addresses. Use the MAC limit feature to control the total number of MAC addresses that can be added to the Ethernet switching table for the specified interface or interfaces. By setting the MAC addresses that are explicitly allowed, you ensure that the addresses of network devices whose network access is critical are guaranteed to be included in the Ethernet switching table. See “Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks” on page 2576. Mitigation of Rogue DHCP Server Attacks If an attacker sets up a rogue DHCP server to impersonate a legitimate DHCP server on the LAN, the rogue server can start issuing leases to the network's DHCP clients. The information provided to the clients by this rogue server can disrupt their network access, causing DoS. The rogue server might also assign itself as the default gateway device for the network. The attacker can then sniff the network traffic and perpetrate a man-in-the-middle attack—that is, it misdirects traffic intended for a legitimate network device to a device of its choice. To mitigate a rogue DHCP server attack, set the interface to which that rogue server is connected as untrusted. That action will block all ingress DHCP server messages from that interface. See “Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks” on page 2579. NOTE: The switch logs all DHCP server packets that are received on untrusted ports—for example: 5 untrusted DHCPOFFER received, interface ge-0/0/0.0[65], vlan v1[10] server ip/mac 12.12.12.1/00:00:00:00:01:12 offer ip/client mac 12.12.12.253/00:AA:BB:CC:DD:01 You can use these messages to detect malicious DHCP servers on the network. 2547 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Protection Against ARP Spoofing Attacks In ARP spoofing, an attacker sends faked ARP messages on the network. The attacker associates its own MAC address with the IP address of a network device connected to the switch. Any traffic sent to that IP address is instead sent to the attacker. Now the attacker can create various types of mischief, including sniffing the packets that were meant for another host and perpetrating man-in-the middle attacks. (In a man-in-the-middle attack, the attacker intercepts messages between two hosts, reads them, and perhaps alters them, all without the original hosts knowing that their communications have been compromised. ) To protect against ARP spoofing on your switch, enable both DHCP snooping and dynamic ARP inspection (DAI). DHCP snooping builds and maintains the DHCP snooping table. That table contains the MAC addresses, IP addresses, lease times, binding types, VLAN information, and interface information for the untrusted interfaces on the switch. DAI uses the information in the DHCP snooping table to validate ARP packets. Invalid ARP packets are blocked and, when they are blocked, a system log message is recorded that includes the type of ARP packet and the sender’s IP address and MAC address. See “Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks” on page 2586. Protection Against DHCP Snooping Database Alteration Attacks In an attack designed to alter the DHCP snooping database, an intruder introduces a DHCP client on one of the switch's untrusted access interfaces that has a MAC address identical to that of a client on another untrusted port. The intruder acquires the DHCP lease, which results in changes to the entries in the DHCP snooping table. Subsequently, what would have been valid ARP requests from the legitimate client are blocked. To protect against this type of alteration of the DHCP snooping database, configure MAC addresses that are explicitly allowed on the interface. See “Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks” on page 2590. Protection Against DHCP Starvation Attacks In a DHCP starvation attack, an attacker floods an Ethernet LAN with DHCP requests from spoofed (counterfeit) MAC addresses so that the switch's trusted DHCP servers cannot keep up with requests from legitimate DHCP clients on the switch. The address space of those servers is completely used up, so they can no longer assign IP addresses and lease times to clients. DHCP requests from those clients are either dropped—that is, the result is a denial of service (DoS)—or directed to a rogue DHCP server set up by the attacker to impersonate a legitimate DHCP server on the LAN. To protect the switch from DHCP starvation attacks, use the MAC limiting feature. Specify the maximum number of MAC addresses that the switch can learn on the access interfaces to which those clients connect. The switch's DHCP server or servers will then be able to supply the specified number of IP addresses and leases to those clients and no more. If a DHCP starvation attack occurs after the maximum number of IP addresses has been 2548 Chapter 93: Port Security Overview assigned, the attack will fail. See “Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks” on page 2583. Related Documentation • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 • Understanding DAI for Port Security on J-EX Series Switches on page 2555 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 • Understanding Trusted DHCP Servers for Port Security on J-EX Series Switches on page 2559 • Configuring Port Security (CLI Procedure) on page 2626 • Configuring Port Security (J-Web Procedure) on page 2627 Understanding DHCP Snooping for Port Security on J-EX Series Switches DHCP snooping allows the switch to monitor and control DHCP messages received from untrusted devices connected to the switch. When DHCP snooping is enabled, the system snoops the DHCP messages to view DHCP lease information and build and maintain a database of valid IP address to MAC address (IP-MAC) bindings called the DHCP snooping database. Only clients with valid bindings are allowed access to the network. • DHCP Snooping Basics on page 2549 • DHCP Snooping Process on page 2550 • DHCP Server Access on page 2551 • DHCP Snooping Table on page 2554 • Static IP Address Additions to the DHCP Snooping Database on page 2554 • Snooping DHCP Packets That Have Invalid IP Addresses on page 2554 DHCP Snooping Basics Dynamic Host Configuration Protocol (DHCP) allocates IP addresses dynamically, “leasing” addresses to devices so that the addresses can be reused when no longer needed. Hosts and end devices that require IP addresses obtained through DHCP must communicate with a DHCP server across the LAN. DHCP snooping acts as a guardian of network security by keeping track of valid IP addresses assigned to downstream network devices by a trusted DHCP server (the server is connected to a trusted network port). By default, all trunk ports on the switch are trusted and all access ports are untrusted for DHCP snooping. You can modify these defaults on each of the switch's interfaces. When DHCP snooping is enabled, the lease information from the switch (which is a DHCP client) is used to create the DHCP snooping database, a mapping of IP address to VLAN–MAC-address pairs. For each VLAN–MAC-address pair, the database stores the corresponding IP address. 2549 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Entries in the DHCP database are updated in these events: • When a DHCP client releases an IP address (sends a DHCPRELEASE message), the associated mapping entry is deleted from the database. • If you move a network device from one VLAN to another, typically the device has to acquire a new IP address, so its entry in the database, including the VLAN ID, is updated. • When the lease time (timeout value) assigned by the DHCP server expires, the associated entry is deleted from the database. TIP: By default, the IP-MAC bindings are lost when the switch is rebooted and DHCP clients (the network devices, or hosts) must reacquire bindings. However, you can configure the bindings to persist by setting the dhcp-snooping-file statement to store the database file either locally or remotely. You can configure the switch to snoop DHCP server responses only from particular VLANs. Doing this prevents spoofing of DHCP server messages. You configure DHCP snooping for each VLAN, not for each interface (port). By default, DHCP snooping is disabled for all VLANs. TIP: For private VLANs (PVLANs), enable DHCP snooping on the primary VLAN. If you enable DHCP snooping only on a community VLAN, DHCP messages coming from PVLAN trunk ports are not snooped. DHCP Snooping Process The basic process of DHCP snooping is shown in Figure 60 on page 2551. 2550 Chapter 93: Port Security Overview Figure 60: DHCP Snooping For general information about the messages that the DHCP client and DHCP server exchange during the assignment of an IP address for the client, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. DHCP Server Access Switch access to the DHCP server can be configured in three ways: • Switch, DHCP Clients, and DHCP Server Are All on the Same VLAN on page 2551 • Switch Acts as DHCP Server on page 2553 • Switch Acts as Relay Agent on page 2553 Switch, DHCP Clients, and DHCP Server Are All on the Same VLAN When the switch, DHCP clients, and DHCP server are all members of the same VLAN, the DHCP server can be connected to the switch in one of two ways: • The server is directly connected to the same switch as the one connected to the DHCP clients (the hosts, or network devices, that are requesting IP addresses from the server). You must configure the port that connects the server to the switch as a trusted port. See Figure 61 on page 2552. • The server is directly connected to a switch that is itself directly connected through a trunk port to the switch that the DHCP clients are connected to. The trunk port is configured by default as a trusted port. The switch that the DHCP server is connected 2551 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS to is not configured for DHCP snooping. See Figure 62 on page 2552—in the figure, ge-0/0/11 is a trusted trunk port. Figure 61: DHCP Server Connected Directly to Switch Figure 62: DHCP Server Connected Directly to Switch 2, with Switch 2 Connected to Switch 1 Through a Trusted Trunk Port 2552 Chapter 93: Port Security Overview Switch Acts as DHCP Server The switch itself is configured as a DHCP server; this is known as a “local” configuration. See Figure 63 on page 2553. Figure 63: Switch Is the DHCP Server Switch Acts as Relay Agent The switch functions as a relay agent when the DHCP clients or the DHCP server is connected to the switch through a Layer 3 interface (on the switch, these interfaces are configured as routed VLAN interfaces, or RVIs). These trunk interfaces are trusted by default. These two scenarios illustrate the switch acting as a relay agent: • The DHCP server and clients are in different VLANs. • The switch is connected to a router that is in turn connected to the DHCP server. See Figure 64 on page 2554. 2553 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 64: Switch Acting as Relay Agent Through Router to DHCP Server DHCP Snooping Table The software creates a DHCP snooping information table that displays the content of the DHCP snooping database. The table shows current IP-MAC bindings, as well as lease time, type of binding, names of associated VLANs, and associated interface. To view the table, type show dhcp snooping binding at the operational mode prompt: user@switch> show dhcp snooping binding DHCP Snooping Information: MAC address IP address Lease (seconds) 00:05:85:3A:82:77 192.0.2.17 600 00:05:85:3A:82:79 192.0.2.18 653 00:05:85:3A:82:80 192.0.2.19 720 Type dynamic dynamic dynamic VLAN employee employee employee Interface ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 Static IP Address Additions to the DHCP Snooping Database You can add specific static IP addresses to the database as well as have the addresses dynamically assigned through DHCP snooping. To add static IP addresses, you supply the IP address, the MAC address of the device, the interface on which the device is connected, and the VLAN with which the interface is associated. No lease time is assigned to the entry. The statically configured entry never expires. Snooping DHCP Packets That Have Invalid IP Addresses If you enable DHCP snooping on a VLAN and then devices on that VLAN send DHCP packets that request invalid IP addresses, these invalid IP addresses will be stored in the DHCP snooping database until they are deleted when their default timeout is reached. To eliminate this unnecessary consumption of space in the DHCP snooping database, 2554 Chapter 93: Port Security Overview the switch drops the DCHP packets that request invalid IP addresses, preventing the snooping of these packets. The invalid IP addresses are: Related Documentation • 0.0.0.0 • 128.0.x.x • 191.255.x.x • 192.0.0.x • 223.255.255.x • 224.x.x.x • 240.x.x.x to 255.255.255.255 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding Trusted DHCP Servers for Port Security on J-EX Series Switches on page 2559 • Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560 • DHCP Services for J-EX Series Switches Overview on page 445 • DHCP/BOOTP Relay for J-EX Series Switches Overview on page 446 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Enabling DHCP Snooping (CLI Procedure) on page 2630 and Enabling DHCP Snooping (J-Web Procedure) on page 2631 • Troubleshooting Port Security on page 2665 Understanding DAI for Port Security on J-EX Series Switches Dynamic ARP inspection (DAI) protects J-EX Series Switches against ARP spoofing. DAI inspects ARP packets on the LAN and uses the information in the DHCP snooping database on the switch to validate ARP packets and to protect against ARP cache poisoning. 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. When an attacker tries to use a forged ARP packet to spoof an address, the switch compares the address to entries in the database. If the MAC address or IP address in an ARP packet does not match a valid entry in the DHCP snooping database, the packet is dropped. ARP packets are trapped to the Routing Engine and are rate-limited to protect the switch from CPU overload. • Address Resolution Protocol on page 2556 • ARP Spoofing on page 2556 • DAI on J-EX Series Switches on page 2556 2555 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Address Resolution Protocol Sending IP packets on a multiaccess network requires mapping an IP address to an Ethernet media access control (MAC) address. Ethernet LANs use Address Resolution Protocol (ARP) to map MAC addresses to IP addresses. The switch maintains this mapping in a cache that it consults when forwarding packets to network devices. If the ARP cache does not contain an entry for the destination device, the host (the DHCP client) broadcasts an ARP request for that device's address and stores the response in the cache. ARP Spoofing ARP spoofing (also known as ARP poisoning or ARP cache poisoning) is one way to initiate man-in-the-middle attacks. The attacker sends an ARP packet that spoofs the MAC address of another device on the LAN. Instead of the switch sending traffic to the proper network device, it sends it to the device with the spoofed address that is impersonating the proper device. If the impersonating device is the attacker's machine, the attacker receives all the traffic from the switch that should have gone to another device. The result is that traffic from the switch is misdirected and cannot reach its proper destination. One type of ARP spoofing is gratuitous ARP, which is when a network device sends an ARP request to resolve its own IP address. In normal LAN operation, gratuitous ARP messages indicate that two devices have the same MAC address. They are also broadcast when a network interface card (NIC) in a device is changed and the device is rebooted, so that other devices on the LAN update their ARP caches. In malicious situations, an attacker can poison the ARP cache of a network device by sending an ARP response to the device that directs all packets destined for a certain IP address to go to a different MAC address instead. To prevent MAC spoofing through gratuitous ARP and through other types of spoofing, J-EX Series switches examine ARP responses through DAI. DAI on J-EX Series Switches DAI examines ARP requests and responses on the LAN and validates ARP packets. The switch intercepts ARP packets from an access port and validates them against the DHCP snooping database. If no IP-MAC entry in the database corresponds to the information in the ARP packet, DAI drops the ARP packet and the local ARP cache is not updated with the information in that packet. DAI also drops ARP packets when the IP address in the packet is invalid. The Junos OS for J-EX switches uses DAI for ARP packets received on access ports because these ports are untrusted by default. Trunk ports are trusted by default, so ARP packets bypass DAI on them. You configure DAI for each VLAN, not for each interface (port). By default, DAI is disabled for all VLANs. You can set an interface to be trusted for ARP packets by setting dhcp-trusted on that port. 2556 Chapter 93: Port Security Overview For packets directed to the switch to which a network device is connected, ARP queries are broadcast on the VLAN. The ARP responses to those queries are subjected to the DAI check. For DAI, all ARP packets are trapped to the Routing Engine. To prevent CPU overloading, ARP packets destined for the Routing Engine are rate-limited. If the DHCP server goes down and the lease time for an IP-MAC entry for a previously valid ARP packet runs out, that packet is blocked. Related Documentation • Port Security for J-EX Series Switches Overview on page 2545 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Enabling Dynamic ARP Inspection (J-Web Procedure) on page 2634 Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches MAC limiting protects against flooding of the Ethernet switching table (also known as the MAC forwarding table or Layer 2 forwarding table). You enable this feature on interfaces (ports). MAC move limiting detects MAC movement and MAC spoofing on access interfaces. You enable this feature on VLANs. • MAC Limiting on page 2557 • MAC Move Limiting on page 2558 • Actions for MAC Limiting and MAC Move Limiting on page 2558 • MAC Addresses That Exceed the MAC Limit or MAC Move Limit on page 2559 MAC Limiting MAC limiting sets a limit on the number of MAC addresses that can be learned on a single Layer 2 access interface or on all the Layer 2 access interfaces on the switch. The Junos OS provides two MAC limiting methods: • Maximum number of MAC addresses—You configure the maximum number of dynamic MAC addresses allowed per interface. When the limit is exceeded, incoming packets with new MAC addresses are treated as specified by the configuration. The incoming packets with new MAC addresses can be ignored, dropped, logged, or the interface can be shut down or temporarily disabled. 2557 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Allowed MAC—You configure specific “allowed” MAC addresses for the access interface. Any MAC address that is not in the list of configured addresses is not learned and the switch logs the message. Allowed MAC binds MAC addresses to a VLAN so that the address does not get registered outside the VLAN. If an allowed MAC setting conflicts with a dynamic MAC setting, the allowed MAC setting takes precedence. NOTE: If you do not want the switch to log messages received for invalid MAC addresses on an interface that has been configured for specific “allowed” MAC addresses, you can disable the logging by configuring the no-allowed-mac-log statement. MAC Move Limiting MAC move limiting causes the switch to track the number of times a MAC address can move to a new interface (port). It can help to prevent MAC spoofing, and it can also detect and prevent loops. If a MAC address moves more than the configured number of times within one second, the switch performs the configured action. You can configure MAC move limiting to apply to all VLANs or to a specific VLAN. Actions for MAC Limiting and MAC Move Limiting You can choose to have one of the following actions performed when the limit of MAC addresses or the limit of MAC moves is exceeded: • drop—Drop the packet and generate an alarm, an SNMP trap, or a system log entry. This is the default. • log—Do not drop the packet but generate an alarm, an SNMP trap, or a system log entry. • none—Take no action. • shutdown—Disable the interface and generate an alarm. If you have configured the switch with the port-error-disable statement, the disabled interface recovers automatically upon expiration of the specified disable timeout. If you have not configured the switch for autorecovery from port error disabled conditions, you can bring up the disabled interfaces by running the clear ethernet-switching port-error command. See descriptions of results of these various action settings in “Verifying That MAC Limiting Is Working Correctly” on page 2657. If you have set a MAC limit to apply to all interfaces on the switch, you can override that setting for a particular interface by specifying action none. See “Setting the none Action on an Interface to Override a MAC Limit Applied to All Interfaces (CLI Procedure)” on page 2642. 2558 Chapter 93: Port Security Overview MAC Addresses That Exceed the MAC Limit or MAC Move Limit If you have configured the port-error-disable statement, you can view which interfaces are temporarily disabled due to exceeding the MAC limit or MAC move limit in the output for the show ethernet-switching interfaces command. The log messages that indicate the MAC limit or MAC move limit has been exceeded include the offending MAC addresses that have exceeded the limit. See “Troubleshooting Port Security” on page 2665 for details. Related Documentation • Port Security for J-EX Series Switches Overview on page 2545 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • no-allowed-mac-log on page 2686 Understanding Trusted DHCP Servers for Port Security on J-EX Series Switches Any interface on the switch that connects to a DHCP server can be configured as a trusted port. Configuring a DHCP server on a trusted port protects against rogue DHCP servers sending leases. Ensure that the DHCP server interface is physically secure—that is, that access to the server is monitored and controlled at the site—before you configure the port as trusted. Related Documentation • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Enabling a Trusted DHCP Server (J-Web Procedure) on page 2632 2559 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding DHCP Option 82 for Port Security on J-EX Series Switches You can use DHCP option 82, also known as the DHCP relay agent information option, to help protect the switch against attacks such as spoofing (forging) of IP addresses and MAC addresses, and DHCP IP address starvation. Hosts on untrusted access interfaces on Ethernet LAN switches send requests for IP addresses in order to access the Internet. The switch forwards or relays these requests to DHCP servers, and the servers send offers for IP address leases in response. Attackers can use these messages to perpetrate address spoofing and 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. The Junos OS implementation of DHCP option 82 supports RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. This topic covers: • DHCP Option 82 Processing on page 2560 • Suboption Components of Option 82 on page 2561 • Configurations of the J-EX Series Switch That Support Option 82 on page 2561 DHCP Option 82 Processing If DHCP option 82 is enabled on the switch, then when a network device—a DHCP client—that is connected to the switch on an untrusted interface sends a DHCP request, the switch inserts information about the client's network location into the packet header of that request. The switch then sends the request to the DHCP server. The DHCP server reads the option 82 information in the packet header and uses it to implement the IP address or another parameter for the client. See “Suboption Components of Option 82” on page 2561 for details about option 82 information. You can enable DHCP option 82 on a single VLAN or on all VLANs on the switch. You can also configure it on Layer 3 interfaces (in routed VLAN interfaces, or RVIs) when the switch is functioning as a relay agent. When option 82 is enabled on the switch, then this sequence of events occurs when a DHCP client sends a DHCP request: 1. The switch receives the request and inserts the option 82 information in the packet header. 2. The switch forwards or relays the request to the DHCP server. 3. The server uses the DHCP option 82 information to formulate its reply and sends a response back to the switch. It does not alter the option 82 information. 4. The switch strips the option 82 information from the response packet. 5. The switch forwards the response packet to the client. 2560 Chapter 93: Port Security Overview NOTE: To use the DHCP option 82 feature, you must ensure that the DHCP server is configured to accept option 82. If it is not configured to accept option 82, then when it receives requests containing option 82 information, it does not use the information in setting parameters and it does not echo the information in its response message. For detailed information about configuring DHCP services, see the Junos OS System Basics Configuration Guide at http://www.juniper.net/techpubs/software/junos/. The configuration for DHCP service on the J-EX Series Switch includes the dhcp statement at the [edit system services] hierarchy level. Suboption Components of Option 82 Option 82 as implemented on the J-EX Series switch comprises the suboptions circuit ID, remote ID, and vendor ID. These suboptions are fields in the packet header: • circuit ID—Identifies the circuit (interface and/or VLAN) on the switch on which the request was received. The circuit ID contains the interface name and/or VLAN name, with the two elements separated by a colon—for example, ge-0/0/10:vlan1, where ge-0/0/10 is the interface name and vlan1 is the VLAN name. If the request packet is received on a Layer 3 interface, the circuit ID is just the interface name—for example, ge-0/0/10. Use the prefix option to add an optional prefix to the circuit ID. If you enable the prefix option, the hostname for the switch is used as the prefix; for example, switch1:ge-0/0/10:vlan1, where switch1 is the hostname. You can also specify that the interface description be used rather than the interface name and/or that the VLAN ID be used rather than the VLAN name. • remote ID—Identifies the host. By default, the remote ID is the MAC address of the switch. You can specify that the remote ID be the hostname of the switch, the interface description, or a character string of your choice. You can also add an optional prefix to the remote ID. • vendor ID—Identifies the vendor of the host. If you specify the vendor-id option but do not enter a value, the default value Juniper is used. To specify a value, you type a character string. Configurations of the J-EX Series Switch That Support Option 82 Configurations of the J-EX Series switch that support option 82 are: • Switch and Clients Are on Same VLAN as DHCP Server on page 2561 • Switch Acts as Relay Agent on page 2562 Switch and Clients Are on Same VLAN as DHCP Server If the DHCP clients, the switch, and the DHCP server are all on the same VLAN, the switch forwards the requests from the clients on untrusted access interfaces to the server on a trusted interface. See Figure 65 on page 2562. 2561 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 65: DHCP Clients, Switch, and DHCP Server Are All on Same VLAN For the configuration shown in Figure 65 on page 2562, you set DHCP option 82 at the [edit ethernet-switching-options secure-access-port vlan] hierarchy level. Switch Acts as Relay Agent The switch functions as a relay agent when the DHCP clients or the DHCP server is connected to the switch through a Layer 3 interface. On the switch, these interfaces are configured as routed VLAN interfaces, or RVIs. Figure 66 on page 2563 illustrates a scenario for the switch-as-relay-agent; in this instance, the switch relays requests through a router to the server. 2562 Chapter 93: Port Security Overview Figure 66: Switch Relays DHCP Requests to Server For the configuration shown in Figure 66 on page 2563, you set DHCP option 82 at the [edit forwarding-options helpers bootp] hierarchy level. Related Documentation • Port Security for J-EX Series Switches Overview on page 2545 • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 Understanding IP Source Guard for Port Security on J-EX Series Switches Ethernet LAN switches are vulnerable to attacks that involve spoofing (forging) of source IP addresses or source MAC addresses. You can use the IP source guard access port security feature on J-EX Series Switches to mitigate the effects of these attacks. • IP Address Spoofing on page 2564 • How IP Source Guard Works on page 2564 • The IP Source Guard Database on page 2564 • Typical Uses of Other Junos OS Features with IP Source Guard on page 2565 2563 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS IP Address Spoofing Hosts on access interfaces can spoof source IP addresses and/or source MAC addresses by flooding the switch with packets containing invalid addresses. Such attacks combined with other techniques such as TCP SYN flood attacks can result in denial-of-service (DoS) attacks. With source IP address or source MAC address spoofing, the system administrator cannot identify the source of the attack. The attacker can spoof addresses on the same subnet or on a different subnet. How IP Source Guard Works IP source guard checks the IP source address and MAC source address in a packet sent from a host attached to an untrusted access interface on the switch against entries stored in the DHCP snooping database. If IP source guard determines that the packet header contains an invalid source IP address or source MAC address, it ensures that the switch does not forward the packet—that is, the packet is discarded. When you configure IP source guard, you enable on it on one or more VLANs. IP source guard applies its checking rules to packets sent from untrusted access interfaces on those VLANs. By default, on J-EX Series switches, access interfaces are untrusted and trunk interfaces are trusted. IP source guard does not check packets that have been sent to the switch by devices connected to either trunk interfaces or trusted access interfaces—that is, interfaces configured as dhcp-trusted so that a DHCP server can be connected to that interface to provide dynamic IP addresses. IP source guard obtains information about IP-address/MAC-address/VLAN bindings from the DHCP snooping database. It causes the switch to validate incoming IP packets against the entries in that database. After the DHCP snooping database has been populated either through dynamic DHCP snooping or through configuration of specific static IP address/MAC address bindings, the IP source guard feature builds its database. It then checks incoming packets from access interfaces on the VLANs on which it is enabled. If the source IP addresses and source MAC addresses match the IP source guard binding entries, the switch forwards the packets to their specified destination addresses. If there are no matches, the switch discards the packets. The IP Source Guard Database The IP source guard database looks like this: user@switch> show ip-source-guard IP source guard information: Interface Tag IP Address MAC Address VLAN ge-0/0/12.0 0 10.10.10.7 00:30:48:92:A5:9D vlan100 ge-0/0/13.0 0 10.10.10.9 00:30:48:8D:01:3D vlan100 ge—0/0/13.0 100 * * voice The IP source guard database table contains the VLANs enabled for IP source guard, the untrusted access interfaces on those VLANs, the VLAN 802.1Q tag IDs if there are any, 2564 Chapter 93: Port Security Overview and the IP addresses and MAC addresses that are bound to one another. If a switch interface is associated with multiple VLANs and some of those VLANs are enabled for IP source guard and others are not, the VLANs that are not enabled for IP source guard have a star (*) in the IP Address and MAC Address fields. See the entry for the voice VLAN in the preceding sample output. Typical Uses of Other Junos OS Features with IP Source Guard You can configure IP source guard with various other features on the J-EX Series switch to provide access port security, including: • VLAN tagging (used for voice VLANs) • GRES (Graceful Routing Engine switchover) • Virtual Chassis configurations (multiple J-EX4200 switches that are managed through a single management interface) • Link-aggregation groups (LAGs) • 802.1X user authentication, in single supplicant mode NOTE: The 802.1X user authentication is applied in one of three modes: single supplicant, single-secure supplicant, or multiple supplicant. Single supplicant mode works with IP source guard, but single-secure and multiple supplicant modes do not. Related Documentation • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 2565 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Proxy ARP on J-EX Series Switches You can configure proxy Address Resolution Protocol (ARP) on your J-EX Series Switch to enable the switch to respond to ARP queries for network addresses by offering its own Ethernet media access control (MAC) address. With proxy ARP enabled, the switch captures and routes traffic to the intended destination. Proxy ARP is useful in situations where hosts are on different physical networks and you do not want to use subnet masking. Because ARP broadcasts are not propagated between hosts on different physical networks, hosts will not receive a response to their ARP request if the destination is on a different subnet. Enabling the switch to act as an ARP proxy allows the hosts to transparently communicate with each other through the switch. Proxy ARP can help hosts on a subnet reach remote subnets without your having to configure routing or a default gateway. • What Is ARP? on page 2566 • Proxy ARP Overview on page 2566 • Best Practices for Proxy ARP on J-EX Series Switches on page 2567 What Is ARP? Ethernet LANs use ARP to map Ethernet MAC addresses to IP addresses. Each device maintains a cache containing a mapping of MAC addresses to IP addresses. The switch maintains this mapping in a cache that it consults when forwarding packets to network devices. If the ARP cache does not contain an entry for the destination device, the host (the DHCP client) broadcasts an ARP request for that device's address and stores the response in the cache. Proxy ARP Overview When proxy ARP is enabled, if the switch receives an ARP request for which it has a route to the target (destination) IP address, the switch responds by sending a proxy ARP reply packet containing its own MAC address. The host that sent the ARP request then sends its packets to the switch, which forwards them to the intended host. NOTE: For security reasons, the source address in an ARP request must be on the same subnet as the interface on which the ARP request is received. You can configure proxy ARP for each interface. You can also configure proxy ARP for a VLAN by using a routed VLAN interface (RVI). J-EX Series switches support two modes of proxy ARP, restricted and unrestricted. Both modes require that the switch have an active route to the destination address of the ARP request. • 2566 Restricted—The switch responds to ARP requests in which the physical networks of the source and target are different and does not respond if the source and target IP addresses are on the same subnet. In this mode, hosts on the same subnet communicate without proxy ARP. We recommend that you use this mode on the switch. Chapter 93: Port Security Overview • Unrestricted—The switch responds to all ARP requests for which it has a route to the destination. This is the default mode (because it is the default mode in Junos OS configurations other than those on the switch). We recommend using restricted mode on the switch. Best Practices for Proxy ARP on J-EX Series Switches We recommend these best practices for configuring proxy ARP on the switches: Related Documentation • Set proxy ARP to restricted mode. • Use restricted mode when configuring proxy ARP on RVIs. • If you set proxy ARP to unrestricted, disable gratuitous ARP requests on each interface enabled for proxy ARP. • Example: Configuring Proxy ARP on a J-EX Series Switch on page 2621 • Configuring Proxy ARP (CLI Procedure) on page 1153 2567 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2568 CHAPTER 94 Examples: Port Security Configuration • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Configuring Proxy ARP on a J-EX Series Switch on page 2621 Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch You can configure DHCP snooping, dynamic ARP inspection (DAI), MAC limiting, and MAC move limiting on the access ports of J-EX Series switches to protect the switch and the Ethernet LAN against address spoofing and Layer 2 denial-of-service (DoS) attacks. You can also configure a trusted DHCP server and specific (allowed) MAC addresses for the switch interfaces. 2569 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to configure basic port security features—DHCP snooping, DAI, MAC limiting, and MAC move limiting, as well as a trusted DHCP server and allowed MAC addresses—on a switch. The DHCP server and its clients are all members of a single VLAN on the switch. • Requirements on page 2570 • Overview and Topology on page 2570 • Configuration on page 2572 • Verification on page 2573 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure DHCP snooping, DAI, and MAC limiting port security features, be sure you have: • Connected the DHCP server to the switch. • Configured the VLAN employee-vlan on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. To protect the devices from such attacks, you can configure DHCP snooping to validate DHCP server messages, DAI to protect against MAC spoofing, and MAC cache limiting to constrain the number of MAC addresses the switch adds to its MAC address cache. You can also configure MAC move limiting to help prevent MAC spoofing. This example shows how to configure these security features on a J-EX4200-24T switch. The switch is connected to a DHCP server. The setup for this example includes the VLAN employee-vlan on the switch. The procedure for creating that VLAN is described in the topic “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. That procedure is not repeated here. Figure 67 on page 2571 illustrates the topology for this example. 2570 Chapter 94: Examples: Port Security Configuration Figure 67: Network Topology for Basic Port Security The components of the topology for this example are shown in Table 321 on page 2571. Table 321: Components of the Port Security Topology Properties Settings Switch hardware One J-EX4200-24T, 24 ports (8 PoE ports) VLAN name and ID employee-vlan, tag 20 VLAN subnets 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is subnet's broadcast address Interfaces in employee-vlan ge-0/0/1, ge-0/0/2, ge-0/0/3, ge-0/0/8 Interface for DHCP server ge-0/0/8 In this example, the switch is initially configured with the default port security setup. In the default configuration on the switch: • Secure port access is activated on the switch. • DHCP snooping and DAI are disabled on all VLANs. • All access ports are untrusted and all trunk ports are trusted for DHCP snooping, which is the default setting. In the configuration tasks for this example, you set the DHCP server first as untrusted and then as trusted; you enable DHCP snooping, DAI, and MAC move limiting on a VLAN; 2571 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS you modify the value for MAC limit; and you configure some specific (allowed) MAC addresses on an interface. Configuration To configure basic port security on a switch whose DHCP server and client ports are in a single VLAN: CLI Quick Configuration To quickly configure basic port security on the switch, copy the following commands and paste them into the switch terminal window: [edit ethernet-switching-options secure-access-port] set interface ge-0/0/1 mac-limit 4 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:80 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:81 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:83 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:85 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:88 set interface ge-0/0/2 mac-limit 4 set interface ge-0/0/8 dhcp-trusted set vlan employee–vlan arp-inspection set vlan employee-vlan examine-dhcp set vlan employee-vlan mac-move-limit 5 Step-by-Step Procedure Configure basic port security on the switch: 1. Enable DHCP snooping on the VLAN: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee-vlan examine-dhcp 2. Specify the interface (port) from which DHCP responses are allowed: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/8 dhcp-trusted 3. Enable dynamic ARP inspection (DAI) on the VLAN: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee-vlan arp-inspection 4. Configure the MAC limit of 4 and use the default action, drop. (Packets will be dropped and the MAC address will not be added to the Ethernet switching table if the MAC limit has been exceeded on the interfaces): [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/1 mac-limit 4 user@switch# set interface ge-0/0/2 mac-limit 4 5. Configure a MAC move limit of 5 and use the default action, drop. (Packets will be dropped and the MAC address will not be added to the Ethernet switching table if a MAC address has exceeded the MAC move limit): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee-vlan mac-move-limit 5 6. Configure the allowed MAC addresses: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:80 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:81 2572 Chapter 94: Examples: Port Security Configuration user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:83 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:85 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:88 Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show interface ge-0/0/1.0 { mac-limit 4 action drop; } interface ge-0/0/2.0 { allowed-mac [ 00:05:85:3a:82:80 00:05:85:3a:82:81 00:05:85:3a:82:83 00:05:85:3a:82:85 00:05:85:3a:82:88 ]; mac-limit 4 action drop; } interface ge-0/0/8.0 { dhcp-trusted; } vlan employee-vlan { arp-inspection examine-dhcp; mac-move-limit 5 action drop; } Verification To confirm that the configuration is working properly: • Verifying That DHCP Snooping Is Working Correctly on the Switch on page 2573 • Verifying That DAI Is Working Correctly on the Switch on page 2574 • Verifying That MAC Limiting and MAC Move Limiting Are Working Correctly on the Switch on page 2574 • Verifying That Allowed MAC Addresses Are Working Correctly on the Switch on page 2575 Verifying That DHCP Snooping Is Working Correctly on the Switch Purpose Action Verify that DHCP snooping is working on the switch. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the interface on which the DHCP server connects to the switch is trusted. The following output results when requests are sent from the MAC addresses and the server has provided the IP addresses and leases: user@switch> show dhcp snooping binding 2573 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS DHCP Snooping Information: MAC Address IP Address -------------------------00:05:85:3A:82:77 192.0.2.17 00:05:85:3A:82:79 192.0.2.18 00:05:85:3A:82:80 192.0.2.19 00:05:85:3A:82:81 192.0.2.20 00:05:85:3A:82:83 192.0.2.21 00:05:85:27:32:88 192.0.2.22 Meaning Lease ----600 653 720 932 1230 3200 Type ---dynamic dynamic dynamic dynamic dynamic dynamic VLAN ---employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan Interface --------ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 When the interface on which the DHCP server connects to the switch has been set to trusted, the output (see preceding sample) shows, for each MAC address, the assigned IP address and lease time—that is, the time, in seconds, remaining before the lease expires. If the DHCP server had been configured as untrusted, no entries would be added to the DHCP snooping database and nothing would be shown in the output of the show dhcp snooping binding command. Verifying That DAI Is Working Correctly on the Switch Purpose Action Verify that DAI is working on the switch. Send some ARP requests from network devices connected to the switch. Display the DAI information: user@switch> show arp inspection statistics ARP inspection statistics: Interface Packets received ARP inspection pass ARP inspection failed --------------- ---------------------------------- --------------------ge-0/0/1.0 7 5 2 ge-0/0/2.0 10 10 0 ge-0/0/3.0 12 12 0 Meaning The sample output shows the number of ARP packets received and inspected per interface, with a listing of how many packets passed and how many failed the inspection on each interface. The switch compares the ARP requests and replies against the entries in the DHCP snooping database. If a MAC address or IP address in the ARP packet does not match a valid entry in the database, the packet is dropped. Verifying That MAC Limiting and MAC Move Limiting Are Working Correctly on the Switch Purpose Action Verify that MAC limiting and MAC move limiting are working on the switch. Suppose that two packets have been sent from hosts on ge-0/0/1 and five packets from hosts on ge-0/0/2, with both interfaces set to a MAC limit of 4 with the default action drop. Display the MAC addresses learned: user@switch> show ethernet-switching table 2574 Chapter 94: Examples: Port Security Configuration Ethernet-switching table: 7 entries, 6 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan * 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:3A:82:85 Age Interfaces 0 0 0 0 0 0 ge-0/0/2.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 Flood Learn Learn Learn Learn Learn Learn Now suppose packets have been sent from two of the hosts on ge-0/0/2 after they have been moved to other interfaces more than 5 times in 1 second, with employee-vlan set to a MAC move limit of 5 with the default action drop. Display the MAC addresses in the table: user@switch> show ethernet-switching table Ethernet-switching table: 7 entries, 4 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning * 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 * * Age Interfaces 0 0 0 0 - ge-0/0/2.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 Flood Learn Learn Learn Learn Flood Flood The first sample output shows that with a MAC limit of 4 for each interface, the fifth MAC address on ge-0/0/2 was not learned because it exceeded the MAC limit. The second sample output shows that MAC addresses for three of the hosts on ge-/0/0/2 were not learned, because the hosts had been moved back more than 5 times in one second. Verifying That Allowed MAC Addresses Are Working Correctly on the Switch Purpose Action Verify that allowed MAC addresses are working on the switch. Display the MAC cache information after 5 allowed MAC addresses have been configured on interface ge-0/0/2: user@switch> show ethernet-switching table Ethernet-switching table: 5 entries, 4 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:3A:82:85 * Learn Learn Learn Learn Flood Age Interfaces 0 0 0 0 - ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 Because the MAC limit value for this interface has been set to 4, only 4 of the 5 configured allowed addresses are learned. 2575 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Configuring Port Security (CLI Procedure) on page 2626 • Configuring Port Security (J-Web Procedure) on page 2627 Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks In an Ethernet switching table overflow attack, an intruder sends so many requests from new MAC addresses that the Ethernet switching table fills up and then overflows, forcing the switch to broadcast all messages. This example describes how to configure MAC limiting and allowed MAC addresses, two port security features, to protect the switch from Ethernet switching table attacks: • Requirements on page 2576 • Overview and Topology on page 2577 • Configuration on page 2578 • Verification on page 2579 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure specific port security features to mitigate common access-interface attacks, be sure you have: 2576 • Connected the DHCP server to the switch. • Configured the VLAN employee-vlan on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. Chapter 94: Examples: Port Security Configuration Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. This example describes how to protect the switch from an attack on the Ethernet switching table that causes the table to overflow and thus forces the switch to broadcast all messages. This example shows how to configure port security features on a J-EX4200-24T switch. The switch is connected to a DHCP server. The setup for this example includes the VLAN employee-vlan on the switch. The procedure for creating that VLAN is described in the topic “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. That procedure is not repeated here. Figure 68 on page 2577 illustrates the topology for this example. Figure 68: Network Topology for Basic Port Security The components of the topology for this example are shown in Table 322 on page 2577. Table 322: Components of the Port Security Topology Properties Settings Switch hardware One J-EX4200-24T, 24 ports (8 PoE ports) VLAN name and ID employee-vlan, tag 20 VLAN subnets 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is subnet's broadcast address Interfaces in employee-vlan ge-0/0/1, ge-0/0/2, ge-0/0/3, ge-0/0/8 2577 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 322: Components of the Port Security Topology (continued) Properties Settings Interface for DHCP server ge-0/0/8 In this example, use the MAC limit feature to control the total number of MAC addresses that can be added to the Ethernet switching table for the specified interface. Use the allowed MAC addresses feature to ensure that the addresses of network devices whose network access is critical are guaranteed to be included in the Ethernet switching table. In this example, the switch has already been configured as follows: • Secure port access is activated on the switch. • No MAC limit is set on any of the interfaces. • All access interfaces are untrusted, which is the default setting. Configuration To configure MAC limiting and some allowed MAC addresses to protect the switch against Ethernet switching table overflow attacks: CLI Quick Configuration To quickly configure MAC limiting and some allowed MAC addresses, copy the following commands and paste them into the switch terminal window: [edit ethernet-switching-options secure-access-port] set interface ge-0/0/1 mac-limit 4 action drop set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:80 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:81 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:83 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:85 Step-by-Step Procedure Configure MAC limiting and some allowed MAC addresses: 1. Configure a MAC limit of 4 on ge-0/0/1 and specify that incoming packets with different addresses be dropped once the limit is exceeded on the interface: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/1 mac-limit 4 action drop 2. Configure the allowed MAC addresses on ge-0/0/2: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:80 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:81 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:83 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:85 Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show interface ge-0/0/1.0 { mac-limit 4 action drop; } interface ge-0/0/2.0 { 2578 Chapter 94: Examples: Port Security Configuration allowed-mac [ 00:05:85:3a:82:80 00:05:85:3a:82:81 00:05:85:3a:82:83 00:05:85 :3a:82:85 ]; } Verification To confirm that the configuration is working properly: • Verifying That MAC Limiting Is Working Correctly on the Switch on page 2579 Verifying That MAC Limiting Is Working Correctly on the Switch Purpose Action Verify that MAC limiting is working on the switch. Display the MAC cache information after DHCP requests have been sent from hosts on ge-0/0/1, with the interface set to a MAC limit of 4 with the action drop, and after four allowed MAC addresses have been configured on interface ge/0/0/2: user@switch> show ethernet-switching table Ethernet-switching table: 5 entries, 4 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning Related Documentation 00:05:85:3A:82:71 00:05:85:3A:82:74 00:05:85:3A:82:77 00:05:85:3A:82:79 * 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:3A:82:85 * Age Interfaces 0 0 0 0 0 0 0 0 0 - ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 Learn Learn Learn Learn Flood Learn Learn Learn Learn Flood The sample output shows that with a MAC limit of 4 for the interface, the DHCP request for a fifth MAC address on ge-0/0/1 was dropped because it exceeded the MAC limit and that only the specified allowed MAC addresses have been learned on the ge-0/0/2 interface. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks In a rogue DHCP server attack, an attacker has introduced a rogue server into the network, allowing it to give IP address leases to the network's DHCP clients and to assign itself as the gateway device. 2579 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to configure a DHCP server interface as untrusted to protect the switch from a rogue DHCP server: • Requirements on page 2580 • Overview and Topology on page 2580 • Configuration on page 2582 • Verification on page 2582 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure an untrusted DHCP server interface to mitigate rogue DHCP server attacks, be sure you have: • Connected the DHCP server to the switch. • Enabled DHCP snooping on the VLAN. • Configured the VLAN employee-vlan on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. This example describes how to protect the switch from rogue DHCP server attacks. This example shows how to explicitly configure an untrusted interface on a J-EX4200-24T switch. Figure 69 on page 2581 illustrates the topology for this example. 2580 Chapter 94: Examples: Port Security Configuration Figure 69: Network Topology for Basic Port Security The components of the topology for this example are shown in Table 323 on page 2581. Table 323: Components of the Port Security Topology Properties Settings Switch hardware One J-EX4200-24T, 24 ports (8 PoE ports) VLAN name and ID employee-vlan, tag 20 VLAN subnets 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is the subnet's broadcast address Interfaces in employee-vlan ge-0/0/1, ge-0/0/2, ge-0/0/3, ge-0/0/8 Interface for DHCP server ge-0/0/8 In this example, the switch has already been configured as follows: • Secure port access is activated on the switch. • DHCP snooping is enabled on the VLAN employee-vlan. • The interface (port) where the rogue DHCP server has connected to the switch is currently trusted. 2581 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuration To configure the DHCP server interface as untrusted because the interface is being used by a rogue DHCP server: CLI Quick Configuration To quickly set the rogue DHCP server interface as untrusted, copy the following command and paste it into the switch terminal window: [edit ethernet-switching-options secure-access-port] set interface ge-0/0/8 no-dhcp-trusted Step-by-Step Procedure To set the DHCP server interface as untrusted: Specify the interface (port) from which DHCP responses are not allowed: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/8 no–dhcp-trusted Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show interface ge-0/0/8.0 { no-dhcp-trusted; } Verification To confirm that the configuration is working properly: • Verifying That the DHCP Server Interface Is Untrusted on page 2582 Verifying That the DHCP Server Interface Is Untrusted Purpose Action Verify that the DHCP server is untrusted. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the port on which the DHCP server connects to the switch is not trusted. user@switch> show dhcp snooping binding Meaning Related Documentation 2582 There is no output from the command because no entries are added to the DHCP snooping database. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Enabling a Trusted DHCP Server (J-Web Procedure) on page 2632 Chapter 94: Examples: Port Security Configuration Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks In a DHCP starvation attack, an attacker floods an Ethernet LAN with DHCP requests from spoofed (counterfeit) MAC addresses. The switch's trusted DHCP server or servers cannot keep up with the requests and can no longer assign IP addresses and lease times to legitimate DHCP clients on the switch. Requests from those clients are either dropped or directed to a rogue DHCP server set up by the attacker. This example describes how to configure MAC limiting, a port security feature, to protect the switch against DHCP starvation attacks: • Requirements on page 2583 • Overview and Topology on page 2583 • Configuration on page 2584 • Verification on page 2585 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure MAC limiting, a port security feature, to mitigate DHCP starvation attacks, be sure you have: • Connected the DHCP server to the switch. • Configured the VLAN employee-vlan on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. This example describes how to protect the switch against one common type of attack, a DHCP starvation attack. This example shows how to configure port security features on a J-EX4200-24T switch that is connected to a DHCP server. The setup for this example includes the VLAN employee-vlan on the switch. The procedure for creating that VLAN is described in the topic “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. That procedure is not repeated here. Figure 70 on page 2584 illustrates the topology for this example. 2583 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 70: Network Topology for Basic Port Security The components of the topology for this example are shown in Table 324 on page 2584. Table 324: Components of the Port Security Topology Properties Settings Switch hardware One J-EX4200-24T, 24 ports (8 PoE ports) VLAN name and ID default Interfaces in employee-vlan ge-0/0/1, ge-0/0/2, ge-0/0/3, ge-0/0/8 Interface for DHCP server ge-0/0/8 In this example, the switch has already been configured as follows: • Secure port access is activated on the switch. • No MAC limit is set on any of the interfaces. • DHCP snooping is disabled on the VLAN employee-vlan. • All access interfaces are untrusted, which is the default setting. Configuration To configure the MAC limiting port security feature to protect the switch against DHCP starvation attacks: CLI Quick Configuration 2584 To quickly configure MAC limiting, copy the following commands and paste them into the switch terminal window: Chapter 94: Examples: Port Security Configuration [edit ethernet-switching-options secure-access-port] set interface ge-0/0/1 mac-limit 3 action drop set interface ge-0/0/2 mac-limit 3 action drop Step-by-Step Procedure Configure MAC limiting: 1. Configure a MAC limit of 3 on ge-0/0/1 and specify that packets with new addresses be dropped if the limit has been exceeded on the interface: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge–0/0/1 mac-limit 3 action drop 2. Configure a MAC limit of 3 on ge-0/0/2 and specify that packets with new addresses be dropped if the limit has been exceeded on the interface: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/2 mac-limit 3 action drop Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show interface ge-0/0/1.0 { mac-limit 3 action drop; } interface ge-0/0/2.0 { mac-limit 3 action drop; } Verification To confirm that the configuration is working properly: • Verifying That MAC Limiting Is Working Correctly on the Switch on page 2585 Verifying That MAC Limiting Is Working Correctly on the Switch Purpose Action Verify that MAC limiting is working on the switch. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the MAC addresses learned when DHCP requests are sent from hosts on ge-0/0/1 and from hosts on ge-0/0/2, with both interfaces set to a MAC limit of 3 with the action drop: user@switch> show ethernet-switching table Ethernet-switching table: 7 entries, 6 learned VLAN MAC address Type default default default default default default * 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 Flood Learn Learn Learn Learn Learn Age Interfaces 0 0 0 0 0 ge-0/0/2.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 2585 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS default Meaning 00:05:85:3A:82:85 Learn 0 ge-0/0/2.0 The sample output shows that with a MAC limit of 3 for each interface, the DHCP request for a fourth MAC address on ge-0/0/2 was dropped because it exceeded the MAC limit. Because only 3 MAC addresses can be learned on each of the two interfaces, attempted DHCP starvation attacks will fail. Related Documentation • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks In an ARP spoofing attack, the attacker associates its own MAC address with the IP address of a network device connected to the switch. Traffic intended for that IP address is now sent to the attacker instead of being sent to the intended destination. The attacker can send faked, or “spoofed,” ARP messages on the LAN. NOTE: On J-EX Series switches, when dynamic ARP inspection (DAI) is enabled, the switch logs the number of invalid ARP packets that it receives on each interface, along with the sender’s IP and MAC addresses. You can use these log messages to discover ARP spoofing on the network. This example describes how to configure DHCP snooping and dynamic ARP inspection (DAI), two port security features, to protect the switch against ARP spoofing attacks: • Requirements on page 2586 • Overview and Topology on page 2587 • Configuration on page 2588 • Verification on page 2589 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure DHCP snooping and DAI, two port security features, to mitigate ARP spoofing attacks, be sure you have: • 2586 Connected the DHCP server to the switch. Chapter 94: Examples: Port Security Configuration • Configured the VLAN employee-vlan on the switch. Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. This example describes how to protect the switch against one common type of attack, an ARP spoofing attack. In an ARP spoofing attack, the attacker sends faked ARP messages, thus creating various types of mischief on the LAN—for example, the attacker might launch a man-in-the middle attack. This example shows how to configure port security features on a J-EX4200-24T switch that is connected to a DHCP server. The setup for this example includes the VLAN employee-vlan on the switch. The procedure for creating that VLAN is described in the topic “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. That procedure is not repeated here. Figure 71 on page 2587 illustrates the topology for this example. Figure 71: Network Topology for Basic Port Security The components of the topology for this example are shown in Table 325 on page 2587. Table 325: Components of the Port Security Topology Properties Settings Switch hardware One J-EX4200-24T, 24 ports (8 PoE ports) VLAN name and ID employee-vlan, tag 20 2587 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 325: Components of the Port Security Topology (continued) Properties Settings VLAN subnets 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is subnet's broadcast address Interfaces in employee-vlan ge-0/0/1,ge-0/0/2, ge-0/0/3, ge-0/0/8 Interface for DHCP server ge-0/0/8 In this example, the switch has already been configured as follows: • Secure port access is activated on the switch. • DHCP snooping is disabled on the VLAN employee-vlan. • All access ports are untrusted, which is the default setting. Configuration To configure DHCP snooping and dynamic ARP inspection (DAI) to protect the switch against ARP attacks: CLI Quick Configuration To quickly configure DHCP snooping and dynamic ARP inspection (DAI), copy the following commands and paste them into the switch terminal window: [edit ethernet-switching-options secure-access-port] set interface ge-0/0/8 dhcp-trusted set vlan employee-vlan examine-dhcp set vlan employee-vlan arp-inspection Step-by-Step Procedure Configure DHCP snooping and dynamic ARP inspection (DAI) on the VLAN: 1. Set the ge-0/0/8 interface as trusted: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/8 dhcp-trusted 2. Enable DHCP snooping on the VLAN: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee-vlan examine-dhcp 3. Enable DAI on the VLAN: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee-vlan arp-inspection Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show interface ge-0/0/8.0 { dhcp-trusted; } vlan employee-vlan { 2588 Chapter 94: Examples: Port Security Configuration arp-inspection; examine-dhcp; } Verification To confirm that the configuration is working properly: • Verifying That DHCP Snooping Is Working Correctly on the Switch on page 2589 • Verifying That DAI Is Working Correctly on the Switch on page 2589 Verifying That DHCP Snooping Is Working Correctly on the Switch Purpose Action Verify that DHCP snooping is working on the switch. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the port on which the DHCP server connects to the switch is trusted. The following output results when requests are sent from the MAC addresses and the server has provided the IP addresses and leases: user@switch> show dhcp snooping binding DHCP Snooping Information: MAC Address IP Address Lease -----------------------------00:05:85:3A:82:77 192.0.2.17 600 00:05:85:3A:82:79 192.0.2.18 653 00:05:85:3A:82:80 192.0.2.19 720 00:05:85:3A:82:81 192.0.2.20 932 00:05:85:3A:82:83 192.0.2.21 1230 00:05:85:27:32:88 192.0.2.22 3200 Meaning Type ---dynamic dynamic dynamic dynamic dynamic dynamic VLAN ---employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Interface --------ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/3.0 When the interface on which the DHCP server connects to the switch has been set to trusted, the output (see preceding sample) shows, for each MAC address, the assigned IP address and lease time—that is, the time, in seconds, remaining before the lease expires. Verifying That DAI Is Working Correctly on the Switch Purpose Action Verify that DAI is working on the switch. Send some ARP requests from network devices connected to the switch. Display the DAI information: user@switch> show arp inspection statistics ARP inspection statistics: Interface Packets received ARP inspection pass ARP inspection failed --------------- ---------------------------------- --------------------ge-0/0/1.0 7 5 2 ge-0/0/2.0 10 10 0 ge-0/0/3.0 12 12 0 2589 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning Related Documentation The sample output shows the number of ARP packets received and inspected per interface, with a listing of how many packets passed and how many failed the inspection on each interface. The switch compares the ARP requests and replies against the entries in the DHCP snooping database. If a MAC address or IP address in the ARP packet does not match a valid entry in the database, the packet is dropped. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Enabling DHCP Snooping (CLI Procedure) on page 2630 • Enabling DHCP Snooping (J-Web Procedure) on page 2631 • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Enabling Dynamic ARP Inspection (J-Web Procedure) on page 2634 Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks In one type of attack on the DHCP snooping database, an intruder introduces a DHCP client on an untrusted access interface with a MAC address identical to that of a client on another untrusted interface. The intruder then acquires the DHCP lease of that other client, thus changing the entries in the DHCP snooping table. Subsequently, what would have been valid ARP requests from the legitimate client are blocked. This example describes how to configure allowed MAC addresses, a port security feature, to protect the switch from DHCP snooping database alteration attacks: • Requirements on page 2590 • Overview and Topology on page 2591 • Configuration on page 2592 • Verification on page 2592 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure specific port security features to mitigate common access-inteface attacks, be sure you have: 2590 • Connected the DHCP server to the switch. • Configured the VLAN employee-vlan on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. Chapter 94: Examples: Port Security Configuration Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. This example describes how to protect the switch from an attack on the DHCP snooping database that alters the MAC addresses assigned to some clients. This example shows how to configure port security features on a J-EX4200-24T switch that is connected to a DHCP server. The setup for this example includes the VLAN employee-vlan on the switch. The procedure for creating that VLAN is described in the topic “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. That procedure is not repeated here. Figure 72 on page 2591 illustrates the topology for this example. Figure 72: Network Topology for Basic Port Security The components of the topology for this example are shown in Table 326 on page 2591. Table 326: Components of the Port Security Topology Properties Settings Switch hardware One J-EX4200-24T, 24 ports (8 PoE ports) VLAN name and ID employee-vlan, tag 20 VLAN subnets 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is subnet's broadcast address Interfaces in employee-vlan ge-0/0/1, ge-0/0/2, ge-0/0/3, ge-0/0/8 2591 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 326: Components of the Port Security Topology (continued) Properties Settings Interface for DHCP server ge-0/0/8 In this example, the switch has already been configured as follows: • Secure port access is activated on the switch. • DHCP snooping is enabled on the VLAN employee-vlan. • All access ports are untrusted, which is the default setting. Configuration To configure allowed MAC addresses to protect the switch against DHCP snooping database alteration attacks: CLI Quick Configuration To quickly configure some allowed MAC addresses on an interface, copy the following commands and paste them into the switch terminal window: [edit ethernet-switching-options secure-access-port] set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:80 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:81 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:83 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:85 set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:88 Step-by-Step Procedure To configure some allowed MAC addresses on an interface: Configure the five allowed MAC addresses on an interface: [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:80 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:81 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:83 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:85 user@switch# set interface ge-0/0/2 allowed-mac 00:05:85:3A:82:88 Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show interface ge-0/0/2.0 { allowed-mac [ 00:05:85:3a:82:80 00:05:85:3a:82:81 00:05:85:3a:82:83 00:05:85 :3a:82:85 00:05:85:3a:82:88 ]; } Verification To confirm that the configuration is working properly: • Verifying That Allowed MAC Addresses Are Working Correctly on the Switch on page 2592 Verifying That Allowed MAC Addresses Are Working Correctly on the Switch Purpose 2592 Verify that allowed MAC addresses are working on the switch. Chapter 94: Examples: Port Security Configuration Action Display the MAC cache information: user@switch> show ethernet-switching table Ethernet-switching table: 6 entries, 5 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning Related Documentation 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:3A:82:85 00:05:85:3A:82:88 * Age Interfaces 0 0 0 0 0 - ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 Learn Learn Learn Learn Learn Flood The output shows that the five MAC addresses configured as allowed MAC addresses have been learned and are displayed in the MAC cache. The last MAC address in the list, one that had not been configured as allowed, has not been added to the list of learned addresses. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch You can configure DHCP snooping, dynamic ARP inspection (DAI), and MAC limiting on the access interfaces of J-EX Series switches to protect the switch and the Ethernet LAN against address spoofing and Layer 2 denial-of-service (DoS) attacks. To obtain those basic settings, you can use the switch's default configuration for port security, configure the MAC limit, and enable DHCP snooping and DAI on a VLAN. You can configure those features when the DHCP server is connected to a different switch from the one to which the DHCP clients (network devices) are connected. This example describes how to configure port security features on a J-EX Series switch whose hosts obtain IP addresses and lease times from a DHCP server connected to a second switch: • Requirements on page 2594 • Overview and Topology on page 2594 • Configuring a VLAN, Interfaces, and Port Security Features on Switch 1 on page 2596 • Configuring a VLAN and Interfaces on Switch 2 on page 2598 • Verification on page 2599 2593 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Requirements This example uses the following hardware and software components: • One J-EX4200-24T switch—“Switch 1” in this example. • An additional J-EX Series switch—”Switch 2” in this example. You will not configure port security on this switch. • A DHCP server connected to Switch 2. You will use the server to provide IP addresses to network devices connected to Switch 1. • At least two network devices (hosts) that you will connect to access interfaces on Switch 1. These devices will be DHCP clients. Before you configure DHCP snooping, DAI, and MAC limiting port security features, be sure you have: • Connected the DHCP server to Switch 2. • Configured the VLAN employee-vlan on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070. Overview and Topology Ethernet LANs are vulnerable to address spoofing and DoS attacks on network devices. To protect the devices from such attacks, you can configure: • DHCP snooping to validate DHCP server messages • DAI to protect against ARP spoofing • MAC limiting to constrain the number of MAC addresses the switch adds to its MAC address cache This example shows how to configure these port security features on a J-EX4200 switch, which is Switch 1 in this example. Switch 1 is connected to a switch that is not configured with port security features. That second switch (Switch 2) is connected to a DHCP server. (See Figure 73 on page 2595. ) Network devices (hosts) that are connected to Switch 1 will send requests for IP addresses (that is, the devices will be DHCP clients). Those requests will be transmitted from Switch 1 to Switch 2 and then to the DHCP server connected to Switch 2. Responses to the requests will be transmitted along the reverse path of the one followed by the requests. The setup for this example includes the VLAN employee-vlan on both switches. Figure 73 on page 2595 shows the network topology for the example. 2594 Chapter 94: Examples: Port Security Configuration Figure 73: Network Topology for Port Security Setup with Two Switches on the Same VLAN The components of the topology for this example are shown in Table 327 on page 2595. Table 327: Components of Port Security Setup on Switch 1 with a DHCP Server Connected to Switch 2 Properties Settings Switch hardware One J-EX4200-24T (Switch 1), and an additional J-EX Series switch (Switch 2) VLAN name and ID employee-vlan, tag 20 VLAN subnets 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is subnet's broadcast address Trunk interface on both switches ge-0/0/11 Access interfaces on Switch 1 ge-0/0/1, ge-0/0/2, and ge-0/0/3 Access interface on Switch 2 ge-0/0/1 Interface for DHCP server ge-0/0/1 on Switch 2 Switch 1 is initially configured with the default port security setup. In the default configuration on the switch: 2595 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Secure port access is activated on the switch. • The switch does not drop any packets, which is the default setting. • DHCP snooping and dynamic ARP inspection (DAI) are disabled on all VLANs. • All access interfaces are untrusted and trunk interfaces are trusted; these are the default settings. In the configuration tasks for this example, you configure a VLAN on both switches. In addition to configuring the VLAN, you enable DHCP snooping on Switch 1. In this example, you will also enable DAI and a MAC limit of 5 on Switch 1. Because the interface that connects Switch 2 to Switch 1 is a trunk interface, you do not have to configure this interface to be trusted. As noted above, trunk interfaces are automatically trusted, so DHCP messages coming from the DHCP server to Switch 2 and then on to Switch 1 are trusted. Configuring a VLAN, Interfaces, and Port Security Features on Switch 1 To configure a VLAN, interfaces, and port security features on Switch 1: CLI Quick Configuration To quickly configure a VLAN, interfaces, and port security features, copy the following commands and paste them into the switch terminal window: [edit] set ethernet-switching-options secure-access-port interface ge-0/0/1 mac–limit 5 set ethernet-switching-options secure-access-port vlan employee-vlan arp–inspection set ethernet-switching-options secure-access-port vlan employee-vlan examine–dhcp set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members 20 set interfaces ge-0/0/2 unit 0 family ethernet-switching vlan members 20 set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members 20 set interfaces ge-0/0/11 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/11 unit 0 family ethernet-switching vlan members 20 set vlans employee–vlan vlan-id 20 Step-by-Step Procedure To configure MAC limiting, a VLAN, and interfaces on Switch 1 and enable DAI and DHCP on the VLAN: 1. Configure the VLAN employee-vlan with VLAN ID 20: [edit vlans] user@switch1# set employee-vlan vlan-id 20 2. Configure an interface on Switch 1 as a trunk interface: [edit interfaces] user@switch1# set ge-0/0/11 unit 0 family ethernet-switching port-mode trunk 3. Associate the VLAN with interfaces ge-0/0/1, ge-0/0/2, ge-0/0/3, and ge-0/0/11: [edit interfaces] user@switch1# set ge-0/0/1 unit 0 family ethernet-switching vlan members 20 user@switch1# set ge-0/0/2 unit 0 family ethernet-switching vlan members 20 user@switch1# set ge-0/0/3 unit 0 family ethernet-switching vlan members 20 user@switch1# set ge-0/0/11 unit 0 family ethernet-switching vlan members 20 4. Enable DHCP snooping on the VLAN: [edit ethernet-switching-options secure-access-port] 2596 Chapter 94: Examples: Port Security Configuration user@switch1# set vlan employee-vlan examine-dhcp 5. Enable DAI on the VLAN: [edit ethernet-switching-options secure-access-port] user@switch1# set vlan employee-vlan arp-inspection 6. Configure a MAC limit of 5 on ge-0/0/1 and use the default action, drop (packets with new addresses are dropped if the limit has been exceeded): [edit ethernet-switching-options secure-access-port] user@switch1# set interface ge-0/0/1 mac-limit 5 Results Display the results of the configuration: [edit] user@switch1# show ethernet-switching-options { secure-access-port { interface ge-0/0/1.0{ mac-limit 5 action drop; } vlan employee-vlan { arp-inspection; examine-dhcp; } } } interfaces { ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members 20; } } } } ge-0/0/2 { unit 0 { family ethernet-switching { vlan { members 20; } } } } ge-0/0/3 { unit 0 { family ethernet-switching { vlan { members 20; } } } } 2597 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/11 { unit 0 { family ethernet-switching { port-mode trunk; vlan { members 20; } } } } } vlans { employee-vlan { vlan-id 20; } } Configuring a VLAN and Interfaces on Switch 2 To configure the VLAN and interfaces on Switch 2: CLI Quick Configuration To quickly configure the VLAN and interfaces on Switch 2, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/0/1 unit 0 family ethernet-switching port-mode trunk set interfaces ge-0/0/11 unit 0 family ethernet-switching port-mode trunk set vlans employee-vlan vlan-id 20 Step-by-Step Procedure To configure the VLAN and interfaces on Switch 2: 1. Configure an interface on Switch 2 as a trunk interface: [edit interfaces] user@switch2# set ge-0/0/11 unit 0 ethernet-switching port-mode trunk 2. Associate the VLAN with interfaces ge-0/0/1 and ge-0/0/11: [edit interfaces] user@switch2# set ge-0/0/1 unit 0 family ethernet-switching vlan members 20 user@switch2# set ge-0/0/11 unit 0 family ethernet-switching vlan members 20 Results Display the results of the configuration: [edit] user@switch2# show interfaces { ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members 20; } } } } ge-0/0/11 { 2598 Chapter 94: Examples: Port Security Configuration unit 0 { family ethernet-switching { port-mode trunk; vlan { members 20; } } } } } vlans { employee-vlan { vlan-id 20; } } Verification To confirm that the configuration is working properly: • Verifying That DHCP Snooping Is Working Correctly on Switch 1 on page 2599 • Verifying That DAI Is Working Correctly on Switch 1 on page 2599 • Verifying That MAC Limiting Is Working Correctly on Switch 1 on page 2600 Verifying That DHCP Snooping Is Working Correctly on Switch 1 Purpose Action Verify that DHCP snooping is working on Switch 1. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the interface through which Switch 2 sends the DHCP server replies to clients connected to Switch 1 is trusted. The server has provided the IP addresses and leases: user@switch1> show dhcp snooping binding DHCP Snooping Information: MAC Address IP Address Lease -----------------------------00:05:85:3A:82:77 192.0.2.17 600 00:05:85:3A:82:79 192.0.2.18 653 00:05:85:3A:82:80 192.0.2.19 720 00:05:85:3A:82:81 192.0.2.20 932 00:05:85:3A:82:83 192.0.2.21 1230 00:05:85:3A:82:90 192.0.2.20 932 00:05:85:3A:82:91 192.0.2.21 1230 Meaning Type ---dynamic dynamic dynamic dynamic dynamic dynamic dynamic VLAN ---employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan Interface --------ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/3.0 The output shows, for each MAC address, the assigned IP address and lease time—that is, the time, in seconds, remaining before the lease expires. Verifying That DAI Is Working Correctly on Switch 1 Purpose Verify that DAI is working on Switch 1. 2599 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Action Send some ARP requests from network devices connected to the switch. Display the DAI information: user@switch1> show arp inspection statistics ARP inspection statistics: Interface Packets received ARP inspection pass ---------–-------------–- ------------------ge-0/0/1.0 7 5 ge-0/0/2.0 10 10 ge-0/0/3.0 18 15 Meaning ARP inspection failed --------------------2 0 3 The sample output shows the number of ARP packets received and inspected per interface, with a listing of how many packets passed and how many failed the inspection on each interface. The switch compares the ARP requests and replies against the entries in the DHCP snooping database. If a MAC address or IP address in the ARP packet does not match a valid entry in the database, the packet is dropped. Verifying That MAC Limiting Is Working Correctly on Switch 1 Purpose Action Verify that MAC limiting is working on Switch 1. Display the MAC addresses that are learned when DHCP requests are sent from hosts on ge-0/0/1: user@switch1> show ethernet-switching table Ethernet-switching table: 6 entries, 5 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning Related Documentation 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 * Learn Learn Learn Learn Learn Flood Age Interfaces 0 0 0 0 0 - ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/1.0 The sample output shows that five MAC addresses have been learned for interface ge-0/0/1, which corresponds to the MAC limit of 5 set in the configuration. The last line of the output shows that a sixth MAC address request was dropped, as indicated by the asterisk (*) in the MAC address column. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring Port Security (CLI Procedure) on page 2626 • Configuring Port Security (J-Web Procedure) on page 2627 Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces Ethernet LAN switches are vulnerable to attacks that involve spoofing (forging) of source IP addresses or source MAC addresses. These spoofed packets are sent from hosts 2600 Chapter 94: Examples: Port Security Configuration connected to untrusted access interfaces on the switch. You can enable the IP source guard port security feature on J-EX Series switches to mitigate the effects of such attacks. If IP source guard determines that a source IP address and a source MAC address in a binding in an incoming packet are not valid, the switch does not forward the packet. You can use IP source guard in combination with other J-EX Series switch features to mitigate address-spoofing attacks on untrusted access interfaces. This example shows two configuration scenarios: • Requirements on page 2601 • Overview and Topology on page 2601 • Configuring IP Source Guard with 802.1X Authentication, DHCP Snooping, and Dynamic ARP Inspection on page 2602 • Configuring IP Source Guard on a Guest VLAN on page 2604 • Verification on page 2607 Requirements This example uses the following hardware and software components: • A J-EX4200-24T switch • A DHCP server to provide IP addresses to network devices on the switch • A RADIUS server to provide 802.1X authentication Before you configure IP source guard for these scenarios, be sure you have: • Connected the DHCP server to the switch. • Connected the RADIUS server and configured user authentication on the RADIUS server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Configured the VLANs on the switch. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070 for detailed information about configuring VLANs. Overview and Topology IP source guard checks the IP source address and MAC source address in a packet sent from a host attached to an untrusted access interface on the switch. If IP source guard determines that the packet header contains an invalid source IP address or source MAC address, it ensures that the switch does not forward the packet—that is, the packet is discarded. When you configure IP source guard, you enable on it on one or more VLANs. IP source guard applies its checking rules to untrusted access interfaces on those VLANs. By default, on J-EX Series switches, access interfaces are untrusted and trunk interfaces are trusted. IP source guard does not check packets that have been sent to the switch by devices connected to either trunk interfaces or trusted access interfaces—that is, interfaces 2601 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS configured with dhcp-trusted so that a DHCP server can be connected to that interface to provide dynamic IP addresses. IP source guard obtains information about IP-address/MAC-address/VLAN bindings from the DHCP snooping database. It causes the switch to validate incoming IP packets against the entries in that database. The topology for this example includes a J-EX4200-24P switch, a connection to a DHCP server, and a connection to a RADIUS server for user authentication. NOTE: The 802.1X user authentication applied in this example is for single supplicants. Single-secure supplicant mode and multiple supplicant mode do not work with IP source guard. For more information about 802.1X authentication, see “Understanding Authentication on J-EX Series Switches” on page 2248. In the first example configuration, two clients (network devices) are connected to an access switch. You configure IP source guard and 802.1X user authentication, in combination with two access port security features: DHCP snooping and dynamic ARP inspection (DAI). This setup is designed to protect the switch from IP attacks such as “ping of death” attacks, DHCP starvation, and ARP spoofing. In the second example configuration, the switch is configured for 802.1X user authentication. If the client fails authentication, the switch redirects the client to a guest VLAN that allows this client to access a set of restricted network features. You configure IP source guard on the guest VLAN to mitigate effects of source IP spoofing. NOTE: Control-plane rate limiting is achieved by restricting CPU control-plane protection. It can be used in conjunction with storm control (see “Understanding Storm Control on J-EX Series Switches” on page 2511) to limit data-plane activity. TIP: You can set the ip-source-guard flag in the traceoptions statement for debugging purposes. Configuring IP Source Guard with 802.1X Authentication, DHCP Snooping, and Dynamic ARP Inspection CLI Quick Configuration To quickly configure IP source guard with 802.1X authentication and with other access port security features, copy the following commands and paste them into the switch terminal window: [edit] set ethernet-switching-options secure-access-port interface ge-0/0/24 dhcp-trusted set ethernet-switching-options secure-access-port vlan data examine-dhcp set ethernet-switching-options secure-access-port vlan data arp-inspection set ethernet-switching-options secure-access-port vlan data ip-source-guard 2602 Chapter 94: Examples: Port Security Configuration set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members data set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members data set interfaces ge-0/0/24 unit 0 family ethernet-switching vlan members data set protocols lldp-med interface ge-0/0/0.0 set protocols dot1x authenticator authentication-profile-name profile52 set protocols dot1x authenticator interface ge-0/0/0.0 supplicant single set protocols lldp-med interface ge-0/0/1.0 set protocols dot1x authenticator interface ge-0/0/1.0 supplicant single Step-by-Step Procedure To configure IP source guard with 802.1X authentication and various port security features: 1. Configure the interface on which the DHCP server is connected to the switch as a trusted interface and add that interface to the data VLAN: [edit ethernet-switching-options] user@switch# set secure-access-port interface ge-0/0/24 dhcp-trusted user@switch# set set ge-0/0/24 unit 0 family ethernet-switching vlan members data 2. Associate two interfaces with the data VLAN: [edit interfaces] user@switch# set ge-0/0/0 unit 0 family ethernet-switching vlan members data user@switch# set ge-0/0/1 unit 0 family ethernet-switching vlan members data 3. Configure 802.1X user authentication and LLDP-MED on the two interfaces that you associated with the data VLAN: [edit protocols] user@switch# set lldp-med interface ge-0/0/0.0 user@switch# set dot1x authenticator authentication-profile-name profile52 user@switch# set dot1x authenticator interface ge-0/0/0.0 supplicant single user@switch# set lldp-med interface ge-0/0/1.0 user@switch# set dot1x authenticator interface ge-0/0/1.0 supplicant single 4. Configure three access port security features—DHCP snooping, dynamic ARP inspection (DAI), and IP source guard—on the data VLAN: [edit ethernet-switching-options] user@switch# set secure-access-port vlan data examine-dhcp user@switch# set secure-access-port vlan data arp-inspection user@switch# set secure-access-port vlan data ip-source-guard Results Check the results of the configuration: [edit ethernet-switching-options] secure-access-port { interface ge-0/0/24.0 { dhcp-trusted; } vlan data { arp-inspection; examine-dhcp; ip-source-guard; } } [edit interfaces] ge-0/0/0 { unit 0 { 2603 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS family ethernet-switching { vlan { members data; } } } } ge-0/0/1 { unit 0 { family ethernet-switching { vlan { members data; } } } } ge-0/0/24 { unit 0 { family ethernet-switching { vlan { members data; } } } } [edit protocols] lldp-med { interface ge-0/0/14.0; interface ge-0/0/0.0; interface ge-0/0/1.0; } dot1x { authenticator { authentication-profile-name profile52; } interface { ge-0/0/0.0 { supplicant single; } ge-0/0/1.0 { supplicant single; } ge-0/0/14.0 { supplicant single; } } } Configuring IP Source Guard on a Guest VLAN CLI Quick Configuration To quickly configure IP source guard on a guest VLAN, copy the following commands and paste them into the switch terminal window: [edit] set ethernet-switching-options secure-access-port interface ge-0/0/24 dhcp-trusted set interfaces ge-0/0/24 unit 0 family ethernet-switching vlan members employee 2604 Chapter 94: Examples: Port Security Configuration set ethernet-switching-options secure-access-port vlan employee examine-dhcp set ethernet-switching-options secure-access-port vlan employee ip-source-guard set ethernet-switching-options secure-access-port interface ge-0/0/0 static-ip 11.1.1.1 mac 00:11:11:11:11:11 vlan employee set ethernet-switching-options secure-access-port interface ge-0/0/1 static-ip 11.1.1.2 mac 00:22:22:22:22:22 vlan employee set interfaces ge-0/0/0 unit 0 family ethernet-switching port-mode access set interfaces ge-0/0/1 unit 0 family ethernet-switching port-mode access set protocols dot1x authenticator authentication-profile-name profile52 set protocols dot1x authenticator interface ge-0/0/0 supplicant single set protocols dot1x authenticator interface ge-0/0/0 guest-vlan employee set protocols dot1x authenticator interface ge-0/0/0 supplicant-timeout 2 set protocols dot1x authenticator interface ge-0/0/1 supplicant single set protocols dot1x authenticator interface ge-0/0/1 guest-vlan employee set protocols dot1x authenticator interface ge-0/0/1 supplicant-timeout 2 set vlans employee vlan-id 300 Step-by-Step Procedure To configure IP source guard on a guest VLAN: 1. Configure the interface on which the DHCP server is connected to the switch as a trusted interface and add that interface to the employee VLAN: [edit ethernet-switching-options] user@switch# set secure-access-port interface ge-0/0/24 dhcp-trusted user@switch# set ge-0/0/24 unit 0 family ethernet-switching vlan members employee 2. Configure two interfaces for the access port mode: [edit interfaces] user@switch# set ge-0/0/0 unit 0 family ethernet-switching port-mode access user@switch# set ge-0/0/1 unit 0 family ethernet-switching port-mode access 3. Configure DHCP snooping and IP source guard on the employee VLAN: [edit ethernet-switching-options] user@switch# set secure-access-port vlan employee examine-dhcp user@switch# set secure-access-port vlan employee ip-source-guard 4. Configure a static IP address on each of two interfaces on the employee VLAN (optional): [edit ethernet-switching-options] user@switch# set secure-access-port interface ge-0/0/0 static-ip 11.1.1.1 mac 00:11:11:11:11:11 vlan employee [edit ethernet-switching-options] user@switch# set secure-access-port interface ge-0/0/1 static-ip 11.1.1.2 mac 00:22:22:22:22:22 vlan employee 5. Configure 802.1X user authentication: [edit protocols] user@switch# set dot1x authenticator authentication-profile-name profile52 user@switch# set dot1x authenticator interface ge-0/0/0 supplicant single user@switch# set dot1x authenticator interface ge-0/0/1 supplicant single user@switch# set dot1x authenticator interface ge-0/0/0 supplicant-timeout 2 user@switch# set dot1x authenticator interface ge-0/0/1 supplicant-timeout 2 6. Set the VLAN ID for the employee VLAN: [edit vlans] user@switch# set employee vlan-id 100 2605 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Results Check the results of the configuration: [edit protocols] dot1x { authenticator { authentication-profile-name profile52; } interface { ge-0/0/0.0 { guest-vlan employee; supplicant single; supplicant-timeout 2; } ge-0/0/1.0 { guest-vlan employee; supplicant single; supplicant-timeout 2; } } } } [edit vlans] employee { vlan-id 100; } [edit interfaces] ge-0/0/0 { unit 0 { family ethernet-switching { port-mode access; } } } ge-0/0/1 { unit 0 { family ethernet-switching { port-mode access; } } } ge-0/0/24 { unit 0 { family ethernet-switching { vlan { members employee; } } } } [edit ethernet-switching-options] secure-access-port { interface ge-0/0/0.0 { static-ip 11.1.1.1 vlan employee mac 00:11:11:11:11:11; 2606 Chapter 94: Examples: Port Security Configuration } interface ge-0/0/1.0 { static-ip 11.1.1.2 vlan employee mac 00:22:22:22:22:22; } interface ge-0/0/24.0 { dhcp-trusted; } vlan employee { examine-dhcp; ip-source-guard; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That 802.1X User Authentication Is Working on the Interface on page 2607 • Verifying the VLAN Association with the Interface on page 2607 • Verifying That DHCP Snooping and IP Source Guard Are Working on the VLAN on page 2607 Verifying That 802.1X User Authentication Is Working on the Interface Purpose Action Meaning Verify that the 802.1X configuration is working on the interface. Use the show dot1x interface command to view the 802.1X details. The Supplicant mode output field displays the configured administrative mode for each interface. Verifying the VLAN Association with the Interface Purpose Action Meaning Verity interface states and VLAN memberships. Use the show ethernet-switching interfaces command to view the Ethernet switching table entries. The field VLAN members shows the associations between VLANs and interfaces. The State field shows whether the interfaces are up or down. For the guest VLAN configuration, the interface is associated with the guest VLAN if and when the supplicant fails 802.1X user authentication. Verifying That DHCP Snooping and IP Source Guard Are Working on the VLAN Purpose Action Verify that DHCP snooping and IP source guard are enabled and working on the VLAN. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. 2607 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Use the show dhcp snooping binding command to display the DHCP snooping information when the interface on which the DHCP server connects to the switch is trusted. View the MAC addresses from which requests were sent and the IP addresses and leases provided by the server. Use the show ip-source-guard command to view IP source guard information for the VLAN. Meaning When the interface on which the DHCP server connects to the switch has been set to trusted, the output shows, for each MAC address, the assigned IP address and lease time—that is, the time, in seconds, remaining before the lease expires. Static IP addresses have no assigned lease time. Statically configured entries never expire. The IP source guard database table contains the VLANs enabled for IP source guard, the untrusted access interfaces on those VLANs, the VLAN 802.1Q tag IDs if there are any, and the IP addresses and MAC addresses that are bound to one another. If a switch interface is associated with multiple VLANs and some of those VLANs are enabled for IP source guard and others are not, the VLANs that are not enabled for IP source guard have a star (*) in the IP Address and MAC Address fields. Related Documentation • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Configuring IP Source Guard (CLI Procedure) on page 2643 Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN Ethernet LAN switches are vulnerable to attacks that involve spoofing (forging) of source IP addresses or source MAC addresses. These spoofed packets are sent from hosts connected to untrusted access interfaces on the switch. You can enable the IP source guard port security feature on J-EX Series switches to mitigate the effects of such attacks. If IP source guard determines that a source IP address and a source MAC address in a binding in an incoming packet are not valid, the switch does not forward the packet. If two VLANs share an interface, you can configure IP source guard on just one of the VLANs; in this example, you configure IP source guard on an untagged data VLAN but not on the tagged voice VLAN. You can use 802.1X user authentication to validate the device connections on the data VLAN. 2608 Chapter 94: Examples: Port Security Configuration This example describes how to configure IP source guard with 802.1X user authentication on a data VLAN, with a voice VLAN on the same interface: • Requirements on page 2609 • Overview and Topology on page 2609 • Configuration on page 2610 • Verification on page 2612 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch • A RADIUS server to provide 802.1X authentication Before you configure IP source guard for the data VLANs, be sure you have: • Connected the DHCP server to the switch. • Connected the RADIUS server to the switch and configured user authentication on the server. See “Example: Connecting a RADIUS Server for 802.1X to a J-EX Series Switch” on page 2267. • Configured the VLANs. See “Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches” on page 1070 for detailed information about configuring VLANs. Overview and Topology IP source guard checks the IP source address and MAC source address in a packet sent from a host attached to an untrusted access interface on the switch. If IP source guard determines that the packet header contains an invalid source IP address or source MAC address, it ensures that the switch does not forward the packet—that is, the packet is discarded. When you configure IP source guard, you enable on it on one or more VLANs. IP source guard applies its checking rules to untrusted access interfaces on those VLANs. By default, on J-EX Series switches, access interfaces are untrusted and trunk interfaces are trusted. IP source guard does not check packets that have been sent to the switch by devices connected to either trunk interfaces or trusted access interfaces—that is, interfaces configured with dhcp-trusted so that a DHCP server can be connected to that interface to provide dynamic IP addresses. IP source guard obtains information about IP-address/MAC-address/VLAN bindings from the DHCP snooping database. It causes the switch to validate incoming IP packets against the entries in that database. The topology for this example includes one J-EX4200-24T switch, a PC and an IP phone connected on the same interface, a connection to a DHCP server, and a connection to a RADIUS server for user authentication. 2609 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: The 802.1X user authentication applied in this example is for single supplicants. Single-secure supplicant mode and multiple supplicant mode do not work with IP source guard. For more information about 802.1X authentication, see “Understanding Authentication on J-EX Series Switches” on page 2248. TIP: You can set the ip-source-guard flag in the traceoptions statement for debugging purposes. This example shows how to configure a static IP address to be added to the DHCP snooping database. Configuration CLI Quick Configuration To quickly configure IP source guard on a data VLAN, copy the following commands and paste them into the switch terminal window: set ethernet-switching-options voip interface ge-0/0/14.0 vlan voice set ethernet-switching-options secure-access-port interface ge-0/0/24.0 dhcp-trusted set ethernet-switching-options secure-access-port interface ge-0/0/14 static-ip 11.1.1.1 mac 00:11:11:11:11:11 vlan data set ethernet-switching-options secure-access-port vlan data examine-dhcp set ethernet-switching-options secure-access-port vlan data ip-source-guard set interfaces ge-0/0/24 unit 0 family ethernet-switching vlan members data set vlans voice vlan-id 100 set protocols lldp-med interface ge-0/0/14.0 set protocols dot1x authenticator authentication-profile-name profile52 set protocols dot1x authenticator interface ge-0/0/14.0 supplicant single Step-by-Step Procedure To configure IP source guard on the data VLAN: 1. Configure the VoIP interface: [edit ethernet-switching-options] user@switch# set voip interface ge-0/0/14.0 vlan voice 2. Configure the interface on which the DHCP server is connected to the switch as a trusted interface and add that interface to the data VLAN: [edit ethernet-switching-options] user@switch# set secure-access-port interface ge-0/0/24.0 dhcp-trusted [edit interfaces] user@switch# set ge-0/0/24 unit 0 family ethernet-switching vlan members data 3. Configure a static IP address on an interface on the data VLAN (optional) [edit ethernet-switching-options] user@switch# set secure-access-port interface ge-0/0/14 static-ip 11.1.1.1 mac 00:11:11:11:11:11 vlan data 4. Configure DHCP snooping and IP source guard on the data VLAN: [edit ethernet-switching-options] user@switch# set secure-access-port vlan data examine-dhcp user@switch# set secure-access-port vlan data ip-source-guard 2610 Chapter 94: Examples: Port Security Configuration 5. Configure 802.1X user authentication and LLDP-MED on the interface that is shared by the data VLAN and the voice VLAN: [edit protocols] user@switch# set lldp-med interface ge-0/0/14.0 user@switch# set dot1x authenticator authentication-profile-name profile52 user@switch# set dot1x authenticator interface ge-0/0/14.0 supplicant single 6. Set the VLAN ID for the voice VLAN: [edit vlans] user@switch# set voice vlan-id 100 Results Check the results of the configuration: [edit ethernet-switching-options] user@switch# show voip { interface ge-0/0/14.0 { vlan voice; } } secure-access-port { interface ge-0/0/14.0 { static-ip 11.1.1.1 vlan data mac 00:11:11:11:11:11; } interface ge-0/0/24.0 { dhcp-trusted; } vlan data { examine-dhcp; ip-source-guard; } } [edit interfaces] ge-0/0/24 { unit 0 { family ethernet-switching { vlan { members data; } } } } [edit vlans] voice { vlan-id 100; } [edit protocols] lldp-med { interface ge-0/0/14.0; } dot1x { authenticator { 2611 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS authentication-profile-name profile52; interface { ge-0/0/14.0 { supplicant single; } } } } TIP: If you wanted to configure IP source guard on the voice VLAN as well as on the data VLAN, you would configure DHCP snooping and IP source guard exactly as you did for the data VLAN. The configuration result for the voice VLAN under secure-access-port would look like this: secure-access-port { vlan voice { examine-dhcp; ip-source-guard; } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That 802.1X User Authentication Is Working on the Interface on page 2612 • Verifying the VLAN Association with the Interface on page 2613 • Verifying That DHCP Snooping and IP Source Guard Are Working on the Data VLAN on page 2613 Verifying That 802.1X User Authentication Is Working on the Interface Purpose Action Verify the 802.1X configuration on interface ge-0/0/14. Verify the 802.1X configuration with the operational mode command show dot1x interface: user@switch> show dot1x interface ge-0/0/14.0 detail ge-0/0/14.0 Role: Authenticator Administrative state: Auto Supplicant mode: Single Number of retries: 3 Quiet period: 60 seconds Transmit period: 30 seconds Mac Radius: Disabled Mac Radius Restrict: Disabled Reauthentication: Enabled Configured Reauthentication interval: 3600 seconds Supplicant timeout: 30 seconds Server timeout: 30 seconds Maximum EAPOL requests: 2 Guest VLAN member: Number of connected supplicants: 1 Supplicant: user101, 00:04:0f:fd:ac:fe 2612 Chapter 94: Examples: Port Security Configuration Operational state: Authenticated Authentication method: Radius Authenticated VLAN: vo11 Dynamic Filter: Session Reauth interval: 60 seconds Reauthentication due in 50 seconds Meaning The Supplicant mode output field displays the configured administrative mode for each interface. Interface ge-0/0/14.0 displays Single supplicant mode. Verifying the VLAN Association with the Interface Purpose Action Display the interface state and VLAN membership. user@switch> show ethernet-switching interfaces Ethernet-switching table: 0 entries, 0 learned user@switch> show ethernet-switching interfaces Interface State VLAN members Blocking ge-0/0/0.0 down default unblocked ge-0/0/1.0 down employee unblocked ge-0/0/2.0 down employee unblocked ge-0/0/12.0 down default unblocked ge-0/0/13.0 down default unblocked ge-0/0/13.0 down vlan100 unblocked ge-0/0/14.0 up voice unblocked data unblocked ge-0/0/17.0 down employee unblocked ge-0/0/23.0 down default unblocked ge-0/0/24.0 down data unblocked employee unblocked vlan100 unblocked voice unblocked Meaning The field VLAN members shows that the ge-0/0/14.0 interface supports both the data VLAN and the voice VLAN. The State field shows that the interface is up. Verifying That DHCP Snooping and IP Source Guard Are Working on the Data VLAN Purpose Action Verify that DHCP snooping and IP source guard are enabled and working on the data VLAN. Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the interface on which the DHCP server connects to the switch is trusted. The following output results when requests are sent from the MAC addresses and the server has provided the IP addresses and leases: user@switch> show dhcp snooping binding 2613 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS DHCP Snooping Information: MAC address IP address Lease (seconds) Type VLAN Interface 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 600 653 720 932 employee employee employee employee ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 192.0.2.17 192.0.2.18 192.0.2.19 192.0.2.20 00:30:48:92:A5:9D vlan100 ge-0/0/13.0 00:30:48:8D:01:3D 10.10.10.9 720 00:30:48:8D:01:5D 10.10.10.8 1230 00:11:11:11:11:11 11.1.1.1 — 00:05:85:27:32:88 192.0.2.22 — 00:05:85:27:32:89 192.0.2.23 — 00:05:85:27:32:90 192.0.2.27 — dynamic dynamic dynamic dynamic 10.10.10.7 720 dynamic dynamic static static static static data voice data employee employee employee dynamic ge-0/0/14.0 ge-0/0/14.0 ge-0/0/14.0 ge-0/0/17.0 ge-0/0/17.0 ge-0/0/17.0 View the IP source guard information for the data VLAN. Meaning user@switch> show ip-source-guard IP source guard information: Interface Tag IP Address MAC Address VLAN ge-0/0/13.0 0 10.10.10.7 00:30:48:92:A5:9D vlan100 ge-0/0/14.0 ge-0/0/14.0 0 0 10.10.10.9 11.1.1.1 00:30:48:8D:01:3D 00:11:11:11:11:11 data data ge–0/0/13.0 100 * * voice When the interface on which the DHCP server connects to the switch has been set to trusted, the output (see the preceding sample output for show dhcp snooping binding) shows, for each MAC address, the assigned IP address and lease time—that is, the time, in seconds, remaining before the lease expires. Static IP addresses have no assigned lease time. Statically configured entries never expire. The IP source guard database table contains the VLANs enabled for IP source guard, the untrusted access interfaces on those VLANs, the VLAN 802.1Q tag IDs if there are any, and the IP addresses and MAC addresses that are bound to one another. If a switch interface is associated with multiple VLANs and some of those VLANs are enabled for IP source guard and others are not, the VLANs that are not enabled for IP source guard have a star (*) in the IP Address and MAC Address fields. See the entry for the voice VLAN in the preceding sample output. Related Documentation 2614 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Setting Up VoIP with 802.1X and LLDP-MED on a J-EX Series Switch on page 2302 • Configuring IP Source Guard (CLI Procedure) on page 2643 Chapter 94: Examples: Port Security Configuration Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server You can use DHCP option 82, also known as the DHCP relay agent information option, to help 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. This example describes how to configure DHCP option 82 on a switch that is on the same VLAN with the DHCP clients but on a different VLAN from the DHCP server; the switch acts as a relay agent: • Requirements on page 2615 • Overview and Topology on page 2615 • Configuration on page 2616 Requirements This example uses the following hardware and software components: • One J-EX4200-24T switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure DHCP option 82 on the switch, be sure you have: • Connected and configured the DHCP server. NOTE: Your DHCP server must be configured to accept DHCP option 82. If it is not configured for DHCP option 82, it does not use the DHCP option 82 information in the requests sent to it when it formulates its reply messages. • Configured the employee VLAN on the switch and associated the interfaces on which the clients connect to the switch with that VLAN. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136. • Configured the corporate VLAN for the DHCP server. • Configured the switch as a BOOTP relay agent. See “DHCP/BOOTP Relay for J-EX Series Switches Overview” on page 446. • Configured the routed VLAN interface (RVI) to allow the switch to relay packets to the server and receive packets from the server. See “Configuring Routed VLAN Interfaces (CLI Procedure)” on page 1137. Overview and Topology If DHCP option 82 is enabled on the switch, then when a network device—a DHCP client—that is connected to the switch on an untrusted interface sends a DHCP request, the switch inserts information about the client's network location into the packet header 2615 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS of that request. The switch then sends the request (in this setting, it relays the request) to the DHCP server. The DHCP server reads the option 82 information in the packet header and uses it to implement the IP address or other parameter for the client. When option 82 is enabled on the switch, then this sequence of events occurs when a DHCP client sends a DHCP request: 1. The switch receives the request and inserts the option 82 information in the packet header. 2. The switch relays the request to the DHCP server. 3. The server uses the DHCP option 82 information to formulate its reply and sends a response back to the switch. It does not alter the option 82 information. 4. The switch strips the option 82 information from the response packet. 5. The switch forwards the response packet to the client. In this example, you configure option 82 on the J-EX Series switch. The switch is configured as a BOOTP relay agent. The switch connects to the DHCP server through the routed VLAN interface (RVI) that you configured. The switch and clients are members of the employee VLAN. The DHCP server is a member of the corporate VLAN. Configuration To configure DHCP option 82: CLI Quick Configuration To quickly configure DHCP option 82, copy the following commands and paste them into the switch terminal window: set forwarding-options helpers bootp dhcp-option82 set forwarding-options helpers bootp dhcp-option82 circuit-id prefix hostname set forwarding-options helpers bootp dhcp-option82 circuit-id use-vlan-id set forwarding-options helpers bootp dhcp-option82 remote-id set forwarding-options helpers bootp dhcp-option82 remote-id prefix mac set forwarding-options helpers bootp dhcp-option82 remote-id use-string employee-switch1 set forwarding-options helpers bootp dhcp-option82 vendor-id Step-by-Step Procedure To configure DHCP option 82: 1. Specify DHCP option 82 for the employee VLAN: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 2. Configure a prefix for the circuit ID suboption (the prefix is always the hostname of the switch): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 circuit-id prefix hostname 3. Specify that the circuit ID suboption value contains the VLAN ID rather than the VLAN name (the default): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 circuit-id use-vlan-id 4. 2616 Specify that the remote ID suboption be included in the DHCP option 82 information: Chapter 94: Examples: Port Security Configuration [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id 5. Configure a prefix for the remote ID suboption (here, the prefix is the MAC address of the switch): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id prefix mac 6. Specify that the remote ID suboption value contains a character string (here, the string is employee-switch1): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id use-string employee-switch1 7. Configure a vendor ID suboption value, and use the default value. To use the default value, do not type a character string after the vendor-id option keyword: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 vendor-id Results Check the results of the configuration: [edit forwarding-options helpers bootp] user@switch# show dhcp-option82 { circuit-id { prefix hostname; use-vlan-id; } remote-id { prefix mac; use-string employee-switch1; } vendor-id; } Related Documentation • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server You can use DHCP option 82, also known as the DHCP relay agent information option, to help 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. 2617 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS This example describes how to configure DHCP option 82 on a switch with DHCP clients, DHCP server, and switch all on the same VLAN: • Requirements on page 2618 • Overview and Topology on page 2618 • Configuration on page 2619 Requirements This example uses the following hardware and software components: • One J-EX Series switch • A DHCP server to provide IP addresses to network devices on the switch Before you configure DHCP option 82 on the switch, be sure you have: • Connected and configured the DHCP server. NOTE: Your DHCP server must be configured to accept DHCP option 82. If it is not configured for DHCP option 82, it does not use the DHCP option 82 information in the requests sent to it when it formulates its reply messages. • Configured the employee VLAN on the switch and associated the interfaces on which the clients and the server connect to the switch with that VLAN. See “Configuring VLANs for J-EX Series Switches (CLI Procedure)” on page 1136. Overview and Topology If DHCP option 82 is enabled on the switch, then when a network device—a DHCP client—that is connected to the switch on an untrusted interface sends a DHCP request, the switch inserts information about the client's network location into the packet header of that request. The switch then sends the request to the DHCP server. The DHCP server reads the option 82 information in the packet header and uses it to implement the IP address or other parameter for the client. DHCP option 82 is enabled on an individual VLAN or on all VLANs on the switch. When option 82 is enabled on the switch, then this sequence of events occurs when a DHCP client sends a DHCP request: 1. The switch receives the request and inserts the option 82 information in the packet header. 2. The switch forwards the request to the DHCP server. 3. The server uses the DHCP option 82 information to formulate its reply and sends a response back to the switch. It does not alter the option 82 information. 4. The switch strips the option 82 information from the response packet. 5. The switch forwards the response packet to the client. 2618 Chapter 94: Examples: Port Security Configuration Figure 74 on page 2619 illustrates the topology for this example. Figure 74: Network Topology for Configuring DHCP Option 82 on a Switch That Is on the Same VLAN as the DHCP Clients and the DHCP Server In this example, you configure DHCP option 82 on the J-EX Series switch. The switch connects to the DHCP server on interface ge-0/0/8. The DHCP clients connect to the switch on interfaces ge-0/0/1, ge-0/0/2, and ge-0/0/3. The switch, server, and clients are all members of the employee VLAN. Configuration To configure DHCP option 82: CLI Quick Configuration To quickly configure DHCP option 82, copy the following commands and paste them into the switch terminal window: set ethernet-switching-options secure-access-port vlan employee dhcp-option82 set ethernet-switching-options secure-access-port vlan employee dhcp-option82 circuit-id prefix hostname set ethernet-switching-options secure-access-port vlan employee dhcp-option82 circuit-id use-vlan-id set ethernet-switching-options secure-access-port vlan employee dhcp-option82 remote-id set ethernet-switching-options secure-access-port vlan employee dhcp-option82 remote-id prefix mac set ethernet-switching-options secure-access-port vlan employee dhcp-option82 remote-id use-string employee-switch1 set ethernet-switching-options secure-access-port vlan employee dhcp-option82 vendor-id 2619 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure DHCP option 82: 1. Specify DHCP option 82 for the employee VLAN: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 2. Configure a prefix for the circuit ID suboption (the prefix is always the hostname of the switch): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 circuit-id prefix hostname 3. Specify that the circuit ID suboption value contains the VLAN ID rather than the VLAN name (the default): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 circuit-id use-vlan-id 4. Specify that the remote ID suboption be included in the DHCP option 82 information: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id 5. Configure a prefix for the remote ID suboption (here, the prefix is the MAC address of the switch): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id prefix mac 6. Specify that the remote ID suboption value contains a character string (here, the string is employee-switch1): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id use-string employee-switch1 7. Configure a vendor ID suboption value, and use the default value. To use the default value, do not type a character string after the vendor-id option keyword: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 vendor-id Results Check the results of the configuration: [edit ethernet-switching-options secure-access-port] user@switch# show vlan employee { dhcp-option82 { circuit-id { prefix hostname; use-vlan-id; } remote-id { prefix mac; use-string employee-switch1; } vendor-id; } } 2620 Chapter 94: Examples: Port Security Configuration Related Documentation • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Example: Configuring Proxy ARP on a J-EX Series Switch You can configure proxy Address Resolution Protocol (ARP) on your J-EX Series switch to enable the switch to respond to ARP queries for network addresses by offering its own MAC address. With proxy ARP enabled, the switch captures and routes traffic to the intended destination. This example shows how to configure proxy ARP on an access switch: • Requirements on page 2621 • Overview and Topology on page 2621 • Configuration on page 2621 • Verification on page 2622 Requirements This example uses the following hardware and software components: • One J-EX Series switch Overview and Topology This example shows the configuration of proxy ARP on an interface of a J-EX Series switch using restricted mode. In restricted mode, the switch does not proxy for hosts on the same subnet. The topology for this example consists of one J-EX Series switch. When a host wants to communicate with a host that is not already in its ARP table, it broadcasts an ARP request for the MAC address of the destination host: • When proxy ARP is not enabled, a host that shares the same IP address replies directly to the ARP request, providing its MAC address, and future transmissions are sent directly to the destination host MAC address. • When proxy ARP is enabled, the switch responds to ARP requests, providing the switch’s MAC address—even when the destination IP address is the same as the source IP address. Thus, communications must be sent through the switch and then routed through the switch to the appropriate destination. Configuration To configure proxy ARP, perform the following tasks: 2621 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS CLI Quick Configuration To quickly configure proxy ARP on an interface, copy the following command and paste it into the switch terminal window: [edit] set interfaces ge-0/0/3 unit 0 proxy-arp restricted Step-by-Step Procedure You configure proxy ARP on individual interfaces. 1. To configure proxy ARP on an interface: [edit interfaces] user@switch# set ge-0/0/3 unit 0 proxy-arp restricted BEST PRACTICE: We recommend that you configure proxy ARP in restricted mode. In restricted mode, the switch does not act as proxy if the source and target IP addresses are on the same subnet. If you use unrestricted mode, disable gratuitous ARP requests on the interface to avoid the situation of the switch’s response to a gratuitous ARP request appearing to the host to be an indication of an IP conflict: [edit interfaces] user@switch# set ge-0/0/3 no-gratuitous-arp-request Results Display the results of the configuration: user@switch> show configuration interfaces { ge-0/0/3 { unit 0 { proxy-arp restricted; family ethernet-switching; } } Verification To verify that the switch is sending proxy ARP messages, perform these tasks: • Verifying That the Switch Is Sending Proxy ARP Messages on page 2622 Verifying That the Switch Is Sending Proxy ARP Messages Purpose Action Verify that the switch is sending proxy ARP messages. List the system statistics for ARP messages: user@switch> show system statistics arp arp: 198319 datagrams received 45 ARP requests received 12 ARP replies received 2 resolution requests received 2 unrestricted proxy requests 0 restricted proxy requests 0 received proxy requests 2622 Chapter 94: Examples: Port Security Configuration 0 proxy requests not proxied 0 restricted-proxy requests not proxied 0 with bogus interface 0 with incorrect length 0 for non-IP protocol 0 with unsupported op code 0 with bad protocol address length 0 with bad hardware address length 0 with multicast source address 0 with multicast target address 0 with my own hardware address 168705 for an address not on the interface 0 with a broadcast source address 0 with source address duplicate to mine 29555 which were not for me 0 packets discarded waiting for resolution 4 packets sent after waiting for resolution 27 ARP requests sent 47 ARP replies sent 0 requests for memory denied 0 requests dropped on entry 0 requests dropped during retry 0 requests dropped due to interface deletion 0 requests on unnumbered interfaces 0 new requests on unnumbered interfaces 0 replies for from unnumbered interfaces 0 requests on unnumbered interface with non-subnetted donor 0 replies from unnumbered interface with non-subnetted donor Meaning Related Documentation The statistics show that two proxy ARP requests were received, and the proxy requests not proxied field indicates that all the unproxied ARP requests received have been proxied by the switch. • Configuring Proxy ARP (CLI Procedure) on page 1153 • Understanding Proxy ARP on J-EX Series Switches on page 1059 2623 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2624 CHAPTER 95 Configuring Port Security • Configuring Port Security (CLI Procedure) on page 2626 • Configuring Port Security (J-Web Procedure) on page 2627 • Enabling DHCP Snooping (CLI Procedure) on page 2630 • Enabling DHCP Snooping (J-Web Procedure) on page 2631 • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Enabling a Trusted DHCP Server (J-Web Procedure) on page 2632 • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Enabling Dynamic ARP Inspection (J-Web Procedure) on page 2634 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 • Configuring MAC Move Limiting (CLI Procedure) on page 2639 • Configuring MAC Move Limiting (J-Web Procedure) on page 2641 • Setting the none Action on an Interface to Override a MAC Limit Applied to All Interfaces (CLI Procedure) on page 2642 • Configuring IP Source Guard (CLI Procedure) on page 2643 • Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) on page 2645 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Configuring Proxy ARP (CLI Procedure) on page 2651 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2652 2625 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring Port Security (CLI Procedure) Ethernet LANs are vulnerable to attacks such as address spoofing and Layer 2 denial of service (DoS) on network devices. Port security features such as DHCP snooping, DAI (dynamic ARP inspection), MAC limiting, and MAC move limiting, as well as trusted DHCP server, help protect the access ports on your J-EX Series switch against the losses of information and productivity that can result from such attacks. To configure port security features using the CLI: 1. Enable DHCP snooping: • On a specific VLAN: [edit ethernet-switching-options secure-access port] user@switch# set vlan default examine-dhcp • On all VLANs: [edit ethernet-switching-options secure-access port] user@switch# set vlan all examine-dhcp 2. Enable DAI: • On a single VLAN (here, the VLAN is employee-vlan): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee–vlan arp-inspection • On all VLANs: [edit ethernet-switching-options secure-access-port] user@switch# set vlan all arp-inspection 3. Limit the number of dynamic MAC addresses and specify the action to take if the limit is exceeded—for example, set a MAC limit of 5 with an action of drop: • On a single interface (here, the interface is ge-0/0/1): [edit ethernet-switching-options secure-access-port] user@switch# set interface ge–0/0/1 mac-limit 5 action drop • On all interfaces: [edit ethernet-switching-options secure-access-port] user@switch# set interface all mac–limit 5 action drop 4. Specify allowed MAC addresses: • On a single interface (here, the interface is ge-0/0/2): [edit ethernet-switching-options secure-access-port] user@switch# set interface ge–0/0/2 allowed-mac 00:05:85:3A:82:80 user@switch# set interface ge–0/0/2 allowed-mac 00:05:85:3A:82:81 user@switch# set interface ge–0/0/2 allowed-mac 00:05:85:3A:82:83 • 2626 On all interfaces: Chapter 95: Configuring Port Security [edit ethernet-switching-options secure-access-port] user@switch# set interface all allowed-mac 00:05:85:3A:82:80 user@switch# set interface all allowed-mac 00:05:85:3A:82:81 user@switch# set interface all allowed-mac 00:05:85:3A:82:83 5. Limit the number of times a MAC address can move from its original interface in one second—for example, set a MAC move limit of 5 with an action of drop if the limit is exceeded: • On a single VLAN (here, the VLAN is employee-vlan): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee–vlan mac-move-limit 5 action drop • On all VLANs: [edit ethernet-switching-options secure-access-port] user@switch# set vlan all mac–move-limit 5 action drop 6. Configure a trusted DHCP server on an interface (here, the interface is ge-0/0/8): [edit ethernet-switching-options secure-access port] user@switch# set interface ge–0/0/8 dhcp-trusted Related Documentation • Configuring Port Security (J-Web Procedure) on page 2627 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Monitoring Port Security on page 2653 • Port Security for J-EX Series Switches Overview on page 2545 Configuring Port Security (J-Web Procedure) To configure port security on a J-EX Series switch using the J-Web interface: 1. Select Configure > Security > Port Security. The VLAN List table lists all the VLAN names, VLAN identifiers, port members, and port security VLAN features. The Interface List table lists all the ports and indicates whether security features have been enabled on the ports. 2627 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 334 for details about all commit options. 2. Click one: • Edit—Click this option to modify the security features for the selected port or VLAN. Enter information as specified in Table 328 on page 2628 to modify Port Security settings on VLANs. Enter information as specified in Table 329 on page 2629 to modify Port Security settings on interfaces. • Activate/Deactivate—Click this option to enable or disable security on the switch. Table 328: Port Security Settings on VLANs Field Function Your Action Enable DHCP Snooping on VLAN Allows the switch to monitor and control DHCP messages received from untrusted devices connected to the switch. Builds and maintains a database of valid IP addresses/MAC address bindings. (By default, access ports are untrusted and trunk ports are trusted.) Select to enable DHCP snooping on a specified VLAN or all VLANs. Enable ARP Inspection on VLAN Uses information in the DHCP snooping database to validate ARP packets on the LAN and protect against ARP cache poisoning. Select to enable ARP inspection on a specified VLAN or all VLANs. (Configure any port on which you do not want ARP inspection to occur as a trusted DHCP server port.) MAC Movement Specifies the number of times per second that a MAC address can move to a new interface. Enter a number. The default is unlimited. MAC Movement Action Specifies the action to be taken if the MAC move limit is exceeded. Select one: 2628 TIP: For private VLANs (PVLANs), enable DHCP snooping on the primary VLAN. If you enable DHCP snooping only on a community VLAN, DHCP messages coming from PVLAN trunk ports are not snooped. • Log—Generate a system log entry, an SNMP trap, or an alarm. • Drop—Drop the packets and generate a system log entry, an SNMP trap, or an alarm (default). • Shutdown—Shut down the VLAN and generate an alarm. You can mitigate the effect of this option by configuring autorecovery from the disabled state and specifying a disable timeout value. See “Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure)” on page 2516. • None—No action to be taken. Chapter 95: Configuring Port Security Table 329: Port Security on Interfaces Field Function Your Action Trust DHCP Specifies trusting DHCP packets on the selected interface. By default, trunk ports are dhcp-trusted. Select to enable DHCP trust. MAC Limit Specifies the number of MAC addresses that can be learned on a single Layer 2 access port. This option is not valid for trunk ports. Enter a number. MAC Limit Action Specifies the action to be taken if the MAC limit is exceeded. This option is not valid for trunk ports. Select one: Allowed MAC List Specifies the MAC addresses that are allowed for the interface. • Log—Generate a system log entry, an SNMP trap, or an alarm. • Drop—Drop the packets and generate a system log entry, an SNMP trap, or an alarm. (Default) • Shutdown—Shut down the interface and generate an alarm. You can mitigate the effect of this option by configuring autorecovery from the disabled state and specifying a disable timeout value. See “Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure).” on page 2516 • None—No action to be taken. To add a MAC address: 1. Click Add. 2. Enter the MAC address. 3. Click OK. Related Documentation • Configuring Port Security (CLI Procedure) on page 2626 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Monitoring Port Security on page 2653 • Port Security for J-EX Series Switches Overview on page 2545 2629 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Enabling DHCP Snooping (CLI Procedure) DHCP snooping allows the switch to monitor and control DHCP messages received from untrusted devices connected to the J-EX Series switch. It builds and maintains a database of valid IP-address/MAC-address (IP-MAC) bindings called the DHCP snooping database. You configure DHCP snooping for each VLAN, not for each interface (port). By default, DHCP snooping is disabled for all VLANs. To enable DHCP snooping on a VLAN or all VLANs by using the CLI: • On a specific VLAN (here, the VLAN is default): [edit ethernet-switching-options secure-access port] user@switch# set vlan default examine-dhcp • On all VLANs: [edit ethernet-switching-options secure-access port] user@switch# set vlan all examine-dhcp TIP: By default, the IP-MAC bindings are lost when the switch is rebooted and DHCP clients (the network devices, or hosts) must reacquire bindings. However, you can configure the bindings to persist by setting the dhcp-snooping-file statement to store the database file either locally or remotely. TIP: For private VLANs (PVLANs), enable DHCP snooping on the primary VLAN. If you enable DHCP snooping only on a community VLAN, DHCP messages coming from PVLAN trunk ports are not snooped. Related Documentation 2630 • Enabling DHCP Snooping (J-Web Procedure) on page 2631 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Verifying That DHCP Snooping Is Working Correctly on page 2654 • Monitoring Port Security on page 2653 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 Chapter 95: Configuring Port Security Enabling DHCP Snooping (J-Web Procedure) DHCP snooping allows the J-EX Series switch to monitor and control DHCP messages received from untrusted devices connected to the switch. It builds and maintains a database of valid IP-address/MAC-address (IP-MAC) bindings called the DHCP snooping database. You configure DHCP snooping for each VLAN, not for each interface (port). By default, DHCP snooping is disabled for all VLANs. To enable DHCP snooping on one or more VLANs by using the J-Web interface: 1. Select Configure>Security>Port Security. 2. Select one or more VLANs from the VLAN list. 3. Click the Edit button. If a message appears asking if you want to enable port security, click Yes. 4. Select the Enable DHCP Snooping on VLAN check box and then click OK. 5. Click OK after the command has been successfully delivered. NOTE: You can enable or disable port security on the switch at any time by clicking the Activate or Deactivate button on the Port Security Configuration page. If security status is shown as Disabled when you try to edit settings for any VLANs or interfaces (ports), the message asking if you want to enable port security appears. Related Documentation • Enabling DHCP Snooping (CLI Procedure) on page 2630 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Verifying That DHCP Snooping Is Working Correctly on page 2654 • Monitoring Port Security on page 2653 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 2631 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Enabling a Trusted DHCP Server (CLI Procedure) You can configure any interface on the J-EX Series switch that connects to a DHCP server as a trusted interface (port). Configuring a DHCP server on a trusted interface protects against rogue DHCP servers sending leases. You configure a trusted DHCP server on an interface, not on a VLAN. By default, all access interfaces are untrusted and all trunk interfaces are trusted. To configure a trusted interface for a DHCP server by using the CLI (here, the interface is ge-0/0/8): [edit ethernet-switching-options secure-access port] user@switch# set interface ge–0/0/8 dhcp-trusted Related Documentation • Enabling a Trusted DHCP Server (J-Web Procedure) on page 2632 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Verifying That a Trusted DHCP Server Is Working Correctly on page 2655 • Monitoring Port Security on page 2653 • Understanding Trusted DHCP Servers for Port Security on J-EX Series Switches on page 2559 Enabling a Trusted DHCP Server (J-Web Procedure) You can configure any interface on the J-EX Series switch that connects to a DHCP server as a trusted interface (port). Configuring a DHCP server on a trusted interface protects against rogue DHCP servers sending leases. You configure a trusted DHCP server on an interface, not on a VLAN. By default, all access interfaces are untrusted and all trunk interfaces are trusted. To enable a trusted DHCP server on one or more interfaces by using the J-Web interface: 1. Select Configure>Security>Port Security. 2. Select one or more interfaces from the Port list. 3. Click the Edit button. If a message appears asking if you want to enable port security, click Yes. 4. Select the Trust DHCP check box and then click OK. 5. Click OK after the command has been successfully delivered. 2632 Chapter 95: Configuring Port Security NOTE: You can enable or disable port security on the switch at any time by clicking the Activate or Deactivate button on the Port Security Configuration page. If security status is shown as Disabled when you try to edit settings for any VLANs or interfaces (ports), the message asking if you want to enable port security appears. Related Documentation • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Verifying That a Trusted DHCP Server Is Working Correctly on page 2655 • Monitoring Port Security on page 2653 • Understanding Trusted DHCP Servers for Port Security on J-EX Series Switches on page 2559 Enabling Dynamic ARP Inspection (CLI Procedure) Dynamic ARP inspection (DAI) protects J-EX Series switches against ARP spoofing. DAI inspects ARP packets on the LAN and uses the information in the DHCP snooping database on the switch to validate ARP packets and to protect against ARP cache poisoning. You configure DAI for each VLAN, not for each interface (port). By default, DAI is disabled for all VLANs. To enable dynamic ARP inspection (DAI) on a VLAN or all VLANs using the CLI: • On a single VLAN (here, the VLAN is employee-vlan): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee-vlan arp-inspection • On all VLANs: [edit ethernet-switching-options secure-access-port] user@switch# set vlan all arp-inspection Related Documentation • Enabling Dynamic ARP Inspection (J-Web Procedure) on page 2634 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 2633 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Verifying That DAI Is Working Correctly on page 2656 • Monitoring Port Security on page 2653 • Understanding DAI for Port Security on J-EX Series Switches on page 2555 Enabling Dynamic ARP Inspection (J-Web Procedure) Dynamic ARP inspection (DAI) protects J-EX Series switches against ARP spoofing. DAI inspects ARP packets on the LAN and uses the information in the DHCP snooping database on the switch to validate ARP packets and to protect against ARP cache poisoning. You configure DAI for each VLAN, not for each interface (port). By default, DAI is disabled for all VLANs. To enable DAI on one or more VLANs by using the J-Web interface: 1. Select Configure>Security>Port Security. 2. Select one or more VLANs from the VLAN list. 3. Click the Edit button. If a message appears asking if you want to enable port security, click Yes. 4. Select the Enable ARP Inspection on VLAN check box and then click OK. 5. Click OK after the command has been successfully delivered. NOTE: You can enable or disable port security on the switch at any time by clicking the Activate or Deactivate button on the Port Security Configuration page. If security status is shown as Disabled when you try to edit settings for any VLANs or interfaces (ports), the message asking if you want to enable port security appears. Related Documentation 2634 • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Verifying That DAI Is Working Correctly on page 2656 • Monitoring Port Security on page 2653 Chapter 95: Configuring Port Security • Understanding DAI for Port Security on J-EX Series Switches on page 2555 Configuring MAC Limiting (CLI Procedure) MAC limiting protects against flooding of the Ethernet switching table on the J-EX Series switch. MAC limiting sets a limit on the number of MAC addresses that can be learned on a single Layer 2 access interface (port). The Junos OS provides two MAC limiting methods: • Maximum number of dynamic MAC addresses allowed per interface—When the limit is exceeded, incoming packets with new MAC addresses are dropped. • Specific “allowed” MAC addresses for the access interface—Any MAC address that is not in the list of configured addresses is not learned and the switch logs the message. NOTE: If you do not want the switch to log messages received for invalid MAC addresses on an interface that has been configured for specific “allowed” MAC addresses, you can disable the logging by configuring the no-allowed-mac-log statement. You configure MAC limiting per interface, not per VLAN. You can specify the maximum number of dynamic MAC addresses that can be learned on a single Layer 2 access interface or on all Layer 2 access interfaces. You can choose to have one of the following actions performed when the limit of MAC addresses is exceeded: • drop—Drop the packet and generate an alarm, an SNMP trap, or a system log entry. This is the default. • log—Do not drop the packet but generate an alarm, an SNMP trap, or a system log entry. • none—Take no action. • shutdown—Disable the interface and generate an alarm. If you have configured the switch with the port-error-disable statement, the disabled interface recovers automatically upon expiration of the specified disable timeout. If you have not configured the switch for autorecovery from port error disabled conditions, you can bring up the disabled interfaces by running the clear ethernet-switching port-error command. To configure MAC limiting on a specific interface or on all interfaces, using the CLI: 1. For limiting the number of dynamic MAC addresses, set a MAC limit of 5. The action is not specified, so the switch performs the default action drop if the limit is exceeded: • On a single interface (here, the interface is ge-0/0/1): 2635 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit ethernet-switching-options secure-access-port] user@switch# set interface ge–0/0/1 mac-limit 5 • On all interfaces: [edit ethernet-switching-options secure-access-port] user@switch# set interface all mac–limit 5 NOTE: Do not set the mac-limit to 1. The first learned MAC address is often inserted into the forwarding database automatically (for instance, for Routed VLAN Interfaces the first MAC address inserted into the forwarding database is the MAC address of the RVI. For Aggregated Ethernet bundles using LACP, the first MAC address inserted into the forwarding database in the forwarding table is the source address of the protocol packet). The switch will therefore not learn MAC addresses other than the automatic addresses when the mac-limit is set to 1, and this will cause problems with MAC learning and forwarding. 2. For specifying specific allowed MAC addresses: • On a single interface (here, the interface is ge-0/0/2): [edit ethernet-switching-options secure-access-port] user@switch# set interface ge–0/0/2 allowed-mac 00:05:85:3A:82:80 user@switch# set interface ge–0/0/2 allowed-mac 00:05:85:3A:82:81 user@switch# set interface ge–0/0/2 allowed-mac 00:05:85:3A:82:83 • On all interfaces: [edit ethernet-switching-options secure-access-port] user@switch# set interface all allowed-mac 00:05:85:3A:82:80 user@switch# set interface all allowed-mac 00:05:85:3A:82:81 user@switch# set interface all allowed-mac 00:05:85:3A:82:83 Related Documentation 2636 • Configuring MAC Limiting (J-Web Procedure) on page 2637 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Verifying That MAC Limiting Is Working Correctly on page 2657 • Setting the none Action on an Interface to Override a MAC Limit Applied to All Interfaces (CLI Procedure) on page 2642 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 • no-allowed-mac-log on page 2686 Chapter 95: Configuring Port Security Configuring MAC Limiting (J-Web Procedure) MAC limiting protects against flooding of the Ethernet switching table on a J-EX Series switch. MAC limiting sets a limit on the number of MAC addresses that can be learned on a single Layer 2 access interface (port). The Junos OS provides two MAC limiting methods: • Maximum number of dynamic MAC addresses allowed per interface—If the limit is exceeded, incoming packets with new MAC addresses are dropped. • Specific “allowed” MAC addresses for the access interface—Any MAC address that is not in the list of configured addresses is not learned. You configure MAC limiting for each interface, not for each VLAN. You can specify the maximum number of dynamic MAC addresses that can be learned on a single Layer 2 access interface or on all Layer 2 access interfaces. The default action that the switch will take if that maximum number is exceeded is drop—drop the packet and generate an alarm, an SNMP trap, or a system log entry. To enable MAC limiting on one or more interfaces using the J-Web interface: 1. Select Configure>Security>Port Security. 2. Select one or more interfaces from the Interface List. 3. Click the Edit button. If a message appears asking whether you want to enable port security, click Yes. 4. To set a dynamic MAC limit: 1. Type a limit value in the MAC Limit box. 2. Select an action from the MAC Limit Action box (optional). The switch takes this action when the MAC limit is exceeded. If you do not select an action, the switch applies the default action, drop. • Log—Generate a system log entry, an SNMP trap, or an alarm. • Drop—Drop the packets and generate a system log entry, an SNMP trap, or an alarm. (Default) • Shutdown—Shut down the VLAN and generate an alarm. You can mitigate the effect of this option by configuring the switch for autorecovery from the disabled state and specifying a disable timeout value. See “Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure)” on page 2516. If you have not configured autorecovery from the disabled state, you can bring up the interfaces by running the clear ethernet-switching port-error command. • None— No action to be taken. 5. To add allowed MAC addresses: 2637 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1. Click Add. 2. Type the allowed MAC address and click OK. Repeat this step to add more allowed MAC addresses. 6. Click OK when you have finished setting MAC limits. 7. Click OK after the configuration has been successfully delivered. NOTE: You can enable or disable port security on the switch at any time by clicking the Activate or Deactivate button on the Port Security Configuration page. If security status is shown as Disabled when you try to edit settings for any VLANs or interfaces (ports), a message asking whether you want to enable port security appears. Related Documentation 2638 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Verifying That MAC Limiting Is Working Correctly on page 2657 • Setting the none Action on an Interface to Override a MAC Limit Applied to All Interfaces (CLI Procedure) on page 2642 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 Chapter 95: Configuring Port Security Configuring MAC Move Limiting (CLI Procedure) MAC move limiting detects MAC address movement and MAC address spoofing on access ports. MAC address movements are tracked, and if a MAC address moves more than the configured number of times within one second, the configured (or default) action is performed. You enable this feature on VLANs. NOTE: Although you enable this feature on VLANs, the MAC move limitation pertains to the number of movements for each individual MAC address rather than the total number of MAC address moves in the VLAN. For example, If the MAC move limit is set to 1, the switch allows an unlimited number of MAC address movements within the VLAN as long as the same MAC address does not move more than once. You configure MAC move limiting per VLAN, not per interface (port). In the default configuration, the number of MAC moves permitted is unlimited. You can choose to have one of the following actions performed when the MAC move limit is exceeded: • drop—Drop the packet and generate an alarm, an SNMP trap, or a system log entry. This is the default. • log—Do not drop the packet but generate an alarm, an SNMP trap, or a system log entry. • none—Take no action. • shutdown—Disable the interfaces in the VLAN and generate an alarm. If you have configured the switch with the port-error-disable statement, the disabled interfaces recover automatically upon expiration of the specified disable timeout. If you have not configured the switch for autorecovery from port error disabled conditions, you can bring up the disabled interfaces by running the clear ethernet-switching port-error command. 2639 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To configure a MAC move limit for MAC addresses within a specific VLAN or for MAC addresses within all VLANs, using the CLI: • On a single VLAN: To limit the number of MAC address movements that can be made by an individual MAC address within the VLAN employee-vlan, set a MAC move limit of 5: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee–vlan mac-move-limit 5 The action is not specified, so the switch performs the default action drop if it tracks that an individual MAC address within the employee-vlan has moved more than 5 times within one second. • On all VLANs: To limit the number of MAC movements that can be made by individual MAC addresses within all VLANs, set a MAC move limit of 5: [edit ethernet-switching-options secure-access-port] user@switch# set vlan all mac–move-limit 5 The action is not specified, so the switch performs the default action drop if it tracks that an individual MAC address within any of the VLANs has moved more than 5 times within one second. Related Documentation 2640 • Configuring MAC Move Limiting (J-Web Procedure) on page 2641 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That MAC Move Limiting Is Working Correctly on page 2661 • Monitoring Port Security on page 2653 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 Chapter 95: Configuring Port Security Configuring MAC Move Limiting (J-Web Procedure) MAC move limiting detects MAC address movement and MAC address spoofing on access ports. MAC address movements are tracked, and if a MAC address moves more than the configured number of times within one second, the configured (or default) action is performed. You enable this feature on VLANs. NOTE: Although you enable this feature on VLANs, the MAC move limitation pertains to the number of movements for each individual MAC address rather than the total number of MAC address moves in the VLAN. For example, If the MAC move limit is set to 1, the switch allows an unlimited number of MAC address movements within the VLAN as long as the same MAC address does not move more than once. In the default configuration, the MAC move limit within each VLAN is unlimited; the default action that the switch will take if the specified MAC move limit is exceeded is drop. To enable MAC move limiting for MAC addresses within one or more VLANs by using the J-Web interface: 1. Select Configure>Security>Port Security. 2. Select one or more VLANs from the VLAN List. 3. Click the Edit button. If a message appears asking whether you want to enable port security, click Yes. 4. To set a MAC move limit: 1. Type a limit value in the MAC Movement box. 2. Select an action from the MAC Movement Action box (optional). The switch takes this action when an individual MAC address exceeds the MAC move limit. If you do not select an action, the switch applies the default action, drop. Select one: • Log—Generate a system log entry, an SNMP trap, or an alarm. • Drop—Drop the packets and generate a system log entry, an SNMP trap, or an alarm. (Default) • Shutdown—Shut down the VLAN and generate an alarm. You can mitigate the effect of this option by configuring the switch for autorecovery from the disabled state and specifying a disable timeout value. See “Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure)” on page 2516. If you have not configured autorecovery from the disabled state, you can bring up the interfaces by running the clear ethernet-switching port-error command. • None— No action to be taken. 2641 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3. Click OK. 5. Click OK after the configuration has been successfully delivered. NOTE: You can enable or disable port security on the switch at any time by clicking the Activate or Deactivate button on the Port Security Configuration page. If security status is shown as Disabled when you try to edit settings for any VLANs, a message asking whether you want to enable port security appears. Related Documentation • Configuring MAC Move Limiting (CLI Procedure) on page 2639 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That MAC Move Limiting Is Working Correctly on page 2661 • Monitoring Port Security on page 2653 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 Setting the none Action on an Interface to Override a MAC Limit Applied to All Interfaces (CLI Procedure) If you set a MAC limit in your port security settings to apply to all interfaces on the J-EX Series switch, you can override that setting for a particular interface by specifying action none. To use the none action to override a MAC limit setting: 1. Set the MAC limit—for example, a limit of 5 with action drop: [edit ethernet-switching-options secure-access-port] user@switch# set interface all mac-limit 5 action drop 2. Then change the action for one interface (here, ge-0/0/2) with this command. You don't need to specify a limit value. [edit ethernet-switching-options secure-access-port] user@switch# set interface ge–0/0/2 mac-limit action none Related Documentation 2642 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That MAC Limiting Is Working Correctly on page 2657 Chapter 95: Configuring Port Security Configuring IP Source Guard (CLI Procedure) You can use the IP source guard access port security feature on J-EX Series switches to mitigate the effects of source IP address spoofing and source MAC address spoofing. If IP source guard determines that a host connected to an access interface has sent a packet with an invalid source IP address or source MAC address in the packet header, it ensures that the switch does not forward the packet—that is, the packet is discarded. You enable the IP source guard feature on VLANs. You can enable it on a specific VLAN, on all VLANs, or on a VLAN range. NOTE: IP source guard applies only to access interfaces and only to untrusted interfaces. If you enable IP source guard on a VLAN that includes trunk interfaces or an interface set to dhcp-trusted, the CLI shows an error when you try to commit the configuration. Before you configure IP source guard, be sure that you have: Enabled DHCP snooping on the VLAN or VLANs on which you will configure IP source guard. See “Enabling DHCP Snooping (CLI Procedure)” on page 2630. 2643 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To enable IP source guard on a VLAN, all VLANs, or a VLAN range (a series of tagged VLANs) by using the CLI: NOTE: Replace values displayed in italics with values for your configuration. • On a specific VLAN: [edit ethernet-switching-options secure-access port] user@switch#set vlan default ip-source-guard • On all VLANs: [edit ethernet-switching-options secure-access port] user@switch# set vlan all ip-source-guard • On a VLAN range: 1. Set the VLAN range (the VLAN name is employee): [edit vlans] user@switch# set employeevlan-range 100-101 2. Associate an interface with a VLAN-range number (100 in the following example) and set the port mode to access: [edit interfaces] user@switch# set ge-0/0/6 unit 0 family ethernet-switching port-mode access vlan members100 3. Enable IP source guard on the VLAN employee: [edit ethernet-switching-options secure-access port] user@switch# set vlan employee ip-source-guard NOTE: You can use the no-ip-source-guard statement to disable IP source guard for a specific VLAN after you have enabled the feature for all VLANs. To view results of the configuration steps before committing the configuration, type the show command at the user prompt. To commit these changes to the active configuration, type the commit command at the user prompt. Related Documentation 2644 • Verifying That IP Source Guard Is Working Correctly on page 2662 • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 • Understanding IP Source Guard for Port Security on J-EX Series Switches on page 2563 Chapter 95: Configuring Port Security Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) You can add static (fixed) IP addresses and bind them to fixed MAC addresses in the DHCP snooping database. These bindings are labeled as “static” in the database, while those bindings that have been added through the process of DHCP snooping are labeled “dynamic.” To configure a static IP address/MAC address binding in the DHCP snooping database (replace ge-0/0/2, 10.0.10.12, data-vlan, and 00:05:85:3A:82:80 with values for your configuration): [edit ethernet-switching-options secure-access-port] user@switch# set interface ge-0/0/2 static-ip 10.0.10.12 vlan data-vlan mac 00:05:85:3A:82:80 To view results of the configuration steps before committing the configuration, type the show command at the user prompt. To commit these changes to the active configuration, type the commit command at the user prompt. Related Documentation • Verifying That DHCP Snooping Is Working Correctly on page 2654 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 2645 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) You can use DHCP option 82, also known as the DHCP relay agent information option, to help 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. You can configure the DHCP option 82 feature in two topologies: • The switch functions as a relay agent when the DHCP clients or the DHCP server is connected to the switch through a Layer 3 interface. On the switch, these interfaces are configured as routed VLAN interfaces, or RVIs. The switch relays the clients' requests to the server and then forwards the server's replies to the clients. This topic describes this configuration. • The switch, DHCP clients, and DHCP server are all on the same VLAN. The switch forwards the clients' requests to the server and forwards the server's replies to the clients. This configuration is described in “Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure)” on page 2649. Before you configure DHCP option 82 on the switch, perform these tasks: • Connect and configure the DHCP server. NOTE: Your DHCP server must be configured to accept DHCP option 82. If the server is not configured for DHCP option 82, the server does not use the DHCP option 82 information in the requests sent to it when it formulates its reply messages. 2646 • Configure the VLAN on the switch and associate the interfaces on which the clients connect to the switch with that VLAN. • Configure the routed VLAN interface (RVI) to allow the switch to relay packets to the server and receive packets from the server. See “Configuring Routed VLAN Interfaces (CLI Procedure)” on page 1137. • Configure the switch as a BOOTP relay agent. See “DHCP/BOOTP Relay for J-EX Series Switches Overview” on page 446. Chapter 95: Configuring Port Security To configure DHCP option 82: NOTE: Replace values displayed in italics with values for your configuration. 1. Specify DHCP option 82 for the BOOTP server: • On all interfaces that connect to the server: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 • On a specific interface that connects to the server: [edit forwarding-options helpers bootp] user@switch# set interface ge-0/0/10 dhcp-option82 The remaining steps are optional. They show configurations for all interfaces; include the specific interface designation to configure any of the following options on a specific interface: 2. To configure a prefix for the circuit ID suboption (the prefix is always the hostname of the switch): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 circuit-id prefix hostname 3. To specify that the circuit ID suboption value contains the interface description rather than the interface name (the default): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 circuit-id use-interface-description 4. To specify that the circuit ID suboption value contains the VLAN ID rather than the VLAN name (the default): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 circuit-id use-vlan-id 5. To specify that the remote ID suboption is included in the DHCP option 82 information: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id 6. To configure a prefix for the remote ID suboption (here, the prefix is the MAC address of the switch): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id prefix mac 7. To specify that the prefix for the remote ID suboption is the hostname of the switch rather than the MAC address of the switch (the default): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id prefix hostname 8. To specify that the remote ID suboption value contains the interface description: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id use-interface-description 2647 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 9. To specify that the remote ID suboption value contains a character string: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 remote-id use-stringmystring 10. To configure a vendor ID suboption and use the default value (the default value is Juniper), do not type a character string after the vendor-id option keyword: [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 vendor-id 11. To specify that the vendor ID suboption value contains a character string value that you specify rather than Juniper (the default): [edit forwarding-options helpers bootp] user@switch# set dhcp-option82 vendor-id mystring To view results of the configuration steps before committing the configuration, type the show command at the user prompt. To commit these changes to the active configuration, type the commit command at the user prompt. Related Documentation 2648 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Chapter 95: Configuring Port Security Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) You can use DHCP option 82, also known as the DHCP relay agent information option, to help 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. You can configure the DHCP option 82 feature in two topologies: • The switch, DHCP clients, and DHCP server are all on the same VLAN. The switch forwards the clients' requests to the server and forwards the server's replies to the clients. This topic describes this configuration. • The switch functions as a relay agent when the DHCP clients or the DHCP server is connected to the switch through a Layer 3 interface. On the switch, these interfaces are configured as routed VLAN interfaces, or RVIs. The switch relays the clients' requests to the server and then forwards the server's replies to the clients. This configuration is described in “Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure)” on page 2646. Before you configure DHCP option 82 on the switch, perform these tasks: • Connect and configure the DHCP server. NOTE: Your DHCP server must be configured to accept DHCP option 82. If the server is not configured for DHCP option 82, the server does not use the DHCP option 82 information in the requests sent to it when it formulates its reply messages. • Configure a VLAN on the switch and associate the interfaces on which the clients and the server connect to the switch with that VLAN. 2649 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To configure DHCP option 82: NOTE: Replace values displayed in italics with values for your configuration. 1. Specify DHCP option 82 for all VLANs associated with the switch or for a specified VLAN. (You can also configure the feature for a VLAN range.) • On a specific VLAN: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 • On all VLANs: [edit ethernet-switching-options secure-access-port] user@switch# set vlan all dhcp-option82 The remaining steps are optional. 2. To configure a prefix for the circuit ID suboption (the prefix is always the hostname of the switch): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 circuit-id prefix hostname 3. To specify that the circuit ID suboption value contains the interface description rather than the interface name (the default): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 circuit-id use-interface-description 4. To specify that the circuit ID suboption value contains the VLAN ID rather than the VLAN name (the default): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 circuit-id use-vlan-id 5. To specify that the remote ID suboption is included in the DHCP option 82 information: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id 6. To configure a prefix for the remote ID suboption (here, the prefix is the MAC address of the switch): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id prefix mac 7. To specify that the prefix for the remote ID suboption is the hostname of the switch rather than the MAC address of the switch (the default): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id prefix hostname 8. To specify that the remote ID suboption value contains the interface description: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id use-interface-description 2650 Chapter 95: Configuring Port Security 9. To specify that the remote ID suboption value contains a character string: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 remote-id use-stringmystring 10. To configure a vendor ID suboption and use the default value (the default value is Juniper), do not type a character string after the vendor-id option keyword: [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 vendor-id 11. To specify that the vendor ID suboption value contains a character string value that you specify rather than Juniper (the default): [edit ethernet-switching-options secure-access-port] user@switch# set vlan employee dhcp-option82 vendor-id mystring To view results of the configuration steps before committing the configuration, type the show command at the user prompt. To commit these changes to the active configuration, type the commit command at the user prompt. Related Documentation • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Configuring Proxy ARP (CLI Procedure) You can configure proxy Address Resolution Protocol (ARP) on your J-EX Series switch to enable the switch to respond to ARP queries for network addresses by offering its own media access control (MAC) address. With proxy ARP enabled, the switch captures and routes traffic to the intended destination. To configure proxy ARP on a single interface: [edit interfaces] user@switch# set ge-0/0/3 unit 0 proxy-arp restricted BEST PRACTICE: We recommend that you configure proxy ARP in restricted mode. In restricted mode, the switch is not a proxy if the source and target IP addresses are on the same subnet. If you use unrestricted mode, disable gratuitous ARP requests on the interface to avoid the situation of the switch’s response to a gratuitous ARP request appearing to the host to be an indication of an IP conflict: To configure proxy ARP on a routed VLAN interface (RVI): [edit interfaces] user@switch# set vlan unit 100 proxy-arp restricted 2651 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Example: Configuring Proxy ARP on a J-EX Series Switch on page 2621 • Verifying That Proxy ARP Is Working Correctly on page 1164 • Configuring Routed VLAN Interfaces (CLI Procedure) on page 1137 Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) An Ethernet switching access interface on a J-EX Series switch might shut down or be disabled as a result of one of the following port-security or storm-control configurations: • MAC limiting—mac-limit statement is configured with action shutdown. • MAC move limiting—mac-move-limit statement is configured with action shutdown. • Storm control—storm-control statement is configured with the action shutdown. You can configure the switch to automatically restore the disabled interfaces to service after a specified period of time. Autorecovery applies to all the interfaces that have been disabled due to MAC limiting, MAC move limiting, or storm control errors. NOTE: You must specify the disable timeout value for the interfaces to recover automatically. There is no default disable timeout. If you do not specify a timeout value, you need to use the clear ethernet-switching port-error command to clear the errors and restore the interfaces or the specified interface to service. To configure autorecovery from the disabled state due to MAC limiting, MAC move limiting, or storm control shutdown actions: [edit ethernet-switching-options] user@switch# set port-error-disable disable-timeout 60 Related Documentation 2652 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Understanding MAC Limiting and MAC Move Limiting for Port Security on J-EX Series Switches on page 2557 • Understanding Storm Control on J-EX Series Switches on page 2511 CHAPTER 96 Verifying Port Security • Monitoring Port Security on page 2653 • Verifying That DHCP Snooping Is Working Correctly on page 2654 • Verifying That a Trusted DHCP Server Is Working Correctly on page 2655 • Verifying That DAI Is Working Correctly on page 2656 • Verifying That MAC Limiting Is Working Correctly on page 2657 • Verifying That MAC Move Limiting Is Working Correctly on page 2661 • Verifying That IP Source Guard Is Working Correctly on page 2662 • Verifying That Proxy ARP Is Working Correctly on page 2662 • Verifying That the Port Error Disable Setting Is Working Correctly on page 2663 Monitoring Port Security Purpose Action Use the monitoring functionality to view these port security details: • DHCP snooping database for a VLAN or all VLANs • ARP inspection details for all interfaces To monitor port security in the J-Web interface, select Monitor > Security > Port Security. To monitor and manipulate the DHCP snooping database and ARP inspection statistics in the CLI, enter the following commands: • show dhcp snooping binding • clear dhcp snooping binding—In addition to clearing the whole database, you can clear database entries for specified VLANs or MAC addresses. Meaning • show arp inspection statistics • clear arp inspection statistics The J-Web Port Security Monitoring page comprises two sections: • DHCP Snooping—Displays the DHCP snooping database for all the VLANs for which DHCP snooping is enabled. To view the DHCP snooping database for a specific VLAN, select the specific VLAN from the list. 2653 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • ARP Inspection—Displays the ARP inspection details for all interfaces. The information includes details of the number of packets that passed ARP inspection and the number of packets that failed the inspection. The pie chart graphically represents these statistics when you select an interface. To view ARP inspection statistics for a specific interface, select the interface from the list. You have the following options on the page: • Clear ALL—Clears the DHCP snooping database, either for all VLANs if the option ALL has been selected in the Select VLANs list or for the specific VLAN that has been selected in that list. • Clear—Deletes a specific IP address from the DHCP snooping database. To clear ARP statistics on the page, click Clear All in the ARP Statistics section. Use the CLI commands to show and clear DHCP snooping database and ARP inspection statistics details. Related Documentation • Configuring Port Security (CLI Procedure) on page 2626 • Configuring Port Security (J-Web Procedure) on page 2627 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 Verifying That DHCP Snooping Is Working Correctly Purpose Verify that DHCP snooping is working on the switch and that the DHCP snooping database is correctly populated with both dynamic and static bindings. Action Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the interface on which the DHCP server connects to the switch is trusted. The following output results when requests are sent from the MAC addresses and the server has provided the IP addresses and leases: Meaning 2654 user@switch> show dhcp snooping binding DHCP Snooping Information: MAC address IP address Lease (seconds) Type VLAN Interface 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:27:32:88 employee employee employee employee employee data ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/4.0 192.0.2.17 192.0.2.18 192.0.2.19 192.0.2.20 192.0.2.21 192.0.2.22 600 653 720 932 1230 — dynamic dynamic dynamic dynamic dynamic static When the interface on which the DHCP server connects to the switch has been set to trusted, the output (see preceding sample) shows, for each MAC address, the assigned Chapter 96: Verifying Port Security IP address and lease time—that is, the time, in seconds, remaining before the lease expires. Static IP addresses have no assigned lease time. The statically configured entry never expires. If the DHCP server had been configured as untrusted, no entries would be added to the DHCP snooping database and nothing would be shown in the output of the show dhcp snooping binding command. Related Documentation • Enabling DHCP Snooping (CLI Procedure) on page 2630 • Enabling DHCP Snooping (J-Web Procedure) on page 2631 • Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) on page 2645 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Monitoring Port Security on page 2653 • Troubleshooting Port Security on page 2665 Verifying That a Trusted DHCP Server Is Working Correctly Purpose Verify that a DHCP trusted server is working on the switch. See what happens when the DHCP server is trusted and then untrusted. Action Send some DHCP requests from network devices (here they are DHCP clients) connected to the switch. Display the DHCP snooping information when the interface on which the DHCP server connects to the switch is trusted. The following output results when requests are sent from the MAC addresses and the server has provided the IP addresses and leases: user@switch> show dhcp snooping binding DHCP Snooping Information: MAC Address IP Address Lease -----------------------------00:05:85:3A:82:77 192.0.2.17 600 00:05:85:3A:82:79 192.0.2.18 653 00:05:85:3A:82:80 192.0.2.19 720 00:05:85:3A:82:81 192.0.2.20 932 00:05:85:3A:82:83 192.0.2.21 1230 00:05:85:27:32:88 192.0.2.22 3200 Meaning Type ---dynamic dynamic dynamic dynamic dynamic dynamic VLAN ---employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan employee—vlan Interface --------ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 When the interface on which the DHCP server connects to the switch has been set to trusted, the output (see preceding sample) shows, for each MAC address, the assigned 2655 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS IP address and lease time—that is, the time, in seconds, remaining before the lease expires. If the DHCP server had been configured as untrusted, no entries would be added to the DHCP snooping database and nothing would be shown in the output of the show dhcp snooping binding command. Related Documentation • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Enabling a Trusted DHCP Server (J-Web Procedure) on page 2632 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Monitoring Port Security on page 2653 • Troubleshooting Port Security on page 2665 Verifying That DAI Is Working Correctly Purpose Action Verify that dynamic ARP inspection (DAI) is working on the switch. Send some ARP requests from network devices connected to the switch. Display the DAI information: user@switch> show arp inspection statistics ARP inspection statistics: Interface Packets received ARP inspection pass ARP inspection failed --------------- ---------------------------------- --------------------ge-0/0/1.0 7 5 2 ge-0/0/2.0 10 10 0 ge-0/0/3.0 12 12 0 Meaning Related Documentation 2656 The sample output shows the number of ARP packets received and inspected per interface, with a listing of how many packets passed and how many failed the inspection on each interface. The switch compares the ARP requests and replies against the entries in the DHCP snooping database. If a MAC address or IP address in the ARP packet does not match a valid entry in the database, the packet is dropped. • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Enabling Dynamic ARP Inspection (J-Web Procedure) on page 2634 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 Chapter 96: Verifying Port Security • Monitoring Port Security on page 2653 Verifying That MAC Limiting Is Working Correctly MAC limiting protects against flooding of the Ethernet switching table. MAC limiting sets a limit on the number of MAC addresses that can be learned on a single Layer 2 access interface (port). The Junos OS provides two MAC limiting methods: • Maximum number of dynamic MAC addresses allowed per interface—When the limit is exceeded, incoming packets with new MAC addresses are dropped. • Specific “allowed” MAC addresses for the access interface—Any MAC address that is not in the list of configured addresses is not learned. To verify MAC limiting configurations: 1. Verifying That MAC Limiting for Dynamic MAC Addresses Is Working Correctly on page 2657 2. Verifying That Allowed MAC Addresses Are Working Correctly on page 2658 3. Verifying Results of Various Action Settings When the MAC Limit Is Exceeded on page 2658 4. Customizing the Ethernet Switching Table Display to View Information for a Specific Interface on page 2660 Verifying That MAC Limiting for Dynamic MAC Addresses Is Working Correctly Purpose Action Verify that MAC limiting for dynamic MAC addresses is working on the switch. Display the MAC addresses that have been learned. The following sample output shows the results when two packets were sent from hosts on ge-0/0/1 and five packets requests were sent from hosts on ge-0/0/2, with both interfaces set to a MAC limit of 4 with the action drop: user@switch> show ethernet-switching table Ethernet-switching table: 7 entries, 6 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning * 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:3A:82:85 Flood Learn Learn Learn Learn Learn Learn Age Interfaces 0 0 0 0 0 0 ge-0/0/2.0 ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 The sample output shows that with a MAC limit of 4 for each interface, the packet for a fifth MAC address on ge-0/0/2 was dropped because it exceeded the MAC limit. The address was not learned, and thus an asterisk (*) rather than an address appears in the MAC address column in the first line of the sample output. 2657 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Verifying That Allowed MAC Addresses Are Working Correctly Purpose Action Verify that allowed MAC addresses are working on the switch. Display the MAC cache information after allowed MAC addresses have been configured on an interface. The following sample shows the MAC cache after 5 allowed MAC addresses had been configured on interface ge/0/0/2. In this instance, the interface was also set to a dynamic MAC limit of 4 with action drop. user@switch> show ethernet-switching table Ethernet-switching table: 5 entries, 4 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning 00:05:85:3A:82:80 00:05:85:3A:82:81 00:05:85:3A:82:83 00:05:85:3A:82:85 * Learn Learn Learn Learn Flood Age Interfaces 0 0 0 0 - ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 Because the MAC limit value for this interface had been set to 4, only four of the five configured allowed addresses were learned and thus added to the MAC cache. Because the fifth address was not learned, an asterisk (*) rather than an address appears in the MAC address column in the last line of the sample output. Verifying Results of Various Action Settings When the MAC Limit Is Exceeded Purpose Action Verify the results provided by the various action settings for MAC limits—drop, log, none, and shutdown—when the limits are exceeded. Display the results of the various action settings. NOTE: You can view log messages by using the show log messages command. You can also have the log messages displayed by configuring the monitor start messages with the monitor start messages command. • drop action—For MAC limiting configured with a drop action and with the MAC limit set to 5: user@switch> show ethernet-switching table Ethernet-switching table: 6 entries, 5 learned VLAN MAC address Type 2658 Age Interfaces employee—vlan * Flood - ge-0/0/2.0 employee—vlan 00:05:85:3A:82:80 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:81 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:83 Learn 0 ge-0/0/2.0 Chapter 96: Verifying Port Security • employee—vlan 00:05:85:3A:82:85 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:88 Learn 0 ge-0/0/2.0 log action—For MAC limiting configured with a log action and with MAC limit set to 5: user@switch> show ethernet-switching table Ethernet-switching table: 74 entries, 73 learned VLAN MAC address Type Age Interfaces employee—vlan * Flood - ge-0/0/2.0 employee—vlan 00:05:85:3A:82:80 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:81 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:82 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:83 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:84 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:85 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:87 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:88 Learn 0 ge-0/0/2.0 . . . • shutdown action—For MAC limiting configured with a shutdown action and with MAC limit set to 3: user@switch> show ethernet-switching table Ethernet-switching table: 4 entries, 3 learned VLAN MAC address Type • Age Interfaces employee—vlan * Flood - ge-0/0/2.0 employee—vlan 00:05:85:3A:82:82 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:84 Learn 0 ge-0/0/2.0 employee—vlan 00:05:85:3A:82:87 Learn 0 ge-0/0/2.0 none action—If you set a MAC limit to apply to all interfaces on the switch, you can override that setting for a particular interface by specifying this action for that interface. See “Setting the none Action on an Interface to Override a MAC Limit Applied to All Interfaces (CLI Procedure)” on page 2642. Meaning For the drop action results—The sixth MAC address exceeded the MAC limit. The request packet for that address was dropped. Only five MAC addresses have been learned on ge-0/0/2. 2659 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS For the log action results—The sixth MAC address exceeded the MAC limit. No MAC addresses were blocked. For the shutdown action results—The fourth MAC address exceeded the MAC limit. Only three MAC addresses have been learned on ge-0/0/2. The interface ge-0/0/1 is shut down. For more information about interfaces that have been shut down, use the show ethernet-switching interfaces command. user@switch> show ethernet-switching interfaces Interface State VLAN members Tag Tagging bme0.32770 down mgmt untagged unblocked ge-1/0/0.0 down v1 untagged MAC limit exceeded ge-1/0/1.0 up v1 untagged unblocked ge-1/0/2.0 up v1 untagged unblocked me0.0 up mgmt untagged unblocked Blocking NOTE: You can configure the switch to recover automatically from this type of error condition by specifying the port-error-disable statement with a disable timeout value. The switch automatically restores the disabled interface to service when the disable timeout expires. The port-error-disable configuration does not apply to pre-existing error conditions. It impacts only error conditions that are detected after port-error-disable has been enabled and committed. To clear a pre-existing error condition and restore the interface to service, use the clear ethernet-switching port-error command. Customizing the Ethernet Switching Table Display to View Information for a Specific Interface Purpose You can use the show ethernet-switching table command to view information for a specific interface. Action For example, to display the MAC addresses that have been learned on ge-0/0/2 interface, type: user@switch> show ethernet-switching table interface ge-0/0/2.0 Ethernet-switching table: 1 unicast entries 2660 VLAN MAC address Type v1 * Flood v1 00:00:06:00:00:00 Learn Age Interfaces - All-members 0 ge-2/0/0.0 Chapter 96: Verifying Port Security Meaning Related Documentation The MAC limit value for ge-0/0/2 had been set to 1, and the output shows that only one MAC address was learned and thus added to the MAC cache. An asterisk (*) rather than an address appears in the MAC address column in the first line of the sample output. • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Monitoring Port Security on page 2653 Verifying That MAC Move Limiting Is Working Correctly Purpose Action Verify that MAC move limiting is working on the switch. Display the MAC addresses in the Ethernet switching table when MAC move limiting has been configured for a VLAN. The following sample shows the results after two of the hosts on ge-0/0/2 sent packets after the MAC addresses for those hosts had moved to other interfaces more than five times in 1 second. The VLAN, employee-vlan, was set to a MAC move limit of 5 with the action drop: user@switch> show ethernet-switching table Ethernet-switching table: 7 entries, 4 learned VLAN MAC address Type employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan employee-vlan Meaning 00:05:85:3A:82:77 00:05:85:3A:82:79 00:05:85:3A:82:80 00:05:85:3A:82:81 * * Learn Learn Learn Learn Flood Flood Age Interfaces 0 0 0 0 - ge-0/0/1.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 ge-0/0/2.0 The last two lines of the sample output show that MAC addresses for two hosts on ge-0/0/2 were not learned, because the hosts had been moved back and forth from the original interfaces more than five times in 1 second. NOTE: For descriptions of the results of the various action settings—drop, log, none, and shutdown—see “Verifying That MAC Limiting Is Working Correctly” on page 2657. 2661 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Configuring MAC Move Limiting (CLI Procedure) on page 2639 • Configuring MAC Move Limiting (J-Web Procedure) on page 2641 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Monitoring Port Security on page 2653 Verifying That IP Source Guard Is Working Correctly Purpose Action Meaning Related Documentation Verify that IP source guard is enabled and is mitigating the effects of any source IP spoofing attacks on the J-EX Series switch. Display the IP source guard database. user@switch> show ip-source-guard IP source guard information: Interface Tag IP Address MAC Address VLAN ge-0/0/12.0 0 10.10.10.7 00:30:48:92:A5:9D vlan100 ge-0/0/13.0 0 10.10.10.9 00:30:48:8D:01:3D vlan100 ge—0/0/13.0 100 * * voice The IP source guard database table contains the VLANs enabled for IP source guard, the untrusted access interfaces on those VLANs, the VLAN 802.1Q tag IDs if there are any, and the IP addresses and MAC addresses that are bound to one another. If a switch interface is associated with multiple VLANs and some of those VLANs are enabled for IP source guard and others are not, the VLANs that are not enabled for IP source guard have a star (*) in the IP Address and MAC Address fields. See the entry for the voice VLAN in the preceding sample output. • Configuring IP Source Guard (CLI Procedure) on page 2643 Verifying That Proxy ARP Is Working Correctly Purpose Action Verify that the switch is sending proxy ARP messages. List the system statistics for ARP: user@switch> show system statistics arp arp: 198319 datagrams received 45 ARP requests received 12 ARP replies received 2 resolution requests received 2 unrestricted proxy requests 0 restricted proxy requests 0 received proxy requests 2662 Chapter 96: Verifying Port Security 0 proxy requests not proxied 0 restricted-proxy requests not proxied 0 with bogus interface 0 with incorrect length 0 for non-IP protocol 0 with unsupported op code 0 with bad protocol address length 0 with bad hardware address length 0 with multicast source address 0 with multicast target address 0 with my own hardware address 168705 for an address not on the interface 0 with a broadcast source address 0 with source address duplicate to mine 29555 which were not for me 0 packets discarded waiting for resolution 4 packets sent after waiting for resolution 27 ARP requests sent 47 ARP replies sent 0 requests for memory denied 0 requests dropped on entry 0 requests dropped during retry 0 requests dropped due to interface deletion 0 requests on unnumbered interfaces 0 new requests on unnumbered interfaces 0 replies for from unnumbered interfaces 0 requests on unnumbered interface with non-subnetted donor 0 replies from unnumbered interface with non-subnetted donor Meaning Related Documentation The statistics show that two proxy ARP requests were received, and the proxy requests not proxied field indicates that all the unproxied ARP requests received have been proxied by the switch. • Configuring Proxy ARP (CLI Procedure) on page 1153 Verifying That the Port Error Disable Setting Is Working Correctly Purpose Action Verify that the port error disable setting is working as expected on MAC limited, MAC move limited and rate-limited interfaces on a J-EX Series switch. Display information about interfaces: user@switch> show ethernet-switching interfaces Interface State VLAN members ge-0/0/0.0 up T1122 ge-0/0/1.0 down default ge-0/0/2.0 down default ge-0/0/3.0 down default ge-0/0/4.0 down default ge-0/0/5.0 down default ge-0/0/6.0 down default ge-0/0/7.0 down default ge-0/0/8.0 down default ge-0/0/9.0 up T111 ge-0/0/10.0 down default ge-0/0/11.0 down default ge-0/0/12.0 down default Blocking unblocked MAC limit exceeded MAC move limit exceeded Storm control in effect unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked 2663 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ge-0/0/13.0 ge-0/0/14.0 ge-0/0/15.0 ge-0/0/16.0 ge-0/0/17.0 ge-0/0/18.0 ge-0/0/19.0 ge-0/1/0.0 ge-0/1/1.0 ge-0/1/2.0 ge-0/1/3.0 Meaning down down down down down down up down down down down default default default default default default T111 default default default default unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked unblocked The sample output from the show ethernet-switching interfaces command shows that three of the down interfaces specify the reason that the interface is disabled: • MAC limit exceeded—The interface is temporarily disabled due to a mac-limit error. The disabled interface is automatically restored to service when the disable-timeout expires. • MAC move limit exceeded—The interface is temporarily disabled due to a mac-move-limit error. The disabled interface is automatically restored to service when the disable-timeout expires. • Storm control in efffect —The interface is temporarily disabled due to a storm-control error. The disabled interface is automatically restored to service when the disable-timeout expires. Related Documentation 2664 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 CHAPTER 97 Troubleshooting Port Security • Troubleshooting Port Security on page 2665 Troubleshooting Port Security Troubleshooting issues for port security on J-EX Series switches: • MAC Addresses That Exceed the MAC Limit or MAC Move Limit Are Not Listed in the Ethernet Switching Table on page 2665 • Multiple DHCP Server Packets Have Been Received on Untrusted Interfaces on page 2665 MAC Addresses That Exceed the MAC Limit or MAC Move Limit Are Not Listed in the Ethernet Switching Table Problem You see log messages telling you that the MAC limit or MAC move limit has been exceeded, but the specific offending MAC addresses that have been exceeding the limit are not listed in the Ethernet switching table. Solution 1. Set the MAC limit or MAC move limit action to log. [edit ethernet-switching-options secure-access port] user@switch# set interface ge-0/0/2 mac-limit 5 action log 2. Allow some MAC address requests to come in. 3. View the entries in the Ethernet switching table: user@switch> show ethernet-switching table Multiple DHCP Server Packets Have Been Received on Untrusted Interfaces Problem You see log messages that DHCP server packets were received on an untrusted interface—for example: 5 untrusted DHCPOFFER received, interface ge-0/0/0.0[65], vlan v1[10] server ip/mac 12.12.12.1/00:00:00:00:01:12 offer ip/client mac 12.12.12.253/00:AA:BB:CC:DD:01 These messages can signal the presence of a malicious DHCP server on the network. Solution Configure a firewall filter to block the IP address or MAC address of the malicious DHCP server. See “Configuring Firewall Filters (CLI Procedure)” on page 2779. 2665 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation 2666 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That a Trusted DHCP Server Is Working Correctly on page 2655 • Verifying That MAC Limiting Is Working Correctly on page 2657 • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Configuring MAC Limiting (CLI Procedure) on page 2635 CHAPTER 98 Configuration Statements for Port Security • [edit ethernet-switching-options] Configuration Statement Hierarchy on page 2667 • [edit forwarding-options] Configuration Statement Hierarchy on page 2669 [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; 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; 2667 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS port-error-disable { disable-timeout timeout; } redundant-trunk-group { group-name name { interface interface-name ; } } secure-access-port { 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 ); 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 ); 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 ); (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-unknown-unicast; } } traceoptions { 2668 Chapter 98: Configuration Statements for Port Security 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 ; } } } Related Documentation • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 [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; } vendor-id ; } interface interface-name { dhcp-option82 { circuit-id { 2669 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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 2670 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • Understanding DHCP Option 82 for Port Security on J-EX Series Switches on page 2560 • DHCP/BOOTP Relay for J-EX Series Switches Overview on page 446 • For more information about the [edit forwarding-options] hierarchy and all its options, see the Junos OS Policy Framework Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Chapter 98: Configuration Statements for Port Security allowed-mac Syntax Hierarchy Level Release Information Description allowed-mac { mac-address-list; } [edit ethernet-switching-options secure-access-port interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify particular MAC addresses to be added to the MAC address cache. NOTE: Although this configuration restricts the addresses that can be added to the MAC address cache, it does not block the switch from receiving Layer 2 control packets—such as Link Layer Discovery Protocol (LLDP) packets—transmitted from MAC addresses that are not specified in the list of allowed MAC addresses. Control packets do not undergo the MAC address check and they are therefore included in the statistics of packets received. However, they are not forwarded to another destination. They are trapped within the switch. Default Options Allowed MAC addresses take precedence over dynamic MAC values that have been applied with the mac-limit statement. mac-address-list—One or more MAC addresses configured as allowed MAC addresses for a specified interface or all interfaces. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • mac-limit on page 2684 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 2671 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS arp-inspection Syntax Hierarchy Level Release Information Description (arp-inspection | no-arp-inspection); [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Perform dynamic ARP inspection (DAI) on all VLANs or on the specified VLAN. • arp-inspection—Enable DAI. When ARP inspection is enabled, the switch logs invalid ARP packets that it receives on each interface, along with the sender’s IP and MAC addresses. • Default Required Privilege Level Related Documentation 2672 no-arp-inspection—Disable DAI. Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Enabling Dynamic ARP Inspection (J-Web Procedure) on page 2634 Chapter 98: Configuration Statements for Port Security circuit-id Syntax Hierarchy Level Release Information Description circuit-id { prefix hostname; use-interface-description; use-vlan-id; } [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82] [edit forwarding-options helpers bootp dhcp-option82] [edit forwarding-options helpers bootp interface interface-name dhcp-option82] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the circuit-id suboption (suboption 1) of DHCP option 82 (the DHCP relay agent information option) in DHCP packets destined for a DHCP server. This suboption identifies the circuit (interface and/or VLAN) on which the DHCP request arrived. The format of the circuit-id information for Gigabit Ethernet interfaces that use VLANs is interface-name:vlan-name . On a Layer 3 interface, the format is just interface-name. The remaining statements are explained separately. Default Required Privilege Level Related Documentation If DCHP option 82 is enabled on the switch, the circuit ID is supplied by default in the format interface-name:vlan-name or, on a Layer 3 interface, just interface-name . routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. 2673 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dhcp-option82 Syntax Hierarchy Level Release Information Description 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 ; } [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] [edit forwarding-options helpers bootp] [edit forwarding-options helpers bootp interface interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. When the switch receives a DHCP request from a DHCP client connected on one of the switch's interfaces, have the switch insert DHCP option 82 (also known as the DHCP relay agent information option) information in the DHCP request packet header before it forwards or relays the request to a DHCP server. The server uses the option 82 information, which provides details about the circuit and host the request came from, in formulating the reply; the server does not, however, make any changes to the option 82 information in the packet header. The switch receives the reply and then removes the DHCP option 82 information before forwarding the reply to the client. The remaining statements are explained separately. Default Required Privilege Level Related Documentation 2674 Insertion of DHCP option 82 information is not enabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Chapter 98: Configuration Statements for Port Security dhcp-snooping-file Syntax Hierarchy Level Release Information Description dhcp-snooping-file { location local_pathname | remote_URL; timeout seconds; write-interval seconds; } [edit ethernet-switching-options secure-access-port] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a local pathname or remote URL for the DHCP snooping database file to maintain persistence of IP-MAC bindings. The remaining statements are explained separately. Default Required Privilege Level Related Documentation The IP-MAC bindings in the DHCP snooping database file are not persistent. If the switch is rebooted, the bindings are lost. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 2675 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dhcp-trusted Syntax Hierarchy Level (dhcp-trusted | no-dhcp-trusted); [edit ethernet-switching-options secure-access-port interface (all | interface-name)] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Allow DHCP responses from the specified interfaces (ports) or all interfaces. Default Required Privilege Level Related Documentation 2676 • dhcp-trusted—Allow DHCP responses. • no-dhcp-trusted—Deny DHCP responses. Trusted for trunk ports, untrusted for access ports. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Enabling a Trusted DHCP Server (J-Web Procedure) on page 2632 Chapter 98: Configuration Statements for Port Security disable-timeout Syntax Hierarchy Level Release Information Description disable-timeout timeout; [edit ethernet-switching-options port-error-disable] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how long the Ethernet switching interfaces remain in a disabled state due to MAC limiting, MAC move limiting, or storm control errors. NOTE: If you modify the timeout value of an existing disable timeout, the new timeout value does not impact the timing of restoration to service of currently disabled interfaces that have been configured for automatic recovery. The new timeout value is applied only during the next occurrence of a port error. You can bring up the currently disabled interfaces by running the clear ethernet-switching port-error command. Default Options The disable timeout is not enabled. timeout—Time, in seconds, that the disabled state remains in effect. The disabled interface is automatically restored to service when the specified timeout value is reached. Range: 10 through 3600 seconds Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 2677 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ethernet-switching-options Syntax 2678 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; 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 name { interface interface-name ; interface interface-name; } } secure-access-port { dhcp-snooping-file { location local_pathname | remote_URL; timeout seconds; write-interval seconds; } interface (all | interface-name) { allowed-mac { mac-address-list; } Chapter 98: Configuration Statements for Port Security (dhcp-trusted | no-dhcp-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); 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); (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-unknown-unicast; } } 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 ; } } } 2679 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Hierarchy Level Release Information Description [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Ethernet switching options. The remaining statements are explained separately. Required Privilege Level Related Documentation 2680 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Understanding Port Mirroring on J-EX Series Switches on page 3245 • Port Security for J-EX Series Switches Overview on page 2545 • Understanding BPDU Protection for STP, RSTP, and MSTP on J-EX Series Switches on page 1278 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding Storm Control on J-EX Series Switches on page 2511 • Understanding 802.1X and VoIP on J-EX Series Switches on page 2263 • Understanding Q-in-Q Tunneling on J-EX Series Switches on page 1051 • Understanding Unknown Unicast Forwarding on J-EX Series Switches on page 2512 • Understanding MAC Notification on J-EX Series Switches on page 1060 Chapter 98: Configuration Statements for Port Security examine-dhcp Syntax Hierarchy Level Release Information Description (examine-dhcp | no-examine-dhcp); [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable DHCP snooping on all VLANs or on the specified VLAN. • examine-dhcp—Enable DHCP snooping. • no-examine-dhcp—Disable DHCP snooping. When DHCP snooping is enabled, the switch logs DHCP packets (DHCPOFFER, DHCPDECLINE, DHCPACK, and DHCPNAK packets) that it receives on untrusted ports. You can monitor the log for these messages, which can signal the presence of a malicious DHCP server on the network. TIP: For Private VLANs (PVLANs), enable DHCP snooping on the primary VLAN. If you enable DHCP snooping only on a community VLAN, DHCP messages coming from PVLAN trunk ports are not snooped. Default Required Privilege Level Related Documentation Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring DHCP Snooping and DAI to Protect the Switch from ARP Spoofing Attacks on page 2586 • Enabling DHCP Snooping (CLI Procedure) on page 2630 • Enabling DHCP Snooping (J-Web Procedure) on page 2631 2681 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description interface (all | interface-name) { allowed-mac { mac-address-list; } (dhcp-trusted | no-dhcp-trusted); mac-limit limit action action; no-allowed-mac-log; static-ip ip-address { vlan vlan-name; mac mac-address; } } [edit ethernet-switching-options secure-access-port] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply port security features to all interfaces or to the specified interface. The statements are explained separately. Options all—Apply port security features to all interfaces. interface-name —Apply port security features to the specified interface. Required Privilege Level Related Documentation 2682 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Example: Configuring a DHCP Server Interface as Untrusted to Protect the Switch from Rogue DHCP Server Attacks on page 2579 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Enabling a Trusted DHCP Server (CLI Procedure) on page 2632 • Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) on page 2645 Chapter 98: Configuration Statements for Port Security ip-source-guard Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation (ip-source-guard | no-ip-source-guard); [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Perform IP source guard checking on packets sent from access interfaces. Validate source IP addresses and source MAC addresses on all VLANs or on the specified VLAN or VLAN range. Forward packets with valid addresses and drop those with invalid addresses. • ip-source-guard—Enable IP source guard checking. • no-ip-source-guard—Disable IP source guard checking. Disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 • Configuring IP Source Guard (CLI Procedure) on page 2643 mac Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation mac mac-address; [edit ethernet-switching-options secure-access-port interface (all | interface-name) static-ip ip-address vlan vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Media access control (MAC) address, or hardware address, for the device connected to the specified interface. mac-address —Value (in hexadecimal format) for address assigned to this device. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) on page 2645 2683 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mac-limit Syntax Hierarchy Level Release Information Description Default Options mac-limit limit action action; [edit ethernet-switching-options secure-access-port interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the number of MAC addresses to dynamically add to the MAC address cache for this access interface (port) and the action to be taken by the switch if the MAC address learning limit is exceeded on the interface (port). The default action is drop. limit—Maximum number of MAC addresses. action action—(Optional) Action to take when the MAC address limit is exceeded: • drop—Drop the packet and generate an alarm, an SNMP trap, or a system log entry. This is the default. • log—Do not drop the packet but generate an alarm, an SNMP trap, or a system log entry. • none—No action. • shutdown—Disable the interface and generate an alarm. If you have configured the switch with the port-error-disable statement, the disabled interface recovers automatically upon expiration of the specified disable timeout. If you have not configured the switch for autorecovery from port error disabled conditions, you can bring up the disabled interfaces by running the clear ethernet-switching port-error command. Required Privilege Level Related Documentation 2684 routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • allowed-mac on page 2671 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring MAC Limiting, Including Dynamic and Allowed MAC Addresses, to Protect the Switch from Ethernet Switching Table Overflow Attacks on page 2576 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 Chapter 98: Configuration Statements for Port Security mac-move-limit Syntax Hierarchy Level Release Information Description Default Options mac-move-limit limit action action; [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the number of times a MAC address can move to a new interface (port) in 1 second and the action to be taken by the switch if the MAC address move limit is exceeded. The default move limit is unlimited. The default action is drop. limit—Maximum number of moves to a new interface per second. action action—(Optional) Action to take when the MAC address move limit is reached: • drop—Drop the packet and generate an alarm, an SNMP trap, or a system log entry. This is the default. • log—Do not drop the packet but generate an alarm, an SNMP trap, or a system log entry. • none—No action. • shutdown—Disable the VLAN and generate an alarm. If you have configured the switch with the port-error-disable statement, the disabled interfaces recover automatically upon expiration of the specified disable timeout. If you have not configured the switch for autorecovery from port error disabled conditions, you can bring up the disabled interfaces by running the clear ethernet-switching port-error command. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • mac-limit on page 2684 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Configuring MAC Move Limiting (CLI Procedure) on page 2639 • Configuring MAC Move Limiting (J-Web Procedure) on page 2641 • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 2685 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS no-allowed-mac-log Syntax Hierarchy Level Release Information [edit ethernet-switching-options secure-access-port interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Specify that the switch does not log messages when it receives packets from invalid MAC addresses on an interface that has been configured for particular (allowed) MAC addresses. Default The switch logs messages when it receives packets from invalid MAC addresses on an interface that has been configured for particular (allowed) MAC addresses. Required Privilege Level Related Documentation 2686 no-allowed-mac-log; routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • allowed-mac on page 2671 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring Allowed MAC Addresses to Protect the Switch from DHCP Snooping Database Alteration Attacks on page 2590 • Example: Configuring MAC Limiting to Protect the Switch from DHCP Starvation Attacks on page 2583 • Configuring MAC Limiting (CLI Procedure) on page 2635 • Configuring MAC Limiting (J-Web Procedure) on page 2637 Chapter 98: Configuration Statements for Port Security no-gratuitous-arp-request Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation no-gratuitous-arp-request; [edit interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the switch not to respond to gratuitous ARP requests. You can disable responses to gratuitous ARP requests on both Layer 2 Ethernet switching interfaces and routed VLAN interfaces (RVIs). Gratuitous ARP responses are enabled on all Ethernet switching interfaces and RVIs. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Unrestricted Proxy ARP on a J-EX Series Switch on page 2621 • Configuring Unrestricted Proxy ARP (CLI Procedure) on page 1153 2687 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS port-error-disable Syntax Hierarchy Level Release Information Description port-error-disable { disable-timeout timeout ; } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable rather than block an interface when enforcing MAC limiting, MAC move limiting, and rate-limiting configuration options for shutting down the interface; and allow the interface to recovery automatically from the error condition after a specified period of time: NOTE: The port-error-disable configuration does not apply to pre-existing error conditions. It impacts only error conditions that are detected after port-error-disable has been enabled and committed. To clear a pre-existing error condition and restore the interface to service, use the clear ethernet-switching port-error command. Default Required Privilege Level Related Documentation 2688 • If you have enabled mac-limit with the shutdown option and enable port-error-disable, the switch disables (rather than shuts down) the interface when the MAC address limit is reached. • If you have enabled mac-move-limit with the shutdown option and you enable port-error-disable, the switch disables (rather than shuts down) the interface when the maximum number of moves to a new interface is reached. • If you have enabled storm-control with the action-shutdown option and you enable port-error-disable, the switch disables (rather than shuts down) the interface when broadcast traffic and unknown unicast traffic exceeds the specified levels. Not enabled. routing—To view this statement in the configuration. routing–control—To add this statement to the configuration. • Configuring Autorecovery From the Disabled State on Secure or Storm Control Interfaces (CLI Procedure) on page 2516 • Configuring Port Security (CLI Procedure) on page 2626 • Example: Configuring Storm Control to Prevent Network Outages on J-EX Series Switches on page 2513 Chapter 98: Configuration Statements for Port Security prefix Syntax Hierarchy Level Release Information prefix hostname; [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82 circuit-id] [edit forwarding-options helpers bootp dhcp-option82 circuit-id] [edit forwarding-options helpers bootp interface interface-name dhcp-option82 circuit-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure an optional prefix for the circuit ID suboption in the DHCP option 82 information that is inserted by the switch into the packet header of a DHCP request before it forwards or relays the request to a DHCP server. Default If prefix is not explicitly specified, no prefix is appended to the circuit ID. When prefix is specified, it is specified as prefix hostname (and the value is the hostname of the switch). Options hostname—Name of the host system (the switch) that is forwarding or relaying the DHCP request from the DHCP client to the DHCP server. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. 2689 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS prefix Syntax Hierarchy Level Release Information Description Default Options prefix hostname | mac | none; [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82 remote-id] [edit forwarding-options helpers bootp dhcp-option82 remote-id] [edit forwarding-options helpers bootp interface interface-name dhcp-option82 remote-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure an optional prefix for the remote ID suboption in the DHCP option 82 information that is inserted by the switch into the packet header of a DHCP request before it forwards or relays the request to a DHCP server. If prefix is not explicitly specified, no prefix is appended to the remote ID. hostname—Name of the host system (the switch) that is forwarding or relaying the DHCP request from the DHCP client to the DHCP server. mac—MAC address of the host system (the switch) that is forwarding or relaying the DHCP request from the DHCP client to the DHCP server. none—No prefix is applied to the remote ID. Required Privilege Level Related Documentation 2690 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Chapter 98: Configuration Statements for Port Security proxy-arp Syntax Hierarchy Level Release Information Description proxy-arp ; [edit interfaces interface-name unit logical-unit-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the switch to respond to an ARP request if the switch has an active route to the ARP request’s target (destination). Default Proxy ARP is not enabled. The switch responds to an ARP request only if the destination IP address is its own. Options none—The switch responds to any ARP request for a local or remote address if the switch has a route to the target IP address. restricted—(Optional) The switch responds to ARP requests in which the physical networks of the source and target are different, and does not respond if the source and target IP addresses are in the same subnet. The switch must also have a route to the target IP address. unrestricted—(Optional) The switch responds to any ARP request for a local or remote address if the switch has a route to the target IP address. Default: unrestricted Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Proxy ARP on a J-EX Series Switch on page 2621 • Configuring Proxy ARP (CLI Procedure) on page 1153 2691 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS remote-id Syntax Hierarchy Level Release Information Description remote-id { prefix hostname | mac | none; use-interface-description; use-string string; } [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82] [edit forwarding-options helpers bootp dhcp-option82] [edit forwarding-options helpers bootp interface interface-name dhcp-option82] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Insert the remote-id suboption of DHCP option 82 (also known as the DHCP relay agent information option) in DHCP request packet headers before forwarding or relaying requests to a DHCP server. This suboption provides a trusted identifier for the host system that has forwarded or relayed requests to the server. The remaining statements are explained separately. Default Required Privilege Level Related Documentation 2692 If remote-id is not explicitly set, no remote ID value is inserted in the DHCP request packet header. If the remote-id option is specified but is not qualified by a keyword, the MAC address of the host device (the switch) is used as the remote ID. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Chapter 98: Configuration Statements for Port Security secure-access-port Syntax Hierarchy Level Release Information Description secure-access-port { 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); 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); 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 ; } (examine-dhcp | no-examine-dhcp); (ip-source-guard | no-ip-source-guard); mac-move-limit limit action action; } } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure port security features, including MAC limiting and whether interfaces can receive DHCP responses, and apply dynamic ARP inspection, DHCP snooping, IP source guard, DHCP option 82, and MAC move limiting to no VLANs, specific VLANs, or all VLANs. The remaining statements are explained separately. Required Privilege Level routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. 2693 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring DHCP Snooping, DAI , and MAC Limiting on a J-EX Series Switch with Access to a DHCP Server Through a Second Switch on page 2593 • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Understanding How to Protect Access Ports on J-EX Series Switches from Common Attacks on page 2546 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 static-ip Syntax Hierarchy Level Release Information Description Options static-ip ip-address { vlan vlan-name; mac mac-address; } [edit ethernet-switching-options secure-access-port interface (all|interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Static (fixed) IP address and static MAC address, with an associated VLAN, added to the DHCP snooping database. ip-address—IP address assigned to a device connected on the specified interface. The remaining statements are explained separately. Required Privilege Level Related Documentation 2694 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) on page 2645 Chapter 98: Configuration Statements for Port Security timeout Syntax Hierarchy Level Release Information Description Default Options timeout seconds; [edit ethernet-switching-options secure-access-port dhcp-snooping-file] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a timeout value for remote read and write operations. This value determines the amount of time that the switch waits for a remote system to respond when the DHCP snooping database is stored on a remote FTP site. None seconds —Value in seconds. Range: 10 through 3600 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 2695 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS traceoptions Syntax Hierarchy Level Release Information Description Default Options traceoptions { file filename ; flag flag ; } [edit ethernet-switching-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define global tracing operations for access security features on Ethernet switches. The traceoptions feature is disabled by default. disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all. file filename —Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. 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 (xk to specify KB, xm to specify MB, or xg to specify gigabytes), at which point the oldest trace file is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the size option. Range: 2 through 1000 Default: 3 files flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: 2696 • access-security—Trace access security events. • all—All tracing operations. • config-internals—Trace internal configuration operations. • forwarding-database—Trace forwarding database and next-hop events. • general—Trace general events. • interface—Trace interface events. • ip-source-guard—Trace IP source guard events. • krt—Trace communications over routing sockets. • lib—Trace library calls. • normal—Trace normal events. Chapter 98: Configuration Statements for Port Security • parse—Trace reading of the configuration. • regex-parse—Trace regular-expression parsing operations. • rtg—Trace redundant trunk group events. • state—Trace state transitions. • stp—Trace spanning-tree events. • task—Trace Ethernet-switching task processing. • timer—Trace Ethernet-switching timer processing. • vlan—Trace VLAN events. no-stamp—(Optional) Do not timestamp the trace file. Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output. no-world-readable—(Optional) Restrict file access to the user who created the file. replace—(Optional) Replace an existing trace file if there is one rather than appending to it. Default: If you do not include this option, tracing output is appended to an existing trace file. size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes. 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 also must specify a maximum file size with the files option. Syntax: xk to specify KB, xm to specify MB, or xg to specify gigabytes Range: 10 KB through 1 gigabyte Default: 128 KB world-readable—(Optional) Enable unrestricted file access. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Port Security for J-EX Series Switches Overview on page 2545 • J-EX Series Switches Interfaces Overview on page 863 • Understanding IP Source Guard for Port Security on J-EX Series Switches on page 2563 • Understanding Redundant Trunk Links on J-EX Series Switches on page 1049 • Understanding STP for J-EX Series Switches on page 1275 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 2697 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS use-interface-description Syntax Hierarchy Level use-interface-description; [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82 circuit-id] [edit forwarding-options helpers bootp dhcp-option82 circuit-id] [edit forwarding-options helpers bootp interface interface-name dhcp-option82 circuit-id] [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82 remote-id] [edit forwarding-options helpers bootp dhcp-option82 remote-id] [edit forwarding-options helpers bootp interface interface-name dhcp-option82 remote-id] Release Information Description Required Privilege Level Related Documentation 2698 Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Use the interface description rather than the interface name (the default) in the circuit ID or remote ID value in the DHCP option 82 information. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Chapter 98: Configuration Statements for Port Security use-string Syntax Hierarchy Level Release Information Description Options use-string string; [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82 remote-id] [edit forwarding-options helpers bootp dhcp-option82 remote-id] [edit forwarding-options helpers bootp interface interface-name dhcp-option82 remote-id] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Use a string rather than the MAC address of the host system (the default) in the remote ID value in the DHCP option 82 information. string—Character string used as the remote ID value. Range:1–255 characters Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. 2699 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS use-vlan-id Syntax Release Information Description Required Privilege Level Related Documentation 2700 use-vlan-id; Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Use the VLAN ID rather than the VLAN name (the default) in the circuit ID value in the DHCP option 82 information. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 • RFC 3046, DHCP Relay Agent Information Option, at http://tools.ietf.org/html/rfc3046. Chapter 98: Configuration Statements for Port Security vendor-id Syntax Hierarchy Level Release Information Description Default Options vendor-id ; [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82] [edit forwarding-options helpers bootp dhcp-option82] [edit forwarding-options helpers bootp interface interface-name dhcp-option82] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Insert a vendor ID in the DHCP option 82 information in a DHCP request packet header before forwarding or relaying the request to a DHCP server. If vendor-id is not explicitly configured for DHCP option 82, no vendor ID is set. string—(Optional) A single string that designates the vendor ID. Range: 1–255 characters Default: If you specify vendor-id with no string value, the default vendor ID Juniper is configured. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Example: Setting Up DHCP Option 82 with a J-EX Series Switch as Relay Agent Between Clients and a DHCP Server on page 2615 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 • Setting Up DHCP Option 82 with the Switch as a Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2646 • [edit forwarding-options] Configuration Statement Hierarchy on page 43 2701 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS vlan Syntax Hierarchy Level Release Information Description vlan (all | vlan-name) { (arp-inspection | no-arp-inspection); 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 ; } (examine-dhcp | no-examine-dhcp); (ip-source-guard | no-ip-source-guard); mac-move-limit limit action action; } [edit ethernet-switching-options secure-access-port] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply DHCP snooping, dynamic ARP inspection (DAI), IP source guard, DHCP option 82, and MAC move limiting. The remaining statements are explained separately. TIP: To display a list of all configured VLANs on the system, including VLANs that are configured but not committed, type ? after vlan or vlans in your configuration mode command line. Note that only one VLAN is displayed for a VLAN range. Options all—Apply DHCP snooping, DAI, IP source guard, DHCP option 82, and MAC move limiting to all VLANs. vlan-name—Apply DHCP snooping, DAI, IP source guard, DHCP option 82, and MAC move limiting to the specified VLAN. Required Privilege Level Related Documentation 2702 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 Chapter 98: Configuration Statements for Port Security • Example: Setting Up DHCP Option 82 on a J-EX Series Switch with No Relay Agent Between Clients and DHCP Server on page 2617 • Enabling Dynamic ARP Inspection (CLI Procedure) on page 2633 • Enabling DHCP Snooping (CLI Procedure) on page 2630 • Configuring IP Source Guard (CLI Procedure) on page 2643 • Configuring MAC Move Limiting (CLI Procedure) on page 2639 • Setting Up DHCP Option 82 on the Switch with No Relay Agent Between Clients and DHCP Server (CLI Procedure) on page 2649 vlan Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation vlan vlan-name; [edit ethernet-switching-options secure-access-port interface (all | interface-name) static-ip ip-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate the static IP address with the specified VLAN associated with the specified interface. vlan-name —Name of a specific VLAN associated with the specified interface. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Static IP Addresses for DHCP Bindings on Access Ports (CLI Procedure) on page 2645 2703 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS write-interval Syntax Hierarchy Level Release Information Description Default Options write-interval seconds; [edit ethernet-switching-options secure-access-port dhcp-snooping-file] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify how frequently the switch writes the database entries from memory into the specified DHCP snooping database file. None seconds—Value in seconds. Range: 60 through 86400 Required Privilege Level Related Documentation 2704 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 CHAPTER 99 Operational Mode Commands for Port Security 2705 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear arp inspection statistics Syntax Release Information Description Options clear arp inspection statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear ARP inspection statistics. none—Clears ARP statistics on all interfaces. interface interface-names—(Optional) Clear ARP statistics on one or more interfaces. Required Privilege Level Related Documentation List of Sample Output Output Fields clear arp inspection statistics 2706 clear • show arp inspection statistics on page 2709 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That DAI Is Working Correctly on page 2656 clear arp inspection statistics on page 2706 This command produces no output. user@switch> clear arp inspection statistics Chapter 99: Operational Mode Commands for Port Security clear dhcp snooping binding Syntax Release Information Description Options clear dhcp snooping binding Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear the DHCP snooping database information. mac (all | mac-address)—(Optional) Clear DHCP snooping information for the specified MAC address or all MAC addresses. vlan (all | vlan-name )—(Optional) Clear DHCP snooping information for the specified VLAN or all VLANs. Required Privilege Level Related Documentation List of Sample Output Output Fields clear dhcp snooping binding clear • show dhcp snooping binding on page 2710 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That DHCP Snooping Is Working Correctly on page 2654 clear dhcp snooping binding on page 2707 This command produces no output. user@switch> clear dhcp snooping binding 2707 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear dhcp snooping statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields clear dhcp snooping statistics clear dhcp snooping statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear all Dynamic Host Configuration Protocol (DHCP) snooping statistics. view • show dhcp snooping statistics on page 2711 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 clear dhcp snooping statistics on page 2708 See show dhcp snooping statistics for an explanation of the output fields. The following sample output displays the DHCP snooping statistics before and after the clear dhcp snooping statistics command is issued. user@switch> show dhcp snooping statistics Successful Transfers : 0 Failed Transfers : Successful Reads : 0 Failed Reads : Successful Writes : 0 Failed Writes : 21 0 21 user@switch> clear dhcp snooping statistics user@switch> show dhcp snooping statistics Successful Transfers : 0 Failed Transfers : Successful Reads : 0 Failed Reads : Successful Writes : 0 Failed Writes : 2708 0 0 0 Chapter 99: Operational Mode Commands for Port Security show arp inspection statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show arp inspection statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display ARP inspection statistics. view • clear arp inspection statistics on page 2706 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That DAI Is Working Correctly on page 2656 show arp inspection statistics on page 2709 Table 330 on page 2709 lists the output fields for the show arp inspection statistics command. Output fields are listed in the approximate order in which they appear. Table 330: show arp inspection statistics Output Fields Field Name Field Description Level of Output Interface Interface on which ARP inspection has been applied. All levels Packets received Total number of packets total that underwent ARP inspection. All levels ARP inspection pass Total number of packets that passed ARP inspection. All levels ARP inspection failed Total number of packets that failed ARP inspection. All levels show arp inspection statistics user@switch> show arp inspection statistics Interface --------ge-0/0/0 ge-0/0/1 ge-0/0/2 ge-0/0/3 ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 Packets received ----------------0 0 0 0 0 0 0 703 ARP inspection pass ------------------0 0 0 0 0 0 0 701 ARP inspection failed --------------------0 0 0 0 0 0 0 2 2709 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show dhcp snooping binding Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show dhcp snooping binding Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the DHCP snooping database information. view • clear dhcp snooping binding on page 2707 • Example: Configuring Port Security, with DHCP Snooping, DAI, MAC Limiting, and MAC Move Limiting, on a J-EX Series Switch on page 2569 • Verifying That DHCP Snooping Is Working Correctly on page 2654 show dhcp snooping binding on page 2710 Table 331 on page 2710 lists the output fields for the show dhcp snooping binding command. Output fields are listed in the approximate order in which they appear. Table 331: show dhcp snooping binding Output Fields Field Name Field Description Level of Output MAC Address MAC address of the network device; bound to the IP address. All levels IP Address IP address of the network device; bound to the MAC address. All levels Lease Lease granted to the IP address. All levels Type How the MAC address was acquired. All levels VLAN VLAN name of the network device whose MAC address is shown. All levels Interface Interface address (port). All levels show dhcp snooping binding user@switch> show dhcp snooping binding DHCP Snooping Information: MAC Address IP Address -------------------------00:00:01:00:00:03 192.0.2.0 00:00:01:00:00:04 192.0.2.1 00:00:01:00:00:05 192.0.2.5 2710 Lease ----640 720 800 Type ------dynamic dynamic dynamic VLAN ---guest guest guest Interface --------ge-0/0/12.0 ge-0/0/12.0 ge-0/0/13.0 Chapter 99: Operational Mode Commands for Port Security show dhcp snooping statistics Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show dhcp snooping statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display statistics for read and write operations to the DHCP snooping database. view • clear dhcp snooping statistics on page 2708 • Understanding DHCP Snooping for Port Security on J-EX Series Switches on page 2549 show dhcp snooping statistics on page 2711 Table 332 on page 2711 lists the output fields for the show dhcp snooping statistics command. Output fields are listed in the approximate order in which they appear. Table 332: show dhcp snooping statistics Output Fields Field Name Field Description Successful Transfers Number of entries successfully transferred from memory to the DHCP snooping database. Successful Reads Number of entries successfully read from memory to the DHCP snooping database. Successful Writes Number of entries successfully written from memory to the DHCP snooping database. Failed Transfers Number of entries that failed being transferred from memory to the DHCP snooping database. Failed Reads Number of entries that failed being read from memory to the DHCP snooping database. Failed Writes Number of entries that failed being written from memory to the DHCP snooping database. show dhcp snooping statistics user@switch> show dhcp snooping statistics Successful Transfers : 0 Failed Transfers : Successful Reads : 0 Failed Reads : Successful Writes : 0 Failed Writes : 21 0 21 2711 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ethernet-switching table Syntax Release Information Description Options show ethernet-switching table Command introduced before Junos OS Release 10.2 for J-EX Series switches. Displays the Ethernet switching table. none—(Optional) Display brief information about the Ethernet switching table. brief | detail | extensive | summary—(Optional) Display the specified level of output. management-vlan—(Optional) Display the Ethernet switching table for a management VLAN. interface-name—(Optional) Display the Ethernet switching table for a specific interface. sort-by (name | tag)—(Optional) Display VLANs in ascending order of VLAN IDs or VLAN names. vlan vlan-name—(Optional) Display the Ethernet switching table for a specific VLAN. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Example: Setting Up Basic Bridging and a VLAN for a J-EX Series Switch on page 1063 • Example: Setting Up Bridging with Multiple VLANs for J-EX Series Switches on page 1070 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Example: Setting Up Q-in-Q Tunneling on J-EX Series Switches on page 1105 show ethernet-switching table on page 2713 show ethernet-switching table brief on page 2714 show ethernet-switching table detail on page 2714 show ethernet-switching table extensive on page 2715 show ethernet-switching table interface ge-0/0/1 on page 2715 Table 333 on page 2712 lists the output fields for the show ethernet-switching table command. Output fields are listed in the approximate order in which they appear. Table 333: show ethernet-switching table Output Fields Field Name Field Description Level of Output VLAN The name of a VLAN. All levels 2712 Chapter 99: Operational Mode Commands for Port Security Table 333: show ethernet-switching table Output Fields (continued) Field Name Field Description Level of Output Tag The VLAN ID tag name or number. extensive MAC or MAC address The MAC address associated with the VLAN. All levels Type The type of MAC address. Values are: All levels • static—The MAC address is manually created. • learn—The MAC address is learned dynamically from a packet's source MAC address. • flood—The MAC address is unknown and flooded to all members. Age The time remaining before the entry ages out and is removed from the Ethernet switching table. All levels Interfaces Interface associated with learned MAC addresses or All-members (flood entry). All levels Learned For learned entries, the time which the entry was added to the Ethernet-switching table. detail, extensive Nexthop index The nexthop index number. detail, extensive show ethernet-switching table user@switch> show ethernet-switching table Ethernet-switching table: 57 entries, 17 learned VLAN MAC address Type F2 * Flood F2 00:00:05:00:00:03 Learn F2 00:19:e2:50:7d:e0 Static Linux * Flood Linux 00:19:e2:50:7d:e0 Static Linux 00:30:48:90:54:89 Learn T1 * Flood T1 00:00:05:00:00:01 Learn T1 00:00:5e:00:01:00 Static T1 00:19:e2:50:63:e0 Learn T1 00:19:e2:50:7d:e0 Static T10 * Flood T10 00:00:5e:00:01:09 Static T10 00:19:e2:50:63:e0 Learn T10 00:19:e2:50:7d:e0 Static T111 * Flood T111 00:19:e2:50:63:e0 Learn T111 00:19:e2:50:7d:e0 Static T111 00:19:e2:50:ac:00 Learn T2 * Flood T2 00:00:5e:00:01:01 Static T2 00:19:e2:50:63:e0 Learn T2 00:19:e2:50:7d:e0 Static T3 * Flood T3 00:00:5e:00:01:02 Static T3 00:19:e2:50:63:e0 Learn T3 00:19:e2:50:7d:e0 Static T4 * Flood Age 0 0 0 0 0 0 0 0 0 - Interfaces All-members ge-0/0/44.0 Router All-members Router ge-0/0/47.0 All-members ge-0/0/46.0 Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members ge-0/0/15.0 Router ge-0/0/15.0 All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members 2713 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS T4 T4 [output truncated] 00:00:5e:00:01:03 Static 00:19:e2:50:63:e0 Learn - Router 0 ge-0/0/46.0 show ethernet-switching table brief user@switch> show ethernet-switching table brief Ethernet-switching table: 57 entries, 17 learned VLAN MAC address Type F2 * Flood F2 00:00:05:00:00:03 Learn F2 00:19:e2:50:7d:e0 Static Linux * Flood Linux 00:19:e2:50:7d:e0 Static Linux 00:30:48:90:54:89 Learn T1 * Flood T1 00:00:05:00:00:01 Learn T1 00:00:5e:00:01:00 Static T1 00:19:e2:50:63:e0 Learn T1 00:19:e2:50:7d:e0 Static T10 * Flood T10 00:00:5e:00:01:09 Static T10 00:19:e2:50:63:e0 Learn T10 00:19:e2:50:7d:e0 Static T111 * Flood T111 00:19:e2:50:63:e0 Learn T111 00:19:e2:50:7d:e0 Static T111 00:19:e2:50:ac:00 Learn T2 * Flood T2 00:00:5e:00:01:01 Static T2 00:19:e2:50:63:e0 Learn T2 00:19:e2:50:7d:e0 Static T3 * Flood T3 00:00:5e:00:01:02 Static T3 00:19:e2:50:63:e0 Learn T3 00:19:e2:50:7d:e0 Static T4 * Flood T4 00:00:5e:00:01:03 Static T4 00:19:e2:50:63:e0 Learn [output truncated] show ethernet-switching table detail user@switch> show ethernet-switching table detail Ethernet-switching table: 5 entries, 2 learned VLAN: default, Tag: 0, MAC: *, Interface: All-members Interfaces: ge-0/0/11.0, ge-0/0/20.0, ge-0/0/30.0, ge-0/0/36.0, ge-0/0/3.0 Type: Flood Nexthop index: 1307 Age 0 0 0 0 0 0 0 0 0 0 Interfaces All-members ge-0/0/44.0 Router All-members Router ge-0/0/47.0 All-members ge-0/0/46.0 Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members ge-0/0/15.0 Router ge-0/0/15.0 All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 Router All-members Router ge-0/0/46.0 VLAN: default, Tag: 0, MAC: 00:1f:12:30:b8:83, Interface: ge-0/0/3.0 Type: Learn, Age: 0, Learned: 20:09:26 Nexthop index: 1315 VLAN: v1, Tag: 101, MAC: *, Interface: All-members Interfaces: ge-0/0/31.0 Type: Flood Nexthop index: 1313 VLAN: v1, Tag: 101, MAC: 00:1f:12:30:b8:89, Interface: ge-0/0/31.0 Type: Learn, Age: 0, Learned: 20:09:25 Nexthop index: 1312 2714 Chapter 99: Operational Mode Commands for Port Security VLAN: v2, Tag: 102, MAC: *, Interface: All-members Interfaces: ae0.0 Type: Flood Nexthop index: 1317 show ethernet-switching table extensive user@switch> show ethernet-switching table extensive Ethernet-switching table: 3 entries, 1 learned VLAN: v1, Tag: 10, MAC: *, Interface: All-members Interfaces: ge-0/0/14.0, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0, ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/8.0, ge-0/0/10.0, ge-0/0/0.0 Type: Flood Nexthop index: 567 VLAN: v1, Tag: 10, MAC: 00:21:59:c6:93:22, Interface: Router Type: Static Nexthop index: 0 VLAN: v1, Tag: 10, MAC: 00:21:59:c9:9a:4e, Interface: ge-0/0/14.0 Type: Learn, Age: 0, Learned: 18:40:50 Nexthop index: 564 show ethernet-switching table interface ge-0/0/1 user@switch> show ethernet-switching table interface ge-0/0/1 Ethernet-switching table: 1 unicast entries VLAN MAC address Type Age Interfaces V1 * Flood - All-members V1 00:00:05:00:00:05 Learn 0 ge-0/0/1.0 2715 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show ip-source-guard Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show ip-source-guard Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display IP source guard database information. view • Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN on page 2608 • Example: Configuring IP Source Guard with Other J-EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces on page 2600 • Verifying That IP Source Guard Is Working Correctly on page 2662 show ip-source-guard on page 2716 Table 334 on page 2716 lists the output fields for the show ip-source-guard command. Output fields are listed in the approximate order in which they appear. Table 334: show ip-source-guard Output Fields Field Name Field Description VLAN VLAN on which IP source guard is enabled. Interface Access interface associated with the VLAN in column 1. Tag VLAN ID for the VLAN in column 1. Possible values are: • 0, indicating the VLAN is not tagged. • 1 – 4093 IP Address Source IP address for a device connected to the interface in column 2. A value of * (star, or asterisk) indicates that IP source guard is not enabled on this VLAN but the interface is shared with a VLAN that is enabled for IP source guard. MAC Address Source MAC address for a device connected to the interface in column 2. A value of * (star, or asterisk) indicates that IP source guard is not enabled on this VLAN but the interface is shared with a VLAN that is enabled for IP source guard. show ip-source-guard 2716 user@switch> show ip-source-guard IP source guard information: Interface Tag IP Address MAC Address VLAN ge-0/0/12.0 0 10.10.10.7 00:30:48:92:A5:9D vlan100 ge-0/0/13.0 0 10.10.10.9 00:30:48:8D:01:3D vlan100 Chapter 99: Operational Mode Commands for Port Security ge—0/0/13.0 100 * * voice 2717 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show system statistics arp Syntax Release Information Description Required Privilege Level 2718 show system statistics arp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display system-wide Address Resolution Protocol (ARP) statistics. view Related Documentation • Example: Configuring Unrestricted Proxy ARP on a J-EX Series Switch on page 2621 • Verifying That Unrestricted Proxy ARP Is Working Correctly on page 1164 Sample Output user@switch> show system statistics arp arp: 90060 datagrams received 34 ARP requests received 610 ARP replies received 0 resolution request received 0 unrestricted proxy requests 0 restricted proxy requests 0 received proxy requests 0 unrestricted proxy requests not proxied 0 restricted proxy requests not proxied 0 datagrams with bogus interface 0 datagrams with incorrect length 0 datagrams for non-IP protocol 0 datagrams with unsupported op code 0 datagrams with bad protocol address length 0 datagrams with bad hardware address length 0 datagrams with multicast source address 0 datagrams with multicast source address 0 datagrams with my own hardware address 0 datagrams for an address not on the interface 0 datagrams with a broadcast source address 294 datagrams with source address duplicate to mine 89113 datagrams which were not for me 0 packets discarded waiting for resolution 0 packets sent after waiting for resolution 309 ARP requests sent 35 ARP replies sent 0 requests for memory denied 0 requests dropped on entry 0 requests dropped during retry 0 requests dropped due to interface deletion 0 requests on unnumbered interfaces 0 new requests on unnumbered interfaces 0 replies for from unnumbered interfaces 0 requests on unnumbered interface with non-subnetted donor 0 replies from unnumbered interface with non-subnetted donor PART 20 Routing Policy and Packet Filtering (Firewall Filters) • Firewall Filters—Overview on page 2721 • Examples of Firewall Filters Configuration on page 2755 • Configuring Firewall Filters on page 2779 • Verifying Firewall Filter Configuration on page 2799 • Troubleshooting Firewall Filters on page 2803 • Configuration Statements for Firewall Filters on page 2805 • Operational Mode Commands for Firewall Filters on page 2835 2719 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2720 CHAPTER 100 Firewall Filters—Overview • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding Planning of Firewall Filters on page 2724 • Understanding Firewall Filter Processing Points for Bridged and Routed Packets on J-EX Series Switches on page 2726 • Understanding How Firewall Filters Control Packet Flows on page 2727 • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Understanding How Firewall Filters Are Evaluated on page 2746 • Understanding Firewall Filter Match Conditions on page 2748 • Understanding How Firewall Filters Test a Packet's Protocol on page 2752 • Understanding the Use of Policers in Firewall Filters on page 2752 • Understanding Filter-Based Forwarding for J-EX Series Switches on page 2753 Firewall Filters for J-EX Series Switches Overview Firewall filters provide rules that define whether to permit, deny, or forward packets that are transiting an interface on a J-EX Series Switch from a source address to a destination address. You configure firewall filters to determine whether to permit, deny, or forward traffic before it enters or exits a port, VLAN, or Layer 3 (routed) interface to which the firewall filter is applied. An ingress firewall filter is a filter that is applied to packets that are entering a network. An egress firewall filter is a filter that is applied to packets that are exiting a network. You can configure firewall filters to subject packets to filtering, class-of-service (CoS) marking (grouping similar types of traffic together, and treating each type of traffic as a class with its own level of service priority), and traffic policing (controlling the maximum rate of traffic sent or received on an interface). • Firewall Filter Types on page 2721 • Firewall Filter Components on page 2722 • Firewall Filter Processing on page 2723 Firewall Filter Types The following firewall filter types are supported for J-EX Series switches: • Port (Layer 2) firewall filter—Port firewall filters apply to Layer 2 switch ports. You can apply port firewall filters in both ingress and egress directions on a physical port. 2721 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • VLAN firewall filter—VLAN firewall filters provide access control for packets that enter a VLAN, are bridged within a VLAN, and leave a VLAN. You can apply VLAN firewall filters in both ingress and egress directions on a VLAN. VLAN firewall filters are applied to all packets that are forwarded to or forwarded from the VLAN. • Router (Layer 3) firewall filter—You can apply a router firewall filter in both ingress and egress directions on Layer 3 (routed) interfaces and routed VLAN interfaces (RVIs). You can apply a router firewall filter in the ingress direction on the loopback interface (lo0) also. NOTE: Firewall filters configured on loopback interfaces are applied only to packets that are sent to the routing engine CPU for further processing. Firewall filters are not applied to packets transiting the management interface (me0). On J-EX4200 and J-EX8200 Ethernet switches, you can apply a router firewall filter to both IPv4 and IPv6 traffic. You can apply firewall filter match conditions to IPv6 traffic on Layer 3 interfaces, aggregated Ethernet interfaces, and loopback interfaces. To configure port firewall filters and VLAN firewall filters for IPv6 traffic, you must include the match condition ether-type ipv6 and apply the filter on Layer 2 interfaces or VLANs. When you include the match condition ether-type ipv6 in a term, you must ensure that other match conditions specified in the term are valid for IPv6 traffic. If the port firewall filter or VLAN firewall filter term contains the match condition ether-type ipv6, with no other IPv6 match condition specified, all IPv6 traffic is matched. NOTE: A term without the match condition ether-type ipv6 applies only to IPv4 traffic, and a term with that match condition applies only to IPv6 traffic. Hence, to configure port and VLAN firewall filters for both IPv4 and IPv6 traffic, you should configure two different terms, once each for IPv4 and IPv6 traffic. To apply a firewall filter, you must: 1. Configure the firewall filter. 2. Apply the firewall filter to a port, VLAN, or Layer 3 interface. You can apply a firewall filter to aggregated Ethernet interfaces and loopback interfaces also. Firewall Filter Components In a firewall filter, you first define the family address type, (ethernet-switching, inet, or inet6), and then you define one or more terms that specify the filtering criteria and the action to take if a match occurs. The maximum number of terms allowed per firewall filter depends on the switch platform: • 2722 2048 for J-EX4200 switches—as allocated by the dynamic allocation of Ternary Content Addressable Memory (TCAM) for port, VLAN, and router firewall filters Chapter 100: Firewall Filters—Overview • Determined by the dynamic allocation of TCAM for port, VLAN, and router firewall filters on J-EX8200 switches NOTE: The on-demand dynamic allocation of the shared space TCAM in J-EX8200 switches is achieved by assigning free space blocks to firewall filters. Firewall filters are categorized into two different pools. Port and VLAN filters are pooled together (the memory threshold for this pool is 22K) while router firewall filters are pooled separately (the threshold for this pool is 32K). The assignment happens based on the filter pool type. Free space blocks can be shared only among the firewall filters belonging to the same filter pool type. An error message is generated when you try to configure a firewall filter beyond the TCAM threshold. Each term consists of the following components: • Match conditions—Specifies the values or fields that the packet must contain. You can define various match conditions, including the IP source address field, IP destination address field, Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) source port field, IP protocol field, Internet Control Message Protocol (ICMP) packet type, TCP flags, and interfaces. • Action—Specifies what to do if a packet matches the match conditions. Possible actions are to accept or discard the packet or to send the packet to a specific virtual routing interface. In addition, packets can be counted to collect statistical information. If no action is specified for a term, the default action is to accept the packet. Firewall Filter Processing The order of the terms within a firewall filter configuration is important. Packets are tested against each term in the order in which the terms are listed in the firewall filter configuration. When a firewall filter contains multiple terms, the switch takes a top-down approach and compares a packet against the first term in the firewall filter. If the packet matches the first term, the switch executes the action defined by that term to either permit or deny the packet, and no other terms are evaluated. If the switch does not find a match between the packet and first term, it compares the packet to the next term in the firewall filter by using the same match process. If no match occurs between the packet and the second term, the switch continues to compare the packet to each successive term defined in the firewall filter until a match is found. If a packet does not match any terms in a firewall filter, the default action is to discard the packet. Related Documentation • Understanding Planning of Firewall Filters on page 2724 • Understanding Firewall Filter Processing Points for Bridged and Routed Packets on J-EX Series Switches on page 2726 • Understanding How Firewall Filters Are Evaluated on page 2746 • Understanding Firewall Filter Match Conditions on page 2748 • Understanding the Use of Policers in Firewall Filters on page 2752 2723 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Understanding Filter-Based Forwarding for J-EX Series Switches on page 2753 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 Understanding Planning of Firewall Filters Before you create a firewall filter and apply it to an interface, determine what you want the firewall filter to accomplish and how to use its match conditions and actions to achieve your goals. You must understand how packets are matched to match conditions, the default and configured actions of the firewall filter, and proper placement of the firewall filter. You can configure and apply no more than one firewall filter per port, VLAN, or router interface, per direction. The following limits apply for the number of firewall filter terms allowed per filter on various switch models: • On J-EX4200 switches, the number of terms allowed per filter cannot exceed 2048. • On J-EX8200 switches, the number of terms allowed per filter cannot exceed 32768. In addition, you should try to be conservative in the number of terms (rules) that you include in each firewall filter because a large number of terms requires longer processing time during a commit and also can make firewall filter testing and troubleshooting more difficult. Similarly, applying firewall filters across many switch and router interfaces can make testing and troubleshooting the rules of those filters difficult. Before you configure and apply firewall filters, answer the following questions for each of those firewall filters: 1. What is the purpose of the firewall filter? For example, you can use a firewall filter to limit traffic to source and destination MAC addresses, specific protocols, or certain data rates or to prevent denial of service (DoS) attacks. 2. What are the appropriate match conditions? a. Determine the packet header fields that the packet must contain for a match. Possible fields include: 2724 • Layer 2 header fields—Source and destination MAC addresses, dot1q tag, Ethernet type, and VLAN • Layer 3 header fields—Source and destination IP addresses, protocols, and IP options (IP precedence, IP fragmentation flags, TTL type) • TCP header fields—Source and destination ports and flags • ICMP header fields—Packet type and code Chapter 100: Firewall Filters—Overview b. Determine the port, VLAN, or router interface on which the packet was received. 3. What are the appropriate actions to take if a match occurs? Possible actions to take if a match occurs are accept, discard, and forward to a routing instance. 4. What additional action modifiers might be required? Determine whether additional actions are required if a packet matches a match condition; for example, you can specify an action modifier to count, analyze, or police packets. 5. On what interface should the firewall filter be applied? Start with the following basic guidelines: • If all the packets entering a port need to be exposed to filtering, then use port firewall filters. • If all the packets that are bridged need filtering, then use VLAN firewall filters. • If all the packets that are routed need filtering, then use router firewall filters. Before you choose the interface on which to apply a firewall filter, understand how that placement can impact traffic flow to other interfaces. In general, apply a firewall filter that filters on source and destination IP addresses, IP protocols, or protocol information—such as ICMP message types, and TCP and UDP port numbers—nearest to the source devices. However, typically apply a firewall filter that filters only on a source IP address nearest to the destination devices. When applied too close to the source device, a firewall filter that filters only on a source IP address could potentially prevent that source device from accessing other services that are available on the network. NOTE: Egress firewall filters do not affect the flow of locally generated control packets from the Routing Engine. 6. In which direction should the firewall filter be applied? You can apply firewall filters to ports on the switch to filter packets that are entering a port. You can apply firewall filters to VLANs, and Layer 3 (routed) interfaces to filter packets that are entering or exiting a VLAN or routed interface. Typically, you configure different sets of actions for traffic entering an interface than you configure for traffic exiting an interface. Related Documentation • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding the Use of Policers in Firewall Filters on page 2752 • Understanding How Firewall Filters Are Evaluated on page 2746 • Understanding Filter-Based Forwarding for J-EX Series Switches on page 2753 2725 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 Understanding Firewall Filter Processing Points for Bridged and Routed Packets on J-EX Series Switches J-EX Series Switches are multilayered switches that provide Layer 2 switching and Layer 3 routing. You apply firewall filters at multiple processing points in the packet forwarding path on J-EX Series switches. At each processing point, the action to be taken on a packet is determined based on the results of the lookup in the switch's forwarding table. A table lookup determines which exit port on the switch to use to forward the packet. For both bridged unicast packets and routed unicast packets, firewall filters are evaluated and applied hierarchically. First, a packet is checked against the port firewall filter, if present. If the packet is permitted, it is then checked against the VLAN firewall filter, if present. If the packet is permitted, it is then checked against the router firewall filter, if present. The packet must be permitted by the router firewall filter before it is processed. Figure 75 on page 2726 shows the various firewall filter processing points in the packet forwarding path in a multilayered switching platform. Figure 75: Firewall Filter Processing Points in the Packet Forwarding Path 2726 Chapter 100: Firewall Filters—Overview For a multicast packet that results in replications, an egress firewall filter is applied to each copy of the packet based on its corresponding egress VLAN. For Layer 2 (bridged) unicast packets, the following firewall filter processing points apply: • Ingress port firewall filter • Ingress VLAN firewall filter • Egress port firewall filter • Egress VLAN firewall filter For Layer 3 (routed and multilayer-switched) unicast packets, the following firewall filter processing points apply: Related Documentation • Ingress port firewall filter • Ingress VLAN firewall filter (Layer 2 CoS) • Ingress router firewall filter (Layer 3 CoS) • Egress router firewall filter • Egress VLAN firewall filter • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding How Firewall Filters Control Packet Flows on page 2727 • Understanding Bridging and VLANs on J-EX Series Switches on page 1041 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 Understanding How Firewall Filters Control Packet Flows J-EX Series Switches support firewall filters that allow you to control flows of data packets and local packets. Data packets are chunks of data that transit the switch as they are forwarded from a source to a destination. Local packets are chunks of data that are destined for or sent by the switch. Local packets usually contain routing protocol data, data for IP services such as Telnet or SSH, and data for administrative protocols such as the Internet Control Message Protocol (ICMP). You create firewall filters to protect your switch from excessive traffic transiting the switch to a network destination or destined for the Routing Engine on the switch. Firewall filters that control local packets can also protect your switch from external incidents such as denial-of-service (DoS) attacks. Firewall filters affect packet flows entering in to or exiting from the switch's interfaces: • Ingress firewall filters affect the flow of data packets that are received by the switch's interfaces. The Packet Forwarding Engine (PFE) handles this flow. When a switch receives a data packet on an interface, the switch determines where to forward the packet by looking in the forwarding table for the best route (Layer 2 switching, Layer 3 2727 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS routing) to a destination. Data packets are forwarded to their destination through an outgoing interface. Locally destined packets are forwarded to the Routing Engine. • Egress firewall filters affect the flow of data packets that are transmitted from the switch's interfaces but do not affect the flow of locally generated control packets from the Routing Engine. The Packet Forwarding Engine handles the flow of data packets that are transmitted from the switch, and egress firewall filters are applied here. The Packet Forwarding Engine also handles the flow of control packets from the Routing Engine. Figure 76 on page 2728 illustrates the application of ingress and egress firewall filters to control the flow of packets through the switch. Figure 76: Application of Firewall Filters to Control Packet Flow 1. Ingress firewall filter applied to control locally destined packets that are received on the switch's interfaces and are destined for the Routing Engine. 2. Ingress firewall filter applied to control incoming packets on the switch's interfaces. 3. Egress firewall filter applied to control packets that are transiting the switch's interfaces. Related Documentation • Understanding Firewall Filter Processing Points for Bridged and Routed Packets on J-EX Series Switches on page 2726 • Understanding How Firewall Filters Are Evaluated on page 2746 Firewall Filter Match Conditions and Actions for J-EX Series Switches Each term in a firewall filter consists of match conditions and an action. Match conditions are the values or fields that a packet must contain. You can define multiple, single, or no match conditions. If no match conditions are specified for the term, all packets are matched by default. The action is the action that the switch takes if a packet matches the match conditions for the specific term. Action modifiers are optional and specify one 2728 Chapter 100: Firewall Filters—Overview or more actions that the switch takes if a packet matches the match conditions for the specific term. Allowed actions are accept a packet or discard a packet. In addition, you can specify action modifiers to count, mirror, rate limit, and classify packets. For each firewall filter, you define the terms that specify the filtering criteria (match conditions) to apply to packets and the action for the switch to take if a match occurs. The string that defines a match condition is called a match statement. The following tables list various match conditions and their support platforms, binding points, and actions. • Table 335 on page 2729 describes the match conditions you can specify when configuring a firewall filter for IPv4 traffic. • Table 336 on page 2738 describes the match conditions you can specify when configuring a firewall filter for IPv6 traffic. • Table 337 on page 2744 shows the actions that you can specify in a term. • Table 338 on page 2744 shows the action modifiers that you can specify in a term. Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches Supported Platforms and Bind Points Match Condition Description Ingress Egress destination-address ip-address IP destination address field, which is the address of the final destination node. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs For IPv6, specifies the 128-bit address that is the final destination node address for the packet. The filter description syntax supports the text representations for IPv6 addresses as described in RFC 2373, IP Version6 Addressing Architecture. destination-mac-address mac-address Destination media access control (MAC) address of the packet. 2729 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress destination-port number TCP or User Datagram Protocol (UDP) destination port field. Typically, you specify this match in conjunction with the protocol match statement to determine which protocol is used on the port. In place of the numeric value, you can specify one of the following text synonyms (the port numbers are also listed): • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces afs (1483), bgp (179), biff (512), bootpc (68), bootps (67), cmd (514), cvspserver (2401), dhcp (67), domain (53), eklogin (2105), ekshell (2106), exec (512), finger (79), ftp (21), ftp-data (20), http (80), https (443), ident (113), imap (143), kerberos-sec (88), klogin (543), kpasswd (761), krb-prop (754), krbupdate (760), kshell (544), ldap (389), login (513), mobileip-agent (434), mobilip-mn (435), msdp (639), netbios-dgm (138), netbios-ns (137), netbios-ssn (139), nfsd (2049), nntp (119), ntalk (518), ntp (123), pop3 (110), pptp (1723), printer (515), radacct (1813),radius (1812), rip (520), rkinit (2108), smtp (25), snmp (161), snmptrap (162), snpp (444), socks (1080), ssh (22), sunrpc (111), syslog (514), tacacs-ds (65), talk (517), telnet (23), tftp (69), timed (525), who (513), xdmcp (177), zephyr-clt (2103), zephyr-hm (2104) 2730 Chapter 100: Firewall Filters—Overview Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress destination-prefix-list prefix-list IP destination prefix list field. • • You can define a list of IP address prefixes under a prefix-list alias for frequent use. You make this definition at the [edit policy-options] hierarchy level. J-EX4200—ports, VLANs, and Layer 3 interfaces J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—not supported • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs dot1q-tag number dot1q-user-priority number The tag field in the Ethernet header. The tag values can be 1–4095. User-priority field of the tagged Ethernet packet. User-priority values can be 0–7. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • background (1)—Background • best-effort (0)—Best effort • controlled-load (4)—Controlled load • excellent-load (3)—Excellent load • network-control (7)—Network control reserved traffic • standard (2)—Standard or Spare • video (5)—Video • voice (6)—Voice 2731 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress dscp number Differentiated Services code point (DSCP). The DiffServ protocol uses the type-of-service (ToS) byte in the IP header. The most significant six bits of this byte form the DSCP. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—not supported. You can specify DSCP in hexadecimal, binary, or decimal form. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • ef (46)—as defined in RFC 2598, An Expedited Forwarding PHB. • af11 (10), af12 (12), af13 (14); af21 (18), af22 (20), af23 (22); af31 (26), af32 (28), af33 (30); af41 (34), af42 (36), af43 (38) These four classes, with three drop precedences in each class, for a total of 12 code points, are defined in RFC 2597, Assured Forwarding PHB. ether-type [aarp | appletalk | arp | ipv4 | ipv6 | mpls—multicast | mpls-unicast | oam | ppp | pppoe-discovery | pppoe-session | sna |value] Ethernet type field of a packet. The EtherType value specifies what protocol is being transported in the Ethernet frame. In place of the numeric value, you can specify one of the following text synonyms: • aarp—EtherType value AARP (0x80F3) • appletalk—EtherType value AppleTalk (0x809B) • arp—EtherType value ARP (0x0806) • ipv4—EtherType value IPv4 (0x0800) • ipv6—EtherType value IPv6 (0x08DD) • mpls multicast—EtherType value MPLS multicast (0x8848) • mpls unicast—EtherType value MPLS unicast (0x8847) • oam—EtherType value OAM (0x88A8) • ppp—EtherType value PPP (0x880B) • pppoe-discovery—EtherType value PPPoE Discovery Stage (0x8863) • pppoe-session—EtherType value PPPoE Session Stage (0x8864) • 2732 sna—EtherType value SNA (0x80D5) Chapter 100: Firewall Filters—Overview Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress fragment-flags fragment-flags IP fragmentation flags, specified in symbolic or hexadecimal formats. You can specify one of the following options: • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—ports, VLANs, and Layer 3 interfaces J-EX8200—not supported • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—VLANs and Layer 3 interfaces • • J-EX8200—ports, VLANs, and Layer 3 interfaces J-EX8200—ports, VLANs, and Layer 3 interfaces dont-fragment (0x4000), more-fragments (0x2000), or reserved (0x8000) icmp-code number ICMP code field. This value or option provides more specific information than icmp-type. Because the value’s meaning depends upon the associated icmp-type, you must specify icmp-type along with icmp-code. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed). The options are grouped by the ICMP type with which they are associated: • parameter-problem—ip-header-bad (0), required-option-missing (1) • redirect—redirect-for-host (1), redirect-for-network (0), redirect-for-tos-and-host (3), redirect-for-tos-and-net (2) • time-exceeded—ttl-eq-zeroduring-reassembly (1), ttl-eq-zero-during-transit (0) • unreachable—communicationprohibited-by-filtering (13), destination-host-prohibited (10), destination-host-unknown (7), destination-network-prohibited (9), destination-network-unknown (6), fragmentation-needed (4), host-precedence-violation (14), host-unreachable (1), host-unreachable-for-TOS (12), network-unreachable (0), network-unreachable-for-TOS (11), port-unreachable (3), precedence-cutoff-in-effect (15), protocol-unreachable (2), source-host-isolated (8), source-route-failed (5) 2733 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress icmp-type number ICMP packet type field. Typically, you specify this match in conjunction with the protocol match statement to determine which protocol is being used on the port. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX4200—not supported • J-EX8200—Layer 3 interfaces • J-EX8200—not supported If the packet is a trailing fragment. This match condition does not match the first fragment of a fragmented packet. Use two terms to match both first and trailing fragments. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—ports, VLANs, and Layer 3 interfaces J-EX8200—not supported 8-bit protocol field that identifies the type of header immediately following the IPv6 header. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—not supported • J-EX8200—not supported echo-reply (0), echo-request (8), info-reply (16), info-request (15), mask-request (17), mask-reply (18), parameter-problem (12), redirect (5), router-advertisement (9), router-solicit (10), source-quench (4), time-exceeded (11), timestamp (13), timestamp-reply (14), unreachable (3) interface interface-name Interface on which the packet is received. You can specify the wildcard character (*) as part of an interface name. NOTE: An interface from which a packet is sent cannot be used as a match condition. ip-options is-fragment next-header bytes Presence of the options field in the IP header. ah (51), dstops (60), egp (8), esp (50), fragment (44), gre (47), hop-by-hop (0), icmp (1), icmpv6 (1), igmp (2), ipip (4), ipv6 (41), no-next-header (59), ospf (89), pim (103), routing (43), rsvp (46), sctp (132), tcp (6), udp (17), or vrrp (112). 2734 Chapter 100: Firewall Filters—Overview Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress precedence precedence IP precedence. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces IP source address field, which is the address of the source node sending the packet. For IPV6, the source-address field is 128 bits in length. The filter description syntax supports the text representations for IPv6 addresses that are described in RFC 2373, IP Version 6 Addressing Architecture. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces Source MAC address. • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs TCP or UDP source-port field. Typically, you specify this match in conjunction with the protocol match statement to determine which protocol is being used on the port. In place of the numeric field, you can specify one of the text synonyms listed under destination-port. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces IP source prefix list field. • • You can define a list of IP address prefixes under a prefix-list alias for frequent use. You make this definition at the [edit policy-options] hierarchy level. J-EX4200—ports, VLANs, and Layer 3 interfaces J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces critical-ecp (5), flash (3), flash-override (4), immediate (2), internet-control (6), net-control (7), priority (1), or routine (0). protocol list of protocols IPv4 protocol value. In place of the numeric value, you can specify one of the following text synonyms: egp (8), esp (50), gre (47), icmp (1), igmp (2), ipip (4), ospf (89), pim (103), rsvp (46), tcp (6), udp (17) source-address ip-address source-mac-address mac-address source-port number source-prefix-list prefix-list 2735 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress tcp-established TCP packets of an established TCP connection. This condition matches packets other than the first packet of a connection. tcp-established is a synonym for the bit names "(ack | rst)". • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—ports, VLANs, and Layer 3 interfaces J-EX8200—not supported • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—ports, VLANs, and Layer 3 interfaces J-EX8200—not supported • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—ports, VLANs, and Layer 3 interfaces J-EX8200—not supported tcp-established does not implicitly check whether the protocol is TCP. To do so, specify the protocol tcp match condition. tcp-flags [flags tcp-initial] One or more TCP flags: • bit-name—fin, syn, rst, push, ack, urgent • logical operators—& (logical AND), | (logical OR), ! (negation) • numerical value—0x01 through 0x20 • text synonym—tcp-initial To specify multiple flags, use logical operators. tcp-initial Match the first TCP packet of a connection. tcp-initial is a synonym for the bit names "(syn & !ack)". tcp-initial does not implicitly check whether the protocol is TCP. To do so, specify the protocol tcp match condition. 2736 Chapter 100: Firewall Filters—Overview Table 335: Supported Match Conditions Applicable to IPv4 Traffic for Firewall Filters on J-EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress traffic-class Differentiated Services code point (DSCP). The DiffServ protocol uses the type-of-service (ToS) byte in the IP header. The most significant six bits of this byte form the DSCP. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—not supported • J-EX8200—not supported • J-EX4200—Layer 3 interfaces • J-EX4200—not supported • J-EX8200—Layer 3 interfaces • J-EX8200—not supported • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs You can specify DSCP in hexadecimal, binary, or decimal form. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • ef (46)—as defined in RFC 2598, An Expedited Forwarding PHB. • af11 (10), af12 (12), af13 (14); af21 (18), af22 (20), af23 (22); af31 (26), af32 (28), af33 (30); af41 (34), af42 (36), af43 (38) These four classes, with three drop precedences in each class, for a total of 12 code points, are defined in RFC 2597, Assured Forwarding PHB. ttl value vlan [vlan-name | vlan-id] TTL type to match. The value can be 1–255. The VLAN that is associated with the packet. Some of the numeric range and bit-field match conditions allow you to specify a text synonym. For a list of all the synonyms for a match condition, do any of the following: • If you are using the J-Web Filters Configuration page, select the synonym from the appropriate list. • If you are using the CLI, type a question mark (?) after the from statement. To specify the bit-field value to match, you must enclose the values in quotation marks (" "). For example, a match occurs if the RST bit in the TCP flags field is set: tcp-flags "rst"; 2737 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS For information about logical operators and how to use bit-field logical operations to create expressions that are evaluated for matches, see “Understanding Firewall Filter Match Conditions” on page 2748. On J-EX Series Ethernet switches, you can apply a router firewall filter to both IPv4 and IPv6 traffic. You can apply firewall filter match conditions to IPv6 traffic on Layer 3 interfaces, aggregated Ethernet interfaces, and loopback interfaces. Table 336 on page 2738 describes the match conditions you can specify when configuring a firewall filter for IPv6 traffic. Table 336: Supported Match Conditions Applicable to IPv6 Traffic for Firewall Filters on EX Series Switches Supported Platforms and Bind Points Match Condition Description Ingress Egress destination-address ip-address Specifies the 128-bit address that is the final destination node address for the packet. The filter description syntax supports the text representations for IPv6 addresses as described in RFC 2373, IP Version6 Addressing Architecture. • J-EX4200— Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces Destination media access control (MAC) address of the packet. • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs destination-mac-address mac-address You can define a destination MAC address with a prefix, such as from destination-mac-address 00:01:02:03:04:05/24. If no prefix is specified, the default value 48 is used. 2738 Chapter 100: Firewall Filters—Overview Table 336: Supported Match Conditions Applicable to IPv6 Traffic for Firewall Filters on EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress destination-port number Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) destination port field. Typically, you specify this match in conjunction with the protocol match statement to determine which protocol is used on the port. In place of the numeric value, you can specify one of the following text synonyms (the port numbers are also listed): • J-EX4200— VLANs, and Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces afs (1483), bgp (179), biff (512), bootpc (68), bootps (67), cmd (514), cvspserver (2401), dhcp (67), domain (53), eklogin (2105), ekshell (2106), exec (512), finger (79), ftp (21), ftp-data (20), http (80), https (443), ident (113), imap (143), kerberos-sec (88), klogin (543), kpasswd (761), krb-prop (754), krbupdate (760), kshell (544), ldap (389), login (513), mobileip-agent (434), mobilip-mn (435), msdp (639), netbios-dgm (138), netbios-ns (137), netbios-ssn (139), nfsd (2049), nntp (119), ntalk (518), ntp (123), pop3 (110), pptp (1723), printer (515), radacct (1813),radius (1812), rip (520), rkinit (2108), smtp (25), snmp (161), snmptrap (162), snpp (444), socks (1080), ssh (22), sunrpc (111), syslog (514), 2739 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 336: Supported Match Conditions Applicable to IPv6 Traffic for Firewall Filters on EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—not supported • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200— ports and VLANs. tacacs-ds (65), talk (517), telnet (23), tftp (69), timed (525), who (513), xdmcp (177), zephyr-clt (2103), zephyr-hm (2104) destination-prefix-list prefix-list IP destination prefix list field. You can define a list of IP address prefixes under a prefix-list alias for frequent use. You make this definition at the [edit policy-options] hierarchy level. dot1q-tag number dot1q-user-priority number The tag field in the Ethernet header. The tag values can be 1–4095. User-priority field of the tagged Ethernet packet. User-priority values can be 0–7. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • background (1)—Background • best-effort (0)—Best effort • controlled-load (4)—Controlled load • excellent-load (3)—Excellent load • network-control (7)—Network control reserved traffic ether-type (ipv6)value • standard (2)—Standard or Spare • video (5)—Video • voice (6)—Voice Ethernet type field of a packet. The EtherType value specifies what protocol is being transported in the Ethernet frame. In place of the numeric value, you can specify the following text synonym: • 2740 ipv6—EtherType value IPv6 (0x08DD) Chapter 100: Firewall Filters—Overview Table 336: Supported Match Conditions Applicable to IPv6 Traffic for Firewall Filters on EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress icmp-code number ICMP code field. This value or option provides more specific information than icmp-type. Because the value’s meaning depends upon the associated icmp-type, you must specify icmp-type along with icmp-code. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed). The options are grouped by the ICMP type with which they are associated: • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • • J-EX8200—Layer 3 interfaces J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—Layer 3 interfaces icmp-type number • parameter-problem—ip-header-bad (0), unrecognized-next-header (1), unrecognized-option (2) • time-exceeded—ttl-eq-zeroduring-reassembly (1), ttl-eq-zero-during-transit (0) • destination-unreachable— no-route-to--destination (0), administratively-prohibited (1), address-unreachable (3), port-unreachable (4) ICMP packet type field. Typically, you specify this match in conjunction with the protocol match statement to determine which protocol is being used on the port. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): echo-reply (0), echo-request (8), info-reply (16), info-request (15), mask-request (17), mask-reply (18), parameter-problem (12), redirect (5), router-advertisement (9), router-solicit (10), source-quench (4), time-exceeded (11), timestamp (13), timestamp-reply (14), unreachable (3) interface interface-name Interface on which the packet is received. • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces • J-EX8200—ports, VLANs, and Layer 3 interfaces 2741 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 336: Supported Match Conditions Applicable to IPv6 Traffic for Firewall Filters on EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress next-header bytes 8-bit protocol field that identifies the type of header immediately following the IPv6 header. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces IP source address field, which is 128 bits in length. The filter description syntax supports the text representations for IPv6 addresses that are described in RFC 2373, IP Version 6 Addressing Architecture. • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces Source MAC address. • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs TCP or UDP source-port field. Typically, you specify this match in conjunction with the next-header match statement to determine which next-header is being used on the port. In place of the numeric field, you can specify one of the text synonyms listed under destination-port. • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces IP source prefix list field. • J-EX4200—Layer 3 interfaces • J-EX4200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces ah (51), dstops (60), egp (8), esp (50), fragment (44), gre (47), hop-by-hop (0), icmp (1), icmpv6 (1), igmp (2), ipip (4), ipv6 (41), no-next-header (59), ospf (89), pim (103), routing (43), rsvp (46), sctp (132), tcp (6), udp (17), or vrrp (112). packet-length bytes Length of the received packet, in bytes. The length refers only to the IP packet, including the packet header, and does not include any Layer 2 encapsulation overhead. source-address ip-address source-mac-address mac-address You can define a source MAC address with a prefix, such as from destination-mac-address 00:01:02:03:04:05/24. If no prefix is specified, the default value 48 is used. source-port number source-prefix-list prefix-list You can define a list of IP address prefixes under a prefix-list alias for frequent use. You make this definition at the [edit policy-options] hierarchy level. 2742 Chapter 100: Firewall Filters—Overview Table 336: Supported Match Conditions Applicable to IPv6 Traffic for Firewall Filters on EX Series Switches (continued) Supported Platforms and Bind Points Match Condition Description Ingress Egress tcp-flags (flags tcp-initial) One or more TCP flags: • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—Layer 3 interfaces J-EX8200—not supported • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—not supported • • J-EX8200—Layer 3 interfaces J-EX8200—not supported • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX4200—ports, VLANs, and Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX8200—Layer 3 interfaces • J-EX4200—ports and VLANs • J-EX4200—ports and VLANs • J-EX8200—ports and VLANs • J-EX8200—ports and VLANs • bit-name—fin, syn, rst, push, ack, urgent • logical operators—& (logical AND), | (logical OR), ! (negation) • numerical value—0x01 through 0x20 • text synonym—tcp-initial To specify multiple flags, use logical operators. tcp-initial Match the first TCP packet of a connection. tcp-initial is a synonym for the bit names "(syn & !ack)". tcp-initial does not implicitly check whether the protocol is TCP. To do so, specify the protocol tcp match condition. traffic-class number Differentiated Services code point (DSCP). The DiffServ protocol uses the type-of-service (ToS) byte in the IP header. The most significant six bits of this byte form the DSCP. You can specify DSCP in hexadecimal, binary, or decimal form. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed): • ef (46)—as defined in RFC 2598, An Expedited Forwarding PHB. • af11 (10), af12 (12), af13 (14); af21 (18), af22 (20), af23 (22); af31 (26), af32 (28), af33 (30); af41 (34), af42 (36), af43 (38) These four classes, with three drop precedences in each class, for a total of 12 code points, are defined in RFC 2597, Assured Forwarding PHB. vlan (vlan-id | vlan-name) The VLAN that is associated with the packet. 2743 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS When you define one or more terms that specify the filtering criteria, you also define the action to take if the packet matches all criteria. Table 337 on page 2744 shows the actions that you can specify in a term. Table 337: Actions for Firewall Filters Action Description Supported Platforms and Direction accept Accept a packet. • J-EX4200—ingress and egress • J-EX8200—ingress and egress Discard a packet silently without sending an Internet Control Message Protocol (ICMP) message. • J-EX4200—ingress and egress • J-EX8200—ingress and egress Discard a packet, and send an ICMPv4 message (type 3) “destination unreachable”. You can log the rejected packets if you configure the syslog action modifier. • J-EX4200—ingress only • J-EX8200—ingress only • J-EX4200—ingress and egress • J-EX8200—not supported • J-EX4200—ingress only • J-EX8200—not supported discard reject message-type You can specify one of the following message codes: administratively-prohibited (default), bad-host-tos, bad-network-tos, host-prohibited, host-unknown, host-unreachable, network-prohibited, network-unknown, network-unreachable, port-unreachable, precedence-cutoff, precedence-violation, protocol-unreachable, source-host-isolated, source-route-failed, or tcp-reset. If you specify tcp-reset, a TCP reset is returned if the packet is a TCP packet. Otherwise nothing is returned. If you do not specify a message type, the ICMP notification “destination unreachable” is sent with the default message “communication administratively filtered”. NOTE: reject is not a supported action for IPv6 traffic. routing-instance routing-instance-name Forward matched packets to a virtual routing instance. vlan vlan-name Forward matched packets to a specific VLAN. NOTE: vlan is not a supported action for IPv6 traffic. In addition to the actions, you can specify action modifiers. Table 338 on page 2744 shows the action modifiers that you can specify in a term. Table 338: Action Modifiers for Firewall Filters Action Modifier Description Supported Platforms and Direction analyzer analyzer-name Mirror port traffic to a specified destination port or VLAN that is connected to a protocol analyzer application. Mirroring copies all packets seen on one switch port to a network monitoring connection on another switch port. The analyzer name must be configured under [edit ethernet-switching-options analyzer]. • J-EX4200—ingress only • J-EX8200—ingress only 2744 Chapter 100: Firewall Filters—Overview Table 338: Action Modifiers for Firewall Filters (continued) Action Modifier Description Supported Platforms and Direction count counter-name Count the number of packets that pass this filter, term, or policer. • J-EX4200—ingress and egress • J-EX8200—not supported Classify the packet in one of the following forwarding classes: • J-EX4200—ingress and egress • J-EX8200—ingress and egress • J-EX4200—ingress only • J-EX8200—ingress only • J-EX4200—ingress only • J-EX8200—ingress only • J-EX4200—ingress only • J-EX8200—not supported • J-EX4200—ingress only • J-EX8200—ingress only • J-EX4200—ingress only • J-EX8200—ingress only forwarding-class class • assured-forwarding • best-effort • expedited-forwarding • network-control Forward the traffic to the specified interface bypassing the switching lookup. interface interface-name NOTE: interface is not a supported action modifier for IPv6 traffic. Log the packet's header information in the Routing Engine. To view this information, issue the show firewall log command in the CLI. log NOTE: log is not a supported action modifier for IPv6 traffic. Set the packet loss priority (PLP). loss-priority (high | low) Apply rate limits to the traffic. policer policer-name You can specify a policer for ingress port, VLAN, and router firewall filters only. Log an alert for this packet. You can specify that the log be sent to a server for storage and analysis. syslog NOTE: syslog is not a supported action modifier for IPv6 traffic. NOTE: On J-EX Series switches, accept and discard are the only actions supported for firewall filters applied on loopback interfaces. Related Documentation • Firewall Filter Configuration Statements Supported by Junos OS for J-EX Series Switches on page 2806 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 2745 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Understanding Firewall Filter Match Conditions on page 2748 • Understanding How Firewall Filters Are Evaluated on page 2746 • Understanding How Firewall Filters Test a Packet's Protocol on page 2752 • Understanding the Use of Policers in Firewall Filters on page 2752 • Understanding Filter-Based Forwarding for J-EX Series Switches on page 2753 Understanding How Firewall Filters Are Evaluated A firewall filter consists of one or more terms, and the order of the terms within a firewall filter is important. Before you configure firewall filters, you should understand how J-EX Series Switches evaluate the terms within a firewall filter and how packets are evaluated against the terms. When a firewall filter consists of a single term, the filter is evaluated as follows: • If the packet matches all the conditions, the action in the then statement is taken. • If the packet matches all the conditions, and no action is specified in the then statement, the default action accept is taken. When a firewall filter consists of more than one term, the firewall filter is evaluated sequentially: 1. The packet is evaluated against the conditions in the from statement in the first term. 2. If the packet matches all the conditions in the term, the action in the then statement is taken and the evaluation ends. Subsequent terms in the filter are not evaluated. 3. If the packet does not match all the conditions in the term, the packet is evaluated against the conditions in the from statement in the second term. This process continues until either the packet matches the conditions in the from statement in one of the subsequent terms or there are no more terms in the filter. 4. If a packet passes through all the terms in the filter without a match, the packet is discarded. Figure 77 on page 2747 shows how a J-EX Series switch evaluates the terms within a firewall filter. 2746 Chapter 100: Firewall Filters—Overview Figure 77: Evaluation of Terms Within a Firewall Filter If a term does not contain a from statement, the packet is considered to match and the action in the then statement of the term is taken. If a term does not contain a then statement, or if an action has not been configured in the then statement, and the packet matches the conditions in the from statement of the term, the packet is accepted. Every firewall filter contains an implicit deny statement at the end of the filter, which is equivalent to the following explicit filter term: term implicit-rule { then discard; } Consequently, if a packet passes through all the terms in a filter without matching any conditions, the packet is discarded. If you configure a firewall filter that has no terms, all packets that pass through the filter are discarded. NOTE: Firewall filtering is supported on packets that are at least 48 bytes long. Related Documentation • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding Firewall Filter Match Conditions on page 2748 • Understanding the Use of Policers in Firewall Filters on page 2752 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 2747 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Firewall Filter Match Conditions Before you define terms for firewall filters, you must understand how the conditions that you specify in a term are handled and how to specify interface filter, numeric filter, address filter, and bit-field filter match conditions to achieve the desired filtering results. • Filter Match Conditions on page 2748 • Numeric Filter Match Conditions on page 2748 • Interface Filter Match Conditions on page 2749 • IP Address Filter Match Conditions on page 2749 • MAC Address Filter Match Conditions on page 2750 • Bit-Field Filter Match Conditions on page 2750 Filter Match Conditions In the from statement of a firewall filter term, you specify the conditions that the packet must match for the action in the then statement to be taken. All conditions in the from statement must match for the action to be taken. The order in which you specify match conditions is not important, because a packet must match all the conditions in a term for a match to occur. If you specify no match conditions in a term, that term matches all packets. An individual condition in a from statement cannot contain a list of values. For example, you cannot specify numeric ranges or multiple source or destination addresses. Individual conditions in a from statement cannot be negated. A negated condition is an explicit mismatch. Numeric Filter Match Conditions Numeric filter conditions match packet fields that are identified by a numeric value, such as port and protocol numbers. For numeric filter match conditions, you specify a keyword that identifies the condition and a single value that a field in a packet must match. You can specify the numeric value in one of the following ways: • Single number—A match occurs if the value of the field matches the number. For example: source-port 25; • Text synonym for a single number— A match occurs if the value of the field matches the number that corresponds to the synonym. For example: source-port http; To specify more than one value in a filter term, you enter each value in its own match statement. For example, a match occurs in the following term if the value of vlan field is 10 or 30. [edit firewall family family-name filter filter-name term term-name from] 2748 Chapter 100: Firewall Filters—Overview vlan 10; vlan 30; The following restrictions apply to numeric filter match conditions: • You cannot specify a range of values. • You cannot specify a list of comma-separated values. • You cannot exclude a specific value in a numeric filter match condition. For example, you cannot specify a condition that would match only if the match condition was not equal to a given value. Interface Filter Match Conditions Interface filter match conditions can match interface name values in a packet. For interface filter match conditions, you specify the name of the interface, for example: [edit firewall family family-name filter filter-name term term-name from] user@host# set interface ge-0/0/1 Port and VLAN interfaces do not use logical unit numbers. However, a firewall filter that is applied to a router interface can specify the logical unit number in the interface filter match condition, for example: [edit firewall family family-name filter filter-name term term-name from] user@host# set interface ge-0/1/0.0 You can include the * wildcard as part of the interface name, for example: [edit firewall family family-name filter filter-name term term-name from] user@host# set interface ge-0/*/1 user@host# set interface ge-0/1/* user@host# set interface ge-* IP Address Filter Match Conditions Address filter match conditions can match prefix values in a packet, such as IP source and destination prefixes. For address filter match conditions, you specify a keyword that identifies the field and one prefix of that type that a packet must match. You specify the address as a single prefix. A match occurs if the value of the field matches the prefix. For example: [edit firewall family family-name filter filter-name term term-name from] user@host# set destination-address 10.2.1.0/28; Each prefix contains an implicit 0/0 except statement, which means that any prefix that does not match the prefix that is specified is explicitly considered not to match. To specify the address prefix, use the notation prefix/prefix-length. If you omit prefix-length, it defaults to /32. For example: [edit firewall family family-name filter filter-name term term-name from] user@host# set destination-address 10 [edit firewall family family-name filter filter-name term term-name from] user@host# show destination-address { 10.0.0.0/32; } 2749 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To specify more than one IP address in a filter term, you enter each address in its own match statement. For example, a match occurs in the following term if the value of the source-address field matches either of the following source-address prefixes: [edit firewall family family-name filter filter-name term term-name from] user@host# set source-address 10.0.0.0/8 user@host# set source-address 10.1.0.0/16 MAC Address Filter Match Conditions MAC address filter match conditions can match source and destination MAC address values in a packet. For MAC address filter match conditions, you specify a keyword that identifies the field and one value of that type that a packet must match. You can specify the MAC address as six hexadecimal bytes in the following formats: [edit firewall family family-name filter filter-name term term-name from] user@host# set destination-mac-address 0011.2233.4455 [edit firewall family family-name filter filter-name term term-name from] user@host# set destination-mac-address 00:11:22:33:44:55 [edit firewall family family-name filter filter-name term term-name from] user@host# set destination-mac-address 001122334455 To specify more than one MAC address in a filter term, you enter each MAC address in its own match statement. For example, a match occurs in the following term if the value of the source-mac-address field matches either of the following addresses. [edit firewall family family-name filter filter-name term term-name from] user@host# set source-mac-address 00:11:22:33:44:55 user@host# set source-mac-address 00:11:22:33:20:15 Bit-Field Filter Match Conditions Bit-field filter conditions match packet fields if particular bits in those fields are or are not set. You can match the IP options, TCP flags, and IP fragmentation fields. For bit-field filter match conditions, you specify a keyword that identifies the field and tests to determine that the option is present in the field. To specify the bit-field value to match, enclose the value in double quotation marks. For example, a match occurs if the RST bit in the TCP flags field is set: [edit firewall family family-name filter filter-name term term-name from] user@host# set tcp-flags "rst" Typically, you specify the bits to be tested by using keywords. Bit-field match keywords always map to a single bit value. You also can specify bit fields as hexadecimal or decimal numbers. To match multiple bit-field values, use the logical operators, which are described in Table 339 on page 2750. The operators are listed in order from highest precedence to lowest precedence. Operations are left-associative. Table 339: Actions for Firewall Filters Logical Operators Description ! Negation. 2750 Chapter 100: Firewall Filters—Overview Table 339: Actions for Firewall Filters (continued) Logical Operators Description & or + Logical AND. | or , Logical OR. To negate a match, precede the value with an exclamation point. For example, a match occurs only if the RST bit in the TCP flags field is not set: [edit firewall family family-name filter filter-name term term-name from] user@host# set tcp-flags "!rst" In the following example of a logical AND operation, a match occurs if the packet is the initial packet on a TCP session: [edit firewall family family-name filter filter-name term term-name from] user@host# set tcp-flags "syn&!ack" In the following example of a logical OR operation, a match occurs if the packet is not the initial packet on a TCP session: [edit firewall family family-name filter filter-name term term-name from] user@host# set tcp-flags "syn|ack" For a logical OR operation, you can specify a maximum of two match conditions in a single term. If you need to match more than two bit-field values in a logical OR operation, configure the same match condition in consecutive terms with additional bit-field values. In the following example, the two terms configured match the SYN, ACK, FIN, or RST bit in the TCP flags field: [edit firewall family family-name filter filter-name term term-name1 from] user@host# set tcp-flags "syn|ack" [edit firewall family family-name filter filter-name term term-name2 from] user@host# set tcp-flags "fin|rst" You can use text synonyms to specify some common bit-field matches. You specify these matches as a single keyword. In the following example of a text synonym, a match occurs if the packet is the initial packet on a TCP session: [edit firewall family family-name filter filter-name term term-name from] user@host# set tcp-flags tcp-initial Related Documentation • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding How Firewall Filters Test a Packet's Protocol on page 2752 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 2751 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding How Firewall Filters Test a Packet's Protocol When examining match conditions, the Junos OS for J-EX Series Switches tests only the field that is specified. The software does not implicitly test the IP header to determine whether a packet is an IP packet. Therefore, in some cases, you must specify protocol field match conditions in conjunction with other match conditions to ensure that the filters are performing the expected matches. If you specify a protocol match condition or a match of the ICMP type or TCP flags field, there is no implied protocol match. For the following match conditions, you must explicitly specify the protocol match condition in the same term: • destination-port—Specify the match protocol tcp or protocol udp. • source-port—Specify the match protocol tcp or protocol udp. If you do not specify the protocol when using the preceding fields, design your filters carefully to ensure that they perform the expected matches. For example, if you specify a match of destination-port ssh, the switch deterministically matches any packets that have a value of 22 in the two-byte field that is two bytes beyond the end of the IP header without ever checking the IP protocol field. Related Documentation • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding Firewall Filter Match Conditions on page 2748 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 Understanding the Use of Policers in Firewall Filters Policing, or rate limiting, is an important component of firewall filters that lets you control the amount of traffic that enters an interface. A single firewall filter configured with a policer permits only traffic at specified data rates to provide protection from denial-of-service (DOS) attacks. Traffic that exceeds the rate limits specified by the policer can be discarded. Discard is the only supported policer action. Typically, traffic that exceeds the rate limits specified by the policer is either discarded or marked as lower priority than traffic that meets the rate limits specified by the policer. When necessary, low-priority traffic can be discarded by the switch to prevent congestion. A policer applies two types of rate limits on traffic: • Bandwidth—The number of bits per second permitted, on average • Maximum burst size—The maximum size permitted for bursts of data that exceed the given bandwidth limit Policing uses an algorithm to enforce a limit on average bandwidth while allowing bursts up to a specified maximum value. You can define specific classes of traffic on an interface 2752 Chapter 100: Firewall Filters—Overview and apply a set of rate limits to each class. After you name and configure a policer, it is stored as a template. You can then use a policer in a firewall filter configuration. Each policer you configure includes an implicit counter that counts the number of packets exceeding the rate limits specified for the policer. To get filter or term-specific packets counts, you must configure a new policer for each filter or term that requires policing. Related Documentation • Firewall Filters for J-EX Series Switches Overview on page 2721 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 Understanding Filter-Based Forwarding for J-EX Series Switches Administrators of J-EX Series Switches can use firewall filters in conjunction with virtual routing instances to specify different routes for packets to travel in their networks. To set up this feature, which is called filter-based forwarding, you specify a filter and match criteria and then specify the virtual routing instance to send packets to. You might want to use filter-based forwarding to route specific types of traffic through a firewall or security device before the traffic continues on its path. You can also use filter-based forwarding to give certain types of traffic preferential treatment or to improve load balancing of switch traffic. Related Documentation • Understanding Virtual Routing Instances on J-EX Series Switches on page 1048 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 2753 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2754 CHAPTER 101 Examples of Firewall Filters Configuration • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches This example shows how to configure and apply firewall filters to control traffic that is entering or exiting a port on the switch, a VLAN on the network, and a Layer 3 interface on the switch. Firewall filters define the rules that determine whether to forward or deny packets at specific processing points in the packet flow. • Requirements on page 2755 • Overview on page 2756 • Configuring an Ingress Port Firewall Filter to Prioritize Voice Traffic and Rate-Limit TCP and ICMP Traffic on page 2759 • Configuring a VLAN Ingress Firewall Filter to Prevent Rogue Devices from Disrupting VoIP Traffic on page 2764 • Configuring a VLAN Firewall Filter to Count, Monitor, and Analyze Egress Traffic on the Employee VLAN on page 2766 • Configuring a VLAN Firewall Filter to Restrict Guest-to-Employee Traffic and Peer-to-Peer Applications on the Guest VLAN on page 2768 • Configuring a Router Firewall Filter to Give Priority to Egress Traffic Destined for the Corporate Subnet on page 2770 • Verification on page 2771 Requirements This example uses the following software and hardware components: • Two J-EX4200-48T switches: one to be used as an access switch, the other to be used as a distribution switch • One uplink module • One router 2755 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Before you configure and apply the firewall filters in this example, be sure you have: • An understanding of firewall filter concepts, policers, and CoS • Installed the uplink module in the distribution switch. See Installing an Uplink Module in a J-EX4200 Switch. Overview This configuration example show how to configure and apply firewall filters to provide rules to evaluate the contents of packets and determine when to discard, forward, classify, count, and analyze packets that are destined for or originating from the J-EX Series switches that handle all voice-vlan, employee-vlan, and guest-vlan traffic. Table 340 on page 2756 shows the firewall filters that are configured for the J-EX Series switches in this example. Table 340: Configuration Components: Firewall Filters Component Purpose/Description Port firewall filter, This firewall filter performs two functions: ingress-port-voip-class-limit-tcp-icmp • Assigns priority queueing to packets with a source MAC address that matches the phone MAC addresses. The forwarding class expedited-forwarding provides low loss, low delay, low jitter, assured bandwidth, and end-to-end service for all voice-vlan traffic. • Performs rate limiting on packets that enter the ports for employee-vlan. The traffic rate for TCP and ICMP packets is limited to 1 Mbps with a burst size up to 30,000 bytes. This firewall filter is applied to port interfaces on the access switch. VLAN firewall filter, ingress-vlan-rogue-block Prevents rogue devices from using HTTP sessions to mimic the gatekeeper device that manages call registration, admission, and call status for VoIP calls. Only TCP or UDP ports should be used; and only the gatekeeper uses HTTP. That is, all voice-vlan traffic on TCP ports should be destined for the gatekeeper device. This firewall filter applies to all phones on voice-vlan, including communication between any two phones on the VLAN and all communication between the gatekeeper device and VLAN phones. This firewall filter is applied to VLAN interfaces on the access switch. VLAN firewall filter, egress-vlan-watch-employee Accepts employee-vlan traffic destined for the corporate subnet, but does not monitor this traffic. Employee traffic destined for the Web is counted and analyzed. This firewall filter is applied to vlan interfaces on the access switch. VLAN firewall filter, ingress-vlan-limit-guest Prevents guests (non-employees) from talking with employees or employee hosts on employee-vlan. Also prevents guests from using peer-to-peer applications on guest-vlan, but allows guests to access the Web. This firewall filter is applied to VLAN interfaces on the access switch. Router firewall filter, egress-router-corp-class Prioritizes employee-vlan traffic, giving highest forwarding-class priority to employee traffic destined for the corporate subnet. This firewall filter is applied to a routed port (Layer 3 uplink module) on the distribution switch. 2756 Chapter 101: Examples of Firewall Filters Configuration Figure 78 on page 2757 shows the application of port, VLAN, and Layer 3 routed firewall filters on the switch. Figure 78: Application of Port, VLAN, and Layer 3 Routed Firewall Filters Network Topology The topology for this configuration example consists of one J-EX4200-48T switch at the access layer, and one J-EX4200-48T switch at the distribution layer. The distribution switch's uplink module is configured to support a Layer 3 connection to a J-series router. The J-EX Series switches are configured to support VLAN membership. Table 341 on page 2757 shows the VLAN configuration components for the VLANs. Table 341: Configuration Components: VLANs VLAN Name VLAN ID voice-vlan 10 VLAN Subnet and Available IP Addresses VLAN Description 192.0.2.0/28 192.0.2.1 through 192.0.2.14 Voice VLAN used for employee VoIP traffic 192.0.2.15 is subnet’s broadcast address 2757 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 341: Configuration Components: VLANs (continued) VLAN Name VLAN ID employee-vlan 20 VLAN Subnet and Available IP Addresses 192.0.2.16/28 192.0.2.17 through 192.0.2.30 192.0.2.31 is subnet’s broadcast address guest-vlan 30 192.0.2.32/28 192.0.2.33 through 192.0.2.46 192.0.2.47 is subnet’s broadcast address camera-vlan 40 192.0.2.48/28 192.0.2.49 through 192.0.2.62 192.0.2.63 VLAN Description VLAN standalone PCs, PCs connected to the network through the hub in VoIP telephones, wireless access points, and printers. This VLAN completely includes the voice VLAN. Two VLANs (voice-vlan and employee-vlan) must be configured on the ports that connect to the telephones. VLAN for guests’ data devices (PCs). The scenario assumes that the corporation has an area open to visitors, either in the lobby or in a conference room, that has a hub to which visitors can plug in their PCs to connect to the Web and to their company’s VPN. VLAN for the corporate security cameras. is subnet’s broadcast address Ports on the J-EX Series switches support Power over Ethernet (PoE) to provide both network connectivity and power for VoIP telephones connecting to the ports. Table 342 on page 2758 shows the switch ports that are assigned to the VLANs and the IP and MAC addresses for devices connected to the switch ports: Table 342: Configuration Components: Switch Ports on a 48-Port All-PoE Switch Switch and Port Number VLAN Membership IP and MAC Addresses Port Devices ge-0/0/0, ge-0/0/1 voice-vlan, employee-vlan IP addresses: 192.0.2.1 through Two VoIP telephones, each connected to one PC. 192.0.2.2 MAC addresses: 00.05.85.00.00.01, 00.05.85.00–00.02 ge-0/0/2, ge-0/0/3 employee-vlan 192.0.2.17 through 192.0.2.18 Printer, wireless access points ge-0/0/4, ge-0/0/5 guest-vlan 192.0.2.34 through 192.0.2.35 Two hubs into which visitors can plug in their PCs. Hubs are located in an area open to visitors, such as a lobby or conference room ge-0/0/6, ge-0/0/7 camera-vlan 192.0.2.49 through 192.0.2.50 Two security cameras 2758 Chapter 101: Examples of Firewall Filters Configuration Table 342: Configuration Components: Switch Ports on a 48-Port All-PoE Switch (continued) Switch and Port Number VLAN Membership IP and MAC Addresses Port Devices ge-0/0/9 voice-vlan IP address: 192.0.2.14 Gatekeeper device. The gatekeeper manages call registration, admission, and call status for VoIP phones. MAC address:00.05.85.00.00.0E ge-0/1/0 IP address: 192.0.2.65 Layer 3 connection to a router; note that this is a port on the switch’s uplink module Configuring an Ingress Port Firewall Filter to Prioritize Voice Traffic and Rate-Limit TCP and ICMP Traffic To configure and apply firewall filters for port, VLAN, and router interfaces, perform these tasks: CLI Quick Configuration To quickly configure and apply a port firewall filter to prioritize voice traffic and rate-limit packets that are destined for the employee-vlan subnet, copy the following commands and paste them into the switch terminal window: [edit] set firewall policer tcp-connection-policer if-exceeding burst-size-limit 30k bandwidth-limit 1m set firewall policer tcp-connection-policer then discard set firewall policer icmp-connection-policer if-exceeding burst-size-limit 30k bandwidth-limit 1m set firewall policer icmp-connection-policer then discard set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term voip-high from source-mac-address 00.05.85.00.00.01 set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term voip-high from source-mac-address 00.05.85.00.00.02 set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term voip-high from protocol udp set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term voip-high then forwarding-class expedited-forwarding set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term voip-high then loss-priority low set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term network-control from precedence net-control set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term network-control then forwarding-class network-control set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term network-control then loss-priority low set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term tcp-connection from destination-address 192.0.2.16/28 set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term tcp-connection from protocol tcp set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term tcp-connection then policer tcp-connection-policer set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term tcp-connection then count tcp-counter set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term tcp-connection then forwarding-class best-effort set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term tcp-connection then loss-priority high 2759 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term icmp-connection from destination-address 192.0.2.16/28 set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term icmp-connection from protocol icmp set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term icmp-connection then policer icmp-connection-policer set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term icmp-connection then count icmp-counter set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term icmp-connection then forwarding-class best-effort set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term icmp-connection then loss-priority high set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term best-effort then forwarding-class best-effort set firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp term best-effort then loss-priority high set interfaces ge-0/0/0 description "voice priority and tcp and icmp traffic rate-limiting filter at ingress port" set interfaces ge-0/0/0 unit 0 family ethernet-switching filter input ingress-port-voip-class-limit-tcp-icmp set interfaces ge-0/0/1 description "voice priority and tcp and icmp traffic rate-limiting filter at ingress port" set interfaces ge-0/0/1 unit 0 family ethernet-switching filter input ingress-port-voip-class-limit-tcp-icmp set class-of-service schedulers voice-high buffer-size percent 15 set class-of-service schedulers voice-high priority high set class-of-service schedulers net-control buffer-size percent 10 set class-of-service schedulers net-control priority high set class-of-service schedulers best-effort buffer-size percent 75 set class-of-service schedulers best-effort priority low set class-of-service scheduler-maps ethernet-diffsrv-cos-map forwarding-class expedited-forwarding scheduler voice-high set class-of-service scheduler-maps ethernet-diffsrv-cos-map forwarding-class network-control scheduler net-control set class-of-service scheduler-maps ethernet-diffsrv-cos-map forwarding-class best-effort scheduler best-effort Step-by-Step Procedure To configure and apply a port firewall filter to prioritize voice traffic and rate-limit packets that are destined for the employee-vlan subnet: 1. Define the policers tcp-connection-policer and icmp-connection-policer: [edit] user@switch# set firewall policer tcp-connection-policer if-exceeding burst-size-limit 30k bandwidth-limit 1m user@switch# set firewall policer tcp-connection-policer then discard user@switch# set firewall policer icmp-connection-policer if-exceeding burst-size-limit 30k bandwidth-limit 1m user@switch# set firewall policer icmp-connection-policer then discard 2. Define the firewall filter ingress-port-voip-class-limit-tcp-icmp: [edit firewall] user@switch# set family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp 3. Define the term voip-high: [edit firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp ] user@switch# set term voip-high from source-mac-address 00.05.85.00.00.01 user@switch# set term voip-high from source-mac-address 00.05.85.00.00.02 2760 Chapter 101: Examples of Firewall Filters Configuration user@switch# set term voip-high from protocol udp user@switch# set term voip-high then forwarding-class expedited-forwarding user@switch# set term voip-high then loss-priority low 4. Define the term network-control: [edit firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp ] user@switch# set term network-control from precedence net-control user@switch# set term network-control then forwarding-class network-control user@switch# set term network-control then loss-priority low 5. Define the term tcp-connection to configure rate limits for TCP traffic: [edit firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp] user@switch# set term tcp-connection from destination-address 192.0.2.16/28 user@switch# set term tcp-connection from protocol tcp user@switch# set term tcp-connection then policer tcp-connection-policer user@switch# set term tcp-connection then count tcp-counter user@switch# set term tcp-connection then forwarding-class best-effort user@switch# set term tcp-connection then loss-priority high 6. Define the term icmp-connection to configure rate limits for ICMP traffic: [edit firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp] user@switch# set term icmp-connection from destination-address 192.0.2.16/28 user@switch# set term icmp-connection from protocol icmp user@switch# set term icmp-connection then policer icmp-policer user@switch# set term icmp-connection then count icmp-counter user@switch# set term icmp-connection then forwarding-class best-effort user@switch# set term icmp-connection then loss-priority high 7. Define the term best-effort with no match conditions for an implicit match on all packets that did not match any other term in the firewall filter: [edit firewall family ethernet-switching filter ingress-port-voip-class-limit-tcp-icmp] user@switch# set term best-effort then forwarding-class best-effort user@switch# set term best-effort then loss-priority high 8. Apply the firewall filter ingress-port-voip-class-limit-tcp-icmp as an input filter to the port interfaces for employee-vlan : [edit interfaces] user@switch# set ge-0/0/0 description "voice priority and tcp and icmp traffic rate-limiting filter at ingress port" user@switch# set ge-0/0/0 unit 0 family ethernet-switching filter input ingress-port-voip-class-limit-tcp-icmp user@switch# set ge-0/0/1 description "voice priority and tcp and icmp traffic rate-limiting filter at ingress port" user@switch# set ge-0/0/1 unit 0 family ethernet-switching filter input ingress-port-voip-class-limit-tcp-icmp 9. Configure the parameters that are desired for the different schedulers. NOTE: When you configure parameters for the schedulers, define the numbers to match your network traffic patterns. 2761 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit class-of-service] user@switch# set schedulers voice-high buffer-size percent 15 user@switch# set schedulers voice-high priority high user@switch# set schedulers network—control buffer-size percent 10 user@switch# set schedulers network—control priority high user@switch# set schedulers best-effort buffer-size percent 75 user@switch# set schedulers best-effort priority low 10. Assign the forwarding classes to schedulers with a scheduler map: [edit class-of-service] user@switch# set scheduler-maps ethernet-diffsrv-cos-map user@switch# set scheduler-maps ethernet-diffsrv-cos-map forwarding-class expedited-forwarding scheduler voice-high user@switch# set scheduler-maps ethernet-diffsrv-cos-map forwarding-class network-control scheduler net-control user@switch# set scheduler-maps ethernet-diffsrv-cos-map forwarding-class best-effort scheduler best-effort 11. Associate the scheduler map with the outgoing interface: [edit class-of-service] user@switch# set interfaces ge–0/1/0 scheduler-map ethernet-diffsrv-cos-map Results Display the results of the configuration: user@switch# show firewall { policer tcp-connection-policer { if-exceeding { bandwidth-limit 1m; burst-size-limit 30k; } then { discard; } } policer icmp-connection-policer { if-exceeding { bandwidth-limit 1m; burst-size-limit 30k; } then { discard; } } family ethernet-switching { filter ingress-port-voip-class-limit-tcp-icmp { term voip-high { from { destination-mac-address 00.05.85.00.00.01; destination-mac-address 00.05.85.00.00.02; protocol udp; } then { forwarding-class expedited-forwarding; loss-priority low; 2762 Chapter 101: Examples of Firewall Filters Configuration } } term network-control { from { precedence net-control ; } then { forwarding-class network-control; loss-priority low; } } term tcp-connection { from { destination-address 192.0.2.16/28; protocol tcp; } then { policer tcp-connection-policer; count tcp-counter; forwarding-class best-effort; loss-priority high; } } term icmp-connection from { protocol icmp; } then { policer icmp-connection-policer; count icmp-counter; forwarding-class best-effort; loss-priority high; } } term best-effort { then { forwarding-class best-effort; loss-priority high; } } } } } interfaces { ge-0/0/0 { description "voice priority and tcp and icmp traffic rate-limiting filter at ingress port"; unit 0 { family ethernet-switching { filter { input ingress-port-voip-class-limit-tcp-icmp; } } } } ge-0/0/1 { description "voice priority and tcp and icmp traffic rate-limiting filter at ingress port"; 2763 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit 0 { family ethernet-switching { filter { input ingress-port-voip-class-limit-tcp-icmp; } } } } } scheduler-maps { ethernet-diffsrv-cos-map { forwarding-class expedited-forwarding scheduler voice-high; forwarding-class network-control scheduler net-control; forwarding-class best-effort scheduler best-effort; } } interfaces { ge/0/1/0 { scheduler-map ethernet-diffsrv-cos-map; } } Configuring a VLAN Ingress Firewall Filter to Prevent Rogue Devices from Disrupting VoIP Traffic To configure and apply firewall filters for port, VLAN, and router interfaces, perform these tasks: CLI Quick Configuration To quickly configure a VLAN firewall filter on voice-vlan to prevent rogue devices from using HTTP sessions to mimic the gatekeeper device that manages VoIP traffic, copy the following commands and paste them into the switch terminal window: [edit] set firewall family ethernet-switching filter ingress-vlan-rogue-block term to-gatekeeper from destination-address 192.0.2.14 set firewall family ethernet-switching filter ingress-vlan-rogue-block term to-gatekeeper from destination-port 80 set firewall family ethernet-switching filter ingress-vlan-rogue-block term to-gatekeeper then accept set firewall family ethernet-switching filter ingress-vlan-rogue-block term from-gatekeeper from source-address 192.0.2.14 set firewall family ethernet-switching filter ingress-vlan-rogue-block term from-gatekeeper from source-port 80 set firewall family ethernet-switching filter ingress-vlan-rogue-block term from-gatekeeper then accept set firewall family ethernet-switching filter ingress-vlan-rogue-block term not-gatekeeper from destination-port 80 set firewall family ethernet-switching filter ingress-vlan-rogue-block term not-gatekeeper then count rogue-counter set firewall family ethernet-switching filter ingress-vlan-rogue-block term not-gatekeeper then discard set vlans voice-vlan description "block rogue devices on voice-vlan" set vlans voice-vlan filter input ingress-vlan-rogue-block 2764 Chapter 101: Examples of Firewall Filters Configuration Step-by-Step Procedure To configure and apply a VLAN firewall filter on voice-vlan to prevent rogue devices from using HTTP to mimic the gatekeeper device that manages VoIP traffic: 1. Define the firewall filter ingress-vlan-rogue-block to specify filter matching on the traffic you want to permit and restrict: [edit firewall] user@switch# set family ethernet-switching filter ingress-vlan-rogue-block 2. Define the term to-gatekeeper to accept packets that match the destination IP address of the gatekeeper: [edit firewall family ethernet-switching filter ingress-vlan-rogue-block] user@switch# set term to-gatekeeper from destination-address 192.0.2.14 user@switch# set term to-gatekeeper from destination-port 80 user@switch# set term to-gatekeeper then accept 3. Define the term from-gatekeeper to accept packets that match the source IP address of the gatekeeper: [edit firewall family ethernet-switching filter ingress-vlan-rogue-block] user@switch# set term from-gatekeeper from source-address 192.0.2.14 user@switch# set term from-gatekeeper from source-port 80 user@switch# set term from-gatekeeper then accept 4. Define the term not-gatekeeper to ensure all voice-vlan traffic on TCP ports is destined for the gatekeeper device: [edit firewall family ethernet-switching filter ingress-vlan-rogue-block] user@switch# set term not-gatekeeper from destination-port 80 user@switch# set term not-gatekeeper then count rogue-counter user@switch# set term not-gatekeeper then discard 5. Apply the firewall filter ingress-vlan-rogue-block as an input filter to the VLAN interface for the VoIP telephones: [edit] user@switch# set vlans voice-vlan description "block rogue devices on voice-vlan" user@switch# set vlans voice-vlan filter input ingress-vlan-rogue-block Results Display the results of the configuration: user@switch# show firewall { family ethernet-switching { filter ingress-vlan-rogue-block { term to-gatekeeper { from { destination-address 192.0.2.14/32 destination-port 80; } then { accept; } } term from-gatekeeper { from { source-address 192.0.2.14/32 2765 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS source-port 80; } then { accept; } } term not-gatekeeper { from { destination-port 80; } then { count rogue-counter; discard; } } } vlans { voice-vlan { description "block rogue devices on voice-vlan"; filter { input ingress-vlan-rogue-block; } } } Configuring a VLAN Firewall Filter to Count, Monitor, and Analyze Egress Traffic on the Employee VLAN To configure and apply firewall filters for port, VLAN, and router interfaces, perform these tasks: CLI Quick Configuration A firewall filter is configured and applied to VLAN interfaces to filter employee-vlan egress traffic. Employee traffic destined for the corporate subnet is accepted but not monitored. Employee traffic destined for the Web is counted and analyzed. To quickly configure and apply a VLAN firewall filter, copy the following commands and paste them into the switch terminal window: [edit] set firewall family ethernet-switching filter egress-vlan-watch-employee term employee-to-corp from destination-address 192.0.2.16/28 set firewall family ethernet-switching filter egress-vlan-watch-employee term employee-to-corp then accept set firewall family ethernet-switching filter egress-vlan-watch-employee term employee-to-web from destination-port 80 set firewall family ethernet-switching filter egress-vlan-watch-employee term employee-to-web then count employee-web-counter set firewall family ethernet-switching filter egress-vlan-watch-employee term employee-to-web then analyzer employee-monitor set vlans employee-vlan description "filter at egress VLAN to count and analyze employee to Web traffic" set vlans employee-vlan filter output egress-vlan-watch-employee 2766 Chapter 101: Examples of Firewall Filters Configuration Step-by-Step Procedure To configure and apply an egress port firewall filter to count and analyze employee-vlan traffic that is destined for the Web: 1. Define the firewall filter egress-vlan-watch-employee: [edit firewall] user@switch# set family ethernet-switching filter egress-vlan-watch-employee 2. Define the term employee-to-corp to accept but not monitor all employee-vlan traffic destined for the corporate subnet: [edit firewall family ethernet-switching filter egress-vlan-watch-employee] user@switch# set term employee-to-corp from destination-address 192.0.2.16/28 user@switch# set term employee-to-corp then accept 3. Define the term employee-to-web to count and monitor all employee-vlan traffic destined for the Web: [edit firewall family ethernet-switching filter egress-vlan-watch-employee] user@switch# set term employee-to-web from destination-port 80 user@switch# set term employee-to-web then count employee-web-counter user@switch# set term employee-to-web then analyzer employee-monitor NOTE: See “Example: Configuring Port Mirroring for Local Monitoring of Employee Resource Use on J-EX Series Switches” on page 3249 for information about configuring the employee-monitor analyzer. 4. Apply the firewall filter egress-vlan-watch-employee as an output filter to the port interfaces for the VoIP telephones: [edit] user@switch# set vlans employee-vlan description "filter at egress VLAN to count and analyze employee to Web traffic" user@switch# set vlans employee-vlan filter output egress-vlan-watch-employee Results Display the results of the configuration: user@switch# show firewall { family ethernet-switching { filter egress-vlan-watch-employee { term employee-to-corp { from { destination-address 192.0.2.16/28 } then { accept; } } term employee-to-web { from { destination-port 80; } then { count employee-web-counter: 2767 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS analyzer employee-monitor; } } } } } vlans { employee-vlan { description "filter at egress VLAN to count and analyze employee to Web traffic"; filter { output egress-vlan-watch-employee; } } } Configuring a VLAN Firewall Filter to Restrict Guest-to-Employee Traffic and Peer-to-Peer Applications on the Guest VLAN To configure and apply firewall filters for port, VLAN, and router interfaces, perform these tasks: CLI Quick Configuration In the following example, the first filter term permits guests to talk with other guests but not employees on employee-vlan. The second filter term allows guests Web access but prevents them from using peer-to-peer applications on guest-vlan. To quickly configure a VLAN firewall filter to restrict guest-to-employee traffic, blocking guests from talking with employees or employee hosts on employee-vlan or attempting to use peer-to-peer applications on guest-vlan, copy the following commands and paste them into the switch terminal window: [edit] set firewall family ethernet-switching filter ingress-vlan-limit-guest term guest-to-guest from destination-address 192.0.2.33/28 set firewall family ethernet-switching filter ingress-vlan-limit-guest term guest-to-guest then accept set firewall family ethernet-switching filter ingress-vlan-limit-guest term no-guest-employee-no-peer-to-peer from destination-mac-address 00.05.85.00.00.DF set firewall family ethernet-switching filter ingress-vlan-limit-guest term no-guest-employee-no-peer-to-peer then accept set vlans guest-vlan description "restrict guest-to-employee traffic and peer-to-peer applications on guest VLAN" set vlans guest-vlan filter input ingress-vlan-limit-guest Step-by-Step Procedure To configure and apply a VLAN firewall filter to restrict guest-to-employee traffic and peer-to-peer applications on guest-vlan: 1. Define the firewall filter ingress-vlan-limit-guest: [edit firewall] set firewall family ethernet-switching filter ingress-vlan-limit-guest 2. Define the term guest-to-guest to permit guests on the guest-vlan to talk with other guests but not employees on the employee-vlan: [edit firewall family ethernet-switching filter ingress-vlan-limit-guest] user@switch# set term guest-to-guest from destination-address 192.0.2.33/28 user@switch# set term guest-to-guest then accept 2768 Chapter 101: Examples of Firewall Filters Configuration 3. Define the term no-guest-employee-no-peer-to-peer to allow guests on guest-vlan Web access but prevent them from using peer-to-peer applications on the guest-vlan. NOTE: The destination-mac-address is the default gateway, which for any host in a VLAN is the next-hop router. [edit firewall family ethernet-switching filter ingress-vlan-limit-guest] user@switch# set term no-guest-employee-no-peer-to-peer from destination-mac-address 00.05.85.00.00.DF user@switch# set term no-guest-employee-no-peer-to-peer then accept 4. Apply the firewall filter ingress-vlan-limit-guest as an input filter to the interface for guest-vlan : [edit] user@switch# set vlans guest-vlan description "restrict guest-to-employee traffic and peer-to-peer applications on guest VLAN" user@switch# set vlans guest-vlan filter input ingress-vlan-limit-guest Results Display the results of the configuration: user@switch# show firewall { family ethernet-switching { filter ingress-vlan-limit-guest { term guest-to-guest { from { destination-address 192.0.2.33/28; } then { accept; } } term no-guest-employee-no-peer-to-peer { from { destination-mac-address 00.05.85.00.00.DF; } then { accept; } } } } } vlans { guest-vlan { description "restrict guest-to-employee traffic and peer-to-peer applications on guest VLAN"; filter { input ingress-vlan-limit-guest; } } } 2769 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring a Router Firewall Filter to Give Priority to Egress Traffic Destined for the Corporate Subnet To configure and apply firewall filters for port, VLAN, and router interfaces, perform these tasks: CLI Quick Configuration To quickly configure a firewall filter for a routed port (Layer 3 uplink module) to filter employee-vlan traffic, giving highest forwarding-class priority to traffic destined for the corporate subnet, copy the following commands and paste them into the switch terminal window: [edit] set firewall family inet filter egress-router-corp-class term corp-expedite from destination-address 192.0.2.16/28 set firewall family inet filter egress-router-corp-class term corp-expedite then forwarding-class expedited-forwarding set firewall family inet filter egress-router-corp-class term corp-expedite then loss-priority low set firewall family inet filter egress-router-corp-class term not-to-corp then accept set interfaces ge-0/1/0 description "filter at egress router to expedite destined for corporate network" set ge-0/1/0 unit 0 family inet address 103.104.105.1 set interfaces ge-0/1/0 unit 0 family inet filter output egress-router-corp-class Step-by-Step Procedure To configure and apply a firewall filter to a routed port (Layer 3 uplink module) to give highest priority to employee-vlan traffic destined for the corporate subnet: 1. Define the firewall filter egress-router-corp-class: [edit] user@switch# set firewall family inet filter egress-router-corp-class 2. Define the term corp-expedite: [edit firewall] user@switch# set family inet filter egress-router-corp-class term corp-expedite from destination-address 192.0.2.16/28 user@switch# set family inet filter egress-router-corp-class term corp-expedite then forwarding-class expedited-forwarding user@switch# set family inet filter egress-router-corp-class term corp-expedite then loss-priority low 3. Define the term not-to-corp: [edit firewall] user@switch# set family inet filter egress-router-corp-class term not-to-corp then accept 4. Apply the firewall filter egress-router-corp-class as an output filter for the port on the switch's uplink module, which provides a Layer 3 connection to a router: [edit interfaces] user@switch# set ge-0/1/0 description "filter at egress router to expedite employee traffic destined for corporate network" user@switch# set ge-0/1/0 unit 0 family inet address 103.104.105.1 user@switch# set ge-0/1/0 unit 0 family inet filter output egress-router-corp-class Results Display the results of the configuration: user@switch# show 2770 Chapter 101: Examples of Firewall Filters Configuration firewall { family inet { filter egress-router-corp-class { term corp-expedite { from { destination-address 192.0.2.16/28; } then { forwarding-class expedited-forwarding; loss-priority low; } } term not-to-corp { then { accept; } } } } } interfaces { ge-0/1/0 { unit 0 { description "filter at egress router interface to expedite employee traffic destined for corporate network"; family inet { source-address 103.104.105.1 filter { output egress-router-corp-class; } } } } } Verification To confirm that the firewall filters are working properly, perform the following tasks: • Verifying that Firewall Filters and Policers are Operational on page 2771 • Verifying that Schedulers and Scheduler-Maps are Operational on page 2772 Verifying that Firewall Filters and Policers are Operational Purpose Action Verify the operational state of the firewall filters and policers that are configured on the switch. Use the operational mode command: user@switch> show firewall Filter: ingress-port-voip-class-limit-tcp-icmp Counters: Name icmp-counter tcp-counter Policers: Packets 0 0 2771 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Name icmp-connection-policer tcp-connection-policer Packets 0 0 Filter: ingress-vlan-rogue-block Filter: egress-vlan-watch-employee Counters: Name employee-web—counter Meaning Packets 0 The show firewall command displays the names of the firewall filters, policers, and counters that are configured on the switch. The output fields show byte and packet counts for all configured counters and the packet count for all policers. Verifying that Schedulers and Scheduler-Maps are Operational Purpose Action Verify that schedulers and scheduler-maps are operational on the switch. Use the operational mode command: user@switch> show class-of-service scheduler-map Scheduler map: default, Index: 2 Scheduler: default-be, Forwarding class: Transmit rate: 95 percent, Rate Limit: Priority: low Drop profiles: Loss priority Protocol Index Low non-TCP 1 Low TCP 1 High non-TCP 1 High TCP 1 best-effort, Index: 20 none, Buffer size: 95 percent, Name default-drop-profile default-drop-profile default-drop-profile default-drop-profile Scheduler: default-nc, Forwarding class: network-control, Index: 22 Transmit rate: 5 percent, Rate Limit: none, Buffer size: 5 percent, Priority: low Drop profiles: Loss priority Protocol Index Name Low non-TCP 1 default-drop-profile Low TCP 1 default-drop-profile High non-TCP 1 default-drop-profile High TCP 1 default-drop-profileScheduler map: ethernet-diffsrv-cos-map, Index: 21657 Scheduler: best-effort, Forwarding class: best-effort, Index: 61257 Transmit rate: remainder, Rate Limit: none, Buffer size: 75 percent, Priority: low Drop profiles: Loss priority Protocol Index Name Low non-TCP 1 Low TCP 1 High non-TCP 1 High TCP 1 Scheduler: voice-high, Forwarding class: expedited-forwarding, Index: 3123 Transmit rate: remainder, Rate Limit: none, Buffer size: 15 percent, Priority: high 2772 Chapter 101: Examples of Firewall Filters Configuration Drop profiles: Loss priority Low Low High High Protocol non-TCP TCP non-TCP TCP Index 1 1 1 1 Name Scheduler: net-control, Forwarding class: network-control, Index: 2451 Transmit rate: remainder, Rate Limit: none, Buffer size: 10 percent, Priority: high Drop profiles: Loss priority Protocol Index Name Low non-TCP 1 Low TCP 1 High non-TCP 1 High TCP 1 Meaning Related Documentation Displays statistics about the configured schedulers and schedulers-maps. • Example: Configuring Port Mirroring for Remote Monitoring of Employee Resource Use on J-EX Series Switches on page 3254 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • [edit firewall] Configuration Statement Hierarchy on page 42 Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches Administrators can configure filter-based forwarding on a J-EX Series switch by using a firewall filter to forward matched traffic to a specific virtual routing instance. This example describes how to set up filter-based forwarding: • Requirements on page 2773 • Overview and Topology on page 2774 • Configuration on page 2774 • Verification on page 2776 Requirements This example uses the following software and hardware components: 2773 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • One J-EX Series switch Overview and Topology In this example, traffic from one application server that is destined for a different application server is matched by a firewall filter based on the IP address. Any matching packets are routed to a particular virtual routing instance that first sends all traffic to a security device, then forwards it to the designated destination address. Configuration To configure filter-based forwarding: CLI Quick Configuration To quickly create and configure filter-based forwarding, copy the following commands and paste them into the switch terminal window: [edit] set interfaces ge-0/0/0 unit 0 family inet address 10.1.0.1/24 set interfaces ge-0/0/3 unit 0 family inet address 10.1.3.1/24 set firewall family inet filter fil term t1 from source-address 1.1.1.1/32 set firewall family inet filter fil term t1 from protocol tcp set interfaces ge-0/0/0 unit 0 family inet filter input fil set routing-instances vrf01 instance-type virtual-router set routing-instances vrf01 interface ge-0/0/1.0 set routing-instances vrf01 interface ge-0/0/3.0 set routing-instances vrf01 routing-options static route 12.34.56.0/24 next-hop 10.1.3.254 set firewall family inet filter fil term t1 then routing-instance vrf01 Step-by-Step Procedure To configure filter-based forwarding: 1. Create interfaces to the application servers: [edit] user@switch# set interfaces ge-0/0/0 unit 0 family inet address 10.1.0.1/24 user@switch# set interfaces ge-0/0/3 unit 0 family inet address 10.1.3.1/24 2. Create a firewall filter that matches the correct source address: [edit] user@switch# set firewall family inet filter fil term t1 from source-address 1.1.1.1/32 user@switch# set firewall family inet filter fil term t1 from protocol tcp 3. Associate the filter with the source application server’s interface: [edit] user@switch# set interfaces ge-0/0/0 unit 0 family inet filter input fil 4. Create a virtual router: [edit] user@switch# set routing-instances vrf01 instance-type virtual-router 5. Associate the interfaces with the virtual router: [edit] user@switch# set routing-instances vrf01 interface ge-0/0/1.0 user@switch# set routing-instances vrf01 interface ge-0/0/3.0 6. Configure the routing information for the virtual routing instance: [edit] 2774 Chapter 101: Examples of Firewall Filters Configuration user@switch# set routing-instances vrf01 routing-options static route 12.34.56.0/24 next-hop 10.1.3.254 7. Set the filter to forward packets to the virtual router you created: [edit] user@switch# set firewall family inet filter fil term t1 then routing-instance vrf01 Results Check the results of the configuration: user@switch> show configuration interfaces { ge-0/0/0 { unit 0 { family inet { filter { input fil; } address 10.1.0.1/24; } } } ge-0/0/3 { unit 0 { family inet { address 10.1.3.1/24; } } } } firewall { family inet { filter fil { term t1 { from { source-address { 1.1.1.1/32; } protocol tcp; } then { routing-instance vrf01; } } } } } routing-instances { vrf01 { instance-type virtual-router; interface ge-0/0/1.0; interface ge-0/0/3.0; routing-options { static { route 12.34.56.0/24 next-hop 10.1.3.254; } 2775 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That Filter-Based Forwarding Was Configured on page 2776 Verifying That Filter-Based Forwarding Was Configured Purpose Action Verify that filter-based forwarding was properly enabled on the switch. 1. Use the show interfaces filters command: user@switch> show interfaces filters ge-0/0/0.0 Interface ge-0/0/0.0 Admin Link Proto Input Filter up down inet fil Output Filter 2. Use the show route forwarding-table command: user@switch> show route forwarding-table Routing table: default.inet Internet: Destination Type RtRef default user 1 default perm 0 0.0.0.0/32 perm 0 10.1.0.0/24 ifdn 0 ge-0/0/0.0 10.1.0.0/32 iddn 0 ge-0/0/0.0 10.1.0.1/32 user 0 10.1.0.1/32 intf 0 10.1.0.1/32 iddn 0 10.1.0.255/32 iddn 0 ge-0/0/0.0 10.1.1.0/26 ifdn 0 10.1.1.0/32 iddn 0 10.1.1.1/32 user 0 10.1.1.1/32 intf 0 10.1.1.1/32 iddn 0 10.1.1.63/32 iddn 0 255.255.255.255/32 perm 0 Routing table: vrf01.inet Internet: Destination Type RtRef default perm 0 0.0.0.0/32 perm 0 10.1.3.0/24 ifdn 0 ge-0/0/3.0 10.1.3.0/32 iddn 0 ge-0/0/3.0 10.1.3.1/32 user 0 10.1.3.1/32 intf 0 10.1.3.1/32 iddn 0 2776 Next hop 0:12:f2:21:cf:0 Type Index NhRef Netif ucst 331 4 me0.0 rjct 36 3 dscd 34 1 rslv 613 1 10.1.0.0 recv 611 1 10.1.0.1 10.1.0.1 10.1.0.255 rjct locl locl bcst 36 612 612 610 3 2 2 1 rslv recv rjct locl locl bcst bcst 583 581 36 582 582 580 32 1 vlan.0 1 vlan.0 3 2 2 1 vlan.0 1 10.1.1.0 10.1.1.1 10.1.1.1 10.1.1.63 Next hop Type Index NhRef Netif rjct 559 2 dscd 545 1 rslv 617 1 10.1.3.0 recv 615 1 10.1.3.1 10.1.3.1 rjct locl locl 559 616 616 2 2 2 Chapter 101: Examples of Firewall Filters Configuration 10.1.3.255/32 ge-0/0/3.0 224.0.0.0/4 224.0.0.1/32 255.255.255.255/32 Meaning Related Documentation iddn 0 10.1.3.255 bcst 614 1 perm perm perm 0 0 224.0.0.1 0 mdsc mcst bcst 546 529 543 1 1 1 Routing table: default.iso ISO: Destination Type RtRef Next hop default perm 0 Type Index NhRef Netif rjct 60 1 Routing table: vrf01.iso ISO: Destination Type RtRef Next hop default perm 0 Type Index NhRef Netif rjct 600 1 The output indicates that the filter was created on the interface and that the virtual routing instance is forwarding matching traffic to the correct IP address. • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Static Routing (CLI Procedure) on page 1444 • Configuring Static Routing (J-Web Procedure) on page 1444 • Understanding Filter-Based Forwarding for J-EX Series Switches on page 2753 2777 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2778 CHAPTER 102 Configuring Firewall Filters • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Assigning Multifield Classifiers in Firewall Filters to Specify Packet-Forwarding Behavior (CLI Procedure) on page 2791 • Configuring Routing Policies (J-Web Procedure) on page 2792 Configuring Firewall Filters (CLI Procedure) You configure firewall filters on J-EX Series switches to control traffic that enters ports on the switch or enters and exits VLANs on the network and Layer 3 (routed) interfaces. To configure a firewall filter you must configure the filter and then apply it to a port, VLAN, or Layer 3 interface. • Configuring a Firewall Filter on page 2779 • Applying a Firewall Filter to a Port on a Switch on page 2782 • Applying a Firewall Filter to a VLAN on a Network on page 2782 • Applying a Firewall Filter to a Layer 3 (Routed) Interface on page 2783 Configuring a Firewall Filter To configure a firewall filter: 2779 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1. Configure the family address type for the firewall filter: • For a firewall filter that is applied to a port or VLAN, specify the family address type ethernet-switching to filter Layer 2 (Ethernet) packets and Layer 3 (IP) packets, for example: [edit firewall] user@switch# set family ethernet-switching • For a firewall filter that is applied to a Layer 3 (routed) interface: • To filter IPv4 packets, specify the family address type inet, for example: [edit firewall] user@switch# set family inet • To filter IPv6 packets, specify the family address type inet6, for example: [edit firewall] user@switch# set family inet6 NOTE: You can configure firewall filters for both IPv4 and IPv6 traffic on the same Layer 3 interface. 2. Specify the filter name: [edit firewall family ethernet-switching] user@switch# set filter ingress-port-filter The filter name can contain letters, numbers, and hyphens (-) and can have a maximum of 64 characters. Each filter name must be unique. 3. If you want to apply a firewall filter to multiple interfaces and name individual firewall counters specific to each interface, configure the interface-specific option: [edit firewall family ethernet-switching filter ingress-port-filter] user@switch# set interface-specific 4. Specify a term name: [edit firewall family ethernet-switching filter ingress-port-filter] user@switch# set term term-one The term name can contain letters, numbers, and hyphens (-) and can have a maximum of 64 characters. A firewall filter can contain one or more terms. Each term name must be unique within a filter. NOTE: For J-EX4200 switches, the maximum number of terms allowed per firewall filter is 2048. For J-EX8200 switches, the maximum number of terms allowed per firewall filter is 32768. If you attempt to configure a firewall filter that exceeds these limits, the switch returns an error message when you commit the configuration. 2780 Chapter 102: Configuring Firewall Filters 5. In each firewall filter term, specify the match conditions to use to match components of a packet. To specify match conditions to match on packets that contain a specific source-address and source-port—for example: [edit firewall family ethernet-switching filter ingress-port-filter term term-one] user@switch# set from source-address 192.0.2.14 user@switch# set from source-port 80 You can specify one or more match conditions in a single from statement. For a match to occur, the packet must match all the conditions in the term. The from statement is optional, but if included in a term, the from statement cannot be empty. If you omit the from statement, all packets are considered to match. 6. In each firewall filter term, specify the actions to take if the packet matches all the conditions in that term. You can specify an action and/or action modifiers: • To specify a filter action, for example, to discard packets that match the conditions of the filter term: [edit firewall family ethernet-switching filter ingress-port-filter term term-one] user@switch# set then discard You can specify no more than one action (accept, discard, or routing-instance) per filter term. • To specify action modifiers, for example, to count and classify packets in a forwarding class: [edit firewall family ethernet-switching filter ingress-port-filter term term-one] user@switch# set then count counter-one user@switch# set then forwarding-class expedited-forwarding You can specify any of the following action modifiers in a then statement: • analyzer analyzer-name—Mirror port traffic to a specified destination port or VLAN that is connected to a protocol analyzer application. An analyzer must be configured under the ethernet-switching family address type. See “Configuring Port Mirroring to Analyze Traffic (CLI Procedure)” on page 3260. • count counter-name—Count the number of packets that pass this filter term. NOTE: We recommend that you configure a counter for each term in a firewall filter, so that you can monitor the number of packets that match the conditions specified in each filter term. • forwarding-class class—Classify packets in a forwarding class. 2781 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • loss-priority priority—Set the priority of dropping a packet. • policer policer-name—Apply rate-limiting to the traffic. If you omit the then statement or do not specify an action, packets that match all the conditions in the from statement are accepted. However, you must always explicitly configure an action and/or action modifier in the then statement. You can include no more than one action statement, but you can use any combination of action modifiers. For an action or action modifier to take effect, all conditions in the from statement must match. NOTE: Implicit discard is also applicable to a firewall filter applied to the loopback interface, lo0. Applying a Firewall Filter to a Port on a Switch To apply a firewall filter to an ingress port on a switch: 1. Specify the interface name and provide a meaningful description of the firewall filter and the interface to which the filter is applied: [edit interfaces] user@switch# set ge-0/0/1 description "filter to limit tcp traffic filter at trunk port for employee-vlan and voice-vlan applied on the interface" NOTE: Providing the description is optional. 2. Specify the unit number and family address type for the interface: [edit interfaces] user@switch# set ge-0/0/1 unit 0 family ethernet-switching For firewall filters that are applied to ports, the family address type must be ethernet-switching. 3. To apply a firewall filter to filter packets that are entering a port: [edit interfaces] user@switch# set ge-0/0/1 unit 0 family ethernet-switching filter input ingress-port-filter You cannot apply a firewall filter to filter packets that are exiting ports. NOTE: You can apply no more than one firewall filter per ingress port. Applying a Firewall Filter to a VLAN on a Network To apply a firewall filter to a VLAN: 2782 Chapter 102: Configuring Firewall Filters 1. Specify the VLAN name and VLAN ID and provide a meaningful description of the firewall filter and the VLAN to which the filter is applied: [edit vlans] user@switch# set employee-vlan vlan-id 20 vlan-description "filter to rate limit traffic applied on employee-vlan" NOTE: Providing the description is optional. 2. Apply firewall filters to filter packets that are entering or exiting the VLAN: • To apply a firewall filter to filter packets that are entering the VLAN: [edit vlans] user@switch# set employee-vlan vlan-id 20 filter input ingress-vlan-filter • To apply a firewall filter to filter packets that are exiting the VLAN: [edit vlans] user@switch# set employee-vlan vlan-id 20 filter output egress-vlan-filter NOTE: You can apply no more than one firewall filter per VLAN, per direction. Applying a Firewall Filter to a Layer 3 (Routed) Interface To apply a firewall filter to a Layer 3 (routed) interface on a switch: 1. Specify the interface name and provide a meaningful description of the firewall filter and the interface to which the filter is applied: [edit interfaces] user@switch# set ge-0/1/0 description "filter to count and monitor employee-vlan traffic applied on layer 3 interface" NOTE: Providing the description is optional. 2. Specify the unit number, family address type, and address for the interface: [edit interfaces] user@switch# set ge-0/1/0 unit 0 family inet address 10.10.10.1/24 For firewall filters applied to Layer 3 (routed) interfaces, the family address type must be inet (for IPv4 traffic) or inet6 (for IPv6 traffic). 3. You can apply firewall filters to filter packets that are entering or exiting a Layer 3 (routed) interface: • To apply a firewall filter to filter packets that are entering a Layer 3 interface: [edit interfaces] 2783 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch# set ge-0/1/0 unit 0 family inet address 10.10.10.1/24 filter input ingress-router-filter • To apply a firewall filter to filter packets that are exiting a Layer 3 interface: [edit interfaces] user@switch# set ge-0/1/0 unit 0 family inet address 10.10.10.1/24 filter output egress-router-filter NOTE: You can apply no more than one firewall filter per Layer 3 interface, per direction. Related Documentation • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 • Verifying That Firewall Filters Are Operational on page 2799 • Monitoring Firewall Filter Traffic on page 2800 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Assigning Multifield Classifiers in Firewall Filters to Specify Packet-Forwarding Behavior (CLI Procedure) on page 2791 • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Firewall Filters for J-EX Series Switches Overview on page 2721 Configuring Firewall Filters (J-Web Procedure) You configure firewall filters on J-EX Series switches to control traffic that enters ports on the switch or enters and exits VLANs on the network and Layer 3 (routed) interfaces. To configure a firewall filter you must configure the filter and then apply it to a port, VLAN, or Layer 3 interface. To configure firewall filter settings using the J-Web interface: 1. Select Configure > Security > Filters. The Firewall Filter Configuration page displays a list of all configured port/VLAN or router filters and the ports or VLANs associated with a particular filter. 2784 Chapter 102: Configuring Firewall Filters 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 334 for details about all commit options. 2. Click one: • Add—Select this option to create a new filter. Enter information as specified in Table 343 on page 2785. • Edit—Select this option to edit an existing filter. Enter information as specified in Table 343 on page 2785. • Delete—Select this option to delete a filter. • Term Up—Select this option to move a term up in the filter term list. • Term Down—Select this option to move a term down in the filter term list. Table 343: Create a New Filter Field Function Your Action Filter type Specifies the filter type: port/VLAN firewall filter or router firewall filter. Select the filter type. Filter name Specifies the name for the filter. Enter a name. Select terms to be part of the filter Specifies the terms to be associated with the filter. Add new terms or edit existing terms. Click Add to add new terms. Enter information as specified in Table 344 on page 2786 and Table 345 on page 2786. Specifies the ports with which the filter is associated. 1. NOTE: For a port/VLAN filter type, only Ingress direction is supported for port association. 2. Select the direction: Ingress or Egress. Filter tab Association tab Port Associations Click Add. 3. Select the ports. 4. Click OK. VLAN Associations Specifies the VLANs with which the filter is associated. 1. Click Add. NOTE: Because router firewall filters can be associated with ports only, this section is not displayed for a router firewall filter. 2. Select the direction: Ingress or Egress. 3. Select the VLANs. 4. Click OK. 2785 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 344: Create a New Term Field Function Your Action Term Name Specifies the name of the term. Enter a name. Protocols Specifies the protocols to be associated with the term. 1. Click Add. 2. Select the protocols. 3. Click OK. Source Specifies the source IP address, MAC address, and available ports. To specify the IP address, click Add > IP and enter the IP address. NOTE: MAC address is specified only for port/VLAN filters. To specify the MAC address, click Add > MAC and enter the MAC address. To specify the ports (interfaces), click Add > Ports and enter the port number. To delete the IP address, MAC address, or port details, select it and click Remove. Destination Specifies the destination IP address, MAC address, and available ports. To specify the IP address, click Add > IP and enter the IP address. NOTE: MAC address is specified only for port/VLAN filters. To specify the MAC address, click Add > MAC and enter the MAC address. To specify the ports (interfaces), click Add > Ports and enter the port number. To delete the IP address, MAC address, or port details, select it and click Remove. Action More Specifies the packet action for the term. Specifies advanced configuration options for the filter. Select one: • Accept • Discard Select the match conditions as specified in Table 345 on page 2786. Select the packet action for the term as specified in Table 345 on page 2786. Table 345: Advanced Options for Terms Table Function Your Action ICMP Type Specifies the ICMP packet type field. Typically, you specify this match condition in conjunction with the protocol match condition to determine which protocol is being used on the port. Select the option from the list. 2786 Chapter 102: Configuring Firewall Filters Table 345: Advanced Options for Terms (continued) Table Function Your Action ICMP Code Specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify icmp-type along with icmp-code. The keywords are grouped by the ICMP type with which they are associated. Select a value from the list. DSCP Specifies the Differentiated Services code point (DSCP). The DiffServ protocol uses the type-of-service (ToS) byte in the IP header. The most significant six bits of this byte form the DSCP. Select the DSCP number from the list. Precedence Specifies IP precedence. Select the option from the list. NOTE: IP precedence and DSCP number cannot be specified together for the same term. IP Options Specifies the presence of the options field in the IP header. Select the option from the list. Interface Specifies the interface on which the packet is received. Select the interface from the list. Ether type Specifies the Ethernet type field of a packet. Select a value from the list. NOTE: This option is not applicable for a routing filter. Dot 1q user priority Specifies the user-priority field of the tagged Ethernet packet. User-priority values can be 0–7. Select a value from the list. In place of the numeric value, you can specify one of the following text synonyms (the field values are also listed) • background (1)—Background • best-effort (0)—Best effort • controlled-load (4)—Controlled load • excellent-load (3)—Excellent load • network-control (7)—Network control reserved traffic • standard (2)—Standard or Spare • video (5)—Video • voice (6)—Voice NOTE: This option is not applicable for a routing filter. VLAN Specifies the VLAN to be associated with the packet. Select the VLAN from the list. NOTE: This option is not applicable for a routing filter. TCP Flags Specifies one or more TCP flags. NOTE: TCP flags are supported on ingress ports, VLANs, and router interfaces. Select the option TCP Initial or enter a combination of TCP flags. 2787 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 345: Advanced Options for Terms (continued) Table Function Your Action Fragmentation Flags Specifies the IP fragmentation flags. Select either the option is-fragment or enter a combination of fragment action flags. NOTE: Fragmentation flags are supported on ingress ports, VLANs, and router interfaces. Dot1q tag Specifies the value for tag field in the Ethernet header. Values can be from 1 through 4095. Enter the value. NOTE: This option is not applicable for a routing filter. Action Counter name Specifies the count of the number of packets that pass this filter, term, or policer. Enter a value. Forwarding class Classifies the packet into one of the following forwarding classes: Select the option from the list. Loss priority • assured-forwarding • best-effort • expedited-forwarding • network-control • user-defined Specifies the packet loss priority. Enter the value. NOTE: Forwarding class and loss priority should be specified together for the same term. Analyzer Specifies whether to perform port-mirroring on packets. Port-mirroring copies all packets entering one switch port to a network monitoring connection on another switch port. Related Documentation Select the analyzer (port mirroring configuration) from the list. • Configuring Firewall Filters (CLI Procedure) on page 2779 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 Configuring Policers to Control Traffic Rates (CLI Procedure) You can configure policers to rate limit traffic on J-EX Series switches. After you configure a policer, you can include it in an ingress firewall filter configuration. When you configure a firewall filter, you can specify a policer action for any term or terms within the filter. All traffic that matches a term that contains a policer action goes through 2788 Chapter 102: Configuring Firewall Filters the policer that the term references. Each policer that you configure includes an implicit counter. To get term-specific packet counts, you must configure a new policer for each filter term that requires policing. The following policer limits apply on the switch: • A maximum of 512 policers can be configured for port firewall filters. • A maximum of 512 policers can be configured for VLAN and Layer 3 firewall filters. If the policer configuration exceeds these limits, the switch returns the following message after the commit operation: Cannot assign policers: Max policer limit reached 1. Configuring Policers on page 2789 2. Specifying Policers in a Firewall Filter Configuration on page 2790 3. Applying a Firewall Filter That Is Configured with a Policer on page 2790 Configuring Policers To configure a policer: 1. Specify the name of the policer: [edit firewall] user@switch# set policer policer-one The policer name can contain letters, numbers, and hyphens (-) and can be up to 64 characters long. 2. Configure rate limiting for the policer: a. Specify the bandwidth limit in bits per second (bps) to control the traffic rate on an interface: [edit firewall policer policer-one] user@switch# set if-exceeding bandwidth-limit 300k The range for the bandwidth limit is 1k through 102.3g bps. b. Specify the maximum allowed burst size to control the amount of traffic bursting: [edit firewall policer policer-one] user@switch# set if-exceeding burst-size-limit 500k To determine the value for the burst-size limit, multiply the bandwidth of the interface on which the filter is applied by the amount of time to allow a burst of traffic at that bandwidth to occur: burst size = bandwidth * allowable time for burst traffic The range for the burst-size limit is 1 through 2,147,450,880 bytes. 3. Specify the policer action discard to discard packets that exceed the rate limits: [edit firewall policer] user@switch# set policer-one then discard 2789 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Discard is the only supported policer action. Specifying Policers in a Firewall Filter Configuration To reference a policer for a single firewall, configure a filter term that includes the policer action: [edit firewall family ethernet-switching] user@switch# set filter limit-hosts term term-one from source-address 192.0.2.16/28 user@switch# set filter limit-hosts term term-one then policer policer-one Applying a Firewall Filter That Is Configured with a Policer A firewall filter that is configured with one or more policer actions, like any other filter, must be applied to a port, VLAN, or Layer 3 interface. For information about applying firewall filters, see the sections on applying firewall filters in “Configuring Firewall Filters (CLI Procedure)” on page 2779. NOTE: You can include policer actions on ingress firewall filters only. Related Documentation 2790 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Verifying That Policers Are Operational on page 2800 • Understanding the Use of Policers in Firewall Filters on page 2752 Chapter 102: Configuring Firewall Filters Assigning Multifield Classifiers in Firewall Filters to Specify Packet-Forwarding Behavior (CLI Procedure) You can configure firewall filters with multifield classifiers to classify packets transiting a port, VLAN, or Layer 3 interface on a J-EX Series switch. You specify multifield classifiers in a firewall filter configuration to set the forwarding class and packet loss priority (PLP) for incoming or outgoing packets. By default, the data traffic that is not classified is assigned to the best-effort class associated with queue 0. You can specify any of the following default forwarding classes: Forwarding class Queue best-effort 0 assured-forwarding 1 expedited-forwarding 5 network-control 7 To assign multifield classifiers in firewall filters: 1. Configure the family name and filter name for the filter at the [edit firewall] hierarchy level, for example: [edit firewall] user@switch# set family ethernet-switching user@switch# set family ethernet-switching filter ingress-filter 2. Configure the terms of the filter, including the forwarding-class and loss-priority action modifiers as appropriate. When you specify a forwarding class you must also specify the packet loss priority. For example, each of the following terms examines different packet header fields and assigns an appropriate classifier and the packet loss priority: • The term voice-traffic matches packets on the voice-vlan and assigns the forwarding class expedited-forwarding and packet loss priority low: [edit firewall family ethernet-switching filter ingress-filter] user@switch# set term voice-traffic from vlan-id voice-vlan user@switch# set term voice-traffic then forwarding-class expedited-forwarding user@switch# set term voice-traffic then loss-priority low • The term data-traffic matches packets on employee-vlan and assigns the forwarding class assured-forwarding and packet loss priority low: [edit firewall family ethernet-switching filter ingress-filter] user@switch# set term data-traffic from vlan-id employee-vlan user@switch# set term data-traffic then forwarding-class assured-forwarding user@switch# set term data-traffic then loss-priority low 2791 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Because loss of network-generated packets can jeopardize proper network operation, delay is preferable to discard of packets. The following term, network-traffic, assigns the forwarding class network-control and packet loss priority low: [edit firewall family ethernet-switching filter ingress-filter] user@switch# set term network-traffic from precedence net-control user@switch# set term network-traffic then forwarding-class network user@switch# set term network-traffic then loss-priority low • The last term accept-traffic matches any packets that did not match on any of the preceding terms and assigns the forwarding class best-effort and packet loss priority low: [edit firewall family ethernet-switching filter ingress-filter] user@switch# set term accept-traffic from precedence net-control user@switch# set term accept-traffic then forwarding-class best-effort user@switch# set term accept-traffic then loss-priority low 3. Apply the filter ingress-filter to a port, VLAN or Layer 3 interface. For information about applying the filter, see “Configuring Firewall Filters (CLI Procedure)” on page 2779. Related Documentation • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 • Monitoring Firewall Filter Traffic on page 2800 • Defining CoS Classifiers (CLI Procedure) on page 2914 • Defining CoS Classifiers (J-Web Procedure) on page 2916 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 Configuring Routing Policies (J-Web Procedure) All routing protocols use the Junos OS routing table to store the routes that they learn and to determine which routes are advertised in the protocol packets. Routing policy allows you to control which routes the routing protocols store in and retrieve from the routing table on the routing device. To configure routing policies for a J-EX Series switch using the J-Web interface: 1. Select Configure > Routing > Policies. 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 334 for details about all commit options. 2792 Chapter 102: Configuring Firewall Filters 2. Click one: • Global Options—Configures global options for policies. Enter information into the configuration page as described in Table 346 on page 2793. • Add—Configures a new policy. Select New and specify a policy name. To add terms, enter information into the configuration page as described in Table 347 on page 2794 . Select Clone to create a copy of an existing policy. • Edit—Edits an existing policy. To modify an existing term, enter information into the configuration page as described in Table 347 on page 2794. • Term Up—Moves a term up in the list. • Term Down—Moves a term down in the list. • Delete—Deletes the selected policy. • Test Policy—Tests the policy. Use this option to check whether the policy produces the results that you expect. Table 346: Policies Global Configuration Parameters Field Function Your Action Prefix List Specifies a list of IPv4 address prefixes for use in a routing policy statement. To add a prefix list: 1. Click Add. 2. Enter a name for the prefix list. 3. To add an IP address, click Add. 4. Enter the IP address and the subnet mask and click OK. 5. Click OK. To edit a prefix list, click Edit. Edit the settings and click OK. To delete a prefix list, select it and click Delete. BGP Community Specifies a BGP community. To add a BGP community: 1. Click Add. 2. Enter a name for the community. 3. To add a community, click Add. 4. Enter the community ID and click OK. 5. Click OK. To edit a BGP community, click Edit. Edit the settings and click OK. To delete a BGP community, select it and click Delete. 2793 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 346: Policies Global Configuration Parameters (continued) Field Function Your Action AS Path Specifies an AS path. This is applicable to BGP only. To add an AS path: 1. Click Add. 2. Enter the AS path name. 3. Enter the regular expression and click OK. 4. Click OK. To edit an AS path, click Edit. Edit the settings and click OK. To delete an AS path, select it and click Delete. Table 347: Terms Configuration Parameters Field Function Your Action Term Name Specifies a term name. Type or select and edit the name. Family Specifies an address family protocol. Select a value from the list. Routing Instance Specifies a routing instance. Select a value from the list. RIB Specifies the name of a routing table. Select a value from the list Preference Specifies the individual preference value for the route. Type or select and edit the value. Metric Specifies a metric value. You can specify up to four metric values. Type or select and edit the value. Interface Specifies a name or IP address of one or more routing device interfaces. Do not use this qualifier with protocols that are not interface-specific, such as internal BGP (IBGP). To add an interface, select Add > Interface. Select the interface from the list. Source tab To add an address, select Add > Address. Select the address from the list. To remove an interface, select it and click Remove. Prefix List Specifies a named list of IP addresses. You can specify an exact match with incoming routes. Click Add. Select the prefix list from the list and click OK. To remove a prefix list, select it and click Remove. Protocol Specifies the name of the protocol from which the route was learned or to which the route is being advertised. Click Add and select the protocol from the list. To remove a protocol, select it and click Remove. 2794 Chapter 102: Configuring Firewall Filters Table 347: Terms Configuration Parameters (continued) Field Function Your Action Policy Specifies the name of a policy to evaluate as a subroutine. Click Add. Select the policy from the list. To remove a policy, select it and click Remove. More Specifies advanced configuration options for policies. Click More for advanced configuration. OSPF Area ID Specifies the area identifier. Type the IP address. BGP Origin Specifies the origin of the AS path information. Select a value from the list. Local Preference Specifies the BGP local preference. Type a value. Route Specifies the type of route. Select External. Select the OSPF type from the list. AS Path Specifies the name of an AS path regular expression. Click Add. Select the AS path from the list. Community Specifies the name of one or more communities. Click Add. Select the community from the list. Family Specifies an address family protocol. Select a value from the list. Routing Instance Specifies a routing instance. Select a value from the list. RIB Specifies the name of a routing table. Select a value from the list. Preference Specifies the individual preference value for the route. Type a value. Metric Specifies a metric value. Type a value. Interface Specifies a name or IP address of one or more routing device interfaces. Do not use this qualifier with protocols that are not interface-specific, such as internal BGP (IBGP). To add an interface, select Add > Interface. Select the interface from the list. Destination tab To add an address, select Add > Address. Select the address from the list. To delete an interface, select it and click Remove. Protocol Specifies the name of the protocol from which the route was learned or to which the route is being advertised. Click Add and select the protocol from the list. To delete a protocol, select it and click Remove. Action tab 2795 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 347: Terms Configuration Parameters (continued) Field Function Your Action Action Specifies the action to take if the conditions match. Select a value from the list. Default Action Specifies that any action that is intrinsic to the protocol is overridden. This action is also nonterminating, so that various policy terms can be evaluated before the policy is terminated. Select a value from the list. Next Specifies the default control action if a match occurs, and there are no further terms in the current routing policy. Select a value from the list. Priority Specifies a priority for prefixes included in an OSPF import policy. Prefixes learned through OSPF are installed in the routing table based on the priority assigned to the prefixes. Select a value from the list. BGP Origin Specifies the BGP origin attribute. Select a value from the list. AS Path Prepend Affixes an AS number at the beginning of the AS path. The AS numbers are added after the local AS number has been added to the path. This action adds an AS number to AS sequences only, not to AS sets. If the existing AS path begins with a confederation sequence or set, the affixed AS number is placed within a confederation sequence. Otherwise, the affixed AS number is placed with a nonconfederation sequence. Enter a value. AS Path Expand Extracts the last AS number in the existing AS path and affixes that AS number to the beginning of the AS path n times, where n is a number from 1 through 32. The AS number is added before the local AS number has been added to the path. This action adds AS numbers to AS sequences only, not to AS sets. If the existing AS path begins with a confederation sequence or set, the affixed AS numbers are placed within a confederation sequence. Otherwise, the affixed AS numbers are placed within a nonconfederation sequence. This option is typically used in non-IBGP export policies. Select the type and type a value. Load Balance Per Packet Specifies that all next-hop addresses in the forwarding table must be installed and have the forwarding table perform per-packet load balancing. This policy action allows you to optimize VPLS traffic flows across multiple paths. Select the check box to enable the option. Tag Specifies the tag value. The tag action sets the 32-bit tag field in OSPF external link-state advertisement (LSA) packets. Select the action and type a value. Metric Changes the metric (MED) value by the specified negative or positive offset. This action is useful only in an external BGP (EBGP) export policy. Select the action and type a value. Route Specifies whether the route is external. Select the External check box to enable the option, and select the OSPF type. Preference Specifies the preference value. Select the preference action and type a value. 2796 Chapter 102: Configuring Firewall Filters Table 347: Terms Configuration Parameters (continued) Field Function Your Action Local Preference Specifies the BGP local preference attribute. Select the action and type a value. Class of Service Specifies and applies the class-of-service parameters to routes installed into the routing table. Type the source class. Type the destination class. • Source class The value entered here maintains the packet counts for a route passing through your network, based on the source address. • Type the forwarding class. Destination class The value entered here maintains packet counts for a route passing through your network, based on the destination address in the packet. • Forwarding class Related Documentation • Configuring BGP Sessions (J-Web Procedure) on page 1431 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Configuring a RIP Network (J-Web Procedure) on page 1439 • Configuring Static Routing (J-Web Procedure) on page 1444 • Layer 3 Protocols Supported on J-EX Series Switches on page 13 2797 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2798 CHAPTER 103 Verifying Firewall Filter Configuration • Verifying That Firewall Filters Are Operational on page 2799 • Verifying That Policers Are Operational on page 2800 • Monitoring Firewall Filter Traffic on page 2800 Verifying That Firewall Filters Are Operational Purpose Action After you configure and apply firewall filters to ports, VLANs, or Layer 3 interfaces, you can perform the following task to verify that the firewall filters configured on J-EX Series switches are working properly. Use the operational mode command to verify that the firewall filters on the switch are working properly: user@switch> show firewall Filter: egress-vlan-watch-employee Counters: Name counter-employee-web Filter: ingress-port-voip-class-limit-tcp-icmp Counters: Name icmp-counter Policers: Name icmp-connection-policer tcp-connection-policer Filter: ingress-vlan-rogue-block Filter: ingress-vlan-limit-guest Meaning Related Documentation Bytes 0 Packets 0 Bytes 0 Packets 0 Packets 0 0 The show firewall command displays the names of all firewall filters, policers, and counters that are configured on the switch. For each counter that is specified in a filter configuration, the output field shows the byte count and packet count for the term in which the counter is specified. For each policer that is specified in a filter configuration, the output field shows the packet count for packets that exceed the specified rate limits. • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 2799 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Monitoring Firewall Filter Traffic on page 2800 Verifying That Policers Are Operational Purpose After you configure policers and include them in firewall filter configurations, you can perform the following tasks to verify that the policers configured on J-EX Series switches are working properly. Action Use the operational mode command to verify that the policers on the switch are working properly: user@switch> show policer Filter: egress-vlan-watch-employee Filter: ingress-port-filter Filter: ingress-port-voip-class-limit-tcp-icmp Policers: Name icmp-connection-policer tcp-connection-policer Filter: ingress-vlan-rogue-block Filter: ingress-vlan-limit-guest Meaning Related Documentation Packets 0 0 The show policer command displays the names of all firewall filters and policers that are configured on the switch. For each policer that is specified in a filter configuration, the output field shows the current packet count for all packets that exceed the specified rate limits. • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Monitoring Firewall Filter Traffic on page 2800 Monitoring Firewall Filter Traffic You can monitor firewall filter traffic on J-EX Series switches. 2800 • Monitoring Traffic for All Firewall Filters and Policers That Are Configured on the Switch on page 2801 • Monitoring Traffic for a Specific Firewall Filter on page 2801 • Monitoring Traffic for a Specific Policer on page 2801 Chapter 103: Verifying Firewall Filter Configuration Monitoring Traffic for All Firewall Filters and Policers That Are Configured on the Switch Purpose Action Perform the following task to monitor the number of packets and bytes that matched the firewall filters and monitor the number of packets that exceeded policer rate limits: Use the operational mode command: user@switch> show firewall Filter: egress-vlan-watch-employee Counters: Name counter-employee-web Filter: ingress-port-voip-class-limit-tcp-icmp Counters: Name icmp-counter Policers: Name icmp-connection-policer tcp-connection-policer Filter: ingress-vlan-rogue-block Filter: ingress-vlan-limit-guest Meaning Bytes 3348 Packets 27 Bytes 4100 Packets 49 Packets 0 0 The show firewall command displays the names of all firewall filters, policers, and counters that are configured on the switch. The output fields show byte and packet counts for counters and packet count for policers. Monitoring Traffic for a Specific Firewall Filter Purpose Action Perform the following task to monitor the number of packets and bytes that matched a firewall filter and monitor the number of packets that exceeded the policer rate limits. Use the operational mode command: user@switch> show firewall filter ingress-vlan-rogue-block Filter: ingress-vlan-rogue-block Counters: Name rogue-counter Meaning Bytes 2308 Packets 20 The show firewall filter filter-name command displays the name of the firewall filter, the packet and byte count for all counters configured with the filter, and the packet count for all policers configured with the filter. Monitoring Traffic for a Specific Policer Purpose Action Perform the following task to monitor the number of packets that exceeded policer rate limits: Use the operational mode command: user@switch> show policer tcp-connection-policer Filter: ingress-port-voip-class-limit-tcp-icmp Policers: 2801 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Name tcp-connection-policer Meaning Related Documentation 2802 Packets 0 The show policer policer-name command displays the name of the firewall filter that specifies the policer-action and displays the number of packets that exceeded rate limits for the specified filter. • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 CHAPTER 104 Troubleshooting Firewall Filters • Troubleshooting Firewall Filters on page 2803 Troubleshooting Firewall Filters 1. Firewall Filter Configuration Returns a No Space Available in TCAM Message on page 2803 Firewall Filter Configuration Returns a No Space Available in TCAM Message Problem When a firewall filter configuration exceeds the amount of available ternary content addressable memory (TCAM) space, the switch returns the following syslogd message: No space available in tcam. Rules for filter filter-name will not be installed. The switch returns this message during the commit operation if the firewall filter that has been applied to a port, VLAN, or Layer 3 interface exceeds the amount of available TCAM space. However, the commit operation for the firewall filter configuration is completed in the CLI module. Solution When a firewall filter configuration exceeds the amount of available TCAM table space, you must configure a new firewall filter with fewer filter terms so that the space requirements for the filter do not exceed the available space in the TCAM table. You can perform either of the following procedures to correct the problem: To delete the firewall filter and its bind points and apply the new smaller firewall filter to the same bind points: 1. Delete the firewall filter configuration and the bind points to ports, VLANs, or Layer 3 interfaces—for example: [edit] user@switch# delete firewall family ethernet-switching filter filter-ingress-vlan user@switch# delete vlans voice-vlan description "filter to block rogue devices on voice-vlan" user@switch# delete vlans voice-vlan filter input mini-filter—ingress-vlan 2. Commit the operation: [edit] user@switch# commit 2803 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3. Configure a smaller filter with fewer terms that does not exceed the amount of available TCAM space on the switch—for example: [edit] user@switch# set firewall family ethernet-switching filter new—filter-ingress-vlan ... 4. Apply (bind) the new firewall filter to a port, VLAN , or Layer 3 interface—for example: [edit] user@switch# set vlans voice-vlan description "filter to block rogue devices on voice-vlan" user@switch# set vlans voice-vlan filter input new-filter—ingress-vlan 5. Commit the operation: [edit] user@switch# commit To apply a new firewall filter and overwrite the existing bind points: 1. Configure a firewall filter with fewer terms than the original filter: [edit] user@switch# set firewall family ethernet-switching filter new-filter-ingress-vlan... 2. Apply the firewall filter to the port, VLAN, or Layer 3 interfaces to overwrite the bind points of the original filter—for example: [edit] user@switch# set vlans voice-vlan description "smaller filter to block rogue devices on voice-vlan" user@switch# set vlans voice-vlan filter input new-filter-ingress-vlan 3. Commit the operation: [edit] user@switch# commit Only the original bind points, and not the original firewall filter itself, are deleted. Related Documentation 2804 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 CHAPTER 105 Configuration Statements for Firewall Filters • [edit firewall] Configuration Statement Hierarchy on page 2805 • Firewall Filter Configuration Statements Supported by the Junos OS for J-EX Series Switches on page 2806 [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 • Firewall Filter Configuration Statements Supported by Junos OS for J-EX Series Switches on page 2806 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 2805 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Firewall Filters for J-EX Series Switches Overview on page 2721 Firewall Filter Configuration Statements Supported by the Junos OS for J-EX Series Switches You configure firewall filters to filter packets based on their components and to perform an action on packets that match the filter. Table 348 on page 2806 lists the options that are supported for the firewall statement in Junos OS for J-EX Series switches. Table 348: Supported Options for Firewall Filter Statements Statement and Option family family-name { } Description The family-name option specifies the version or type of addressing protocol: • any—Filter packets based on protocol-independent match conditions. • ethernet-switching—Filter Layer 2 (Ethernet) packets and Layer 3 (IP) packets • inet—Filter IPv4 packets • inet6—Filter IPv6 packets filter filter-name { } The filter-name option identifies the filter. The name can contain letters, numbers, and hyphens (-) and can be up to 64 characters long. To include spaces in the name, enclose the name in quotation marks (" "). interface-specific The interface-specific statement configures unique names for individual firewall counters specific to each interface. term term-name { } The term-name option identifies the term. The name can contain letters, numbers, and hyphens (-) and can be up to 64 characters long. To include spaces in the name, enclose the entire name in quotation marks (" " ). Each term name must be unique within a filter. from { match-conditions; } The from statement is optional. If you omit it, all packets are considered to match. then { action; action-modifiers; } For information about the action and action-modifiers options, see “Firewall Filter Match Conditions and Actions for J-EX Series Switches” on page 2728. 2806 Chapter 105: Configuration Statements for Firewall Filters Table 348: Supported Options for Firewall Filter Statements (continued) Statement and Option Description policer policer-name { } The policer-name option identifies the policer. The name can contain letters, numbers, and hyphens (-) and can be up to 64 characters long. To include spaces in the name, enclose the name in quotation marks (" "). filter-specific The filter-specific statement configures policers and counters for a specific filter name. if-exceeding { bandwidth-limit bps burst-size-limit bytes } The bandwidth-limit bps option specifies the traffic rate in bits per second (bps). You can specify bps as a decimal value or as a decimal number followed by one of the following abbreviations: • k (thousand) • m (million) • g (billion, which is also called a thousand million) Range: 1000 (1k) through 102,300,000,000 (102.3g) bps The burst-size-limit bytes option specifies the maximum allowed burst size to control the amount of traffic bursting. To determine the value for the burst-size limit, you can multiply the bandwidth of the interface on which the filter is applied by the amount of time (in seconds) to allow a burst of traffic at that bandwidth to occur: burst size = bandwidth * allowable time for burst traffic You can specify a decimal value or a decimal number followed by k (thousand) or m (million). Range: 1 through 2,147,450,880 bytes then { policer-action } Use the policer-action option to specify discard to discard traffic that exceeds the rate limits. The Junos OS for J-EX Series switches does not support some of the firewall filter statements that are supported by other Junos OS packages. Table 349 on page 2808 shows the firewall filter statements that are not supported by Junos OS for J-EX Series switches. 2807 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 349: Firewall Filter Statements That Are Not Supported by the Junos OS for J-EX Series Switches Statements Not Supported Statement Hierarchy Level • interface-set interface-set-name { } • load-balance-group group-name { } • three-color-policer name { } • logical-interface-policer; • single-rate { } • two-rate { } • prefix-action name { } • prefix-policer { } • service-filter filter-name { } • simple-filter simple-filter-name { } • accounting-profile name; [edit firewall family family-name filter filter-name] • logical-bandwidth-policer; [edit firewall policer policer-name] • logical-interface-policer; [edit firewall family family-name] bandwidth-percent number; Related Documentation 2808 [edit firewall] [edit firewall policer policer-name if-exceeding] • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Firewall Filters for J-EX Series Switches Overview on page 2721 Chapter 105: Configuration Statements for Firewall Filters apply-path Syntax Hierarchy Level Release Information Description Options apply-path path; [edit logical-systems logical-system-name policy-options prefix-list name], [edit policy-options prefix-list name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Expand a prefix list to include all prefixes pointed to by a defined path. path—String of elements composed of identifiers or configuration keywords that points to a set of prefixes. You can include wildcards (enclosed in angle brackets) to match more than one identifier. You cannot add a path element, including wildcards, after a leaf statement. Path elements, including wildcards, can only be used after a container statement. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Prefix Lists as-path Syntax Hierarchy Level Release Information Description Options as-path name regular-expression; [edit dynamic policy-options], [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define an autonomous system (AS) path regular expression for use in a routing policy match condition. name—Name that identifies the regular expression. The name can contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To include spaces in the name, enclose it in quotation marks (“ ”). regular-expression—One or more regular expressions used to match the AS path. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring AS Path Regular Expressions to Use as Routing Policy Match Conditions • Configuring Routing Policies and Policy Objects in the Dynamic Database • dynamic-db on page 2817 2809 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS as-path-group Syntax Hierarchy Level Release Information Description Options as-path-group group-name { as-path name regular-expression; } [edit dynamic policy-options], [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a group containing multiple AS path regular expressions for use in a routing policy match condition. group-name—Name that identifies the AS path group. One or more AS path regular expressions must be listed below the as-path-group hierarchy. name—Name that identifies the regular expression. The name can contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To include spaces in the name, enclose it in quotation marks (“ ”). regular-expression—One or more regular expressions used to match the AS path. Required Privilege Level Related Documentation 2810 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring AS Path Regular Expressions to Use as Routing Policy Match Conditions • Configuring Routing Policies and Policy Objects in the Dynamic Database • dynamic-db on page 2817 Chapter 105: Configuration Statements for Firewall Filters bandwidth-limit Syntax Hierarchy Level Release Information Description Options bandwidth-limit bps; [edit firewall policer policer-name if-exceeding] [edit logical-systems logical-system-name firewall policer policer-name if-exceeding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the traffic rate in bits per second. bps —Traffic rate to be specified in bits per second. Specify bps as a decimal value or as a decimal number followed by one of the following abbreviations: • k (thousand) • m (million) • g (billion, which is also called a thousand million) Range: Required Privilege Level Related Documentation • 1000 (1k) through 102,300,000,000 (102.3g) bps (J-EX Series switches) • 8000 (8k) through 40,000,000,000 (40g) bps (routers) firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 • Rate Limiting • Single-Rate Two-Color Policer Overview • Configuring a Single-Rate Two-Color Policer 2811 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS burst-size-limit Syntax Hierarchy Level Release Information Description Options burst-size-limit bytes; [edit firewall policer policer-name if-exceeding] [edit logical-systems logical-system-name firewall policer policer-name if-exceeding] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the maximum allowed burst size to control the amount of traffic bursting. bytes —Decimal value or a decimal number followed by k (thousand) or m (million). Range: Required Privilege Level Related Documentation 2812 • 1 through 2,147,450,880 bytes (J-EX Series switches) • 1500 through 1,00,000,000,000 bytes (routers) firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 • Rate Limiting • Single-Rate Two-Color Policer Overview • Configuring a Single-Rate Two-Color Policer Chapter 105: Configuration Statements for Firewall Filters community Syntax Hierarchy Level Release Information community name { invert-match; members [ community-ids ]; } [edit dynamic policy-options], [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Define a community or extended community for use in a routing policy match condition. Options name—Name that identifies the regular expression. The name can contain letters, numbers, and hyphens (-) and can be up to 255 characters. To include spaces in the name, enclose it in quotation marks (“ ”). invert-match—Invert the results of the community expression matching. members community-ids—One or more community members. If you specify more than one member, you must enclose all members in brackets. The format for community-ids is: as-number:community-value as-number is the AS number and can be a value in the range from 0 through 65,535. community-value is the community identifier and can be a number in the range from 0 through 65,535. You also can specify community-ids for communities as one of the following well-known community names, which are defined in RFC 1997, BGP Communities Attribute: • no-export—Routes containing this community name are not advertised outside a BGP confederation boundary. • no-advertise—Routes containing this community name are not advertised to other BGP peers. • no-export-subconfed—Routes containing this community name are not advertised to external BGP peers, including peers in other members' ASs inside a BGP confederation. You can explicitly exclude BGP community information with a static route using the none option. Include none when configuring an individual route in the route portion of the static statement to override a community option specified in the defaults portion of the statement. The format for extended community-ids is the following: type:administrator:assigned-number 2813 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS type is the type of extended community and can be either a bandwidth, target, origin, domain-id, src-as, or rt-import community or a 16-bit number that identifies a specific BGP extended community. The target community identifies the destination to which the route is going. The origin community identifies where the route originated. The domain-id community identifies the OSPF domain from which the route originated. The src-as community identifies the autonomous system from which the route originated. The rt-import community identifies the route to install in the routing table. NOTE: For src-as, you can specify only an AS number and not an IP address. For rt-import, you can specify only an IP address and not an AS number. administrator is the administrator. It is either an AS number or an IPv4 address prefix, depending on the type of extended community. assigned-number identifies the local provider. The format for linking a bandwidth with an AS number is: bandwidth:as-number:bandwidth as-number specifies the AS number and bandwidth specifies the bandwidth in bytes per second. NOTE: You can specify 4-byte AS numbers as defined in RFC 4893, BGP Support for Four-octet AS Number Space, as well as the 2-byte AS numbers. In plain-number format, you can configure a value in the range from 1 through 4,294,967,295. To configure a target or origin extended community that includes a 4-byte AS number in the plain-number format, append the letter “L” to the end of number. For example, a target community with the 4-byte AS number 334,324 and an assigned number of 132 is represented as target:334324L:132. You can also use AS-dot notation when defining a 4-byte AS number for the target and origin extended communities. Specify two integers joined by a period: 16-bit high-order value in decimal.16-bit low-order value in decimal. For example, the 4-byte AS number represented in plain-number format as 65546 is represented in AS-dot notation as 1.10. For more information about configuring AS numbers, see the Junos OS Routing Protocols Configuration Guide. Required Privilege Level 2814 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 105: Configuration Statements for Firewall Filters Related Documentation • Overview of BGP Communities and Extended Communities as Routing Policy Match Conditions • Defining BGP Communities and Extended Communities for Use in Routing Policy Match Conditions • Configuring Routing Policies and Policy Objects in the Dynamic Database • dynamic-db on page 2817 condition Syntax Hierarchy Level Release Information Description Options condition condition-name { if-route-exists address table table-name; } [edit dynamic policy-options], [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a policy condition based on the existence of routes in specific tables for use in BGP export policies. if-route-exists address—Specify the address of the route in question. table table-name—Specify a routing table. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Routing Policy Match Conditions Based on Routing Table Entries • Configuring Routing Policies and Policy Objects in the Dynamic Database • dynamic-db on page 2817 2815 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS damping Syntax Hierarchy Level Release Information Description Options damping name { disable; half-life minutes; max-suppress minutes; reuse number; suppress number; } [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. . Define route flap damping properties to set on BGP routes. disable—Disable damping on a per-prefix basis. Any damping state that is present in the routing table for a prefix is deleted if damping is disabled. half-life minutes—Decay half-life. minutes is the interval after which the accumulated figure-of-merit value is reduced by half if the route remains stable. Range: 1 through 45 Default: 15 minutes max-suppress minutes—Maximum hold-down time. minutes is the maximum time that a route can be suppressed no matter how unstable it has been. Range: 1 through 720 Default: 60 minutes name—Name that identifies the set of damping parameters. The name can contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To include spaces in the name, enclose it in quotation marks (“ ”). reuse number—Reuse threshold. number is the figure-of-merit value below which a suppressed route can be used again. Range: 1 through 20,000 Default: 750 (unitless) suppress number—Cutoff (suppression) threshold. number is the figure-of-merit value above which a route is suppressed for use or inclusion in advertisements. Range: 1 through 20,000 Default: 3000 (unitless) Required Privilege Level 2816 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. Chapter 105: Configuration Statements for Firewall Filters Related Documentation • Configuring BGP Flap Damping Parameters dynamic-db Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation dynamic-db; [edit logical-systems logical-system-name policy-options as-path path-name], [edit logical-systems logical-system-name policy-options as-path-group group-name], [edit logical-systems logical-system-name policy-options community community-name], [edit logical-systems logical-system-name policy-options condition condition-name], [edit logical-systems logical-system-name policy-options policy-statement policy-statement-name], [edit logical-systems logical-system-name policy-options prefix-list prefix-list-name], [edit policy-options as-path path-name], [edit policy-options as-path-group group-name], [edit policy-options community community-name], [edit policy-options condition condition-name], [edit policy-options policy-statement policy-statement-name], [edit policy-options prefix-list prefix-list-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define routing policies and policy objects that reference policies configured in the dynamic database at the [edit dynamic] hierarchy level. routing—To view this statement in the configuration. routing-control-level—To add this statement to the configuration. • Configuring Routing Policies Based on Dynamic Database Configuration 2817 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS family Syntax Hierarchy Level Release Information Description Options family family-name { filter filter-name { interface-specific; term term-name { from { match-conditions; } then { action; action-modifiers; } } } } [edit firewall] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a firewall filter for IP version 4 or IP version 6. family-name—Version or type of addressing protocol: • any—Filter packets based on protocol-independent match conditions. • ethernet-switching—Filter Layer 2 (Ethernet) packets and Layer 3 (IP) packets. • inet—Filter IPv4 packets. • inet6—Filter IPv6 packets. The remaining statements are explained separately. Required Privilege Level Related Documentation 2818 interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 Chapter 105: Configuration Statements for Firewall Filters filter Syntax Hierarchy Level Release Information Description Options filter filter-name { interface-specific; term term-name { from { match-conditions; } then { action; action-modifiers; } } } [edit firewall family family-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure firewall filters. filter-name—Name that identifies the filter. The name can contain letters, numbers, and hyphens (-), and can be up to 64 characters long. To include spaces in the name, enclose it in quotation marks. The remaining statements are explained separately. Required Privilege Level Related Documentation firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 2819 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS filter Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation filter (input | output) filter-name; [edit interfaces interface-name unit logical-unit-number family ethernet-switching], [edit interfaces interface-name unit logical-unit-number family inet], [edit interfaces interface-name unit logical-unit-number family inet6] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a firewall filter to traffic entering the port or Layer 3 interface or exiting the Layer 3 interface. All incoming traffic is accepted unmodified on the port or Layer 3 interface, and all outgoing traffic is sent unmodified from the port or Layer 3 interface. filter-name—Name of a firewall filter defined in the filter statement. • input—Apply a firewall filter to traffic entering the port or Layer 3 interface. • output—Apply a firewall filter to traffic exiting the Layer 3 interface. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 919 • Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 909 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 2820 Chapter 105: Configuration Statements for Firewall Filters filter Syntax Hierarchy Level Release Information Description Default Options Required Privilege Level Related Documentation filter (input | output) filter-name; [edit vlans vlan-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a firewall filter to traffic coming into or exiting from the VLAN. All incoming traffic is accepted unmodified to the VLAN, and all outgoing traffic is sent unmodified from the VLAN. filter-name —Name of a firewall filter defined in a filter statement. • input—Apply a firewall filter to VLAN ingress traffic. • output—Apply a firewall filter to VLAN egress traffic. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 filter-specific Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation filter-specific; [edit firewall policer policer-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a policer to act as a filter-specific policer. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 2821 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS firewall Syntax Hierarchy Level Release Information Description firewall { familyfamily-name { filter filter-name { interface-specific; term term-name { from { match-conditions; } then { action; action-modifiers; } } } } policerpolicer-name { filter-specific; if-exceeding { bandwidth-limit bps; burst-size-limit bytes; } then { policer-action; } } } [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure firewall filters and policers. The remaining statements are explained separately. Required Privilege Level Related Documentation 2822 firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Firewall Filters for J-EX Series Switches Overview on page 2721 Chapter 105: Configuration Statements for Firewall Filters from Syntax Hierarchy Level Release Information from { match-conditions; } [edit firewall family family-name filter filter-name term term-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Match packet fields to values specified in a match condition. If the from statement is not included in a firewall filter configuration, all packets are considered to match and the actions and action modifiers in the then statement are taken. Options match-conditions —Conditions that define the values or fields that the incoming or outgoing packets must contain for a match. You can specify one or more match conditions. If you specify more than one, they all must match for a match to occur and for the action in the then statement to be taken. Required Privilege Level Related Documentation firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Understanding Firewall Filter Match Conditions on page 2748 2823 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS if-exceeding Syntax Hierarchy Level Release Information Description if-exceeding { bandwidth-limit bps; bandwidth-percentpercent burst-size-limit bytes; } [edit firewall policer policer-name] [edit logical-systems logical-system-name firewall policer policer-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure policer rate limits. The bandwidth-percent statement is supported on routers only. The remaining statements are explained separately. Required Privilege Level Related Documentation 2824 firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 • Rate Limiting • Single-Rate Two-Color Policer Overview • Configuring a Single-Rate Two-Color Policer Chapter 105: Configuration Statements for Firewall Filters interface-specific Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation interface-specific; [edit firewall family family-name filter filter-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure interface-specific names for firewall counters. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 2825 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS policer Syntax Hierarchy Level Release Information Description Options policer policer-name { filter-specific; if-exceeding { bandwidth-limit bps; bandwidth-percent percent burst-size-limit bytes; } then { policer-action; } } [edit firewall] [edit logical-systems logical-system-name firewall] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure policer rate limits and actions. To activate a policer, you must include the policer action modifier in the then statement in a firewall filter term. Each policer that you configure includes an implicit counter. To ensure term-specific packet counts, you configure a policer for each term in the filter that requires policing. policer-name—Name that identifies the policer. The name can contain letters, numbers, hyphens (-), and can be up to 64 characters long. The remaining statements are explained separately. Required Privilege Level Related Documentation 2826 firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Combining CoS with MPLS on J-EX Series Switches on page 2883 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Understanding the Use of Policers in Firewall Filters on page 2752 • Single-Rate Two-Color Policer Overview • Configuring a Single-Rate Two-Color Policer Chapter 105: Configuration Statements for Firewall Filters policy-statement Syntax Hierarchy Level Release Information Description Options policy-statement policy-name { term term-name { from { family family-name; match-conditions; policy subroutine-policy-name; prefix-list prefix-list-name; prefix-list-filter prefix-list-name match-type ; route-filter destination-prefix match-type ; source-address-filter source-prefix match-type ; } to { match-conditions; policy subroutine-policy-name; } then actions; } } [edit dynamic policy-options], [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a routing policy, including subroutine policies. actions—(Optional) One or more actions to take if the conditions match. The actions are described in Configuring Flow Control Actions. family family-name—(Optional) Specify an address family protocol. Specify inet for IPv4. Specify inet6 for 128-bit IPv6, and to enable interpretation of IPv6 router filter addresses. For IS-IS traffic, specify iso. For IPv4 multicast VPN traffic, specify inet-mvpn. For IPv6 multicast VPN traffic, specify inet6-mvpn. For multicast-distribution-tree (MDT) IPv4 traffic, specify inet-mdt. NOTE: When family is not specified, the routing device uses the default IPv4 setting. from—(Optional) Match a route based on its source address. match-conditions—(Optional in from statement; required in to statement) One or more conditions to use to make a match. The qualifiers are described in Configuring Match Conditions in Routing Policy Terms. policy subroutine-policy-name—Use another policy as a match condition within this policy. The name identifying the subroutine policy can contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To include spaces in the name, enclose it 2827 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS in quotation marks (“ ”). For information about how to configure subroutines, see Configuring Subroutines in Routing Policy Match Conditions. policy-name—Name that identifies the policy. The name can contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To include spaces in the name, enclose it in quotation marks (“ ”). prefix-list prefix-list-name —Name of a list of IPv4 or IPv6 prefixes. prefix-list-filter prefix-list-name—Name of a prefix list to evaluate using qualifiers; match-type is the type of match (see Configuring Prefix List Filters), and actions is the action to take if the prefixes match. route-filter destination-prefix match-type —(Optional) List of routes on which to perform an immediate match; destination-prefix is the IPv4 or IPv6 route prefix to match, match-type is the type of match (see Configuring Route Lists), and actions is the action to take if the destination-prefix matches. source-address-filter source-prefix match-type —(Optional) Unicast source addresses in multiprotocol BGP (MBGP) and Multicast Source Discovery Protocol (MSDP) environments on which to perform an immediate match. source-prefix is the IPv4 or IPv6 route prefix to match, match-type is the type of match (see Configuring Route Lists), and actions is the action to take if the source-prefix matches. term term-name—Name that identifies the term. to—(Optional) Match a route based on its destination address or the protocols into which the route is being advertised. then—(Optional) Actions to take on matching routes. The actions are described in Configuring Flow Control Actions and Configuring Actions That Manipulate Route Characteristics. Required Privilege Level Related Documentation 2828 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Defining Routing Policies • Configuring Routing Policies and Policy Objects in the Dynamic Database • dynamic-db on page 2817 Chapter 105: Configuration Statements for Firewall Filters prefix-list Syntax Hierarchy Level Release Information Description Options prefix-list name { ip-addresses; apply-path path; } [edit dynamic policy-options], [edit logical-systems logical-system-name policy-options], [edit policy-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Support for the vpls protocol family introduced in Junos OS Release 10.2 for J-EX Series switches. Define a list of IPv4 or IPv6 address prefixes for use in a routing policy statement or firewall filter statement. name—Name that identifies the list of IPv4or IPv6 address prefixes. ip-addresses—List of IPv4 or IPv6 address prefixes, one IP address per line in the configuration. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Prefix Lists for Use in Routing Policy Match Conditions • Configuring Routing Policies and Policy Objects in the Dynamic Database • dynamic-db on page 2817 2829 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS routing-instance Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2830 routing-instance routing-instance-name; [edit firewall family inet filter filter-name term term-name then] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a specific virtual routing instance to which the switch sends matched packets. routing-instance-name —Name of a virtual routing instance. firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Example: Configuring Filter-Based Forwarding on J-EX Series Switches on page 2773 • Configuring Virtual Routing Instances (CLI Procedure) on page 1142 • Understanding Filter-Based Forwarding for J-EX Series Switches on page 2753 Chapter 105: Configuration Statements for Firewall Filters term Syntax Hierarchy Level Release Information Description Options term term-name { from { match-conditions; } then { action; action-modifiers; } } [edit firewall family family-name filter filter-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define a firewall filter term. term-name —Name that identifies the term. The name can contain letters, numbers, and hyphens (-), and can be up to 64 characters long. To include spaces in the name, enclose it in quotation marks. The remaining statements are explained separately. Required Privilege Level Related Documentation firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Firewall Filters for J-EX Series Switches Overview on page 2721 2831 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS then Syntax Hierarchy Level Release Information Description Options then { action; action-modifiers; } [edit firewall family family-name filter filter-name term term-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a filter action. action—Actions to accept, discard, or forward packets that match all match conditions specified in a filter term. action-modifiers—Additional actions to analyze, classify, count, or police packets that match all conditions specified in a filter term. Required Privilege Level Related Documentation 2832 firewall—To view this statement in the configuration. firewall-control—To add this statement to the configuration. • Firewall Filter Match Conditions and Actions for J-EX Series Switches on page 2728 • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device on J-EX Series Switches on page 2773 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Understanding Firewall Filter Match Conditions on page 2748 Chapter 105: Configuration Statements for Firewall Filters then Syntax Hierarchy Level Release Information Description Options then { policer-action; } [edit firewall policer policer-name] [edit logical-systems logical-system-name firewall policer policer-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a policer action. policer-action—Actions to take are: • discard—Discard traffic that exceeds the rate limits defined by the policer. • forwarding-class class-name—For routers only, classify traffic that exceeds the rate limits defined by the policer. • loss-priority—Set the loss priority for traffic that exceeds the rate limits defined by the policer. Required Privilege Level Related Documentation firewall—To view this statement in the configuration. firewall -control—To add this statement to the configuration. • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Configuring Firewall Filters (CLI Procedure) on page 2779 • Configuring Firewall Filters (J-Web Procedure) on page 2784 • Understanding the Use of Policers in Firewall Filters on page 2752 • Example: Configuring CoS for a PBB Network on MX Series Routers • Single-Rate Two-Color Policer Overview • Configuring a Single-Rate Two-Color Policer 2833 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2834 CHAPTER 106 Operational Mode Commands for Firewall Filters 2835 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear firewall Syntax Syntax (J-EX Series Switch) Release Information Description clear firewall (all | counter counter-name | filter filter-name | logical-system logical-system-name) clear firewall (all | counter counter-name | filter filter-name) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear statistics about configured firewall filters. NOTE: The clear firewall command cannot be used to clear the Routing Engine filter counters on a backup Routing Engine that is enabled for GRES. Options all—Clear the packet and byte counts for all filters. counter counter-name—Clear the packet and byte counts for a filter counter that has been configured with the counter firewall filter action. filter filter-name—Clear the packet and byte counts for the specified firewall filter. logical-system logical-system-name—Clear the packet and byte counts for the specified logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear firewall all 2836 clear • show firewall on page 2838 clear firewall all on page 2836 When you enter this command, you are provided feedback on the status of your request. user@host> clear firewall all Chapter 106: Operational Mode Commands for Firewall Filters clear firewall Syntax Release Information Description Options clear firewall Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear statistics about configured firewall filters. none—Clear the packet and byte counts for all firewall filter counters and clear the packet counts for all policer counters. all—(Optional) Clear the packet and byte counts for all firewall filter counters and clear the packet counts for all policer counters. counter counter-name —(Optional) Clear the packet and byte counts for the specified firewall filter counter. filter filter-name —(Optional) Clear the packet and byte counts for the specified firewall filter. Required Privilege Level Related Documentation clear firewall (all) clear firewall (counter counter-name) clear firewall (filter filter-name) clear • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 • Verifying That Policers Are Operational on page 2800 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding the Use of Policers in Firewall Filters on page 2752 user@host> clear firewall all user@host> clear firewall counter port-filter-counter user@host> clear firewall filter ingress-port-filter 2837 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show firewall Syntax Syntax (J-EX Series Switch) Release Information Description Options show firewall show firewall Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display statistics about configured firewall filters. none—(Optional) Display statistics about configured firewall filters. filter filter-name—(Optional) Name of a configured filter. counter counter-name—(Optional) Name of a filter counter. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular system. log—(Optional) Display log entries for firewall filters. terse—(Optional) Display firewall filter names only. Required Privilege Level Related Documentation List of Sample Output Output Fields 2838 view • clear firewall on page 2836 show firewall filter on page 2840 show firewall filter (Dynamic Input Filter) on page 2840 show firewall (Logical Systems) on page 2840 Table 350 on page 2839 lists the output fields for the show firewall command. Output fields are listed in the approximate order in which they appear. Chapter 106: Operational Mode Commands for Firewall Filters Table 350: show firewall Output Fields Field Name Field Description Filter Name of a filter that has been configured with the filter statement at the [edit firewall] hierarchy level. When an interface-specific filter is displayed, the name of the filter is followed by the full interface name and by either -i for an input filter or -o for an output filter. When dynamic filters are displayed, the name of the filter is followed by the full interface name and by either -in for an input filter or -out for an output filter. When a logical system–specific filter is displayed, the name of the filter is prefixed with two underscore (__) characters and the name of the logical system (for example, __ls1/filter1). Counters Policers Display filter counter information: • Name—Name of a filter counter that has been configured with the counter firewall filter action. • Bytes—Number of bytes that match the filter term under which the counter action is specified. • Packets—Number of packets that matched the filter term under which the counter action is specified. Display policer information: • Name—Name of policer. • Packets—Number of packets that matched the filter term under which the policer action is specified. This is only the number of out-of-specification (out-of-spec) packet counts, not all packets policed by the policer. 2839 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show firewall filter show firewall filter (Dynamic Input Filter) show firewall (Logical Systems) user@host> show firewall filter test Filter: test Counters: Name Counter-1 Counter-2 Policers: Name Policer-1 user@host> show firewall filter dfwd-ge-5/0/0.1-in Filter: dfwd-ge-5/0/0.1-in Counters: Name c1-ge-5/0/0.1-in Packets 0 0 Packets 0 Bytes 0 Packets 0 Bytes 420 Packets 5 Bytes 0 0 Packets 0 0 Bytes 0 0 Packets 0 0 Bytes 0 0 Packets 0 0 user@host>show firewall Filter: __lr1/test Counters: Name icmp Filter: __default_bpdu_filter__ Filter: __lr1/inet_filter1 Counters: Name inet_tcp_count inet_udp_count Filter: __lr1/inet_filter2 Counters: Name inet_icmp_count inet_pim_count Filter: __lr2/inet_filter1 Counters: Name inet_tcp_count inet_udp_count 2840 Bytes 0 0 Chapter 106: Operational Mode Commands for Firewall Filters show firewall Syntax Release Information Description Options show firewall log (detail | interface interface-name) terse Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display statistics about configured firewall filters. none—Display statistics about all configured firewall filters, counters, and policers. counter counter-name—(Optional) Display statistics about a particular firewall filter counter. filter filter-name—(Optional) Display statistics about a particular firewall filter. log (detail | interface interface-name)—(Optional) Display detailed log entries of firewall activity or log information about a specific interface. terse—(Optional) Display firewall filter names only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 • Verifying That Policers Are Operational on page 2800 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding the Use of Policers in Firewall Filters on page 2752 show firewall on page 2842 show firewall (filter filter-name) on page 2842 show firewall (counter counter-name) on page 2842 show firewall log on page 2842 Table 351 on page 2841 lists the output fields for the show firewall command. Output fields are listed in the approximate order in which they appear. Table 351: show firewall Output Fields Field Name Field Description Level of Output Filter Name of the filter that is configured with the filter statement at the [edit firewall] hierarchy level. All levels 2841 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 351: show firewall Output Fields (continued) Field Name Field Description Level of Output Counters Display filter counter information: All levels Policers • Name—Name of a filter counter that has been configured with the counter firewall filter action • Bytes—Number of bytes that match the filter term where the counter action was specified. • Packets—Number of packets that matched the filter term where the counter action was specified. Display policer information: • Name—Name of policer. • Packets—Number of packets that matched the filter term where the policer action was specified. This is the number of packets that exceed the rate limits that the policer specifies. show firewall show firewall (filter filter-name) show firewall (counter counter-name) show firewall log user@host> show firewall Filter: egress-vlan-filter Counters: Name employee-web-counter Filter: ingress-port-filter Counters: Name ingress-port-counter Filter: ingress-port-voip-class-filter Counters: Name icmp-counter Policers: Name icmp-connection-policer tcp-connection-policer Bytes 0 Packets 0 Bytes 0 Packets 0 Bytes 0 Packets 0 Packets 0 0 user@host> show firewall filter egress-vlan-filter Filter: egress-vlan-filter Counters: Name employee-web-counter Bytes 0 Packets 0 user@host> show firewall counter icmp-counter Filter: ingress-port-voip-class-filter Counters: Name icmp-counter Bytes 0 Packets 0 user@host> show firewall log Log : Time Filter Action Interface Dest Addr 08:00:53 pfe R ge-1/0/1.0 192.168.3.4 2842 All levels Protocol Src Addr ICMP 192.168.3.5 Chapter 106: Operational Mode Commands for Firewall Filters 08:00:52 08:00:51 08:00:50 08:00:49 08:00:48 08:00:47 pfe R 192.168.3.4 pfe R 192.168.3.4 pfe R 192.168.3.4 pfe R 192.168.3.4 pfe R 192.168.3.4 pfe R 192.168.3.4 ge-1/0/1.0 ICMP 192.168.3.5 ge-1/0/1.0 ICMP 192.168.3.5 ge-1/0/1.0 ICMP 192.168.3.5 ge-1/0/1.0 ICMP 192.168.3.5 ge-1/0/1.0 ICMP 192.168.3.5 ge-1/0/1.0 ICMP 192.168.3.5 2843 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show firewall log Syntax Syntax (J-EX Series Switch) Release Information Description Options show firewall log show firewall log Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display log information about firewall filters. none—Display log information about firewall filters. detail—(Optional) Display detailed information. interface interface-name—(Optional) Display log information about a specific interface. logical-system (logical-system-name | all)—(Optional) Perform this operation on all logical systems or on a particular system. Required Privilege Level List of Sample Output Output Fields view show firewall log on page 2845 show firewall log detail on page 2845 Table 352 on page 2844 lists the output fields for the show firewall log command. Output fields are listed in the approximate order in which they appear. Table 352: show firewall log Output Fields 2844 Field Name Field Description Time of Log Time that the event occurred. Filter Name of a filter that has been configured with the filter statement at the [edit firewall] hierarchy level. • A hyphen (-) indicates that the packet was handled by the Packet Forwarding Engine. • A space (no hyphen) indicates the packet was handled by the Routing Engine. • The notation pfe indicates packets logged by the Packet Forwarding Engine hardware filters. Chapter 106: Operational Mode Commands for Firewall Filters Table 352: show firewall log Output Fields (continued) show firewall log show firewall log detail Field Name Field Description Filter Action Filter action: • A—Accept • D—Discard • R—Reject Name of Interface Ingress interface for the packet. Name of protocol Packet’s protocol name: egp, gre, icmp, ipip, ospf, pim, rsvp, tcp, or udp. Packet length Length of the packet. Source address Packet’s source address. Destination address Packet’s destination address and port. user@host>show firewall log Time Filter Action Interface Protocol Src Addr Dest Addr 13:10:12 pfe D rlsq0.902 ICMP 180.1.177.2 180.1.177.1 13:10:11 pfe D rlsq0.902 ICMP 180.1.177.2 180.1.177.1 user@host> show firewall log detail Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of interface: fxp0.0Name of protocol: TCP, Packet Length: 50824, Source address: 172.17.22.108:829, Destination address: 192.168.70.66:513 Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of interface: fxp0.0 Name of protocol: TCP, Packet Length: 1020, Source address: 172.17.22.108:829, Destination address: 192.168.70.66:513 Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of interface: fxp0.0 Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829, Destination address: 192.168.70.66:513 Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of interface: fxp0.0 Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829, Destination address: 192.168.70.66:513 Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of interface: fxp0.0 Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829, Destination address: 192.168.70.66:513 Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of interface: fxp0.0 Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829, Destination address: 192.168.70.66:513 .... 2845 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show interfaces filters Syntax Release Information Description Options show interfaces filters Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display firewall filters that are configured on each interface in a system. none—Display firewall filter information about all interfaces. interface-name—(Optional) Display firewall filter information about a particular interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show interfaces policers on page 2848 • show firewall on page 2841 show interfaces filters on page 2846 show interfaces filters on page 2847 Table 353 on page 2846 lists the output fields for the show interfaces filters command. Output fields are listed in the approximate order in which they appear. Table 353: show interfaces filters Output Fields Field Name Field Description Level of Output Interface Name of the physical interface. All levels Admin Interface state: up or down. All levels Link Link state: up or down. All levels Proto Protocol that is configured on the interface. All levels Input Filter Name of the firewall filter to be evaluated when packers are received on the interface. All levels Output Filter Name of the firewall filter to be evaluated when packets are transmitted on the interface. All levels show interfaces filters 2846 user@host> show interfaces filters Interface Admin Link Proto Input Filter ge-0/0/0 up down ge-0/0/0.0 up down eth-switch unknown ge-0/0/1 up down ge-0/0/1.0 up down eth-switch unknown ge-0/0/2 up down ge-0/0/3 up down Output Filter Chapter 106: Operational Mode Commands for Firewall Filters ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 ge-0/0/8 ge-0/0/9 ge-0/0/10 ge-0/0/10.0 show interfaces filters up up up up up up up up down down down down down down down down user@host> show interfaces filters ge-0/0/0 Interface Admin Link Proto Input Filter ge-0/0/0 up down ge-0/0/0.0 up down eth-switch unknown Output Filter 2847 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show interfaces policers Syntax Release Information Description Options show interfaces policers Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display all policers that are configured on each interface in a system. none—Display policer information about all interfaces. interface-name—(Optional) display firewall filters information about a particular interface. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show interfaces filters on page 2846 • show policer on page 2850 show interfaces policers on page 2848 show interfaces policers on page 2849 show interfaces policers ( interface-name) on page 2849 Table 354 on page 2848 lists the output fields for the show interfaces policers command. Output fields are listed in the approximate order in which they appear. Table 354: show interfaces policers Output Fields Field Name Field Description Level of Output Interface Name of the interface. All levels Admin Interface state: up or down. All levels Link Link state: up or down. All levels Proto Protocol configured on the interface. All levels Input Policer Policer to be evaluated when packets are received on the interface. It has the format interface-name-in-policer. All levels Output Policer Policer to be evaluated when packets are transmitted on the interface. It has the format interface-name-out-policer. All levels show interfaces policers user@host> show interfaces policers Interface Admin Link Proto Input Policer ge-0/0/0 up down ge-0/0/0.0 up down eth-switch Interface 2848 Admin Link Proto Input Policer Output Policer Output Policer Chapter 106: Operational Mode Commands for Firewall Filters show interfaces policers ge-0/0/1 ge-0/0/1.0 up up down down Interface ge-0/0/2 ge-0/0/3 ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 ge-0/0/8 ge-0/0/9 ge-0/0/10 ge-0/0/10.0 Admin up up up up up up up up up up eth-switch Link Proto Input Policer down down down down down down down down down down eth-switch user@host> show interfaces policers Interface Admin Link Proto Input Policer ge-0/0/0 up down ge-0/0/0.0 up down eth-switch Interface ge-0/0/1 ge-0/0/1.0 Interface ge-0/0/2 ge-0/0/3 ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 ge-0/0/8 ge-0/0/9 ge-0/0/10 ge-0/0/10.0 show interfaces policers ( interface-name) Admin Link Proto Input Policer up down up down eth-switch Admin Link Proto Input Policer up down up down up down up down up down up down up down up down up down up down eth-switch user@host> show interfaces policers ge-0/0/1 Interface Admin Link Proto Input Policer ge-0/0/0 up down ge-0/0/0.0 up down eth-switch Output Policer Output Policer Output Policer Output Policer Output Policer 2849 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show policer Syntax Release Information Description Options show policer Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display statistics about configured policers. none—Display the count of policed packets for all configured policers in the system. policer-name—(Optional) Display the count of policed packets for the specified policer. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on J-EX Series Switches on page 2755 • Verifying That Firewall Filters Are Operational on page 2799 • Verifying That Policers Are Operational on page 2800 • Firewall Filters for J-EX Series Switches Overview on page 2721 • Understanding the Use of Policers in Firewall Filters on page 2752 show policer on page 2850 show policer (policer-name) on page 2851 Table 355 on page 2850 lists the output fields for the show policer command. Output fields are listed in the approximate order in which they appear. Table 355: show policer Output Fields Field Name Field Description Level of Output Filter Name of filter that is configured with the filter statement at the [edit firewall] hierarchy level. All levels Policers Display policer information: All levels • Filter—Name of filter that specifies the policer action. • Name—Name of policer. • Packets—Number of packets that matched the filter term where the policer action is specified. This is the number of packets that exceed the rate limits that the policer specifies. show policer 2850 user@host> show policer Filter: egress-vlan-filter Filter: ingress-port-filter Policers: Name Packets Chapter 106: Operational Mode Commands for Firewall Filters icmp-connection-policer tcp-connection-policer Filter: ingress-vlan-rogue-block show policer (policer-name) user@host> show policer tcp-connection-policer Filter: ingress-port-filter Policers: Name tcp-connection-policer 0 0 Packets 0 2851 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show policy Syntax Syntax (J-EX Series Switch) Release Information Description Options show policy show policy Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about configured routing policies. none—List the names of all configured routing policies. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. policy-name—(Optional) Show the contents of the specified policy. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show policy damping on page 1886 show policy on page 2852 show policy policy-name on page 2853 show policy (Multicast Scoping) on page 2853 Table 356 on page 2852 lists the output fields for the show policy command. Output fields are listed in the approximate order in which they appear. Table 356: show policy Output Fields show policy 2852 Field Name Field Description policy-name Name of the policy listed. term Policy term listed. from Match condition for the policy. then Action for the policy. user@host> show policy Configured policies: __vrf-export-red-internal__ __vrf-import-red-internal__ Chapter 106: Operational Mode Commands for Firewall Filters red-export all_routes show policy policy-name user@host> show policy test-statics Policy test-statics: from 3.0.0.0/8 accept 3.1.0.0/16 accept then reject show policy (Multicast Scoping) user@host> show policy test-statics Policy test-statics: from multicast-scoping == 8 2853 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show policy conditions Syntax Syntax (J-EX Series Switch) Release Information Description Options show policy conditions show policy conditions Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display all the configured conditions as well as the routing tables with which the configuration manager is interacting. If the detail keyword is included, the output also displays dependent routes for each condition. none—Display all configured conditions and associated routing tables. condition-name—(Optional) Display information about the specified condition only. detail—(Optional) Display the specified level of output. dynamic—(Optional) Display information about the conditions in the dynamic database. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show policy conditions detail on page 2855 Table 357 on page 2854 lists the output fields for the show policy conditions command. Output fields are listed in the approximate order in which they appear. Table 357: show policy conditions Output Fields Field Name Field Description Level of Output Condition Name of configured condition. All levels event Condition type. If the if-route-exists option is configured, the event type is: Existence of a route in a specific routing table. All levels Dependent routes List of routes dependent on the condition, along with the latest generation number. detail Condition tables List of routing tables associated with the condition, along with the latest generation number and number of dependencies. All levels 2854 Chapter 106: Operational Mode Commands for Firewall Filters Table 357: show policy conditions Output Fields (continued) Field Name Field Description Level of Output If-route-exists conditions List of conditions configured to look for a route in the specified table. All levels show policy conditions detail user@host> show policy conditions detail Configured conditions: Condition cond1, event: Existence of a route in a specific routing table Dependent routes: 4.4.4.4/32, generation 3 6.6.6.6/32, generation 3 10.10.10.10/32, generation 3 Condition cond2, event: Existence of a route in a specific routing table Dependent routes: None Condition tables: Table inet.0, generation 4, dependencies 3, If–route-exists conditions: cond1 cond2 2855 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS test policy Syntax Release Information Description Options test policy policy-name prefix Command introduced before Junos OS Release 10.2 for J-EX Series switches. Test a policy configuration to determine which prefixes match routes in the routing table. policy-name—Name of a policy. prefix—Destination prefix to match. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields test policy All prefixes in the default unicast routing table (inet.0) that match prefixes that are the same as or longer than the specific prefix are processed by the from clause in the specified policy. All prefixes accepted by the policy are displayed. The test policy command evaluates a policy differently from the Border Gateway Protocol (BGP) import process. When testing a policy that contains an interface match condition in the from clause, the test policy command uses the match condition. In contrast, BGP does not use the interface match condition when evaluating the policy against routes learned from internal BGP (IBGP) or external BGP (EGBP) multihop peers. view • show policy damping on page 1886 test policy on page 2856 For information about output fields, see the output field tables for the show route command, the show route detail command, the show route extensive command, or the show route terse command. user@host> test policy test-statics 3.0.0.1/8 inet.0: 44 destinations, 44 routes (44 active, 0 holddown, 0 hidden) Prefixes passing policy: 3.0.0.0/8 *[BGP/170] 16:22:46, localpref 100, from 10.255.255.41 AS Path: 50888 I > to 10.11.4.32 via en0.2, label-switched-path l2 3.3.3.1/32 *[IS-IS/18] 2d 00:21:46, metric 0, tag 2 > to 10.0.4.7 via fxp0.0 3.3.3.2/32 *[IS-IS/18] 2d 00:21:46, metric 0, tag 2 > to 10.0.4.7 via fxp0.0 3.3.3.3/32 *[IS-IS/18] 2d 00:21:46, metric 0, tag 2 > to 10.0.4.7 via fxp0.0 3.3.3.4/32 *[IS-IS/18] 2d 00:21:46, metric 0, tag 2 > to 10.0.4.7 via fxp0.0 Policy test-statics: 5 prefixes accepted, 0 prefixes rejected 2856 PART 21 Class of Service • Class of Service (CoS)—Overview on page 2859 • Examples: CoS Configuration on page 2883 • Configuring CoS on page 2911 • Verifying CoS Configuration on page 2935 • Configuration Statements for CoS on page 2943 • Operational Mode Commands for CoS on page 2977 2857 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2858 CHAPTER 107 Class of Service (CoS)—Overview • Junos OS CoS for J-EX Series Switches Overview on page 2860 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Understanding CoS Code-Point Aliases on page 2864 • Understanding CoS Classifiers on page 2867 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Tail Drop Profiles on page 2872 • Understanding CoS Schedulers on page 2873 • Understanding CoS Two-Color Marking on page 2876 • Understanding CoS Rewrite Rules on page 2876 • Understanding Port Shaping and Queue Shaping for CoS on J-EX Series Switches on page 2878 • Understanding Junos OS EZQoS for CoS Configurations on J-EX Series Switches on page 2879 • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 2859 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Junos OS CoS for J-EX Series Switches Overview When a network experiences congestion and delay, some packets must be dropped. Junos OS class of service (CoS) divides traffic into classes to which you can apply different levels of throughput and packet loss when congestion occurs. This allows packet loss to happen according to rules that you configure. For interfaces that carry IPv4, IPv6, and MPLS traffic, you can configure Junos OS CoS features to provide multiple classes of service for different applications. CoS also allows you to rewrite the Differentiated Services code point (DSCP), IP precedence, 802.1p, or EXP CoS bits of packets egressing out of an interface, thus allowing you to tailor packets for the remote peers’ network requirements. See “Understanding Using CoS with MPLS Networks on J-EX Series Switches” on page 2880 for more information about CoS for MPLS networks. CoS provides multiple classes of service for different applications. You can configure multiple forwarding classes for transmitting packets, define which packets are placed into each output queue, and schedule the transmission service level for each queue. In designing CoS applications, you must give careful consideration to your service needs and thoroughly plan and design your CoS configuration to ensure consistency and interoperability across all platforms in a CoS domain. Because J-EX Series Switches implement CoS in hardware rather than in software, you can experiment with and deploy CoS features without affecting packet-forwarding and switching performance. NOTE: CoS policies can be enabled or disabled on each interface of a J-EX Series switch. Also, each physical and logical interface on the switch can have custom CoS rules associated with it. When CoS is used in an MPLS network, there are some additional restrictions. See “Understanding Using CoS with MPLS Networks on J-EX Series Switches” on page 2880. • How Junos OS CoS Works on page 2860 • Default CoS Behavior on J-EX Series Switches on page 2861 How Junos OS CoS Works Junos OS CoS works by examining traffic entering at the edge of your network. The switches classify traffic into defined service groups to provide the special treatment of traffic across the network. For example, voice traffic can be sent across certain links, and data traffic can use other links. In addition, the data traffic streams can be serviced differently along the network path. As the traffic leaves the network at the far edge, you can rewrite the traffic to meet the policies of the targeted peer. To support CoS, you must configure each switch in the network. Generally, each switch examines the packets that enter it to determine their CoS settings. These settings then dictate which packets are transmitted first to the next downstream switch. Switches at 2860 Chapter 107: Class of Service (CoS)—Overview the edges of the network might be required to alter the CoS settings of the packets that enter the network to classify the packets into the appropriate service groups. Figure 79 on page 2861 represents the network scenario of an enterprise. Switch A is receiving traffic from various network nodes such as desktop computers, servers, surveillance cameras, and VoIP telephones. As each packet enters, Switch A examines the packet’s CoS settings and classifies the traffic into one of the groupings defined by the enterprise. This definition allows Switch A to prioritize resources for servicing the traffic streams it receives. Switch A might alter the CoS settings of the packets to better match the enterprise’s traffic groups. When Switch B receives the packets, it examines the CoS settings, determines the appropriate traffic groups, and processes the packets according to those settings. It then transmits the packets to Switch C, which performs the same actions. Switch D also examines the packets and determines the appropriate groups. Because Switch D sits at the far end of the network, it can rewrite the CoS bits of the packets before transmitting them. Figure 79: Packet Flow Across the Network Default CoS Behavior on J-EX Series Switches If you do not configure any CoS settings on the switch, the software performs some CoS functions to ensure that user traffic and protocol packets are forwarded with minimum delay when the network is experiencing congestion. Some CoS settings, such as classifiers, are automatically applied to each logical interface that you configure. Other settings, such as rewrite rules, are applied only if you explicitly associate them with an interface. Related Documentation • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Understanding Junos OS EZQoS for CoS Configurations on J-EX Series Switches on page 2879 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Example: Combining CoS with MPLS on J-EX Series Switches on page 2898 2861 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Junos OS CoS Components for J-EX Series Switches This topic describes the Junos OS class-of-service (CoS) components for J-EX Series Switches: • Code-Point Aliases on page 2862 • Policers on page 2862 • Classifiers on page 2862 • Forwarding Classes on page 2863 • Tail Drop Profiles on page 2863 • Schedulers on page 2863 • Rewrite Rules on page 2863 Code-Point Aliases A code-point alias assigns a name to a pattern of code-point bits. You can use this name instead of the bit pattern when you configure other CoS components such as classifiers, drop-profile maps, and rewrite rules. Policers Policers limit traffic of a certain class to a specified bandwidth and burst size. Packets exceeding the policer limits can be discarded. You define policers with filters that can be associated with input interfaces. For more information about policers, see “Understanding the Use of Policers in Firewall Filters” on page 2752. NOTE: You can configure policers to discard packets that exceed the rate limits. If you want to configure CoS parameters such as loss-priority and forwarding-class, you must use firewall filters. Classifiers Packet classification associates incoming packets with a particular CoS servicing level. In the Junos OS, classifiers associate packets with a forwarding class and loss priority and assign packets to output queues based on the associated forwarding class. Junos OS supports two general types of classifiers: 2862 • Behavior aggregate or CoS value traffic classifiers—Examines the CoS value in the packet header. The value in this single field determines the CoS settings applied to the packet. BA classifiers allow you to set the forwarding class and loss priority of a packet based on the Differentiated Services code point (DSCP) value, IP precedence value, and IEEE 802.1p value. • Multifield traffic classifiers—Examines multiple fields in the packet such as source and destination addresses and source and destination port numbers of the packet. With Chapter 107: Class of Service (CoS)—Overview multifield classifiers, you set the forwarding class and loss priority of a packet based on firewall filter rules. Forwarding Classes Forwarding classes group the packets for transmission. Based on forwarding classes, you assign packets to output queues. Forwarding classes affect the forwarding, scheduling, and marking policies applied to packets as they transit a switch. By default, four categories of forwarding classes are defined: best effort, assured forwarding, expedited forwarding, and network control. For J-EX Series switches, 16 forwarding classes are supported, providing granular classification capability. Tail Drop Profiles Drop profile is a mechanism that defines parameters that allow packets to be dropped from the network. Drop profiles define the meanings of the loss priorities. When you configure drop profiles you are essentially setting the value for queue fullness. The queue fullness represents a percentage of the queue used to store packets in relation to the total amount that has been allocated for that specific queue. Loss priorities set the priority of dropping a packet. Loss priority affects the scheduling of a packet without affecting the packet’s relative ordering. You can use the loss priority setting to identify packets that have experienced congestion. Typically you mark packets exceeding some service level with a high loss priority. Schedulers Each switch interface has multiple queues assigned to store packets. The switch determines which queue to service based on a particular method of scheduling. This process often involves determining which type of packet should be transmitted before another. You can define the priority, bandwidth, delay buffer size, and tail drop profiles to be applied to a particular queue for packet transmission. A scheduler map associates a specified forwarding class with a scheduler configuration. You can associate up to four user-defined scheduler maps with the interfaces. Rewrite Rules A rewrite rule sets the appropriate CoS bits in the outgoing packet, thus allowing the next downstream device to classify the packet into the appropriate service group. Rewriting, or marking, outbound packets is useful when the switch is at the border of a network and must alter the CoS values to meet the policies of the targeted peer. NOTE: Rewrite rules are applied when the packets are routed. Rewrite rules are not applied when the packets are forwarded. Egress firewall filters can also assign forwarding class and loss priority so that the packets are rewritten based on forwarding class and loss priority. 2863 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Understanding CoS Code-Point Aliases on page 2864 • Understanding CoS Classifiers on page 2867 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Tail Drop Profiles on page 2872 • Understanding CoS Schedulers on page 2873 • Understanding CoS Two-Color Marking on page 2876 • Understanding CoS Rewrite Rules on page 2876 • Example: Configuring CoS on J-EX Series Switches on page 2883 Understanding CoS Code-Point Aliases A code-point alias assigns a name to a pattern of code-point bits. You can use this name instead of the bit pattern when you configure other CoS components such as classifiers, drop-profile maps, and rewrite rules. Behavior aggregate classifiers use class-of-service (CoS) values such as Differentiated Services code points (DSCPs), IP precedence, and IEEE 802.1 bits to associate incoming packets with a particular CoS servicing level. On a switch, you can assign a meaningful name or alias to the CoS values and use this alias instead of bits when configuring CoS components. These aliases are not part of the specifications but are well known through usage. For example, the alias for DSCP 101110 is widely accepted as ef (expedited forwarding). When you configure classes and define classifiers, you can refer to the markers by alias names. You can configure user-defined classifiers in terms of alias names. If the value of an alias changes, it alters the behavior of any classifier that references it. You can configure code-point aliases for the following type of CoS markers: • dscp—Handles incoming IPv4 packets. • ieee-802.1—Handles Layer 2 CoS. • inet-precedence—Handles incoming IPv4 packets. IP precedence mapping requires only the upper three bits of the DSCP field. This topic covers: • Default Code-Point Aliases on page 2864 Default Code-Point Aliases Table 358 on page 2865 shows the default mappings between the bit values and standard aliases. 2864 Chapter 107: Class of Service (CoS)—Overview Table 358: Default Code-Point Aliases CoS Value Types Mapping DSCP CoS Values ef 101110 af11 001010 af12 001100 af13 001110 af21 010010 af22 010100 af23 010110 af31 011010 af32 011100 af33 011110 af41 100010 af42 100100 af43 100110 be 000000 cs1 001000 cs2 010000 cs3 011000 cs4 100000 cs5 101000 nc1/cs6 110000 nc2/cs7 111000 IEEE 802.1p CoS Values be 000 2865 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 358: Default Code-Point Aliases (continued) CoS Value Types Mapping be1 001 ef 100 ef1 101 af11 010 af12 011 nc1/cs6 110 nc2/cs7 111 Legacy IP Precedence CoS Values be 000 be1 001 ef 010 ef1 011 af11 100 af12 101 nc1/cs6 110 nc2/cs7 111 Related Documentation 2866 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 • Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 Chapter 107: Class of Service (CoS)—Overview Understanding CoS Classifiers Packet classification associates incoming packets with a particular class-of-service (CoS) servicing level. Classifiers associate packets with a forwarding class and loss priority and assign packets to output queues based on the associated forwarding class. There are two general types of classifiers: • Behavior aggregate (BA) classifiers • Multifield (MF) classifiers You can configure both a BA classifier and an MF classifier on an interface. If you do this, the BA classification is performed first and then the MF classification. If the two classification results conflict, the MF classification result overrides the BA classification result. NOTE: When a source media access control (MAC) address is learned, the frame that contains the source MAC address is always sent out on queue 0 while egressing from the network interface, irrespective of the classifier applied to the ingress interface. On J-EX8200 Ethernet Switches, you can specify BA classifiers for bridged multidestination traffic and IP multidestination traffic. The BA classifier for multicast packets is applied to all interfaces on the J-EX8200 switch. This topic describes: • Behavior Aggregate Classifiers on page 2867 • Multifield Classifiers on page 2869 Behavior Aggregate Classifiers The behavior aggregate classifier maps a CoS value to a forwarding class and loss priority. The forwarding class determines the output queue. The loss priority is used by a scheduler to control packet discard during periods of congestion. There are three types of BA classifiers: • Differentiated Services Code Point (DSCP) for IP DiffServ • IP precedence bits • IEEE 802.1p CoS bits BA classifiers are based on fixed-length fields, which makes them computationally more efficient than MF classifiers. Therefore core devices, which handle high traffic volumes, are normally configured to perform BA classification. 2867 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Default Behavior Aggregate Classification The Junos OS automatically assigns implicit default classifiers to all logical interfaces based on the type of interface. Table 359 on page 2868 lists different types of interfaces and the corresponding implicit default classifiers. Table 359: Default BA Classification Type of Interface Default BA Classification Trunk interface ieee8021p-default Layer 3 interface (IPv4) dscp-default Layer 3 interface (IPv6) dscp-ipv6-default Access interface Untrusted Routed VLAN interface (RVI) No default classification When you explicitly associate a classifier with a logical interface, you are in effect overriding the implicit default classifier with an explicit classifier. On J-EX4200 switches, you can apply classifier rules for each interface. Table 360 on page 2868 describes the different classifier types you can configure on Layer 2 and Layer 3 interfaces. Table 360: Allowed BA Classification Type of Interface Allowed BA Classification Layer 2 interface IEEE 802.1p, IP Precedence, DSCP, DSCP IPv6 Layer 3 interface (IPv4) IEEE 802.1p, IP Precedence, DSCP Layer 3 interface (IPv6) IEEE 802.1p, IP Precedence, DSCP IPv6 You can configure all the allowed classifier types on the same logical interface or on different logical interfaces. If you need to apply all classifier rules on the same logical interface, configure the classifier rules allowed for both IPv4 and IPv6 on the logical interface. If you have not explicitly associated a classifier with a logical interface, the default classifiers are assigned and classification works as follows: 2868 • If the logical interface is configured with an IPv4 address, DSCP classifier is assigned by default, and IPv4 and IPv6 packets are classified using the DSCP classifier. • If the logical interface is configured with an IPv6 address, DSCP IPv6 classifier is assigned by default, and IPv4 and IPv6 packets are classified using the DSCP IPv6 classifier. Chapter 107: Class of Service (CoS)—Overview NOTE: On J-EX8200 switches, only one classifier of type DSCP and of type IEEE 802.1p can be applied to an interface. You can configure routed VLAN interfaces (RVIs) to classify packets. After you do this, the User Priority (UP) bits in the incoming packets are rewritten according to the default IEEE 802.1p rewrite rule, except on J-EX8200 switches. On J-EX8200 switches, you must explicitly assign the default IEEE 802.1p rewrite rule to RVIs. NOTE: By default, all BA classifiers classify traffic into either the best-effort forwarding class or the network-control forwarding class. Multifield Classifiers Multifield classifiers examine multiple fields in a packet such as source and destination addresses and source and destination port numbers of the packet. With MF classifiers, you set the forwarding class and loss priority of a packet based on firewall filter rules. MF classification is normally performed at the network edge because of the general lack of DSCP or IP precedence support in end-user applications. On an edge switch, an MF classifier provides the filtering functionality that scans through a variety of packet fields to determine the forwarding class for a packet. Typically, a classifier performs matching operations on the selected fields against a configured value. Related Documentation • Understanding Junos OS Components for J-EX Series Switches on page 2862 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 • Defining CoS Classifiers (J-Web Procedure) on page 2916 2869 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding CoS Forwarding Classes It is helpful to think of forwarding classes as output queues. In effect, the end result of classification is the identification of an output queue for a particular packet. For a classifier to assign an output queue to each packet, it must associate the packet with one of the following forwarding classes: • expedited-forwarding (ef)—Provides a low loss, low latency, low jitter, assured bandwidth, end-to-end service. • assured-forwarding (af)—Provides a group of values you can define and includes four subclasses: AF1, AF2, AF3, and AF4, each with two drop probabilities: low and high. • best-effort (be)—Provides no service profile. Loss priority is typically not carried in a class-of-service (CoS) value. • network-control (nc)—Supports protocol control and thus is typically high priority. • multicast best-effort (mcast-be)—Used for high-priority multicast packets. • multicast assured-forwarding (mcast-af)—Provides two drop profiles, high and low, for multicast packets. • multicast best-effort (mcast-be)—Provides no service profile for multicast packets. NOTE: The forwarding classes multicast expedited-forwarding, multicast assured-forwarding, and multicast best-effort are applicable only to J-EX8200 Ethernet Switches. J-EX Series Switches support up to 16 forwarding classes, thus allowing granular packet classification. For example, you can configure multiple classes of EF traffic such as EF, EF1, and EF2. J-EX Series switches support up to eight output queues. Therefore, if you configure more than eight forwarding classes, you must map multiple forwarding classes to single output queues. • Default Forwarding Classes on page 2870 Default Forwarding Classes Table 361 on page 2871 shows the four default forwarding classes defined for unicast traffic, and Table 362 on page 2871 shows the three default forwarding classes defined for multicast traffic. NOTE: The default forwarding classes for multicast traffic are applicable only to J-EX8200 switches. If desired, you can rename the forwarding classes associated with the queues supported on your switch. Assigning a new class name to an output queue does not alter the default 2870 Chapter 107: Class of Service (CoS)—Overview classification or scheduling that is applicable to that queue. CoS configurations can be quite complicated, so unless it is required by your scenario, we recommend that you not alter the default class names or queue number associations. Table 361: Default Forwarding Classes for Unicast Packets Forwarding Class Name Comments best-effort (be) The software does not apply any special CoS handling to packets with 000000 in the DiffServ field. This is a backward compatibility feature. These packets are usually dropped under congested network conditions. expedited-forwarding (ef) The software delivers assured bandwidth, low loss, low delay, and low delay variation (jitter) end-to-end for packets in this service class. The software accepts excess traffic in this class, but in contrast to the assured forwarding class, the out-of-profile expedited-forwarding class packets can be forwarded out of sequence or dropped. assured-forwarding (af) The software offers a high level of assurance that the packets are delivered as long as the packet flow from the customer stays within a certain service profile that you define. The software accepts excess traffic, but it applies a tail drop profile to determine if the excess packets are dropped and not forwarded. Up to two drop probabilities (low and high) are defined for this service class. network-control (nc) The software delivers packets in this service class with a high priority. (These packets are not delay-sensitive.) Typically, these packets represent routing protocol hello or keep alive messages. Because loss of these packets jeopardizes proper network operation, packet delay is preferable to packet discard. Table 362: Default Forwarding Classes for Multicast Packets Forwarding Class Name Comments multicast best-effort (mcast-be) The software does not apply any special CoS handling to the multicast packets. These packets are usually dropped under congested network conditions. multicast expedited-forwarding (mcast-ef) The software delivers assured bandwidth, low loss, low delay, and low delay variation (jitter) end-to-end for multicast packets in this service class. The software accepts excess traffic in this class, but in contrast to the multicast assured forwarding class, out-of-profile multicast expedited-forwarding class packets can be forwarded out of sequence or dropped. multicast assured-forwarding (mcast-af) The software offers a high level of assurance that the multicast packets are delivered as long as the packet flow from the customer stays within a certain service profile that you define. The software accepts excess traffic, but it applies a tail drop profile to determine if the excess packets are dropped and not forwarded. Up to two drop probabilities (low and high) are defined for this service class. The following rules govern queue assignment: 2871 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • CoS configurations that specify more queues than the switch can support are not accepted. The commit fails with a detailed message that states the total number of queues available. • All default CoS configurations are based on queue number. The name of the forwarding class that shows up when the default configuration is displayed is the forwarding class currently associated with that queue. • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 • Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 Understanding CoS Tail Drop Profiles Tail drop profile is a congestion management mechanism that allows switch to drop arriving packets when queue buffers become full or begin to overflow. Tail drop profiles define the meanings of the loss priorities. When you configure tail drop profiles you are essentially setting the value for queue fullness. The queue fullness represents a percentage of the memory used to store packets in relation to the total amount that has been allocated for that specific queue. The queue fullness defines the delay-buffer bandwidth, which provides packet buffer space to absorb burst traffic up to the specified duration of delay. Once the specified delay buffer becomes full, packets with 100 percent drop probability are dropped from the tail of the buffer. On J-EX Series Switches, drop probability is implicitly set to 100 percent and it cannot be modified. You specify drop probabilities in the drop profile section of the CoS configuration hierarchy and reference them in each scheduler configuration. By default, if you do not configure any drop profile, tail drop profile is in effect and functions as the primary mechanism for managing congestion. In the default tail drop profile, when the fill level is 0 percent, the drop probability is 0 percent. When the fill level is 100 percent, the drop probability is 100 percent. NOTE: The default drop profile associated with the packets whose loss priority is low cannot be modified. You can configure custom drop profile only for those packets whose loss priority is high. Related Documentation 2872 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925 Chapter 107: Class of Service (CoS)—Overview Understanding CoS Schedulers You use schedulers to define the properties of output queues. These properties include the amount of interface bandwidth assigned to the queue, the size of the memory buffer allocated for storing packets, the priority of the queue, and the drop profiles associated with the queue. You associate the schedulers with forwarding classes by means of scheduler maps. You can then associate each scheduler map with an interface, thereby configuring the queues, packet schedulers, and tail drop processes that operate according to this mapping. • Default Schedulers on page 2873 • Transmission Rate on page 2874 • Scheduler Buffer Size on page 2874 • Priority Scheduling on page 2874 • Scheduler Drop-Profile Maps on page 2875 • Scheduler Maps on page 2875 Default Schedulers Each forwarding class has an associated scheduler priority. Only two forwarding classes, best-effort (queue0) and network-control (queue7) are used in the default configuration. NOTE: On J-EX8200 Ethernet Switches three forwarding classes—best-effort (queue0), multicast best-effort (queue2), and network-control (queue7)—are used in the default configuration. By default, the best-effort forwarding class (queue 0) receives 95 percent of the bandwidth and buffer space for the output link, and the network-control forwarding class (queue 7) receives 5 percent. The default drop profile causes the buffer to fill completely and then to discard all incoming packets until it has free space. NOTE: On J-EX8200 switches, by default, the best-effort forwarding class (queue 0) receives 75 percent of the bandwidth, the multicast best-effort forwarding class (queue 2) receives 20 percent of the bandwidth and buffer space for the output link, and the network-control forwarding class (queue 7) receives 5 percent. The expedited-forwarding and assured-forwarding classes have no scheduler because no resources are assigned to queue 5 and queue 1, by default. However, you can manually configure resources for the expedited-forwarding and assured-forwarding classes. Also by default, each queue can exceed the assigned bandwidth if additional bandwidth is available from other queues. When a forwarding class does not fully use the allocated transmission bandwidth, the remaining bandwidth can be used by other forwarding 2873 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS classes if they receive a larger amount of offered load than their allocated bandwidth allows. Transmission Rate The transmission-rate control determines the actual traffic bandwidth from each forwarding class you configure. The rate is specified in bits per second. Each queue is allocated some portion of the bandwidth of the outgoing interface. This bandwidth amount can be a fixed value, such as 1 megabit per second (Mbps), a percentage of the total available bandwidth, or the rest of the available bandwidth. You can allow transmission bandwidth to exceed the configured rate if additional bandwidth is available from other queues. In case of congestion, configured amount of transmission rate is guaranteed for the queue. This property allows you to ensure that each queue receives the amount of bandwidth appropriate to its level of service. Scheduler Buffer Size To control congestion at the output stage, you can configure the delay-buffer bandwidth. The delay-buffer bandwidth provides packet buffer space to absorb burst traffic up to the specified duration of delay. Once the specified delay buffer becomes full, packets with 100 percent drop probability are dropped from the tail of the buffer. The default scheduler transmission rate for queues 0 through 7 are 95, 0, 0, 0, 0, 0, 0, and 5 percent of the total available bandwidth. The default buffer-size percentages for queues 0 through 7 are 95, 0, 0, 0, 0, 0, 0, and 5 percent of the total available buffer. NOTE: On J-EX8200 switches, the default scheduler transmission rates for queues 0 through 7 are 75, 0, 20, 0, 0, 0, 0, and 5 percent of the total available bandwidth. The default buffer-size percentages for queues 0 through 7 are 75, 0, 20, 0, 0, 0, 0, and 5 percent of the total available buffer. For each scheduler, you can configure the buffer size as one of the following: • A percentage of the total buffer. • The remaining buffer available. The remainder is the buffer percentage that is not assigned to other queues. For example, if you assign 40 percent of the delay buffer to queue 0, allow queue 2 to keep the default allotment of 20 percent, allow queue 7 to keep the default allotment of 5 percent, and assign the remainder to queue 3, then queue 3 uses approximately 35 percent of the delay buffer. Priority Scheduling Priority scheduling determines the order in which an output interface transmits traffic from the queues, thus ensuring that queues containing important traffic are provided better access to the outgoing interface. Priority scheduling is accomplished through a procedure in which the scheduler examines the priority of the queue. The Junos OS supports two levels of transmission priority: 2874 Chapter 107: Class of Service (CoS)—Overview • Low—The scheduler determines if the individual queue is within its defined bandwidth profile. This binary decision, which is reevaluated on a regular time cycle, compares the amount of data transmitted by the queue against the amount of bandwidth allocated to it by the scheduler. When the transmitted amount is less than the allocated amount, the queue is considered to be in profile. A queue is out of profile when its transmitted amount is larger than its allocated amount. Out of profile queue will be transmitted only if bandwidth is available. Otherwise, it will be buffered. A queue from the set is selected based on the shaped deficit weighted round robin (SDWRR) algorithm, which operates within the set. • Strict-high—Strict-high priority queue receives preferential treatment over low priority queue. Unlimited bandwidth is assigned to strict-high priority queue. Queues are scheduled according to the queue number, starting with the highest queue 7, with decreasing priority down through queue 0. Traffic in higher queue numbers is always scheduled prior to traffic in lower queue numbers. In other words, in case of two high priority queues, the queue with higher queue number is processed first. Packets in low priority queues are transmitted only when strict-high priority queues are empty. Scheduler Drop-Profile Maps Drop-profile maps associate drop profiles with a scheduler. Drop-profile map sets the drop profile for a specific packet loss priority (PLP) and protocol type. The inputs for the drop-profile map are the PLP and the protocol type. The output is the drop profile. Scheduler Maps A scheduler map associates a specified forwarding class with a scheduler configuration. After configuring a scheduler, you must include it in a scheduler map and then associate the scheduler map with an output interface. J-EX Series Switches allow you to associate up to four user-defined scheduler maps with interfaces. Related Documentation • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Schedulers (CLI Procedure) on page 2920 • Defining CoS Schedulers (J-Web Procedure) on page 2920 2875 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding CoS Two-Color Marking Networks police traffic by limiting the input or output transmission rate of a class of traffic on the basis of user-defined criteria. Policing traffic allows you to control the maximum rate of traffic sent or received on an interface and to partition a network into multiple priority levels or classes of service. Policers require you to apply limits to the traffic flow and set a consequence for packets that exceed these limits—usually a higher loss priority, so that packets exceeding the policer limits are discarded first. J-EX Series Switches support a single-rate two-color marking type of policer, which is a simplified version of Single-Rate-Three-Color marking, defined in RFC 2697, A Single Rate Three Color Marker. This type of policer meters traffic based on the configured committed information rate (CIR) and committed burst size (CBS). The single-rate two-color marker meters traffic and marks incoming packets depending on whether they are smaller than the committed burst size (CBS)—marked green—or exceed it— marked red. The single-rate two-color marking policer operates in color-blind mode. In this mode, the policer's actions are not affected by any previous marking or metering of the examined packets. In other words, the policer is “blind? to any previous coloring a packet might have had. Related Documentation • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Understanding the Use of Policers in Firewall Filters on page 2752 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 Understanding CoS Rewrite Rules As packets enter or exit a network, edge switches might be required to alter the class-of-service (CoS) settings of the packets. This topic describes how to use rewrite rules to alter the CoS settings. It covers: • How Rewrite Rules Work on page 2876 • Default Rewrite Rule on page 2877 How Rewrite Rules Work Rewrite rules set the value of the CoS bits within the packet’s header. Each rewrite rule reads the current forwarding class and loss priority associated with the packet, locates the chosen CoS value from a table, and writes this CoS value into the packet header. For rewrites to occur, rewrite rules must be explicitly assigned to an interface. Only tagged Layer 3 interfaces and tagged routed VLAN interfaces (RVIs) automatically rewrite packets by using the default IEEE 802.1p rewrite rule. Multiple rewrite rules of different types can be assigned to a single interface. 2876 Chapter 107: Class of Service (CoS)—Overview NOTE: On J-EX8200 Ethernet Switches, tagged Layer 3 interfaces and tagged RVIs do not automatically rewrite packets using the default IEEE 802.1p rewrite rule. You must explicitly assign the IEEE 802.1p rewrite rule to these interfaces for rewrites to occur. Also, only one rewrite rule of each type can be assigned to any interface on a J-EX8200 switch. In effect, the rewrite rule performs the opposite function of the behavior aggregate (BA) classifier used when the packet enters the switch. As the packet leaves the switch, the final CoS action is generally the application of a rewrite rule. You configure rewrite rules to alter CoS values in outgoing packets on the outbound interfaces of an edge switch to meet the policies of a targeted peer. This allows the downstream switch in a neighboring network to classify each packet into the appropriate service group. NOTE: When an IP precedence rewrite rule is active, bits 3, 4, and 5 of the ToS byte are always reset to zero when code points are rewritten. Default Rewrite Rule To enable a rewrite rule on an interface, you can either create your own rewrite rule and enable it on the interface or enable a default rewrite rule. See “Defining CoS Rewrite Rules (CLI Procedure)” on page 2925. Table 363 on page 2877 shows the default rewrite-rule mappings. These are based on the default bit definitions of Differentiated Services code point (DSCP), IEEE 802.1p, and IP precedence values and the default forwarding classes. When the CoS values of a packet match the forwarding-class and packet-loss-priority (PLP) values, the switch rewrites markings on the packet based on the rewrite table. Table 363: Default Packet Header Rewrite Mappings Map from Forwarding Class PLP Value Map to DSCP/IEEE 802.1p/IP Precedence Value expedited-forwarding low ef expedited-forwarding high ef assured-forwarding low af11 assured-forwarding high af12 (DSCP) best-effort low be 2877 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 363: Default Packet Header Rewrite Mappings (continued) Map from Forwarding Class PLP Value Map to DSCP/IEEE 802.1p/IP Precedence Value best-effort high be network-control low nc1/cs6 network-control high nc2/cs7 Related Documentation • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 • Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 Understanding Port Shaping and Queue Shaping for CoS on J-EX Series Switches If the amount of traffic on a switch's network interface is more than the maximum bandwidth allowed on the interface, it leads to congestion. Port shaping and queue shaping can be used to manage the excess traffic and avoid congestion. Port shaping defines the maximum bandwidth allocated to a port, while queue shaping defines a limit on excess-bandwidth usage per queue. This topic covers: • Port Shaping on page 2878 • Queue Shaping on page 2878 Port Shaping Port shaping enables you to shape the aggregate traffic through a port or channel to a rate that is less than the line or port rate. Queue Shaping Queue shaping throttles the rate at which queues transmit packets. For example, using queue shaping, you can rate-limit a strict-priority queue so that the strict-priority queue does not lock out (or starve) low-priority queues. Similarly, for any queue, you can configure queue shaping. Related Documentation 2878 • Understanding CoS Schedulers on page 2873 • Defining CoS Schedulers (CLI Procedure) on page 2920 Chapter 107: Class of Service (CoS)—Overview Understanding Junos OS EZQoS for CoS Configurations on J-EX Series Switches Junos OS EZQoS on J-EX Series Switches eliminates the complexities involved in configuring class of service (CoS) across the network. EZQoS offers templates for key traffic classes. Junos OS CoS allows you to divide traffic into classes and offer various levels of throughput and packet loss when congestion occurs. You can use CoS to ensure that different types of traffic (voice, video, and data) get the bandwidth and consideration they need to meet user expectations and business objectives. Configuring CoS requires careful consideration of your service needs and thorough planning and design to ensure consistency across all switches in a CoS domain. To configure CoS manually, you must define and fine-tune all CoS components such as classifiers, rewrite rules, forwarding classes, schedulers, and scheduler-maps and then apply these components to the interfaces. Therefore, configuring CoS can be a fairly complex and time-consuming task. EZQoS works by automatically assigning preconfigured values to all CoS parameters based on the typical application requirements. These preconfigured values are stored in a template with a unique name. You can change the preconfigured values of these parameters to suit your particular application needs. For using EZQoS, you must identify which switch ports are being used for a specific application (such as VoIP, video, and data) and manually apply the corresponding application-specific EZQoS template to these switch ports. NOTE: Currently, we provide an EZQoS template for configuring CoS for VoIP. NOTE: We recommend that you do not use the term EZQoS for defining a classifier. Related Documentation • Junos OS CoS for J-EX Series Switches Overview on page 2860 • Configuring Junos OS EZQoS for CoS (CLI Procedure) on page 2930 2879 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Using CoS with MPLS Networks on J-EX Series Switches You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. J-EX Series Switches support Differentiated Service Code Point (DSCP) or IP precedence and IEEE 802.1p CoS classifiers on the customer-edge interfaces of the ingress provider edge (PE) switch. DSCP or IP precedence classifiers are used for Layer 3 packets. IEEE 802.1p is used for Layer 2 packets. When a packet enters a customer-edge interface of the ingress PE switch, the switch associates the packet with a particular CoS servicing level prior to putting the packet onto the label-switched path (LSP). The switches within the LSP utilize the CoS value set at the ingress PE switch. The CoS value that was embedded in the DSCP, IP precedence, or IEEE 802.1 p classifier is translated and encoded in the MPLS header by means of the EXP or experimental bits. J-EX Series switches enable a default EXP classifier and a default EXP rewrite rule. You can configure a custom EXP classifier and a custom EXP rewrite rule if you prefer. However, the switch supports only one type of EXP classifier (default or custom) and only one EXP rewrite rule (default or custom). You do not bind the EXP classifier or the EXP rewrite rule to individual interfaces. The switch automatically and implicitly applies the default or the custom EXP classifier and the default or the custom EXP rewrite rule to the appropriate MPLS-enabled interfaces. Because rewrite rules affect only egress interfaces, the switch applies the EXP rewrite rule only to those MPLS interfaces that are transmitting MPLS packets (not to the MPLS interfaces that are receiving the packets). This topic includes: • Guidelines for Using CoS Classifiers on CCCs on page 2880 • Using CoS Classifiers with IP over MPLS on page 2881 • Default Classifiers and Default Rewrite Rules on page 2881 • EXP Rewrite Rules on page 2881 • Policer on page 2882 • Schedulers on page 2882 Guidelines for Using CoS Classifiers on CCCs When you are configuring CoS for MPLS over circuit cross-connect (CCC), there are some additional guidelines, as follows: 2880 • You must explicitly bind a CoS classifier to the CCC interface on the ingress PE switch. • You cannot use more than one type of DSCP/IP precedence and not more than one type of IEEE 802.1p classifier on the CCC interfaces. Thus, if you configure one CCC interface to use DSCP1, you cannot configure another CCC interface to use DSCP2. Likewise, if you configure one CCC interface to use IEEE1, you cannot configure another Chapter 107: Class of Service (CoS)—Overview CCC interface on the same switch to use IEEE2. All the CCC interfaces on the switch must use the same DSCP classifier and the same type of IEEE 802.1p classifier. • You cannot configure one CCC interface as DSCP and another CCC interface as IP precedence, because these classifier types overlap. • You can configure one CCC interface as DSCP and another CCC interface as IEEE 802.1p. • You can configure one CCC interface as both DSCP and IEEE 802.1p. If you configure a CCC interface with both these classifiers, the DSCP classifier is used for routing Layer 3 packets and the IEEE 802.1p classifier is used for routing Layer 2 packets. NOTE: You can define multiple types of DSCP, IP precedence, and IEEE 802.1p on the switch and use the different classifier types for the non-CCC interfaces on the switch. Using CoS Classifiers with IP over MPLS When you are configuring CoS for IP over MPLS, the customer-edge interface uses the CoS configuration that has been set up for the switch as the default. You do not have to bind a classifier to the customer-edge interface in this case. There are no restrictions regarding using multiple types of DSCP, IP precedence, and IEEE 802.1p on the same switch. • You can modify the CoS classifier for a particular interface, but it is not required. • You can configure one interface as DSCP1 and another as DSCP2 and another and IP precedence, and so forth. Default Classifiers and Default Rewrite Rules The default classifiers support only two forwarding classes, best-effort and network-control, and use only two queues, 0 and 7. However, J-EX Series switches support up to sixteen forwarding classes and eight queues. To use the additional forwarding classes and queues, create a custom classifier. To modify the code point and loss priority for a specific forwarding class, configure a rewrite rule on the switch. The default rewrite rule for EXP is enabled in the default configuration. However, the default rewrite rules for the other classifiers are not enabled in the default configuration. You can display the default classifier mappings and default rewrite mappings by entering the show class-of-service command on the switch. EXP Rewrite Rules When traffic passes from the customer-edge interface to an MPLS interface, the DSCP, IP precedence, or IEEE 802.1p CoS classifier is translated into the EXP bits within the MPLS header. You cannot disable the default EXP rewrite rule, but you can configure your own custom EXP classifier and a custom EXP rewrite rule. You cannot bind the EXP classifier to individual MPLS interfaces; the switch applies it globally to all the MPLS-enabled interfaces on the switch. 2881 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Only one EXP rewrite rule (either default or custom) is supported on a switch. The switch applies it to all the MPLS-enabled egress interfaces. Policer Policing helps to ensure that the amount of traffic forwarded through an LSP never exceeds the requested bandwidth allocation. During periods of congestion (when the total rate of queuing packets exceeds the rate of transmission), any new packets being sent to an interface can be dropped because there is no place to store them. You should configure a policer on the ingress PE switch: • If you are using MPLS with CCC, you bind the policer to the LSP. You cannot bind a policer to a CCC interface. • If you are using IP over MPLS, you bind the policer to the inet-family customer-edge interface. You cannot bind a policer to the LSP when you are using IP over MPLS. Schedulers The schedulers for using CoS with MPLS are the same as for the other CoS configurations on J-EX Series switches. Default schedulers are provided for best-effort and network-control forwarding classes. If you are using assured-forwarding, expedited-forwarding, or other custom forwarding classes, we recommend that you configure a scheduler to support that forwarding class. See “Understanding CoS Schedulers” on page 2873. Related Documentation 2882 • Junos OS MPLS for J-EX Series Switches Overview on page 3057 • Understanding CoS Classifiers on page 2867 • Understanding CoS Schedulers on page 2873 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) on page 2932 • Configuring Rewrite Rules for EXP Classifiers on MPLS Networks (CLI Procedure) • Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) on page 3106 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 CHAPTER 108 Examples: CoS Configuration • Example: Configuring CoS on J-EX Series Switches on page 2883 • Example: Combining CoS with MPLS on J-EX Series Switches on page 2898 Example: Configuring CoS on J-EX Series Switches Configure class of service (CoS) on your switch to manage traffic so that when the network experiences congestion and delay, critical applications are protected. Using CoS, you can divide traffic on your switch into classes and provide various levels of throughput and packet loss. This is especially important for traffic that is sensitive to jitter and delay, such as voice traffic. This example shows how to configure CoS on a single J-EX Series switch in the network. • Requirements on page 2883 • Overview and Topology on page 2883 • Configuration on page 2886 • Verification on page 2896 Requirements This example uses the following hardware and software components: • One J-EX4200 switch Overview and Topology This example uses the topology shown in Figure 80 on page 2884. 2883 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 80: Topology for Configuring CoS The topology for this configuration example consists of one J-EX Series switch at the access layer. The J-EX Series access switch is configured to support VLAN membership. Switch ports ge-0/0/0and ge-0/0/1 are assigned to the voice-vlan for two VoIP phones. Switch port ge-0/0/2 is assigned to the camera-vlan for the surveillance camera. Switch ports 2884 Chapter 108: Examples: CoS Configuration ge-0/0/3, ge-0/0/4, ge-0/0/5, and ge-0/0/6 are assigned to the server-vlan for the servers hosting various applications such as those provided by Citrix, Microsoft, Oracle, and SAP. Table 364 on page 2885 shows the VLAN configuration components. Table 364: Configuration Components: VLANs VLAN Name VLAN ID voice-vlan 10 VLAN Subnet and Available IP Addresses 192.168.1.0/32 192.168.1.1 through 192.168.1.11 VLAN Description Voice VLAN used for employee VoIP communication. 192.168.1.12 is the subnet’s broadcast address. camera-vlan 20 192.168.1.13/32 192.168.1.14 through 192.168.1.20 VLAN for the surveillance cameras. 192.168.1.21 is the subnet’s broadcast address. server-vlan 30 192.168.1.22/32 192.168.1.23 through 192.168.1.35 VLAN for the servers hosting enterprise applications. 192.168.1.36 is the subnet’s broadcast address. Ports on the J-EX Series switches support Power over Ethernet (PoE) to provide both network connectivity and power for VoIP telephones connecting to the ports. Table 365 on page 2885 shows the switch interfaces that are assigned to the VLANs and the IP addresses for devices connected to the switch ports: Table 365: Configuration Components: Switch Ports on a 48-Port All-PoE Switch Interfaces VLAN Membership IP Addresses Port Devices ge-0/0/0, ge-0/0/1 voice-vlan 192.168.1.1 through 192.168.1.2 Two VoIP telephones. ge-0/0/2 camera-vlan 192.168.1.14 Surveillance camera. ge-0/0/3, ge-0/0/4, ge-0/0/5, ge-0/0/6 sevrer-vlan 192.168.1.23 through 192.168.1.26 Four servers hosting applications such as those provided by Citrix, Microsoft, Oracle, and SAP. 2885 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS NOTE: This example shows how to configure CoS on a single J-EX Series switch. This example does not consider across-the-network applications of CoS in which you might implement different configurations on ingress and egress switches to provide differentiated treatment to different classes across a set of nodes in a network. Configuration CLI Quick Configuration To quickly configure CoS, copy the following commands and paste them into the switch terminal window: [edit] set class-of-service forwarding-classes class app queue-num 5 set class-of-service forwarding-classes class mail queue-num 1 set class-of-service forwarding-classes class db queue-num 2 set class-of-service forwarding-classes class erp queue-num 3 set class-of-service forwarding-classes class video queue-num 4 set class-of-service forwarding-classes class best-effort queue-num 0 set class-of-service forwarding-classes class voice queue-num 6 set class-of-service forwarding-classes class network-control queue-num 7 set firewall family ethernet-switching filter voip_class term voip from source-address 192.168.1.1/32 set firewall family ethernet-switching filter voip_class term voip from source-address 192.168.1.2/32 set firewall family ethernet-switching filter voip_class term voip from protocol udp set firewall family ethernet-switching filter voip_class term voip from source-port 2698 set firewall family ethernet-switching filter voip_class term voip then forwarding-class voice loss-priority low set firewall family ethernet-switching filter voip_class term network_control from precedence [net-control internet-control] set firewall family ethernet-switching filter voip_class term network_control then forwarding-class network-control loss-priority low set firewall family ethernet-switching filter voip_class term best_effort_traffic then forwarding-class best-effort loss-priority low set interfaces ge-0/0/0 description phone1–voip-ingress-port set interfaces ge-0/0/0 unit 0 family ethernet-switching filter input voip_class set interfaces ge-0/0/1 description phone2–voip-ingress-port set interfaces ge-0/0/1 unit 0 family ethernet-switching filter input voip_class set firewall family ethernet-switching filter video_class term video from source-address 192.168.1.14/32 set firewall family ethernet-switching filter video_class term video from protocol udp set firewall family ethernet-switching filter video_class term video from source-port 2979 set firewall family ethernet-switching filter video_class term video then forwarding-class video loss-priority low set firewall family ethernet-switching filter video_class term network_control from precedence [net-control internet-control] set firewall family ethernet-switching filter video_class term network_control then forwarding-class network-control loss-priority low set firewall family ethernet-switching filter video_class term best_effort_traffic then forwarding-class best-effort loss-priority low set interfaces ge-0/0/2 description video-ingress-port set interfaces ge-0/0/2 unit 0 family ethernet-switching filter input video_class set firewall family ethernet-switching filter app_class term app from source-address 192.168.1.23/32 set firewall family ethernet-switching filter app_class term app from protocol tcp set firewall family ethernet-switching filter app_class term app from source-port [1494 2512 2513 2598 2897] 2886 Chapter 108: Examples: CoS Configuration set firewall family ethernet-switching filter app_class term app then forwarding-class app loss-priority low set firewall family ethernet-switching filter app_class term mail from source-address 192.168.1.24/32 set firewall family ethernet-switching filter app_class term mail from protocol tcp set firewall family ethernet-switching filter app_class term mail from source-port [25 143 389 691 993 3268 3269] set firewall family ethernet-switching filter app_class term mail then forwarding-class mail loss-priority low set firewall family ethernet-switching filter app_class term db from source-address 192.168.1.25/32 set firewall family ethernet-switching filter app_class term db from protocol tcp set firewall family ethernet-switching filter app_class term db from source-port [1521 1525 1527 1571 1810 2481] set firewall family ethernet-switching filter app_class term db then forwarding-class db loss-priority low set firewall family ethernet-switching filter app_class term erp from source-address 192.168.1.26/32 set firewall family ethernet-switching filter app_class term erp from protocol tcp set firewall family ethernet-switching filter app_class term erp from source-port [3200 3300 3301 3600] set firewall family ethernet-switching filter app_class term erp then forwarding-class erp loss-priority low set firewall family ethernet-switching filter app_class term network_control from precedence [net-control internet-control] set firewall family ethernet-switching filter app_class term network_control then forwarding-class network-control loss-priority low set firewall family ethernet-switching filter app_class term best_effort_traffic then forwarding-class best-effort loss-priority low set interfaces ge-0/0/3 unit 0 family ethernet-switching filter input app_class set interfaces ge-0/0/4 unit 0 family ethernet-switching filter input app_class set interfaces ge-0/0/5 unit 0 family ethernet-switching filter input app_class set interfaces ge-0/0/6 unit 0 family ethernet-switching filter input app_class set class-of-service schedulers voice-sched buffer-size percent 10 set class-of-service schedulers voice-sched priority strict-high set class-of-service schedulers voice-sched transmit-rate percent 10 set class-of-service schedulers video-sched buffer-size percent 15 set class-of-service schedulers video-sched priority low set class-of-service schedulers video-sched transmit-rate percent 15 set class-of-service schedulers app-sched buffer-size percent 10 set class-of-service schedulers app-sched priority low set class-of-service schedulers app-sched transmit-rate percent 10 set class-of-service schedulers mail-sched buffer-size percent 5 set class-of-service schedulers mail-sched priority low set class-of-service schedulers mail-sched transmit-rate percent 5 set class-of-service schedulers db-sched buffer-size percent 10 set class-of-service schedulers db-sched priority low set class-of-service schedulers db-sched transmit-rate percent 10 set class-of-service schedulers erp-sched buffer-size percent 10 set class-of-service schedulers erp-sched priority low set class-of-service schedulers erp-sched transmit-rate percent 10 set class-of-service schedulers nc-sched buffer-size percent 5 set class-of-service schedulers nc-sched priority strict-high set class-of-service schedulers nc-sched transmit-rate percent 5 set class-of-service schedulers be-sched buffer-size percent 35 set class-of-service schedulers be-sched priority low set class-of-service schedulers be-sched transmit-rate percent 35 set class-of-service scheduler-maps ethernet-cos-map forwarding-class voice scheduler voice-sched set class-of-service scheduler-maps ethernet-cos-map forwarding-class video scheduler video-sched set class-of-service scheduler-maps ethernet-cos-map forwarding-class app scheduler app-sched 2887 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS set class-of-service scheduler-maps ethernet-cos-map forwarding-class mail scheduler mail-sched set class-of-service scheduler-maps ethernet-cos-map forwarding-class db scheduler db-sched set class-of-service scheduler-maps ethernet-cos-map forwarding-class erp scheduler erp-sched set class-of-service scheduler-maps ethernet-cos-map forwarding-class network-control scheduler nc-sched set class-of-service scheduler-maps ethernet-cos-map forwarding-class best-effort scheduler be-sched set class-of-service interfaces ge-0/0/20 scheduler-map ethernet-cos-map Step-by-Step Procedure To configure and apply CoS: 1. Configure one-to-one mapping between eight forwarding classes and eight queues: [edit class-of-service] user@switch# set forwarding-classes class app queue-num 5 user@switch# set forwarding-classes class mail queue-num 1 user@switch# set forwarding-classes class db queue-num 2 user@switch# set forwarding-classes class erp queue-num 3 user@switch# set forwarding-classes class video queue-num 4 user@switch# set forwarding-classes class best-effort queue-num 0 user@switch# set forwarding-classes class voice queue-num 6 user@switch# set forwarding-classes class network-control queue-num 7 2. Define the firewall filter voip_class to classify the VoIP traffic: [edit firewall] user@switch# set family ethernet-switching filter voip_class 3. Define the term voip: [edit firewall] user@switch# set family ethernet-switching filter voip_class term voip from source-address 192.168.1.1/32 user@switch# set family ethernet-switching filter voip_class term voip from source-address 192.168.1.2/32 user@switch# set family ethernet-switching filter voip_class term voip protocol udp user@switch# set family ethernet-switching filter voip_class term voip source-port 2698 user@switch# set family ethernet-switching filter voip_class term voip then forwarding-class voice loss-priority low 4. Define the term network_control: [edit firewall] user@switch# set family ethernet-switching filter voip_class term network_control from precedence [net-control internet-control] user@switch# set family ethernet-switching filter voip_class term network_control then forwarding-class network-control loss-priority low 5. Define the term best_effort_traffic with no match conditions: [edit firewall] user@switch# set family ethernet-switching filter voip_class term best_effort_traffic then forwarding-class best-effort loss-priority low 6. Apply the firewall filter voip_class as an input filter to the interfaces for the VoIP phones: [edit interfaces] user@switch# set ge-0/0/0 description phone1–voip-ingress-port user@switch# set ge-0/0/0 unit 0 family ethernet-switching filter input voip_class user@switch# set ge-0/0/1 description phone2–voip-ingress-port 2888 Chapter 108: Examples: CoS Configuration user@switch# set ge-0/0/1 unit 0 family ethernet-switching filter input voip_class 7. Define the firewall filter video_class to classify the video traffic: [edit firewall] user@switch# set family ethernet-switching filter video_class 8. Define the term video: [edit firewall] user@switch# set family ethernet-switching filter video_class term video from source-address 192.168.1.14/32 user@switch# set family ethernet-switching filter video_class term video protocol udp user@switch# set family ethernet-switching filter video_class term video source-port 2979 user@switch# set family ethernet-switching filter video_class term video then forwarding-class video loss-priority low 9. Define the term network_control (for the video_class filter): [edit firewall] user@switch# set family ethernet-switching filter video_class term network_control from precedence [net-control internet-control] user@switch# set family ethernet-switching filter video_class term network_control then forwarding-class network-control loss-priority low 10. Define the term best_effort_traffic (for the video_class filter): [edit firewall] user@switch# set family ethernet-switching filter video_class term best_effort_traffic then forwarding-class best-effort loss-priority low 11. Apply the firewall filter video_class as an input filter to the interface for the surveillance camera: [edit interfaces] user@switch# set ge-0/0/2 description video-ingress-port user@switch# set ge-0/0/2 unit 0 family ethernet-switching filter input video_class 12. Define the firewall filter app_class to classify the application server traffic: [edit firewall] user@switch# set family ethernet-switching filter app_class 13. Define the term app: [edit firewall] user@switch# set family ethernet-switching filter app_class term app from source-address 192.168.1.23/32 user@switch# set family ethernet-switching filter app_class term app protocol tcp user@switch# set family ethernet-switching filter app_class term app source-port [1494 2512 2513 2598 2897] user@switch# set family ethernet-switching filter app_class term app then forwarding-class app loss-priority low 14. Define the term mail: [edit firewall] user@switch# set family ethernet-switching filter app_class term mail from source-address 192.168.1.24/32 user@switch# set family ethernet-switching filter app_class term mail protocol tcp user@switch# set family ethernet-switching filter app_class term mail source-port [25 143 389 691 993 3268 3269] 2889 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch# set family ethernet-switching filter app_class term mail then forwarding-class mail loss-priority low 15. Define the term db: [edit firewall] user@switch# set family ethernet-switching filter app_class term db from source-address 192.168.1.25/32 user@switch# set family ethernet-switching filter app_class term db protocol tcp user@switch# set family ethernet-switching filter app_class term db source-port [1521 1525 1527 1571 1810 2481] user@switch# set family ethernet-switching filter app_class term db then forwarding-class db loss-priority low 16. Define the term erp: [edit firewall] user@switch# set family ethernet-switching filter app_class term erp from source-address 192.168.1.26/32 user@switch# set family ethernet-switching filter app_class term erp protocol tcp user@switch# set family ethernet-switching filter app_class term erp source-port [3200 3300 3301 3600] user@switch# set family ethernet-switching filter app_class term erp then forwarding-class erp loss-priority low 17. Define the term network_control (for the app_class filter): [edit firewall] user@switch# set family ethernet-switching filter app_class term network_control from precedence [net-control internet-control] user@switch# set family ethernet-switching filter app_class term network_control then forwarding-class network-control loss-priority low 18. Define the term best_effort_traffic (for the app_class filter): [edit firewall] user@switch# set family ethernet-switching filter app_class term best_effort_traffic then forwarding-class best-effort loss-priority low 19. Apply the firewall filter app_class as an input filter to the interfaces for the servers hosting applications: [edit interfaces] user@switch# set ge-0/0/3 unit 0 family ethernet-switching filter input app_class user@switch# set ge-0/0/4 unit 0 family ethernet-switching filter input app_class user@switch# set ge-0/0/5 unit 0 family ethernet-switching filter input app_class user@switch# set ge-0/0/6 unit 0 family ethernet-switching filter input app_class 20. Configure schedulers: [edit class-of-service] user@switch# set schedulers voice-sched buffer-size percent 10 user@switch# set schedulers voice-sched priority strict-high user@switch# set schedulers voice-sched transmit-rate percent 10 user@switch# set schedulers video-sched buffer-size percent 15 user@switch# set schedulers video-sched priority low user@switch# set schedulers video-sched transmit-rate percent 15 user@switch# set schedulers app-sched buffer-size percent 10 user@switch# set schedulers app-sched priority low user@switch# set schedulers app-sched transmit-rate percent 10 user@switch# set schedulers mail-sched buffer-size percent 5 user@switch# set schedulers mail-sched priority low 2890 Chapter 108: Examples: CoS Configuration user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# user@switch# 21. set schedulers mail-sched transmit-rate percent 5 set schedulers db-sched buffer-size percent 10 set schedulers db-sched priority low set schedulers db-sched transmit-rate percent 10 set schedulers erp-sched buffer-size percent 10 set schedulers erp-sched priority low set schedulers erp-sched transmit-rate percent 10 set schedulers nc-sched buffer-size percent 5 set schedulers nc-sched priority strict-high set schedulers nc-sched transmit-rate percent 5 set schedulers be-sched buffer-size percent 35 set schedulers be-sched priority low set schedulers be-sched transmit-rate percent 35 Assign the forwarding classes to schedulers with the scheduler map ethernet-cos-map: [edit class-of-service] user@switch# set scheduler-maps ethernet-cos-map forwarding-class voice scheduler voice-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class video scheduler video-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class app scheduler app-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class mail scheduler mail-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class db scheduler db-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class erp scheduler erp-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class network-control scheduler nc-sched user@switch# set scheduler-maps ethernet-cos-map forwarding-class best-effort scheduler be-sched 22. Associate the scheduler map with the outgoing interface: [edit class-of-service interfaces] user@switch# set ge-0/0/20 scheduler-map ethernet-cos-map Results Display the results of the configuration: user@switch# show firewall firewall family ethernet-switching { filter voip_class { term voip { from { source-address { 192.168.1.1/32; 192.168.1.2/32; } protocol udp; source-port 2698; } then { forwarding-class voice; loss-priority low; } 2891 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } term network control { from { precedence [net-control internet-control]; } then { forwarding-class network-control; loss-priority low; } } term best_effort_traffic { then { forwarding-class best-effort; loss-priority low; } } } filter video_class { term video { from { source-address { 192.168.1.14/32; } protocol udp; source-port 2979; } then { forwarding-class video; loss-priority low; } } term network control { from { precedence [net-control internet-control]; } then { forwarding-class network-control; loss-priority low; } } term best_effort_traffic { then { forwarding-class best-effort; loss-priority low; } } } filter app_class { term app { from { source-address { 192.168.1.23/32; } protocol tcp; source-port [1491 2512 2513 2598 2897]; } 2892 Chapter 108: Examples: CoS Configuration then { forwarding-class app; loss-priority low; } } term mail { from { source-address { 192.168.1.24/32; } protocol tcp; source-port [25 143 389 691 993 3268 3269]; } then { forwarding-class mail; loss-priority low; } } term db { from { source-address { 192.168.1.25/32; } protocol tcp; source-port [1521 1525 1527 1571 1810 2481]; } then { forwarding-class db; loss-priority low; } } term erp { from { source-address { 192.168.1.26/32; } protocol tcp; source-port [3200 3300 3301 3600]; } then { forwarding-class erp; loss-priority low; } } term network control { from { precedence [net-control internet-control]; } then { forwarding-class network-control; loss-priority low; } } term best_effort_traffic { then { forwarding-class best-effort; 2893 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS loss-priority low; } } } } user@switch# show class-of-service forwarding-classes { class app queue-num 5; class mail queue-num 1; class db queue-num 2; class erp queue-num 3; class video queue-num 4; class best-effort queue-num 0; class voice queue-num 6; class network-control queue-num 7; } schedulers { voice-sched { buffer-size percent 10; priority strict-high; transmit-rate percent 10; } video-sched { buffer-size percent 15; priority low; transmit-rate percent 15; } app-sched { buffer-size percent 10; priority low; transmit-rate percent 10; } mail-sched { buffer-size percent 5; priority low; transmit-rate percent 5; } db-sched { buffer-size percent 10; priority low; transmit-rate percent 10; } erp-sched { buffer-size percent 10; priority low; transmit-rate percent 10; } nc-sched { buffer-size percent 5; priority strict-high; transmit-rate percent 5; } be-sched { buffer-size percent 35; priority low; 2894 Chapter 108: Examples: CoS Configuration transmit-rate percent 35; } } scheduler-maps { ethernet-cos-map { forwarding-class voice scheduler voice-sched; forwarding-class video scheduler video-sched; forwarding-class app scheduler app-sched; forwarding-class mail scheduler mail-sched; forwarding-class db scheduler db-sched; forwarding-class erp scheduler erp-sched; forwarding-class network-control scheduler nc-sched; forwarding-class best-effort scheduler be-sched; } } user@switch# show interfaces ge-0/0/0 { unit 0 { family ethernet { filter { input voip_class; } } } } ge-0/0/1 { unit 0 { family ethernet { filter { input voip_class; } } } } ge-0/0/2 { unit 0 { family ethernet { filter { input video_class; } } } } ge-0/0/3 { unit 0 { family ethernet { filter { input app_class; } } } } ge-0/0/4 { unit 0 { family ethernet { 2895 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS filter { input app_class; } } } } ge-0/0/5 { unit 0 { family ethernet { filter { input app_class; } } } } ge-0/0/6 { unit 0 { family ethernet { filter { input app_class; } } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That the Defined Forwarding Classes Exist and Are Mapped to Queues on page 2896 • Verifying That the Forwarding Classes Have Been Assigned to Schedulers on page 2897 • Verifying That the Scheduler Map Has Been Applied to the Interface on page 2898 Verifying That the Defined Forwarding Classes Exist and Are Mapped to Queues Purpose Action Meaning 2896 Verify that the following forwarding classes app, db, erp, mail, video, and voice have been defined and mapped to queues. user@switch> show class-of-service forwarding-class Forwarding class ID Queue app 0 5 db 1 2 erp 2 3 best-effort 3 0 mail 4 1 voice 5 6 video 6 4 network-control 7 7 This output shows that the forwarding classes have been defined and mapped to appropriate queues. Chapter 108: Examples: CoS Configuration Verifying That the Forwarding Classes Have Been Assigned to Schedulers Purpose Action Verify that the forwarding classes have been assigned to schedulers. user@switch> show class-of-service scheduler-map Scheduler map: ethernet-cos-map, Index: 2 Scheduler: voice-sched, Forwarding class: voice, Index: 22 Transmit rate: 5 percent, Rate Limit: none, Buffer size: 15 percent, Priority: Strict-high Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: video-sched, Forwarding class: video, Index: 22 Transmit rate: 10 percent, Rate Limit: none, Buffer size: 10 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: app-sched, Forwarding class: app, Index: 22 Transmit rate: 10 percent, Rate Limit: none, Buffer size: 10 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: mail-sched, Forwarding class: mail, Index: 22 Transmit rate: 5 percent, Rate Limit: none, Buffer size: 5 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: db-sched, Forwarding class: db, Index: 22 Transmit rate: 10 percent, Rate Limit: none, Buffer size: 10 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: erp-sched, Forwarding class: erp, Index: 22 Transmit rate: 10 percent, Rate Limit: none, Buffer size: 10 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: be-sched, Forwarding class: best-effort, Index: 20 Transmit rate: 35 percent, Rate Limit: none, Buffer size: 35 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 2897 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS High TCP 1 Scheduler: nc-sched, Forwarding class: network-control, Index: 22 Transmit rate: 5 percent, Rate Limit: none, Buffer size: 5 percent, Priority: Strict-high Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Meaning This output shows that the forwarding classes have been assigned to schedulers. Verifying That the Scheduler Map Has Been Applied to the Interface Purpose Action Meaning Related Documentation Verify that the scheduler map has been applied to the interface. user@switch> show class-of-service interface ... Physical interface: ge-0/0/20, Index: 149 Queues supported: 8, Queues in use: 8 Scheduler map: ethernet-cos-map, Index: 43366 Input scheduler map: , Index: 3 ... This output shows that the scheduler map (ethernet-cos-map) has been applied to the interface (ge-0/0/20). • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 • Defining CoS Classifiers (CLI Procedure) on page 2914 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 • Defining CoS Schedulers (CLI Procedure) on page 2920 • Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Configuring Firewall Filters (CLI Procedure) on page 2779 Example: Combining CoS with MPLS on J-EX Series Switches You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. The CoS value is included within the MPLS label, which is passed through the network, enabling end-to-end CoS across the network. MPLS services are often used to ensure better performance for low-latency applications such as VoIP and other business-critical functions. These applications place specific demands on a network for successful transmission. CoS gives you the ability to control the mix of bandwidth, delay, jitter, and packet loss while taking advantage of the MPLS labeling mechanism. 2898 Chapter 108: Examples: CoS Configuration This example shows how to configure CoS on an MPLS network that is using a unidirectional circuit cross-connect (CCC) from the ingress provider edge (PE) switch to the egress PE switch. for the customer-edge interface of the ingress provider edge (PE) switch. It describes adding the configuration of CoS components to the ingress PE switch, the egress PE switch, and the core provider switches of the existing MPLS network. Because of the unidirectional configuration, the DSCP classifier needs to be configured only on the ingress PE switch. • Requirements on page 2899 • Overview and Topology on page 2899 • Configuring the Local PE Switch on page 2901 • Configuring the Remote PE Switch on page 2903 • Configuring the Provider Switch on page 2904 • Verification on page 2905 Requirements This example uses the following hardware and software components: • Three J-EX Series switches Before you configure CoS with MPLS, be sure you have: Configured an MPLS network with two PE switches and one provider switch. See “Example: Configuring MPLS on J-EX Series Switches” on page 3071. This example assumes that an MPLS network has been configured using a cross circuit-connect (CCC). Overview and Topology This example describes adding custom classifiers and custom rewrite rules to switches in an MPLS network that is using MPLS over CCC. It is a unidirectional configuration. Therefore, you need to configure custom classifiers and custom rewrite rules as follows: • On the ingress PE switch: custom DSCP classifier and custom EXP rewrite rule • On the egress PE switch: custom EXP classifier • On the provider switch: customer EXP classifier and custom EXP rewrite rule NOTE: You can also configure schedulers and shapers as needed. If you are using assured-forwarding, expedited-forwarding, or other custom forwarding classes, we recommend that you configure a scheduler to support that forwarding class. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. The example creates a custom DSCP classifier (dscp1) on the ingress PE switch and binds this classifier to the CCC interface. It includes configuration of a policer on the ingress PE switch. The policer is applied as a filter on the label-switched path (LSP) lsp_to_pe2_ge1(created in “Example: Configuring MPLS on J-EX Series Switches” on 2899 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS page 3071) to ensure that the amount of traffic forwarded through the LSP never exceeds the requested bandwidth allocation. This example creates a custom EXP rewrite rule (exp1) on the ingress PE switch, specifying a loss-priority and code point to be used for the expedited-forwarding class as the packet travels through the LSP. The switch applies this custom rewrite rule on the core interfaces ge-0/0/5.0 and ge-0/0/6.0, which are the egress interfaces for this switch. Table 366 on page 2900 shows the CoS configuration components added to the ingress PE switch. Table 366: CoS Configuration Components on the Ingress PE Switch Property Settings Description Local PE switch hardware J-EX Series switch PE-1 Policing filter configured and applied to the LSP. policing filter mypolicer Name of the rate-limiting policer. filter myfilter Name of the filter, which refers to the policer Custom DSCP classifier dscp1 Specifies the name of the custom DSCP classifier Custom EXP rewrite rule e1 Name of the custom EXP rewrite rule. Customer-edge interface ge-0/0/1.0 Interface that receives packets from devices outside the network. The custom DSCP classifier must be specified on this CCC interface. Core interfaces ge-0/0/5.0 and ge-0/0/6.0 Interfaces that transmit MPLS packets to other switches within the MPLS network. The EXP rewrite rule is applied implicitly to these interfaces. Table 367 on page 2900 shows the CoS configuration components added to the egress PE switch in this example. Table 367: CoS Configuration Components of the Egress PE Switch Property Settings Description Remote provider edge switch hardware J-EX Series switch PE-2 Custom EXP classifier exp1 Name of custom EXP classifier 2900 Chapter 108: Examples: CoS Configuration Table 367: CoS Configuration Components of the Egress PE Switch (continued) Property Settings Description Customer-edge interface ge-0/0/1.0 Interface that transmits packets from this network to devices outside the network. No CoS classifier is specified for this interface. A scheduler can be specified. Core interfaces ge-0/0/7.0 and ge-0/0/8.0 Core interfaces on PE-2 that receive MPLS packets from the provider switch. The EXP classifier is enabled by default on the switch and applied implicitly to these interfaces. Table 368 on page 2901 shows the MPLS configuration components used for the provider switch in this example. Table 368: CoS Configuration Components of the Provider Switch Property Settings Description Provider switch hardware J-EX Series switch Transit switch within the MPLS network configuration. Custom EXP classifier exp1 Name of the custom EXP classifier. Custom EXP rewrite rule e1 Name of the custom EXP rewrite rule. Core interfaces receiving packets from other MPLS switches. ge-0/0/5.0 and ge-0/0/6.0 Interfaces that connect the provider switch to the ingress PE switch (PE-1). The EXP classifier is enabled by default on the switch and applied implicitly to these interfaces. Core interfaces transmitting packets to other switches within the MPLS network. ge-0/0/7.0 and ge-0/0/8.0 Interfaces that transmit packets to the egress PE (PE-2). The EXP rewrite rule is applied implicitly on these interfaces. Schedulers can also be specified and will be applied to these interfaces. Configuring the Local PE Switch CLI Quick Configuration To quickly configure a custom DSCP classifier, custom EXP rewrite rule, and a policer on the local PE switch, copy the following commands and paste them into the switch terminal window of PE-1: [edit] set class-of-service classifiers dscp dscp1 import default set class-of-service classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 set class-of-service rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1 set firewall policer mypolicer if-exceeding bandwidth-limit 500m 2901 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS set firewall policer mypolicer if-exceeding burst-size-limit 33553920 set firewall policer mypolicer then discard set firewall family any filter myfilter term t1 then policer mypolicer set protocols mpls label-switched-path lsp_to_pe2_ge1 to 127.1.1.3 policing filter myfilter Step-by-Step Procedure To configure a custom DSCP classifier, custom EXP rewrite rule, and a policer on the ingress PE switch: 1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating: [edit class-of-service] user@switch# set classifiers dscp dscp1 import default 2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch# set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 4. Bind the DSCP classifier to the CCC interface: [edit ] user@switch# set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1 5. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the LSP: [edit firewall] set policer mypolicer if-exceeding bandwidth-limit 500m 6. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer: [edit firewall policer] set mypolicer if-exceeding burst-size-limit 33553920 7. Discard traffic that exceeds the rate limits for this policer: [edit firewall policer] set mypolicer then discard 8. To reference the policer, configure a filter term that includes the policer action: [edit firewall] user@switch# set family any filter myfilter term t1 then policer mypolicer 9. Apply the filter to the LSP: [edit protocols mpls] set label-switched-path lsp_to_pe2_ge1 policing filter myfilter Results Display the results of the configuration: [edit] 2902 Chapter 108: Examples: CoS Configuration user@switch# show class-of-service { classifiers { dscp dscp1 { import default; forwarding-class expedited-forwarding { loss-priority low code-points 000111; } } } interfaces { ge-0/0/1 { unit 0 { classifiers { dscp dscp1; } } } } rewrite-rules { exp e1 { forwarding-class expedited-forwarding { loss-priority low code-point 111; } } } } firewall { family any { filter myfilter { term t1 { then policer mypolicer; } } } policer mypolicer { if-exceeding { bandwidth-limit 500m; burst-size-limit 33553920; } then discard; } } Configuring the Remote PE Switch CLI Quick Configuration To quickly configure a custom EXP classifier on the remote PE switch, copy the following commands and paste them into the switch terminal window of PE-2: [edit] set class-of-service classifiers exp exp1 import default set class-of-service classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 2903 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Step-by-Step Procedure To configure a custom EXP classifier on the egress PE switch: 1. Import the default EXP classifier classes to the custom EXP classifier that you are creating: [edit class-of-service] user@switch# set classifiers exp exp1 import default 2. Add the expedited-forwarding class to this custom EXP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch# set classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 Results Display the results of the configuration: [edit] user@switch# show class-of-service { classifiers { exp exp1 { import default; forwarding-class expedited-forwarding { loss-priority low code-points 010; } } Configuring the Provider Switch CLI Quick Configuration To quickly configure a custom EXP classifier and a custom EXP rewrite rule on the provider switch, copy the following commands and paste them into the switch terminal window of the provider switch: [edit] set class-of-service classifiers exp exp1 import default set class-of-service classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 set class-of-service rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 Step-by-Step Procedure To configure a custom EXP classifier and a custom EXP rewrite rule on the provider switch: 1. Import the default EXP classifier classes to the custom EXP classifier that you are creating: [edit class-of-service] user@switch# set classifiers exp exp1 import default 2. Add the expedited-forwarding class to this custom EXP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch# set classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 3. 2904 Specify the values for the custom EXP rewrite rule, e1: Chapter 108: Examples: CoS Configuration [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 Results Display the results of the configuration: [edit] user@switch# show class-of-service { classifiers { exp exp1 { import default; forwarding-class expedited-forwarding { loss-priority low code-points 010; } } } rewrite-rules { exp e1 { forwarding-class expedited-forwarding { loss-priority low code-point 111; } } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That the Policer Firewall Filter Is Operational on page 2905 • Verifying That the CoS Classifiers Are Going to the Right Queue on page 2905 • Verifying the CoS Forwarding Table Mapping on page 2908 • Verifying the Rewrite Rules on page 2909 Verifying That the Policer Firewall Filter Is Operational Purpose Action Meaning Verify the operational state of the policer that is configured on the ingress PE switch. user@switch> show firewall Filter: myfilter Policers: Name mypolicer-t1 Packets 0 This output shows that the firewall filter mypolicer has been created. Verifying That the CoS Classifiers Are Going to the Right Queue Purpose Action Verify that the CoS classifiers are going to the right queue. user@switch> show class-of-service forwarding-table classifier Classifier table index: 7, # entries: 64, Table type: DSCP 2905 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Entry # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 2906 Code point 000000 000001 000010 000011 000100 000101 000110 000111 001000 001001 001010 001011 001100 001101 001110 001111 010000 010001 010010 010011 010100 010101 010110 010111 011000 011001 011010 011011 011100 011101 011110 011111 100000 100001 100010 100011 100100 100101 100110 100111 101000 101001 101010 101011 101100 101101 101110 101111 110000 110001 110010 110011 110100 110101 110110 110111 111000 111001 111010 111011 Forwarding-class # 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 PLP Chapter 108: Examples: CoS Configuration 60 61 62 63 111100 111101 111110 111111 3 3 3 3 0 0 0 0 Classifier table index: 11, # entries: 8, Table type: IEEE 802.1 Entry # Code point Forwarding-class # PLP 0 000 0 0 1 001 0 0 2 010 0 0 3 011 0 0 4 100 0 0 5 101 0 0 6 110 3 0 7 111 3 0 Classifier table index: 12, # entries: 8, Table type: IPv4 precedence Entry # Code point Forwarding-class # PLP 0 000 0 0 1 001 0 0 2 010 0 0 3 011 0 0 4 100 0 0 5 101 0 0 6 110 3 0 7 111 3 0 Classifier table index: 16, # entries: 8, Table type: Untrust Entry # Code point Forwarding-class # PLP 0 000 0 0 1 001 0 0 2 010 0 0 3 011 0 0 4 100 0 0 5 101 0 0 6 110 0 0 7 111 0 0 Classifier table index: 9346, # entries: 64, Table type: DSCP Entry # Code point Forwarding-class # PLP 0 000000 0 0 1 000001 0 0 2 000010 0 0 3 000011 0 0 4 000100 0 0 5 000101 0 0 6 000110 0 0 7 000111 1 0 8 001000 0 0 9 001001 0 0 10 001010 0 0 11 001011 0 0 12 001100 0 0 13 001101 0 0 14 001110 0 0 15 001111 0 0 16 010000 0 0 17 010001 0 0 18 010010 0 0 19 010011 0 0 20 010100 0 0 2907 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Meaning 010101 010110 010111 011000 011001 011010 011011 011100 011101 011110 011111 100000 100001 100010 100011 100100 100101 100110 100111 101000 101001 101010 101011 101100 101101 101110 101111 110000 110001 110010 110011 110100 110101 110110 110111 111000 111001 111010 111011 111100 111101 111110 111111 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This output shows that a new DSCP classifier has been created, index 9346, on the ingress PE switch (PE-1). Verifying the CoS Forwarding Table Mapping Purpose Action For each logical interface, display either the table index of the classifier for a given code point type or the queue number (if it is a fixed classification) in the forwarding table. user@switch>show class-of-service forwarding-table classifier mapping Table Index/ 2908 Chapter 108: Examples: CoS Configuration Interface ge-0/0/1.0 Meaning Index 92 Q num 9346 Table type DSCP The results show that the new DSCP classifier, index number 9346, is bound to interface ge-0/0/1.0. Verifying the Rewrite Rules Purpose Action Display mapping of the queue number and loss priority to code point value for each rewrite rule as it exists in the forwarding table. user@switch>show class-of-service forwarding-table rewrite-rule Rewrite FC# 0 1 2 3 table index: 31, # entries: 4, Table type: DSCP Low bits State High bits State 000000 Enabled 000000 Enabled 101110 Enabled 101110 Enabled 001010 Enabled 001100 Enabled 110000 Enabled 111000 Enabled Rewrite table index: 34, # entries: 4, Table type: IEEE 802.1 FC# Low bits State High bits State 0 000 Enabled 001 Enabled 1 010 Enabled 011 Enabled 2 100 Enabled 101 Enabled 3 110 Enabled 111 Enabled Rewrite table index: 35, # entries: 4, Table type: IPv4 precedence FC# Low bits State High bits State 0 000 Enabled 000 Enabled 1 101 Enabled 101 Enabled 2 001 Enabled 001 Enabled 3 110 Enabled 111 Enabled Rewrite table index: 9281, # entries: 1, Table type: EXP FC# Low bits State High bits State 1 111 Enabled 000 Disabled Meaning Related Documentation This output shows that a new EXP classifier with the index number 9281 has been created. • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 • Monitoring CoS Forwarding Classes on page 2936 2909 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2910 CHAPTER 109 Configuring CoS • Configuring CoS (J-Web Procedure) on page 2911 • Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 • Defining CoS Classifiers (CLI Procedure) on page 2914 • Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 • Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Defining CoS Schedulers (CLI Procedure) on page 2920 • Defining CoS Schedulers (J-Web Procedure) on page 2920 • Defining CoS Scheduler Maps (J-Web Procedure) on page 2923 • Defining CoS Drop Profiles (J-Web Procedure) on page 2923 • Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 • Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Configuring Junos OS EZQoS for CoS (CLI Procedure) on page 2930 • Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI Procedure) on page 2931 • Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) on page 2932 Configuring CoS (J-Web Procedure) The Class of Service Configuration pages allow you to configure the Junos OS CoS components. You can configure forwarding classes for transmitting packets, define which packets are placed into each output queue, and schedule the transmission service level for each queue. After defining the CoS components you must assign classifiers to the required physical and logical interfaces. 2911 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Using the Class of Service Configuration pages, you can configure various CoS components individually or in combination to define particular CoS services. To configure CoS components : 1. In the J-Web interface, select Configure>Class of Service. 2. On the Class of Service Configuration page, select one of the following options depending on the CoS component that you want to define. Enter information into the pages as described in the respective table: • To define or edit CoS value aliases, select CoS Value Aliases . • To define or edit forwarding classes and assign queues, select Forwarding Classes. • To define or edit classifiers, select Classifiers . • To define or edit rewrite rules, select Rewrite Rules. • To define or edit schedulers, select Schedulers. • To define or edit virtual channel groups, select Interface Associations. 3. Click Apply after completing configuration on any Configuration page. Related Documentation • Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Defining CoS Schedulers (J-Web Procedure) on page 2920 • Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 Defining CoS Code-Point Aliases (J-Web Procedure) You can use the J-Web interface to define CoS code-point aliases on a J-EX Series switch. By defining aliases you can assign meaningful names to a particular set of bit values and refer to them when configuring CoS components. To define CoS code-point aliases: 1. Select Configure > Class of Service > CoS Value Aliases. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2912 Chapter 109: Configuring CoS 2. Click one: • Add—Adds a code-point alias. Enter information into the code point alias page as described in Table 369 on page 2913. • Edit—Modifies an existing code-point alias. Enter information into the code point alias page as described in Table 369 on page 2913. • Delete—Deletes an existing code-point alias. Table 369 on page 2913 describes the related fields. Table 369: CoS Value Aliases Configuration Fields Field Function Your Action Code point name Specifies the name for a code-point—for example, af11 or be. Enter a name. Code point type Specifies a code-point type. The code-point type can be DSCP or IP precedence. Select a value. Code point value bits Specifies the CoS value for which an alias is defined. To specify a CoS value, type it in the appropriate format: Changing this value alters the behavior of all classifiers that refer to this alias. • For DSCP CoS values, use the format xxxxxx, where x is 1 or 0—for example, 101110. • For IP precedence CoS values, use the format xxx, where x is 1 or 0—for example, 111. Related Documentation • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 • Monitoring CoS Value Aliases on page 2940 • Example: Configuring CoS on J-EX Series Switches on page 2883 2913 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Defining CoS Code-Point Aliases (CLI Procedure) You can use code-point aliases to streamline the process of configuring CoS features on your J-EX Series switch. A code-point alias assigns a name to a pattern of code-point bits. You can use this name instead of the bit pattern when you configure other CoS components such as classifiers, drop-profile maps, and rewrite rules. You can configure code-point aliases for the following CoS marker types: • DSCP—Handles incoming IPv4 packets. • IEEE 802.1p—Handles Layer 2 CoS. • Inet precedence—Handles incoming IPv4 packets. IP precedence mapping requires only the higher order three bits of the DSCP field. To configure a code-point alias for a specified CoS marker type (dscp), assign an alias (my1) to the code-point (110001): [edit class-of-service code-point-aliases] user@switch# set dscp my1 110001 Related Documentation • Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Value Aliases on page 2940 • Understanding CoS Code-Point Aliases on page 2864 Defining CoS Classifiers (CLI Procedure) Packet classification associates incoming packets with a particular CoS servicing level. Classifiers associate packets with a forwarding class and loss priority and assign packets to output queues based on the associated forwarding class. The Junos OS supports two general types of classifiers: • Behavior aggregate or CoS value traffic classifiers—Examines the CoS value in the packet header. The value in this single field determines the CoS settings applied to the packet. BA classifiers allow you to set the forwarding class and loss priority of a packet based on the Differentiated Services code point (DSCP) value, IP precedence value, or IEEE 802.1p value. • Multifield traffic classifiers—Examines multiple fields in the packet such as source and destination addresses and source and destination port numbers of the packet. With multifield classifiers, you set the forwarding class and loss priority of a packet based on firewall filter rules. The following example describes how to configure a BA classifier ba-classifier as the default DSCP map and apply it to either a specific Gigabit Ethernet interface or to all the Gigabit Ethernet interfaces on the switch. The BA classifier assigns loss priorities, as shown in Table 370 on page 2915, to incoming packets in the four forwarding classes. 2914 Chapter 109: Configuring CoS You can use the same procedure to set multifield classifiers (except that you would use firewall filter rules). Table 370: BA-classifier Loss Priority Assignments Forwarding Class For CoS Traffic Type ba-classifier Assignment be Best-effort traffic High-priority code point: 000001 ef Expedited-forwarding traffic High-priority code point: 101110 af Assured-forwarding traffic High-priority code point: 001100 nc Network-control traffic High-priority code point: 110001 To configure a DSCP BA classifier named ba-classifier as the default DSCP map: • Associate code point 000001 with forwarding class be and loss priority high: [edit class-of-service classifiers] user@switch# set dscp ba-classifier import default forwarding-class be loss-priority high code-points 000001 • Associate code point 101110 with forwarding class ef and loss priority high: [edit class-of-service classifiers] user@switch# set dscp ba-classifier forwarding-class ef loss-priority high code-points 101110 • Associate code point 001100 with forwarding class af and loss priority high: [edit class-of-service classifiers] user@switch# set dscp ba-classifier forwarding-class af loss-priority high code-points 001100 • Associate code point 110001 with forwarding class nc and loss priority high: [edit class-of-service classifiers] user@switch# set dscp ba-classifier forwarding-class nc loss-priority high code-points 110001 • Apply the classifier to a specific interface or to all Gigabit Ethernet interfaces on the switch. • To apply the classifier to a specific interface: [edit class-of-service interfaces] user@switch# set ge-0/0/0 unit 0 classifiers dscp ba-classifier • To apply the classifier to all Gigabit Ethernet interfaces on the switch, use wildcards for the interface name and the logical-interface (unit) number: [edit class-of-service interfaces] user@switch# set ge-* unit * classifiers dscp ba-classifier 2915 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Defining CoS Classifiers (J-Web Procedure) on page 2916 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Monitoring CoS Classifiers on page 2935 • Understanding CoS Classifiers on page 2867 Defining CoS Classifiers (J-Web Procedure) You can use the J-Web interface to define CoS classifiers on a J-EX Series switch. Classifiers examine the CoS value or alias of an incoming packet and assign the packet a level of service by setting its forwarding class and loss priority. To define CoS classifiers: 1. Select Configure > Class of Service > Classifiers. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one: • Add—Adds a classifier. Enter information into the classifier page as described in Table 371 on page 2916. • Edit—Modifies an existing classifier. Enter information into the classifier page as described in Table 371 on page 2916. • Delete—Deletes an existing classifier. Table 371: Classifiers Configuration Fields Field Function Your Action Classifier Name Specifies the name for a classifier. To name a classifier, type the name—for example, ba-classifier. Classifier Type Specifies the type of classifier: dscp, ieee-802.1, or inet-precedence. Select a value from the list. 2916 Chapter 109: Configuring CoS Table 371: Classifiers Configuration Fields (continued) Field Function Your Action Code Point Mapping Sets the forwarding classes and the packet loss priorities (PLPs) for specific CoS values and aliases. To add a code point mapping: 1. Click Add. 2. Select the code point. 3. Select a forwarding class from the following list: • expedited-forwarding—Provides low loss, low delay, low jitter, assured bandwidth, and end-to-end service. Packets can be forwarded out of sequence or dropped. • best-effort—Provides no special CoS handling of packets. Typically, RED drop profile is aggressive and no loss priority is defined. • assured-forwarding—Provides high assurance for packets within the specified service profile. Excess packets are dropped. • network-control—Packets can be delayed but not dropped. 4. Select the loss priority. To assign a loss priority, select one: Related Documentation • high—Packet has a high loss priority. • low—Packet has a low loss priority. • Defining CoS Classifiers (CLI Procedure) on page 2914 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Classifiers on page 2935 • Understanding CoS Classifiers on page 2867 2917 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Defining CoS Forwarding Classes (CLI Procedure) Forwarding classes allow you to group packets for transmission. Based on forwarding classes, you assign packets to output queues. By default, four categories of forwarding classes are defined: best effort, assured forwarding, expedited forwarding, and network control. J-EX Series switches support up to 16 forwarding classes. You can configure forwarding classes in one of the following ways: • Using class statement—You can configure up to 16 forwarding classes and you can map multiple forwarding classes to single queue. • Using queue statement—You can configure up to 8 forwarding classes and you can map one forwarding class to one queue. This example uses the class statement to configure forwarding classes. To configure CoS forwarding classes, map the forwarding classes to queues: [edit class-of-service forwarding-classes] user@switch# set class be queue—num 0 user@switch# set class ef queue—num 1 user@switch# set class af queue—num 2 user@switch# set class nc queue—num 3 user@switch# set class ef1 queue—num 4 user@switch# set class ef2 queue—num 5 user@switch# set class af1 queue—num 6 user@switch# set class nc1 queue—num 7 Related Documentation • Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Monitoring CoS Forwarding Classes on page 2936 • Understanding CoS Forwarding Classes on page 2870 Defining CoS Forwarding Classes (J-Web Procedure) You can define CoS forwarding classes on a J-EX Series switch using the J-Web interface. Assigning a forwarding class to a queue number affects the scheduling and marking of a packet as it transits a switch. To define forwarding classes: 1. 2918 Select Configure > Class of Service > Forwarding Classes. Chapter 109: Configuring CoS NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one: • Add—Adds a forwarding class. Enter information into the forwarding class page as described in Table 372 on page 2919. • Edit—Modifies an existing forwarding class. Enter information into the forwarding class page as described in Table 372 on page 2919. • Delete—Deletes an existing forwarding class. Table 372: Forwarding Classes Configuration Fields Field Function Your Action Forwarding Class Summary Queue # Specifies the internal queue numbers to which forwarding classes are assigned. To specify an internal queue number, select an integer from 0 through 7, appropriate for your platform. By default, if a packet is not classified, it is assigned to the class associated with queue 0. You can have more than one forwarding class to a queue number. Forwarding Class Name Specifies the forwarding class names assigned to specific internal queue numbers. Type the name—for example, be-class. By default, four forwarding classes are assigned to queue numbers 0 (best-effort), 1 (assured-forwarding), 5 (expedited-forwarding), and 7 (network-connect). Related Documentation • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Forwarding Classes on page 2936 • Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Understanding CoS Forwarding Classes on page 2870 2919 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Defining CoS Schedulers (CLI Procedure) You use schedulers to define the CoS properties of output queues. These properties include the amount of interface bandwidth assigned to the queue, the size of the memory buffer allocated for storing packets, the priority of the queue, and the tail drop profiles associated with the queue. You associate the schedulers with forwarding classes by means of scheduler maps. You can then associate each scheduler map with an interface, thereby configuring the queues and packet schedulers that operate according to this mapping. You can associate up to four user-defined scheduler maps with the interfaces. To configure CoS schedulers using the CLI: 1. Create a scheduler (be-sched) with low priority: [edit class-of-service schedulers] user@switch# set be-sched priority low 2. Configure a scheduler map (be-map) that associates the scheduler (be-sched) with the forwarding class (best-effort): [edit class-of-service scheduler-maps] user@switch# set be-map forwarding-class best-effort scheduler be-sched 3. Assign the scheduler map (be-map) to an Ethernet interface (ge-0/0/1): [edit class-of-service interfaces] user@switch# set ge-0/0/1 scheduler-map be-map 4. Alternatively to assign the scheduler map (be-map) to all the Ethernet interfaces using wild cards (ge-*): [edit class-of-service interfaces] user@switch# set ge-* scheduler-map be-map Related Documentation • Defining CoS Schedulers (J-Web Procedure) on page 2920 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Monitoring CoS Scheduler Maps on page 2939 • Understanding CoS Schedulers on page 2873 Defining CoS Schedulers (J-Web Procedure) You can use the J-Web interface to define CoS schedulers on a J-EX Series switch. Using schedulers, you can assign attributes to queues and thereby provide congestion control for a particular class of traffic. These attributes include the amount of interface bandwidth, memory buffer size, transmit rate, and schedule priority. To configure schedulers: 2920 Chapter 109: Configuring CoS 1. Select Configure > Class of Service > Schedulers. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one: • Add—Adds a scheduler. Enter information into the schedulers page as described in Table 373 on page 2921. • Edit—Modifies an existing scheduler. Enter information into the schedulers page as described in Table 373 on page 2921. • Delete—Deletes an existing scheduler. Table 373: Schedulers Configuration Page Field Function Your Action Scheduler Name Specifies the name for a scheduler. To name a scheduler, type the name—for example, be-scheduler. Scheduling Priority Sets the transmission priority of the scheduler, which determines the order in which an output interface transmits traffic from the queues. To set a priority, select one: • low—Packets in this queue are transmitted last. You can set scheduling priority at different levels in the order of increasing priority from low to high. • strict-high—Packets in this queue are transmitted first. • To specify no scheduling priority, select the blank. A high-priority queue with a high transmission rate might lock out lower-priority traffic. 2921 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 373: Schedulers Configuration Page (continued) Field Function Your Action Buffer Size Defines the size of the delay buffer. To define a delay buffer size for a scheduler, select the appropriate option: By default, queues 0 through 7 are allotted the following percentage of the total available buffer space: • Queue 0—95 percent • Queue 1—0 percent • Queue 2—0 percent • Queue 3—0 percent • Queue 4—0 percent • Queue 5—0 percent • Queue 6—0 percent • Queue 7—5 percent • To specify no buffer size, select the blank. • To specify buffer size as a percentage of the total buffer, select Percent and type an integer from 1 through 100. • To specify buffer size as the remaining available buffer, select Remainder. NOTE: On J-EX8200 switches, you can specify the buffer size as a temporal value. The queuing algorithm will then drop packets once it has queued a computed number of bytes. This number is the product of the logical interface speed and the configured temporal value. NOTE: A large buffer size value correlates with a greater possibility of packet delays. Such a value might not be practical for sensitive traffic such as voice or video. Shaping Rate Specifies the rate at which queues transmit packets. Transmit Rate Defines the transmission rate of a scheduler. The transmit rate determines the traffic bandwidth from each forwarding class you configure. By default, queues 0 through 7 are allotted the following percentage of the transmission capacity: Related Documentation 2922 • Queue 0—95 percent • Queue 1—0 percent • Queue 2—0 percent • Queue 3—5 percent • Queue 4—0 percent • Queue 6—0 percent • Queue 7—5 percent • To specify shaping rate as a percentage, select Percent and type an integer from 1 through 100. • To specify shaping rate as a number, select Rate and enter a value. • To specify no shaping rate, select the blank. To define a transmit rate, select the appropriate option: • To enforce the exact transmission rate, select Rate and enter a value. • To specify the remaining transmission capacity, select Remainder Available. • To specify a percentage of transmission capacity, select Percent and type an integer from 1 through 100. • To specify no transmit rate, select the blank. • Defining CoS Schedulers (CLI Procedure) on page 2920 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Scheduler Maps on page 2939 Chapter 109: Configuring CoS Defining CoS Scheduler Maps (J-Web Procedure) You can use the J-Web interface to configure CoS scheduler maps on a J-EX Series switch. To configure scheduler maps: 1. Select Configure > Class of Service > Scheduler Maps. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one: • Add—Adds a scheduler map. Enter information into the scheduler map page as described in Table 374 on page 2923. • Edit—Modifies an existing scheduler map. Enter information into the scheduler map page as described in Table 374 on page 2923. • Delete—Deletes an existing scheduler map. Table 374: Scheduler Maps Configuration Fields Field Function Your Action Scheduler Map Name Specifies the name for a scheduler map. To name a map, type the name—for example, be-scheduler-map. Scheduler Mapping Allows you to associate a preconfigured scheduler with a forwarding class. To associate a scheduler with a forwarding class, locate the forwarding class and select the scheduler in the box next to it. After scheduler maps have been applied to an interface, they affect the hardware queues and packet schedulers. Related Documentation For example, for the best-effort forwarding class, select the configured scheduler from the list. • Defining CoS Schedulers (J-Web Procedure) on page 2920 • Defining CoS Schedulers (CLI Procedure) on page 2920 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Scheduler Maps on page 2939 Defining CoS Drop Profiles (J-Web Procedure) You can use the J-Web interface to define CoS drop profiles on J-EX8200 switches. 2923 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To configure CoS drop profiles: 1. Select Configure > Class of Service > Drop Profile. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one: • Add—Adds a drop profile. Enter information into the drop profiles page as described in Table 375 on page 2924. • Edit—Modifies an existing drop file. Enter information into the drop profiles page as described in Table 375 on page 2924. • Delete—Deletes an existing drop profile. Table 375: Drop Profiles Configuration parameters Field Function Your Action Drop Profile Name Specifies the name for a drop profile. Type the name. Drop profile graph Specifies the drop profile graph type Select one: Segmented or Interpolated. Drop profile values Specifies values for the following two parameters of the drop profile: the queue fill level and the drop probability. To add new values: The queue fill level represents a percentage of the memory used to store packets in relation to the total amount that has been allocated for that specific queue. The drop probability is a percentage value that correlates to the likelihood that an individual packet is dropped from the network. 1. Click Add. 2. Enter the fill level. 3. Enter the drop probability. 4. Click OK. To edit an existing value, click Edit and modify the fill level and drop probability. To delete a value, select it and click Delete. Related Documentation 2924 • Monitoring CoS Drop Profiles on page 2941 • Example: Configuring CoS on J-EX Series Switches on page 2883 Chapter 109: Configuring CoS Configuring CoS Tail Drop Profiles (CLI Procedure) Tail drop is a simple and effective traffic congestion avoidance mechanism. When you apply this mechanism to manage congestion, packets are dropped when the output queue is full. To configure CoS tail-drop profiles, create a drop profile name (be-dp) and assign a fill level (25): [edit class-of-service drop-profiles] user@switch# set be-dp fill-level 25 Related Documentation • Example: Configuring CoS on J-EX Series Switches on page 2883 • Understanding CoS Tail Drop Profiles on page 2872 Defining CoS Rewrite Rules (CLI Procedure) You configure rewrite rules to alter CoS values in outgoing packets on the outbound interfaces of a J-EX Series switch to match the policies of a targeted peer. Policy matching allows the downstream routing platform or switch in a neighboring network to classify each packet into the appropriate service group. To configure a CoS rewrite rule, create the rule by giving it a name and associating it with a forwarding class, loss priority, and a code point, thus creating a rewrite table. After the rewrite rule is created, enable it on an interface. You can also apply an existing rewrite rule on an interface. NOTE: To replace an existing rewrite rule on the interface with a new rewrite rule of the same type, first explicitly remove the rewrite rule and then apply the new rule. NOTE: Custom rewrite-rule bindings are implemented through filters. And custom rewrite rules cannot be bound to routed VLAN interfaces (RVIs). To create rewrite rules and enable them on interfaces: • To create an 802.1p rewrite rule named customup-rw in the rewrite table for all Layer 2 interfaces: [edit class-of-service rewrite-rules] user@switch# set ieee-802.1 customup-rw forwarding-class be loss-priority low code-point 000 user@switch# set ieee-802.1 customup-rw forwarding-class be loss-priority high code-point 001 user@switch# set ieee-802.1 customup-rw forwarding-class af loss-priority low code-point 010 user@switch# set ieee-802.1 customup-rw forwarding-class af loss-priority high code-point 011 2925 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch# set ieee-802.1 customup-rw forwarding-class ef loss-priority low code-point 100 user@switch# set ieee-802.1 customup-rw forwarding-class ef loss-priority high code-point 101 user@switch# set ieee-802.1 customup-rw forwarding-class nc loss-priority low code-point 110 user@switch# set ieee-802.1 customup-rw forwarding-class nc loss-priority high code-point 111 • To enable an 802.1p rewrite rule named customup-rw on a Layer 2 interface: [edit] user@switch# set class-of-service interfaces ge-0/0/0 unit 0 rewrite-rules ieee-802.1 customup-rw • To enable an 802.1p rewrite rule named customup-rw on all Gigabit Ethernet interfaces on the switch, use wildcards for the interface name and logical-interface (unit) number: [edit] user@switch# set class-of-service interfaces ge-* unit * rewrite-rules customup-rw Related Documentation • Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Rewrite Rules on page 2938 • Understanding CoS Rewrite Rules on page 2876 Defining CoS Rewrite Rules (J-Web Procedure) You can use the J-Web interface to define CoS rewrite rules. Use the rewrite rules to alter the CoS values in outgoing packets to meet the requirements of the targeted peer. A rewrite rule examines the forwarding class and loss priority of a packet and sets its bits to a corresponding value specified in the rule. To define rewrite rules: 1. Select Configure > Class of Service > Rewrite Rules. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. Click one: • Add—Adds a rewrite rule. Enter information into the rewrite rule page as described in Table 376 on page 2927. • Edit—Modifies an existing rewrite rule. Enter information into the rewrite rule page as described in Table 376 on page 2927. 2926 Chapter 109: Configuring CoS • Delete—Deletes an existing rewrite rule. Table 376: Rewrite Rules Configuration Page Summary Field Function Your Action Rewrite Rule Name Specifies the name for the rewrite rule. To name a rule, type the name—for example, rewrite-dscps. Rewrite rule type Specifies the type of rewrite rule: dscp, ieee-802.1, or inet-precedence. Select a value from the list. Code Point Mapping Rewrites outgoing CoS values of a packet based on the forwarding class and loss priority. To configure a CoS value assignment, follow these steps: Allows you to remove a code point mapping entry. To add a code point mapping: 1. Click Add. 2. Select the code point. 3. Select a forwarding class from the following list: • expedited-forwarding—Provides low loss, low delay, low jitter, assured bandwidth, and end-to-end service. Packets can be forwarded out of sequence or dropped. • best-effort—Provides no special CoS handling of packets. Typically, RED drop profile is aggressive and no loss priority is defined. • assured-forwarding—Provides high assurance for packets within the specified service profile. Excess packets are dropped. • network-control—Packets can be delayed but not dropped. 4. Select the loss priority. To assign a loss priority, select one: • high—Packet has a high loss priority. • low—Packet has a low loss priority. To edit an existing code point mapping, select it and click Edit. To remove a code point mapping entry, select it and click Remove. Related Documentation • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 • Understanding CoS Rewrite Rules on page 2876 • Monitoring CoS Rewrite Rules on page 2938 • Example: Configuring CoS on J-EX Series Switches on page 2883 2927 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Assigning CoS Components to Interfaces (CLI Procedure) After you have defined the following CoS components, you must assign them to logical or physical interfaces. • Forwarding classes—Assign only to logical interfaces. • Classifiers—Assign only to logical interfaces. • Scheduler maps—Assign to either physical or logical interfaces. • Rewrite rules—Assign to either physical or logical interfaces. You can assign a CoS component to a single interface or to multiple interfaces using wild cards. To assign CoS components to interfaces: •To assign CoS components to a single interface, associate a CoS component (for example a scheduler map named ethernet-cos-map) with an interface: [edit class-of-service interfaces] user@switch# set ge-0/0/20 scheduler-map ethernet-cos-map •To assign a CoS component to multiple interfaces, associate a CoS component (for example, a rewrite rule named customup-rw) to all Gigabit Ethernet interfaces on the switch, use wild characters for the interface name and logical-interface (unit) number: [edit class-of-service interfaces] user@switch# set ge-* unit * rewrite-rules ieee-802.1 customup-rw Related Documentation • Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring Interfaces That Have CoS Components on page 2937 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 Assigning CoS Components to Interfaces (J-Web Procedure) After you have defined CoS components on a J-EX Series switch, you must assign them to logical or physical interfaces. You can use the J-Web interface to assign scheduler maps to physical or logical interfaces and to assign forwarding classes or classifiers to logical interfaces. To assign CoS components to interfaces: 2928 Chapter 109: Configuring CoS 1. Select Configure > Class of Service > Assign to Interface. NOTE: After you make changes to the configuration in this page, you must commit the changes immediately 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 334 for details about all commit options. 2. To configure interface association, select an interface from the list and click Edit. 3. Select one: • Associate system default scheduler map—Associates the interface with the default scheduler map. • Select the scheduler map—Associates the interface with a configured scheduler map. Select the scheduler map from the list. 4. Click OK. 5. To manage a CoS service assignment on a logical interface, click one: • Add—Adds a CoS service to a logical interface on a specified physical interface. Enter information as described in Table 377 on page 2929. • Edit—Modifies a CoS service assignment to a logical interface. Enter information as described in Table 377 on page 2929. • Delete—Deletes the CoS service assignment to a logical interface. Table 377: Assigning CoS Components to Logical Interfaces Field Function Your Action Unit Specifies the name of a logical interface. Allows you to assign CoS components while configuring a logical interface on a physical interface at the same time. Type the interface name. Forwarding Class Assigns a predefined forwarding class to incoming packets on a logical interface. To assign a forwarding class to an interface, select the forwarding class. Classifiers Allows you to apply classification maps to a logical interface. Classifiers assign a forwarding class and loss priority to an incoming packet based on its CoS value. To assign a classification map to an interface, select an appropriate classifier for each CoS value type used on the interface. Rewrite Rules Allows you to alter the CoS values in outgoing packets to meet the requirements of the targeted peer. A rewrite rule examines the forwarding class and loss priority of a packet and sets its bits to a corresponding value specified in the rule. To assign rewrite rules to the interface, select the appropriate rewrite rule for each CoS value type used on the interface. To assign CoS services to all logical interfaces configured on this physical interface, type the wildcard character (*). 2929 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring Interfaces That Have CoS Components on page 2937 Configuring Junos OS EZQoS for CoS (CLI Procedure) You use Junos OS EZQoS on J-EX Series switches to eliminate the complexities involved in configuring class of service (CoS) across the network. EZQoS offers templates for key traffic classes. When you configure EZQoS on J-EX Series switches, preconfigured values are assigned to all CoS parameters based on the typical application requirements. These preconfigured values are stored in a template with a unique name. NOTE: Currently, we provide an EZQoS template for configuring CoS for VoIP applications. The EZQoS VoIP template is stored in /etc/config/ezqos-voip.conf. To configure EZQoS using the CLI: 1. Load the EZQoS configuration file (/etc/config/ezqos-voip.conf): [edit] user@switch# load merge /etc/config/ezqos-voip.conf 2. Apply the EZQoS group (ezqos-voip): [edit] user@switch# set apply-groups ezqos-voip 3. Apply the DSCP classifier (ezqos-dscp-classifier) to a Gigabit Ethernet interface (ge-0/0/0): [edit class-of-service interfaces] user@switch# set ge-0/0/0 unit 0 classifiers dscp ezqos-dscp-classifier 4. Apply the scheduler map (ezqos-voip-sched-maps) to a Gigabit Ethernet interface (ge-0/0/1): [edit class-of-service interfaces] user@switch# set ge-0/0/1 scheduler-map ezqos-voip-sched-maps Related Documentation 2930 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Understanding Junos OS EZQoS for CoS Configurations on J-EX Series Switches on page 2879 Chapter 109: Configuring CoS Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI Procedure) You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. This topic describes configuring CoS components on a provider edge (PE) switch that is using IP Over MPLS. This task describes now to create a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE switch. It includes configuring a policer firewall filter and applying it to the customer-edge interface of the ingress PE switch. The policer firewall filter ensures that the amount of traffic forwarded through the MPLS tunnel never exceeds the requested bandwidth allocation. For this procedure, we assume that the switch has already been configured for MPLS. See “Configuring MPLS on Provider Edge Switches Using MPLS Over IP (CLI Procedure)” on page 3107. 1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating: [edit class-of-service] user@switch#set classifiers dscp dscp1 import default 2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch#set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 4. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the customer-edge-interface: [edit firewall] set policer mypolicer if-exceeding bandwidth-limit 500m 5. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer: [edit firewall policer] set mypolicer if-exceeding burst-size-limit 33553920 6. Discard traffic that exceeds the rate limits for this policer: [edit firewall policer] set mypolicer then discard 7. To reference the policer, configure a filter term that includes the policer action: [edit firewall] user@switch# set family inet filter myfilter term t1 then policer mypolicer 8. Apply the filter to the customer-edge interface: 2931 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit interfaces] user@switch# set ge-2/0/3 unit 0 family inet address 121.121.121.1/16 policing filter myfilter NOTE: You can also configure schedulers and shapers as needed. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. Related Documentation • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. This topic describes configuring CoS components on provider edge (PE) switch that is using MPLS over circuit-cross connect (CCC). NOTE: If you are using MPLS with CCC, you can use only one type of DSCP/IP precedence and only one type of IEEE 802.1p on the CCC interfaces. This procedure creates a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE. It also enables a policer on the label-switched path (LSP) of the ingress PE to ensure that the amount of traffic forwarded through the LSP never exceeds the requested bandwidth allocation. 1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating: [edit class-of-service] user@switch#set classifiers dscp dscp1 import default 2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch#set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 4. Bind the DSCP classifier to the CCC interface: 2932 Chapter 109: Configuring CoS [edit ] user@switch# set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1 5. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the LSP: [edit firewall] set policer mypolicer if-exceeding bandwidth-limit 500m 6. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer: [edit firewall policer] set mypolicer if-exceeding burst-size-limit 33553920 7. Discard traffic that exceeds the rate limits for this policer: [edit firewall policer] set mypolicer then discard 8. To reference the policer, configure a filter term that includes the policer action: [edit firewall] user@switch# set family any filter myfilter term t1 then policer mypolicer 9. Apply the filter to the LSP: [edit protocols mpls] set label-switched-path lsp_to_pe2_ge1 policing filter myfilter NOTE: You can also configure schedulers and shapers as needed. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. Related Documentation • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 2933 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 2934 CHAPTER 110 Verifying CoS Configuration • Monitoring CoS Classifiers on page 2935 • Monitoring CoS Forwarding Classes on page 2936 • Monitoring Interfaces That Have CoS Components on page 2937 • Monitoring CoS Rewrite Rules on page 2938 • Monitoring CoS Scheduler Maps on page 2939 • Monitoring CoS Value Aliases on page 2940 • Monitoring CoS Drop Profiles on page 2941 Monitoring CoS Classifiers Purpose Action Use the monitoring functionality to display the mapping of incoming CoS values to forwarding class and loss priority for each classifier. To monitor CoS classifiers in the J-Web interface, select Monitor>Class of Service>Classifiers To monitor CoS classifiers in the CLI, enter the following CLI command: show class-of-service classifier Meaning Table 378 on page 2935 summarizes key output fields for CoS classifiers. Table 378: Summary of Key CoS Classifier Output Fields Field Values Additional Information Classifier Name Name of a classifier. To display classifier assignments, click the plus sign (+). CoS Value Type The classifiers are displayed by type: • dscp—All classifiers of the DSCP type. • ieee-802.1—All classifiers of the IEEE 802.1 type. • inet-precedence—All classifiers of the IP precedence type. Index Internal index of the classifier. 2935 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 378: Summary of Key CoS Classifier Output Fields (continued) Field Values Incoming CoS Value CoS value of the incoming packets, in bits. These values are used for classification. Assign to Forwarding Class Forwarding class that the classifier assigns to an incoming packet. This class affects the forwarding and scheduling policies that are applied to the packet as it transits the switch. Assign to Loss Priority Loss priority value that the classifier assigns to the incoming packet based on its CoS value. Related Documentation Additional Information • Defining CoS Classifiers (CLI Procedure) on page 2914 • Defining CoS Classifiers (J-Web Procedure) on page 2916 • Example: Configuring CoS on J-EX Series Switches on page 2883 Monitoring CoS Forwarding Classes Purpose Action View the current assignment of class-of-service (CoS) forwarding classes to queues on the switch. To monitor CoS forwarding classes in the J-Web interface, select Monitor>Class of Service>Forwarding Classes. To monitor CoS forwarding classes in the CLI, enter the following CLI command: show class-of-service forwarding-class Meaning Table 379 on page 2936 summarizes key output fields for CoS forwarding classes. Table 379: Summary of Key CoS Forwarding Class Output Fields Field Values Forwarding Class Names of forwarding classes assigned to queue numbers. By default, the following forwarding classes are assigned to queues 0, 1, 5, or 7: • best-effort—Provides no special CoS handling of packets. Loss priority is typically not carried in a CoS value. • expedited-forwarding—Provides low loss, low delay, low jitter, assured bandwidth, and end-to-end service. • assured-forwarding—Provides high assurance for packets within specified service profile. Excess packets are dropped. • 2936 network-control—Packets can be delayed but not dropped. Chapter 110: Verifying CoS Configuration Table 379: Summary of Key CoS Forwarding Class Output Fields (continued) Field Values Queue Queue number corresponding to the forwarding class name. By default, four queues, 0, 1, 5, or 7, are assigned to forwarding classes. Related Documentation • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 • Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Example: Configuring CoS on J-EX Series Switches on page 2883 Monitoring Interfaces That Have CoS Components Purpose Action Use the monitoring functionality to display details about the physical and logical interfaces and the CoS components assigned to them. To monitor interfaces that have CoS components in the J-Web interface, select Monitor>Class of Service>Interface Association. To monitor interfaces that have CoS components in the CLI, enter the following command: show class-of-service interface interface Meaning Table 380 on page 2937 summarizes key output fields for CoS interfaces. Table 380: Summary of Key CoS Interfaces Output Fields Field Values Additional Information Interface Name of a physical interface to which CoS components are assigned. To display names of logical interfaces configured on this physical interface, click the plus sign (+). Scheduler Map Name of the scheduler map associated with this interface. Queues Supported Number of queues you can configure on the interface. Queues in Use Number of queues currently configured. Logical Interface Name of a logical interface on the physical interface to which CoS components are assigned. Object Category of an object—for example, classifier, scheduler-map, or rewrite. Name Name that you have given to an object—for example, ba-classifier. 2937 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 380: Summary of Key CoS Interfaces Output Fields (continued) Field Values Type Type of an object—for example, dscp for a classifier. Index Index of this interface or the internal index of a specific object. Related Documentation Additional Information • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Example: Configuring CoS on J-EX Series Switches on page 2883 Monitoring CoS Rewrite Rules Purpose Action Use the monitoring functionality to display information about CoS value rewrite rules, which are based on the forwarding class and loss priority. To monitor CoS rewrite rules in the J-Web interface, select Monitor>Class of Service>Rewrite Rules. To monitor CoS rewrite rules in the CLI, enter the following command: show class-of-service rewrite-rules Meaning Table 381 on page 2938 summarizes key output fields for CoS rewrite rules. Table 381: Summary of Key CoS Rewrite Rules Output Fields Field Values Rewrite Rule Name Names of rewrite rules. CoS Value Type Rewrite rule type: • dscp—For IPv4 DiffServ traffic. • exp—For MPLS traffic. • ieee-802.1—For Layer 2 traffic. • inet-precedence—For IPv4 traffic. Index Internal index for this particular rewrite rule. Forwarding Class Forwarding class that is used to determine CoS values for rewriting in combination with loss priority. Loss Priority Loss priority that is used to determine CoS values for rewriting in combination with forwarding class. 2938 Additional Information To display forwarding classes, loss priorities, and rewritten CoS values, click the plus sign (+). Rewrite rules are applied to CoS values in outgoing packets based on forwarding class and loss priority setting. Chapter 110: Verifying CoS Configuration Table 381: Summary of Key CoS Rewrite Rules Output Fields (continued) Field Values Rewrite CoS Value To Value that the CoS value is rewritten to. Related Documentation Additional Information • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 • Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Example: Configuring CoS on J-EX Series Switches on page 2883 Monitoring CoS Scheduler Maps Purpose Action Use the monitoring functionality to display assignments of CoS forwarding classes to schedulers. To monitor CoS scheduler maps in the J-Web interface, select Monitor>Class of Service>Scheduler Maps. To monitor CoS scheduler maps in the CLI, enter the following CLI command: show class-of-service scheduler-map Meaning Table 382 on page 2939 summarizes key output fields for CoS scheduler maps. Table 382: Summary of Key CoS Scheduler Maps Output Fields Field Values Additional Information Scheduler Map Name of a scheduler map. For details, click the plus sign (+). Index Index of a specific object—scheduler maps, schedulers, or drop profiles. Scheduler Name Name of a scheduler. Forwarding Class Forwarding classes this scheduler is assigned to. Transmit Rate Configured transmit rate of the scheduler in bits per second (bps). The rate value can be either of the following: • A percentage—The scheduler receives the specified percentage of the total interface bandwidth. • remainder— The scheduler receives the remaining bandwidth of the interface after bandwidth allocation to other schedulers. 2939 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 382: Summary of Key CoS Scheduler Maps Output Fields (continued) Field Values Buffer Size Delay buffer size in the queue or the amount of transmit delay (in milliseconds). The buffer size can be either of the following: • A percentage—The buffer is a percentage of the total buffer allocation. • remainder—The buffer is sized according Additional Information to what remains after other scheduler buffer allocations. Priority Scheduling priority of a queue: • strict-high—Packets in this queue are transmitted first. • low—Packets in this queue are transmitted last. Drop Profiles Name and index of a drop profile that is assigned to a specific loss priority and protocol pair. Loss Priority Packet loss priority corresponding to a drop profile. Protocol Transport protocol corresponding to a drop profile. Drop Profile Name Name of the drop profile. Index Index of a specific object—scheduler maps, schedulers, or drop profiles. Related Documentation • Defining CoS Schedulers (CLI Procedure) on page 2920 • Defining CoS Schedulers (J-Web Procedure) on page 2920 • Example: Configuring CoS on J-EX Series Switches on page 2883 Monitoring CoS Value Aliases Purpose Use the monitoring functionality to display information about the CoS value aliases that the system is currently using to represent DSCP, IEEE 802.1p, and IPv4 precedence bits. Action To monitor CoS value aliases in the J-Web interface, select Monitor>Class of Service>CoS Value Aliases. To monitor CoS value aliases in the CLI, enter the following command: show class-of-service code-point-aliases 2940 Chapter 110: Verifying CoS Configuration Meaning Table 383 on page 2941 summarizes key output fields for CoS value aliases. Table 383: Summary of Key CoS Value Alias Output Fields Field Values Additional Information CoS Value Type Type of the CoS value: To display aliases and bit patterns, click the plus sign (+). • dscp—Examines Layer 3 packet headers for IP packet classification. • ieee-802.1—Examines Layer 2 packet headers for packet classification. • inet-precedence—Examines Layer 3 packet headers for IP packet classification. CoS Value Alias Name given to a set of bits—for example, af11 is a name for 001010 bits. CoS Value Set of bits associated with an alias. Related Documentation • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 • Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Example: Configuring CoS on J-EX Series Switches on page 2883 Monitoring CoS Drop Profiles Purpose Action Use the monitoring functionality to view data point information for each CoS random early detection (RED) drop profile on the J-EX8200 switch. To monitor CoS RED drop profiles in the J-Web interface, select Monitor > Class of Service > RED Drop Profiles. To monitor CoS RED drop profiles in the CLI, enter the following CLI command: show class-of-service drop-profile Meaning Table 384 on page 2941 summarizes the key output fields for CoS RED drop profiles. Table 384: Summary of the Key Output Fields for CoS Red Drop Profiles Field Values Additional Information RED Drop Profile Name Name of the RED drop profile. To display profile values, click the plus sign (+). A drop profile consists of pairs of values between 0 and 100, one for queue buffer fill level and the other for drop probability, that determine the relationship between a buffer's fullness and the likelihood it will drop packets. Graph RED Profile Links to a graph of a RED curve that the system uses to determine the drop probability based on queue buffer fullness. The x axis represents the queue buffer fill level, and the y axis represents the drop probability. 2941 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 384: Summary of the Key Output Fields for CoS Red Drop Profiles (continued) Field Values Type Type of a specific drop profile: • Additional Information interpolated—The two coordinates (x and y) of the graph are interpolated to produce a smooth profile. • segmented—The two coordinates (x and y) of the graph are represented by line fragments to produce a segmented profile. Index Internal index of this drop profile. Fill Level Percentage fullness of a buffer queue. This value is the x coordinate of the RED drop profile graph. Drop Probability Drop probability of a packet corresponding to a specific queue buffer fill level. This value is the y coordinate of the RED drop profile graph. Related Documentation 2942 • Defining CoS Drop Profiles (J-Web Procedure) on page 2923 • Example: Configuring CoS on J-EX Series Switches on page 2883 CHAPTER 111 Configuration Statements for CoS • [edit class-of-service] Configuration Statement Hierarchy on page 2943 [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; } } forwarding-classes { class class-name queue-num queue-number priority ( high | low ); } interfaces { interface-name { 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; } inet { classifiers { 2943 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS (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 2944 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 Chapter 111: Configuration Statements for CoS broadcast Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation broadcast forwarding-class-name; [edit class-of-service multi-destination family ethernet] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the forwarding class for the broadcast traffic belonging to the Ethernet family. forwarding-class-name —Name of the forwarding class: • mcast-af—Default forwarding class for assured forwarding of multicast traffic. • mcast-be—Default best-effort forwarding class for multicast traffic. • mcast-ef—Default forwarding class for expedited forwarding of multicast traffic. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding CoS Schedulers on page 2873 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Classifiers on page 2867 2945 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS buffer-size Syntax Hierarchy Level Release Information Description buffer-size (exact | percent percentage | remainder); [edit class-of-serviceschedulersscheduler-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify buffer size. Default If you do not include this statement, the default scheduler transmission rate and buffer size percentages for queues 0 through 7 are 95, 0, 0, 0, 0, 0, 0, and 5 percent. Options exact—Enforce the exact buffer size. When this option is configured, sharing is disabled on the queue, restricting the usage to guaranteed buffers only. percentpercentage—Buffer size as a percentage of total buffer. remainder—Remaining buffer available. Required Privilege Level Related Documentation 2946 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Understanding CoS Schedulers on page 2873 Chapter 111: Configuration Statements for CoS class Syntax Hierarchy Level Release Information Description class class-name queue-num queue-number priority ( high | low ); [edit class-of-service forwarding-classes] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure up to 16 forwarding classes with multiple forwarding classes mapped to single queues. If you want to configure up to eight forwarding classes with one-to-one mapping to output queues, use the queue statement instead of the class statement at the [edit class-of-service forwarding-classes] hierarchy level. On J-EX8200 switches, you can assign a fabric priority to a forwarding class. The fabric priority determines whether packets belonging to the forwarding class are sent to the high priority ingress queue or the low priority ingress queue. By default, packets are sent to the low priority ingress queue. The primary use of this option is to prevent high priority input traffic from being dropped due to congestion on the port groups of oversubscribed line cards. Options class-name—Name of forwarding class. queue-num queue-number—Output queue number. Range: 0 through 15. priority (high | low)—(Optional) (J-EX8200 switches only) Fabric priority. Values: high or low Default: low Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 2947 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS class-of-service Syntax 2948 class-of-service { classifiers { (dscp | ieee-802.1 | inet-precedence) classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 6 bit-patterns ]; } } } } code-point-aliases { (dscp | ieee-802.1 | inet-precedence) { alias-name bits; } } forwarding-classes { class class-name queue-num queue-number priority ( high | low ); } interfaces { interface-name { 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; } 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 priority code-point (alias | bits); } } } scheduler-maps { Chapter 111: Configuration Statements for CoS 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); } } } Hierarchy Level Release Information Description [edit] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure class-of-service (CoS) parameters on J-EX Series switches. The remaining statements are explained separately. Default Required Privilege Level Related Documentation If you do not configure any CoS features, the default CoS settings are used. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 2949 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS classifiers Syntax Hierarchy Level Release Information Description classifiers { (dscp | ieee-802.1 | inet-precedence | exp) classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 6–bit-patterns ]; } } } } [edit class-of-service], [edit class-of-service interfaces interface-name unit logical-unit-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a CoS aggregate behavior classifier to a logical interface. You can apply a default classifier or a custom classifier. The statements are explained separately. Required Privilege Level Related Documentation 2950 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Example: Combining CoS with MPLS on J-EX Series Switches on page 2898 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Understanding CoS Classifiers on page 2867 Chapter 111: Configuration Statements for CoS code-point-aliases Syntax Hierarchy Level Release Information Description code-point-aliases { (dscp | ieee-802.1 | inet-precedence) |{ alias-name bits; } } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define an alias for a CoS marker. The statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Understanding CoS Code-Point Aliases on page 2864 code-points Syntax Hierarchy Level Release Information Description Options code-points [ aliases ] [ 6 bit-patterns ]; [edit class-of-service classifiers (dscp | ieee-802.1 | inet-precedence) forwarding-class class-name loss-priority level] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify one or more DSCP code-point aliases or bit sets for association with a forwarding class. aliases —Name of the DSCP alias. 6 bit-patterns —Value of the code-point bits, in decimal form. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Understanding CoS Classifiers on page 2867 2951 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS drop-profile-map Syntax Hierarchy Level Release Information Description Options drop-profile-map loss-priority loss-priority protocol protocol drop-profile profile-name; [edit class-of-service schedulers scheduler-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the loss priority value for the specified drop profile. drop-profile profile-name —Name of the drop profile. The remaining statements are explained separately. Required Privilege Level Related Documentation 2952 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Understanding CoS Schedulers on page 2873 Chapter 111: Configuration Statements for CoS dscp Syntax Hierarchy Level Release Information Description Options dscp classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 6–bit-patterns ]; } } } [edit class-of-service classifiers], [edit class-of-service code-point-aliases], [editclass-of-service interfaces interface-name unit logical-unit-number classifiers], [edit class-of-service rewrite-rules] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the Differentiated Services code point (DSCP) mapping that is applied to the packets. classifier-name—Name of the classifier. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Understanding CoS Classifiers on page 2867 2953 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS dscp-ipv6 Syntax Hierarchy Level Release Information Description Options dscp-ipv6 classifier-name { import (classifier-name | default); forwarding-classclass-name { loss-priority level { code-points [ aliases ] [ 6–bit-patterns ]; } } } [edit class-of-serviceclassifiers], [edit class-of-servicecode-point-aliases], [editclass-of-serviceinterfacesinterface-nameunitlogical-unit-number classifiers] [editclass-of-serviceinterfacesinterface-nameunitlogical-unit-number rewrite-rules] [edit class-of-servicerewrite-rules] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Define the Differentiated Services code point (DSCP) mapping that is applied to the IPv6 packets. classifier-name—Name of the classifier. The remaining statements are explained separately. Required Privilege Level Related Documentation 2954 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Understanding CoS Classifiers on page 2867 Chapter 111: Configuration Statements for CoS ethernet Syntax Hierarchy Level Release Information Description ethernet { broadcast forwarding-class-name; } [edit class-of-service multi-destination family] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the Ethernet broadcast traffic family. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding CoS Schedulers on page 2873 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Classifiers on page 2867 2955 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS exp Syntax Hierarchy Level Release Information Description exp classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 3–bit-patterns ]; } } } [edit class-of-service classifiers] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the experimental bits (EXP) code point mapping that is applied to the MPLS packets. J-EX Series switches support only one EXP code mapping on the switch (either default or custom). It is applied globally and implicitly to all the MPLS-enabled interfaces on the switch. You cannot bind it to an individual interface and you cannot disable it. Options classifier-name—Name of the classifier. The remaining statements are explained separately. Required Privilege Level Related Documentation 2956 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) on page 3106 Chapter 111: Configuration Statements for CoS family Syntax Hierarchy Level Release Information Description family { ethernet { broadcast forwarding-class-name; } inet { classifiers{ (dscp | ieee-802.1 | inet-precedence) classifier-name; } } } [edit class-of-service multi-destination] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the multidestination traffic family. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding CoS Schedulers on page 2873 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Classifiers on page 2867 2957 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS forwarding-class Syntax Hierarchy Level Release Information Description Options forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 6–bit-patterns ]; } } [edit class-of-service classifiers (dscp | ieee-802.1 | inet-precedence) classifier-name], [editclass-of-service interfaces interface-name unit logical-unit-number], [edit class-of-service rewrite-rules] (dscp | ieee-802.1 | inet-precedence) rewrite-name], [edit class-of-service scheduler-maps map-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define forwarding class name and option values. class-name —Name of the forwarding class. The remaining statements are explained separately. Required Privilege Level Related Documentation 2958 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Understanding CoS Forwarding Classes on page 2870 Chapter 111: Configuration Statements for CoS forwarding-classes Syntax Hierarchy Level Release Information Description forwarding-classes { class class-name queue-num queue-number; } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate the forwarding class with a queue name and number. The statement is explained separately. Required Privilege Level Related Documentation interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX-series Switches on page 2883 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Understanding CoS Forwarding Classes on page 2870 2959 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ieee-802.1 Syntax Hierarchy Level Release Information Description Options ieee-802.1 classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 6 bit-patterns ]; } } } [edit class-of-service classifiers], [edit class-of-service code-point-aliases], [editclass-of-service interfaces interface-name unit logical-unit-number classifiers], [edit class-of-service rewrite-rules] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply an IEEE-802.1 rewrite rule. classifier-name —Name of the classifier. The remaining statements are explained separately. Required Privilege Level Related Documentation 2960 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Understanding CoS Classifiers on page 2867 • Understanding CoS Rewrite Rules on page 2876 Chapter 111: Configuration Statements for CoS import Syntax Hierarchy Level Release Information Description Options import (classifier-name | default); [edit class-of-service classifiers (dscp | ieee-802.1 | inet-precedence) classifier-name], [edit class-of-service rewrite-rules (dscp | ieee-802.1 | inet-precedence) rewrite-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a default or previously defined classifier. classifier-name —Name of the classifier mapping configured at the [edit class-of-service classifiers] hierarchy level. default—Default classifier mapping. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Understanding CoS Classifiers on page 2867 • Understanding CoS Rewrite Rules on page 2876 2961 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS inet Syntax Hierarchy Level Release Information Description inet { classifiers { (dscp | ieee-802.1 | inet-precedence) classifier-name ; } } [edit class-of-service multi-destination family] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the IP multicast family. The remaining statements are explained separately. Required Privilege Level Related Documentation 2962 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding CoS Schedulers on page 2873 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Classifiers on page 2867 Chapter 111: Configuration Statements for CoS inet-precedence Syntax Hierarchy Level Release Information Description Options inet-precedence classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 6–bit-patterns ]; } } } [edit class-of-service classifiers], [edit class-of-service code-point-aliases], [editclass-of-service interfaces interface-name unit logical-unit-number classifiers], [edit class-of-service rewrite-rules] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply an IPv4 precedence rewrite rule. classifier-name—Name of the classifier. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Code-Point Aliases (CLI Procedure) on page 2914 or Defining CoS Code-Point Aliases (J-Web Procedure) on page 2912 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Understanding CoS Classifiers on page 2867 • Understanding CoS Rewrite Rules on page 2876 2963 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interfaces Syntax Hierarchy Level Release Information Description Options interfaces { interface-name { scheduler-map map-name; unit logical-unit-number { forwarding-class class-name; classifiers { (dscp | ieee-802.1 | inet-precedence) (classifier-name | default); } } } } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure interface-specific CoS properties for incoming packets. interface-name —Name of the interface. The statements are explained separately. Required Privilege Level Related Documentation 2964 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • J-EX Series Switches Interfaces Overview on page 863 Chapter 111: Configuration Statements for CoS loss-priority Syntax Hierarchy Level Release Information Description Options loss-priority level { code-points [ aliases ] [ 6–bit-patterns | 3–bit-patterns ]; } [edit class-of-service classifiers (dscp | ieee-802.1 | inet-precedence |exp) classifier-name forwarding-class class-name], [edit class-of-service rewrite-rules (dscp | ieee-802.1 | inet-precedence | exp) rewrite-name forwarding-class class-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify packet loss priority value for a specific set of code-point aliases and bit patterns. level —Can be one of the following: • high—Packet has high loss priority. • low—Packet has low loss priority. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Classifiers (CLI Procedure) on page 2914 or Defining CoS Classifiers (J-Web Procedure) on page 2916 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Understanding CoS Classifiers on page 2867 • Understanding CoS Rewrite Rules on page 2876 2965 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS multi-destination Syntax Hierarchy Level Release Information Description multi-destination { family { ethernet { broadcast forwarding-class-name; } inet { classifiers { (dscp | ieee-802.1 | inet-precedence) classifier-name; } } } scheduler-map map-name; } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the CoS configuration for multidestination traffic. The remaining statements are explained separately. Required Privilege Level Related Documentation 2966 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding CoS Schedulers on page 2873 • Understanding CoS Forwarding Classes on page 2870 • Understanding CoS Classifiers on page 2867 Chapter 111: Configuration Statements for CoS policing Syntax Hierarchy Level Release Information Description Options policing (filter filter-name | no-automatic-policing); [edit protocols mpls label-switched-path lsp-name] [edit interfaces interface-id unit number-of-logical-unit family inet address ip-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a rate-limiting policer as the specified policing filter: • To the LSP for MPLS over CCC. • To the customer-edge interface for IP over MPLS. filter filter-name—Specify the name of the policing filter. no-automatic-policing—Disable automatic policing on this LSP. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • policer on page 2826 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) on page 2932 • Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI Procedure) on page 2931 2967 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS priority Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation priority priority; [edit class-of-service schedulers scheduler-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify packet-scheduling priority value. priority —It can be one of the following: • low—Scheduler has low priority. • strict-high—Scheduler has strictly high priority. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Understanding CoS Schedulers on page 2873 protocol Syntax Hierarchy Level Release Information Description Options protocol protocol drop-profile profile-name; [edit class-of-service schedulers scheduler-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the protocol type for the specified drop profile. drop-profile profile-name —Name of the drop profile. protocol —Type of protocol. It can be: • Required Privilege Level Related Documentation 2968 any—Accept any protocol type. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Configuring CoS Tail Drop Profiles (CLI Procedure) on page 2925 • Understanding CoS Tail Drop Profiles on page 2872 Chapter 111: Configuration Statements for CoS rewrite-rules Syntax Hierarchy Level Release Information Description rewrite-rules { (dscp | exp |ieee-802.1 | inet-precedence ) rewrite-name { import ( default | rewrite-name); forwarding-class class-name { loss-priority level code-point (alias | bits); } } } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a rewrite-rules mapping for the traffic that passes through all queues on the interface. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Combining CoS with MPLS on J-EX Series Switches on page 2883 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 or Defining CoS Rewrite Rules (J-Web Procedure) on page 2926 • Understanding CoS Rewrite Rules on page 2876 • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 2969 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS scheduler-map Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 2970 scheduler-map map-name; [edit class-of-service interfaces], [edit class-of-service multi-destination] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Associate a scheduler map name with an interface or with a multidestination traffic configuration. map-name —Name of the scheduler map. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 • Understanding CoS Schedulers on page 2873 • Understanding CoS Classifiers on page 2867 Chapter 111: Configuration Statements for CoS scheduler-maps Syntax Hierarchy Level Release Information Description Options scheduler-maps { map-name { forwarding-class class-name scheduler scheduler-name; } } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a scheduler map name and associate it with the scheduler configuration and forwarding class. map-name —Name of the scheduler map. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 or Defining CoS Forwarding Classes (J-Web Procedure) on page 2918 • Understanding CoS Schedulers on page 2873 • Understanding CoS Forwarding Classes on page 2870 2971 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS schedulers Syntax Hierarchy Level Release Information Description Options 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); } } [edit class-of-service] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify scheduler name and parameter values. scheduler-name —Name of the scheduler. The remaining statements are explained separately. Required Privilege Level Related Documentation 2972 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Understanding CoS Schedulers on page 2873 Chapter 111: Configuration Statements for CoS shaping-rate Syntax Hierarchy Level shaping-rate (percent percentage | rate); [edit class-of-service schedulers scheduler-name] Release Information Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure shaping rate to throttle the rate at which queues transmit packets. We recommend that you configure the shaping rate as an absolute maximum usage and not as additional usage beyond the configured transmit rate. Default If you do not include this statement, the default shaping rate is 100 percent, which is the same as no shaping at all. Options percentpercentage —Shaping rate as a percentage of the available interface bandwidth. Range: 0 through 100 percent rate—Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Range: 3200 through 32,000,000,000 bps Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 2973 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS shared-buffer Syntax Hierarchy Level Release Information Description Options shared-buffer percent percentage [edit class-of-service], Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the buffer allocation for the shared buffer pool. percent percentage—Size of the shared buffer as a percentage of the buffer allocated to the shared buffer pool. Required Privilege Level Related Documentation 2974 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 Chapter 111: Configuration Statements for CoS transmit-rate Syntax Hierarchy Level Release Information Description Default Options transmit-rate (rate | percent percentage | remainder); [edit class-of-service schedulers scheduler-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the transmit rate or percentage for a scheduler. If you do not include this statement, the default scheduler transmission rate and buffer size percentages for queues 0 through 7 are 95, 0, 0, 0, 0, 0, 0, and 5 percent. rate —Transmission rate, in bps. You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Range: 3200 through 160,000,000,000 bps percent percentage —Percentage of transmission capacity. A percentage of zero drops all packets in the queue. Range: 0 through 100 percent remainder—Remaining rate available Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Defining CoS Schedulers (CLI Procedure) on page 2920 or Defining CoS Schedulers (J-Web Procedure) on page 2920 • Understanding CoS Schedulers on page 2873 2975 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS unit Syntax Hierarchy Level Release Information Description Options unit logical-unit-number { forwarding-class class-name; classifiers { (dscp | ieee-802.1 | inet-precedence) (classifier-name | default); } } [edit class-of-service interfaces interface-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure a logical interface on the physical device. You must configure a logical interface to be able to use the physical device. logical-unit-number —Number of the logical unit. Range: 0 through 16,385 The remaining statements are explained separately. Required Privilege Level Related Documentation 2976 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring CoS on J-EX Series Switches on page 2883 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 or Assigning CoS Components to Interfaces (J-Web Procedure) on page 2928 CHAPTER 112 Operational Mode Commands for CoS 2977 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show class-of-service Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show class-of-service Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the class-of-service (CoS) information. view • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Value Aliases on page 2940 • Monitoring CoS Classifiers on page 2935 • Monitoring CoS Forwarding Classes on page 2936 • Monitoring CoS Scheduler Maps on page 2939 • Monitoring CoS Rewrite Rules on page 2938 show class-of- service on page 2979 show class-of-service rewrite-rule on page 2982 Table 385 on page 2978 lists the output fields for the show class-of-service command. Output fields are listed in the approximate order in which they appear. Table 385: show class-of-service Output Fields Field Name Field Description Level of Output Forwarding class The forwarding class configuration: All levels • Forwarding class—Name of the forwarding class. • ID—Forwarding class ID. • Queue—Queue number. • Fabric Priority—(J-EX8200 switches only) Fabric priority: either high or low. The fabric priority determines which CoS ingress queues packets are sent to. Code point type The type of code-point alias: • dscp—Aliases for DiffServ code point (DSCP) values. • ieee–802.1—Aliases for IEEE 802.1p values. • inet-precedence—Aliases for IP precedence values. • exp—Aliases for experimental (EXP) values. All levels Alias Names given to CoS values. All levels Bit pattern Set of bits associated with an alias. All levels Classifier Name of the classifier. All levels 2978 Chapter 112: Operational Mode Commands for CoS Table 385: show class-of-service Output Fields (continued) Field Name Field Description Level of Output Code point Code-point values. All levels Loss priority Loss priority assigned to specific CoS values and aliases of the classifier. All levels Rewrite rule Name of the rewrite-rule. All levels Drop profile Name of the drop profile. All levels Type Type of drop profile. J-EX Series switches support only the discrete type of drop profile. All levels Fill level Percentage of queue buffer fullness of high packets beyond which high packets are dropped. All levels Scheduler Name of the scheduler. All levels Transmit rate Transmission rate of the scheduler. All levels Buffer size Delay buffer size in the queue. All levels Drop profiles Drop profiles configured for the specified scheduler. All levels Protocol Transport protocol corresponding to the drop profile. All levels Name Name of the drop profile. All levels Queues supported Number of queues that can be configured on the interface. All levels Queues in use Number of queues currently configured. All levels Physical interface Name of the physical interface. All levels Scheduler map Name of the scheduler map. All levels Index Internal index of a specific object. All levels show class-of- service user@switch> show class-of-service Forwarding class best-effort expedited-forwarding assured-forwarding network-control ID 0 1 2 3 Queue 0 5 1 7 Code point type: dscp Alias Bit pattern af11 001010 af12 001100 ... ... 2979 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Code point type: ieee-802.1 Alias Bit pattern af11 010 ... ... Code point type: inet-precedence Alias Bit pattern af11 001 ... ... Classifier: dscp-default, Code point type: dscp, Index: 7 Code point Forwarding class Loss priority 000000 best-effort low 000001 best-effort low ... ... ... Classifier: ieee8021p-default, Code point type: ieee-802.1, Index: 11 Code point Forwarding class Loss priority 000 best-effort low 001 best-effort low 010 best-effort low 011 best-effort low 100 best-effort low 101 best-effort low 110 network-control low 111 network-control low Classifier: ipprec-default, Code point type: inet-precedence, Index: 12 Code point Forwarding class Loss priority 000 best-effort low 001 best-effort low 010 best-effort low 011 best-effort low 100 best-effort low 101 best-effort low 110 network-control low 111 network-control low Classifier: ieee8021p-untrust, Code point type: ieee-802.1, Index: 16 Code point Forwarding class Loss priority 000 best-effort low 001 best-effort low 010 best-effort low 011 best-effort low 100 best-effort low 101 best-effort low 110 best-effort low 111 best-effort low Rewrite rule: dscp-default, Code point type: dscp, Index: Forwarding class Loss priority best-effort low best-effort high expedited-forwarding low expedited-forwarding high assured-forwarding low assured-forwarding high network-control low network-control high 2980 27 Code point 000000 000000 101110 101110 001010 001100 110000 111000 Chapter 112: Operational Mode Commands for CoS Rewrite rule: ieee8021p-default, Code point type: ieee-802.1, Index: 30 Forwarding class Loss priority Code point best-effort low 000 best-effort high 001 expedited-forwarding low 100 expedited-forwarding high 101 assured-forwarding low 010 assured-forwarding high 011 network-control low 110 network-control high 111 Rewrite rule: ipprec-default, Code point type: inet-precedence, Index: 31 Forwarding class Loss priority Code point best-effort low 000 best-effort high 000 expedited-forwarding low 101 expedited-forwarding high 101 assured-forwarding low 001 assured-forwarding high 001 network-control low 110 network-control high 111 Drop profile:, Type: discrete, Index: 1 Fill level 100 Scheduler map: , Index: 2 Scheduler: , Forwarding class: best-effort, Index: 20 Transmit rate: 95 percent, Rate Limit: none, Buffer size: 95 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Scheduler: , Forwarding class: network-control, Index: 22 Transmit rate: 5 percent, Rate Limit: none, Buffer size: 5 percent, Priority: low Drop profiles: Loss priority Protocol Index Name High non-TCP 1 High TCP 1 Physical interface: ge-0/0/0, Index: 129 Queues supported: 8, Queues in use: 4 Scheduler map: , Index: 2 Physical interface: ge-0/0/1, Index: 130 Queues supported: 8, Queues in use: 4 Scheduler map: , Index: 2 ... ... ... Fabric priority: low Scheduler: , Index: 23 Drop profiles: Loss priority Protocol Index High non-TCP 1 High TCP 1 Name 2981 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Fabric priority: high Scheduler: , Index: 23 Drop profiles: Loss priority Protocol Index High non-TCP 1 High TCP 1 show class-of-service rewrite-rule Name user@switch> show class-of-service rewrite-rule Rewrite rule: dscp-default, Code point type: dscp, Index: Forwarding class Loss priority best-effort low best-effort high expedited-forwarding low expedited-forwarding high fw-class low fw-class high network-control low network-control high 31 Code point 000000 000000 101110 101110 001010 001100 110000 111000 Rewrite rule: exp-default, Code point type: exp, Index: 33 Forwarding class Loss priority Code point best-effort low 000 best-effort high 001 expedited-forwarding low 010 expedited-forwarding high 011 fw-class low 100 fw-class high 101 network-control low 110 network-control high 111 Rewrite rule: ieee8021p-default, Code point type: ieee-802.1, Index: 34 Forwarding class Loss priority Code point best-effort low 000 best-effort high 001 expedited-forwarding low 010 expedited-forwarding high 011 fw-class low 100 fw-class high 101 network-control low 110 network-control high 111 Rewrite rule: ipprec-default, Code point type: inet-precedence, Index: 35 Forwarding class Loss priority Code point best-effort low 000 best-effort high 000 expedited-forwarding low 101 expedited-forwarding high 101 fw-class low 001 fw-class high 001 network-control low 110 network-control high 111 2982 Chapter 112: Operational Mode Commands for CoS show class-of-service classifier Syntax show class-of-service classifier Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Options For each class-of-service (CoS) classifier, display the mapping of code point value to forwarding class and loss priority. none—Display all classifiers. name name—(Optional) Display named classifier. type dscp—(Optional) Display all classifiers of the Differentiated Services code point (DSCP) type. type dscp-ipv6—(Optional) Display all classifiers of the DSCP for IPv6 type. type exp—(Optional) Display all classifiers of the MPLS experimental (EXP) type. type ieee-802.1—(Optional) Display all classifiers of the ieee-802.1 type. type inet-precedence—(Optional) Display all classifiers of the inet-precedence type. Required Privilege Level List of Sample Output Output Fields view show class-of-service classifier type ieee-802.1 on page 2984 Table 386 on page 2983 describes the output fields for the show class-of-service classifier command. Output fields are listed in the approximate order in which they appear. Table 386: show class-of-service classifier Output Fields Field Name Field Description Classifier Name of the classifier. Code point type Type of the classifier: exp (not on J-EX Series switches), dscp, dscp-ipv6 (not on J-EX Series switches), ieee-802.1, or inet-precedence. Index Internal index of the classifier. Code point Code point value used for classification Forwarding class Classification of a packet affecting the forwarding, scheduling, and marking policies applied as the packet transits the router. 2983 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 386: show class-of-service classifier Output Fields (continued) show class-of-service classifier type ieee-802.1 Field Name Field Description Loss priority Loss priority value used for classification. For most platforms, the value is high or low. For some platforms, the value is high, medium-high, medium-low, or low. user@host> show class-of-service classifier type ieee-802.1 Classifier: ieee802.1-default, Code point type: ieee-802.1, Index: 3 Code Point Forwarding Class Loss priority 000 best-effort low 001 best-effort high 010 expedited-forwarding low 011 expedited-forwarding high 100 assured-forwarding low 101 assured-forwarding medium-high 110 network-control low 111 network-control high Classifier: users-ieee802.1, Code point type: ieee-802.1 Code point Forwarding class Loss priority 100 expedited-forwarding low 2984 Chapter 112: Operational Mode Commands for CoS show class-of-service code-point-aliases Syntax Release Information Description Options show class-of-service code-point-aliases Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the mapping of class-of-service (CoS) code point aliases to corresponding bit patterns. none—Display code point aliases of all code point types. dscp—(Optional) Display Differentiated Services code point (DSCP) aliases. dscp-ipv6—(Optional) Display IPv6 DSCP aliases. exp—(Optional) Display MPLS EXP code point aliases. ieee-802.1—(Optional) Display IEEE-802.1 code point aliases. inet-precedence—(Optional) Display IPv4 precedence code point aliases. Required Privilege Level List of Sample Output Output Fields view show class-of-service code-point-aliases exp on page 2986 Table 387 on page 2985 describes the output fields for the show class-of-service code-point-aliases command. Output fields are listed in the approximate order in which they appear. Table 387: show class-of-service code-point-aliases Output Fields Field Name Field Description Code point type Type of the code points displayed: dscp, dscp-ipv6 (not on J-EX Series switches), exp (not on J-EX Series switches), ieee-802.1, or inet-precedence. Alias Alias for a bit pattern. Bit pattern Bit pattern for which the alias is displayed. 2985 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show class-of-service code-point-aliases exp 2986 user@host> show class-of-service code-point-aliases exp Code point type: exp Alias Bit pattern af11 100 af12 101 be 000 be1 001 cs6 110 cs7 111 ef 010 ef1 011 nc1 110 nc2 111 Chapter 112: Operational Mode Commands for CoS show class-of-service drop-profile Syntax Release Information Description Options show class-of-service drop-profile Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display data points for each class-of-service (CoS) random early detection (RED) drop profile. none—Display all drop profiles. profile-name profile-name—(Optional) Display the specified profile only. Required Privilege Level List of Sample Output Output Fields view show class-of-service drop-profile on page 2988 Table 388 on page 2987 describes the output fields for the show class-of-service drop-profile command. Output fields are listed in the approximate order in which they appear. Table 388: show class-of-service drop-profile Output Fields Field Name Field Description Drop profile Name of a drop profile. Type Type of this drop profile: discrete or interpolated. Index Internal index of this drop profile. Fill Level Percentage fullness of a queue. Drop probability Drop probability at this fill level. 2987 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show class-of-service drop-profile 2988 user@host> show class-of-service drop-profile Drop profile: , Type: discrete, Index: 1 Fill level Drop probability 100 100 Drop profile: user-drop-profile, Type: interpolated, Index: 2989 Fill level Drop probability 0 0 1 1 2 2 4 4 5 5 6 6 8 8 10 10 12 15 14 20 15 23 ... 64 entries total 90 96 92 96 94 97 95 98 96 98 98 99 99 99 100 100 Chapter 112: Operational Mode Commands for CoS show class-of-service forwarding-class Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show class-of-service forwarding-class Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about forwarding classes, including the mapping of forwarding classes to queue numbers. view • Example: Configuring CoS on J-EX Series Switches on page 2883 • Monitoring CoS Forwarding Classes on page 2936 • Defining CoS Forwarding Classes (CLI Procedure) on page 2918 show class-of-service forwarding-class on page 2989 show class-of-service forwarding-class (J-EX8200 Switch) on page 2989 Table 389 on page 2989 describes the output fields for the show class-of-service forwarding-class command. Output fields are listed in the approximate order in which they appear. Table 389: show class-of-service forwarding-class Output Fields show class-of-service forwarding-class show class-of-service forwarding-class (J-EX8200 Switch) Field Name Field Description Forwarding class Name of forwarding class. ID Forwarding class identifier. Queue CoS queue mapped to the forwarding class. Policing priority Not supported on J-EX Series switches and can be ignored. Fabric priority (J-EX8200 switches only) Fabric priority for the forwarding class, either high or low. Determines the priority of packets ingressing the switch fabric. user@switch> show class-of-service forwarding-class Forwarding class ID best-effort 0 expedited-forwarding 1 assured-forwarding 2 network-control 3 user@switch> show class-of-service forwarding-class Forwarding class ID Queue best-effort 0 0 expedited-forwarding 1 5 assured-forwarding 2 1 Queue Policing priority normal normal normal normal 0 5 1 7 Fabric priority low low low 2989 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS network-control mcast-be mcast-ef mcast-af 2990 3 4 5 6 7 2 4 6 low low low low Chapter 112: Operational Mode Commands for CoS show class-of-service interface Syntax Release Information Description Options show class-of-service interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the logical and physical interface associations for the classifier, rewrite rules, and scheduler map objects. none—Display class of service (CoS) associations for all physical and logical interfaces. interface-name—(Optional) Display CoS associations for the specified interface. Required Privilege Level List of Sample Output Output Fields view show class-of-service interface (Physical) on page 2992 show class-of-service interface (Logical) on page 2992 show class-of-service interface (Gigabit Ethernet) on page 2993 Table 390 on page 2991 describes the output fields for the show class-of-service interface command. Output fields are listed in the approximate order in which they appear. Table 390: show class-of-service interface Output Fields Field Name Field Description Physical interface Name of a physical interface. Index Index of this interface or the internal index of this object. Dedicated Queues Status of dedicated queues configured on an interface. Supported on Trio MPC/MIC interfaces on MX Series routers only. Queues supported Number of queues you can configure on the interface. Queues in use Number of queues currently configured. Total non-default queues created Number of queues created in addition to the default queues. Supported on Trio MPC/MIC interfaces on MX Series routers. Shaping rate Maximum transmission rate on the physical interface. You can configure the shaping rate on the physical interface, or on the logical interface, but not both. Therefore, the Shaping rate field is displayed for the physical interface or the logical interface, but not both. Scheduler map Name of the output scheduler map associated with this interface. Input shaping rate For Gigabit Ethernet IQ2 PICs, maximum transmission rate on the input interface. Input scheduler map For Gigabit Ethernet IQ2 PICs, name of the input scheduler map associated with this interface. 2991 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 390: show class-of-service interface Output Fields (continued) Field Name Field Description Chassis scheduler map Name of the scheduler map associated with the packet forwarding component queues. Rewrite Name and type of the rewrite rules associated with this interface. Classifier Name and type of classifiers associated with this interface. Forwaridng-class-map Name of the forwarding map associated with this interface. Logical interface Name of a logical interface. Shaping rate Maximum transmission rate on the logical interface. You can configure the shaping rate on the physical interface, or on the logical interface, but not both. Therefore, the Shaping rate field is displayed for the physical interface or the logical interface, but not both. Object Category of an object: Classifier, Fragmentation-map (for LSQ interfaces only), Scheduler-map, Rewrite, or Translation Table (for IQE PICs only). Name Name of an object. Type Type of an object: dscp, dscp-ipv6, exp, ieee-802.1, ip, or inet-precedence. show class-of-service interface (Physical) user@host> show class-of-service interface so-0/2/3 Physical interface: so-0/2/3, Index: 135 Queues supported: 8, Queues in use: 4 Total non—default queues created: 4 Scheduler map: , Index: 2032638653 Logical interface: fe-0/0/1.0, Index: 68, Dedicated Queues: no Shaping rate: 32000 Object Name Type Index Scheduler-map 27 Rewrite exp-default exp 21 Classifier exp-default exp 5 Classifier ipprec-compatibility ip 8 Forwarding—class—map exp-default exp 5 show class-of-service interface (Logical) 2992 user@host> show class-of-service interface so-0/2/3.0 Logical interface: so-0/2/3.0, Index: 68, Dedicated Queues: no Shaping rate: 32000 Object Name Type Index Scheduler-map 27 Rewrite exp-default exp 21 Chapter 112: Operational Mode Commands for CoS Classifier 5 Classifier 8 Forwarding—class—map 5 show class-of-service interface (Gigabit Ethernet) exp-default exp ipprec-compatibility ip exp-default exp user@host> show class-of-service interface ge-6/2/0 Physical interface: ge-6/2/0, Index: 175 Queues supported: 4, Queues in use: 4 Scheduler map: , Index: 2 Input scheduler map: , Index: 3 Chassis scheduler map: , Index: 4 2993 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show pfe statistics traffic Syntax show pfe statistics traffic Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display the packet forwarding engine traffic statistics. Options none—Display statistics about all the traffic handled by the packet forwarding engine. Required Privilege Level admin List of Sample Output show pfe statistics traffic on page 2995 Output Fields Table 391 on page 2994 lists the output fields for the show pfe statistics traffic command. Output fields are listed in the approximate order in which they appear. Table 391: show pfe statistics traffic Output Fields Field Name Field Description Packet Forwarding Engine Traffic statistics Information about Packet Forwarding Engine traffic: Packet Forwarding Engine Local Traffic statistics 2994 • Input Packets—Number and rate of input packets. • Output Packets—Number and rate of output packets. Information about Packet Forwarding Engine local traffic: • Local packets input—Number of local input packets. • Local packets output—Number of local output packets. • Software input high drops—Number of software input high-priority drops. • Software input medium drops—Number of software input medium-priority drops. • Software input low drops—Number of software input low-priority drops. • Software output drops—Number of software output drops. • Hardware input drops—Number of hardware input drops. Chapter 112: Operational Mode Commands for CoS Table 391: show pfe statistics traffic Output Fields (continued) Field Name Field Description Packet Forwarding Engine Local Protocol statistics Information about the Packet Forwarding Engine Local Protocol: • HDLC keepalives—Number of HDLC keepalive packets. • ATM OAM—Number of Asynchronous Transfer Mode (ATM) Operation, Administration, and Maintenance (OAM) packets. • Frame Relay LMI—Number of Frame Relay Local Management Interface (LMI) packets. • PPP LCP/NCP—Number of Point-to-Point Protocol (PPP) Link Control Protocol (LCP) or Network Control Protocol (NCP) packets. Packet Forwarding Engine Hardware Discard statistics show pfe statistics traffic • OSPF hello—Number of Open Shortest Path First (OSPF) hello packets. • OSPF3 hello—Number of Open Shortest Path First version 3 (OSPFv3) hello packets. • RSVP hello—Number of Reservation Setup Protocol (RSVP) hello packets. • LDP hello—Number of Label Distribution Protocol (LDP) hello packets. • BFD—Number of Bidirectional Forwarding Detection Protocol (BFD) hello packets. • IS-IS IIH—Number of Intermediate System-to-Intermediate System Hello (IIH) packets. • LACP—Number of Link Aggregation Control Protocol (LACP) packets. • ARP—Number of Address Resolution Protocol (ARP) packets. • ETHER OAM—Number of Ethernet Operations, Administration, and Management (OAM) packets. • Unknown—Number of unknown packets not matching any of the packet types listed above. Information about Packet Forwarding Engine hardware discards: • Timeout—Number of packets discarded because of timeouts. • Truncated key—Number of packets discarded because of truncated keys. • Bits to test—Number of bits to test. • Data error—Number of packets discarded because of data errors. • Stack underflow—Number of packets discarded because of stack underflows. • Stack overflow—Number of packets discarded because of stack overflows. • Normal discard—Number of packets discarded because of discard routes. • Extended discard—Number of packets discarded because of illegal next hops. • Invalid interface—Number of packets discarded because of invalid incoming interfaces. • Info cell drops—Number of information cell drops. • Fabric drops—Number of fabric drops. user@host> show pfe statistics traffic Packet Forwarding Engine traffic statistics: Input packets: 102682 Output packets: 58033 Packet Forwarding Engine local traffic statistics: Local packets input : Local packets output : Software input control plane drops : Software input high drops : Software input medium drops : Software input low drops : Software output drops : Hardware input drops : Packet Forwarding Engine local protocol statistics: HDLC keepalives : 0 5 pps 4 pps 44628 46146 0 0 0 0 0 0 2995 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS ATM OAM : 0 Frame Relay LMI : 0 PPP LCP/NCP : 5597 OSPF hello : 3195 OSPF3 hello : 0 RSVP hello : 0 LDP hello : 7478 BFD : 0 IS-IS IIH : 0 LACP : 0 ARP : 0 ETHER OAM : 0 Unknown : 8 Packet Forwarding Engine hardware discard statistics: Timeout : 0 Truncated key : 0 Bits to test : 0 Data error : 0 Stack underflow : 0 Stack overflow : 0 Normal discard : 0 Extended discard : 0 Invalid interface : 0 Info cell drops : 0 Fabric drops : 0 Packet Forwarding Engine Input IPv4 Header Checksum Error and Output MTU Error statistics: Input Checksum : 0 Output MTU : 0 2996 Chapter 112: Operational Mode Commands for CoS show pfe statistics traffic cpu Syntax Release Information Description show pfe statistics traffic cpu Command introduced before Junos OS Release 10.2 for J-EX Series switches. (On J-EX8200 switches only) Display count of multidestination packets ingressing from the physical interface to the CPU. NOTE: Multidestination packets include unknown unicast, broadcast, and multicast packets. Options none—Displays the count of packets ingressing from all the physical interfaces (line cards) to the CPU. fpc fpc-slot—(Optional) Displays the count of packets ingressing from the physical interface, referred to by the slot number, to the CPU. On a J-EX8200 switch, the FPC slot number is the slot number for the line card. Possible values are 0 through 7 on the J-EX8208 switch and 0 through 15 on the J-EX8216 switch. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show pfe statistics traffic multicast on page 3003 • show pfe statistics traffic egress-queues on page 3001 • show interfaces queue on page 1016 • Monitoring Interface Status and Traffic on page 931 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 show pfe statistics traffic cpu (J-EX8208 Switch) on page 2998 Table 392 on page 2997 lists the output fields for the show pfe statistics traffic cpu command. Output fields are listed in the approximate order in which they appear. Table 392: show pfe statistics traffic cpu Output Fields Field Name Field Description Queue CoS queue number. Forwarding classes Forwarding class name. Queued Packets Number of packets queued to this queue. Queued Bytes Number of bytes queued to this queue. 2997 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 392: show pfe statistics traffic cpu Output Fields (continued) Field Name Field Description Packets Number of packets transmitted by this queue. Bytes Number of bytes transmitted by this queue. Tail-dropped packets Count of packets dropped at the tail end of the queue because of lack of buffer space. RED-dropped packets Number of packets dropped because of Random Early Discard (RED): RED-dropped bytes show pfe statistics traffic cpu (J-EX8208 Switch) 2998 • Low—Number of low-loss priority packets dropped because of RED. • High—Number of high-loss priority packets dropped because of RED. Number of bytes dropped because of Random Early Discard (RED): • Low—Number of low-loss priority bytes dropped because of RED. • High—Number of high-loss priority bytes dropped because of RED. user@switch> show pfe statistics traffic cpu Queue: 0, Forwarding classes: best-effort Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 1, Forwarding classes: expedited-forwarding Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 2, Forwarding classes: assured-forwarding Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 bps 0 bps 0 bps Chapter 112: Operational Mode Commands for CoS RED-dropped packets : Low : High : Queue: 3, Forwarding classes: network-control Queued: Packets : Not Available Bytes : Not Available Packets : Bytes : Tail-dropped packets : RED-dropped bytes : Low : High : RED-dropped packets : Low : High : Queue: 4 Packets : Not Available Bytes : Not Available Packets : Bytes : Tail-dropped packets : RED-dropped bytes : Low : High : RED-dropped packets : Low : High : Queue: 5 Packets : Not Available Bytes : Not Available Packets : Bytes : Tail-dropped packets : RED-dropped bytes : Low : High : RED-dropped packets : Low : High : Queue: 6 Packets : Not Available Bytes : Not Available Packets : Bytes : Tail-dropped packets : RED-dropped bytes : Low : High : RED-dropped packets : Low : High : Queue: 7 Packets : Not Available Bytes : Not Available Packets : Bytes : Tail-dropped packets : RED-dropped bytes : Low : High : 0 0 0 0 pps 0 pps 0 pps 0 0 0 0 0 0 0 0 0 0 pps 0 bps 0 0 0 0 0 0 0 0 0 0 pps 0 bps 0 0 0 0 0 0 0 0 0 0 pps 0 bps 0 0 0 0 0 0 0 0 0 0 pps 0 bps 0 0 0 0 0 0 0 pps 0 bps 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 bps bps bps pps pps pps bps bps bps pps pps pps bps bps bps pps pps pps bps bps bps pps pps pps 0 bps 0 bps 0 bps 2999 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS RED-dropped packets Low High 3000 : : : 0 0 0 0 pps 0 pps 0 pps Chapter 112: Operational Mode Commands for CoS show pfe statistics traffic egress-queues Syntax Release Information Description show pfe statistics traffic egress-queues Command introduced before Junos OS Release 10.2 for J-EX Series switches. (On J-EX8200 switches only) Display count of multidestination packets dropped on egress ports when the egress queues are oversubscribed due to multidestination traffic. NOTE: Multidestination packets include unknown unicast, broadcast, and multicast packets. Options none—Displays count of packets dropped on egress ports of all physical interfaces (line cards) when egress queues are oversubscribed due to multidestination traffic. fpc fpc-slot—(Optional) Displays count of packets dropped on egress ports of the physical interface (line card) referred to by the slot number. NOTE: On a J-EX8200 switch, the FPC slot number is the slot number for the line card. Possible values are 0 through 7 on the J-EX8208 switch and 0 through 15 on the J-EX8216 switch. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show pfe statistics traffic cpu on page 2997 • show pfe statistics traffic multicast on page 3003 • show interfaces queue on page 1016 • Monitoring Interface Status and Traffic on page 931 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 show pfe statistics traffic egress-queues fpc 4 (J-EX8208 Switch) on page 3001 Table 393 on page 3001 lists the output fields for the show pfe statistics traffic egress-queues command. Output fields are listed in the approximate order in which they appear. Table 393: show pfe statistics traffic egress-queues Output Fields Field Name Field Description Tail-dropped packets Number of arriving packets dropped because the output queue buffers are full. show pfe statistics traffic egress-queues user@switch> show pfe statistics traffic egress-queues fpc 4 3001 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS fpc 4 (J-EX8208 Switch) 3002 Tail-dropped packets : 0 Chapter 112: Operational Mode Commands for CoS show pfe statistics traffic multicast Syntax Release Information Description show pfe statistics traffic multicast Command introduced before Junos OS Release 10.2 for J-EX Series switches. (On J-EX8200 switches only) Display class-of-service (CoS) queue information for multidestination traffic on a physical interface (line card). NOTE: Multidestination packets include unknown unicast, broadcast, and multicast packets. NOTE: To view statistical information for unicast traffic, use the show interfaces queue command. Options fpc fpc-slot—(Optional) Displays class-of-service (CoS) queue information for multidestination traffic on the physical interface (line card) referred to by the slot number. NOTE: On a J-EX8200 switch, the FPC slot number is the slot number for the line card. Possible values are 0 through 7 on the J-EX8208 switch and 0 through 15 on the J-EX8216 switch. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show pfe statistics traffic cpu on page 2997 • show pfe statistics traffic egress-queues on page 3001 • show interfaces queue on page 1016 • Monitoring Interface Status and Traffic on page 931 • Understanding Junos OS CoS Components for J-EX Series Switches on page 2862 show pfe statistics traffic multicast fpc 0 (J-EX8208 Switch) on page 3004 Table 394 on page 3003 lists the output fields for the show pfe statistics traffic multicast command. Output fields are listed in the approximate order in which they appear. Table 394: show pfe statistics traffic multicast Output Fields Field Name Field Description Queue CoS queue number. 3003 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 394: show pfe statistics traffic multicast Output Fields (continued) Field Name Field Description Forwarding classes Forwarding class name. Queued Packets Number of packets queued to this queue. Queued Bytes Number of bytes queued to this queue. Packets Number of packets transmitted by this queue. Bytes Number of bytes transmitted by this queue. Tail-dropped packets Count of packets dropped at the tail end of the queue because of lack of buffer space. RED-dropped packets Number of packets dropped because of Random Early Discard (RED): Multicast Replication Engine-dropped packets 3004 Low—Number of low-loss priority packets dropped because of RED. • High—Number of high-loss priority packets dropped because of RED. Number of bytes dropped because of Random Early Discard (RED): RED-dropped bytes show pfe statistics traffic multicast fpc 0 (J-EX8208 Switch) • • Low—Number of low-loss priority bytes dropped because of RED. • High—Number of high-loss priority bytes dropped because of RED. Egress packets dropped by the PFE because none of the ports on the physical interface are needed to forward the packet. user@switch> show pfe statistics traffic multicast fpc 0 Queue: 0, Forwarding classes: best-effort Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 1, Forwarding classes: expedited-forwarding Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 0 0 0 0 bps bps bps pps pps Chapter 112: Operational Mode Commands for CoS High : 0 Queue: 2, Forwarding classes: assured-forwarding Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 3, Forwarding classes: network-control Queued: Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 4 Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 5 Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 Low : 0 High : 0 Queue: 6 Packets : Not Available Bytes : Not Available Packets : 0 Bytes : 0 Tail-dropped packets : 0 RED-dropped bytes : 0 Low : 0 High : 0 RED-dropped packets : 0 0 pps 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps 0 pps 0 bps 0 0 0 0 bps bps bps pps 3005 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Low : High : Queue: 7 Packets : Not Available Bytes : Not Available Packets : Bytes : Tail-dropped packets : RED-dropped bytes : Low : High : RED-dropped packets : Low : High : Multicast Replication Engine-dropped packets : 3006 0 0 0 pps 0 pps 0 0 0 0 0 0 0 0 0 0 pps 0 pps 0 bps 0 0 0 0 0 0 bps bps bps pps pps pps PART 22 Power over Ethernet • Power over Ethernet (PoE)—Overview on page 3009 • Examples: PoE Configuration on page 3013 • Configuring PoE on page 3021 • Verifying PoE Configuration on page 3025 • Troubleshooting PoE Configuration on page 3031 • Configuration Statements for PoE on page 3033 • Operational Mode Commands for PoE on page 3045 3007 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3008 CHAPTER 113 Power over Ethernet (PoE)—Overview • PoE and J-EX Series Switches Overview on page 3009 PoE and J-EX Series Switches Overview Power over Ethernet (PoE) permits electric power, along with data, to be passed over a copper Ethernet LAN cable. Powered devices, such as voice over IP (VoIP) telephones, wireless access points, video cameras, and point-of-sale devices, that support PoE can receive power safely from the same access ports that are used to connect personal computers to the network. This topic describes PoE on J-EX Series Switches. It covers: • PoE on page 3009 • PoE Power Management on page 3009 • PoE Configuration and Monitoring on page 3011 PoE PoE was first defined in the IEEE 802.3af standard. In this standard, the amount of power that can be supplied to a powered device is limited to 15.4 W. Whether a J-EX Series switch supports PoE depends on the switch model. Consult your switch hardware guide for information on PoE support. PoE Power Management Switches that have PoE ports have a PoE controller that keeps track of the PoE power consumption on the switch and allocates power to the PoE ports. The following factors determine how the PoE controller allocates power to the PoE ports: • PoE Power Budget on page 3009 • Power Management Mode on page 3010 • PoE Interface Power Priority on page 3011 PoE Power Budget The PoE controller allocates power to the PoE ports from a set PoE power budget. The PoE power budget varies according to switch model and, for switches that support power supplies of different capacities, the capacity of the installed power supply. 3009 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS In switches that support power supplies of different capacities, if you change your existing power supply to a lower-capacity power supply, the PoE power budget might no longer be sufficient to power all the PoE ports on the switch. If your switch supports redundant power supplies and you have installed power supplies of different capacities, the PoE power budget is based on the wattage of the lower-capacity power supply. The number of PoE ports on the switch cannot be increased by installing a larger power supply. You can display the PoE power budget for your switch by using the show poe controller command. Power Management Mode J-EX Series switches support two power management modes: class and static. The mode you configure for your switch determines how the maximum power for a PoE interface is derived and how power is allocated to the PoE interfaces: • Class mode—In this mode, the maximum power for an interface is determined by the class of connected powered device. Table 395 on page 3010 lists the classes of powered devices and associated power levels. Table 395: Class of Powered Device and Power Levels Class Maximum Power Delivered by PoE Port Power Range of Powered Device 0 15.4 W 0.44 through 12.95 W 1 4.0 W 0.44 through 3.84 W 2 7.0 W 3.84 through 6.49 W 3 15.4 W 6.49 through 12.95 W Standard IEEE 802.3af (PoE) The powered device communicates to the PoE controller which class it belongs to when it is connected. The PoE controller then allocates to the interface the maximum power required by the class (see Table 395 on page 3010). It does not allocate power to an interface until a powered device is connected. Class 0 is the default class for powered devices that do not provide class information. • Static mode—In this mode, you specify the maximum power for each PoE interface. The PoE controller then allocates this amount of power to the interface from its total budget. For example, if you specify a maximum value of 8.0 W for ge-/0/0/3, the PoE controller allocates 8.0 W out of its total power budget for the interface. This amount is allocated to the interface whether or not a powered device is connected to the interface or whether the connected powered device uses less power than 8.0 W. For switches that support IEEE 802.3af (PoE), the maximum power permitted on any interface is 15.4 W. This wattage guarantees that, after line loss, the powered device receives 12.95 W, which is the maximum required by 802.3af-compliant powered devices. In both class and static mode, if the power consumption of a powered device exceeds the maximum power allocated to the interface, power to the interface is turned off. 3010 Chapter 113: Power over Ethernet (PoE)—Overview PoE Interface Power Priority You can configure a PoE interface to have either a high or low power priority. The power priority determines which interfaces receive power if PoE power demands are greater than the PoE power budget. If the total power allocated for all interfaces exceeds the switch budget, the lower priority interfaces are turned off and the power allocated to those interfaces drops to 0. Thus you should set interfaces that connect powered devices such as security cameras and emergency phones to high priority. Among PoE interfaces that have the same assigned priority, power priority is determined by the port number, with lower-numbered ports having higher priority. PoE Configuration and Monitoring The factory default configuration enables PoE on switches that support PoE. By default, the power management mode is class, and the power priority of all interfaces is low. If the default configuration meets your needs, you do not need to configure PoE before you connect powered devices to the switch. To monitor the powered devices and to manage PoE power consumption, you can use the CLI or J-Web interface to display the current power consumption of the PoE ports. You can also enable the monitoring of power consumption on a port over time and then view the collected records using the CLI or the J-Web interface. Related Documentation • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 3011 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3012 CHAPTER 114 Examples: PoE Configuration • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 Example: Configuring PoE Interfaces on a J-EX Series Switch Power over Ethernet (PoE) ports supply electric power over the same ports that are used to connect network devices and allow you to plug in devices that require both network connectivity and electric power, such as voice over IP (VoIP) phones, wireless access points, and some IP cameras. You do not need to configure PoE unless you wish to modify the default values or disable PoE on a specific interface. This example describes a default configuration of PoE interfaces on a J-EX Series switch: • Requirements on page 3013 • Overview and Topology on page 3013 • Configuration on page 3014 • Verification on page 3014 Requirements This example uses the following software and hardware components: • One J-EX Series switch that supports PoE Before you configure PoE, be sure you have: • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. Overview and Topology The topology used in this example consists of a switch that has 24 ports. Eight of the ports support PoE (IEEE 802.3af), which means they provide both network connectivity and electric power for powered devices such as VoIP telephones, wireless access points, 3013 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS and IP security cameras that require 12.95 W or less. The remaining 16 ports provide only network connectivity. You use the standard ports to connect devices that have their own power sources, such as desktop and laptop computers, printers, and servers. Table 396 on page 3014 details the topology used in this configuration example. Table 396: Components of the PoE Configuration Topology Property Settings Switch hardware J-EX Series switch with 24 Gigabit Ethernet ports: 8 PoE interfaces (ge-0/0/0 through ge-0/0/7) and 16 non-PoE interfaces (ge-0/0/8 through ge-0/0/23) VLAN name default Connection to a wireless access point (requires PoE) ge-0/0/0 Connections to Avaya IP telephones with integrated hubs that allow phone and desktop PC to connect to a single port (requires PoE) ge-0/0/1 through ge-0/0/7 Direct connections to desktop PCs, file servers, integrated printer/fax/copier machines (no PoE required) ge-0/0/8 through ge-0/0/20 Unused ports (for future expansion) ge-0/0/21 through ge-0/0/23 Configuration To enable the default PoE configuration on the switch, perform these tasks: CLI Quick Configuration To quickly enable the default configuration on the switch: Simply connect the powered devices to the PoE ports. Step-by-Step Procedure To use the PoE interfaces with default values: 1. Make sure the switch is powered on. 2. Connect the wireless access point to interface ge-0/0/0. 3. Connect the Avaya phones to interfaces ge-0/0/1 through ge-0/0/7. Verification To verify that PoE interfaces have been created and are operational, perform this task: • Verifying That the PoE Interfaces Have Been Created on page 3014 Verifying That the PoE Interfaces Have Been Created Purpose Action Verify that the PoE interfaces have been created on the switch. List all the PoE interfaces configured on the switch: user@switch> show poe interface 3014 Chapter 114: Examples: PoE Configuration Interface ge-0/0/0 ge-0/0/1 ge-0/0/2 ge-0/0/3 ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 Meaning Related Documentation Admin status Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Oper status Max power ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W Priority Low Low Low Low Low Low Low Low Power consumption Class 7.9W 0 3.2W 2 3.2W 2 3.2W 2 3.2W 2 3.2W 2 3.2W 2 3.2W 2 The show poe interface command lists PoE interfaces configured on the switch, with their status, priority, power consumption, and class. This output shows that eight interfaces have been created with default values and are consuming power at the expected rates. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 • Troubleshooting PoE Interfaces on page 3031 Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch Power over Ethernet (PoE) ports supply electric power over the same ports that are used to connect network devices. These ports allow you to plug in devices that need both network connectivity and electric power, such as voice over IP (VoIP) phones, wireless access points, and some IP cameras. By default, PoE ports on J-EX Series switches are set to low power priority. You can configure a PoE port to have a high power priority setting. If a situation arises where there is not sufficient power for all the PoE ports, the available power is directed to the higher priority ports, while power to the lower priority ports is shut down as needed. Thus you should set ports that connect to security cameras, emergency phones, and other high priority powered devices to high priority. This example describes how to configure a few high priority PoE interfaces. • Requirements on page 3015 • Overview and Topology on page 3016 • Configuration on page 3016 • Verification on page 3019 Requirements This example uses the following software and hardware components: • One J-EX Series switch that supports PoE Before you configure PoE, be sure you have: 3015 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Performed the initial switch configuration. See “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 161 or “Connecting and Configuring a J-EX Series Switch (J-Web Procedure)” on page 163 for details. Overview and Topology The topology used in this example consists of a switch that has 24 ports. Eight of the ports support PoE (IEEE 802.3af), which means they provide both network connectivity and electric power for powered devices such as VoIP telephones, wireless access points, and IP security cameras that require 12.95 W or less. The remaining 16 ports provide only network connectivity. You use the standard ports to connect devices that have their own power sources, such as desktop and laptop computers, printers, and servers. Table 397 on page 3016 details the topology used in this configuration example. Table 397: Components of the PoE Configuration Topology Property Settings Switch hardware Switch with 24 Gigabit Ethernet ports: 8 PoE interfaces (ge-0/0/0 through ge-0/0/7) and 16 non-PoE interfaces (ge-0/0/8 through ge-0/0/23) VLAN name default Connection to a wireless access point (requires PoE) ge-0/0/0 Security IP Cameras (require PoE) ge-0/0/1 and ge-0/0/2 high Emergency VoIP phone (requires PoE) ge-0/0/3 high VoIP phone in Executive Office (requires PoE) ge-0/0/4 high Other VoIP phones (require PoE) ge-0/0/5 through ge-0/0/7 Direct connections to desktop PCs, file servers, integrated printer/fax/copier machines (no PoE required) ge-0/0/8 through ge-0/0/20 Unused ports (for future expansion) ge-0/0/21 through ge-0/0/23 Configuration To configure PoE interfaces: CLI Quick Configuration By default, PoE interfaces are created for all PoE ports and PoE is enabled. The default priority for PoE interfaces is low. To quickly set some interfaces to high priority and to include descriptions of the interfaces, copy the following commands and paste them into the switch terminal window: [edit] set poe interface ge-0/0/1 priority high telemetries set poe interface ge-0/0/2 priority high telemetries set poe interface ge-0/0/3 priority high telemetries set poe interface ge-0/0/4 priority high telemetries 3016 Chapter 114: Examples: PoE Configuration set interfaces ge-0/0/0 description "wireless access point" set interfaces ge-0/0/1 description "security camera front door" set interfaces ge-0/0/2 description "security camera back door" set interfaces ge-0/0/3 description "emergency phone" set interfaces ge-0/0/4 description "Executive Office VoIP phone" set interfaces ge-0/0/5 description "staff VoIP phone" set interfaces ge-0/0/6 description "staff VoIP phone" set interfaces ge-0/0/7 description "staff VoIP phone" Step-by-Step Procedure To configure PoE interfaces with different priorities: 1. Set the interfaces connected to high priority powered devices to high priority. Include the telemetries statement for the high priority interfaces, thus enabling the logging of power consumption on those interfaces: [edit poe] user@switch# user@switch# user@switch# user@switch# 2. set interface ge-0/0/1 priority high telemetries set interface ge-0/0/2 priority high telemetries set interface ge-0/0/3 priority high telemetries set interface ge-0/0/4 priority high telemetries Provide descriptions for the PoE interfaces: [edit interfaces] user@switch# set ge-0/0/0 description "wireless access point" user@switch# set ge-0/0/1 description "security camera front door" user@switch# set ge-0/0/2 description "security camera back door" user@switch# set ge-0/0/3 description "emergency phone" user@switch# set ge-0/0/4 description "Executive Office VoIP phone" user@switch# set ge-0/0/5 description "staff VoIP phone" user@switch# set ge-0/0/6 description "staff VoIP phone" user@switch# set ge-0/0/7 description "staff VoIP phone" Results 3. Connect the wireless access point to interface ge-0/0/0. This interface uses the default PoE settings. 4. Connect the two security cameras to interfaces ge-0/0/1 and ge-0/0/2. These interfaces are set to high priority with telemetries enabled. 5. Connect the emergency VoIP phone to interface ge-0/0/3. This interface is set to high priority with telemetries enabled. 6. Connect the Executive Office VoIP phone to interface ge-0/0/4. This interface is set to high priority with telemetries enabled. 7. Connect the staff VoIP phones to ge-0/0/5, ge-0/0/6, and ge-0/0/7. These interfaces use the default PoE settings. Check the results of the configuration: [edit] user@switch# show interfaces { ge-0/0/0 { description "wireless access point"; unit 0 { family ethernet-switching; 3017 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } ge-0/0/1 { description "security camera front door"; unit 0 { family ethernet-switching; } } ge-0/0/2 { description "security camera back door"; unit 0 { family ethernet-switching; } } ge-0/0/3 { description "emergency phone"; unit 0 { family ethernet-switching; } } ge-0/0/4 { description "Executive Office VoIP phone"; unit 0 { family ethernet-switching; } } ge-0/0/5 { description "staff VoIP phone"; unit 0 { family ethernet-switching; } } ge-0/0/6 { description "staff VoIP phone"; unit 0 { family ethernet-switching; } } ge-0/0/7 { description "staff VoIP phone"; unit 0 { family ethernet-switching; } } } poe { interface all; interface ge-0/0/1 { priority high; telemetries; } interface ge-0/0/2 { priority high; telemetries; } interface ge-0/0/3 { 3018 Chapter 114: Examples: PoE Configuration priority high; telemetries; } interface ge-0/0/4 { priority high; telemetries; } } Verification To verify that PoE interfaces have been created and are operational, perform the following tasks: • Verifying That the PoE Interfaces Have Been Created with the Correct Priorities on page 3019 Verifying That the PoE Interfaces Have Been Created with the Correct Priorities Purpose Action Verify that the PoE interfaces on the switch are now set to the correct priority settings. List all the PoE interfaces configured on the switch: user@switch> show poe interface Interface Admin status Oper status ge-0/0/0 Enabled ON ge-0/0/1 Enabled ON ge-0/0/2 Enabled ON ge-0/0/3 Enabled ON ge-0/0/4 Enabled ON ge-0/0/5 Enabled ON ge-0/0/6 Enabled ON ge-0/0/7 Enabled ON Meaning Related Documentation Max power 15.4W 15.4W 15.4W 15.4W 15.4W 15.4W 15.4W 15.4W Priority Low High High High High Low Low Low Power consumption Class 7.9W 0 4.8W 0 4.8W 0 3.3W 2 4.7W 2 3.2W 2 3.3W 2 3.3W 2 The show poe interface command lists PoE interfaces configured on the switch, with their status, priority, power consumption, and class. This output shows that eight PoE interfaces are enabled. Interfaces ge-0/0/1 through ge-0/0/4 are configured as priority high. The remaining PoE interfaces are configured with the default priority value of low. • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Configuring PoE (CLI Procedure) on page 3021 • Troubleshooting PoE Interfaces on page 3031 3019 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3020 CHAPTER 115 Configuring PoE • Configuring PoE (CLI Procedure) on page 3021 • Configuring PoE (J-Web Procedure) on page 3023 Configuring PoE (CLI Procedure) Power over Ethernet (PoE) ports supply electric power over the same ports that are used to connect network devices. These ports allow you to plug in devices that require both network connectivity and electric power, such as voice over IP (VoIP) phones, wireless access points, and some IP cameras. For J-EX Series switches that support PoE ports, the factory default configuration enables PoE on the PoE-capable ports, with default settings in effect. You might not have to do any additional configuration if the default settings work for you. Table 398 on page 3021 shows the PoE options and their default settings for the switch as a whole and for the PoE interfaces. Table 398: PoE Configurable Options and Default Settings Option Default Description guard-band 0W Reserves up to 19 W out of the PoE power budget to be used in the case of a spike in PoE power consumption. management class Sets the PoE power management mode for the switch: Switch Options • static—The maximum power delivered by an interface is determined by the class of the connected powered device. No power is allocated to the interface until a powered device is connected. • class—The maximum power delivered by an interface is statically configured and independent of the class of the connected powered device. The maximum power is allocated to the interface even if a powered device is not connected notification-control Not included in default configuration When included in the configuration, enables PoE traps. Interface Options 3021 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 398: PoE Configurable Options and Default Settings (continued) Option Default Description priority low Sets an interface’s power priority to either low or high. If power is insufficient for all PoE interfaces, the low priority interfaces are shut down before the high priority interfaces. Among interfaces that have the same assigned priority, the power priority is determined by port number—with lower- numbered ports having higher priority. telemetries Not included in default configuration When included in the configuration, enables the logging of power consumption records on an interface. Logging occurs every five minutes for one hour unless you specify a different interval or duration. maximum-power 15.4 W (for switches that Sets the maximum power that can be delivered by a PoE interface. The maximum power allowed is the same as the default—either 15.4 W for switches that do not support IEEE 802.3at or 30.0 W for switches that do support it. support IEEE 802.3af) 30.0 W (for switches that support IEEE 802.3at) This setting is ignored if the power management mode is class. disable Not included in default configuration When included in the configuration, disables PoE on the interface. The interface maintains network connectivity but no longer supplies power to a connected powered device. Power is not allocated to the interface. To configure PoE: 1. To change power management mode from the default class mode to static mode: [edit poe] user@switch# set management static 2. To reserve a specified wattage of power in case of a spike in PoE consumption: [edit poe] user@switch# set guard-band 15 3. To configure a number of interfaces with the same settings (for example, to enable telemetry collection on all interfaces): [edit poe] user@switch# set interface all telemetries 4. To configure individual interfaces with different settings: [edit poe] user@switch# set interface ge-0/0/0 priority high telemetries duration 24 [edit poe] user@switch# set interface ge-0/0/1 [edit poe] user@switch# set interface ge-0/0/7 disable When you configure an individual interface, its configuration overrides any settings you configure with the set poe interface all command. For example, ge-0/0/1 in the example above retains the default settings regardless of any settings configured with the set poe interface all command. 3022 Chapter 115: Configuring PoE Related Documentation • Configuring PoE (J-Web Procedure) on page 3023 • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 • PoE and J-EX Series Switches Overview on page 3009 Configuring PoE (J-Web Procedure) Power over Ethernet (PoE) ports supply electric power over the same ports that are used to connect network devices to J-EX Series switches. These ports allow you to plug in devices that require both network connectivity and electric power, such as VoIP phones, wireless access points, and some IP cameras. Using the Power over Ethernet (PoE) Configuration page in the J-Web interface, you can modify the settings of all interfaces that are PoE-enabled. To configure PoE: 1. Select Configure > Power over Ethernet. The page displays a list of all interfaces except uplink ports. Specific operational details about an interface are displayed in the Details section of the page. The details include the PoE Operational Status and Port class. 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 334 for details about all commit options. 2. Click one: • Edit—Changes PoE settings for the selected port as described in Table 399 on page 3023. • System Settings—Modifies general PoE settings as described in Table 400 on page 3024. Table 399: PoE Edit Settings Field Description Your Action Enable PoE Specifies that PoE is enabled on the interface. Select this option to enable PoE on the interface. Priority Lists the power priority (Low or High) configured on ports enabled for PoE. Set the priority as High or Low. 3023 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 399: PoE Edit Settings (continued) Field Description Your Action Maximum Power Specifies the maximum PoE wattage available to provision active PoE ports on the switch. Select a value in watts. If no value is specified, the default is 15.4. Table 400: System Settings Field Description Your Action PoE Management Specifies the power management mode. The options are: static and class. By default the power management mode is static. Select class to change the power management mode. NOTE: When the power management mode is set to class, the maximum power value is overridden by the maximum power value of the class of power device that is connected to the switch on the PoE port. Guard Band (watts) Specifies the band to control power availability on the switch. Related Documentation 3024 Enter a value to set the guard band value in watts. The default value is 0. • Configuring PoE (CLI Procedure) on page 3021 • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Monitoring PoE on page 3025 • PoE and J-EX Series Switches Overview on page 3009 CHAPTER 116 Verifying PoE Configuration • Monitoring PoE on page 3025 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 Monitoring PoE Purpose Action Use the monitoring functionality to view real-time data of the power consumed by each PoE interface, and to enable and configure telemetry values. When telemetry is enabled, the software measures the power consumed by each interface and stores the data for future reference. To monitor PoE using the J-Web interface, select Monitor > Power over Ethernet. To monitor PoE power consumption with CLI commands in the CLI Terminal in the J-Web interface: 1. Select Troubleshoot > CLI Terminal. 2. Type a CLI command: • show poe controller • show poe interface • show poe telemetries interface For detailed information about using these CLI commands to monitor PoE power consumption, see “Monitoring PoE Power Consumption (CLI Procedure)” on page 3026. Meaning In the J-Web interface the PoE Monitoring screen is divided into two parts. The top half of the screen displays real-time data of the power consumed by each interface and a list of ports that utilize maximum power. Select a particular interface to view a graph of the power consumed by the selected interface. The bottom half of the screen displays telemetry information for interfaces. The Telemetry Status field displays whether telemetry has been enabled on the interface. Click the Show Graph button to view a graph of the telemetries. The graph can be based on power 3025 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS or voltage. To modify telemetry values, click Edit. Specify Interval in minutes, Duration in hours, and select Log Telemetries to enable telemetry on the selected interface. Related Documentation • Configuring PoE (CLI Procedure) on page 3021 • Configuring PoE (J-Web Procedure) on page 3023 • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 Monitoring PoE Power Consumption (CLI Procedure) You can monitor Power over Ethernet (PoE) power consumption, both for the switch as a whole and for individual PoE interfaces. This topic describes how to monitor: • PoE Power Consumption for the Switch on page 3026 • Current Power Consumption for PoE Interfaces on page 3026 • Power Consumption for PoE Interfaces over Time on page 3027 PoE Power Consumption for the Switch Purpose Action Determine the current PoE power consumption for the switch as a whole. Enter the following command: user@switch> show poe controller Controller Maximum Power index power consumption 0 130 W 65W Meaning Guard band 15W Management Static At the time the command was executed, the PoE interfaces on the switch were consuming 65 W out of the switch PoE power budget of 130 W. Current Power Consumption for PoE Interfaces Purpose Action Determine the current power consumption for individual PoE interfaces. To monitor the power consumption of all PoE interfaces on the switch, use the following command: user@switch> show poe interface Interface Admin status Oper status ge-0/0/0 Enabled ON ge-0/0/1 Enabled ON ge-0/0/2 Enabled ON ge-0/0/3 Enabled ON 3026 Max power 15.4W 15.4W 15.4W 7.0W Priority Low High Low Low Power consumption Class 7.4W 0 12.0W 0 12.4W 0 5.3W 2 Chapter 116: Verifying PoE Configuration ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 Enabled Disabled Enabled Disabled ON Disabled OFF Disabled 4.0W 0.0W 15.4W 0.0W Low Low Low Low 4.0W 0.0W 0.0W 0.0W 1 0 0 0 To monitor the power consumption of an individual PoE interface, use the following command: user@switch> show poe interface ge-0/0/3 PoE interface status: PoE interface : ge-0/0/3 Administrative status : Enabled Operational status : ON Power limit on the interface : 7.0W Priority : Low Power consumed : 5.3W Class of power device : 2 Meaning Using interface ge-0/0/3 as an example, the powered device connected to the interface was consuming 5.3 W at the time the command was executed. Power Consumption for PoE Interfaces over Time Purpose Monitor the power consumption of a PoE interface over a period of time. The records collected remain available for future viewing. You can specify the intervals at which power consumption data is collected, from once every minute to once every 30 minutes. The default is once every 5 minutes. You can also specify the duration over which the records are collected, from 1 hour (default) to 24 hours. Action To collect historical records of PoE interface power consumption and display those records: 1. Add the telemetries statement to the PoE interface configuration: [edit] user@switch# set poe interface ge-0/0/5 telemetries interval 10 When you commit the configuration, record collection begins. 2. Display the collected records: user@switch> show poe telemetries interface ge-0/0/5 all Sl No Timestamp Power Voltage 1 03-19-2010 13:00:07 UTC 3.9W 50.9V 2 03-19-2010 12:50:07 UTC 3.9W 50.9V 3 03-19-2010 12:40:07 UTC 3.9W 50.9V 4 03-19-2010 12:30:07 UTC 3.9W 50.9V 5 03-19-2010 12:20:07 UTC 3.9W 50.9V 6 03-19-2010 12:10:07 UTC 3.9W 50.9V To start another session of record collection on the interface, you must commit the configuration again. 3027 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning Related Documentation Over the hour in which the PoE power consumption data on ge-0/0/5 was collected, the connected powered device consistently consumed 3.9 W. • Configuring PoE (CLI Procedure) on page 3021 • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 Verifying PoE Configuration and Status (CLI Procedure) You can verify the Power over Ethernet (PoE) configuration and status on a J-EX Series switch. This topic describes how to verify the: • Number of PoE Ports on the Switch on page 3028 • PoE Controller Configuration and Status on page 3028 • PoE Interface Configuration and Status on page 3029 • PoE SNMP Trap Generation Status on page 3029 Number of PoE Ports on the Switch Purpose Action Verify the number of PoE ports on a switch. The number of PoE ports on a switch varies according to switch model. Enter the following command: user@switch> show chassis hardware Hardware inventory: Item Version Part number Chassis Routing Engine 0 REV 11 750-021261 FPC 0 REV 11 750-021261 CPU BUILTIN PIC 0 BUILTIN Power Supply 0 REV 03 740-020957 Fan Tray Meaning Serial number BH0208375304 BH0208375304 BH0208375304 BUILTIN BUILTIN AT0508285661 Description EX4200-24T EX4200-24T, 8 POE EX4200-24T, 8 POE FPC CPU 24x 10/100/1000 Base-T PS 320W AC Fan Tray The switch is a J-EX4200-24T model with eight PoE ports. PoE Controller Configuration and Status Purpose Action Verify the PoE controller configuration and status, such as the PoE power budget, total PoE power consumption, and power management mode. Enter the following command: user@switch> show poe controller Controller Maximum Power 3028 Guard band Management Chapter 116: Verifying PoE Configuration index 0 Meaning power 130 W consumption 43W 15W Class The switch has an overall PoE power budget of 130 W, of which 43 W were being used by the PoE ports at the time the command was executed. The Guard band field shows that 15 W is reserved out of the PoE power budget to protect against spikes in power demand. The power management mode is class. PoE Interface Configuration and Status Purpose Action Verify that PoE interfaces are enabled and set to the correct maximum power and priority settings. Also verify current operational status and power consumption. To view configuration and status for all PoE interfaces, enter: user@switch> show poe interface Interface Admin status Oper status ge-0/0/0 Enabled ON ge-0/0/1 Enabled ON ge-0/0/2 Enabled ON ge-0/0/3 Enabled ON ge-0/0/4 Disabled Disabled ge-0/0/5 Enabled ON ge-0/0/6 Enabled ON ge-0/0/7 Enabled OFF Max power 15.4W 15.4W 15.4W 15.4W 0.0W 15.4W 15.4W 15.4W Priority Low High High High Low Low Low Low Power consumption Class 7.9W 3 4.8W 0 4.8W 0 3.3W 2 0.0W 0 3.2W 2 3.3W 2 0.0W 0 To view configuration and status for a single PoE interface, enter: user@switch> show poe interface ge-0/0/3 PoE interface status: PoE interface : ge-0/0/3 Administrative status : Enabled Operational status : ON Power limit on the interface : 15.4W Priority : High Power consumed : 3.3W Class of power device : 2 Meaning The command output shows the status and configuration of interfaces. For example, the interface ge-0/0/3 is administratively enabled. Its operational status is ON; that is, the interface is currently delivering power to a connected powered device. The maximum power the interface can deliver is 15.4 W. The interface has a high power priority. At the time the command was executed, the powered device was consuming 3.3 W. The IEEE 802.3af class of the powered device is class 2. PoE SNMP Trap Generation Status Purpose Action Verify the status of the notification-control option, which determines whether or not PoE SNMP traps are enabled. Enter the following command: user@switch> show poe notification-control FPC slot Notification-control-status 0 OFF 3029 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning Related Documentation 3030 PoE SNMP traps are not enabled. • Configuring PoE (CLI Procedure) on page 3021 • Example: Configuring PoE Interfaces on a J-EX Series Switch on page 3013 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 CHAPTER 117 Troubleshooting PoE Configuration • Troubleshooting PoE Interfaces on page 3031 Troubleshooting PoE Interfaces Problem A Power over Ethernet (PoE) interface is not supplying power to the powered device. Solution Check for the items shown in Table 401 on page 3031. Table 401: Troubleshooting a PoE Interface Related Documentation Items to Check Explanation Is the switch a full PoE model or a partial PoE model? If you are using a partial PoE model, only interfaces ge-0/0/0 through ge-0/0/7 can function as PoE ports. Has PoE capability been disabled for that interface? Use the show poe interface command to check PoE interface status. Is the cable properly seated in the port socket? Check the hardware. Has the PoE power budget been exceeded for the switch? Use the show poe controller command to check the PoE power budget and consumption for the switch. Does the powered device require more power than is available on the interface? Use the show poe interface command to check the maximum power provided by the interface. If the telemetries option has been enabled for the interface, check the history of power consumption. Use the show poe telemetries interface command to display the history of power consumption. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 • Configuring PoE (CLI Procedure) on page 3021 3031 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3032 CHAPTER 118 Configuration Statements for PoE • [edit poe] Configuration Statement Hierarchy on page 3033 [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 • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 • PoE and EX Series Switches Overview on page 3009 3033 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 3034 disable; [edit poe interface (all | interface-name)], [edit poe interface (all | interface-name) telemetries], [edit poe notification-control fpc slot-number] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable a PoE interface, disable the collection of power consumption data for a PoE interface, or disable the generation of the PoE SNMP traps. The action of the disable statement depends on which statement it is used with: • When used with interface—Disable the PoE capability of this interface. The interface operates as a standard network access interface, and power is no longer allocated to it from the PoE power budget. Although the PoE capability is disabled, the PoE configuration for the interface is retained. To re-enable the PoE capability of this interface, delete the disable statement from the interface entry in the configuration. • When used with telemetries—Disable the collection of PoE power consumption records for this port. Any previously collected records are deleted. However, the telemetries configuration is retained, including the values for interval and duration. To re-enable record collection, delete the disable statement from the telemetries entry in the configuration. • When used with notification-control—Disable the generation of PoE traps. To re-enable PoE traps, delete the disable statement from the notification-control entry in the configuration. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 Chapter 118: Configuration Statements for PoE duration Syntax Hierarchy Level Release Information Description Options duration hours; [edit poe interface (all | interface-name) telemetries] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Modify the duration over which data is collected when you are monitoring the power consumption of a PoE interface. hours —Number of hours over which the data is to be collected. Range: 1 through 24 Default: 1 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 3035 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS fpc Syntax Hierarchy Level Release Information Description Default Options fpc slot-number { disable; } [edit poe notification-control] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the generation of PoE traps for the specified FPC. PoE traps are disabled by default. slot-number—The FPC slot number, where slot- number is: • 0—On a standalone J-EX4200 switch. • 0 through 9—On a J-EX4200 switch in a Virtual Chassis, indicating the member ID. The remaining statement is explained separately. Required Privilege Level Related Documentation 3036 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 Chapter 118: Configuration Statements for PoE guard-band Syntax Hierarchy Level Release Information Description Options guard-band watts; [edit poe] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Reserve a specified amount of power out of the PoE power budget in case of a spike in PoE consumption. watts —Amount of power to be reserved in case of a spike in PoE consumption. Range: 0 through 19 Default: 0 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 3037 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Options interface (all | interface-name) { disable; maximum-power watts; priority (high | low); telemetries { disable; duration hours; interval minutes; } } [edit poe] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify a PoE interface to be configured. all—All PoE interfaces on the switch that have not been individually configured for PoE. If a PoE interface has been individually configured, that configuration overrides any settings specified with all. interface-name—Name of the specific interface being configured. If you use the interface statement without any substatements, PoE is enabled on all interfaces or the specified interface with default values for the remaining statements. The remaining statements are explained separately. Required Privilege Level Related Documentation 3038 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 Chapter 118: Configuration Statements for PoE interval Syntax Hierarchy Level Release Information Description Options interval minutes; [edit poe interface (all | interface-name) telemetries] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Modify the interval at which data is collected when you are monitoring the power consumption of a PoE interface. minutes—Frequency of data collection. Range: 1 through 30 Default: 5 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 • Configuring PoE (J-Web Procedure) on page 3023 3039 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS management Syntax Hierarchy Level Release Information Description Default Options management (class | static); [edit poe] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Designate the way that the switch's PoE controller allocates power to the PoE interfaces. class • class—The amount of power allocated to the interface is determined by the class of the connected powered device. If no powered device is connected, no power is allocated to the interface. See “PoE and J-EX Series Switches Overview” on page 3009 for more information about classes of powered devices. • static—The amount of power allocated to the interface is determined by the value of the maximum-power statement, not the class of the connected powered device. This amount is allocated even when a powered device is not connected to the interface, ensuring that power is available when needed. Required Privilege Level Related Documentation 3040 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 Chapter 118: Configuration Statements for PoE maximum-power Syntax Hierarchy Level Release Information Description maximum-power watts; [edit poe interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the maximum amount of power that the switch can supply to the PoE port. NOTE: Although you can set this value when PoE power management is in class mode, it does not establish the maximum power for the port. Instead, the IEEE 802.3af or IEEE 802.3at class of the connected device determines the maximum power for the port. Options watts —The maximum number of watts that can be supplied to the port. Range: 0.0 through 15.4 for switches that support only IEEE 802.3af and 0.0 through 30.0 for switches that also support IEEE 802.3at Default: 15.4 for switches that support IEEE 802.3af and 30.0 for switches that support IEEE 802.3at Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 3041 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS notification-control Syntax Hierarchy Level Release Information Description notification-control { fpc slot-number { disable; } } [edit poe] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable or disable the generation of PoE SNMP traps. If PoE traps are enabled, an SNMP trap is sent whenever a PoE interface is enabled or disabled. The remaining statements are explained separately. Required Privilege Level Related Documentation 3042 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 Chapter 118: Configuration Statements for PoE priority Syntax Hierarchy Level Release Information Description Default Options priority (low | high); [edit poe interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the power priority for individual interfaces when there is insufficient power for all PoE interfaces. If the switch needs to shut down powered devices because PoE demand exceeds the PoE budget, low priority devices are shut down before high priority devices. Among interfaces that have the same assigned priority, priority is determined by port number, with lower-numbered ports having higher priority. low value—high or low: • high—Specifies that this interface is to be treated as high priority in terms of power allocation. If the switch needs to shut down powered devices because PoE demand exceeds the PoE budget, power is not shut down on this interface until it has been shut down on all the low priority interfaces. • low—Specifies that this interface is to be treated as low priority in terms of power allocation. If the switch needs to shut down powered devices because PoE demand exceeds the PoE budget, power is shut down on this interface before it is shut down on high priority interfaces. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 3043 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS telemetries Syntax Hierarchy Level Release Information Description telemetries { disable; duration hours; interval minutes; } [edit poe interface (all | interface-name)] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the logging of power consumption of a PoE interface over time. If you want to log the power consumption of a PoE interface, you must explicitly specify the telemetries statement. When you commit the configuration, logging begins, with data being collected at the specified intervals. Logging stops at the end of the specified duration. If you did not specify the duration and interval statements, data is collected at five minute intervals for one hour. The remaining statements are explained separately. Default Required Privilege Level Related Documentation 3044 Logging of power consumption is disabled. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Example: Configuring PoE Interfaces with Different Priorities on a J-EX Series Switch on page 3015 • Configuring PoE (CLI Procedure) on page 3021 CHAPTER 119 Operational Mode Commands for PoE 3045 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show poe controller Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show poe controller Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display configuration and status of the PoE controller. view • show poe interface on page 3048 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 • Troubleshooting PoE Interfaces on page 3031 show poe controller on page 3047 Table 402 on page 3046 lists the output fields for the show poe controller command. Output fields are listed in the approximate order in which they appear. Table 402: show poe controller Output Fields 3046 Field Name Field Description Controller index Controller number. Maximum power Maximum power that the switch can provide to the PoE ports. Power consumption Total amount of power being used by the PoE ports at the time the command is executed. Guard Band Amount of power that has been placed in reserve for power demand spikes and that cannot be allocated to a PoE interface. Management Power management mode: either Static or Class. Chapter 119: Operational Mode Commands for PoE show poe controller user@switch> show poe controller Controller index 0 Maximum power 130 W Power consumption 43W Guard band 15W Management Class 3047 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show poe interface Syntax Release Information Description Options show poe interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the status of PoE interfaces. none—Display status of all PoE interfaces on the switch. interface-name—(Optional) Display the status of a specific PoE interface on the switch. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show poe controller on page 3046 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 • Troubleshooting PoE Interfaces on page 3031 show poe interface on page 3049 show poe interface ge-0/0/3 on page 3049 Table 403 on page 3048 lists the output fields for the show poe interface command. Output fields are listed in the approximate order in which they appear. Table 403: show poe interface Output Fields Field Name (All Interfaces Output) Field Name (Single Interface Output) Field Description Interface PoE Interface Interface name. Admin status Administrative status Administrative state of the PoE interface: Enabled or Disabled. If the PoE interface is disabled, it can provide network connectivity, but it cannot provide power to connected devices. Oper status Operational status Operational state of the PoE interface: • ON—The interface is currently supplying power to a powered device. • OFF—PoE is enabled on the interface, but the interface is not currently supplying power to a powered device. • Disabled—PoE is disabled on the interface. Max power Power limit on the interface Maximum power that can be provided by the interface. Priority Priority Interface power priority: either High or Low. 3048 Chapter 119: Operational Mode Commands for PoE Table 403: show poe interface Output Fields (continued) Field Name (All Interfaces Output) Field Name (Single Interface Output) Field Description Power consumption Power consumed Amount of power being used by the interface at the time the command is executed. Class Class of power device IEEE 802.3af or IEEE 802.3at classification of the powered device. Class 0 is the default class and is used when the class of the powered device is unknown or no powered device is connected. show poe interface user@switch> show poe interface Interface ge-0/0/0 ge-0/0/1 ge-0/0/2 ge-0/0/3 ge-0/0/4 ge-0/0/5 ge-0/0/6 ge-0/0/7 show poe interface ge-0/0/3 Admin status Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Oper status Max power ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W ON 15.4W Priority Low Low Low Low Low Low Low Low Power consumption Class 7.9W 0 3.2W 2 3.2W 2 3.2W 2 3.2W 2 3.2W 2 3.2W 2 3.2W 2 user@switch> show poe interface ge-0/0/3 PoE interface status: PoE interface : ge-0/0/3 Administrative status : Enabled Operational status : ON Power limit on the interface : 7.0W Priority : Low Power consumed : 5.3W Class of power device : 2 3049 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show poe notification-control Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show poe notification-control Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the state of the PoE notification-control option, which enables or disables PoE SNMP traps. view • show poe controller on page 3046 • show poe interface on page 3048 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 show poe notification-control on page 3051 Table 404 on page 3050 lists the output fields for the show poe notification-control command. Output fields are listed in the approximate order in which they appear. Table 404: show poe notification-control Output Fields Field Name Field Description FPC slot FPC slot number. Notification-control-status Status of notification control: • ON—PoE traps are enabled. An SNMP trap is sent when a PoE interface is enabled or disabled. • 3050 OFF—PoE traps are disabled. Chapter 119: Operational Mode Commands for PoE show poe notification-control user@switch> show poe notification-control FPC slot Notification-control-status 0 OFF 3051 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show poe telemetries interface Syntax Release Information Description show poe telemetries interface interface-name ( all | n ) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a history of power consumption on the specified interface. Telemetries must be enabled on the interface before you can display a history of power consumption. Options interface-name—Display power consumption records for the specified PoE interface. all—Display all power consumption records for the PoE interface. n—Display the specified number of power consumption records for the PoE interface. The records displayed are the most recent. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show poe interface on page 3048 • show poe controller on page 3046 • Monitoring PoE Power Consumption (CLI Procedure) on page 3026 • Verifying PoE Configuration and Status (CLI Procedure) on page 3028 • Troubleshooting PoE Interfaces on page 3031 show poe telemetries interface (Last 10 Records) on page 3053 show poe telemetries interface (All Records) on page 3053 Table 405 on page 3052 lists the output fields for the show poe telemetries interface command. Output fields are listed in the approximate order in which they appear. Table 405: show poe telemetries interface Output Fields 3052 Field Name Field Description S1 No Number of the record for the specified port. Record number 1 is the most recent. Timestamp Date and time when the power-consumption data was gathered. Power Amount of power provided by the specified interface at the time the data was gathered. Voltage Maximum voltage provided by the specified interface at the time the data was gathered. Chapter 119: Operational Mode Commands for PoE show poe telemetries interface (Last 10 Records) user@switch> show poe telemetries interface ge-0/0/0 10 Sl No Timestamp Power Voltage 1 01-27-2008 18:19:58 UTC 15.4W 51.6V 2 01-27-2008 18:18:58 UTC 15.4W 51.6V 3 01-27-2008 18:17:58 UTC 15.4W 51.6V 4 01-27-2008 18:16:58 UTC 15.4W 51.6V 5 01-27-2008 18:15:58 UTC 15.4W 51.6V 6 01-27-2008 18:14:58 UTC 15.4W 51.6V 7 01-27-2008 18:13:58 UTC 15.4W 51.6V 8 01-27-2008 18:12:57 UTC 15.4W 51.6V 9 01-27-2008 18:11:57 UTC 15.4W 51.6V 10 01-27-2008 18:10:57 UTC 15.4W 51.6V show poe telemetries interface (All Records) user@switch> show poe telemetries interface ge-0/0/0 all Sl No Timestamp Power Voltage 1 01-27-2008 18:19:58 UTC 15.4W 51.6V 2 01-27-2008 18:18:58 UTC 15.4W 51.6V 3 01-27-2008 18:17:58 UTC 15.4W 51.6V 4 01-27-2008 18:16:58 UTC 15.4W 51.6V 5 01-27-2008 18:15:58 UTC 15.4W 51.6V 6 01-27-2008 18:14:58 UTC 15.4W 51.6V 7 01-27-2008 18:13:58 UTC 15.4W 51.6V 8 01-27-2008 18:12:57 UTC 15.4W 51.6V 9 01-27-2008 18:11:57 UTC 15.4W 51.6V 10 01-27-2008 18:10:57 UTC 15.4W 51.6V 11 01-27-2008 18:09:57 UTC 15.4W 51.6V 12 01-27-2008 18:08:57 UTC 15.4W 51.6V 13 01-27-2008 18:07:57 UTC 15.4W 51.6V 14 01-27-2008 18:06:57 UTC 15.4W 51.6V 15 01-27-2008 18:05:57 UTC 15.4W 51.6V 16 01-27-2008 18:04:56 UTC 15.4W 51.6V 17 01-27-2008 18:03:56 UTC 15.4W 51.6V 18 01-27-2008 18:02:56 UTC 15.4W 51.6V 19 01-27-2008 18:01:56 UTC 15.4W 51.6V 20 01-27-2008 18:00:56 UTC 15.4W 51.6V 21 01-27-2008 17:59:56 UTC 15.4W 51.6V 22 01-27-2008 17:58:56 UTC 15.4W 51.6V 23 01-27-2008 17:57:56 UTC 15.4W 51.6V 24 01-27-2008 17:56:55 UTC 15.4W 51.6V 25 01-27-2008 17:55:55 UTC 15.4W 51.6V 26 01-27-2008 17:54:55 UTC 15.4W 51.6V 27 01-27-2008 17:53:55 UTC 15.4W 51.6V 28 01-27-2008 17:52:55 UTC 15.4W 51.6V 29 01-27-2008 17:51:55 UTC 15.4W 51.6V 30 01-27-2008 17:50:55 UTC 15.4W 51.6V 31 01-27-2008 17:49:55 UTC 15.4W 51.6V 32 01-27-2008 17:48:55 UTC 15.4W 51.6V 33 01-27-2008 17:47:54 UTC 15.4W 51.6V 34 01-27-2008 17:46:54 UTC 15.4W 51.6V 35 01-27-2008 17:45:54 UTC 15.4W 51.6V 36 01-27-2008 17:44:54 UTC 15.4W 51.6V 37 01-27-2008 17:43:54 UTC 15.4W 51.6V 38 01-27-2008 17:42:54 UTC 15.4W 51.6V 39 01-27-2008 17:41:54 UTC 15.4W 51.6V 40 01-27-2008 17:40:54 UTC 15.4W 51.6V 41 01-27-2008 17:39:53 UTC 15.4W 51.6V 42 01-27-2008 17:38:53 UTC 15.4W 51.6V 43 01-27-2008 17:37:53 UTC 15.4W 51.6V 44 01-27-2008 17:36:53 UTC 15.4W 51.6V 3053 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3054 PART 23 MPLS • MPLS—Overview on page 3057 • Example of MPLS Configuration on page 3071 • Configuring MPLS on page 3097 • Verifying MPLS on page 3115 • Configuration Statements for MPLS on page 3121 • Operational Mode Commands for MPLS on page 3139 3055 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3056 CHAPTER 120 MPLS—Overview • Junos OS MPLS for J-EX Series Switches Overview on page 3057 • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 • Understanding MPLS and Path Protection on J-EX Series Switches on page 3063 • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 3064 • Understanding MPLS Label Operations on J-EX Series Switches on page 3067 Junos OS MPLS for J-EX Series Switches Overview You can configure Junos OS MPLS on J-EX Series Switches to increase transport efficiency in the network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions. Junos OS MPLS for J-EX Series switches supports: • Layer 2 protocols • Layer 2 VPNs • RSVP-based label-switched paths (LSPs) • MPLS-based circuits cross-connect (CCCs) • IP over MPLS • Class of service (CoS) NOTE: MPLS configurations on J-EX Series switches are compatible with configurations on other devices running Junos OS that support MPLS and CCC. • Benefits of MPLS on page 3057 • Additional Benefits of MPLS and Traffic Engineering on page 3058 Benefits of MPLS MPLS has the following advantages over conventional packet forwarding: 3057 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS • Packets arriving on different ports can be assigned different labels. • A packet arriving at a particular provider edge switch may be assigned a label that is different from that of the same packet entering the network at a different provider edge switch. As a result, forwarding decisions that depend on the ingress provider edge switch can be easily made. • Sometimes it is desirable to force a packet to follow a particular route that is explicitly chosen at or before the time the packet enters the network, rather than letting it follow the route chosen by the normal dynamic routing algorithm as the packet travels through the network. In MPLS, a label can be used to represent the route so that the packet need not carry the identity of the explicit route. NOTE: MPLS configurations on J-EX Series switches do not support: • LDP-based MPLS • Routed VLAN interfaces (RVIs) • Q-in-Q tunneling • Aggregated Ethernet interfaces (LAGs) on CCCs • CCCs with a beginning and ending on the same switch Additional Benefits of MPLS and Traffic Engineering MPLS is the packet-forwarding component of the Junos OS traffic engineering architecture. Traffic engineering provides the capabilities to do the following: Related Documentation 3058 • Route primary paths around known bottlenecks or points of congestion in the network. • Provide precise control over how traffic is rerouted when the primary path is faced with single or multiple failures. • Provide efficient use of available aggregate bandwidth and long-haul fiber by ensuring that certain subsets of the network are not overutilized while other subsets of the network along potential alternate paths are underutilized. • Maximize operational efficiency. • Enhance the traffic-oriented performance characteristics of the network by minimizing packet loss, minimizing prolonged periods of congestion, and maximizing throughput. • Enhance statistically bound performance characteristics of the network (such as loss ratio, delay variation, and transfer delay) required to support a multiservice Internet. • Understanding MPLS Label Operations on J-EX Series Switches on page 3067 • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 • Example: Configuring MPLS on J-EX Series Switches on page 3071 Chapter 120: MPLS—Overview • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ • Junos OS VPNs Configuration Guide at http://www.juniper.net/techpubs/software/junos/ Understanding Junos OS MPLS Components for J-EX Series Switches Junos OS MPLS for J-EX Series Switches supports Layer 2 protocols and Layer 2 virtual private networks (VPNs). You can configure MPLS on J-EX Series switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions. This topic includes: • Provider Edge Switches on page 3059 • Provider Switch on page 3060 • Components Required for All Switches in the MPLS Network on page 3060 • Family MPLS on page 3062 Provider Edge Switches To implement MPLS on J-EX Series switches, you must configure two provider edge (PE) switches—that is, an ingress (local) PE switch and an egress (remote) PE switch. The ingress switch (the entry point to the MPLS tunnel) receives an IP packet, analyzes it, and pushes an MPLS label onto it. This label places the packet in a forwarding equivalence class (FEC) and determines its handling and destination through the MPLS tunnel. The egress provider edge switch (the exit point from the MPLS tunnel) pops the MPLS label off the outgoing packet. MPLS traffic is bidirectional. Therefore, each PE switch can be configured as both an ingress switch and an egress switch, depending on the direction of the traffic. J-EX Series switches can handle only single-label MPLS packets. If a packet already has an MPLS label, the PE switch removes the label and swaps it for another MPLS label. MPLS Protocol and Label Switched Paths Each PE switch must be configured to support the MPLS protocol, and the MPLS stanza must include the configuration of a label-switched path (LSP) that specifies the address of the remote PE switch. Junos OS MPLS for J-EX Series switches supports RSVP-based LSPs. Circuit Cross-Connect for Customer-Edge Interfaces You can configure the customer-edge interfaces of the PE switches as a circuit cross-connect (CCC), to create a transparent connection between two circuits. When you configure an interface as a CCC, the interface no longer belongs to a default VLAN. The interface becomes an MPLS tunnel — used exclusively for MPLS packets. You can 3059 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS create different CCCs for different customers or for segregating different traffic streams over different MPLS tunnels. Using CCC, you can connect the following types of circuits: • Local interface with remote interface or VLAN • Local VLAN with remote interface or VLAN NOTE: To configure a VLAN circuit as a CCC, you must enable VLAN tagging and specify a VLAN ID. MPLS on J-EX Series switches does not support the following types of CCC configurations: • LDP-based MPLS • Routed VLAN interfaces (RVIs) • Q-in-Q tunneling • Aggregated Ethernet interfaces (LAGs) on CCCs • CCCs with a beginning and ending on the same switch IP over MPLS For Customer-Edge Interfaces You can configure the customer-edge interfaces of the PE switches for IP over MPLS using a Layer 3 interface and a static route from the ingress PE switch to the egress PE switch. See “Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure)” on page 3107 for additional information. Provider Switch You must configure one or more provider switches as transit switches within the network to support the forwarding of MPLS packets. You can add provider switches without changing the configuration of the PE switches. A provider switch does not analyze the packets. It refers to an MPLS label forwarding table and swaps one label for another. The new label determines the next hop along the MPLS tunnel. A provider switch cannot perform the push or pop operations. Components Required for All Switches in the MPLS Network You must configure the following components on both the provider edge and the provider switches: 3060 • Routing Protocol on page 3061 • Traffic Engineering on page 3061 • MPLS Protocol on page 3061 • RSVP on page 3061 Chapter 120: MPLS—Overview Routing Protocol MPLS works in coordination with the interior gateway protocol (IGP). Therefore, you must configure OSPF or IS-IS as the routing protocol on the loopback interface and core interfaces of both the provider edge and provider switches. These core interfaces can be either Gigabit Ethernet or 10-Gigabit Ethernet interfaces, and they can be configured as either individual interfaces or aggregated Ethernet interfaces. NOTE: These core interfaces cannot be configured with VLAN tagging or a VLAN ID. When you configure them to belong to family mpls, they are removed from the default VLAN. They operate as an exclusive tunnel for MPLS traffic. Traffic Engineering Traffic engineering maps traffic flows onto an existing physical topology and provides the ability to move traffic flow away from the shortest path selected by the IGP and onto a potentially less congested physical path across a network. Traffic engineering enables the selection of specific end-to-end paths to send given types of traffic through your network. For MPLS to work properly, you must enable traffic engineering for the specified routing protocol. MPLS Protocol You must enable the MPLS protocol on all switches that participate in the MPLS network and apply it to the core interfaces of both the provider edge and provider switches. You do not need to apply it to the loopback interface, because the MPLS protocol uses the framework established by the RSVP session to create LSPs. On the provider edge switches, the configuration of the MPLS protocol must also include the definition of an LSP. RSVP Resource Reservation Protocol (RSVP) is a signaling protocol that allocates and distributes labels throughout an MPLS network. RSVP sets up unidirectional paths between the ingress provider edge switch and the egress provider edge switch. RSVP makes the LSPs dynamic; it can detect topology changes and outages and establish new LSPs to move around a failure. You must enable RSVP and apply it to the loopback interface and the core interface of both the provider edge and provider switches. The path message contains the configured information about the resources required for the LSP to be established. When the egress switch receives the path message, it sends a reservation message back to the ingress switch. This reservation message is passed along from switch to switch along the same path as the original path message. Once the ingress switch receives this reservation message, an RSVP path is established. The established LSP stays active as long as the RSVP session remains active. RSVP continues activity through the transmissions and responses to RSVP path and reservation 3061 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS messages. If the messages stop for three minutes, the RSVP session terminates and the LSP is lost. RSVP runs as a separate software process in the Junos OS and is not in the packet-forwarding path. Family MPLS You must configure the core interfaces used for MPLS traffic to belong to family mpls. NOTE: You can enable family mpls on either individual interfaces or aggregated Ethernet interfaces. You cannot enable it on tagged VLAN interfaces. Related Documentation • Junos OS MPLS for J-EX Series Switches Overview on page 3057 • Understanding MPLS and Path Protection on J-EX Series Switches on page 3063 • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ • 3062 Junos OS VPNs Configuration Guide at http://www.juniper.net/techpubs/software/junos/ Chapter 120: MPLS—Overview Understanding MPLS and Path Protection on J-EX Series Switches Junos OS MPLS for J-EX Series Switches provides path protection to protect your MPLS network from label switched path (LSP) failures. By default, an LSP routes itself hop-by-hop from the ingress provider edge switch through the provider switches toward the egress provider edge switch. The LSP generally follows the shortest path as dictated by the local routing table, usually taking the same path as destination-based, best-effort traffic. These paths are “soft” in nature because they automatically reroute themselves whenever a change occurs in a routing table or in the status of a node or link. Typically, when an LSP fails, the switch immediately upstream from the failure signals the outage to the ingress provider edge switch. The ingress provider edge switch calculates a new path to the egress provider edge switch, establishes the new LSP, and then directs traffic from the failed path to the new path. This rerouting process can be time-consuming and prone to failure. For example, the outage signals to the ingress switch might get lost or the new path might take too long to come up, resulting in significant packet drops. You can configure path protection by configuring primary and secondary paths on the ingress switch. If the primary path fails, the ingress switch immediately reroutes traffic from the failed path to the standby path, eliminating the need for the ingress switch to calculate a new route and signal a new path. For information about configuring standby LSPs, see “Configuring Path Protection in an MPLS Network (CLI Procedure)” on page 3097. Related Documentation • Junos OS MPLS for J-EX Series Switches Overview on page 3057 • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 3063 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Understanding Using CoS with MPLS Networks on J-EX Series Switches You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. J-EX Series Switches support Differentiated Service Code Point (DSCP) or IP precedence and IEEE 802.1p CoS classifiers on the customer-edge interfaces of the ingress provider edge (PE) switch. DSCP or IP precedence classifiers are used for Layer 3 packets. IEEE 802.1p is used for Layer 2 packets. When a packet enters a customer-edge interface of the ingress PE switch, the switch associates the packet with a particular CoS servicing level prior to putting the packet onto the label-switched path (LSP). The switches within the LSP utilize the CoS value set at the ingress PE switch. The CoS value that was embedded in the DSCP, IP precedence, or IEEE 802.1 p classifier is translated and encoded in the MPLS header by means of the EXP or experimental bits. J-EX Series switches enable a default EXP classifier and a default EXP rewrite rule. You can configure a custom EXP classifier and a custom EXP rewrite rule if you prefer. However, the switch supports only one type of EXP classifier (default or custom) and only one EXP rewrite rule (default or custom). You do not bind the EXP classifier or the EXP rewrite rule to individual interfaces. The switch automatically and implicitly applies the default or the custom EXP classifier and the default or the custom EXP rewrite rule to the appropriate MPLS-enabled interfaces. Because rewrite rules affect only egress interfaces, the switch applies the EXP rewrite rule only to those MPLS interfaces that are transmitting MPLS packets (not to the MPLS interfaces that are receiving the packets). This topic includes: • Guidelines for Using CoS Classifiers on CCCs on page 3064 • Using CoS Classifiers with IP over MPLS on page 3065 • Default Classifiers and Default Rewrite Rules on page 3065 • EXP Rewrite Rules on page 3065 • Policer on page 3066 • Schedulers on page 3066 Guidelines for Using CoS Classifiers on CCCs When you are configuring CoS for MPLS over circuit cross-connect (CCC), there are some additional guidelines, as follows: 3064 • You must explicitly bind a CoS classifier to the CCC interface on the ingress PE switch. • You cannot use more than one type of DSCP/IP precedence and not more than one type of IEEE 802.1p classifier on the CCC interfaces. Thus, if you configure one CCC interface to use DSCP1, you cannot configure another CCC interface to use DSCP2. Likewise, if you configure one CCC interface to use IEEE1, you cannot configure another Chapter 120: MPLS—Overview CCC interface on the same switch to use IEEE2. All the CCC interfaces on the switch must use the same DSCP classifier and the same type of IEEE 802.1p classifier. • You cannot configure one CCC interface as DSCP and another CCC interface as IP precedence, because these classifier types overlap. • You can configure one CCC interface as DSCP and another CCC interface as IEEE 802.1p. • You can configure one CCC interface as both DSCP and IEEE 802.1p. If you configure a CCC interface with both these classifiers, the DSCP classifier is used for routing Layer 3 packets and the IEEE 802.1p classifier is used for routing Layer 2 packets. NOTE: You can define multiple types of DSCP, IP precedence, and IEEE 802.1p on the switch and use the different classifier types for the non-CCC interfaces on the switch. Using CoS Classifiers with IP over MPLS When you are configuring CoS for IP over MPLS, the customer-edge interface uses the CoS configuration that has been set up for the switch as the default. You do not have to bind a classifier to the customer-edge interface in this case. There are no restrictions regarding using multiple types of DSCP, IP precedence, and IEEE 802.1p on the same switch. • You can modify the CoS classifier for a particular interface, but it is not required. • You can configure one interface as DSCP1 and another as DSCP2 and another and IP precedence, and so forth. Default Classifiers and Default Rewrite Rules The default classifiers support only two forwarding classes, best-effort and network-control, and use only two queues, 0 and 7. However, J-EX Series switches support up to sixteen forwarding classes and eight queues. To use the additional forwarding classes and queues, create a custom classifier. To modify the code point and loss priority for a specific forwarding class, configure a rewrite rule on the switch. The default rewrite rule for EXP is enabled in the default configuration. However, the default rewrite rules for the other classifiers are not enabled in the default configuration. You can display the default classifier mappings and default rewrite mappings by entering the show class-of-service command on the switch. EXP Rewrite Rules When traffic passes from the customer-edge interface to an MPLS interface, the DSCP, IP precedence, or IEEE 802.1p CoS classifier is translated into the EXP bits within the MPLS header. You cannot disable the default EXP rewrite rule, but you can configure your own custom EXP classifier and a custom EXP rewrite rule. You cannot bind the EXP classifier to individual MPLS interfaces; the switch applies it globally to all the MPLS-enabled interfaces on the switch. 3065 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Only one EXP rewrite rule (either default or custom) is supported on a switch. The switch applies it to all the MPLS-enabled egress interfaces. Policer Policing helps to ensure that the amount of traffic forwarded through an LSP never exceeds the requested bandwidth allocation. During periods of congestion (when the total rate of queuing packets exceeds the rate of transmission), any new packets being sent to an interface can be dropped because there is no place to store them. You should configure a policer on the ingress PE switch: • If you are using MPLS with CCC, you bind the policer to the LSP. You cannot bind a policer to a CCC interface. • If you are using IP over MPLS, you bind the policer to the inet-family customer-edge interface. You cannot bind a policer to the LSP when you are using IP over MPLS. Schedulers The schedulers for using CoS with MPLS are the same as for the other CoS configurations on J-EX Series switches. Default schedulers are provided for best-effort and network-control forwarding classes. If you are using assured-forwarding, expedited-forwarding, or other custom forwarding classes, we recommend that you configure a scheduler to support that forwarding class. See “Understanding CoS Schedulers” on page 2873. Related Documentation 3066 • Junos OS MPLS for J-EX Series Switches Overview on page 3057 • Understanding CoS Classifiers on page 2867 • Understanding CoS Schedulers on page 2873 • Example: Configuring CoS on J-EX Series Switches on page 2883 • Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) on page 2932 • Configuring Rewrite Rules for EXP Classifiers on MPLS Networks (CLI Procedure) • Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) on page 3106 • Defining CoS Rewrite Rules (CLI Procedure) on page 2925 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 Chapter 120: MPLS—Overview Understanding MPLS Label Operations on J-EX Series Switches In the traditional packet-forwarding paradigm, as a packet travels from one switch to the next, an independent forwarding decision is made at each hop. The IP network header is analyzed and the next hop is chosen based on this analysis and on the information in the routing table. In an MPLS environment, the analysis of the packet header is made only once, when a packet enters the MPLS tunnel (that is, the path used for MPLS traffic). When an IP packet enters a label-switched path (LSP), the ingress provider edge (PE) switch examines the packet and assigns it a label based on its destination, placing the label in the packet’s header. The label transforms the packet from one that is forwarded based on its IP routing information to one that is forwarded based on information associated with the label. The packet is then forwarded to the next provider switch in the LSP. This switch and all subsequent switches in the LSP do not examine any of the IP routing information in the labeled packet. Rather, they use the label to look up information in their label forwarding table. They then replace the old label with a new label and forward the packet to the next switch in the path. When the packet reaches the egress PE switch, the label is removed, and the packet again becomes a native IP packet and is again forwarded based on its IP routing information. • MPLS Label Switched Paths and MPLS Labels on J-EX Series Switches on page 3067 • Reserved Labels on page 3068 • MPLS Label Operations on J-EX Series Switches on page 3068 • Ultimate and Penultimate Hop Popping on page 3069 MPLS Label Switched Paths and MPLS Labels on J-EX Series Switches When a packet enters the MPLS network, it is assigned to an LSP. Each LSP is identified by a label, which is a short (20-bit), fixed-length value at the front of the packet. Labels are used as lookup indexes for the label forwarding table. For each label, this table stores forwarding information. Because no additional parsing or lookup is done on the encapsulated packet, MPLS supports the transmission of any other protocols within the packet payload. NOTE: MPLS for J-EX Series switches supports only single-label packets. Figure 81 on page 3068 shows the encoding of a single label. The encoding appears after data link layer headers, but before any network layer header. 3067 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Figure 81: Label Encoding Reserved Labels Labels range from 0 through 1,048,575. Labels 0 through 999,999 are for internal use. Some of the reserved labels (in the 0 through 15 range) have well-defined meanings. The following reserved labels are used by J-EX Series switches: • 0, IPv4 Explicit Null label—This value is legal only when it is the sole label entry (no label stacking). It indicates that the label must be popped on receipt. Forwarding continues based on the IP version 4 (IPv4) packet. • 1, Router Alert label—When a packet is received with a top label value of 1, it is delivered to the local software module for processing. • 2, IPv6 Explicit Null label—This value is legal only when it is the sole label entry (no label stacking). It indicates that the label must be popped on receipt. • 3, Implicit Null label—This label is used in the control protocol (RSVP) only to request label popping by the downstream switch. It never actually appears in the encapsulation. Labels with a value of 3 must not be used in the data packet as real labels. No payload type (IPv4 or IPv6) is implied with this label. MPLS Label Operations on J-EX Series Switches J-EX Series switches support the following label operations: • Push • Pop • Swap The push operation affixes a new label to the top of the IP packet. For IPv4 packets, the new label is the first label. The time to live (TTL) field value in the packet header is derived from the IP packet header. The push operation cannot be applied to a packet that already has an MPLS label. 3068 Chapter 120: MPLS—Overview The pop operation removes a label from the beginning of the packet. Once the label is removed, the TTL is copied from the label into the IP packet header, and the underlying IP packet is forwarded as a native IP packet The swap operation removes an existing MPLS label from an IP packet and replaces it with a new MPLS label, based on the following: • Incoming interface • Label • Label forwarding table Figure 82 on page 3069 shows an IP packet without a label arriving on the customer-edge interface (ge-0/0/1) of the ingress PE switch. The ingress PE switch examines the packet and identifies that packet’s destination is the egress PE switch. The ingress PE switch applies label 100 to the packet and sends the MPLS packet to its outgoing MPLS core interface (ge-0/0/5). The MPLS packet is transmitted on the MPLS tunnel through the provider switch, where it arrives at interface ge-0/0/5 with label 100. The provider switch swaps label 100 to label 200 and forwards the MPLS packet through its core interface (ge-0/0/7) to the next hop on the tunnel, which is the egress PE switch. The egress PE switch receives the MPLS packet through its core interface (ge-0/0/7), removes the MPLS label and sends the IP packet out of its customer-edge interface (ge-0/0/1) to a destination that is beyond the scope of the tunnel. Figure 82: MPLS Label Swapping Figure 82 on page 3069 shows the path of a packet as it passes in one direction from the ingress PE switch to the egress PE switch. However, the MPLS configuration also allows traffic to travel in the reverse direction. Thus, each provider edge switch operates as both an ingress switch and an egress switch. Ultimate and Penultimate Hop Popping J-EX Series switches support ultimate and penultimate hop popping (that is, popping off the MPLS label) as follows: • With circuit cross-connect (CCC), ultimate hop popping (UHP) is enabled by default and label 0 (IPv4 Explicit Null Label) is advertised. With UHP, the egress PE switch is responsible for popping the MPLS label at the termination of the CCC. • With IP and MPLS, penultimate hop popping (PHP) is enabled by default. With PHP, the penultimate provider switch is responsible for popping the MPLS label and forwarding the traffic to the egress PE switch. The egress PE switch then performs an IP route lookup and forwards the traffic. This reduces the processing load on the egress PE switch, because it is not responsible for popping off the MPLS label. 3069 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Related Documentation • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP over MPLS (CLI Procedure) on page 3107 • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ • 3070 Junos OS VPNs Configuration Guide at http://www.juniper.net/techpubs/software/junos/ CHAPTER 121 Example of MPLS Configuration • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Example: Combining CoS with MPLS on J-EX Series Switches on page 3085 Example: Configuring MPLS on J-EX Series Switches You can configure MPLS on J-EX Series switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions. To implement MPLS on J-EX Series switches, you must configure two provider edge (PE) switches—an ingress PE switch and an egress PE switch—and at least one provider (transit) switch. You can configure the customer-edge interfaces on the PE switches of the MPLS network as either circuit cross-connect (CCC) or IP (family inet) interfaces. This example shows how to configure an MPLS tunnel using a CCC. For information on configuring MPLS with an IP interface, see “Configuring MPLS on Provider Edge Switches Using MPLS Over IP (CLI Procedure)” on page 3107. • Requirements on page 3071 • Overview and Topology on page 3072 • Configuring the Local PE Switch on page 3075 • Configuring the Remote PE Switch on page 3078 • Configuring the Provider Switch on page 3080 • Verification on page 3082 Requirements This example uses the following hardware and software components: • Three J-EX Series switches Before you begin configuring MPLS, ensure that you have configured the routing protocol (OSPF or IS-IS) on core interface and the loopback interface on all the switches. This example includes the configuration of OSPF on the switches. 3071 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Overview and Topology This example includes an ingress or local PE switch, an egress or remote PE switch, and one provider switch. It includes CCCs that tie the customer-edge interface of the local PE switch (PE-1) to the customer-edge interface of the remote PE switch (PE-2). It also describes how to configure the core interfaces of the PE switches and the provider switch to support the transmission of the MPLS packets. In this example, the core interfaces that connect the local PE switch and the provider switch are individual interfaces while the core interfaces that connect the remote PE switch and the provider switch are aggregated Ethernet interfaces. NOTE: • Core interfaces cannot be tagged VLAN interfaces. • Core interfaces can be aggregated ethernet interfaces. This example includes a LAG between the provider switch and the remote PE switch because this type of configuration is another option you can implement. For information on configuring LAGs, see “Configuring Aggregated Ethernet Interfaces (CLI Procedure)” on page 922. Figure 83 on page 3072 shows the topology used in this example. Figure 83: Configuring MPLS on J-EX Series Switches Table 406 on page 3073 shows the MPLS configuration components used for the ingress PE switch in this example. 3072 Chapter 121: Example of MPLS Configuration Table 406: Components of the Ingress PE Switch in Topology for MPLS with Interface-Based CCC Property Settings Description Local PE switch hardware J-EX Series switch PE-1 Loopback address lo0 127.1.1.1/32 Identifies PE-1 for interswitch communications. Routing protocol ospf traffic-engineering Indicates that this switch is using OSPF as the routing protocol and that traffic engineering is enabled. MPLS protocol and definition of label-switched path mpls Indicates that this PE switch is using the MPLS protocol with the specified LSP to reach the other PE switch (specified by the loopback address). label-switched-path lsp_to_pe2_ge1 to 127.1.13 The statement must also specify the core interfaces to be used for MPLS traffic. RSVP protocol rsvp Indicates that this switch is using the RSVP protocol. The statement must specify the loopback address and the core interfaces that will be used for the RSVP session. Interface family family inet The logical units of the core interfaces are configured to belong to both family inet and family mpls. family mpls family ccc The logical unit of the customer-edge interface is configured to belong to family ccc. Customer-edge interface ge-0/0/1 Interface that connects this network to devices outside the network. Core interfaces ge-0/0/5.0 and ge-0/0/6.0 with IP addresses 10.1.5.1/24 and 10.1.6.1/24 Interfaces that connect to other switches within the MPLS network. CCC definition connections remote-interface-switch ge-1-to-pe2 Associates the circuit cross-connect (CCC), ge-0/0/1, with the LSPs that have been defined on the local and remote PE switches. interface ge-0/0/1.0 transmit-lsp lsp_to_pe2_ge1 receive-lsp lsp_to_pe1_ge1 3073 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 407 on page 3074 shows the MPLS configuration components used for the egress PE switch in this example. Table 407: Components of the Egress PE Switch in Topology for MPLS with Interface-Based CCC Property Settings Description Remote PE switch hardware J-EX Series switch PE-2 Loopback address lo0 127.1.1.3/32 Identifies PE-2 for interswitch communications. Routing protocol ospf traffic-engineering Indicates that this switch is using OSPF as the routing protocol and that traffic engineering is enabled. MPLS protocol and definition of label-switched path mpls Indicates that this PE switch is using the MPLS protocol with the specified label-switched path (LSP) to reach the other PE switch. label-switched-path lsp_to_pe1_ge1 to 127.1.1.1 The statement must also specify the core interfaces to be used for MPLS traffic. RSVP protocol rsvp Indicates that this switch is using the RSVP protocol. The statement must specify the loopback address and the core interfaces that will be used for the RSVP session. Interface family family inet The logical unit of the core interface is configured to belong to both family inet and family mpls. family mpls family ccc The logical unit of the customer-edge interface is configured to belong to family ccc. Customer-edge interface ge-0/0/1 Interface that connects this network to devices outside the network. Core interface ae0 with IP address 10.1.9.2/24 Aggregated Ethernet interface on PE-2 that connects to aggregated Ethernet interface ae0 of the provider switch and belongs to family mpls. CCC definition connections remote-interface-switch ge-1-to-pe1 Associates the CCC, ge-0/0/1, with the LSPs that have been defined on the local and remote PE switches. interface ge-0/0/1.0 transmit-lsp lsp_to_pe1_ge1; receive-lsp lsp_to_pe2_ge1; 3074 Chapter 121: Example of MPLS Configuration Table 408 on page 3075 shows the MPLS configuration components used for the provider switch in this example. Table 408: Components of the Provider Switch in Topology for MPLS with Interface-Based CCC Property Settings Description Provider switch hardware J-EX Series switch Transit switch within the MPLS network configuration. Loopback address lo0 127.1.1.2/32 Identifies provider switch for interswitch communications. Routing protocol ospf traffic-engineering Indicates that this switch is using OSPF as the routing protocol and that traffic engineering is enabled. MPLS protocol mpls Indicates that this switch is using the MPLS protocol. The statement must specify the core interfaces that will be used for MPLS traffic. RSVP protocol rsvp Indicates that this switch is using the RSVP protocol. The statement must specify the loopback and the core interfaces that will be used for the RSVP session. Interface family family inet The logical units for the loopback interface and core interfaces belong to family inet. family mpls The logical units of the core interfaces are also configured to belong to family mpls. Core interfaces ge-0/0/5.0 and ge-0/0/6.0 with IP addresses 10.1.5.1/24 and 10.1.6.1/24 and ae0 with IP address 10.1.9.1/24 Interfaces that connect the provider switch (P) to PE-1. Aggregated Ethernet interface on P that connects to aggregated Ethernet interface ae0 of PE-2. Configuring the Local PE Switch CLI Quick Configuration To quickly configure the local ingress PE switch, copy the following commands and paste them into the switch terminal window of PE-1: [edit] set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/5.0 set protocols ospf area 0.0.0.0 interface ge-0/0/6.0 set protocols mpls label-switched-path lsp_to_pe2_ge1 to 127.1.1.3 3075 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS set protocols mpls interface ge-0/0/5.0 set protocols mpls interface ge-0/0/6.0 set protocols rsvp interface lo0.0 set protocols rsvp interface ge-0/0/5.0 set protocols rsvp interface ge-0/0/6.0 set interfaces lo0 unit 0 family inet address 127.1.1.1/32 set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 set interfaces ge-0/0/5 unit 0 family mpls set interfaces ge-0/0/6 unit 0 family mpls set interfaces ge-0/0/1 unit 0 family ccc set protocols connections remote-interface-switch ge-1–to-pe2 interface ge-0/0/1.0 set protocols connections remote-interface-switch ge-1–to-pe2 transmit-lsp lsp_to_pe2_ge1 set protocols connections remote-interface-switch ge-1–to-pe2 receive-lsp lsp_to_pe1_ge1 Step-by-Step Procedure To configure the local ingress PE switch: 1. Configure OSPF with traffic engineering enabled: [edit protocols] user@switchPE-1# set ospf traffic-engineering 2. Configure OSPF on the loopback address and core interfaces: [edit protocols] user@switchPE-1# set ospf area 0.0.0.0 interface lo0.0 user@switchPE-1# set ospf area 0.0.0.0 interface ge-0/0/5.0 user@switchPE-1# set ospf area 0.0.0.0 interface ge-0/0/6.0 3. Configure MPLS on the local switch with a label-switched path to the remote egress PE switch: [edit protocols] user@switchPE-1# set mpls label-switched-path lsp_to_pe2_ge1 to 127.1.1.3 4. Configure MPLS on the core interfaces: [edit protocols] user@switchPE-1# set mpls interface ge-0/0/5.0 user@switchPE-1# set mpls interface ge-0/0/6.0 5. Configure RSVP on the loopback interface and core interfaces: [edit protocols] user@switchPE-1# set rsvp interface lo0.0 user@switchPE-1# set rsvp interface ge-0/0/5.0 user@switchPE-1# set rsvp interface ge-0/0/6.0 6. Configure IP addresses for the loopback interface and core interfaces: [edit] user@switchPE-1# set interfaces lo0 unit 0 family inet address 127.1.1.1/32 user@switchPE-1# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 user@switchPE-1# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 7. Configure family mpls on the logical unit of the core interface addresses: [edit] user@switchPE-1# set interfaces ge-0/0/5 unit 0 family mpls user@switchPE-1# set interfaces ge-0/0/6 unit 0 family mpls 8. 3076 Configure the logical unit of the customer-edge interface as a CCC: Chapter 121: Example of MPLS Configuration [edit interfaces ge-0/0/1 unit 0] user@PE-1# set family ccc 9. Configure the interface-based CCC from PE-1 to PE-2: NOTE: You can also configure a tagged VLAN interface as a CCC. See Configuring MPLS on Provider Edge Switches (CLI Procedure). [edit protocols] user@PE-1# set connections remote-interface-switch ge-1–to-pe2 interface ge-0/0/1.0 user@PE-1# set connections remote-interface-switch ge-1–to-pe2 transmit-lsp lsp_to_pe2_ge1 user@PE-1# set connections remote-interface-switch ge-1–to-pe2 receive-lsp lsp_to_pe1_ge1 Results Display the results of the configuration: user@switchPE-1> show configuration interfaces { ge-0/0/1 { unit 0 { family ccc; } } ge-0/0/5 { unit 0 { family inet { address 10.1.5.1/24; } family mpls; } } ge-0/0/6 { unit 0 { family inet { address 10.1.6.1/24; } family mpls; } } lo0 { unit 0 { family inet { address 127.1.1.1/32; } } } protocols { rsvp { interface lo0.0; interface ge-0/0/5.0; interface ge-0/0/6.0; } mpls { 3077 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS label-switched-path lsp_to_pe2_ge1 { to 127.1.1.3; } interface ge-0/0/5.0; interface ge-0/0/6.0; } ospf { traffic-engineering; area 0.0.0.0 { interface lo0.0; interface ge-0/0/5.0; interface ge-0/0/6.0; } } connections { remote-interface-switch ge-1-to-pe2 { interface ge-0/0/1.0; transmit-lsp lsp_to_pe2_ge1; receive-lsp lsp_to_pe1_ge1; } } Configuring the Remote PE Switch CLI Quick Configuration To quickly configure the remote PE switch, copy the following commands and paste them into the switch terminal window of PE-2: [edit] set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ospf area 0.0.0.0 interface ae0 set protocols mpls label-switched-path lsp_to_pe1_ge1 to 127.1.1.1 set protocols mpls interface ae0 set protocols rsvp interface lo0.0 set protocols rsvp interface ae0 set interfaces lo0 unit 0 family inet address 127.1.1.3/32 set interfaces ae0 unit 0 family inet address 10.1.9.2/24 set interfaces ae0 unit 0 family mpls set interfaces ge-0/0/1 unit 0 family ccc set protocols connections remote-interface-switch ge-1-to-pe1 interface ge-0/0/1.0 set protocols connections remote-interface-switch ge-1-to-pe1 transmit-lsp lsp_to_pe1_ge1 set protocols connections remote-interface-switch ge-1-to-pe1 receive-lsp lsp_to_pe2_ge1 Step-by-Step Procedure To configure the remote PE switch (PE-2): 1. Configure OSPF with traffic engineering enabled: [edit protocols] user@switchPE-2# set ospf traffic-engineering 2. Configure OSPF on the loopback interface and core interface: [edit protocols] user@switchPE-2# set ospf area 0.0.0.0 interface lo0.0 user@switchPE-2# set ospf area 0.0.0.0 interface ae0 3. Configure MPLS on the switch with a label-switched path to the other PE switch: [edit protocols] 3078 Chapter 121: Example of MPLS Configuration user@switchPE-2# set mpls label-switched-path lsp_to_pe1_ge1 to 127.1.1.1 4. Configure MPLS on the core interface: [edit protocols] user@switchPE-2# set mpls interface ae0 5. Configure RSVP on the loopback interface and core interface: [edit protocols] ser@switchPE-2# set rsvp interface lo0.0 user@switchPE-2# set rsvp interface ae0 6. Configure IP addresses for the loopback interface and core interface: [edit] user@switchPE-2# set interfaces lo0 unit 0 family inet address 127.1.1.3/32 user@switchPE-2# set interfaces ae0 unit 0 family inet address 10.1.9.2/24 7. Configure family mpls on the logical unit of the core interface: [edit] user@switchPE-2# set interfaces ae0 unit 0 family mpls 8. Configure the logical unit of the customer-edge interface as a CCC: [edit interfaces ge-0/0/1 unit 0] user@PE-2# set family ccc 9. Configure the interface-based CCC from PE-2 to PE-1: [edit protocols] user@PE-2# set connections remote-interface-switch ge-1–to-pe2 interface ge-0/0/1.0 user@PE-2# set connections remote-interface-switch ge-1–to-pe2 transmit-lsp lsp_to_pe1_ge1 user@PE-2# set connections remote-interface-switch ge-1–to-pe2 receive-lsp lsp_to_pe2_ge1 Results Display the results of the configuration: user@switchPE-2> show configuration interfaces { ge-0/0/1 { unit 0 { family ccc; } } ae0 { unit 0 { family inet { address 10.1.9.2/24; } family mpls; } } lo0 { unit 0 { family inet { address 127.1.1.3/32; } 3079 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } } } protocols { rsvp { interface lo0.0; interface ae0.0; } mpls { label-switched-path lsp_to_pe1_ge1 { to 127.1.1.1; } interface ae0.0; } ospf { traffic-engineering; area 0.0.0.0 { interface ae0.0; } } connections { remote-interface-switch ge-1-to-pe1 { interface ge-0/0/1.0; transmit-lsp lsp_to_pe1_ge1; receive-lsp lsp_to_pe2_ge1; } } } Configuring the Provider Switch CLI Quick Configuration To quickly configure the provider switch, copy the following commands and paste them into the switch terminal window: [edit] set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/5.0 set protocols ospf area 0.0.0.0 interface ge-0/0/6.0 set protocols ospf area 0.0.0.0 interface ae0 set protocols mpls interface ge-0/0/5.0 set protocols mpls interface ge-0/0/6.0 set protocols mpls interface ae0 set protocols rsvp interface lo0.0 set protocols rsvp interface ge-0/0/5.0 set protocols rsvp interface ge-0/0/6.0 set protocols rsvp interface ae0 set interfaces lo0 unit 0 family inet address 127.1.1.2/32 set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 set interfaces ae0 unit 0 family inet address 10.1.9.1/24 set interfaces ge-0/0/5 unit 0 family mpls set interfaces ge-0/0/6 unit 0 family mpls set interfaces ae0 unit 0 family mpls 3080 Chapter 121: Example of MPLS Configuration Step-by-Step Procedure To configure the provider switch: 1. Configure OSPF with traffic engineering enabled: [edit protocols] user@switchP# set ospf traffic-engineering 2. Configure OSPF on the loopback interface and core interfaces: [edit protocols] user@switchP# set ospf area interface lo0.0 user@switchP# set ospf area interface ge-0/0/5 user@switchP# set ospf area interface ge-0/0/6 user@switchP# set ospf area interface ae0 3. Configure MPLS on the core interfaces on the switch: [edit protocols] user@switchP# set mpls interface ge-0/0/5 user@switchP# set mpls interface ge-0/0/6 user@switchP# set mpls interface ae0 4. Configure RSVP on the loopback interface and core interfaces: [edit protocols] user@switchP# set rsvp interface lo0.0 user@switchP# set rsvp interface ge-0/0/5 user@switchP# set rsvp interface ge-0/0/6 user@switchP# set rsvp interface ae0 5. Configure IP addresses for the loopback and core interfaces: [edit] user@switchP# set interfaces lo0 unit 0 family inet address 127.1.1.2/32 user@switchP# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 user@switchP# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 user@switchP# set interfaces ae0 unit 0 family inet address 10.1.9.1/24 6. Configure family mpls on the logical unit of the core interface addresses: [edit] user@switchP# set interfaces ge-0/0/5 unit 0 family mpls user@switchP# set interfaces ge-0/0/6 unit 0 family mpls user@switchP# set interfaces ae0 unit 0 family mpls Results Display the results of the configuration: user@switchP> show configuration interfaces { ge-0/0/5 { unit 0 { family inet { address 10.1.5.1/24; } family mpls; } } ge-0/0/6 { unit 0 { family inet { 3081 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS address 10.1.6.1/24; } family mpls; } } } ae0 { unit 0 { family inet { address 10.1.9.1/24; } family mpls; } } lo0 { unit 0 { family inet { address 127.1.1.2/32; } } } protocols { rsvp { interface lo0.0; interface ge-0/0/5.0; interface ge-0/0/6.0; interface ae0.0; } mpls { interface ge-0/0/5.0; interface ge-0/0/6.0; interface ae0.0; } ospf { traffic-engineering; area 0.0.0.0 { interface lo0.0; interface ge-0/0/5.0; interface ge-0/0/6.0; interface ae0.0; } } Verification To confirm that the configuration is working properly, perform these tasks: 3082 • Verifying the Physical Layer on the Switches on page 3083 • Verifying the Routing Protocol on page 3083 • Verifying the Core Interfaces Being Used for the MPLS Traffic on page 3083 • Verifying RSVP on page 3084 • Verifying the Assignment of Interfaces for MPLS Label Operations on page 3084 • Verifying the Status of the CCC on page 3084 Chapter 121: Example of MPLS Configuration Verifying the Physical Layer on the Switches Purpose Action Verify that the interfaces are up. Perform this verification task on each of the switches. interface-name terse user@switchPE-1> Interface ge-0/0/0 ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 Admin up up up up up up up Link up up up up up up up Proto up up inet Local Remote ccc eth-switch eth-switch eth-switch inet 10.1.5.1/24 mpls ge-0/0/6.0 10.1.6.1/24 mpls Meaning The show interfaces terse command displays status information about the Gigabit Ethernet interfaces on the switch. This output verifies that the interfaces are up. The output for the protocol family (Proto column) shows that interface ge-0/0/1.0 is configured as a circuit cross-connect. The output for the protocol family of the core interfaces (ge-0/0/5.0 and ge-0/0/6.0), shows that these interfaces are configured as both inet and mpls. The Local column for the core interfaces shows the IP address configured for these interfaces. Verifying the Routing Protocol Purpose Action Verify the state of the configured routing protocol. Perform this verification task on each of the switches. The state must be Full. user@switchPE-1> show ospf neighbor Address 127.1.1.2 Meaning Interface ge—0/0/5 State Full ID 10.10.10.10 Pri 128 Dead 39 The show ospf neighbor command displays the status of the routing protocol. This output shows that the state is Full, meaning that the routing protocol is operating correctly—that is, hello packets are being exchanged between directly connected neighbors. Verifying the Core Interfaces Being Used for the MPLS Traffic Purpose Action Verify that the state of the MPLS interface is Up. Perform this verification task on each of the switches. user@switchPE-1> show mpls interface Interface ge—0/0/5 ge—0/0/6 State Up Up Administrative groups 3083 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Meaning The show mpls interface command displays the status of the core interfaces that have been configured to belong to family mpls. This output shows that the interface configured to belong to family mpls is Up. Verifying RSVP Purpose Action Verify the state of the RSVP session. Perform this verification task on each of the switches. user@switchPE-1> show rsvp session Ingress RSVP: 1 sessions To From State 127.1.13 127.1.1.1 Up Total 1 displayed, Up 1, Down 0 Egress RSVP: 1 sessions To From State 127.1.1.1 127.1.1.3 Up lsp_to_pe1_ge1 Total 1 displayed, Up 1, Down 0 Rt Style Labelin Labelout LSPname 0 1 FF 300064 lsp_to_pe2_ge1 Rt Style Labelin Labelout LSPname 0 1 FF 299968 - Transit RSVP: 0 sessions Total 0 displayed, Up 0, Down 0 Meaning This output confirms that the RSVP sessions are Up. Verifying the Assignment of Interfaces for MPLS Label Operations Purpose Verify which interface is being used as the beginning of the CCC and which interface is being used to push the MPLS packet to the next hop. Perform this task only on the PE switches. Action user@switchPE-1> show route forwarding-table family mpls MPLS: Destination Type RtRef Next hop Type Index NhRef Netif default perm 0 dscd 50 1 0 user 0 recv 49 3 1 user 0 recv 49 3 2 user 0 recv 49 3 299776 user 0 Pop 541 2 ge-0/0/1.0 ge-0/0/1.0 (CCC) user 0 2.0.0.1 Push 299792 540 2 ge-0/0/5.0 Meaning This output shows that the CCC has been set up on interface ge-0/0/1.0. The switch receives ingress traffic on ge-0/0/1.0 and pushes label 299792 onto the packet, which goes out through interface ge-0/0/5.0. The output also shows when the switch receives an MPLS packet with label 29976, it pops the label and sends the packet out through interface ge-0/0/1.0 After you have checked the local PE switch, run the same command on the remote PE switch. Verifying the Status of the CCC Purpose 3084 Verify the status of the CCC. Perform this task only on the PE switches. Chapter 121: Example of MPLS Configuration Action user@switchPE-1> show connections CCC and TCC connections [Link Monitoring On] Legend for status (St) Legend for connection types UN -- uninitialized if-sw: interface switching NP -- not present rmt-if: remote interface switching WE -- wrong encapsulation lsp-sw: LSP switching DS -- disabled tx-p2mp-sw: transmit P2MP switching Dn -- down rx-p2mp-sw: receive P2MP switching -> -- only outbound conn is up <- -- only inbound conn is up Legend for circuit types Up -- operational intf -- interface RmtDn -- remote CCC down tlsp -- transmit LSP Restart -- restarting rlsp -- receive LSP Connection/Circuit ge1-to-pe2 ge-0/0/1.0 lsp_to_pe1_ge1 lsp_to_pe2_ge1 Meaning Related Documentation Type rmt-if intf tlsp rlsp St Up Up Up Up Time last up # Up trans Feb 17 05:00:09 1 The show connections command displays the status of the CCC connections. This output verifies that the CCC interface and its associated transmit and receive LSPs are Up. After you have checked the local PE switch, run the same command on the remote PE switch. • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Junos OS MPLS for J-EX Series Switches Overview on page 3057 • For information on the interface statement for OSPF, see the Junos OS Routing Protocols Configuration Guide at http://www.juniper.net/techpubs/software/junos/. Example: Combining CoS with MPLS on J-EX Series Switches You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. The CoS value is included within the MPLS label, which is passed through the network, enabling end-to-end CoS across the network. MPLS services are often used to ensure better performance for low-latency applications such as VoIP and other business-critical functions. These applications place specific demands on a network for successful transmission. CoS gives you the ability to control the mix of bandwidth, delay, jitter, and packet loss while taking advantage of the MPLS labeling mechanism. This example shows how to configure CoS on an MPLS network that is using a unidirectional circuit cross-connect (CCC) from the ingress provider edge (PE) switch to the egress PE switch. for the customer-edge interface of the ingress provider edge (PE) switch. It describes adding the configuration of CoS components to the ingress PE switch, 3085 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS the egress PE switch, and the core provider switches of the existing MPLS network. Because of the unidirectional configuration, the DSCP classifier needs to be configured only on the ingress PE switch. • Requirements on page 3086 • Overview and Topology on page 3086 • Configuring the Local PE Switch on page 3088 • Configuring the Remote PE Switch on page 3090 • Configuring the Provider Switch on page 3091 • Verification on page 3092 Requirements This example uses the following hardware and software components: • Three J-EX Series switches Before you configure CoS with MPLS, be sure you have: Configured an MPLS network with two PE switches and one provider switch. See “Example: Configuring MPLS on J-EX Series Switches” on page 3071. This example assumes that an MPLS network has been configured using a cross circuit-connect (CCC). Overview and Topology This example describes adding custom classifiers and custom rewrite rules to switches in an MPLS network that is using MPLS over CCC. It is a unidirectional configuration. Therefore, you need to configure custom classifiers and custom rewrite rules as follows: • On the ingress PE switch: custom DSCP classifier and custom EXP rewrite rule • On the egress PE switch: custom EXP classifier • On the provider switch: customer EXP classifier and custom EXP rewrite rule NOTE: You can also configure schedulers and shapers as needed. If you are using assured-forwarding, expedited-forwarding, or other custom forwarding classes, we recommend that you configure a scheduler to support that forwarding class. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. The example creates a custom DSCP classifier (dscp1) on the ingress PE switch and binds this classifier to the CCC interface. It includes configuration of a policer on the ingress PE switch. The policer is applied as a filter on the label-switched path (LSP) lsp_to_pe2_ge1(created in “Example: Configuring MPLS on J-EX Series Switches” on page 3071) to ensure that the amount of traffic forwarded through the LSP never exceeds the requested bandwidth allocation. 3086 Chapter 121: Example of MPLS Configuration This example creates a custom EXP rewrite rule (exp1) on the ingress PE switch, specifying a loss-priority and code point to be used for the expedited-forwarding class as the packet travels through the LSP. The switch applies this custom rewrite rule on the core interfaces ge-0/0/5.0 and ge-0/0/6.0, which are the egress interfaces for this switch. Table 409 on page 3087 shows the CoS configuration components added to the ingress PE switch. Table 409: CoS Configuration Components on the Ingress PE Switch Property Settings Description Local PE switch hardware J-EX Series switch PE-1 Policing filter configured and applied to the LSP. policing filter mypolicer Name of the rate-limiting policer. filter myfilter Name of the filter, which refers to the policer Custom DSCP classifier dscp1 Specifies the name of the custom DSCP classifier Custom EXP rewrite rule e1 Name of the custom EXP rewrite rule. Customer-edge interface ge-0/0/1.0 Interface that receives packets from devices outside the network. The custom DSCP classifier must be specified on this CCC interface. Core interfaces ge-0/0/5.0 and ge-0/0/6.0 Interfaces that transmit MPLS packets to other switches within the MPLS network. The EXP rewrite rule is applied implicitly to these interfaces. Table 410 on page 3087 shows the CoS configuration components added to the egress PE switch in this example. Table 410: CoS Configuration Components of the Egress PE Switch Property Settings Description Remote provider edge switch hardware J-EX Series switch PE-2 Custom EXP classifier exp1 Name of custom EXP classifier Customer-edge interface ge-0/0/1.0 Interface that transmits packets from this network to devices outside the network. No CoS classifier is specified for this interface. A scheduler can be specified. 3087 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 410: CoS Configuration Components of the Egress PE Switch (continued) Property Settings Description Core interfaces ge-0/0/7.0 and ge-0/0/8.0 Core interfaces on PE-2 that receive MPLS packets from the provider switch. The EXP classifier is enabled by default on the switch and applied implicitly to these interfaces. Table 411 on page 3088 shows the MPLS configuration components used for the provider switch in this example. Table 411: CoS Configuration Components of the Provider Switch Property Settings Description Provider switch hardware J-EX Series switch Transit switch within the MPLS network configuration. Custom EXP classifier exp1 Name of the custom EXP classifier. Custom EXP rewrite rule e1 Name of the custom EXP rewrite rule. Core interfaces receiving packets from other MPLS switches. ge-0/0/5.0 and ge-0/0/6.0 Interfaces that connect the provider switch to the ingress PE switch (PE-1). The EXP classifier is enabled by default on the switch and applied implicitly to these interfaces. Core interfaces transmitting packets to other switches within the MPLS network. ge-0/0/7.0 and ge-0/0/8.0 Interfaces that transmit packets to the egress PE (PE-2). The EXP rewrite rule is applied implicitly on these interfaces. Schedulers can also be specified and will be applied to these interfaces. Configuring the Local PE Switch CLI Quick Configuration To quickly configure a custom DSCP classifier, custom EXP rewrite rule, and a policer on the local PE switch, copy the following commands and paste them into the switch terminal window of PE-1: [edit] set class-of-service classifiers dscp dscp1 import default set class-of-service classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 set class-of-service rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1 set firewall policer mypolicer if-exceeding bandwidth-limit 500m set firewall policer mypolicer if-exceeding burst-size-limit 33553920 set firewall policer mypolicer then discard set firewall family any filter myfilter term t1 then policer mypolicer set protocols mpls label-switched-path lsp_to_pe2_ge1 to 127.1.1.3 policing filter myfilter 3088 Chapter 121: Example of MPLS Configuration Step-by-Step Procedure To configure a custom DSCP classifier, custom EXP rewrite rule, and a policer on the ingress PE switch: 1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating: [edit class-of-service] user@switch# set classifiers dscp dscp1 import default 2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch# set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 4. Bind the DSCP classifier to the CCC interface: [edit ] user@switch# set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1 5. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the LSP: [edit firewall] set policer mypolicer if-exceeding bandwidth-limit 500m 6. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer: [edit firewall policer] set mypolicer if-exceeding burst-size-limit 33553920 7. Discard traffic that exceeds the rate limits for this policer: [edit firewall policer] set mypolicer then discard 8. To reference the policer, configure a filter term that includes the policer action: [edit firewall] user@switch# set family any filter myfilter term t1 then policer mypolicer 9. Apply the filter to the LSP: [edit protocols mpls] set label-switched-path lsp_to_pe2_ge1 policing filter myfilter Results Display the results of the configuration: [edit] user@switch# show class-of-service { classifiers { dscp dscp1 { 3089 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS import default; forwarding-class expedited-forwarding { loss-priority low code-points 000111; } } } interfaces { ge-0/0/1 { unit 0 { classifiers { dscp dscp1; } } } } rewrite-rules { exp e1 { forwarding-class expedited-forwarding { loss-priority low code-point 111; } } } } firewall { family any { filter myfilter { term t1 { then policer mypolicer; } } } policer mypolicer { if-exceeding { bandwidth-limit 500m; burst-size-limit 33553920; } then discard; } } Configuring the Remote PE Switch CLI Quick Configuration To quickly configure a custom EXP classifier on the remote PE switch, copy the following commands and paste them into the switch terminal window of PE-2: [edit] set class-of-service classifiers exp exp1 import default set class-of-service classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 Step-by-Step Procedure To configure a custom EXP classifier on the egress PE switch: 1. Import the default EXP classifier classes to the custom EXP classifier that you are creating: [edit class-of-service] user@switch# set classifiers exp exp1 import default 3090 Chapter 121: Example of MPLS Configuration 2. Add the expedited-forwarding class to this custom EXP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch# set classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 Results Display the results of the configuration: [edit] user@switch# show class-of-service { classifiers { exp exp1 { import default; forwarding-class expedited-forwarding { loss-priority low code-points 010; } } Configuring the Provider Switch CLI Quick Configuration To quickly configure a custom EXP classifier and a custom EXP rewrite rule on the provider switch, copy the following commands and paste them into the switch terminal window of the provider switch: [edit] set class-of-service classifiers exp exp1 import default set class-of-service classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 set class-of-service rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 Step-by-Step Procedure To configure a custom EXP classifier and a custom EXP rewrite rule on the provider switch: 1. Import the default EXP classifier classes to the custom EXP classifier that you are creating: [edit class-of-service] user@switch# set classifiers exp exp1 import default 2. Add the expedited-forwarding class to this custom EXP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch# set classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 Results Display the results of the configuration: [edit] 3091 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS user@switch# show class-of-service { classifiers { exp exp1 { import default; forwarding-class expedited-forwarding { loss-priority low code-points 010; } } } rewrite-rules { exp e1 { forwarding-class expedited-forwarding { loss-priority low code-point 111; } } } } Verification To confirm that the configuration is working properly, perform these tasks: • Verifying That the Policer Firewall Filter Is Operational on page 3092 • Verifying That the CoS Classifiers Are Going to the Right Queue on page 3092 • Verifying the CoS Forwarding Table Mapping on page 3095 • Verifying the Rewrite Rules on page 3095 Verifying That the Policer Firewall Filter Is Operational Purpose Action Meaning Verify the operational state of the policer that is configured on the ingress PE switch. user@switch> show firewall Filter: myfilter Policers: Name mypolicer-t1 Packets 0 This output shows that the firewall filter mypolicer has been created. Verifying That the CoS Classifiers Are Going to the Right Queue Purpose Action Verify that the CoS classifiers are going to the right queue. user@switch> show class-of-service forwarding-table classifier Classifier table index: 7, # entries: 64, Table type: DSCP Entry # Code point Forwarding-class # PLP 0 000000 0 0 1 000001 0 0 2 000010 0 0 3 000011 0 0 4 000100 0 0 5 000101 0 0 6 000110 0 0 3092 Chapter 121: Example of MPLS Configuration 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 000111 001000 001001 001010 001011 001100 001101 001110 001111 010000 010001 010010 010011 010100 010101 010110 010111 011000 011001 011010 011011 011100 011101 011110 011111 100000 100001 100010 100011 100100 100101 100110 100111 101000 101001 101010 101011 101100 101101 101110 101111 110000 110001 110010 110011 110100 110101 110110 110111 111000 111001 111010 111011 111100 111101 111110 111111 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Classifier table index: 11, # entries: 8, Table type: IEEE 802.1 Entry # Code point Forwarding-class # PLP 0 000 0 0 3093 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1 2 3 4 5 6 7 001 010 011 100 101 110 111 0 0 0 0 0 3 3 0 0 0 0 0 0 0 Classifier table index: 12, # entries: 8, Table type: IPv4 precedence Entry # Code point Forwarding-class # PLP 0 000 0 0 1 001 0 0 2 010 0 0 3 011 0 0 4 100 0 0 5 101 0 0 6 110 3 0 7 111 3 0 Classifier table index: 16, # entries: 8, Table type: Untrust Entry # Code point Forwarding-class # PLP 0 000 0 0 1 001 0 0 2 010 0 0 3 011 0 0 4 100 0 0 5 101 0 0 6 110 0 0 7 111 0 0 Classifier table index: 9346, # entries: 64, Table type: DSCP Entry # Code point Forwarding-class # PLP 0 000000 0 0 1 000001 0 0 2 000010 0 0 3 000011 0 0 4 000100 0 0 5 000101 0 0 6 000110 0 0 7 000111 1 0 8 001000 0 0 9 001001 0 0 10 001010 0 0 11 001011 0 0 12 001100 0 0 13 001101 0 0 14 001110 0 0 15 001111 0 0 16 010000 0 0 17 010001 0 0 18 010010 0 0 19 010011 0 0 20 010100 0 0 21 010101 0 0 22 010110 0 0 23 010111 0 0 24 011000 0 0 25 011001 0 0 26 011010 0 0 27 011011 0 0 28 011100 0 0 3094 Chapter 121: Example of MPLS Configuration 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Meaning 011101 011110 011111 100000 100001 100010 100011 100100 100101 100110 100111 101000 101001 101010 101011 101100 101101 101110 101111 110000 110001 110010 110011 110100 110101 110110 110111 111000 111001 111010 111011 111100 111101 111110 111111 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This output shows that a new DSCP classifier has been created, index 9346, on the ingress PE switch (PE-1). Verifying the CoS Forwarding Table Mapping Purpose Action For each logical interface, display either the table index of the classifier for a given code point type or the queue number (if it is a fixed classification) in the forwarding table. user@switch>show class-of-service forwarding-table classifier mapping Interface ge-0/0/1.0 Meaning Index 92 Table Index/ Q num 9346 Table type DSCP The results show that the new DSCP classifier, index number 9346, is bound to interface ge-0/0/1.0. Verifying the Rewrite Rules Purpose Display mapping of the queue number and loss priority to code point value for each rewrite rule as it exists in the forwarding table. 3095 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Action user@switch>show class-of-service forwarding-table rewrite-rule Rewrite FC# 0 1 2 3 table index: 31, # entries: 4, Table type: DSCP Low bits State High bits State 000000 Enabled 000000 Enabled 101110 Enabled 101110 Enabled 001010 Enabled 001100 Enabled 110000 Enabled 111000 Enabled Rewrite table index: 34, # entries: 4, Table type: IEEE 802.1 FC# Low bits State High bits State 0 000 Enabled 001 Enabled 1 010 Enabled 011 Enabled 2 100 Enabled 101 Enabled 3 110 Enabled 111 Enabled Rewrite table index: 35, # entries: 4, Table type: IPv4 precedence FC# Low bits State High bits State 0 000 Enabled 000 Enabled 1 101 Enabled 101 Enabled 2 001 Enabled 001 Enabled 3 110 Enabled 111 Enabled Rewrite table index: 9281, # entries: 1, Table type: EXP FC# Low bits State High bits State 1 111 Enabled 000 Disabled Meaning Related Documentation 3096 This output shows that a new EXP classifier with the index number 9281 has been created. • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 • Monitoring CoS Forwarding Classes on page 2936 CHAPTER 122 Configuring MPLS • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI Procedure) on page 3104 • Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) on page 3105 • Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) on page 3106 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 Configuring Path Protection in an MPLS Network (CLI Procedure) The Junos OS implementation of MPLS on J-EX Series switches provides path protection as a mechanism for protecting against label switched path (LSP) failures. Path protection reduces the time required to recalculate a route in case of a failure within the MPLS tunnel. You configure path protection on the ingress provider edge switch in your MPLS network. You do not configure the egress provider edge switch or the provider switches for path protection. You can explicitly specify which provider switches are used for the primary and secondary paths, or you can let the software calculate the paths automatically. Before you configure path protection, be sure you have: • Configured an ingress provider edge switch and an egress provider edge switch. See Configuring MPLS on Provider Edge Switches (CLI Procedure). • Configured at least one provider (transit) switch. See “Configuring MPLS on Provider Switches (CLI Procedure)” on page 3102. • Verified the configuration of your MPLS network. See “Verifying That MPLS Is Working Correctly” on page 3115. 3097 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS To configure path protection, complete the following tasks on the ingress provider edge switch: 1. Configuring the Primary Path on page 3099 2. Configuring the Secondary Path on page 3099 3. Configuring the Revert Timer on page 3100 3098 Chapter 122: Configuring MPLS Configuring the Primary Path The primary statement creates the primary path, which is the LSP’s preferred path. The secondary statement creates an alternative path if the primary path can no longer reach the egress provider edge switch. In the tasks described in this topic, the lsp-name has already been configured on the ingress provider edge switch as lsp_to_240 and the loopback interface address on the remote provider edge switch has already been configured as 127.0.0.8. When the software switches from the primary to the secondary path, it continuously attempts to revert to the primary path, switching back to it when it is again reachable but no sooner than the retry time specified in the revert-timer statement. You can configure zero primary paths or one primary path. If you do not configure a primary path, the first secondary path (if a secondary path has been configured) is selected as the path. If you do not specify any named paths, or if the path that you specify is empty, the software makes all routing decisions necessary for the packets to reach the egress provider edge switch. To configure a primary path: 1. Create the primary path for the LSP: [edit protocols mpls label-switched-path lsp_to_240 to 127.0.0.8] user@switch# set primary primary_path_lsp_to_240 2. Configure an explicit route for the primary path by specifying the IP address of the loopback interface or the switch IP address or hostname of each switch used in the MPLS tunnel. You can specify the link types as either strict or loose in each path statement. If the link type is strict, the LSP must go to the next address specified in the path statement without traversing other switches. If the link type is loose, the LSP can traverse through other switches before reaching this switch. This configuration uses the default strict designation for the paths. NOTE: You can enable path protection without specifying which provider switches are used. If you do not list the specific provider switches to be used for the MPLS tunnel, the switch calculates the route. TIP: Do not include the ingress provider edge switch in these statements. List the IP address of the loopback interface or switch address or hostname of all other switch hops in sequence, ending with the egress provider edge switch. [edit protocols mpls label-switched-path lsp_to_240 to 127.0.0.8] user@switch# set path primary_path_lsp_to_240 127.0.0.2 user@switch# set path primary_path_lsp_to_240 127.0.0.3 user@switch# set path primary_path_lsp_to_240 127.0.0.8 3099 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring the Secondary Path You can configure zero or more secondary paths. All secondary paths are equal, and the software tries them in the order that they are listed in the configuration. The software does not attempt to switch among secondary paths. If the first secondary path in the configuration is not available, the next one is tried, as so on. To create a set of equal paths, specify secondary paths without specifying a primary path. If you do not specify any named paths, or if the path that you specify is empty, the software makes all routing decisions necessary to reach the egress provider edge switch. To configure the secondary path: 1. Create a secondary path for the LSP: [edit protocols mpls label-switched-path lsp_to_240 to 127.0.0.8] user@switch# set secondary secondary_path_lsp_to_240 standby 2. Configure an explicit route for the secondary path by specifying the IP address of the loopback interface or the switch IP address or hostname of each switch used in the MPLS tunnel. You can specify the link types as either strict or loose in each path statement. This configuration uses the default strict designation for the paths. TIP: Do not include the ingress provider edge switch in these statements. List the IP address of the loopback interface or switch address or hostname of all other switch hops in sequence, ending with the egress provider edge switch. [edit protocols mpls label-switched-path lsp_to_240 to 127.0.0.8] user@switch# set path secondary_path_lsp_to_240 127.0.0.4 user@switch# set path primary_path_lsp_to_240 127.0.0.8 Configuring the Revert Timer 3100 Chapter 122: Configuring MPLS For LSPs configured with both primary and secondary paths, you can optionally configure a revert timer. If the primary path goes down and traffic is switched to the secondary path, the revert timer specifies the amount of time (in seconds) that the LSP must wait before it can revert traffic back to the primary path. If the primary path experiences any connectivity problems or stability problems during this time, the timer is restarted. TIP: If you do not explicitly configure the revert timer, it is set by default to 60 seconds. To configure the revert timer for LSPs configured with primary and secondary paths: • For all LSPs on the switch: [edit protocols mpls] user@switch# set revert-timer 120 • For a specific LSP on the switch: [edit protocols mpls label-switched-path] user@switch# set lsp_to_240 revert-timer 120 Related Documentation • Understanding MPLS and Path Protection on J-EX Series Switches on page 3063 3101 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring MPLS on Provider Switches (CLI Procedure) Junos OS MPLS for J-EX Series switches supports Layer 2 protocols and Layer 2 virtual private networks (VPNs). You can configure MPLS on J-EX Series switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions. NOTE: You can use class of service (CoS) on MPLS networks. For further information, see “Understanding Using CoS with MPLS Networks on J-EX Series Switches” on page 2880. To implement MPLS on J-EX Series switches, you must configure at least one provider switch as a transit switch for the MPLS packets. The configuration of all the provider switches is the same regardless of whether the provider edge (PE) switches are using circuit cross-connect (CCC) or using MPLS over IP for the customer-edge interfaces. To configure the provider switch, complete the following tasks: 1. Enable the routing protocol (OSPF or IS-IS) on the loopback interface and on the core interfaces: NOTE: You can use the switch address as an alternative to the loopback interface. [edit protocols] user@switch# set ospf area 0.0.0.0 interface lo0.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/5.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0 user@switch# set ospf area 0.0.0.0 interface ae0 2. Enable traffic engineering for the routing protocol (OSPF or IS-IS): [edit protocols] user@switch# set ospf traffic-engineering 3. Enable MPLS within the protocols stanza and apply it to the core interfaces: [edit protocols] user@switch# set mpls interface ge-0/0/5.0 user@switch# set mpls interface ge-0/0/6.0 user@switch# set mpls interface ae0 4. Configure RSVP on the loopback interface and the core interfaces: [edit protocols] user@switch# set rsvp interface lo0.0 user@switch# set rsvp interface ge-0/0/5.0 user@switch# set rsvp interface ge-0/0/6.0 user@switch# set rsvp interface ae0 5. Configure an IP address for the loopback interface and for the core interfaces: 3102 Chapter 122: Configuring MPLS [edit] user@switch# set interfaces lo0 unit 0 family inet address 127.1.1.1/32 user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 user@switch# set interfaces ae0 unit 0 family inet address 10.1.9.2/24 6. Configure family mpls on the logical units of the core interfaces: [edit] user@switch# set interfaces ge-0/0/5 unit 0 family mpls user@switch# set interfaces ge-0/0/6 unit 0 family mpls user@switch# set interfaces ae0 unit 0 family mpls NOTE: You can enable family mpls on either individual interfaces or aggregated Ethernet interfaces. You cannot enable it on tagged VLAN interfaces. Related Documentation • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using MPLS Over IP (CLI Procedure) on page 3107 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 3103 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI Procedure) You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. This topic describes configuring CoS components on a provider edge (PE) switch that is using IP Over MPLS. This task describes now to create a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE switch. It includes configuring a policer firewall filter and applying it to the customer-edge interface of the ingress PE switch. The policer firewall filter ensures that the amount of traffic forwarded through the MPLS tunnel never exceeds the requested bandwidth allocation. For this procedure, we assume that the switch has already been configured for MPLS. See “Configuring MPLS on Provider Edge Switches Using MPLS Over IP (CLI Procedure)” on page 3107. 1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating: [edit class-of-service] user@switch#set classifiers dscp dscp1 import default 2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch#set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 4. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the customer-edge-interface: [edit firewall] set policer mypolicer if-exceeding bandwidth-limit 500m 5. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer: [edit firewall policer] set mypolicer if-exceeding burst-size-limit 33553920 6. Discard traffic that exceeds the rate limits for this policer: [edit firewall policer] set mypolicer then discard 7. To reference the policer, configure a filter term that includes the policer action: [edit firewall] user@switch# set family inet filter myfilter term t1 then policer mypolicer 8. Apply the filter to the customer-edge interface: 3104 Chapter 122: Configuring MPLS [edit interfaces] user@switch# set ge-2/0/3 unit 0 family inet address 121.121.121.1/16 policing filter myfilter NOTE: You can also configure schedulers and shapers as needed. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. Related Documentation • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. This topic describes configuring CoS components on provider edge (PE) switch that is using MPLS over circuit-cross connect (CCC). NOTE: If you are using MPLS with CCC, you can use only one type of DSCP/IP precedence and only one type of IEEE 802.1p on the CCC interfaces. This procedure creates a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE. It also enables a policer on the label-switched path (LSP) of the ingress PE to ensure that the amount of traffic forwarded through the LSP never exceeds the requested bandwidth allocation. 1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating: [edit class-of-service] user@switch#set classifiers dscp dscp1 import default 2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch#set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 4. Bind the DSCP classifier to the CCC interface: 3105 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS [edit ] user@switch# set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1 5. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the LSP: [edit firewall] set policer mypolicer if-exceeding bandwidth-limit 500m 6. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer: [edit firewall policer] set mypolicer if-exceeding burst-size-limit 33553920 7. Discard traffic that exceeds the rate limits for this policer: [edit firewall policer] set mypolicer then discard 8. To reference the policer, configure a filter term that includes the policer action: [edit firewall] user@switch# set family any filter myfilter term t1 then policer mypolicer 9. Apply the filter to the LSP: [edit protocols mpls] set label-switched-path lsp_to_pe2_ge1 policing filter myfilter NOTE: You can also configure schedulers and shapers as needed. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. Related Documentation • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Assigning CoS Components to Interfaces (CLI Procedure) on page 2928 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Understanding the Use of Policers in Firewall Filters on page 2752 Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) You can add class-of-service (CoS) components to your MPLS networks on J-EX Series switches to achieve end-to-end Differentiated Services to match your specific business requirements. The configuration of CoS components on the provider switches is the same regardless of whether the provider edge (PE) switches are using MPLS over CCC or IP over MPLS. This task shows how to configure a custom EXP classifier and custom EXP rewrite rule on the provider switch. 1. 3106 Import the default EXP classifier classes to the custom EXP classifier that you are creating: Chapter 122: Configuring MPLS [edit class-of-service] user@switch# set classifiers exp exp1 import default 2. Add the expedited-forwarding class to this custom EXP classifier, specifying a loss priority and code point: [edit class-of-service] user@switch#set classifiers exp exp1 forwarding-class expedited-forwarding loss-priority low code-points 010 3. Specify the values for the custom EXP rewrite rule, e1: [edit class-of-service] user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111 NOTE: You can also configure schedulers and shapers as needed. See “Defining CoS Schedulers (CLI Procedure)” on page 2920. Related Documentation • Example: Combining CoS with MPLS on J-EX Series Switches on page 2883 Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) You can configure MPLS on J-EX Series switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network or to ensure better performance for low-latency applications such as VoIP and other business-critical functions. To implement MPLS on J-EX Series switches, you must configure two provider edge (PE) switches—an ingress PE switch and an egress PE switch—and at least one provider switch. You can configure the customer-edge interfaces on the PE switches of the MPLS network as either circuit cross-connect (CCC) or using IP over MPLS. The main differences between configuring IP over MPLS and configuring MPLS over CCC are that for IP over MLPS you configure the customer-edge interfaces to belong to family inet rather than family ccc and you configure a static route for the label-switched path (LSP). The configuration of the provider switch is the same regardless of whether the PE switches are configured for MPLS over CCC or IP over MPLS. See “Configuring MPLS on Provider Switches (CLI Procedure)” on page 3102. This topic describes how to configure an ingress PE switch and an egress PE switch for IP over MPLS: 1. Configuring the Ingress PE Switch on page 3108 2. Configuring the Egress PE Switch on page 3109 3107 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Configuring the Ingress PE Switch To configure the ingress PE switch: 1. Configure OSPF (or IS-IS) on the loopback (or switch address) and core interfaces: [edit protocols] user@switch# set ospf area 0.0.0.0 interface lo0.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/5.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0 2. Enable traffic engineering for the routing protocol: [edit protocols] user@switch# set ospf traffic-engineering 3. Configure an IP address for the loopback interface and for the core interfaces: [edit] user@switch# set interfaces lo0 unit 0 family inet address 100.100.100.100/32 user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 4. Configure MPLS on the core interfaces: [edit protocols] user@switch# set mpls interface ge-0/0/5.0 user@switch# set mpls interface ge-0/0/6.0 5. Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets: [edit] user@switch# set interfaces ge-0/0/5 unit 0 family mpls user@switch# set interfaces ge-0/0/6 unit 0 family mpls 6. Configure RSVP on the loopback interface and the core interfaces: [edit protocols] user@switch# set rsvp interface lo0.0 user@switch# set rsvp interface ge-0/0/5.0 user@switch# set rsvp interface ge-0/0/6.0 7. Configure a customer-edge interface as a Layer 3 routed interface, specifying an IP address: [edit] user@switch# set interfaces ge-2/0/3 unit 0 family inet 121.121.121.1/16 8. Configure this Layer 3 customer-edge interface for the routing protocol: [edit] user@switch# set protocols ospf area 0.0.0 interface ge-2/0/3.0 9. Configure an LSP on the ingress PE switch (100.100.100.100) to send IP packets over MPLS to the egress PE switch (208.208.208.208): [edit protocols mpls] user@switch# set label-switched-path ip_lspjavae_29 from 100.100.100.100 user@switch# set label-switched-path ip_lspjavae_29 to 208.208.208.208 10. Disable constrained-path LSP computation for this LSP: 3108 Chapter 122: Configuring MPLS [edit protocols mpls] user@switch# set label-switched-path ip_lspjavae_29 no-cspf 11. Configure a static route from the ingress PE switch to the egress PE switch, thereby indicating to the routing protocol that the packets will be forwarded over the MPLS LSP that has been set up to that destination: [edit] user@switch# set routing-options static route 2.2.2.0/24 next-hop 100.100.100.100 user@switch# set routing-options static route 2.2.2.0/24 resolve Configuring the Egress PE Switch To configure the egress PE switch: 1. Configure OSPF (or IS-IS) on the loopback interface (or switch address) and core interfaces: [edit protocols] user@switch# set ospf area 0.0.0.0 interface lo0.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/5.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0 2. Enable traffic engineering for the routing protocol: [edit protocols] user@switch# set ospf traffic-engineering 3. Configure an IP address for the loopback interface and for the core interfaces: [edit] user@switch# set interfaces lo0 unit 0 family inet address 208.208.208.208/32 user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.20.1/24 user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.21.1/24 4. Configure MPLS on the core interfaces: [edit protocols] user@switch# set mpls interface ge-0/0/5.0 user@switch# set mpls interface ge-0/0/6.0 5. Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets: [edit] user@switch# set interfaces ge-0/0/5 unit 0 family mpls user@switch# set interfaces ge-0/0/6 unit 0 family mpls 6. Configure RSVP on the loopback interface and the core interfaces: [edit protocols] user@switch# set rsvp interface lo0.0 user@switch# set rsvp interface ge-0/0/5.0 user@switch# set rsvp interface ge-0/0/6.0 7. Configure a customer-edge interface as a Layer 3 routed interface, specifying an IP address: [edit] user@switch# set interfaces ge-2/0/3 unit 0 family inet address 2.2.2.1/16 3109 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 8. Configure this Layer 3 customer-edge interface for the routing protocol: [edit] user@switch# set protocols ospf area 0.0.0 interface ge-2/0/3 9. Configure an LSP on the egress PE switch (208.208.208.208) to send IP packets over MPLS to the ingress PE switch (100.100.100.100): [edit protocols mpls] user@switch# set label-switched-path ip_lsp29_javae from 208.208.208.208 user@switch# set label-switched-path ip_lspjavae_29 to 100.100.100.100 10. Disable constrained-path LSP computation for this LSP: [edit protocols mpls] user@switch# set label-switched-path ip_lsp29_javae no-cspf 11. Configure a static route from the ingress PE switch to the egress PE switch, thereby indicating to the routing protocol that the packets will be forwarded over the MPLS LSP that has been set up to that destination: [edit] user@switch# set routing-options static route 121.121.121.0/24 next-hop 208.208.208.208 user@switch# set routing-options static route 121.121.121.0/24 resolve Related Documentation 3110 • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Verifying That MPLS Is Working Correctly on page 3115 • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 Chapter 122: Configuring MPLS Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) Junos OS MPLS for J-EX Series switches supports Layer 2 protocols and Layer 2 virtual private networks (VPNs). You can configure MPLS on J-EX Series switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions. To implement MPLS on J-EX Series switches, you must configure two provider edge (PE) switches—an ingress PE switch and an egress PE switch— and at least one provider switch. You can configure the customer-edge interfaces on the PE switches of the MPLS network as either circuit cross-connect (CCC) or using MPLS over IP. For information on configuring MPLS over IP, see “Configuring MPLS on Provider Edge Switches Using MPLS Over IP (CLI Procedure)” on page 3107. You can also use class of service (CoS) on MPLS networks. For further information, see “Understanding Using CoS with MPLS Networks on J-EX Series Switches” on page 2880. This topic describes configuring PE switches using a circuit cross-connect (CCC). The customer-edge interface can be either a simple interface or a tagged VLAN interface. In both cases, you configure the logical unit of the customer-edge interface to belong to family ccc and you must configure an association between that interface and two label-switched paths (LSPs)—one for transmitting MPLS packets to the remote PE and the other for receiving MPLS packets from the remote PE. The following guidelines apply to CCC configurations: • When an interface is configured to belong to family ccc, it cannot belong to any other family. • You can send any kind of traffic over a CCC, including nonstandard bridge protocol data units (BPDUs) generated by other vendors’ equipment. If you are configuring a CCC on a tagged VLAN interface, you must explicitly enable VLAN tagging and specify a VLAN ID. NOTE: The VLAN tag ID cannot be configured on logical interface unit 0. The logical unit number must be 1 or higher. This procedure shows how to set up two CCCs: • If you are configuring a CCC on a simple interface (ge-0/0/1), you do not need to enable VLAN tagging or specify a VLAN ID. • If you are configuring a CCC on a tagged VLAN interface (ge-0/0/2), include all the steps in this procedure. To configure a PE switch, complete the following tasks. When you have completed configuring one PE switch, perform the same tasks on the other PE switch: 3111 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1. Configure OSPF on the loopback (or switch address) and core interfaces: [edit protocols] user@switch# set ospf area 0.0.0.0 interface lo0.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/5.0 user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0 user@switch# set ospf area 0.0.0.0 interface ae0 2. Enable traffic engineering for the routing protocol on both PE switches: [edit protocols] user@switch# set ospf traffic-engineering 3. Configure an IP address for the loopback interface and for the core interfaces: [edit] user@switch# set interfaces lo0 unit 0 family inet address 127.1.1.1/32 user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24 user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24 user@switch# set interfaces ae0 unit 0 family inet address 10.1.9.1/24 4. Enable MPLS and define the LSP: [edit protocols] user@switch# set mpls label-switched-path lsp_to_pe2_ge1 to 127.1.1.3 TIP: lsp_to_pe2_ge1 is the LSP name. You will need to use the specified name again when configuring the CCC. 5. Configure MPLS on the core interfaces: [edit protocols] user@switch# set mpls interface ge-0/0/5.0 user@switch# set mpls interface ge-0/0/6.0 user@switch# set mpls interface ae0 6. Configure RSVP on the loopback interface and the core interfaces: [edit protocols] user@switch# set rsvp interface lo0.0 user@switch# set rsvp interface ge-0/0/5.0 user@switch# set rsvp interface ge-0/0/6.0 user@switch# set rsvp interface ae0 7. Configure family mpls on the logical units of the core interfaces: [edit] user@switch# set interfaces ge-0/0/5 unit 0 family mpls user@switch# set interfaces ge-0/0/6 unit 0 family mpls user@switch# set interfaces ae0 unit 0 family mpls NOTE: You can enable family mpls on either individual interfaces or aggregated Ethernet interfaces. You cannot enable it on tagged VLAN interfaces. 3112 Chapter 122: Configuring MPLS 8. If you are configuring a CCC on a tagged VLAN interface, enable VLAN tagging on the customer-edge interface ge-0/0/2 of the local PE switch: [edit interfaces ge-0/0/2] user@switch# set vlan-tagging If you are configuring a CCC on a simple interface (ge-0/0/1), omit this step. 9. If you are configuring a CCC on a tagged VLAN interface, configure the logical unit of the customer-edge interface with a VLAN ID: [edit interfaces ge-0/0/2 unit 1] user@switch# set vlan-id 100 If you are configuring a CCC on a simple interface (ge-0/0/1), omit this step. 10. Configure the logical unit of the customer-edge interface to belong to family ccc: [edit interfaces ge-0/0/1 unit 0] user@switch# set family ccc [edit interfaces ge-0/0/2 unit 1] user@switch# set family ccc 11. Associate the CCC interface with two LSPs, one for transmitting MPLS packets and the other for receiving MPLS packets: [edit protocols] user@switch# set connections remote-interface-switch ge-1–to-pe2 interface ge-0/0/1.0 user@switch# set connections remote-interface-switch ge-1–to-pe2 transmit-lsp lsp_to_pe2_ge1 user@switch# set connections remote-interface-switch ge-1–to-pe2 receive-lsp lsp_to_pe1_ge1 [edit protocols] user@switch# set connections remote-interface-switch ge-1–to-pe2 interface ge-0/0/2.1 user@switch# set connections remote-interface-switch ge-1–to-pe2 transmit-lsp lsp_to_pe2_ge1 user@switch# set connections remote-interface-switch ge-1–to-pe2 receive-lsp lsp_to_pe1_ge1 TIP: The transmit-lsp option specifies the LSP name that was configured on PE-1 (the local PE switch) by the label-switched-path statement within the protocols mpls stanza. The receive-lsp option specifies the LSP name that was configured on PE-2 (the remote PE switch) by the label-switched-path statement within the protocols mpls stanza. When you have completed configuring one PE switch, follow the same procedures to configure the other PE switch. Related Documentation • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 3113 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 3114 • Configuring MPLS on Provider Edge Switches Using MPLS Over IP (CLI Procedure) on page 3107 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Verifying That MPLS Is Working Correctly on page 3115 • Understanding Junos OS MPLS Components for J-EX Series Switches on page 3059 CHAPTER 123 Verifying MPLS • Verifying That MPLS Is Working Correctly on page 3115 • Verifying Path Protection in an MPLS Network on page 3118 Verifying That MPLS Is Working Correctly To verify that MPLS is working correctly on J-EX Series switches, perform the following tasks: 1. Verifying the Physical Layer on the Switches on page 3115 2. Verifying the Routing Protocol on page 3116 3. Verifying the Core Interfaces Being Used for the MPLS Traffic on page 3116 4. Verifying RSVP on page 3116 5. Verifying the Assignment of Interfaces for MPLS Label Operations on page 3117 6. Verifying the Status of the CCC on page 3117 Verifying the Physical Layer on the Switches Purpose Action Verify that the interfaces are up. Perform this verification task on each of the switches. user@switch> show interfaces ge- terse Interface ge-0/0/0 ge-0/0/0.0 ge-0/0/1.0 ge-0/0/2.0 ge-0/0/3.0 ge-0/0/4.0 ge-0/0/5.0 Admin up up up up up up up Link up up up up up up up Proto up up inet Local Remote ccc ccc eth-switch eth-switch inet 10.1.5.1/24 mpls ge-0/0/6.0 10.1.6.1/24 mpls Meaning The show interfaces terse command displays status information about the Gigabit Ethernet interfaces on the switch. This output verifies that the interfaces are up. The output for the protocol family (Proto column) shows that interfaces ge-0/0/1.0 and ge-0/0/2.0 are configured as circuit cross-connect. The Local and Remote columns do not display 3115 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS IP addresses, because the inet family is not configured for CCC interfaces. The output for the protocol family of the core interfaces (ge-0/0/0.5 and ge-0/0/0.6), shows that these interfaces are configured as both inet and mpls. The Local column for the core interfaces shows the IP address configured for these interfaces. Verifying the Routing Protocol Purpose Action Verify the state of the configured routing protocol. You should perform this verification task on each of the switches. The state should be Full. If you have configured OSPF as the routing protocol, use the show ospf neighbor command to verify that the routing protocol is communicating with the switch neighbors. If you have configured IS-IS as the routing protocol, use the show isis adjacency command to verify that the routing protocol is communicating with the switch neighbors. user@switch> show ospf neighbor Address 127.1.1.2 Meaning Interface ge—0/0/5 State Full ID 10.10.10.10 Pri Dead 128 39 The show ospf neighbor command displays the status of the routing protocol that has been configured on this switch. The output shows that the state is full, meaning that the routing protocol is operating correctly—that is, hello packets are being exchanged between directly connected neighbors. For additional information on checking and monitoring routing protocols, see the Junos OS Routing Protocols and Policies Command Reference at http://www.juniper.net/techpubs/software/junos/ . Verifying the Core Interfaces Being Used for the MPLS Traffic Purpose Action Verify that the state of the MPLS interface is Up. You should perform this verification task on each of the switches. user@switch> show mpls interface Interface ge—0/05 Meaning State Up Administrative groups The show mpls interface command displays the status of the core interfaces that have been configured to belong to family mpls. This output shows that the interface configured to belong to family mpls is up. Verifying RSVP Purpose Action Verify the state of the RSVP session. You should perform this verification task on each of the switches. user@switch> show rsvp session Ingress RSVP: 1 sessions To From State 127.1.1.3 127.1.1.1 Up lsp_to_pe2_ge1 Total 1 displayed, Up 1, Down 0 3116 Rt Style Labelin Labelout LSPname 0 1 FF 300064 Chapter 123: Verifying MPLS Egress RSVP: 1 sessions To From State 127.1.1.1 127.1.1.3 Up lsp_to_pe1_ge1 Total 1 displayed, Up 1, Down 0 Rt Style Labelin Labelout LSPname 0 1 FF 299968 - Transit RSVP: 0 sessions Total 0 displayed, Up 0, Down 0 Meaning This output confirms that the RSVP sessions are Up. Verifying the Assignment of Interfaces for MPLS Label Operations Purpose Action Meaning Verify which interface is being used as the beginning of the CCC and which interface is being used to push the MPLS packet to the next hop. You should perform this task only on the provider edge switches. user@switch> show route forwarding-table family mpls MPLS: Destination Type RtRef Next hop default perm 0 0 user 0 1 user 0 2 user 0 299776 user 0 ge-0/0/1.0 (CCC) user 0 127.1.2.1 Type Index NhRef Netif dscd 50 1 recv 49 3 recv 49 3 recv 49 3 Pop 541 2 ge-0/0/1.0 Push 299792 540 2 ge-0/0/5.0 This output shows that CCC has been set up on interface ge-0/0/1.0. The switch receives ingress traffic on ge-0/0/1.0 with label 299776. It pops that label and swaps it to label 299792, which it pushes out on interface ge-0/0/5.0. Verifying the Status of the CCC Purpose Action Verify the status of the CCC. You should perform this task only on the provider edge switches. user@switch> show connections CCC and TCC connections [Link Monitoring On] Legend for status (St) Legend for connection types UN -- uninitialized if-sw: interface switching NP -- not present rmt-if: remote interface switching WE -- wrong encapsulation lsp-sw: LSP switching DS -- disabled tx-p2mp-sw: transmit P2MP switching Dn -- down rx-p2mp-sw: receive P2MP switching -> -- only outbound conn is up <- -- only inbound conn is up Legend for circuit types Up -- operational intf -- interface RmtDn -- remote CCC down tlsp -- transmit LSP Restart -- restarting rlsp -- receive LSP Connection/Circuit ge1-to-pe2 ge-0/0/1.0 Type rmt-if intf St Up Up Time last up # Up trans Feb 17 05:00:09 1 3117 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS lsp_to_pe1_ge1 lsp_to_pe2_ge1 Meaning Related Documentation tlsp rlsp Up Up The show connections command displays the status of the CCC connections. This output verifies that the CCC interface and its associated transmit and receive LSPs are Up. • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 Verifying Path Protection in an MPLS Network To verify that path protection is working correctly on J-EX Series switches, perform the following tasks: 1. Verifying the Primary Path on page 3118 2. Verifying the RSVP-Enabled Interfaces on page 3119 3. Verifying a Secondary Path on page 3119 Verifying the Primary Path Purpose Action Verify that the primary path is operational. user@switch> show mpls lsp extensive ingress Ingress LSP: 2 sessions 127.1.8.8 From: 127.1.9.9, State: Up, ActiveRoute: 0, LSPname: lsp_to_240 ActivePath: primary_path_lsp_to_240 (primary) LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary primary_path_lsp_to_240 State: Up Priorities: 7 0 SmartOptimizeTimer: 180 Exclude: red Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2) 10.3.3.2 S 10.3.4.2 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID): 10.3.3.2 10.3.4.2 6 Mar 11 23:58:01.684 Selected as active path: due to 'primary' 5 Mar 11 23:57:00.750 Record Route: 10.3.3.2 10.3.4.2 4 Mar 11 23:57:00.750 Up 3 Mar 11 23:57:00.595 Originate Call 2 Mar 11 23:57:00.595 CSPF: computation result accepted 10.3.3.2 10.3.4.2 1 Mar 11 23:56:31.135 CSPF failed: no route toward 10.3.2.2[25 times] Standby secondary_path_lsp_to_240 State: Up Standby secondary_path_lsp_to_240 State: Up Priorities: 7 0 SmartOptimizeTimer: 180 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1) 10.3.5.2 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID): 3118 Chapter 123: Verifying MPLS 10.3.5.2 7 Mar 11 23:58:01.684 Deselected as active: due to 'primary' 6 Mar 11 23:46:17.298 Selected as active path 5 Mar 11 23:46:17.295 Record Route: 5.5.5.2 4 Mar 11 23:46:17.287 Up 3 Mar 11 23:46:16.760 Originate Call 2 Mar 11 23:46:16.760 CSPF: computation result accepted 10.3.5.2 1 Mar 11 23:45:48.095 CSPF failed: no route toward 10.5.5.5[2 times] Created: Wed Mar 11 23:44:37 2009 [Output truncated] Meaning As indicated by the ActivePath in the output, the LSP primary_path_lsp_to_240 is active. Verifying the RSVP-Enabled Interfaces Purpose Action Verify the status of Resource Reservation Protocol (RSVP)-enabled interfaces and packet statistics. user@switch> show rsvp interfaces RSVP interface: 1 active Active Subscr- Static Interface State resv iption BW ge-0/0/20.0 Up 2 100% 1000Mbps Meaning Available BW 1000Mbps Reserved BW 0bps Highwater mark 0bps This output verifies that RSVP is enabled and operational on interface ge-0/0/20.0. Verifying a Secondary Path Purpose Action Verify that a secondary path is established. Deactivate a switch that is critical to the primary path and then issue the following command: user@switch> show mpls lsp extensive Ingress LSP: 1 sessions 127.0.0.8 From: 127.0.0.1, State: Up, ActiveRoute: 0, LSPname: ActivePath: secondary_path_lsp_to_240 (secondary) LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: Primary primary_path_lsp_to_240 State: Dn Priorities: 7 0 SmartOptimizeTimer: 180 Exclude: red Will be enqueued for recomputation in 8 second(s). 51 Mar 8 12:23:31.268 CSPF failed: no route toward 50 Mar 4 15:35:25.610 Clear Call: CSPF computation 49 Mar 4 15:35:25.610 CSPF: link down/deleted: 127.0.0.2(127.0.0.1:0)(127.0.0.1)-> 0.0.0.0(127.0.0.20:0)(127.0.0.20) 48 Mar 4 15:35:25.576 Deselected as active 47 Mar 4 15:35:25.550 No Route toward dest 46 Mar 4 15:35:25.550 ????? 45 Mar 4 15:35:25.549 127.0.0.12: Down lsp_to_240 IPv4 127.0.0.11[11420 times] failed 3119 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 44 Mar 4 15:33:29.839 Selected as active path 43 Mar 4 15:33:29.837 Record Route: 127.0.0.20 127.0.0.40 42 Mar 4 15:33:29.835 Up 41 Mar 4 15:33:29.756 Originate Call 40 Mar 4 15:33:29.756 CSPF: computation result accepted 127.0.0.20 127.0.0.40 39 Mar 4 15:33:00.395 CSPF failed: no route toward 127.0.0.11[7 times] 38 Mar 4 15:30:31.412 Clear Call: CSPF computation failed 37 Mar 4 15:30:31.412 CSPF: link down/deleted: 127.0.0.2(127.0.0.1:0)(127.0.0.1)-> 0.0.0.0(127.0.0.20:0)(127.0.0.20) 36 Mar 4 15:30:31.379 Deselected as active 35 Mar 4 15:30:31.350 No Route toward dest 34 Mar 4 15:30:31.350 ????? 33 Mar 4 15:30:31.349 127.0.0.12: Down 32 Mar 4 15:29:05.802 Selected as active path 31 Mar 4 15:29:05.801 Record Route: 127.0.0.20 127.0.0.40 30 Mar 4 15:29:05.801 Up 29 Mar 4 15:29:05.686 Originate Call 28 Mar 4 15:29:05.686 CSPF: computation result accepted 127.0.0.20 127.0.0.40 27 Mar 4 15:28:35.852 CSPF failed: no route toward 127.0.0.11[132 times] 26 Mar 4 14:25:12.113 Clear Call: CSPF computation failed 25 Mar 4 14:25:12.113 CSPF: link down/deleted: 0.0.0.0(127.0.0.20:0)(127.0.0.20)-> 0.0.0.0(10.10.10.10:0)(10.10.10.10) *Standby secondary_path_lsp_to_240 State: Up Priorities: 7 0 SmartOptimizeTimer: 180 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1) [Output truncated] Meaning Related Documentation 3120 As indicated by the ActivePath in the output, the LSP secondary_path_lsp_to_240 is active. • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 • Understanding MPLS and Path Protection on J-EX Series Switches on page 3063 • For information on the show mpls lsp and show rvsp interfaces commands, see the Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/junos95/index.html. CHAPTER 124 Configuration Statements for MPLS • [edit protocols] Configuration Statement Hierarchy on page 3121 [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; 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); } } gvrp { ; interface (all | [interface-name]) { 3121 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS disable; } join-timer millseconds; leave-timer milliseconds; leaveall-timer milliseconds; } 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 { 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; } traceoptions { file filename ; flag flag (detail | disable | receive | send); } } lldp-med { disable; fast-start number; 3122 Chapter 124: Configuration Statements for MPLS 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } 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 { 3123 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 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); 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; 3124 Chapter 124: Configuration Statements for MPLS 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; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; } 3125 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS } sflow { agent-id collector { ip-address; udp-port port-number; } disable; interfaces interface-name { disable; polling-interval seconds; sample-rate number; } polling-interval seconds; sample-rate number; source-ip } stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; alarm; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; } 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 { alarm; block; } cost cost; disable; 3126 Chapter 124: Configuration Statements for MPLS edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } } Related Documentation • 802.1X for J-EX Series Switches Overview on page 2253 • Example: Configure Automatic VLAN Administration Using GVRP on page 1087 • Understanding MAC RADIUS Authentication on J-EX Series Switches • Understanding Server Fail Fallback and 802.1X Authentication on J-EX Series Switches on page 2258 • IGMP Snooping on J-EX Series Switches Overview on page 2047 • Understanding 802.1X and LLDP and LLDP-MED on J-EX Series Switches on page 2261 • Understanding MSTP for J-EX Series Switches on page 1277 • Understanding Multiple VLAN Registration Protocol (MVRP) on J-EX Series Switches on page 1054 • Understanding Ethernet OAM Connectivity Fault Management for a J-EX Series Switch on page 3463 • Understanding Ethernet OAM Link Fault Management for a J-EX Series Switch on page 3427 • Understanding RSTP for J-EX Series Switches on page 1276 • Understanding STP for J-EX Series Switches on page 1275 • Understanding How to Use sFlow Technology for Network Monitoring on a J-EX Series Switch on page 3283 • Understanding VSTP for J-EX Series Switches on page 1281 3127 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS connections Syntax Hierarchy Level Release Information Description connections { remote-interface-switch connection-name { interface interface-name.unit-number; transmit-lsp label-switched-path; receive-lsp label-switched-path; } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the connection between two circuits in a CCC connection. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 3128 Chapter 124: Configuration Statements for MPLS exp Syntax Hierarchy Level Release Information Description exp classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority level { code-points [ aliases ] [ 3–bit-patterns ]; } } } [edit class-of-service classifiers] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Define the experimental bits (EXP) code point mapping that is applied to the MPLS packets. J-EX Series switches support only one EXP code mapping on the switch (either default or custom). It is applied globally and implicitly to all the MPLS-enabled interfaces on the switch. You cannot bind it to an individual interface and you cannot disable it. Options classifier-name—Name of the classifier. The remaining statements are explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Understanding Using CoS with MPLS Networks on J-EX Series Switches on page 2880 • Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure) on page 3111 • Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure) on page 3107 • Configuring CoS on Provider Switches of an MPLS Network (CLI Procedure) on page 3106 3129 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS interface Syntax Hierarchy Level Release Information Description Default Options interface (all | interface-name); [edit protocols mpls] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable MPLS on all interfaces on the switch or on the specified interface. MPLS is disabled. all—All interfaces on the switch. interface-name—Name of an interface: Required Privilege Level Related Documentation 3130 • Aggregated Ethernet—aex • Gigabit Ethernet—ge-fpc/pic/port routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 Chapter 124: Configuration Statements for MPLS label-switched-path Syntax Hierarchy Level Release Information label-switched-path lsp-name to remote-provider-edge-switch; [edit protocols mpls] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Define a label-switched path (LSP) to the remote provider edge switch to use for MPLS traffic. You must specify this statement on the provider edge switch. Options lsp-name —Name that identifies the LSP. The name can be up to 32 characters and can contain letters, digits, periods, and hyphens. To include other characters, enclose the name in quotation marks. The name must be unique on the ingress switch. remote-provider-edge-switch —Either the loopback address or the switch address. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 3131 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mpls Syntax Hierarchy Level Release Information Description mpls { interface ( all | interface-name ); label-switched-path lsp-name to remote-provider-edge-switch; path destination {
} } [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable MPLS on the switch. The remaining statements are explained separately. Default Required Privilege Level Related Documentation MPLS is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 3132 Chapter 124: Configuration Statements for MPLS path Syntax Hierarchy Level Release Information Description Options path destination {
} [edit protocols mpls] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure path protection on your MPLS network. destination —Name of a label switched path (LSP). In addition to specifying the name of the configured LSP, you can include some other designation such as primary-path. address —(Optional) IP address of each transit switch (or the IP address of the loopback interface on the switch) in the LSP. If you want to control exactly which switches are selected for the LSP, specify the address or hostname of each transit switch. Specify the addresses in order, starting with the first provider (transit) switch, and continuing sequentially along the path until reaching the egress provider edge switch. Default: If you do not specify the addresses or hostnames of any switches, the LSP is calculated by the switch. hostname —(Optional) See address . Default: If you do not specify the addresses or hostnames of any switches, the LSP is calculated by the switch. loose—(Optional) Indicates that the next address in the path statement is a loose link. This means that the LSP can traverse through other switches before reaching this switch. Default: strict strict—(Optional) Indicates that the LSP must go to the next address specified in the path statement without traversing other switches. This is the default. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 3133 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS policing Syntax Hierarchy Level Release Information Description Options policing (filter filter-name | no-automatic-policing); [edit protocols mpls label-switched-path lsp-name] [edit interfaces interface-id unit number-of-logical-unit family inet address ip-address] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Apply a rate-limiting policer as the specified policing filter: • To the LSP for MPLS over CCC. • To the customer-edge interface for IP over MPLS. filter filter-name—Specify the name of the policing filter. no-automatic-policing—Disable automatic policing on this LSP. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • policer on page 2826 • Configuring Policers to Control Traffic Rates (CLI Procedure) on page 2788 • Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure) on page 2932 • Configuring CoS on MPLS Provider Edge Switch Using IP Over MPLS (CLI Procedure) on page 2931 primary Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation 3134 primary path-name; [edit protocols mpls label-switched-path lsp-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the primary path to use for a label switched path (LSP). You can configure only one primary path. path-name —Name of the primary path that you created with the path statement. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 Chapter 124: Configuration Statements for MPLS remote-interface-switch Syntax Hierarchy Level Release Information Description Options remote-interface-switch connection-name { interface interface-name.unit-number; receive-lsp label-switched-path; transmit-lsp label-switched-path; } [edit protocols connections] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure MPLS LSP tunnel cross-connects. This makes an association between a CCC interface and two LSPs, one for transmitting MPLS packets from the local provider edge switch to the remote provider edge switch and the other for receiving MPLS packets on the local provider edge switch from the remote provider edge switch. connection-name —Connection name. interface interface-name.unit-number —Interface name. Include the logical portion of the name, which corresponds to the logical unit number of the CCC interface. receive-lsp label-switched-path —Name of the LSP from the connection’s source. This LSP name was specified by the label-switched-path statement on the remote provider edge switch in the protocols mpls stanza. transmit-lsp label-switched-path —Name of the LSP to the connection’s destination. This LSP name was specified by the label-switched-path statement on the local provider edge switch in the protocols mpls stanza. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 3135 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS revert-timer Syntax Hierarchy Level Release Information Description revert-timer seconds; [edit protocols mpls], [edit protocols mpls label-switched-path lsp-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify the amount of time that a label switched path (LSP) must wait before traffic reverts to a primary path. If during this time the primary path experiences any connectivity problem or stability problem, the timer is restarted. If you have configured a value of 0 seconds for the revert-timer statement and traffic is switched to the secondary path, the traffic remains on that path indefinitely. It is never switched back to the primary path unless you intervene. Default Options 60 seconds seconds —Value in seconds. Range: 0 through 65,535 seconds Required Privilege Level Related Documentation 3136 routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 Chapter 124: Configuration Statements for MPLS rsvp Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation rsvp; [edit protocols] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable Resource Reservation Protocol (RSVP) signaling. The primary purpose of RSVP in the Junos OS for J-EX Series switches is to support dynamic signaling within label switched paths (LSPs). RSVP is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ secondary Syntax Hierarchy Level Release Information Description Options secondary path-name { standby; { [edit protocols mpls label-switched-path lsp-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Specify one or more secondary paths to use for the label switched path (LSP). You can configure more than one secondary path. All secondary paths are equal, and the first one that is available is chosen. path-name —Name of a secondary path that you created with the path statement. The remaining statement is explained separately. Required Privilege Level Related Documentation routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 3137 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS standby Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation standby; [edit protocols mpls label-switched-path lsp-name secondary path-name] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the path to remain up at all times to provide instant switchover if connectivity problems occur. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Configuring Path Protection in an MPLS Network (CLI Procedure) on page 3097 traffic-engineering Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation traffic-engineering; [edit protocols ospf | isis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable the traffic engineering features of the specified routing protocol. Traffic engineering is disabled. routing—To view this statement in the configuration. routing-control—To add this statement to the configuration. • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 • Configuring an OSPF Network (J-Web Procedure) on page 1435 • Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/ 3138 CHAPTER 125 Operational Mode Commands for MPLS 3139 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear mpls lsp Syntax Syntax (J-EX Series Switch) Release Information Description clear mpls lsp clear mpls lsp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Release the routes and states associated with MPLS label-switched paths (LSPs), and start new LSPs. CAUTION: This command disconnects existing Resource Reservation Protocol (RSVP) sessions on the ingress routing device. If there is a time lag between the old path being torn down and the new path being set up, this command might impact traffic traveling along the LSPs. Options none—Reset and restart all LSPs that originated from this routing device; that is, all LSPs for which this routing device is the ingress routing device. Depending on the number of LSPs involved, it might take a while to restart all the LSPs. autobandwidth—(Optional) Clear LSP autobandwidth counters. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. name name—(Optional) Reset and restart the specified LSP or group of LSPs. You can include wildcard characters in the interface name, as described in the Junos OS Network Interfaces Configuration Guide at http://www.juniper.net/techpubs/software/junos/. optimize | optimize-aggressive—(Optional) Run nonpreemptive optimization or aggressive optimization computation now. path regular-expression—(Optional) Clear the specific LSP path matching the specified regular expression. statistics—(Optional) Clear LSP statistics. 3140 Chapter 125: Operational Mode Commands for MPLS Required Privilege Level Related Documentation List of Sample Output clear • show mpls lsp on page 3189 • show rsvp session on page 3221 clear mpls lsp on page 3141 Output Fields When you enter this command, you are provided feedback on the status of your request. clear mpls lsp user@host> clear mpls lsp 3141 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear rsvp session Syntax Syntax (J-EX Series Switch) Release Information Description Options clear rsvp session clear rsvp session Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reset and restart Resource Reservation Protocol (RSVP) sessions. none—Reset and restart all RSVP sessions for which this routing device is the ingress, transit, or egress routing device. connection-source address—(Optional) Source address for GMPLS and MPLS LSPs from the RSVP sender template. connection-destination address—(Optional) Destination address for GMPLS and MPLS LSPs from the RSVP sender template. gracefully—(Optional) Gracefully reset an RSVP session for a nonpacket LSP in two passes. In the first pass, the Admin-Status object is signaled along the path to the other endpoint of the RSVP session. In the second pass, the path used by the RSVP session is torn down. This option can only be used on the ingress or egress routing device of the RSVP session and is only valid for nonpacket LSPs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. lsp-id identifier—(Optional) LSP identifier (source port) for the RSVP sender template. name name—(Optional) Reset and restart the specified RSVP session. optimize-fast-reroute—(Optional) Begin fast reroute optimization. tunnel-id identifier—(Optional) Tunnel identifier (destination port) for the RSVP session. 3142 Chapter 125: Operational Mode Commands for MPLS Required Privilege Level Related Documentation List of Sample Output Output Fields clear rsvp session clear • clear mpls lsp on page 3140 • show rsvp session on page 3221 clear rsvp session on page 3143 When you enter this command, you are provided feedback on the status of your request. user@host> clear rsvp session 3143 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS clear rsvp statistics Syntax Syntax (J-EX Series Switch) Release Information Description Options clear rsvp statistics clear rsvp statistics Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear Resource Reservation Protocol (RSVP) packet and error statistics. none—Clear RSVP packet and error statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level Related Documentation List of Sample Output Output Fields clear rsvp statistics 3144 clear • show rsvp statistics on page 3229 clear rsvp statistics on page 3144 When you enter this command, you are provided feedback on the status of your request. user@host> clear rsvp statistics Chapter 125: Operational Mode Commands for MPLS ping mpls l2circuit Syntax Release Information ping mpls l2circuit (interface interface-name | virtual-circuit virtual-circuit-id neighbor address) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Check the operability of the MPLS Layer 2 circuit connections. Type Ctrl+c to interrupt a ping mpls l2circuit command. Options count count—(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5. destination address—(Optional) Specify an address other than the default (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet. detail—(Optional) Display detailed information about the echo requests sent and received. exp forwarding-class—(Optional) Value of the forwarding class for the MPLS ping packets. interface interface-name—Ping an interface configured for the Layer 2 circuit on the egress provider edge (PE) router. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on the specified logical system. size bytes—(Optional) Size of the label-switched path (LSP) ping request packet (96 through 65468 bytes). Packets are 4-byte aligned. For example, If you enter a size of 97, 98, 99, or 100, the router or switch uses a size value of 100 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 96-byte minimum. source source-address—(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface (lo.0). sweep—(Optional) Automatically determine the size of the maximum transmission unit (MTU). v1—(Optional) Use the type 9 Layer 2 circuit type, length, and value (TLV). 3145 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS virtual-circuit virtual-circuit-id neighbor address—Ping the virtual circuit identifier on the egress PE router or switch and the specified neighbor, testing the integrity of the Layer 2 circuit between the ingress and egress PE routers or switches. Additional Information You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress PE router or switch (the router or switch receiving the MPLS echo packets) to ping a Layer 2 circuit. In asymmetric MTU scenarios, the echo response may be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large. Required Privilege Level List of Sample Output Output Fields network ping mpls l2circuit interface on page 3146 ping mpls l2circuit virtual-circuit detail on page 3146 When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code. Packets with an error code are not counted in the received packets count. They are accounted for separately. ping mpls l2circuit interface user@host> ping mpls l2circuit interface so-1/0/0.1 Request for seq 1, to interface 69, labels <100000, 100208>, packet size 100 Reply for seq 1, return code: Egress-ok, time: 0.439 ms ping mpls l2circuit virtual-circuit detail user@host> ping mpls l2circuit virtual-circuit 200 neighbor 10.255.245.122/32 detail Request for seq 1, to interface 68, labels <100048, 100128>, packet size 100 Reply for seq 1, return code: Egress-ok time: 0.539 ms 3146 Chapter 125: Operational Mode Commands for MPLS ping mpls l2vpn Syntax Release Information Description Options ping mpls l2vpn (instance instance-name local-site-id local-site-id-number remote-site-id remote-site-id-number | interface interface-name) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Check the operability of MPLS Layer 2 virtual private network (VPN) connections. Type Ctrl+c to interrupt a ping mpls l2vpn command. bottom-label-ttl—(Optional) Display the time-to-live value for the bottom label in the label stack. count count—(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5. destination address—(Optional) Specify an address other than the default (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet. detail—(Optional) Display detailed information about the echo requests sent and received. exp forwarding-class—(Optional) Value of the forwarding class for the MPLS ping packets. instance instance-name local-site-id local-site-id-number remote-site-id remote-site-id-number—Ping a combination of the Layer 2 VPN routing instance name, the local site identifier, and the remote site identifier, testing the integrity of the Layer 2 VPN circuit (specified by the identifiers) between the ingress and egress provider edge (PE) routers or switches. interface interface-name—Ping an interface configured for the Layer 2 VPN on the egress PE router or switch. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on the specified logical system. size bytes—(Optional) Size of the label-switched path (LSP) ping request packet (96 through 65468 bytes). Packets are 4-byte aligned. For example, If you enter a size of 97, 98, 99, or 100, the router or switch uses a size value of 100 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 96-byte minimum. 3147 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS source source-address—(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface (lo.0). sweep—(Optional) Automatically determine the size of the maximum transmission unit (MTU). Additional Information You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress PE router or switch (the router or switch receiving the MPLS echo packets) to ping a Layer 2 circuit. In asymmetric MTU scenarios, the echo response may be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large. Required Privilege Level List of Sample Output Output Fields network ping mpls l2vpn instance on page 3148 ping mpls l2vpn instance detail on page 3148 When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code these packets are not counted in the received packets count. They are accounted for separately. ping mpls l2vpn instance user@host> ping mpls l2vpn instance vpn1 remote-site-id 1 local-site-id 2 !!!!! --- lsping statistics --5 packets transmitted, 5 packets received, 0% packet loss ping mpls l2vpn instance detail user@host> ping mpls l2vpn instance vpn1 remote-site-id 1 local-site-id 2 detail Request for seq 1, to interface 68, labels <800001, 100176> Reply for seq 1, return code: Egress-ok Request for seq 2, to interface 68, labels <800001, 100176> Reply for seq 2, return code: Egress-ok Request for seq 3, to interface 68, labels <800001, 100176> Reply for seq 3, return code: Egress-ok Request for seq 4, to interface 68, labels <800001, 100176> Reply for seq 4, return code: Egress-ok Request for seq 5, to interface 68, labels <800001, 100176> Reply for seq 5, return code: Egress-ok --- lsping statistics --5 packets transmitted, 5 packets received, 0% packet loss 3148 Chapter 125: Operational Mode Commands for MPLS ping mpls l3vpn Syntax Release Information Description Options ping mpls l3vpn prefix prefix-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Check the operability of a MPLS Layer 3 virtual private network (VPN) connection. Type Ctrl+c to interrupt a ping mpls l3vpn command. bottom-label-ttl—(Optional) Display the time-to-live value for the bottom label in the label stack. count count—(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5. destination address—(Optional) Specify an address other than the default (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet. detail—(Optional) Display detailed information about the echo requests sent and received. exp forwarding-class—(Optional) Value of the forwarding class for the MPLS ping packets. l3vpn-name—(Optional) Layer 3 VPN name. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on the specified logical system. prefix prefix-name—Ping to test whether a prefix is present in a provider edge (PE) router’s or switch's VPN routing and forwarding (VRF) table, by means of a Layer 3 VPN destination prefix. This option does not test the connection between a PE router or switch and a customer edge (CE) router or switch. size bytes—(Optional) Size of the label-switched path (LSP) ping request packet (96 through 65468 bytes). Packets are 4-byte aligned. For example, If you enter a size of 97, 98, 99, or 100, the router or switch uses a size value of 100 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 96-byte minimum. source source-address—(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface (lo.0). 3149 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS sweep—(Optional) Automatically determine the size of the maximum transmission unit (MTU). Additional Information You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress PE router or switch (the router or switch receiving the MPLS echo packets) to ping a Layer 2 circuit. In asymmetric MTU scenarios, the echo response may be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large. Required Privilege Level List of Sample Output Output Fields ping mpls l3vpn ping mpls l3vpn detail 3150 network ping mpls l3vpn on page 3150 ping mpls l3vpn detail on page 3150 When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code these packets are not counted in the received packets count. They are accounted for separately. user@host> ping mpls l3vpn vpn1 prefix 10.255.245.122/32 !!!!! --- lsping statistics --5 packets transmitted, 5 packets received, 0% packet loss user@host> ping mpls l3vpn vpn1 prefix 10.255.245.122/32 detail Request for seq 1, to interface 68, labels <100128, 100112> Reply for seq 1, return code: Egress-ok Request for seq 2, to interface 68, labels <100128, 100112> Reply for seq 2, return code: Egress-ok Request for seq 3, to interface 68, labels <100128, 100112> Reply for seq 3, return code: Egress-ok Request for seq 4, to interface 68, labels <100128, 100112> Reply for seq 4, return code: Egress-ok Request for seq 5, to interface 68, labels <100128, 100112> Reply for seq 5, return code: Egress-ok --- lsping statistics --5 packets transmitted, 5 packets received, 0% packet loss Chapter 125: Operational Mode Commands for MPLS ping mpls ldp Syntax Release Information Description Options ping mpls ldp fec Command introduced before Junos OS Release 10.2 for J-EX Series switches. Check the operability of MPLS LDP-signaled label-switched path (LSP) connections. Type Ctrl+c to interrupt a ping mpls command. count count—(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5. destination address—(Optional) Specify an address other than the default (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet. detail—(Optional) Display detailed information about the echo requests sent and received. exp forwarding-class—(Optional) Value of the forwarding class for the MPLS ping packets. fec—Ping an LDP-signaled LSP using the forwarding equivalence class (FEC) prefix and length. instance routing-instance-name—(Optional) Allows you to ping a combination of the routing instance and forwarding equivalence class (FEC) associated with an LSP. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on the specified logical system. size bytes—(Optional) Size of the label-switched path (LSP) ping request packet (88 through 65468 bytes). Packets are 4-byte aligned. For example, If you enter a size of 89, 90, 91, or 92, the router or switch uses a size value of 92 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 88-byte minimum. source source-address—(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface (lo.0). sweep—(Optional) Automatically determine the size of the maximum transmission unit (MTU). 3151 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Additional Information If the LSP changes, the label and interface information displayed when you issued the ping command continues to be used. You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote router or switch to ping an LSP terminating there. You must configure MPLS even if you intend to ping only LDP forwarding equivalence classes (FECs). You can configure the ping interval for the ping mpls ldp command by specifying a new time in seconds using the lsp-ping-interval statement at the [edit protocols ldp oam] hierarchy level. For more information, see the Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/. In asymmetric MTU scenarios, the echo response may be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large. Required Privilege Level List of Sample Output Output Fields ping mpls ldp fec count 3152 network ping mpls ldp fec count on page 3152 When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code. Packets with error codes are not counted in the received packets count. They are accounted for separately. user@host> ping mpls ldp 10.255.245.222 count 10 !!!xxx...x--- lsping statistics ---10 packets transmitted, 3 packets received, 70% packet loss 4 packets received with error status, not counted as received. Chapter 125: Operational Mode Commands for MPLS ping mpls lsp-end-point Syntax Release Information Description Options ping mpls lsp-end-point prefix-name Command introduced before Junos OS Release 10.2 for J-EX Series switches. Check the operability of MPLS label-switched path (LSP) endpoint connections. Type Ctrl+c to interrupt a ping mpls command. count count—(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5. destination address—(Optional) Specify an address other than the default (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet. detail—(Optional) Display detailed information about the echo requests sent and received. exp forwarding-class—(Optional) Value of the forwarding class for the MPLS ping packets. instance routing-instance-name—(Optional) Ping a combination of the routing instance and forwarding equivalence class (FEC) associated with an LSP connection. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on the specified logical system. prefix-name—LDP forwarding equivalence class (FEC) prefix or RSVP LSP endpoint address. size bytes—(Optional) Size of the LSP ping request packet. If the endpoint is LDP-based, the minimum size of the packet is 88 bytes. If the endpoint is RSVP-based, the minimum size of the packet is 100 bytes. The maximum size in either case is 65468 bytes. source source-address—(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface (lo.0). sweep—(Optional) Automatically determine the size of the maximum transmission unit (MTU). Additional Information If the LSP changes, the label and interface information displayed when you issued the ping command continues to be used. You must configure MPLS at the [edit protocols 3153 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS mpls] hierarchy level on the remote router or switch to ping an LSP terminating there. You must configure MPLS even if you intend to ping only LDP forwarding equivalence classes (FECs). In asymmetric MTU scenarios, the echo response may be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large. Required Privilege Level List of Sample Output Output Fields ping mpls lsp-end-point detail 3154 network ping mpls lsp-end-point detail on page 3154 When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code these packets are not counted in the received packets count. They are accounted for separately. user@host> ping mpls lsp-end-point 10.255.245.119 detail Route to end point address is via LDP FEC Request for seq 1, to interface 67, label 100032 Reply for seq 1, return code: Egress-ok Request for seq 2, to interface 67, label 100032 Reply for seq 2, return code: Egress-ok Request for seq 3, to interface 67, label 100032 Reply for seq 3, return code: Egress-ok Request for seq 4, to interface 67, label 100032 Reply for seq 4, return code: Egress-ok Request for seq 5, to interface 67, label 100032 Reply for seq 5, return code: Egress-ok --- lsping statistics --5 packets transmitted, 5 packets received, 0% packet loss Chapter 125: Operational Mode Commands for MPLS ping mpls rsvp Syntax ping mpls rsvp lsp-name Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. The dynamic-bypass and manual-bypass options were introduced in Junos OS Release 10.2 for J-EX Series switches. Description Check the operability of MPLS RSVP-signaled label-switched path (LSP) connections. Type Ctrl+c to interrupt a ping mpls command. Options count count—(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5. destination address—(Optional) Specify an address other than the default (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet. detail—(Optional) Display detailed information about the echo requests sent and received. NOTE: When using the detail option, the reported time is based on the system time configured on the local and remote routers. Differences in these system times can result in an inaccurate one way ping trip times being reported. dynamic-bypass—(Optional) Ping dynamically generated bypass LSPs, used for protecting other LSPs. egress egress-address—(Optional) Only the specified egress router or switch responds to the ping request. exp forwarding-class—(Optional) Value of the forwarding class for the MPLS ping packets. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on the specified logical system. lsp-name—Ping an RSVP-signaled LSP using an LSP name. 3155 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS manual-bypass—(Optional) Ping manually configured bypass LSPs, used for protecting other LSPs. multipoint—(Optional) Send ping requests to each of the egress routers or switches participating in a point-to-multipoint LSP. You can also include the egress option to ping a specific egress router or switch participating in a point-to-multipoint LSP. size bytes—(Optional) Size of the LSP ping request packet (100 through 65468 bytes). Packets are 4-byte aligned. For example, if you enter a size of 101, 102, 103, or 104, the router or switch uses a size value of 104 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 100-byte minimum. source source-address—(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface. standby standby-path-name—(Optional) Name of the standby path. sweep —(Optional) Automatically determine the size of the maximum transmission unit (MTU). Additional Information If the LSP changes, the label and interface information displayed when you issued the ping command continues to be used. You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote router or switch to ping an LSP terminating there. You must configure MPLS even if you intend to ping only LDP forwarding equivalence classes (FECs). You can configure the ping interval for the ping mpls rsvp command by specifying a new time in seconds using the lsp-ping-interval statement at the [edit protocols mpls oam] hierarchy level. For more information, see the Junos OS MPLS Applications Configuration Guide at http://www.juniper.net/techpubs/software/junos/. In asymmetric MTU scenarios, the echo response may be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large. Required Privilege Level List of Sample Output Output Fields 3156 network ping mpls rsvp (Echo Reply Received) on page 3157 ping mpls rsvp (Echo Reply with Error Code) on page 3157 ping mpls rsvp detail on page 3157 ping mpls rsvp multipoint egress detail count on page 3157 ping mpls rsvp multipoint detail count on page 3157 ping mpls rsvp destination detail count size on page 3158 ping mpls rsvp destination detail sweep size on page 3158 When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates Chapter 125: Operational Mode Commands for MPLS that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code these packets are not counted in the received packets count. They are accounted for separately. ping mpls rsvp (Echo Reply Received) ping mpls rsvp (Echo Reply with Error Code) ping mpls rsvp detail ping mpls rsvp multipoint egress detail count user@host> ping mpls rsvp test1 !!!!!--- lsping statistics ---5 packets transmitted, 5 packets received, 0% packet loss user@host> ping mpls rsvp test2 !!xxx--- lsping statistics ---5 packets transmitted, 2 packets received, 60% packet loss3 packets received with error status, not counted as received. user@host> ping mpls rsvp to-green detail Request for seq 1, to interface 67, labels <100095, 0, 0> Reply for seq 1, return code: Egress-ok Request for seq 2, to interface 67, labels <100095, 0, 0> Reply for seq 2, return code: Egress-ok user@host>ping mpls rsvp sample-lsp multipoint egress 192.168.1.3 detail count 1 Request for seq 1, to interface 70, label 299952 Request for seq 1, to interface 70, no label stack. Request for seq 1, to interface 67, no label stack. Reply for seq 1, egress 192.168.1.3, return code: Egress-ok, time: 0.242 ms Local transmit time: 1205310695s 215737us Remote receive time: 1205310695s 215979us --- lsping, egress 192.168.1.3 statistics --1 packets transmitted, 1 packets received, 0% packet loss ping mpls rsvp multipoint detail count user@host>ping mpls rsvp sample-lsp multipoint detail count 1 Request for seq 1, to interface 70, label 299952 Request for seq 1, to interface 70, no label stack. Request for seq 1, to interface 67, no label stack. Reply for seq 1, return code: Unknown TLV, time: 9.877 ms Local transmit time: 1205310615s 347317us Remote receive time: 1205310615s 357194us Reply for seq 1, egress 192.168.1.3, return code: Egress-ok, time: 0.351 ms Local transmit time: 1205310615s 347262us Remote receive time: 1205310615s 347613us Reply for seq 1, egress 192.168.1.13, return code: Egress-ok, time: 0.301 ms Local transmit time: 1205310615s 347167us Remote receive time: 1205310615s 347468us Timeout for seq 1, egress 192.168.1.1 Timeout for seq 1, egress 192.168.1.4 Timeout for seq 1, egress 192.168.1.14 --- lsping, egress 192.168.1.1 statistics --1 packets transmitted, 0 packets received, 100% packet loss --- lsping, egress 192.168.1.3 statistics --1 packets transmitted, 1 packets received, 0% packet loss --- lsping, egress 192.168.1.4 statistics --1 packets transmitted, 0 packets received, 100% packet loss --- lsping, egress 192.168.1.13 statistics --- 3157 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS 1 packets transmitted, 1 packets received, 0% packet loss --- lsping, egress 192.168.1.14 statistics --1 packets transmitted, 0 packets received, 100% packet loss ping mpls rsvp destination detail count size user@host>ping mpls rsvp chaser-access destination 192.168.0.1 detail count 1 size 4468 Request for seq 1, to interface 88, label 299984, packet size 4468 Reply for seq 1, return code: Egress-ok, time: 44.804 ms Local transmit time: 2009-03-30 22:05:02 CEST 408.629 ms Remote receive time: 2009-03-30 22:05:02 CEST 453.433 ms --- lsping statistics --1 packets transmitted, 1 packets received, 0% packet loss ping mpls rsvp destination detail sweep size 3158 user@router> ping mpls rsvp chaser-access destination 192.168.0.1 detail sweep size 4500 Request for seq 1, to interface 86, no label stack., packet size 100 Reply for seq 1, return code: Egress-ok, time: -39.264 ms Local transmit time: 2009-04-24 14:05:40 CEST 541.423 ms Remote receive time: 2009-04-24 14:05:40 CEST 502.159 ms Request for seq 2, to interface 86, no label stack., packet size 2300 Reply for seq 2, return code: Egress-ok, time: -38.179 ms Local transmit time: 2009-04-24 14:05:41 CEST 544.240 ms Remote receive time: 2009-04-24 14:05:41 CEST 506.061 ms Request for seq 3, to interface 86, no label stack., packet size 4500 Timeout for seq 3 Request for seq 4, to interface 86, no label stack., packet size 3400 Reply for seq 4, return code: Egress-ok, time: -37.545 ms Local transmit time: 2009-04-24 14:05:45 CEST 549.953 ms Remote receive time: 2009-04-24 14:05:45 CEST 512.408 ms Request for seq 5, to interface 86, no label stack., packet size 3952 Reply for seq 5, return code: Egress-ok, time: -37.176 ms Local transmit time: 2009-04-24 14:05:46 CEST 555.881 ms Remote receive time: 2009-04-24 14:05:46 CEST 518.705 ms Request for seq 6, to interface 86, no label stack., packet size 4228 Reply for seq 6, return code: Egress-ok, time: -36.962 ms Local transmit time: 2009-04-24 14:05:47 CEST 561.809 ms Remote receive time: 2009-04-24 14:05:47 CEST 524.847 ms Request for seq 7, to interface 86, no label stack., packet size 4368 Reply for seq 7, return code: Egress-ok, time: -36.922 ms Local transmit time: 2009-04-24 14:05:48 CEST 568.738 ms Remote receive time: 2009-04-24 14:05:48 CEST 531.816 ms Request for seq 8, to interface 86, no label stack., packet size 4440 Reply for seq 8, return code: Egress-ok, time: -36.855 ms Local transmit time: 2009-04-24 14:05:49 CEST 575.669 ms Remote receive time: 2009-04-24 14:05:49 CEST 538.814 ms Request for seq 9, to interface 86, no label stack., packet size 4476 Timeout for seq 9 Request for seq 10, to interface 86, no label stack., packet size 4460 Reply for seq 10, return code: Egress-ok, time: -36.906 ms Local transmit time: 2009-04-24 14:05:53 CEST 584.382 ms Remote receive time: 2009-04-24 14:05:53 CEST 547.476 ms Request for seq 11, to interface 86, no label stack., packet size 4480 Timeout for seq 11 Request for seq 12, to interface 86, no label stack., packet size 4472 Timeout for seq 12 Request for seq 13, to interface 86, no label stack., packet size 4468 Reply for seq 13, return code: Egress-ok, time: -36.943 ms Local transmit time: 2009-04-24 14:06:00 CEST 594.884 ms Remote receive time: 2009-04-24 14:06:00 CEST 557.941 ms Request for seq 14, to interface 86, no label stack., packet size 4476 Chapter 125: Operational Mode Commands for MPLS Timeout for seq 14 Request for seq 15, to interface 86, no label stack., packet size 4472 Timeout for seq 15 --- lsp ping sweep result--Maximum Transmission Unit (MTU) is 4468 bytes 3159 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS request mpls lsp adjust-autobandwidth Syntax Syntax (J-EX Series Switch) Release Information Description Options request mpls lsp adjust-autobandwidth request mpls lsp adjust-autobandwidth Command introduced before Junos OS Release 10.2 for J-EX Series switches. Manually trigger a bandwidth allocation adjustment for active label-switched paths (LSPs). none—Manually trigger a bandwidth allocation adjustment for all active LSP paths. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. name lsp-name—(Optional) Manually trigger a bandwidth allocation adjustment on the specified LSP only. Additional Information Required Privilege Level List of Sample Output Output Fields request mpls lsp adjust-auto-bandwidth 3160 For this command to work properly, the following conditions must exist: • Automatic bandwidth allocation must be enabled on the LSP. The parameters for adjustment interval and maximum average bandwidth are not reset after you issue the request mpls lsp adjust-autobandwidth command. • The difference between the adjusted bandwidth and the current LSP path bandwidth must be greater than the threshold limit. maintenance request mpls lsp adjust-auto-bandwidth on page 3160 When you enter this command, you are provided feedback on the status of your request. user@host> request mpls lsp adjust-auto-bandwidth Chapter 125: Operational Mode Commands for MPLS show connections Syntax show connections Syntax (J-EX Series Switch) show connections Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the configured circuit cross-connect (CCC) connections. none—Display the standard level of output for all configured CCC connections. all—(Optional) Display all connections. brief | extensive—(Optional) Display the specified level of output. Use history to display information about connection history. Use labels to display labels used for transmit and receive LSPs. Use status to display information about the connection and interface status. interface-switch—(Optional) Display interface switch connections only. lsp-switch—(Optional) Display LSP switch connections only. p2mp-receive-switch—(Optional) Display point-to-multipoint LSP to local interfaces switch connections only. p2mp-transmit-switch—(Optional) Display local interface to point-to-multipoint LSP switch connections only. remote-interface-switch—(Optional) Display remote interface switch connections only. down | up | up-down—(Optional) Display nonoperational, operational, or both kinds of connections. history—(Optional) Display information about connection history. 3161 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS labels—(Optional) Display labels used for transmit and receive. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. name—(Optional) Display information about the specified connection only. status—(Optional) Display information about the connection and interface status. Required Privilege Level Output Fields view Table 412 on page 3162 describes the output fields for the show connections command. Output fields are listed in the approximate order in which they appear. Table 412: show connections Output Fields Field Name Field Description CCC and TCC connections [Link Monitoring On I Off] Whether link monitoring is enabled: On or Off. Legend for Status (St) Connection or circuit status. See the output's legend for an explanation of the status field values. Legend for connection types Type of connection: Legend for circuit types 3162 • if-sw—Layer 2 switching cross-connect. • rmt-if—Remote interface switch. While graceful restart is in progress, rmt-if will display a state (St) of Restart. • lsp-sw—LSP stitching cross-connect. While graceful restart is in progress, lsp-sw will display a state (St) of Restart. Type of circuits: • intf—Interface circuit. • tlsp—Transmit LSP circuit. • rlsp—Receive LSP circuit. Connection/Circuit Name of the configured CCC connection. Type Type of connection. St State of the connection. Time last up Time that the connection or circuit last transitioned to the Up (operational) state. # Up trans Number of times that the connection or circuit has transitioned to the Up (operational) state. Chapter 125: Operational Mode Commands for MPLS show connections user@switch> show connections CCC and TCC connections [Link Monitoring On] Legend for status (St) Legend for connection types UN -- uninitialized if-sw: interface switching NP -- not present rmt-if: remote interface switching WE -- wrong encapsulation lsp-sw: LSP switching DS -- disabled Dn -- down Legend for circuit types -> -- only outbound conn is up intf -- interface <- -- only inbound conn is up tlsp -- transmit LSP Up -- operational rlsp -- receive LSP RmtDn -- remote CCC down Restart -- restarting CCC Graceful restart : Restarting Connection/Circuit IFSW-ed so-1/0/2.0 t1-0/1/2.0 SW-db so-1/0/3.0 pro4-ca pro4-ac Type if-sw intf intf rmt-if intf tlsp rlsp St Time last up Up Aug 5 15:39:15 Up Up Restart Up Dn NP # Up trans 1 0 3163 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show connections Syntax Release Information Description Options show connections Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about the configured circuit cross-connect (CCC) connections. none—Display the standard level of output for all configured CCC connections on all logical systems. brief | extensive—(Optional) Display the specified level of output. all—(Optional) Display all connections. down | up | up-down—(Optional) Display nonoperational, operational, or both kinds of connections. history—(Optional) Display information about connection history. labels—(Optional) Display labels used for transmit and receive LSPs. name—(Optional) Display information about the specified connection only. remote-interface-switch—(Optional) Display remote interface switch connections only. name—(Optional) Display information about the specified connection only. status—(Optional) Display information about the connection and interface status. Required Privilege Level Related Documentation List of Sample Output 3164 view • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • connections on page 3128 show connections on page 3165 show connections brief on page 3165 show connections down on page 3166 show connections extensive on page 3166 show connections history on page 3166 show connections labels on page 3166 Chapter 125: Operational Mode Commands for MPLS show connections on page 3166 show connections remote-interface-switch on page 3166 show connections status on page 3167 Output Fields Table 413 on page 3165 describes the output fields for the show connections command. Output fields are listed in the approximate order in which they appear. Table 413: show connections Output Fields Field Name Field Description CCC and TCC connections [Link Monitoring On I Off] Whether link monitoring is enabled: On or Off. Legend for Status (St) Connection or circuit status. See the output's legend for an explanation of the status field values. Legend for connection types Type of connection: Legend for circuit types show connections • if-sw—Layer 2 switching cross-connect. • rmt-if—Remote interface switch. While graceful restart is in progress, rmt-if will display a state (St) of Restart. Type of circuit: • intf—Interface circuit. • tlsp—Transmit LSP circuit. • rlsp—Receive LSP circuit. Connection/Circuit Name of the configured CCC connection. Type Type of connection. St State of the connection. Time last up Time that the connection or circuit last transitioned to the Up (operational) state. # Up trans Number of times that the connection or circuit has transitioned to the Up (operational) state. user@switch> show connections Connection/Circuit ge1-to-pe2 1 ge-0/0/5.0 lsp_pe1_to_ge1_pe2 lsp_pe2_to_ge1_pe1 show connections brief Type rmt-if St Up intf tlsp rlsp Up Up Up Time last up # Up trans Jun 26 18:37:25 user@switch> show connections brief 3165 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Connection/Circuit ge-1_to_pe2 1 Type rmt-if Time last up # Up trans Jan 29 13:07:56 Type rmt-if St Up Time last up # Up trans Jan 29 13:07:56 intf tlsp rlsp Up Up Up Type rmt-if St Up show connections down user@switch> show connections down No matching connections found. show connections extensive user@switch> show connections extensive Connection/Circuit ge1_to_pe2 1 ge-0/0/5.0 lsp_pe1_to_ge1_pe2 lsp_pe2_to_ge1_pe1 Incoming labels: 299776 Outgoing labels: Push 300112 show connections history user@switch> show connections history Connection/Circuit ge1-to-pe2 1 Time Jan 29 Jan 29 Jan 29 Jan 29 Jan 29 Jan 29 Jan 29 Jan 29 Jan 29 Jan 29 show connections labels 13:07:56 13:07:55 13:07:55 13:07:55 13:07:54 13:01:08 13:01:08 13:01:06 13:01:04 13:01:02 Event CCC status update TLSP up TLSP down TLSP up RLSP up Remote CCC down Interface up Interface down Remote CCC down Interface down show connections show connections remote-interface-switch Time last up # Up trans Jan 29 13:07:56 Interface/Label 300112@1:0, 1 300112@1 300112@1:0, 4097 299776 ge-0/0/0.10 ge-0/0/0.10 # Paths Rcv Xmt 1 1 1 1 1 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 user@switch> show connections labels Connection/Circuit ge1-to-pe2 1 Incoming labels: 299776 Outgoing labels: Push 299792 3166 St Up Type rmt-if St RmtDn Time last up # Up trans Jun 26 18:37:25 Time last up # Up trans Jan 29 13:07:56 user@switch> show connections ge1-to-pe2 Connection/Circuit ge1_to_pe2 1 ge-0/0/5.0 lsp_pe1_to_ge1_pe2 lsp_pe2_to_ge1_pe1 Type rmt-if St Up intf tlsp rlsp Up Up Up Connection/Circuit xcon10_ge0_to_239 1 ge-0/0/0.10 lsp_to_240_10 Type rmt-if St Up intf tlsp Up Up Time last up # Up trans Jan 29 13:07:56 Chapter 125: Operational Mode Commands for MPLS lsp_to_239_10 xcon11_ge0_to_239 1 ge-0/0/0.11 lsp_to_240_11 lsp_to_239_11 show connections status rlsp rmt-if Up intf tlsp rlsp Up Up Up user@switch> show connections status Connection/Circuit Type xcon10_ge0_to_239 rmt-if 1 ge-0/0/0.10 intf lsp_to_240_10 tlsp lsp_to_239_10 rlsp xcon11_ge0_to_239 rmt-if 1 ge-0/0/0.11 intf lsp_to_240_11 tlsp lsp_to_239_11 rlsp Up St Up Up Up Up Up Jan 29 13:07:57 Time last up # Up trans Jan 29 13:07:56 Jan 29 13:07:57 Up Up Up 3167 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show link-management Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields show link-management Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiprotocol Label Switching (MPLS) peer and traffic engineering link information. This command has no options. view • show link-management peer on page 3171 • show link-management routing on page 3173 • show link-management statistics on page 3176 • show link-management te-link on page 3178 show link-management on page 3170 Table 414 on page 3168 describes the output fields for the show link-management command. Output fields are listed in the approximate order in which they appear. Table 414: show link-management Output Fields Field Name Field Description Peer Name Name of the peer. System identifier Internal identifier for the peer. The range of values is 0 through 64,000. State State of the peer: Up or Down. Control address Address to which a control channel is established. CC local ID Identifier assigned to the control channel by the local peer. The range of values is 1 through 4,294,967,296. CC remote ID Identifier assigned to the control channel by the remote peer. The range of values is 1 through 4,294,967,296. State State of the control channel: Up or Down. TxSeqNum Sequence number of the hello message being sent to the peer. The range of values is 1 through 4,294,967,295. RcvSeqNum Sequence number of the last hello message received from the peer. The range of values is 0 through 4,294,967,295. 3168 Chapter 125: Operational Mode Commands for MPLS Table 414: show link-management Output Fields (continued) Field Name Field Description Flags Code that provides information about the control channel. Currently supports only code value R, which indicates that the control channel is restarting after a failure in the control plane, as when the Link Management Protocol (LMP) process starts or restarts. TE links Traffic-engineered links that are managed by their peer. TE link name Name of the traffic-engineered link. State State of the traffic-engineered link: Up, Down, or Init. Local identifier Identifier of the local side of the link. Remote identifier Identifier of the remote side of the link. Local address Address of the local side of the link. Remote address Address of the remote side of the link. Encoding Physical layer media type determined by the interfaces contained in the traffic-engineered link. Typical values include SDH/SONET, Ethernet, Packet, and PDH. Switching Type of switching that can be performed on the traffic-engineered link. Supported values are PSC-1 and Packet. Minimum bandwidth Smallest single allocation of bandwidth possible on the traffic-engineered link. This number is equal to the smallest bandwidth interface that is a member of the traffic-engineered link (in bps). Maximum bandwidth Largest single allocation of bandwidth possible on the traffic-engineered link. This number is equal to the largest bandwidth interface that is a member of the link (in bps). Total bandwidth Sum of the bandwidth, in bits per second (bps) and megabits per second (Mbps), of all interfaces that are members of the link. Available bandwidth Sum of the bandwidths of all interfaces that are members of the link and that are not yet allocated (in bps). Name Name of the interface. State State of the interface: Up or Down. Local ID Identifier of the local side of the interface. Remote ID Identifier of the remote side of the interface. Bandwidth Bandwidth, in bps or Mbps, of the member interface. Used Whether the resource is allocated to an LSP: Yes or No. 3169 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 414: show link-management Output Fields (continued) Field Name Field Description LSP-name LSP name. show link-management user@host> show link-management Peer name: PEER-A, System identifier: 11973 State: Up, Control address: 10.255.245.4 CC local ID CC remote ID State TxSeqNum 24547 24547 Up 1027 TE links: pro4-ba RcvSeqNum Flags 1026 TE link name: pro4-ba, State: Init Local identifier: 2662, Remote identifier: 0, Encoding: SDH/SONET, Switching: PSC-1, Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 155.52Mbps Name State Local ID Remote ID so-1/0/2 Up 21271 0 3170 Bandwidth Used 155.52Mbps No LSP-name Chapter 125: Operational Mode Commands for MPLS show link-management peer Syntax Release Information Description Options show link-management peer Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiprotocol Label Switching (MPLS) peer link information. none—Display all peer link information. name peer-name—(Optional) Display information for the specified peer only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show link-management on page 3168 • show link-management routing on page 3173 • show link-management statistics on page 3176 • show link-management te-link on page 3178 show link-management peer on page 3172 Table 415 on page 3171 describes the output fields for the show link-management peer command. Output fields are listed in the approximate order in which they appear. Table 415: show link-management peer Output Fields Field Name Field Description Peer Name Name of the peer. System identifier Internal identifier for the peer. The range of values is 0 through 64,000. State State of the peer: Up or Down. Control address Address to which a control channel is established. Hello interval How often the routing device sends Link Management Protocol (LMP) hello packets. Hello dead interval How long LMP waits before declaring the control channel to be dead. This is an interval during which the routing device receives no LMP hello packets from the neighbor on a control that is active or up. CC local ID Identifier assigned to the control channel by the local peer. The range of values is 1 through 4,294,967,296. CC remote ID Identifier assigned to the control channel by the remote peer. The range of values is 1 through 4,294,967,296. 3171 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 415: show link-management peer Output Fields (continued) Field Name Field Description State State of the control channel: Up or Down. TxSeqNum Sequence number of the hello message being sent to the peer. The range of values is 1 through 4,294,967,295. RcvSeqNum Sequence number of the last hello message received from the peer. The range of values is 0 through 4,294,967,295. Flags Code that provides information about the control channel. Currently supports only code value R, which indicates that the control channel is restarting after a failure in the control plane, as when the Link Management Protocol (LMP) process starts or restarts. TE links Traffic-engineered links that are managed by their peer. show link-management peer 3172 user@host> show link-management peer Peer name: sonet, System identifier: 41448 State: Up, Control address: 70.70.70.70 Hello interval: 10000, Hello dead interval: 30000 CC local ID CC remote ID State TxSeqNum RcvSeqNum Flags 3265 0 ConfSnd 1 0 R TE links: to-sonet Chapter 125: Operational Mode Commands for MPLS show link-management routing Syntax Release Information Description Options show link-management routing | te-link > > Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiprotocol Label Switching (MPLS) peer or traffic engineering link information from the routing process. none—Display all peer and traffic-engineered link information. peer —(Optional) Display information for all peers or for the specified peer only. resource —(Optional) Display information for all resources or for the specified resource only. te-link —(Optional) Display information for all traffic-engineered forwarding paths or for the specified path only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show link-management on page 3168 • show link-management peer on page 3171 • show link-management statistics on page 3176 • show link-management te-link on page 3178 show link-management routing on page 3175 Table 416 on page 3173 describes the output fields for the show link-management routing command. Output fields are listed in the approximate order in which they appear. Table 416: show link-management routing Output Fields Field Name Field Description Peer Name Name of the peer. System identifier Internal identifier for the peer. The range of values is 0 through 64,000. State State of the peer: Up or Down. Control address Address to which a control channel is established. Control channel Interface over which control packets are sent. 3173 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 416: show link-management routing Output Fields (continued) Field Name Field Description State State of the control channel. TE link name Traffic-engineered link name. State State of the traffic-engineered link: Up or Down. Local identifier Identifier of the local side of the link. Remote identifier Identifier of the remote side of the link. Local address Address of the local side of the link. Remote address Address of the remote side of the link. Encoding Physical layer media type determined by the interfaces contained in the traffic-engineered link. Typical values include SDH/SONET, Ethernet, and Packet. Minimum bandwidth Smallest single allocation of bandwidth, in bits per second (bps) or megabits per second (Mbps), possible on the traffic-engineered link. This number is equal to the smallest bandwidth interface that is a member of the traffic-engineered link. Maximum bandwidth Largest single allocation of bandwidth, in bps or Mbps, possible on the traffic-engineered link. This number is equal to the largest bandwidth interface that is a member of the link (in bps). Total bandwidth Sum of the bandwidth, in bps or Mbps, of all interfaces that are members of the link. Available bandwidth Sum of the bandwidth, in bps or Mbps, of all interfaces that are members of the link and that are not yet allocated. Resource Forwarding adjacency LSP information. Type Type of resource. The type is always a forwarding adjacency LSP. State State of the LSP: Up or Down. System Identifier Internal identifier for the peer. The range of values is 0 through 64,000. Total bandwidth Bandwidth resource, in bps or Mbps, on the TE-link learned from the routing process. Traffic parameters • Encoding—Physical layer media type determined by the interfaces contained in the traffic-engineered link. Typical values include SDH/SONET, Ethernet, and Packet. • Switching—Type of switching that can be performed on the traffic-engineered link: PSC-1 and Packet. • Granularity—Layer 2 data for switching Layer 2 LSPs for this resource. Not supported. This value is always unknown. 3174 Chapter 125: Operational Mode Commands for MPLS show link-management routing user@host> show link-management routing Peer name: __rpd:fe-0/1/0.0, System identifier: 2147483649 State: Up, Control address: (null) Control-channel State fe-0/1/0.0 Active Peer name: __rpd:fe-0/1/2.0, System identifier: 2147483650 State: Up, Control address: (null) Control-channel State fe-0/1/2.0 Active Peer name: __rpd:so-0/2/0.0, System identifier: 2147483651 State: Down, Control address: (null) Control-channel State so-0/2/0.0 Peer name: __rpd:so-0/2/1.0, System identifier: 2147483652 State: Down, Control address: (null) Control-channel State so-0/2/1.0 ... TE link name: __rpd:fe-0/1/0.0, State: Up Local identifier: 2147483649, Remote identifier: 0, Local address: 192.168.37.66, Remote address: 192.168.37.66, Encoding: Ethernet, Minimum bandwidth: 0bps, Maximum bandwidth: 100Mbps, Total bandwidth: 100Mbps, Available bandwidth: 100Mbps TE link name: __rpd:fe-0/1/2.0, State: Up Local identifier: 2147483650, Remote identifier: 0, Local address: 192.168.37.73, Remote address: 192.168.37.73, Encoding: Ethernet, Minimum bandwidth: 0bps, Maximum bandwidth: 100Mbps, Total bandwidth: 100Mbps, Available bandwidth: 100Mbps TE link name: __rpd:so-0/2/0.0, State: Down Local identifier: 2147483651, Remote identifier: 0, Local address: 192.168.37.82, Remote address: 192.168.37.95, Encoding: Ethernet, Minimum bandwidth: 0bps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 155.52Mbps ... Resource: falsp-bd, Type: LSP, State: Dn System identifier: 2147483652, Total bandwidth: 0bps, Traffic parameters: Encoding: Packet, Switching: Packet, Granularity: Unknown Resource: falsp-be, Type: LSP, State: Up System identifier: 2147483654, Total bandwidth: bw[1]=10Mbps, Traffic parameters: Encoding: Packet, Switching: Packet, Granularity: Unknown 3175 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show link-management statistics Syntax show link-management statistics > Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display statistical information for Link Management Protocol (LMP) packets. Options none—Display information for all peers. peer —(Optional) Display information for all peers or for the specified peer only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show link-management on page 3168 • show link-management peer on page 3171 • show link-management routing on page 3173 • show link-management te-link on page 3178 show link-management statistics on page 3177 Table 417 on page 3176 describes the output fields for the show link-management statistics command. Output fields are listed in the approximate order in which they appear. Table 417: show link-management statistics Output Fields Field Name Field Description Received packets Number of received packets by message type. If the count for a message type is zero, that message type is not displayed. If the count for all message types is zero, this field is not displayed. Received bad packets Number of received bad packets by message type. If the count for a message type is zero, that message type is not displayed. If the count for all message types is zero, this field is not displayed. Small packets Number of packets that are too small. Wrong protocol version Number of packets specifying the wrong LMP version. Messages for unknown peer Number of packets destined for an unknown peer. Messages for bad state Number of packets indicating a state that does not match the recipient. Stale acknowledgments Number of configAck and LinkSummaryAck packets received that have a stale message ID. Stale negative acknowledgments Number of configNack and LinkSummaryNack packets received that have a stale message ID. 3176 Chapter 125: Operational Mode Commands for MPLS Table 417: show link-management statistics Output Fields (continued) Field Name Field Description Sent packets Number of sent packets by message type. If the count for a message type is zero, that message type is not displayed. If the count for all message types is zero, this field is not displayed. Retransmitted packets Number of retransmitted packets by message type. If the count for a message type is zero, that message type is not displayed. If the count for all message types is zero, this field is not displayed. Dropped packets Number of packets sent, by message type, that have been dropped by the receiver after the LMP retransmission interval has been exceeded. If the count for a message type is zero, that message type is not displayed. If the count for all message types is zero, this field is not displayed. show link-management statistics user@host> show link-management statistics peer pro4-a Statistics for peer pro4-a Received packets Config: 1 Hello: 2572 Small packets: 0 Wrong protocol version: 0 Messages for unknown peer: 0 Messages for bad state: 0 Stale acknowledgments: 0 Stale negative acknowledgments: 0 Sent packets Config: 2 ConfigAck: 1 Hello: 2572 Retransmitted packets Config: 1 3177 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show link-management te-link Syntax Release Information Description Options show link-management te-link Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the resources used to set up Multiprotocol Label Switching (MPLS) traffic-engineered forwarding paths. none—Display information for all traffic-engineered links. brief | detail—(Optional) Display the specified level of output. name name—(Optional) Display information for the specified traffic-engineered link only. Required Privilege Level Related Documentation List of Sample Output Output Fields view • show link-management on page 3168 • show link-management peer on page 3171 • show link-management routing on page 3173 • show link-management statistics on page 3176 show link-management te-link on page 3179 Table 418 on page 3178 describes the output fields for the show link-management te-link command. Output fields are listed in the approximate order in which they appear. Table 418: show link-management te-link Output Fields Field Name Field Description TE link name Traffic-engineered link name. State State of the traffic-engineered link: Up or Down. Local identifier Identifier of the local side of the link. Remote identifier Identifier of the remote side of the link. Local address Address of the local side of the link. Remote address Address of the remote side of the link. Encoding Physical layer media type determined by the interfaces contained in the traffic-engineered link. Typical values include SDH/SONET, Ethernet, Packet, and PDH. 3178 Chapter 125: Operational Mode Commands for MPLS Table 418: show link-management te-link Output Fields (continued) Field Name Field Description Switching Type of switching that can be performed on the traffic-engineered link. Supported values are PSC-1 and Packet. Minimum bandwidth Smallest single allocation of bandwidth, in bits per second (bps) or megabits per second (Mbps), possible on the traffic-engineered link. This number is equal to the smallest bandwidth interface that is a member of the traffic-engineered link. Maximum bandwidth Largest single allocation of bandwidth, in bps or Mbps, possible on the traffic-engineered link. This number is equal to the largest bandwidth interface that is a member of the link. Total bandwidth Sum of the bandwidth, in bps or Mbps, of all interfaces that are members of the link (in bps). Available Bandwidth Sum of the bandwidth, in bps or Mbps, of all interfaces that are members of the link and that are not yet allocated. Name Name of the interface. State State of the interface: Up or Down. Local ID Identifier of the local side of the interface. Remote ID Identifier of the remote side of the interface. Bandwidth Bandwidth, in bps or Mbps, of the member interface. Used Whether the resource is allocated to an LSP: Yes or No. LSP-name LSP name. show link-management te-link user@host> show link-management te-link TE link name: FA-bd, State: Up Local identifier: 4144, Remote identifier: 0, Local address: 2.2.2.1, Remote address: 2.2.2.2, Encoding: Ethernet, Switching: Packet, Minimum bandwidth: 0bps, Maximum bandwidth: 0bps, Total bandwidth: 0bps, Available bandwidth: 0bps Name State Local ID Remote ID Bandwidth Used LSP-name falsp-bd Dn 43077 0 0bps No TE link name: FA-be, State: Up Local identifier: 4145, Remote identifier: 0, Local address: 1.1.1.1, Remote address: 1.1.1.2, Encoding: Ethernet, Switching: Packet, Minimum bandwidth: 0bps, Maximum bandwidth: 10Mbps, Total bandwidth: 10Mbps, Available bandwidth: 8Mbps Name State Local ID Remote ID Bandwidth Used LSP-name falsp-be Up 43076 0 10Mbps Yes e2elsp-bf 3179 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show mpls admin-groups Syntax Syntax (J-EX Series Switch) show mpls admin-groups show mpls admin-groups Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display information about configured Multiprotocol Label Switching (MPLS) administrative groups. Options none—Display information about the configured MPLS administrative groups. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show mpls admin-groups on page 3180 Table 419 on page 3180 describes the output fields for the show mpls admin-groups command. Output fields are listed in the approximate order in which they appear. Table 419: show mpls admin-groups Output Fields show mpls admin-groups 3180 Field Name Field Description Group Name of the administrative group. Bit index Value assigned to the administrative group. user@host> show mpls admin-groups Group Bit index black 3 blue 2 gold 1 green 0 Chapter 125: Operational Mode Commands for MPLS show mpls call-admission-control Syntax Syntax (J-EX Series Switch) Release Information Description Options show mpls call-admission-control show mpls call-admission-control Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiprotocol Label Switching (MPLS) label-switched path (LSP) call admission control (CAC) information. none—Display CAC information for all LSPs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. lsp-name—(Optional) Display CAC information for the specified LSP only. Additional Information Required Privilege Level List of Sample Output Output Fields The available bandwidth on an LSP path at a particular class type is the total path bandwidth at that class type minus the total bandwidth reserved by any Layer 2 connection at that class type. view show mpls call-admission-control on page 3182 Table 420 on page 3181 describes the output fields for the show mpls call-admission-control command. Output fields are listed in the approximate order in which they appear. Table 420: show mpls call-admission-control Output Fields Field Name Field Description Available bandwidth Current available bandwidth on each LSP path. Depending on whether the LSP is an E-LSP or a regular LSP, either per-class bandwidth or a single bandwidth value (corresponding to best-effort bandwidth at ct0) is displayed. The available bandwidth on an LSP path at a particular class type is the total path bandwidth at that class type minus the total bandwidth reserved by some Layer 2 connections at that class type. Layer2 connections Different Layer 2 connections that had some bandwidth requirement and were admitted into an LSP path. LSP name LSP pathname. Neighbor address Neighbor address from which CAC and bandwidth booking are configured for Layer 2 circuits. Circuit Interface name and circuit information. 3181 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 420: show mpls call-admission-control Output Fields (continued) Field Name Field Description Primary LSP's primary standby path. Standby LSP's secondary standby path. VC bandwidth Bandwidth constraints associated with a Layer 2 circuit route. show mpls call-admission-control user@host# show mpls call-admission-control LSP name: pro1-be *Primary Available bandwidth: 0bps LSP name: pro1-be-1 *Primary Available bandwidth: 60kbps LSP name: pro1-be-gold *Primary Available bandwidth: Layer2 connections: Neighbor address: 10.255.245.215, Circuit: so-0/3/0.0(vc 5) VC bandwidth: LSP name: pro1-be-gold-2 *Primary Available bandwidth: LSP name: pro1-be-silver *Primary prim1 Available bandwidth: Layer2 connections: Neighbor address: 10.255.245.215, Circuit: so-0/3/0.1(vc 3) VC bandwidth: Standby sec1 Available bandwidth: Layer2 connections: Neighbor address: 10.255.245.215, Circuit: so-0/3/0.1(vc 3) VC bandwidth: 3182 Chapter 125: Operational Mode Commands for MPLS show mpls cspf Syntax Syntax (J-EX Series Switch) Release Information Description Options show mpls cspf show mpls cspf Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiprotocol Label Switching (MPLS) Constrained Shortest Path First (CSPF) statistics. none—Display MPLS CSFP statistics. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show mpls cspf on page 3184 Table 421 on page 3183 describes the output fields for the show mpls cspf command. Output fields are listed in the approximate order in which they appear. Table 421: show mpls cspf Output Fields Field Name Field Description Queue length Number of LSPs queued for automatic path computation. current Current queue length. maximum Maximum queue length (high-water mark). dequeued Number of aborted computation attempts. Paths Counters for label-switched path computations. total Sum of the next four fields. successful Number of path computations that were successfully completed. no route Number of path computations that failed because the destination is unreachable. Sys Error Number of path computations that failed because of lack of memory. CSPFs Total number of CSPF computations. A single path might require multiple CSPF computations. 3183 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 421: show mpls cspf Output Fields (continued) show mpls cspf 3184 Field Name Field Description Time Time, in seconds, required to perform the label-switched path computation. Total Total amount of time consumed by the CSPF path computation algorithm. CSPFs Total number of CSPF computations. Avg per CSPF Average amount of time required for each CSPF computation. % of rpd Percentage of routing process CPU used in the CSPF computation. user@host> show mpls cspf CSPF statistics Queue length current 0 Paths total 0 Time (secs) total 0.000000 maximum 0 successful 0 CSPFs 0.000000 dequeued 0 no route 0 avg per CSPF 0.000000 sys error 0 % of rpd 0.0000 CSPFs 0 Chapter 125: Operational Mode Commands for MPLS show mpls diffserv-te Syntax Syntax (J-EX Series Switch) Release Information Description Options show mpls diffserve-te show mpls diffserve-te Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display Multiprotocol Label Switching (MPLS) label-switched path (LSP) Differentiated Services (DiffServ) class and preemption priority information. none—Display DiffServ classes and priorities used by MPLS LSPs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Required Privilege Level List of Sample Output Output Fields view show mpls diffserv-te on page 3185 Table 422 on page 3185 describes the output fields for the show mpls diffserv-te command. Output fields are listed in the approximate order in which they appear. Table 422: show mpls diffserv-te Output Fields Field Name Field Description Bandwidth model Bandwidth constraint model supported. The maximum allocation model (MAM) for EXP-inferred LSPs (E-LSPs) is currently supported. TE class DiffServ traffic engineering class. Traffic class MPLS class type that corresponds to the DiffServ traffic engineering class: Priority show mpls diffserv-te • ct0—Best effort • ct1—Assured forwarding • ct2—Expedited forwarding • ct3—Network control MPLS preemption priority for this class type, a value from 0 through 7. Interior gateway protocols (IGPs) distribute information about the available bandwidth for each traffic engineering class. user@host> show mpls diffserv-te Bandwidth model: Maximum Allocation Model with support for E-LSPs. TE class Traffic class Priority 3185 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS te0 te1 3186 ct0 ct1 3 2 Chapter 125: Operational Mode Commands for MPLS show mpls interface Syntax Syntax (J-EX Series Switch) Release Information Description Options show mpls interface show mpls interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about Multiprotocol Label Switching (MPLS)-enabled interfaces. none—Display information about MPLS-enabled interfaces. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. Additional Information Required Privilege Level List of Sample Output Output Fields MPLS is enabled on an interface when the interface is configured with both the set protocol mpls interface interface-name and set interface interface-name unit 0 family mpls statements. view show mpls interface on page 3187 Table 423 on page 3187 describes the output fields for the show mpls interface command. Output fields are listed in the approximate order in which they appear. Table 423: show mpls interface Output Fields show mpls interface Field Name Field Description Interface Name of the interface. State State of the interface: Up or Dn (down). Administrative groups Administratively assigned colors of the link. user@host> show mpls interface Interface State Administrative groups so-1/0/0.0 Up Blue Yellow Red 3187 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show mpls interface Syntax Release Information Description Required Privilege Level Related Documentation List of Sample Output Output Fields show mpls interface Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display information about MPLS-enabled interfaces. MPLS is enabled on an interface when the interface is configured with both the set protocols mpls interface interface-name and set interfaces interface-name unit 0 family mpls commands. view • Example: Configuring MPLS on J-EX Series Switches on page 3071 • Configuring MPLS on Provider Edge Switches (CLI Procedure) • Configuring MPLS on Provider Switches (CLI Procedure) on page 3102 show mpls interface on page 3188 Table 424 on page 3188 describes the output fields for the show mpls interface command. Output fields are listed in the approximate order in which they appear. Table 424: show mpls interface Output Fields show mpls interface 3188 Field Name Field Description Interface Name of the interface. State State of the interface: Up or Dn (down). Administrative groups Administratively assigned colors of the link. user@switch> show mpls interface Interface State Administrative groups so-1/0/0.0 Up Blue Yellow Red Chapter 125: Operational Mode Commands for MPLS show mpls lsp Syntax Syntax (J-EX Series Switch) Release Information show mpls lsp show mpls lsp Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display information about configured and active dynamic Multiprotocol Label Switching (MPLS) label-switched paths (LSPs). Options none—Display standard information about all configured and active dynamic MPLS LSPs. brief | detail | extensive | terse—(Optional) Display the specified level of output. The extensive option displays the same information as the detail option, but covers the most recent 50 events. bidirectional | unidirectional—(Optional) Display bidirectional or unidirectional LSP information, respectively. bypass—(Optional) Display LSPs used for protecting other LSPs. defaults—(Optional) Display the MPLS LSP default settings. descriptions—(Optional) Display the MPLS label-switched path (LSP) descriptions. To view this information, you must configure the description statement at the [edit protocol mpls lsp] hierarchy level. Only LSPs with a description are displayed. This command is only valid for the ingress routing device, because the description is not propagated in RSVP messages. down | up—(Optional) Display only LSPs that are inactive or active, respectively. 3189 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. lsp-type—(Optional) Display information about a particular LSP type: • bypass—Sessions for bypass LSPs. • egress—Sessions that terminate on this routing device. • ingress—Sessions that originate from this routing device. • transit—Sessions that pass through this routing device. name name—(Optional) Display information about the specified LSP or group of LSPs. p2mp—(Optional) Display information about point-to-multipoint LSPs. statistics—(Optional) (Egress and transit routers only) Display accounting information about LSPs. Statistics are not available for LSPs on the egress routing device, because the penultimate routing device in the LSP sets the label to 0. Also, as the packet arrives at the egress routing device, the hardware removes its MPLS header and the packet reverts to being an IPv4 packet. Therefore, it is counted as an IPv4 packet, not an MPLS packet. transit—(Optional) Display LSPs transiting this routing device. Required Privilege Level Related Documentation List of Sample Output Output Fields view • clear mpls lsp on page 3140 show mpls lsp defaults on page 3195 show mpls lsp descriptions on page 3196 show mpls lsp detail on page 3196 show mpls lsp extensive on page 3196 show mpls lsp p2mp on page 3197 show mpls lsp p2mp detail on page 3197 Table 425 on page 3190 describes the output fields for the show mpls lsp command. Output fields are listed in the approximate order in which they appear. Table 425: show mpls lsp Output Fields Field Name Field Description Level of Output Ingress LSP Information about LSPs on the ingress routing device. Each session has one line of output. All levels Egress LSP Information about the LSPs on the egress routing device. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. Each session has one line of output. All levels 3190 Chapter 125: Operational Mode Commands for MPLS Table 425: show mpls lsp Output Fields (continued) Field Name Field Description Level of Output Transit LSP Number of LSPs on the transit routing devices and the state of these paths. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. All levels P2MP name Name of the point-to-multipoint LSP. Dynamically generated P2MP LSPs used for VPLS flooding use dynamically generated P2MP LSP names. The name uses the format identifier:vpls:router-id:routing-instance-name. The identifier is automatically generated by the Junos OS. All levels P2MP branch count Number of destination LSPs the point-to-multipoint LSP is transmitting to. All levels P An asterisk (*) under this heading indicates that the LSP is a primary path. All levels address (detail and extensive) Destination (egress routing device) of the LSP. detail extensive To Destination (egress routing device) of the session. brief From Source (ingress routing device) of the session. brief detail State State of the LSP handled by this RSVP session: Up, Dn (down), or Restart. brief detail Active Route Number of active routes (prefixes) installed in the forwarding table. For ingress LSPs, the forwarding table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the forwarding table is the primary MPLS table (mpls.0). detail extensive P Path. An asterisk (*) underneath this column indicates that the LSP is a primary path. brief LSPname Name of the LSP. brief detail DiffServeInfo Type of LSP: multiclass LSP (multiclass diffServ-TE LSP) or Differentiated-Services-aware traffic engineering LSP (diffServ-TE LSP). detail Bypass (Bypass LSP) Destination address (egress routing device) for the bypass LSP. All levels LSPpath Indicates whether the RSVP session is for the primary or secondary LSP path. LSPpath can be either primary or secondary and can be displayed on the ingress, egress, and transit routing devices. detail Bidir (GMPLS) The LSP allows data to travel in both directions between GMPLS devices. All levels Bidirectional (GMPLS) The LSP allows data to travel both ways between GMPLS devices. All levels Rt Number of active routes (prefixes) installed in the routing table. For ingress RSVP sessions, the routing table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the routing table is the primary MPLS table (mpls.0). brief ActivePath (Ingress LSP) Name of the active path: Primary or Secondary. detail extensive 3191 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 425: show mpls lsp Output Fields (continued) Field Name Field Description Level of Output FastReroute desired Fast reroute has been requested by the ingress routing device. detail Link protection desired Link protection has been requested by the ingress routing device. detail LoadBalance (Ingress LSP) CSPF load-balancing rule that was configured to select the LSP's path among equal-cost paths: Most-fill, Least-fill, or Random. detail extensive Signal type Signal type for GMPLS LSPs. The signal type determines the peak data rate for the LSP: DS0, DS3, STS-1, STM-1, or STM-4. All levels Encoding type LSP encoding type: Packet, Ethernet, PDH, SDH/SONET, Lambda, or Fiber. All levels Switching type Type of switching on the links needed for the LSP: Fiber, Lamda, Packet, TDM, or PSC-1. All levels GPID Generalized Payload Identifier (identifier of the payload carried by an LSP): HDLC, Ethernet, IPv4, PPP, or Unknown. All levels Protection Configured protection capability desired for the LSP: Extra, Enhanced, none, One plus one, One to one, or Shared. All levels Upstream label in (Bidirectional LSPs) Incoming label for reverse direction traffic for this LSP. All levels Upstream label out (Bidirectional LSPs) Outgoing label for reverse direction traffic for this LSP. All levels Suggested label received (Bidirectional LSPs) Label the upstream node suggests to use in the Resv message that is sent. All levels Suggested label sent (Bidirectional LSPs) Label the downstream node suggests to use in the Resv message that is returned. All levels Autobandwidth (Ingress LSP) The LSP is performing autobandwidth allocation. detail extensive MinBW (Ingress LSP) Configured minimum value of the LSP, in bps. detail extensive MaxBW (Ingress LSP) Configured maximum value of the LSP, in bps. detail extensive AdjustTimer (Ingress LSP) Configured value of the bandwidth adjustment timer, indicating the total amount of time allowed before bandwidth adjustment will take place, in seconds. detail extensive MaxAvgBW util (Ingress LSP) Current value of the actual maximum average bandwidth utilization, in bps. detail extensive Overflow limit (Ingress LSP) Configured value of the threshold overflow limit. detail extensive 3192 Chapter 125: Operational Mode Commands for MPLS Table 425: show mpls lsp Output Fields (continued) Field Name Field Description Level of Output Overflow sample count (Ingress LSP) Current value for the overflow sample count. detail extensive Bandwidth Adjustment in nnn second(s) (Ingress LSP) Current value of the bandwidth adjustment timer, indicating the amount of time remaining until the bandwidth adjustment will take place, in seconds. detail extensive Active path indicator (Ingress LSP) A value of * indicates that the path is active. The absence of * indicates that the path is not active. In the following example, “long” is the active path. detail extensive *Primary long Standby short Primary (Ingress LSP) Name of the primary path. detail extensive Secondary (Ingress LSP) Name of the secondary path. detail extensive Standby (Ingress LSP) Name of the path in standby mode. detail extensive State (Ingress LSP) State of the path: Up or Dn (down). detail extensive COS (Ingress LSP) Class-of-service value. detail extensive Bandwidth per class (Ingress LSP) Active bandwidth for the LSP path for each MPLS class type, in bps. detail extensive OptimizeTimer (Ingress LSP) Configured value of the optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds. detail extensive SmartOptimizeTimer (Ingress LSP) Configured value of the smart optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds. detail extensive Reoptimization in xxx seconds (Ingress LSP) Current value of the optimize timer, indicating the amount of time remaining until the path will be reoptimized, in seconds. detail extensive Computed ERO (S [L] denotes strict [loose] hops) (Ingress LSP) Computed explicit route. A series of hops, each with an address followed by a hop indicator. The value of the hop indicator can be strict (S) or loose (L). detail extensive CSPF metric (Ingress LSP) Constrained Shortest Path First metric for this path. detail extensive 3193 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Table 425: show mpls lsp Output Fields (continued) Field Name Field Description Level of Output Received RRO (Ingress LSP) Received record route. A series of hops, each with an address followed by a flag. (In most cases, the received record route is the same as the computed explicit route. If Received RRO is different from Computed ERO, there is a topology change in the network, and the route is taking a detour.) The following flags identify the protection capability and status of the downstream node: detail extensive • 0x01—Local protection available. The link downstream from this node is protected by a local repair mechanism. This flag can be set only if the Local protection flag was set in the SESSION_ATTRIBUTE object of the corresponding Path message. • 0x02—Local protection in use. A local repair mechanism is in use to maintain this tunnel (usually because of an outage of the link it was routed over previously). • 0x03—Combination of 0x01 and 0x02. • 0x04—Bandwidth protection. The downstream routing device has a backup path providing the same bandwidth guarantee as the protected LSP for the protected section. • 0x08—Node protection. The downstream routing device has a backup path providing protection against link and node failure on the corresponding path section. If the downstream routing device can set up only a link-protection backup path, the Local protection available bit is set but the Node protection bit is cleared. • 0x09—Detour is established. Combination of 0x01 and 0x08. • 0x10—Preemption pending. The preempting node sets this flag if a pending preemption is in progress for the traffic engine LSP. This flag indicates to the ingress legacy edge router (LER) of this LSP that it should be rerouted. • 0xb—Detour is in use. Combination of 0x01, 0x02, and 0x08. Index number (Ingress LSP) Log entry number of each LSP path event. The numbers are in chronological descending order, with a maximum of 50 index numbers displayed. extensive Date (Ingress LSP) Date of the LSP event. extensive Time (Ingress LSP) Time of the LSP event. extensive Event (Ingress LSP) Description of the LSP event. extensive Created (Ingress LSP) Date and time the LSP was created. extensive Resv style (Bypass) RSVP reservation style. This field consists of two parts. The first is the number of active reservations. The second is the reservation style, which can be FF (fixed filter), SE (shared explicit), or WF (wildcard filter). brief detail extensive Labelin Incoming label for this LSP. brief detail Labelout Outgoing label for this LSP. brief detail LSPname Name of the LSP. brief detail 3194 Chapter 125: Operational Mode Commands for MPLS Table 425: show mpls lsp Output Fields (continued) Field Name Field Description Level of Output Time left Number of seconds remaining in the lifetime of the reservation. detail Since Date and time when the RSVP session was initiated. detail Tspec Sender's traffic specification, which describes the sender's traffic parameters. detail Port number Protocol ID and sender or receiver port used in this RSVP session. detail PATH rcvfrom Address of the previous-hop (upstream) routing device or client, interface the neighbor used to reach this router, and number of packets received from the upstream neighbor. detail PATH sentto Address of the next-hop (downstream) routing device or client, interface used to reach this neighbor, and number of packets sent to the downstream routing device. detail RESV rcvfrom Address of the previous-hop (upstream) routing device or client, interface the neighbor used to reach this routing device, and number of packets received from the upstream neighbor. The output in this field, which is consistent with that in the PATH rcvfrom field, indicates that the RSVP negotiation is complete. detail Record route Recorded route for the session, taken from the record route object. detail Soft preempt Number of soft preemptions that occurred on a path and when the last soft preemption occurred. Only successful soft preemptions are counted (those that actually resulted in a new path being used). detail Soft preemption pending Path is in the process of being soft preempted. This display is removed once the ingress router has calculated a new path. detail MPLS-TE LSP Defaults Default settings for MPLS traffic engineered LSPs: defaults • LSP Holding Priority—Determines the degree to which an LSP holds on to its session reservation after the LSP has been set up successfully. • LSP Setup Priority—Determines whether a new LSP that preempts an existing LSP can be established. • Hop Limit—Specifies the maximum number of routers the LSP can traverse (including the ingress and egress). • Bandwidth—Specifies the bandwidth in bits per second for the LSP. • LSP Retry Timer—Length of time in seconds that the ingress router waits between attempts to establish the primary path. show mpls lsp defaults user@host> show mpls lsp defaults MPLS-TE LSP Defaults LSP Holding Priority LSP Setup Priority Hop Limit 0 7 255 3195 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS Bandwidth LSP Retry Timer show mpls lsp descriptions show mpls lsp detail 0 30 seconds user@host> show mpls lsp descriptions Ingress LSP: 3 sessions To LSP name 10.0.0.195 to-sanjose 10.0.0.195 to-sanjose-other-desc Total 2 displayed, Up 2, Down 0 Description to-sanjose-desc other-desc user@host> show mpls lsp detail Ingress LSP: 1 sessions 10.255.245.3 From: 10.255.245.5, State: Up, ActiveRoute: 1, LSPname: lsp-ec ActivePath: long-path (primary) LoadBalance: Random Autobandwidth MaxBW: 5Mbps AdjustTimer: 4800 secs AdjustThreshold: 1% Max AvgBW util: 0bps, Bandwidth Adjustment in 3383 second(s). Overflow limit: 5, Overflow sample count: 0 Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary long-path State: Up SmartOptimizeTimer: 180 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 5) 192.168.37.89 S 192.168.37.87 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt): 192.168.37.89 192.168.37.87 Total 1 displayed, Up 1, Down 0 Egress LSP: 0 sessions Total 0 displayed, Up 0, Down 0 show mpls lsp extensive user@host> show mpls lsp extensive Ingress LSP: 5 sessions 10.255.71.242 From: 10.255.71.238, State: Up, ActiveRoute: 1009, LSPname: sample-ccc ActivePath: path3 (primary) Link protection desired LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary path3 State: Up OptimizeTimer: 30 SmartOptimizeTimer: 180 Reoptimization in 26 second(s). Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1) 10.35.1.41 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt): 10 9 8 7 6 5 4 3196 Dec Dec Dec Dec Dec Dec Dec 10.35.1.41(Label=3) 8 13:51:58.986 CSPF: computation result ignored 8 13:51:30.547 Record Route: 10.35.1.41(Label=3) 8 13:51:30.547 Up 8 13:51:30.397 Originate make-before-break call 8 13:51:30.397 CSPF: computation result accepted 10.35.1.41 8 13:50:41.467 Selected as active path 8 13:50:41.467 Record Route: 10.35.1.41(Label=3) Chapter 125: Operational Mode Commands for MPLS 3 Dec 8 13:50:41.466 Up 2 Dec 8 13:50:41.371 Originate Call 1 Dec 8 13:50:41.371 CSPF: computation result accepted Created: Fri Dec 8 13:50:40 2006 Total 1 displayed, Up 1, Down 0 10.35.1.41 Egress LSP: 0 sessions Total 0 displayed, Up 0, Down 0 Transit LSP: 0 sessions Total 0 displayed, Up 0, Down 0 show mpls lsp p2mp user@host> show mpls lsp p2mp Ingress LSP: 2 sessions P2MP name: p2mp-lsp1, P2MP branch count: To From State Rt 10.255.245.51 10.255.245.50 Up 0 P2MP name: p2mp-lsp2, P2MP branch count: To From State Rt 10.255.245.51 10.255.245.50 Up 0 Total 2 displayed, Up 2, Down 0 1 ActivePath path1 1 ActivePath path1 P * LSPname p2mp-branch-1 P * LSPname p2mp-st-br1 Egress LSP: 0 sessions Total 0 displayed, Up 0, Down 0 Transit LSP: 0 sessions Total 0 displayed, Up 0, Down 0 show mpls lsp p2mp detail user@host> show mpls lsp p2mp detail Ingress LSP: 2 sessions P2MP name: p2mp-lsp1, P2MP branch count: 1 10.255.245.51 From: 10.255.245.50, State: Up, ActiveRoute: 0, LSPname: p2mp-branch-1 ActivePath: path1 (primary) P2MP name: p2mp-lsp1 LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary path1 State: Up Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 25) 192.168.208.17 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt): 192.168.208.17 P2MP name: p2mp-lsp2, P2MP branch count: 1 10.255.245.51 From: 10.255.245.50, State: Up, ActiveRoute: 0, LSPname: p2mp-st-br1 ActivePath: path1 (primary) P2MP name: p2mp-lsp2 LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary path1 State: Up Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 25) 192.168.208.17 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt): 192.168.208.17 Total 2 displayed, Up 2, Down 0 3197 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS show mpls path Syntax Syntax (J-EX Series Switch) Release Information Description Options show mpls path show mpls path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display dynamic Multiprotocol Label Switching (MPLS) label-switched paths (LSPs). none—Display standard information about all MPLS LSPs. logical-system (all | logical-system-name)—(Optional) Perform this operation on all logical systems or on a particular logical system. path-name—(Optional) Display information about the specified LSP only. Required Privilege Level List of Sample Output Output Fields view show mpls path on page 3198 Table 426 on page 3198 describes the output fields for the show mpls path command. Output fields are listed in the approximate order in which they appear. Table 426: show mpls path Output Fields show mpls path 3198 Field Name Field Description Path name Information about ingress LSPs. Each path has one line of output. Address Addresses of the routing devices that form the LSP. Strict/loose address Whether the address is a configured as a strict or loose address. user@host> show mpls path Path name Address p1 123.456.55.6 123.456.1.6 p2 191.456.1.4 Strict/loose address Strict Loose Strict Chapter 125: Operational Mode Commands for MPLS show route forwarding-table Syntax Release Information Description Options show route forwarding-table