System Basics and Services Command Reference
System Basics and Services Command Reference
System Basics and Services Command Reference
Release 8.1
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.
Juniper Networks, the Juniper Networks logo, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other
countries. JUNOS 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.
JUNOS Internet Software System Basics and Services Command Reference, Release 8.1
Writing: Andrea Cheek, Lisa Kelly, Elizabeth Lichtenberg, Regina Roman, Ines Salazar, and Alan Twhigg
Editing: Stella Hackell, Nancy Kurahashi, and Sonia Saruba
Illustration: Nathaniel Woodward
Cover design: Edmonds Design
Revision History
15 September 2006—Revision 1
The information in this document is current as of the date listed in the revision history.
Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS software has no known time-related limitations through the year
2038. However, the NTP application is known to have some difficulty in the year 2036.
Software License
The terms and conditions for using this software are described in the software license contained in the acknowledgment to your purchase order or, to the
extent applicable, to any reseller agreement or end-user purchase agreement executed between you and Juniper Networks. By using this software, you
indicate that you understand and agree to be bound by those terms and conditions.
Generally speaking, the software license restricts the manner in which you are permitted to use the software and may contain prohibitions against certain
uses. The software license may state conditions under which the license is automatically terminated. You should consult the license for further details.
For complete product documentation, please see the Juniper Networks Web site at www.juniper.net/techpubs.
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 Juniper Networks, Inc. and its subsidiaries (collectively “Juniper”), and 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, and updates and
releases of such software, for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller. "Embedded
Software" means Software which Juniper has embedded in the Juniper 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 the 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 software on multiple computers requires multiple licenses, regardless of whether such computers are physically contained on a single
chassis.
ii !
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits to
Customer's use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions, calls,
connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate licenses to use particular features,
functionalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing,
temporal, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the Software
to be used only in conjunction with other specific Software. Customer's use of the Software shall be subject to all such limitations and purchase of all
applicable licenses.
d. For any trial copy of the Software, Customer's right to use the Software expires 30 days after download, installation or use of the Software. Customer may
operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or create an additional trial period
by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer's enterprise network.
Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any
commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase the applicable
license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall not:
(a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as necessary
for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove any
proprietary notices, labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of the
Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any 'locked' or key-restricted
feature, function, service, application, operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even
if such feature, function, service, application, operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to
any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper
reseller; (i) use the Embedded Software on non-Juniper equipment; (j) use the 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 for the Software are exclusive of taxes, withholdings, duties, or levies (collectively “Taxes”). Customer shall be responsible for
paying Taxes arising from the purchase of the license, or importation or use of the Software.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign
agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or
without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption
or other capabilities restricting Customer's ability to export the Software without an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or
disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4,
FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface
information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any.
Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any
applicable terms and conditions upon which Juniper makes such information available.
! iii
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)).
iv !
Abbreviated Table of Contents
About This Guide xvii
Part 4 Services
Chapter 14 Compressed Real-Time Transport Protocol Operational Mode Commands 547
Chapter 15 CoS Services Operational Mode Commands 553
Chapter 16 Data Link Switching Operational Mode Commands 559
Chapter 17 Flow Collection and Monitoring Operational Mode Commands 573
Chapter 18 Intrusion Detection Service Operational Mode Commands 615
Chapter 19 IP Security Operational Mode Commands 627
Chapter 20 Layer 2 Tunneling Protocol Operational Mode Commands 689
Part 5 Indexes
Index 755
Index of Commands 765
Table of Contents ! ix
JUNOS 8.1 System Basics and Services Command Reference
x ! Table of Contents
Table of Contents
Table of Contents ! xi
JUNOS 8.1 System Basics and Services Command Reference
Part 4 Services
Part 5 Indexes
Index........................................................................................................................ 755
Index of Commands............................................................................................ 765
Table of Contents ! xv
JUNOS 8.1 System Basics and Services Command Reference
This preface provides the following guidelines for using the JUNOS Internet Software
System Basics and Services Command Reference and related Juniper Networks, Inc.,
technical documents:
Objectives
This manual provides descriptions of JUNOS Internet software commands that you
use to monitor and troubleshoot basic system operations and services on the router.
NOTE: This reference documents Release 8.1 of the JUNOS Internet software. For
additional information about the JUNOS software—either corrections to or
information that might have been omitted from this reference—see the software
release notes at http://www.juniper.net/.
Objectives ! xvii
JUNOS 8.1 System Basics and Services Command Reference
! J-series
! M-series
! T-series
Audience
This guide is designed for network administrators who are configuring and
monitoring a Juniper Networks routing platform.
To use this guide, you need a broad understanding of networks in general, the
Internet in particular, networking principles, and network configuration. You must
also be familiar with one or more of the following Internet routing protocols:
Personnel operating the equipment must be trained and competent; must not
conduct themselves in a careless, willfully negligent, or hostile manner; and must
abide by the instructions provided by the documentation.
Documentation Conventions
Table 1 defines notice icons used in this guide.
Audience ! xix
JUNOS 8.1 System Basics and Services Command Reference
Table 2 defines the text and syntax conventions used in this guide.
Italic typeface ! Introduces important new terms. ! A policy term is a named structure that defines
match conditions and actions.
! Identifies book names. ! JUNOS System Basics Configuration Guide
! Identifies RFC and Internet draft titles. ! RFC 1997, BGP Communities Attribute
Italic sans serif typeface Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or [edit]
configuration statements. root@# set system domain-name domain-name
Sans serif typeface Represents names of configuration ! To configure a stub area, include the stub
statements, commands, files, and statement at the [edit protocols ospf area area-id]
directories; IP addresses; configuration hierarchy level.
hierarchy levels; or labels on routing ! The console port is labeled CONSOLE.
platform components.
< > (angle brackets) Enclose optional keywords or variables. stub <default-metric metric>;
| (pipe symbol) Indicates a choice between the mutually broadcast | multicast
exclusive keywords or variables on either (string1 | string2 | string3)
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.
[ ] (square brackets) Enclose a variable for which you can community name members [ community-ids ]
substitute one or more values.
Indention and braces ( { } ) Identify a level in the configuration [edit]
hierarchy. routing-options {
static {
route default {
; (semicolon) Identifies a leaf statement at a nexthop address;
configuration hierarchy level. retain;
}
}
}
J-Web GUI Conventions
Bold typeface Represents J-Web graphical user interface ! In the Logical Interfaces box, select All Interfaces.
(GUI) items you click or select. ! To cancel the configuration, click Cancel.
> (bold right angle bracket) Separates levels in a hierarchy of J-Web In the configuration editor hierarchy, select
selections. Protocols>Ospf.
xx ! Documentation Conventions
About This Guide
Document Description
JUNOS Internet Software Configuration Guides
Class of Service Provides an overview of the class-of-service (CoS) functions of the JUNOS software
and describes how to configure CoS features, including configuring multiple
forwarding classes for transmitting packets, defining which packets are placed into
each output queue, scheduling the transmission service level for each queue, and
managing congestion through the random early detection (RED) algorithm.
CLI User Guide Describes how to use the JUNOS command-line interface (CLI) to configure, monitor,
and manage Juniper Networks routing platforms. This material was formerly
covered in the JUNOS System Basics Configuration Guide.
Feature Guide Provides a detailed explanation and configuration examples for several of the most
complex features in the JUNOS software.
High Availability Provides an overview of hardware and software resources that ensure a high level of
continuous routing platform operation and describes how to configure high
availability (HA) features such as nonstop routing (NSR) and graceful Routing Engine
switchover (GRES).
MPLS Applications Provides an overview of traffic engineering concepts and describes how to configure
traffic engineering protocols.
Multicast Protocols Provides an overview of multicast concepts and describes how to configure
multicast routing protocols.
Network Interfaces Provides an overview of the network interface functions of the JUNOS software and
describes how to configure the network interfaces on the routing platform.
Network Management Provides an overview of network management concepts and describes how to
configure various network management features, such as SNMP and accounting
options.
Policy Framework Provides an overview of policy concepts and describes how to configure routing
policy, firewall filters, forwarding options, and cflowd.
Routing Protocols Provides an overview of routing concepts and describes how to configure routing,
routing instances, and unicast routing protocols.
Secure Configuration Guide for Common Provides an overview of secure Common Criteria and JUNOS-FIPS protocols for the
Criteria and JUNOS-FIPS JUNOS Internet software and describes how to install and configure secure
Common Criteria and JUNOS-FIPS on a routing platform.
Services Interfaces Provides an overview of the services interfaces functions of the JUNOS software and
describes how to configure the services interfaces on the routing platform.
Software Installation and Upgrade Guide Provides a description of JUNOS software components and packaging, and includes
detailed information about how to initially configure, reinstall, and upgrade the
JUNOS system software. This material was formerly covered in the JUNOS System
Basics Configuration Guide.
System Basics Describes Juniper Networks routing platforms, and provides information about how
to configure basic system parameters, supported protocols and software processes,
authentication, and a variety of utilities for managing your router on the network.
Document Description
VPNs Provides an overview and describes how to configure Layer 2 and Layer 3 virtual
private networks (VPNs), virtual private LAN service (VPLS), and Layer 2 circuits.
Provides configuration examples.
JUNOS References
Hierarchy and RFC Reference Describes the JUNOS configuration mode commands. Provides a hierarchy
reference that displays each level of a configuration hierarchy, and includes all
possible configuration statements that can be used at that level. This material was
formerly covered in the JUNOS System Basics Configuration Guide.
Interfaces Command Reference Describes the JUNOS software operational mode commands you use to monitor and
troubleshoot interfaces.
Routing Protocols and Policies Command Describes the JUNOS software operational mode commands you use to monitor and
Reference troubleshoot routing protocols and policies, including firewall filters.
System Basics and Services Command Describes the JUNOS software operational mode commands you use to monitor and
Reference troubleshoot system basics, including commands for real-time monitoring and route
(or path) tracing, system software management, and chassis management. Also
describes commands for monitoring and troubleshooting services such as CoS, IP
Security (IPSec), stateful firewalls, flow collection, and flow monitoring.
System Log Messages Reference Describes how to access and interpret system log messages generated by JUNOS
software modules and provides a reference page for each message.
J-Web User Guide
J-Web Interface User Guide Describes how to use the J-Web GUI to configure, monitor, and manage Juniper
Networks routing platforms.
JUNOS API and Scripting Documentation
JUNOScript API Guide Describes how to use the JUNOScript application programming interface (API) to
monitor and configure Juniper Networks routing platforms.
JUNOS XML API Configuration Reference Provides reference pages for the configuration tag elements in the JUNOS XML API.
JUNOS XML API Operational Reference Provides reference pages for the operational tag elements in the JUNOS XML API.
JUNOS Configuration and Diagnostic Provides an overview, instructions for using, and examples of the commit script and
Automation Guide self-diagnosis features of the JUNOS software. This guide explains how to enforce
custom configuration rules defined in scripts that run at commit time, how to use
commit script macros to provide simplified aliases for frequently used configuration
statements, and how to configure diagnostic event policies and actions associated
with each policy.
NETCONF API Guide Describes how to use the NETCONF API to monitor and configure Juniper Networks
routing platforms.
JUNOS Comprehensive Index and Glossary
Comprehensive Index and Glossary Provides a complete index of all JUNOS software books, the JUNOScript API Guide,
and the NETCONF API Guide. Also provides a comprehensive glossary.
JUNOScope Documentation
JUNOScope Software User Guide Describes the JUNOScope software GUI, how to install and administer the software,
and how to use the software to manage routing platform configuration files and
monitor routing platform operations.
Document Description
J-series Services Router Documentation
Getting Started Guide Provides an overview, basic instructions, and specifications for J-series Services
Routers. The guide explains how to prepare your site for installation, unpack and
install the router and its components, install licenses, and establish basic
connectivity. Use the Getting Started Guide for your router model.
Basic LAN and WAN Access Configuration Explains how to configure the interfaces on J-series Services Routers for basic IP
Guide routing with standard routing protocols, ISDN backup, and digital subscriber line
(DSL) connections.
Advanced WAN Access Configuration Explains how to configure J-series Services Routers in virtual private networks
Guide (VPNs) and multicast networks, configure data link switching (DLSw) services, and
apply routing techniques such as policies, stateless and stateful firewall filters, IP
Security (IPSec) tunnels, and class-of-service (CoS) classification for safer, more
efficient routing.
Administration Guide Shows how to manage users and operations, monitor network performance,
upgrade software, and diagnose common problems on J-series Services Routers.
M-series and T-series Hardware Documentation
Hardware Guide Describes how to install, maintain, and troubleshoot routing platforms and
components. Each platform has its own hardware guide.
PIC Guide Describes the routing platform PICs. Each platform has its own PIC guide.
Release Notes
JUNOS Release Notes Summarize new features and known problems for a particular software release,
provide corrections and updates to published JUNOS, JUNOScript, and NETCONF
manuals, provide information that might have been omitted from the manuals, and
describe upgrade and downgrade procedures.
Hardware Release Notes Describe the available documentation for the routing platform and the supported
PICs, and summarize known problems with the hardware and accompanying
software. Each platform has its own release notes.
JUNOScope Software Release Notes Contain corrections and updates to the published JUNOScope manual, provide
information that might have been omitted from the manual, and describe upgrade
and downgrade procedures.
J-series Services Router Release Notes Briefly describe the J-series Services Router features, identify known hardware
problems, and provide upgrade and downgrade instructions.
Book Description
Baseline Describes the most basic tasks for running a network using Juniper Networks
products. Tasks include upgrading and reinstalling JUNOS software, gathering basic
system management information, verifying your network topology, and searching
log messages.
Interfaces Describes tasks for monitoring interfaces. Tasks include using loopback testing and
locating alarms.
MPLS Describes tasks for configuring, monitoring, and troubleshooting an example MPLS
network. Tasks include verifying the correct configuration of the MPLS and RSVP
protocols, displaying the status and statistics of MPLS running on all routers in the
network, and using the layered MPLS troubleshooting model to investigate problems
with an MPLS network.
Book Description
MPLS Log Reference Describes MPLS status and error messages that appear in the output of the show
mpls lsp extensive command. The guide also describes how and when to configure
Constrained Shortest Path First (CSPF) and RSVP trace options, and how to examine
a CSPF or RSVP failure in a sample network.
Hardware Describes tasks for monitoring M-series and T-series routing platforms.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. Send your comments to
[email protected], or fill out the documentation feedback form at
http://www.juniper.net/techpubs/docbug/docbugreport.html. If you are using e-mail,
be sure to include the following information with your comments:
! Document name
! Page number
Requesting Support
For technical support, open a support case using the Case Manager link at
http://www.juniper.net/support/ or call 1-888-314-JTAC (from the United States,
Canada, or Mexico) or 1-408-745-9500 (from elsewhere).
Table 5 summarizes the command-line interface (CLI) commands you can use to
perform and monitor connectivity functions. Commands are listed in alphabetical
order.
Task Command
Check host reachability and network connectivity. ping on page 4
! 3
JUNOS 8.1 System Basics and Services Command Reference
ping
Description Check host reachability and network connectivity. The ping command sends
Internet Control Message Protocol (ICMP) ECHO_REQUEST messages to elicit ICMP
ECHO_RESPONSE messages from the specified host.
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.
detail—(Optional) Include in the output the interface on which the ping reply was
received.
4 ! ping
Chapter 1: Connectivity Operational Mode Commands
interval seconds—(Optional) How often to send ping requests. The range of values,
in seconds, is 1 through infinity. The default value is 1.
rapid—(Optional) Send ping requests rapidly. The results are reported in a single
message, not in individual messages for each ping request. By default, five ping
requests are sent before the results are reported. To change the number of
requests, include the count option.
size bytes—(Optional) Size of ping request packets. The range of values, in bytes, is
0 through 65,468. The default value is 56, which is effectively 64 bytes because
8 bytes of ICMP header data are added to the packet.
ttl value—(Optional) Time-to-live (TTL) value to include in the ping request (IPv6).
The range of values is 0 through 255
wait seconds—(Optional) Delay, in seconds, after sending the last packet. If this
option is not specified, the default delay is 10 seconds. If this option is used
without the count option, a default count of 5 packets is used.
ping ! 5
JUNOS 8.1 System Basics and Services Command Reference
Output Fields 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 host size size user@host> ping skye size 200 count 5
count count PING skye.net (192.168.169.254): 200 data bytes
208 bytes from 192.168.169.254: icmp_seq=0 ttl=253 time=1.759 ms
208 bytes from 192.168.169.254: icmp_seq=1 ttl=253 time=2.075 ms
208 bytes from 192.168.169.254: icmp_seq=2 ttl=253 time=1.843 ms
208 bytes from 192.168.169.254: icmp_seq=3 ttl=253 time=1.803 ms
208 bytes from 192.168.169.254: icmp_seq=4 ttl=253 time=17.898 ms
6 ! ping
Chapter 1: Connectivity Operational Mode Commands
ping atm
Description Check the reachability of a remote Asynchronous Transfer Mode (ATM) node. All
packets are 53 bytes.
Options interface interface-name—Interface to use to send the ATM ping requests. For ATM 1
and ATM 2 interfaces, you must include a logical unit number in the interface
name
brief—(Optional) Display only the ATM ping summary statistics. These are
displayed after you type Ctrl+c to interrupt the ping atm command.
end-to-end—(Optional) Cells are sent to the end node. This is the default.
interval seconds—(Optional) How often to send ping requests. The range of values,
in seconds, is 1 through 10,000. The default value is 1.
Output Fields 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 atm ! 7
JUNOS 8.1 System Basics and Services Command Reference
ping clns
Description Check the reachability of a remote Connectionless Network Service (CLNS) node.
detail—(Optional) Include in the output the interface on which the ping reply was
received.
interval seconds—(Optional) How often to send ping requests. The range of values,
in seconds, is 1 through infinity. The default value is 1.
rapid—(Optional) Send ping requests rapidly. The results are reported in a single
message, not in individual messages for each ping request. By default, five ping
requests are sent before the results are reported. To change the number of
request, include the count option.
8 ! ping clns
Chapter 1: Connectivity Operational Mode Commands
size bytes—(Optional) Size of ping request packets. The range of values, in bytes, is
0 through 65,468. The default value is 56, which is effectively 64 bytes because
8 bytes of ICMP header data are added to the packet.
ttl value—(Optional) Time-to-live (TTL) value to include in the ping request (IPv6).
The range of values is 0 through 255.
wait seconds—(Optional) Delay, in seconds, after sending the last packet. If this
option is not specified, the default delay is 10 seconds. If this option is used
without the count option, a default count of 5 packets is used.
Output Fields 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 clns ! 9
JUNOS 8.1 System Basics and Services Command Reference
Description Check the operability of the Multiprotocol Label Switching (MPLS) Layer 2 circuit
connections.
Options interface interface-name—Ping an interface configured for the Layer 2 circuit on the
egress provider edge (PE) router.
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.
v1—(Optional) Use the type 9 Layer 2 circuit type, length, and value (TLV).
Additional Information You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress
PE router (the router receiving the MPLS echo packets) to ping a Layer 2 circuit. You
must also configure address 127.0.0.1/32 (or the address specified using the
destination option) on the egress PE router’s loopback interface. Otherwise, the
egress PE router does not have this forwarding entry and simply drops the
incoming ping packets.
Output Fields 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 l2circuit user@host> ping mpls l2circuit virtual-circuit 200 neighbor 10.255.245.122/32
virtual-circuit detail detail
Request for seq 1, to interface 68, labels <100048, 100128>
Reply for seq 1, return code: Egress-ok time: 0.539 ms
Description Check the operability of Multiprotocol Label Switching (MPLS) Layer 2 virtual
private network (VPN) connections.
bottom-label-ttl—(Optional) Display the time-to-live value for the bottom label in the
label stack.
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.
Additional Information You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress
PE router (the router receiving the MPLS echo packets) to ping a Layer 2 circuit. You
must also configure address 127.0.0.1/32 (or the address specified using the
destination option) on the egress PE router’s loopback interface. Otherwise, the
egress PE router does not have this forwarding entry and simply drops the
incoming ping packets.
Output Fields 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 user@host> ping mpls l2vpn instance vpn1 remote-site-id 1 local-site-id 2
instance !!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
ping mpls l2vpn user@host> ping mpls l2vpn instance vpn1 remote-site-id 1 local-site-id 2 detail
instance 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
Description Check the operability of a Multiprotocol Label Switching (MPLS) Layer 3 virtual
private network (VPN) connection.
Options prefix prefix-name—Ping to test whether a prefix is present in a provider edge (PE)
router’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 and a customer edge (CE) router.
bottom-label-ttl—(Optional) Display the time-to-live value for the bottom label in the
label stack.
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.
Additional Information You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress
PE router (the router receiving the MPLS echo packets) to ping a Layer 2 circuit. You
must also configure address 127.0.0.1/32 (or the address specified using the
destination option) on the egress PE router’s loopback interface. Otherwise, the
egress PE router does not have this forwarding entry and simply drops the
incoming ping packets.
Output Fields 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 l3vpn user@host> ping mpls l3vpn vpn1 prefix 10.255.245.122/32
!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
ping mpls l3vpn detail 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
Description Check the operability of Multiprotocol Label Switching (MPLS) Label Distribution
Protocol (LDP)-signaled label-switched path (LSP) connections.
Options fec—(Optional) Ping an LDP-signaled LSP using the forwarding equivalence class
(FEC) prefix and length.
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.
Additional Information If the LSP changes, the label and interface information displayed when the ping
command was issued continues to be used.
You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote
router to ping an LSP terminating there. You must configure MPLS even if you
intend to ping only LDP forwarding equivalence classes (FECs).
On the egress router (the router receiving the MPLS echo packets), you must
configure the address 127.0.0.1/32 (or the address specified using the destination
option) on its loopback interface. If this address is not configured correctly, the
egress router does not have this forwarding entry and therefore simply drops the
incoming MPLS ping packets and replies with “ICMP host unreachable” messages.
Output Fields 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 ldp fec count 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.
Description Check the operability of Multiprotocol Label Switching (MPLS) label-switched path
(LSP) endpoint connections.
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.
Additional Information If the LSP changes, the label and interface information displayed when the ping
command was issued continues to be used.
You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote
router to ping an LSP terminating there. You must configure MPLS even if you
intend to ping only LDP forwarding equivalence classes (FECs).
On the egress router (the router receiving the MPLS echo packets), you must
configure the address 127.0.0.1/32 (or the address specified using the destination
option) on its loopback interface. If this address is not configured correctly, the
egress router does not have this forwarding entry and therefore simply drops the
incoming MPLS ping packets and replies with “ICMP host unreachable” messages.
Output Fields 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.
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.
Additional Information If the LSP changes, the label and interface information displayed when the ping
command was issued continues to be used.
You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote
router to ping an LSP terminating there. You must configure MPLS even if you
intend to ping only LDP forwarding equivalence classes (FECs).
On the egress router (the router receiving the MPLS echo packets), you must
configure the address 127.0.0.1/32 (or the address specified using the destination
option) on its loopback interface. If this address is not configured correctly, the
egress router does not have this forwarding entry and therefore simply drops the
incoming MPLS ping packets and replies with “ICMP host unreachable” messages.
List of Sample Output ping mpls rsvp (Echo Reply Received) on page 21
ping mpls rsvp (Echo Reply with Error Code) on page 21
ping mpls rsvp lsp-name detail on page 21
Output Fields 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 rsvp lsp-name user@host> ping mpls rsvp to-green detail
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
Table 6 summarizes the command-line interface (CLI) commands you can use to
run diagnostics on router interfaces. Commands are listed in alphabetical order.
Task Command
Start a bit error rate test (BERT) on a DS0 interface. test interface ds0-bert-start on page 24
Stop a BERT on a DS0 interface. test interface ds0-bert-stop on page 25
Start a BERT on an E1 interface. test interface e1-bert-start on page 26
Transmit over a facilities data link (FDL) to initiate or terminate a far-end test interface fdl-line-loop on page 30
line loopback.
Transmit over an FDL to initiate or terminate a far-end payload loopback. test interface fdl-payload-loop on page 31
Transmit the line loopback activate code word sequence on the interface’s test interface feac-loop-initiate on page 32
far-end alarm and control (FEAC) channel.
Transmit the line loopback deactivate code word sequence on the test interface feac-loop-terminate on page 33
interface’s FEAC channel.
Initiate or terminate a far-end line loopback. test interface inband-line-loop on page 34
Initiate or terminate a far-end payload loopback. test interface inband-payload-loop on page 35
Restart auto-negotiation on a Fast Ethernet or Gigabit Ethernet interface. test interface restart-auto-negotiation on page 36
NOTE: For information about how to configure interface test parameters, see the
JUNOS Network Interfaces Configuration Guide. For information about related tasks
performed by Network Operations Center (NOC) personnel, see the JUNOS
Interfaces Network Operations Guide.
! 23
JUNOS 8.1 System Basics and Services Command Reference
Additional Information Before starting a BERT, you must disable the interface. To do so, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT
on only one interface per PIC at a time.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Additional Information Before starting a BERT, you must disable the interface. To do this, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT
on only one interface per PIC at a time.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Additional Information Before starting a BERT, you must disable the interface. To do so, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT
on only one interface per PIC at a time.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Syntax test interface fdl-line-loop (ansi (initiate | terminate) | bellcore (initiate | terminate))
t1-fpc/pic/port<:channel>
Description Send commands over the facilities data link (FDL) on a T1 interface to initiate or
terminate a far-end line loopback using either an ANSI or Bellcore FDL command
code. If the far end of the connection is in C-bit parity mode and it has been
configured to accept line loopback requests from the near end, the far end executes
the request.See the ANSI T1.107 specification for more details.
Output Fields To display the state and the number of times the interface has placed itself into
remote loopback, use the show interfaces extensive command.
Syntax test interface fdl-payload-loop (ansi (initiate | terminate) | bellcore (initiate | terminate)
t1-fpc/pic/port<:channel>)
Description Send commands over the facilities data link (FDL) on a T1 interface to initiate or
terminate a far-end payload loopback using either an ANSI or Bellcore FDL
command code. If the far end of the connection is in C-bit parity mode and has
been configured to accept payload loopback requests from the near end, the far end
executes the request.See the ANSI T1.107 specification for more details.
Output Fields To display the state and the number of times the interface has placed itself into
remote loopback, use the show interfaces extensive command.
Description Have the interface transmit the word sequence for the line loopback activate code
on its far-end alarm and control (FEAC) channel. If the far end of the connection is
in C-bit parity mode and has been configured to accept remote loopback requests
from the near end, the far end places its interface into remote loopback.See the
ANSI T1.107 specification for more details.
NOTE: This command is not supported for T3 interfaces configured on DS3 and
Channelized OC12 PICs.
Output Fields To display the state and the number of times the interface has placed itself into
remote loopback, use the show interfaces extensive command.
Description Have the interface transmit the line loopback deactivate code word sequence on its
far-end alarm and control (FEAC) channel. If the far end of the connection is in C-bit
parity mode and has been configured to accept remote loopback requests from the
near end, the far end clears remote loopback on the interface. See the ANSI T1.107
specification for more details.
NOTE: This command is not supported for T3 interfaces configured on DS3 and
Channelized OC12 PICs.
Output Fields To display the state and the number of times the interface has placed itself into
remote loopback, use the show interfaces extensive command.
Syntax test interface inband-line-loop (ansi (initiate | terminate) | bellcore (initiate | terminate)
t1-fpc/pic/port<:channel>
Output Fields To display the state and the number of times the interface has placed itself into
remote loopback, use the show interfaces extensive command.
Additional information See the ANSI T1.107 specification for more details.
Output Fields To display the state and the number of times the interface has placed itself into
remote loopback, use the show interfaces extensive command.
Output Fields Use the show interfaces extensive fe-fpc/pic/port or show interfaces extensive
ge-fpc/pic/port to see the state for auto-negotiation.
Additional Information Before starting a BERT, you must disable the interface. To do so, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT
on only one interface per PIC at a time.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Additional Information To display the results of the BERT, use the show interfaces extensive command.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Additional Information Before starting a BERT, you must disable the interface. To do this, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT
on only one interface per PIC at a time. To display the results of the BERT, use the
show interfaces extensive command.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Additional Information To display the results of the BERT, use the show interfaces extensive command.
Output Fields To display the results of the BERT, use the show interfaces extensive command.
Table 7 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot real-time performance monitoring (RPM). Commands are
listed in alphabetical order.
Task Command
Show configured probe servers. show services rpm active-servers on page 42
Show the results of the last 50 completed probes show services rpm history-results on page 43
for each RPM instance.
Show probe results. show services rpm probe-results on page 46
NOTE: For information about how to configure RPM, see the JUNOS Services
Interfaces Configuration Guide.
! 41
JUNOS 8.1 System Basics and Services Command Reference
Description Display the protocols and corresponding ports for which a router is configured as a
real-time performance monitoring (RPM) server.
Output Fields Table 8 lists the output fields for the show services rpm active-servers command.
Output fields are listed in the approximate order in which they appear.
Description Display standard information about the results of the last 50 probes for each
real-time performance monitoring (RPM) instance.
Options none—Display the results of the last 50 probes for all RPM instances.
since time—(Optional) Display information from the specified time. Specify time as
yyyy-mm-dd.hh:mm:ss.
Output Fields Table 9 lists the output fields for the show services rpm history-results command.
Output fields are listed in the approximate order in which they appear.
Description Display the results of the most recent real-time performance monitoring (RPM)
probes.
Output Fields Table 10 lists the output fields for the show services rpm probe-results command.
Output fields are listed in the approximate order in which they appear.
Results over current test Probes are grouped into tests, and the statistics are calculated for
each test. If a test contains 10 probes, the average, minimum, and
maximum results are calculated from the results of those 10 probes.
If the command is issued while the test is in progress, the statistics
use information from the completed probes.
! Probes sent—Number of probes sent within the current test.
! Probes received—Number of probe responses received within the
current test.
! Loss percentage—Percentage of lost probes for the current test.
! Measurement—Increment of measurement. Possible values are
round-trip time delay and, for the probe type
icmp-ping-timestamp, the egress delay and ingress delay.
! Minimum—Minimum RTT, ingress delay, or egress delay
measured over the course of the current test.
! Maximum—Maximum RTT, ingress delay, or egress delay
measured over the course of the current test.
! Average—Average RTT, ingress delay, or egress delay measured
over the course of the current test.
! Jitter—Jitter in microseconds.
! Stddev—Standard deviation in microseconds.
Results over all tests Displays statistics made for all the probes, independently of the
grouping into tests, as well as statistics for the current test.
! Probes sent—Number of probes sent in all tests.
! Probes received—Number of probe responses received in all tests.
! Loss percentage—Percentage of lost probes in all tests.
! Measurement—Increment of measurement. Possible values are
round-trip time delay and, for the probe types
icmp-ping-timestamp and udp-ping-timestamp, the egress delay and
ingress delay.
! Minimum—Minimum RTT, ingress delay, or egress delay
measured over the course of the current test.
! Maximum—Maximum RTT, ingress delay, or egress delay
measured over the course of the current test.
! Average—Average RTT, ingress delay, or egress delay measured
over the course of the current test.
! Jitter—Jitter in microseconds.
! Stddev—Standard deviation in microseconds.
Table 11 summarizes the command-line interface (CLI) commands you can use to
monitor files, interfaces, and traffic in real time. Commands are listed in
alphabetical order.
Task Command
Monitor statistics for a physical interface. monitor interface on page 52
Monitor a Resource Reservation Protocol (RSVP) label-switched path (LSP). monitor label-switched-path on page 56
Display the status of monitored log and trace files. monitor list on page 59
Start displaying the system log or trace file and additional entries being added to monitor start on page 60
those files.
Stop displaying the system log or trace file. monitor stop on page 61
Monitor packet headers transmitted through network interfaces sent from or monitor traffic on page 62
received by the Routing Engine.
Display trace information about an IP multicast path. mtrace on page 67
Display trace information about a IP multicast path from a source to the router. mtrace from-source on page 68
Listen passively for IP multicast responses. mtrace monitor on page 71
Display trace information about an IP multicast path from the router to a mtrace to-gateway on page 72
gateway router.
Determine the route to a network system. traceroute on page 74
NOTE: For information about how to configure interface parameters, see the
JUNOS Network Interfaces Configuration Guide.
For information about how to configure IP multicast parameters, see the JUNOS
Multicast Protocols Configuration Guide.
! 51
JUNOS 8.1 System Basics and Services Command Reference
monitor interface
Description Display real-time statistics about interfaces, updating the statistics every second.
Check for and display common interface failures, such as SONET/SDH and T3
alarms, loopbacks detected, and increases in framing errors.
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.
Table 12: 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.
52 ! monitor interface
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
To control the output of the monitor interface traffic command while it is running,
use the keys listed in Table 13. The keys are not case-sensitive.
Table 13: Output Control Keys for the monitor interface traffic Command
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—in bps and pps—instead of the Delta column.
Output Fields Table 14 describes the output fields for the monitor interface command. Output
fields are listed in the approximate order in which they appear.
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
Current delta Cumulative number for the counter in question since the time shown in the All levels
Seconds field, which is the time since you started the command or last cleared
the counters.
Statistics For an explanation of the interface statistics, see the description of the All levels
show interfaces extensive command for a particular interface type in the JUNOS
Interfaces Command Reference.
Description With the traffic option, displays the interface description configured at the detail
[edit interfaces interface-name] hierarchy level.
monitor interface ! 53
JUNOS 8.1 System Basics and Services Command Reference
54 ! monitor interface
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
monitor interface ! 55
JUNOS 8.1 System Basics and Services Command Reference
monitor label-switched-path
Description Display the real-time status of the specified Resource Reservation Protocol (RSVP)
label-switched path (LSP).
Additional information You can track the amount of traffic traversing an RSVP LSP and observe its essential
parameters, such as uptime, ingress and egress addresses, labels, routes, and ports.
Values are typically sampled every second. The display also allows you to scroll to
other currently running LSPs. You cannot use this command to display information
about static LSPs or Label Distribution Protocol (LDP)-signaled LSPs.
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. To
control the output of the monitor label-switched-path command while it is running,
use the keys listed in Table 15. The keys are not case-sensitive.
Table 15: Output Control Keys for the monitor mpls Command
Key Action
c Clears the screen and refreshes the display for this LSP.
f Freezes the display, preventing new information from being displayed.
l Monitors a different LSP. After you type l, you can type the new LSP name.
n Displays information about the next LSP (whose name is alphabetically higher than
the current LSP name) configured on the router.
p Goes to the previous LSP (whose name is alphabetically lower than the current LSP
name) configured on the router.
q or Esc Quits the command and returns to the command prompt.
t Thaws, or restarts, the data display for this LSP.
56 ! monitor label-switched-path
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
Output Fields Table 16 describes the output fields for the monitor label-switched-path command.
Output fields are listed in the approximate order in which they appear.
(6) Port number—The port number for the sending router, the port number for the
receiving router, and the protocol ID. For Multiprotocol Label Switching (MPLS)
traffic engineering applications, the protocol ID is always 0.
(7/8) Record route—All intermediate and egress router addresses for this LSP.
(9/10/11) Displays traffic statistics:
! Output packets—Number of packets that have traversed this LSP, and the
change (delta) in the number since the last sample, typically 1 second ago.
! Output bytes—Number of bytes that have traversed this LSP, and the change
(delta) in the number since the last sample, typically 1 second ago.
(12) Displays any errors the router encountered while attempting to retrieve
information on the LSP.
(13) Lists the keyboard commands you can use to navigate to other LSPs. For a
description of the keyboard commands, see Table 15 on page 56.
monitor label-switched-path ! 57
JUNOS 8.1 System Basics and Services Command Reference
58 ! monitor label-switched-path
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
monitor list
Additional Information 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.
Output Fields Table 17 describes the output fields for the monitor list command. Output fields are
listed in the approximate order in which they appear.
monitor list ! 59
JUNOS 8.1 System Basics and Services Command Reference
monitor start
Description Start displaying the system log or trace file and additional entries being added to
those files.
Additional Information 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.
Output Fields Table 18 describes the output fields for the monitor start command. Output fields
are listed in the approximate order in which they appear.
60 ! monitor start
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
monitor stop
Additional Information 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.
monitor stop ! 61
JUNOS 8.1 System Basics and Services Command Reference
monitor traffic
Description Display packet headers transmitted through network interfaces sent from or
received by the Routing Engine.
NOTE: Using the monitor traffic command can degrade router performance. Not
including options, such as count or a matching expression, can slow packet
throughput on your router.
Options none—(Optional) Display all packet headers transmitted through all network
interfaces sent from or received by the Routing Engine.
62 ! monitor traffic
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
size size—(Optional) Receive the specified number of bytes for each packet. The
default size is 68 bytes and is adequate for capturing IP, ICMP, UDP, and TCP
packet data. The monitor traffic command truncates displayed packets if the
matched data exceeds the configured size.
Additional Information In the monitor traffic command, you can specify an expression to match by using
the matching option and including the expression in quotation marks:
Replace expression with one or more of the match conditions listed in Table 19.
monitor traffic ! 63
JUNOS 8.1 System Basics and Services Command Reference
Logical Operator
(Highest to Lowest
Precedence) Description
! Logical NOT. If the first condition does not match, the next condition is
evaluated.
&& Logical AND. If the first condition matches, the next condition is
evaluated. If the first condition does not match, the next condition is
skipped.
|| Logical OR. If the first condition matches, the next condition is skipped.
If the first condition does not match, the next condition is evaluated.
() Group operators to override default precedence order. Parentheses are
special characters, each of which must be preceded by a backslash (\).
64 ! monitor traffic
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
The optional size field represents the number of bytes examined in the packet
header. The available values are 1, 2, or 4 bytes.
To specify match conditions that have a numeric value, use the arithmetic and
relational operators listed in Table 21.
NOTE: Because the Packet Forwarding Engine removes Layer 2 header information
before sending packets to the Routing Engine, the monitor traffic command cannot
apply match conditions to inbound traffic.
Table 21: Arithmetic and Relational Operators for the monitor traffic Command
Arithmetic or
Relational
Operator Description
Arithmetic Operator
+ Addition operator.
- Subtraction operator.
/ Division operator.
& Bitwise AND.
* Bitwise exclusive OR.
| Bitwise inclusive OR.
Relational Operator (Highest to Lowest Precedence)
<= If the first expression is less than or equal to the second, the packet
matches.
>= If the first expression is greater than or equal to the second, the packet
matches.
< If the first expression is less than the second, the packet matches.
> If the first expression is greater than the second, the packet matches.
= If the compared expressions are equal, the packet matches.
!= If the compared expressions are unequal, the packet matches.
monitor traffic ! 65
JUNOS 8.1 System Basics and Services Command Reference
Output Fields When you enter this command, you are provided feedback on the status of your
request.
66 ! monitor traffic
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
mtrace
Additional Information 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.
Output Fields Table 22 describes the output fields for the mtrace command. Output fields are
listed in the approximate order in which they appear.
mtrace ! 67
JUNOS 8.1 System Basics and Services Command Reference
mtrace from-source
Description Display trace information about an IP multicast path from a source to this router. If
a group address is given, additional information, such as packet rates and losses,
can be gathered.
group group—(Optional) Group address for which to trace the path. The default
group address is 0.0.0.0.
68 ! mtrace from-source
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
ttl ttl—(Optional) IP time-to-live (TTL) value. The range of values is 0 through 255.
Local queries to the multicast group use a value of 1. Otherwise, the default
value is 127.
Output Fields Table 23 describes the output fields for the mtrace from-source command. Output
fields are listed in the approximate order in which they appear.
Table 23: mtrace from-source Output Fields
mtrace from-source ! 69
JUNOS 8.1 System Basics and Services Command Reference
70 ! mtrace from-source
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
mtrace monitor
Output Fields Table 24 describes the output fields for the mtrace monitor command. Output fields
are listed in the approximate order in which they appear.
mtrace monitor ! 71
JUNOS 8.1 System Basics and Services Command Reference
mtrace to-gateway
Description Display trace information about a multicast path from this router to a gateway
router.
group group—(Optional) Group address for which to trace the path. The default
group address is 0.0.0.0.
72 ! mtrace to-gateway
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
ttl ttl—(Optional) IP time-to-live value. The range of values is 0 through 255. Local
queries to the multicast group use TTL 1. Otherwise, the default value is 127.
Output Fields Table 25 describes the output fields for the mtrace to-gateway command. Output
fields are listed in the approximate order in which they appear.
mtrace to-gateway ! 73
JUNOS 8.1 System Basics and Services Command Reference
traceroute
Description Display the route packets take to a specified network host. Use traceroute as a
debugging tool to locate points of failure in a network.
tos value—(Optional) Value to include in the IP type-of-service (ToS) field. The range
of values is 0 through 255.
74 ! traceroute
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
Output Fields Table 26 describes the output fields for the traceroute command. Output fields are
listed in the approximate order in which they appear.
traceroute ! 75
JUNOS 8.1 System Basics and Services Command Reference
76 ! traceroute
Chapter 4: Real-Time Router Monitoring Operational Mode Commands
traceroute monitor
Description Displays live monitoring of each hop in the route packets take to a specified
network host. Use traceroute monitor as a debugging tool to locate points of failure
in a network.
size value—Receive the specified number of bytes for each packet. The range is 0
through 65468 bytes. The default value is 64.
Output Fields Table 27 describes the output fields for the traceroute monitor command. Output
fields are listed in the approximate order in which they appear.
traceroute monitor ! 77
JUNOS 8.1 System Basics and Services Command Reference
78 ! traceroute monitor
Part 2
System Management
System Management ! 79
JUNOS 8.1 System Basics and Services Command Reference
80 ! System Management
Chapter 5
Accounting Operational Mode
Commands
Table 28 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot accounting options. Commands are listed in alphabetical
order.
! Interface—Collects error and statistic information for input and output packets
on a particular physical or logical interface.
! Source class usage (SCU) tracks traffic originating from specific prefixes on
the provider core and destined for specific prefixes on the customer edge.
! Destination class usage (DCU) tracks traffic originating from the customer
edge and destined for specific prefixes on the provider core router.
NOTE: For information about configuring accounting profiles, see the JUNOS
Network Management Configuration Guide.
! 81
JUNOS 8.1 System Basics and Services Command Reference
Output Fields Table 29 lists the output fields for the show accounting profile command. Output
fields are listed in the approximate order in which they appear..
Transfer Interval Length of time (in minutes) the file remains open, receiving
statistics before it is closed, transferred, and rotated. When
either the time or the file size is exceeded, the file is closed and
a new one opened, whether or not a transfer site is specified.
Next Scheduled Transfer Time at which the next transfer occurs.
Output Fields Table 30 lists the output fields for the show accounting records command. Output
fields are listed in the approximate order in which they appear..
Table 31 summarizes the command-line interface (CLI) commands you can use to
monitor the router chassis. Commands are listed in alphabetical order.
! 89
JUNOS 8.1 System Basics and Services Command Reference
(T-series routing platform only) Display the state of the switching show chassis fabric topology on page 171
fabric topology for the SIB connection between the TX Matrix
platform and the T640 routing nodes.
(M5 and M10 routers only). Display FEB status information. show chassis feb on page 175
Display the version levels of the firmware running on the SCB, SFM, show chassis firmware on page 176
SSB, FEB, and FPCs.
90 !
Chapter 6: Chassis Operational Mode Commands
! 91
JUNOS 8.1 System Basics and Services Command Reference
Description (M40e, M160, and M320 routers and the T-series routing platform only) Clear or
stop a text message on the craft interface display, which is on the front of the router.
The craft interface alternates the display of text messages with standard craft
interface messages, switching between messages every 2 seconds. By default, the
text message is displayed for 5 minutes. The craft interface display has four
20-character lines.
Output Fields See show chassis craft-interface on page 117 for an explanation of output fields.
clear chassis display The following example displays and then clears the text message on the craft
message interface display:
request chassis cb
Description (M320 routers and T-series routing platforms only) Control the operation of the
Control Board (CB).
! Routing Matrix only—If you specify the number of the T640 routing node
by using the lcc number option (the recommended method), replace
slot-number with a value from 0 through 7. Otherwise, replace slot-number
with a value from 0 through 31. For example, the following commands
have the same result:
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request chassis cb ! 93
JUNOS 8.1 System Basics and Services Command Reference
Description (M7i and M10i routers only) Control the operation of the Compact Forwarding
Engine Board (CFEB).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M20, M40, M40e, M160, and M320 routers, and T-series routing platform only)
Control the operation of the Flexible PIC Concentrator (FPC).
! Routing matrix only—If you specify the number of the T640 routing node
by using the lcc number option (the recommended method), replace
slot-number with a value from 0 through 7. Otherwise, replace slot-number
with a value from 0 through 31. For example, the following commands
have the same result:
lcc number—(Routing matrix only) (Optional) Control the FPC in a specified T640
routing node that is connected to a TX Matrix platform. Replace number with a
value from 0 through 3.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers, and T-series routing platform only) Resynchronize
the Front Panel Module (FPM) craft interface status.
Options lcc number—(Routing matrix only) Resynchronize the craft interface status on a
specified T640 routing node that is connected to a TX Matrix platform. Replace
number with a value from 0 through 3.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Routing matrix only) Control the operation of a T640 routing node
(or line-card chassis) that is connected to a TX matrix platform.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e and M160 routers only) Control the operation of the Miscellaneous Control
Subsystem (MCS).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e and M160 routers) Control the operation of the Packet Forwarding Engine
(PFE) clock generator (PCG).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Syntax request chassis pic (offline | online) fpc-slot slot-number pic-slot slot-number
Syntax request chassis pic (offline | online) fpc-slot slot-number pic-slot slot-number
(Routing Matrix) <lcc number>
! M40, M40e, M160, M320, T320 routers, and T640 nodes—0 through 7.
! Routing matrix only—If you specify the number of the T640 routing node
by using the lcc number option (the recommended method), replace
slot-number with a value from 0 through 7. Otherwise, replace slot-number
with a value from 0 through 31. For example, the following commands
have the same result:
pic-slot slot-number—PIC slot number. For the M-series routing platform, the T640
routing node, and the routing matrix, it can be 0, 1, 2, or 3. For the T320 router,
it can be 0 or 1.
lcc number—(Routing matrix only) (Optional) Control the PIC in a specified T640
routing node that is connected to a TX Matrix platform. Replace number with a
value from 0 through 3.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request chassis pic user@host> request chassis pic pic-slot 0 online fpc-slot 0
FPC 0, PIC 0 is already online
Description For routers with multiple Routing Engines, control which Routing Engine is the
master.
CAUTION: (Routing matrix only) Within the routing matrix, we recommend that all
Routing Engines run the same JUNOS software release. If you run different JUNOS
releases on the Routing Engines and a change in mastership occurs on any backup
Routing Engine in the routing matrix, one or all T640 routing nodes might become
logically disconnected from the TX Matrix platform and cause data loss. For more
information, see the TX Matrix Platform Hardware Guide or the JUNOS System
Basics Configuration Guide.
lcc number—(Routing matrix only) T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
all-chassis—(Routing matrix only) Available only with the switch option. Switch
mastership on all Routing Engines in a TX Matrix platform.
force—(Optional) Available only with the acquire option. Force the change to a new
master Routing Engine.
Additional Information
NOTE: 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
Physical Interface Cards (PICs). Interior Gateway Protocol (IGP) and Border
Gateway Protocol (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 System Basics Configuration
Guide.
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.
If you configure both Routing Engines as masters, when the chassis software
restarts for any reason, the Routing Engine in slot 0 becomes the master and the
one in slot 1 becomes the backup.
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.
When both Routing Engines are configured as master or when both are configured
as backup, and both Routing Engines become operational at the same time, the
Routing Engine in slot 0 becomes the master.
List of Sample Output request chassis routing-engine master acquire on page 102
request chassis routing-engine master switch on page 103
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Resolving mastership...
Complete. The other Routing Engine becomes the master.
Resolving mastership...
Complete. The local routing engine becomes the master.
Syntax request chassis scg lcc number (offline | online) slot slot-number
(Routing Matrix)
Description (T-series routing platform only) Control the operation of the specified SONET Clock
Generator (SCG).
Options lcc number—(Routing matrix only) Change the SCG status on a specified T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
offline—Take the SCG offline. When you change the SCG status to offline, the unit is
not powered down.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e and M160 routers only) Control the operation of the specified Switching and
Forwarding Module (SFM).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e and M160 routers only) Control which Switching and Forwarding Module
(SFM) is master.
Additional Information By default, the SFM in slot 0 (SFM0) is the master and the SFM in slot 1 (SFM1) is
the backup. 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. To change
the default master SFM, include the sfm statement at the [edit chassis redundancy]
hierarchy level in the configuration. For more information, see the JUNOS System
Basics Configuration Guide.
All installed SFMs are always working together to forward packets. If an SFM fails,
the other SFMs take over and traffic continues to flow uninterrupted.
List of Sample Output request chassis sfm master switch on page 106
request chassis sfm master switch no-confirm on page 106
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request chassis sfm user@host> request chassis sfm master switch no-confirm
master switch Switch initiated, use “show chassis sfm” to verify
no-confirm
Syntax request chassis sib (all-chassis | lcc number | scc) (offline | online) slot slot-number
(Routing Matrix) (start-receiver number | stop-receiver number)
Description (M320 routers and T-series routing platform only) Control the operation of the
specified Switch Interface Board (SIB).
Options all-chassis—(Routing matrix only) Controls the operation of the SIB in the specified
slot on the TX Matrix platform and on all T640 routing nodes.
lcc number—(Routing matrix only) T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
slot slot-number—SIB slot number. For the T640 routing node and a routing matrix,
replace slot-number with a value from 0 through 4. For the T320 router, replace
slot-number with a value from 0 through 2.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Syntax request chassis spmb restart (lcc number | scc) slot slot-number
(Routing Matrix)
Description (T-series routing platform only) Restart the specified Switch Processor Mezzanine
Board (SPMB) on the Control Board (CB).
Options lcc number—(Routing matrix only) T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M20 router only) Control which System and Switch Board (SSB) is master.
Additional Information By default, the SSB in slot 0 (SSB0) is the master and the SSB in slot 1 (SSB1) is the
backup. 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. To change the
default master SSB, include the ssb statement at the [edit chassis redundancy]
hierarchy level in the configuration. For more information, see the JUNOS System
Basics Configuration Guide.
The configurations on the two SSBs do not have to be the same, and they are not
automatically synchronized. If you configure both SSBs as masters, when the
chassis software restarts for any reason, the SSB in slot 0 becomes the master and
the one in slot 1 becomes the backup.
The switchover from the primary SSB to the backup SSB is immediate. The SSB
takes several seconds to reinitialize the Flexible PIC Concentrators (FPCs) and
restart the Physical Interface Cards (PICs). The Interior Gateway Protocol (IGP) and
Border Gateway Protocol (BGP) convergence times depend on the specific network
environment.
List of Sample Output request chassis ssb master switch on page 109
request chassis ssb master switch no-confirm on page 109
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request chassis ssb user@host> request chassis ssb master switch no-confirm
master switch Switch initiated, use “show chassis ssb” to verify
no-confirm
Description (M320 routers only) Change the external clock source used for chassis
synchronization.
List of Sample Output request chassis synchronization switch external-a on page 110
Output Fields When you enter this command, you are provided feedback on the status of your
request. Not configured indicates that the source is not configured. Present indicates
that the source is configured and present. Qualified indicates that the source is being
used for synchronization.
Description Display or stop a text message on the craft interface display, which is on the front of
the router. The craft interface alternates the display of text messages with standard
craft interface messages, switching between messages every 2 seconds. By default,
the text message is displayed for 5 minutes. The craft interface display has four
20-character lines.
lcc number—(Routing matrix only) Display the text message on the craft interface
display of a specified T640 routing node (or line-card chassis) that is connected
to a TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) Display the text message on the craft interface display
of the TX Matrix platform (or switch-card chassis).
List of Sample Output set chassis display message (Creating) on page 112
set chassis display message (Deleting) on page 112
Output Fields See the show chassis craft-interface on page 117 for an explanation of output fields.
set chassis display The following example shows how to set the display message and verify the result:
message (Creating)
user@host> set chassis display message “NOC contact Dusty (888) 555-1234”
message sent
set chassis display The following example shows how to delete the display message and verify that the
message (Deleting) message is removed:
Description Display information about the conditions that have been configured to trigger
alarms.
Options none—(Routing matrix only) Display information about the conditions that have
been configured to trigger alarms on the TX Matrix platform and its attached
T640 routing nodes.
Additional Information 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 in a manner that we do not recommend.
You can manually silence external devices connected to the alarm relay contacts by
pressing the alarm cutoff button, located on the craft interface. Silencing the device
does not remove the alarm messages from the display (if present on the router) or
extinguish the alarm LEDs. In addition, new alarms that occur after you silence an
external device reactivate the external device.
List of Sample Output show chassis alarms (Alarms Active) on page 114
show chassis alarms (No Alarms Active) on page 114
show chassis alarms (Alarms Active on a Routing Matrix) on page 114
show chassis alarms (Backup Routing Engine) on page 114
Output Fields Table 32 lists the output fields for the show chassis alarms command. Output fields
are listed in the approximate order in which they appear.
Table 32: show chassis alarms
lcc2-re0:
--------------------------------------------------------------------------
5 alarms currently active
Alarm time Class Description
2004-08-05 18:43:35 PDT Minor SIB 3 Not Online
2004-08-05 18:43:33 PDT Major SIB 2 Absent
2004-08-05 18:43:33 PDT Major SIB 1 Absent
2004-08-05 18:43:33 PDT Major SIB 0 Absent
2004-08-05 18:43:05 PDT Minor PEM 1 Absent
Description (M7i and M10i routers only) Display status information about the Compact
Forwarding Engine Board (CFEB).
Output Fields Table 33 lists the output fields for the show chassis cfeb command. Output fields are
listed in the approximate order in which they appear.
Table 33: show chassis cfeb
Description For routers that have a display on the craft interface, show the messages that are
currently displayed. On all routers, except for the M20, you must enter this
command on the master Routing Engine.
Options none—(Routing matrix only) Show messages that are currently displayed on the
craft interface on the TX Matrix platform and its attached T640 routing nodes.
lcc number—(Routing matrix only) (Optional) Show messages for a specified T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Show messages for the TX Matrix platform
(or switch-card chassis).
Output Fields Table 34 lists the output fields for the show chassis craft-interface command. Output
fields are listed in the approximate order in which they appear.
Table 34: show chassis craft-interface Output Fields
NICs 0 1 2 3 4 5 6 7
-------------------------------
Green * . * . * . * .
Red . . . . . . . .
LCD Screen:
+--------------------+
|host |
|Up: 27+18:52:37 |
| |
|52.649kpps Load |
+--------------------+
CB LEDs:
CB 0 1
--------------
Amber . .
Green * .
Blue * .
SIB LEDs:
SIB 0 1 2 3 4
--------------------------
Fail . . . . .
OK . . . . *
Active . . . . *
lcc0-re0:
--------------------------------------------------------------------------
FPM Display contents:
+--------------------+
|hybrid |
|5 Alarms active |
|R: SIB 2 Absent |
|R: SIB 1 Absent |
+--------------------|
CB LEDs:
CB 0 1
--------------
Amber . .
Green * .
Blue * .
SCG LEDs:
SCG 0 1
--------------
Amber . .
Green * .
Blue * .
SIB LEDs:
SIB 0 1 2 3 4
--------------------------
Red . . . . .
Green . . . . *
lcc2-re0:
--------------------------------------------------------------------------
FPM Display contents:
+--------------------+
|prius |
|5 Alarms active |
|R: SIB 2 Absent |
|R: SIB 1 Absent |
+--------------------|
CB LEDs:
CB 0 1
--------------
Amber . .
Green * .
Blue * .
SCG LEDs:
SCG 0 1
--------------
Amber . .
Green * .
Blue * .
SIB LEDs:
SIB 0 1 2 3 4
--------------------------
Red . . . . .
Green . . . . *
Description Display environmental information about the routing platform chassis, including
the temperature and information about the fans, power supplies, and Routing
Engine.
Output Fields Table 35 lists the output fields for the show chassis environment command. Output
fields are listed in the approximate order in which they appear.
Table 35: show chassis environment Output Fields
lcc0-re0:
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 29 degrees C / 84 degrees F
PEM 1 Absent
SCG 0 OK 35 degrees C / 95 degrees F
SCG 1 Absent
Routing Engine 0 OK 39 degrees C / 102 degrees F
Routing Engine 1 OK 36 degrees C / 96 degrees F
CB 0 OK 32 degrees C / 89 degrees F
CB 1 OK 32 degrees C / 89 degrees F
SIB 0 OK 40 degrees C / 104 degrees F
SIB 0 (B) OK 51 degrees C / 123 degrees F
FPC 0 Top OK 45 degrees C / 113 degrees F
FPC 0 Bottom OK 31 degrees C / 87 degrees F
FPC 1 Top OK 34 degrees C / 93 degrees F
FPC 1 Bottom OK 31 degrees C / 87 degrees F
FPM GBUS OK 30 degrees C / 86 degrees F
FPM Display OK 34 degrees C / 93 degrees F
Fans Top Left Front fan OK Spinning at normal speed
Top Left Middle fan OK Spinning at normal speed
Top Left Rear fan OK Spinning at normal speed
Top Right Front fan OK Spinning at normal speed
Top Right Middle fan OK Spinning at normal speed
Top Right Rear fan OK Spinning at normal speed
Bottom Left Front fan OK Spinning at normal speed
Bottom Left Middle fan OK Spinning at normal speed
Bottom Left Rear fan OK Spinning at normal speed
Bottom Right Front fan OK Spinning at normal speed
Bottom Right Middle fan OK Spinning at normal speed
Bottom Right Rear fan OK Spinning at normal speed
Rear Tray Top fan OK Spinning at normal speed
Rear Tray Second fan OK Spinning at normal speed
Rear Tray Third fan OK Spinning at normal speed
Rear Tray Fourth fan OK Spinning at normal speed
Rear Tray Fifth fan OK Spinning at normal speed
Rear Tray Sixth fan OK Spinning at normal speed
Rear Tray Seventh fan OK Spinning at normal speed
Rear Tray Bottom fan OK Spinning at normal speed
Misc CIP OK
SPMB 0 OK
SPMB 1 OK
lcc2-re0:
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 29 degrees C / 84 degrees F
PEM 1 Absent
SCG 0 OK 32 degrees C / 89 degrees F
SCG 1 Absent
Routing Engine 0 OK 31 degrees C / 87 degrees F
Routing Engine 1 OK 32 degrees C / 89 degrees F
CB 0 OK 30 degrees C / 86 degrees F
SIB 0 OK 38 degrees C / 100 degrees F
SIB 0 (B) OK 49 degrees C / 120 degrees F
FPC 0 Top OK 45 degrees C / 113 degrees F
FPC 0 Bottom OK 33 degrees C / 91 degrees F
FPC 1 Top OK 37 degrees C / 98 degrees F
FPC 1 Bottom OK 33 degrees C / 91 degrees F
FPM GBUS OK 30 degrees C / 86 degrees F
FPM Display OK 34 degrees C / 93 degrees F
Fans Top Left Front fan OK Spinning at normal speed
Top Left Middle fan OK Spinning at normal speed
...
Description (M320 routers and T-series routing platform only) Display environmental
information about the Control Boards (CBs).
Options none—Display environmental information about all CBs. For the routing matrix
only, display environmental information about all CBs on the TX Matrix
platform and its attached T640 routing nodes.
Output Fields Table 36 lists the output fields for the show chassis environment cb command.
Output fields are listed in the approximate order in which they appear.
Table 36: show chassis environment cb Output Fields
Field Name Field Description
State Status of the CB: Online or Offline. If two CBs are installed and online, one is
functioning as the master, and the other is the standby.
Temperature Temperature of the air flowing past the CB.
Power Power required and measured on the CB. The left column displays the
required power, in volts. The right column displays the measured power, in
millivolts.
BUS Revision Revision level of the generic bus device.
FPGA Revision Revision level of the field-programmable gate array (FPGA)
lcc0-re0:
--------------------------------------------------------------------------
CB 0 status:
State Online Master
Temperature 32 degrees C / 89 degrees F
Power:
1.8 V 1787 mV
2.5 V 2473 mV
3.3 V 3306 mV
4.6 V 4793 mV
5.0 V 5025 mV
12.0 V 12156 mV
lcc2-re0:
--------------------------------------------------------------------------
CB 0 status:
State Online Master
...
CB 1 status:
State Online Standby
...
Description (M40e, M160, and M320 routers, and T-series routing platform only) Display about
Flexible PIC Concentrator (FPC) environmental information.
Options none—Display environmental information about all FPCs. For the routing matrix
only, display environmental information about all FPCs on the TX Matrix
platform and its attached T640 routing nodes.
! Routing matrix only—If you specify the number of the T640 routing node
by using the lcc number option (the recommended method), replace slot
with a value from 0 through 7. Otherwise, replace slot with a value from
0 through 31. For example, the following commands have the same result:
List of Sample Output show chassis environment fpc (M160) on page 135
show chassis environment fpc (M320) on page 135
show chassis environment fpc (T-series) on page 136
show chassis environment fpc lcc (Routing Matrix) on page 137
Output Fields Table 37 lists the output fields for the show chassis environment fpc command.
Output fields are listed in the approximate order in which they appear.
Table 37: show chassis environment fpc Output Fields
FPC 2 status:
State Online
Temperature Top 43 degrees C / 109 degrees F
Temperature Bottom 39 degrees C / 102 degrees F
Temperature MMB1 41 degrees C / 105 degrees F
Power:
1.8 V 1963 mV
2.5 V 2503 mV
3.3 V 3340 mV
5.0 V 5042 mV
1.8 V bias 1797 mV
3.3 V bias 3311 mV
5.0 V bias 5013 mV
8.0 V bias 7221 mV
BUS Revision 40
Description (M40e, M160, and M320 routers, and T-series routing platform only) Display
environmental information about the front panel module in the router.
Options none—(Routing matrix only) Display environmental information about the front
panel modules (craft interfaces) on the TX Matrix platform and its attached
T640 routing nodes.
List of Sample Output show chassis environment fpm (M40e and M160) on page 139
show chassis environment fpm (M320) on page 139
show chassis environment fpm (T-series) on page 139
show chassis environment fpm lcc (Routing Matrix) on page 140
show chassis environment fpm scc (Routing Matrix) on page 140
Output Fields Table 38 lists the output fields for the show chassis environment fpm command.
Output fields are listed in the approximate order in which they appear.
Table 38: show chassis environment fpm Output Fields
Description (M40e and M160 routers only) Display environmental information about the
Miscellaneous Control Subsystems (MCSs).
List of Sample Output show chassis environment mcs (M40e) on page 141
show chassis environment mcs (M160) on page 142
Output Fields Table 39 lists the output fields for the show chassis environment mcs command.
Output fields are listed in the approximate order in which they appear.
Table 39: show chassis environment mcs Output Fields
BUS Revision 12
FPGA Revision 13
Description (M40e and M160 routers only) Display environmental information about the Packet
Forwarding Engine clock generators (PCGs).
List of Sample Output show chassis environment pcg (M40e) on page 143
show chassis environment pcg (M160) on page 144
Output Fields Table 40 lists the output fields for the show chassis environment pcg command.
Output fields are listed in the approximate order in which they appear.
Table 40: show chassis environment pcg Output Fields
Power:
3.3 V 3271 mV
5.0 V bias 4979 mV
8.0 V bias 8117 mV
BUS Revision 12
Description (M40e, M160, and M320 routers, and T-series routing platform only) Display Power
Entry Module (PEM) environmental status information.
Options none—Display environmental information about both PEMs. For the routing matrix
only, display environmental information about the PEMs, the TX Matrix
platform, and its attached T640 routing nodes.
List of Sample Output show chassis environment pem (M40e) on page 146
show chassis environment pem (M160) on page 146
show chassis environment pem (M320) on page 146
show chassis environment pem (T320) on page 146
show chassis environment pem (T640) on page 147
show chassis environment pem lcc (Routing Matrix) on page 147
show chassis environment pem scc (Routing Matrix) on page 147
Output Fields Table 41 lists the output fields for the show chassis environment pem command.
Output fields are listed in the approximate order in which they appear.
Table 41: show chassis environment pem Output Fields
Options none—Display environmental information about all Routing Engines. For the
routing matrix only, display environmental information about all Routing
Engines on the TX Matrix platform and its attached T640 routing nodes.
List of Sample Output show chassis environment routing-engine (Nonredundant) on page 148
show chassis environment routing-engine (Redundant) on page 149
Output Fields Table 42 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 42: show chassis environment routing-engine Output Fields
Options none—Display environmental information about all SCGs. For the routing matrix
only, display environmental information about all SCGs on the TX Matrix
platform and its attached T640 routing nodes.
List of Sample Output show chassis environment scg (T-series) on page 151
show chassis environment scg lcc (Routing Matrix) on page 151
Output Fields Table 43 lists the output fields for the show chassis environment scg command.
Output fields are listed in the approximate order in which they appear.
Table 43: show chassis environment scg Output Fields
Description (M40e and M160 routers only) Display Switching and Forwarding Module (SFM)
environmental information.
List of Sample Output show chassis environment sfm (M40e) on page 153
show chassis environment sfm (M160) on page 153
Output Fields Table 44 lists the output fields for the show chassis environment sfm command.
Output fields are listed in the approximate order in which they appear.
Table 44: show chassis environment sfm Output Fields
SPP Power:
1.5 V 1499 mV
2.5 V 2466 mV
3.3 V 3274 mV
5.0 V 5025 mV
5.0 V bias 4984 mV
SPR Power:
1.5 V 1496 mV
2.5 V 2470 mV
3.3 V 3279 mV
5.0 V 5020 mV
5.0 V bias 4993 mV
8.0 V bias 8222 mV
CMB Revision 12
SFM 2 status:
State Online
SPP temperature 50 degrees C / 122 degrees F
SPR temperature 52 degrees C / 125 degrees F
SPP Power:
1.5 V 1504 mV
2.5 V 2471 mV
3.3 V 3294 mV
5.0 V 5045 mV
5.0 V bias 4981 mV
SPR Power:
1.5 V 1496 mV
2.5 V 2470 mV
3.3 V 3293 mV
5.0 V 5028 mV
5.0 V bias 4971 mV
8.0 V bias 8214 mV
CMB Revision 12
SFM 3 status:
State Online
SPP temperature 49 degrees C / 120 degrees F
SPR temperature 48 degrees C / 118 degrees F
SPP Power:
1.5 V 1505 mV
2.5 V 2484 mV
3.3 V 3296 mV
5.0 V 5040 mV
5.0 V bias 4984 mV
SPR Power:
1.5 V 1503 mV
2.5 V 2488 mV
3.3 V 3302 mV
5.0 V 5037 mV
5.0 V bias 4993 mV
8.0 V bias 8249 mV
CMB Revision 12
Description (M320 routers and T-series routing platform only) Display Switch Interface Boards
(SIB) environmental information.
Options none—Display environmental information about all SIBs. For the routing matrix
only, display environmental information about all SIBs on the TX Matrix
platform and its attached T640 routing nodes.
slot—(Optional) Display environmental information about the specified SIB. For the
M320 router, replace slot with a value from 0 through 3. For the T640 routing
node and routing matrix, replace slot with a value from 0 through 4. For the
T320 router, replace slot with a value from 0 through 2.
List of Sample Output show chassis environment sib (M320) on page 156
show chassis environment sib 1 (T640) on page 157
show chassis environment sib scc (Routing Matrix) on page 157
Output Fields Table 45 lists the output fields for the show chassis environment sib command.
Output fields are listed in the approximate order in which they appear.
Table 45: show chassis environment sib Output Fields
State Status of the SIB: Online, Offline, or Spare (T640 routing node only).
Only four of the five T640 router SIBs are active at any time. The
fifth one is marked Spare. It is activated if there is a fault on one of
the active SIBs.
Temperature Temperature of the air flowing past the SIB.
Power Information about the voltage supplied to the SIB. The left column
displays the required power, in volts. The right column displays the
measured power, in millivolts.
SIB 3 status:
State Online
Temperature 37 degrees C / 98 degrees F
Power:
GROUND 0 mV
1.8 V 1798 mV
2.5 V 2481 mV
3.3 V 3328 mV
1.8 V bias 1792 mV
3.3 V bias 3313 mV
5.0 V bias 5013 mV
8.0 V bias 7467 mV
Description (M10i, M40e, M160, and M320 routers, and T-series routing platform only) Display
information about the ports on the Control Board (CB) Ethernet switch.
Options none—Display information about each connected port on the Ethernet switch. For
the routing matrix only, display information about each connected port on the
Ethernet switch on the TX Matrix platform and its attached T640 routing nodes.
errors port—(Optional) Display the numbers and types of errors accumulated on the
specified port (0 through 15) of the Ethernet switch.
statistics port—(Optional) Display traffic statistics for the specified port on the
Ethernet switch.
lcc number—(Routing matrix only) (Optional) Display information about the ports
on the CB’s Ethernet switch on a specified T640 routing node
(or line-card chassis) that is connected to a TX Matrix platform. Replace number
with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display information about the ports on the
CB’s Ethernet switch on the TX Matrix platform (or switch-card chassis).
Output Fields Table 46 lists the output fields for the show chassis ethernet-switch command.
Output fields are listed in the approximate order in which they appear.
Table 46: show chassis ethernet-switch Output Fields
lcc2-re0:
--------------------------------------------------------------------------
Link is good on FE port 0 connected to device: FPC0
Speed is 100Mb
Duplex is full
Autonegotiate is Enabled
Description (M320 routers and T-series routing platform only) Display the state of the electrical
and optical switch fabric links between the Flexible PIC Concentrators (FPCs) and
the Switch Interface Boards (SIBs).
Options none—Display the switch fabric link state. On a TX Matrix platform, display the
switching fabric link states for the FPCs in all T640 routing nodes connected to
a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display the switch fabric link state for
the FPCs in the specified T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
List of Sample Output show chassis fabric fpcs (M320 Router) on page 165
show chassis fabric fpcs (T320 Router) on page 165
show chassis fabric fpcs (T640 Router) on page 166
show chassis fabric fpcs (Routing Matrix) on page 167
Output Fields Table 47 lists the output fields for the show chassis fabric fpcs command. Output
fields are listed in the approximate order in which they appear.
Table 47: show chassis fabric fpcs Output Fields
...
FPC #7
PFE #1
SIB #0 Links ok
SIB #1 Plane enabled
SIB #2 Plane enabled
SIB #3 Plane enabled
SIB #4 Plane enabled
...
lcc2-re0:
--------------------------------------------------------------------------
Fabric management FPC state:
FPC #0
PFE #1
SIB #4 Links ok
FPC #1
PFE #1
SIB #4 Links ok
FPC #2
PFE #0
SIB #4 Links ok
PFE #1
SIB #4 Links ok
FPC #4
PFE #0
SIB #4 Links ok
PFE #1
SIB #4 Links ok
FPC #5
PFE #1
SIB #4 Links ok
Description (T-series routing platform only) Display the state of the electrical and optical switch
fabric links:
! Between the Switch Interface Boards (SIBs) in the TX Matrix platform (TX SIBs)
and the SIBs in the T640 routing nodes (T640 SIBs).
! Between the T640 SIBs and the Flexible PIC Concentrators (FPCs) in a T640
routing node.
Options none—Display the switching fabric link state for the TX SIBs in the TX Matrix
platform and for the T640 SIBs in all the T640 routing nodes connected to a
TX Matrix platform.
lcc number—(Optional) Display the switching fabric link state for the T640 SIBs in a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Optional) Display the switching fabric link state for the TX SIBs on the
TX Matrix platform (or switch-card chassis).
Output Fields Table 48 lists the output fields for the show chassis fabric sibs command. Output
fields are listed in the approximate order in which they appear.
Table 48: show chassis fabric sibs Output Fields
SIB #2
plane state: S_SPARE
LCC #0 : Links ok
LCC #2 : Links ok
SIB #3
plane state: S_ACTIVE
LCC #0 : Unused
LCC #2 : Unused
SIB #4
plane state: S_ACTIVE
LCC #0 : Links ok
LCC #2 : Links ok
lcc0-re0:
--------------------------------------------------------------------------
Fabric management SIB state:
SIB #2
plane state: S_SPARE
FPC #0
PFE #1 : Links ok
FPC #6
PFE #1 : Links ok
SCC : Links ok
SIB #4
plane state: S_ACTIVE
FPC #0
PFE #1 : Links ok
FPC #6
PFE #1 : Links ok
SCC : Links ok
lcc2-re0:
--------------------------------------------------------------------------
Fabric management SIB state:
SIB #2
plane state: S_SPARE
FPC #0
PFE #1 : Links ok
FPC #1
PFE #1 : Links ok
FPC #2
PFE #0 : Links ok
PFE #1 : Links ok
FPC #3
PFE #1 : Links ok
SCC : Links ok
SIB #4
plane state: S_ACTIVE
FPC #0
PFE #1 : Links ok
FPC #1
PFE #1 : Links ok
FPC #2
PFE #0 : Links ok
PFE #1 : Links ok
FPC #3
PFE #1 : Links ok
SCC : Links ok
Description (T-series routing platform only) Display the state of the switching fabric topology for
the Switch Interface Board (SIB) connection between the TX Matrix platform and
the T640 routing nodes.
Options none—Display the fabric topology state for the TX Matrix platform and for all the
T640 routing nodes connected to it.
lcc number—(Optional) Display the fabric topology state for a specified T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
scc—(Optional) Display the fabric topology state for the TX Matrix platform
(or switch-card chassis).
sib-slot-number—(Optional) Display the fabric topology state for a specified SIB slot.
Replace sib-slot-number with a value from 0 through 4.
List of Sample Output show chassis fabric topology scc on page 171
show chassis fabric topology lcc on page 173
Output Fields Table 49 lists the output fields for the show chassis fabric topology command.
Output fields are listed in the approximate order in which they appear.
Table 49: show chassis fabric topology Output Fields
LCC0_SIB-L0_F0,07->SIB-S0_F0,08 UP SIB-S0_F0,08->LCC0_SIB-L0_F1,04 UP
LCC1_SIB-L0_F0,07->SIB-S0_F0,09 UP SIB-S0_F0,09->LCC1_SIB-L0_F1,12 UP
LCC2_SIB-L0_F0,07->SIB-S0_F0,10 RESET SIB-S0_F0,10->LCC2_SIB-L0_F1,12 UP
LCC3_SIB-L0_F0,07->SIB-S0_F0,11 RESET SIB-S0_F0,11->LCC3_SIB-L0_F1,04 UP
LCC0_SIB-L0_F0,06->SIB-S0_F0,12 UP SIB-S0_F0,12->LCC0_SIB-L0_F1,05 UP
LCC1_SIB-L0_F0,06->SIB-S0_F0,13 UP SIB-S0_F0,13->LCC1_SIB-L0_F1,13 UP
LCC2_SIB-L0_F0,06->SIB-S0_F0,14 RESET SIB-S0_F0,14->LCC2_SIB-L0_F1,13 UP
LCC3_SIB-L0_F0,06->SIB-S0_F0,15 RESET SIB-S0_F0,15->LCC3_SIB-L0_F1,05 UP
SIB0_F1 (F2 ):
LCC0_SIB-L0_F0,11->SIB-S0_F1,00 UP SIB-S0_F1,00->LCC0_SIB-L0_F1,08 UP
LCC1_SIB-L0_F0,11->SIB-S0_F1,01 UP SIB-S0_F1,01->LCC1_SIB-L0_F1,00 UP
LCC2_SIB-L0_F0,11->SIB-S0_F1,02 RESET SIB-S0_F1,02->LCC2_SIB-L0_F1,00 UP
LCC3_SIB-L0_F0,11->SIB-S0_F1,03 RESET SIB-S0_F1,03->LCC3_SIB-L0_F1,08 UP
LCC0_SIB-L0_F0,10->SIB-S0_F1,04 UP SIB-S0_F1,04->LCC0_SIB-L0_F1,09 UP
LCC1_SIB-L0_F0,10->SIB-S0_F1,05 UP SIB-S0_F1,05->LCC1_SIB-L0_F1,01 UP
LCC2_SIB-L0_F0,10->SIB-S0_F1,06 RESET SIB-S0_F1,06->LCC2_SIB-L0_F1,01 UP
LCC3_SIB-L0_F0,10->SIB-S0_F1,07 RESET SIB-S0_F1,07->LCC3_SIB-L0_F1,09 UP
LCC0_SIB-L0_F0,15->SIB-S0_F1,08 UP SIB-S0_F1,08->LCC0_SIB-L0_F1,12 UP
LCC1_SIB-L0_F0,15->SIB-S0_F1,09 UP SIB-S0_F1,09->LCC1_SIB-L0_F1,04 UP
LCC2_SIB-L0_F0,15->SIB-S0_F1,10 RESET SIB-S0_F1,10->LCC2_SIB-L0_F1,04 UP
LCC3_SIB-L0_F0,15->SIB-S0_F1,11 RESET SIB-S0_F1,11->LCC3_SIB-L0_F1,12 UP
LCC0_SIB-L0_F0,14->SIB-S0_F1,12 UP SIB-S0_F1,12->LCC0_SIB-L0_F1,13 UP
LCC1_SIB-L0_F0,14->SIB-S0_F1,13 UP SIB-S0_F1,13->LCC1_SIB-L0_F1,05 UP
LCC2_SIB-L0_F0,14->SIB-S0_F1,14 RESET SIB-S0_F1,14->LCC2_SIB-L0_F1,05 UP
LCC3_SIB-L0_F0,14->SIB-S0_F1,15 RESET SIB-S0_F1,15->LCC3_SIB-L0_F1,13 UP
SIB0_F2 (F2 ):
LCC3_SIB-L0_F0,13->SIB-S0_F2,00 RESET SIB-S0_F2,00->LCC3_SIB-L0_F1,14 UP
LCC2_SIB-L0_F0,13->SIB-S0_F2,01 RESET SIB-S0_F2,01->LCC2_SIB-L0_F1,06 UP
LCC1_SIB-L0_F0,13->SIB-S0_F2,02 UP SIB-S0_F2,02->LCC1_SIB-L0_F1,06 UP
LCC0_SIB-L0_F0,13->SIB-S0_F2,03 UP SIB-S0_F2,03->LCC0_SIB-L0_F1,14 UP
LCC3_SIB-L0_F0,12->SIB-S0_F2,04 RESET SIB-S0_F2,04->LCC3_SIB-L0_F1,15 UP
LCC2_SIB-L0_F0,12->SIB-S0_F2,05 RESET SIB-S0_F2,05->LCC2_SIB-L0_F1,07 UP
LCC1_SIB-L0_F0,12->SIB-S0_F2,06 UP SIB-S0_F2,06->LCC1_SIB-L0_F1,07 UP
LCC0_SIB-L0_F0,12->SIB-S0_F2,07 UP SIB-S0_F2,07->LCC0_SIB-L0_F1,15 UP
LCC3_SIB-L0_F0,09->SIB-S0_F2,08 RESET SIB-S0_F2,08->LCC3_SIB-L0_F1,10 UP
LCC2_SIB-L0_F0,09->SIB-S0_F2,09 RESET SIB-S0_F2,09->LCC2_SIB-L0_F1,02 UP
LCC1_SIB-L0_F0,09->SIB-S0_F2,10 UP SIB-S0_F2,10->LCC1_SIB-L0_F1,02 UP
LCC0_SIB-L0_F0,09->SIB-S0_F2,11 UP SIB-S0_F2,11->LCC0_SIB-L0_F1,10 UP
LCC3_SIB-L0_F0,08->SIB-S0_F2,12 RESET SIB-S0_F2,12->LCC3_SIB-L0_F1,11 UP
LCC2_SIB-L0_F0,08->SIB-S0_F2,13 RESET SIB-S0_F2,13->LCC2_SIB-L0_F1,03 UP
LCC1_SIB-L0_F0,08->SIB-S0_F2,14 UP SIB-S0_F2,14->LCC1_SIB-L0_F1,03 UP
LCC0_SIB-L0_F0,08->SIB-S0_F2,15 UP SIB-S0_F2,15->LCC0_SIB-L0_F1,11 UP
SIB0_F3 (F2 ):
LCC3_SIB-L0_F0,05->SIB-S0_F3,00 RESET SIB-S0_F3,00->LCC3_SIB-L0_F1,06 UP
LCC2_SIB-L0_F0,05->SIB-S0_F3,01 RESET SIB-S0_F3,01->LCC2_SIB-L0_F1,14 UP
LCC1_SIB-L0_F0,05->SIB-S0_F3,02 UP SIB-S0_F3,02->LCC1_SIB-L0_F1,14 UP
LCC0_SIB-L0_F0,05->SIB-S0_F3,03 UP SIB-S0_F3,03->LCC0_SIB-L0_F1,06 UP
LCC3_SIB-L0_F0,04->SIB-S0_F3,04 RESET SIB-S0_F3,04->LCC3_SIB-L0_F1,07 UP
LCC2_SIB-L0_F0,04->SIB-S0_F3,05 RESET SIB-S0_F3,05->LCC2_SIB-L0_F1,15 UP
LCC1_SIB-L0_F0,04->SIB-S0_F3,06 UP SIB-S0_F3,06->LCC1_SIB-L0_F1,15 UP
LCC0_SIB-L0_F0,04->SIB-S0_F3,07 UP SIB-S0_F3,07->LCC0_SIB-L0_F1,07 UP
LCC3_SIB-L0_F0,01->SIB-S0_F3,08 RESET SIB-S0_F3,08->LCC3_SIB-L0_F1,02 UP
LCC2_SIB-L0_F0,01->SIB-S0_F3,09 RESET SIB-S0_F3,09->LCC2_SIB-L0_F1,10 UP
LCC1_SIB-L0_F0,01->SIB-S0_F3,10 UP SIB-S0_F3,10->LCC1_SIB-L0_F1,10 UP
LCC0_SIB-L0_F0,01->SIB-S0_F3,11 UP SIB-S0_F3,11->LCC0_SIB-L0_F1,02 UP
LCC3_SIB-L0_F0,00->SIB-S0_F3,12 RESET SIB-S0_F3,12->LCC3_SIB-L0_F1,03 UP
LCC2_SIB-L0_F0,00->SIB-S0_F3,13 RESET SIB-S0_F3,13->LCC2_SIB-L0_F1,11 UP
LCC1_SIB-L0_F0,00->SIB-S0_F3,14 UP SIB-S0_F3,14->LCC1_SIB-L0_F1,11 UP
LCC0_SIB-L0_F0,00->SIB-S0_F3,15 UP SIB-S0_F3,15->LCC0_SIB-L0_F1,03 UP
Sib #1 :
---------
SIB1_F0 (F2 ):
LCC0_SIB-L1_F0,03->SIB-S1_F0,00 RESET SIB-S1_F0,00->LCC0_SIB-L1_F1,00 UP
SIB2_F1 (F3 ):
SIB-S2_F0,00->SIB-L2_F1,00 UP SIB-L2_F1,00->FPC7_B DOWN
SIB-S2_F0,04->SIB-L2_F1,01 UP SIB-L2_F1,01->FPC7_T DOWN
SIB-S2_F3,11->SIB-L2_F1,02 UP SIB-L2_F1,02->FPC6_B DOWN
SIB-S2_F3,15->SIB-L2_F1,03 UP SIB-L2_F1,03->FPC6_T DOWN
Sib #4 :
---------
SIB4_F0 (F1 ):
FPC0_T->SIB-L4_F0,00 RESET SIB-L4_F0,00->SIB-S4_F3,15 UP
FPC0_B->SIB-L4_F0,01 UP SIB-L4_F0,01->SIB-S4_F3,11 UP
FPC1_T->SIB-L4_F0,02 RESET SIB-L4_F0,02->SIB-S4_F0,04 UP
FPC1_B->SIB-L4_F0,03 RESET SIB-L4_F0,03->SIB-S4_F0,00 UP
FPC2_T->SIB-L4_F0,04 RESET SIB-L4_F0,04->SIB-S4_F3,07 UP
FPC2_B->SIB-L4_F0,05 RESET SIB-L4_F0,05->SIB-S4_F3,03 UP
FPC3_T->SIB-L4_F0,06 RESET SIB-L4_F0,06->SIB-S4_F0,12 UP
FPC3_B->SIB-L4_F0,07 RESET SIB-L4_F0,07->SIB-S4_F0,08 UP
FPC4_T->SIB-L4_F0,08 RESET SIB-L4_F0,08->SIB-S4_F2,15 UP
FPC4_B->SIB-L4_F0,09 RESET SIB-L4_F0,09->SIB-S4_F2,11 UP
FPC5_T->SIB-L4_F0,10 RESET SIB-L4_F0,10->SIB-S4_F1,04 UP
FPC5_B->SIB-L4_F0,11 RESET SIB-L4_F0,11->SIB-S4_F1,00 UP
FPC6_T->SIB-L4_F0,12 RESET SIB-L4_F0,12->SIB-S4_F2,07 UP
FPC6_B->SIB-L4_F0,13 UP SIB-L4_F0,13->SIB-S4_F2,03 UP
FPC7_T->SIB-L4_F0,14 RESET SIB-L4_F0,14->SIB-S4_F1,12 UP
FPC7_B->SIB-L4_F0,15 RESET SIB-L4_F0,15->SIB-S4_F1,08 UP
SIB4_F1 (F3 ):
SIB-S4_F0,00->SIB-L4_F1,00 UP SIB-L4_F1,00->FPC7_B UP
SIB-S4_F0,04->SIB-L4_F1,01 UP SIB-L4_F1,01->FPC7_T UP
SIB-S4_F3,11->SIB-L4_F1,02 UP SIB-L4_F1,02->FPC6_B UP
SIB-S4_F3,15->SIB-L4_F1,03 UP SIB-L4_F1,03->FPC6_T UP
SIB-S4_F0,08->SIB-L4_F1,04 UP SIB-L4_F1,04->FPC5_B UP
SIB-S4_F0,12->SIB-L4_F1,05 UP SIB-L4_F1,05->FPC5_T UP
SIB-S4_F3,03->SIB-L4_F1,06 UP SIB-L4_F1,06->FPC4_B UP
SIB-S4_F3,07->SIB-L4_F1,07 UP SIB-L4_F1,07->FPC4_T UP
SIB-S4_F1,00->SIB-L4_F1,08 UP SIB-L4_F1,08->FPC3_B UP
SIB-S4_F1,04->SIB-L4_F1,09 UP SIB-L4_F1,09->FPC3_T UP
SIB-S4_F2,11->SIB-L4_F1,10 UP SIB-L4_F1,10->FPC2_B UP
SIB-S4_F2,15->SIB-L4_F1,11 UP SIB-L4_F1,11->FPC2_T UP
SIB-S4_F1,08->SIB-L4_F1,12 UP SIB-L4_F1,12->FPC1_B UP
SIB-S4_F1,12->SIB-L4_F1,13 UP SIB-L4_F1,13->FPC1_T UP
SIB-S4_F2,03->SIB-L4_F1,14 UP SIB-L4_F1,14->FPC0_B UP
SIB-S4_F2,07->SIB-L4_F1,15 UP SIB-L4_F1,15->FPC0_T UP
Description (M5 and M10 routers only) Display Forwarding Engine Board (FEB) status
information.
Output Fields Table 50 lists the output fields for the show chassis feb command. Output fields are
listed in the approximate order in which they appear.
Table 50: show chassis feb Output Fields
Description 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).
Options none—(Routing matrix only) Display version levels for the firmware on the
TX Matrix platform and on all the T640 routing nodes connected to it.
lcc number—(Routing matrix only) (Optional) Display version levels for the
firmware on a specified T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from 0
through 3.
scc—(Routing matrix only) (Optional) Display version levels for the firmware on the
TX Matrix platform (or switch-card chassis).
Output Fields Table 51 lists the output fields for the show chassis firmware command. Output
fields are listed in the approximate order in which they appear.
Table 51: show chassis firmware Output Fields
Field Name Field Description
Part Chassis part name.
Type Type of firmware: ROM or O/S.
Version Version of firmware running on the chassis part.
Description (J-series routing platform only) Display status of the forwarding process (fwdd).
Output Fields Table 52 lists the output fields for the show chassis forwarding command. Output
fields are listed in the approximate order in which they appear.
Table 52: show chassis forwarding Output Fields
Description Display status information about the installed Flexible PIC Concentrators (FPCs)
and Physical Interface Cards (PICs).
Options none—Display status information for all FPCs. For the routing matrix only, display
status information for all FPCs on the TX Matrix platform and its attached T640
routing nodes.
detail—(Optional) Display detailed status information for all FPCs or for the FPC in
the specified slot (see fpc-slot).
! Routing matrix only—If you specify the number of the T640 routing node
by using the lcc number option (the recommended method), replace fpc-slot
with a value from 0 through 7. Otherwise, replace fpc-slot with a value from
0 through 31. For example, the following commands have the same result:
pic-status—(Optional) Display status information for all PICs or for the PIC in the
specified slot (see fpc-slot).
lcc number—(Routing matrix only) (Optional) Display status information for a T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
Output Fields Table 53 lists the output fields for the show chassis fpc command. Output fields are
listed in the approximate order in which they appear.
lcc1-re0:
--------------------------------------------------------------------------
lcc2-re0:
--------------------------------------------------------------------------
Slot 1 Online FPC Type 3
PIC 0 Online 1x OC-192 SM SR1
Slot 5 Online FPC Type 2
PIC 0 Online 1x OC-48 SONET, SMSR
PIC 1 Online 2x G/E, 1000 BASE-LX
PIC 2 Online 2x G/E, 1000 BASE-LX
PIC 3 Online 1x OC-48 SONET, SMSR
lcc3-re0:
--------------------------------------------------------------------------
Description Display a list of all Flexible Physical Interface Card (PIC) Concentrators (FPCs) and
PICs installed in the router chassis, including the hardware version level and serial
number.
Options none—Display information about hardware. For the routing matrix only, display
information about the TX Matrix platform and its attached T640 routing nodes.
detail | extensive | frus—(Optional) Display the specified level of output. Use the frus
option to display information about field-replaceable units (FRUs).
Output Fields Table 54 lists the output fields for the show chassis hardware command. Output
fields are listed in the approximate order in which they appear.
Table 54: show chassis hardware Output Fields
Description (Routing matrix only) Display the status of all T640 routing nodes (or line-card
chassis) connected to the TX Matrix platform.
Output Fields Table 55 lists the output fields for the show chassis lccs command. Output fields are
listed in the approximate order in which they appear.
Table 55: show chassis lccs Output Fields
Description Display the physical location of the chassis. This command can only be used on the
master Routing Engine.
Options none—Display all information about the physical location of the chassis. For the
routing matrix only, display all information about the physical location of the
TX Matrix platform and its attached T640 routing nodes.
fpc—(Routing matrix only) (Optional) Display the physical location of all Flexible
PIC Concentrators (FPCs).
interface by-slot fpc number lcc number—(Routing matrix only) (Optional) Display
the global FPC number of an interface by specifying its local FPC number and
T640 routing node (or line-card chassis) number.
! The global FPC number is the FPC slot number when all the FPC slots in
the routing matrix are considered: 0 through 31. The local FPC number is
the FPC slot number on a particular T640 routing node.
scc—(Routing matrix only) (Optional) Display the physical location of the TX Matrix
platform (or switch-card chassis).
Output Fields Table 56 lists the output fields for the show chassis location command. Output
fields are listed in the approximate order in which they appear.
Table 56: show chassis location Output Fields
show chassis location user@host> show chassis location interface by-slot fpc 1 lcc 1
interface by-slot Global FPC: 9
(Routing Matrix)
Description Display the media access control (MAC) addresses for the router chassis.
Options none—Display the MAC addresses for the router chassis. For the routing matrix
only, display MAC addresses on the TX Matrix platform and its attached T640
routing nodes.
lcc number—(Routing matrix only) (Optional) Display MAC addresses for a specified
T640 routing node (or line-card chassis) that is connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display MAC addresses for the TX Matrix
platform (or switch-card chassis).
Output Fields Table 57 lists the output fields for the show chassis mac-addresses command.
Output fields are listed in the approximate order in which they appear.
Table 57: show chassis mac-addresses Output Fields
lcc0-re0:
--------------------------------------------------------------------------
MAC address information:
Public base address 00:05:85:68:98:00
Public count 2032
Private base address 00:05:85:68:9f:f0
Private count 16
lcc2-re0:
--------------------------------------------------------------------------
MAC address information:
Public base address 00:05:85:68:78:00
Public count 2032
Private base address 00:05:85:68:7f:f0
Private count 16
Description Display status information about the Physical Interface Card (PIC) installed in the
specified Flexible PIC Concentrator (FPC) and PIC slot.
Options fpc-slot slot-number—Display information about the PIC in this particular FPC slot:
! Routing matrix only—If you specify the number of the T640 routing node
by using the lcc number option (the recommended method), replace
slot-number with a value from 0 through 7. Otherwise, replace slot-number
with a value from 0 through 31. For example, the following commands
have the same result:
pic-slot slot-number—Display information about the PIC in this particular PIC slot.
Replace slot-number with a value from 0 through 3.
List of Sample Output show chassis pic fpc-slot pic-slot on page 205
show chassis pic fpc-slot pic-slot (PIC Offline) on page 205
show chassis pic fpc-slot pic-slot (FPC Offline) on page 205
show chassis pic fpc-slot pic-slot (FPC Not Present) on page 205
show chassis pic fpc-slot pic-slot (PIC Not Present) on page 205
show chassis pic fpc-slot pic-slot lcc (Routing Matrix) on page 205
Output Fields Table 58 lists the output fields for the show chassis pic command. Output fields are
listed in the approximate order in which they appear.
Table 58: show chassis pic Output Fields
show chassis pic user@host> show chassis pic fpc-slot 1 pic-slot 1 lcc 0
fpc-slot pic-slot lcc lcc0-re0:
(Routing Matrix) --------------------------------------------------------------------------
PIC fpc slot 1 pic slot 1 information:
Type 4x OC-3 SONET, SMIR
ASIC type D chip
State Online
PIC version 1.2
Uptime 5 days, 2 hours, 12 minutes, 8 seconds
Options none—Display information about one or more Routing Engines. For the routing
matrix only, display information about all Routing Engines on the TX Matrix
platform and its attached T640 routing nodes.
scc—(Routing matrix only) (Optional) Display Routing Engine information for the
TX Matrix platform (or switch-card chassis).
Output Fields Table 59 lists the output fields for the show chassis routing-engine command.
Output fields are listed in the approximate order in which they appear.
Table 59: show chassis routing-engine Output Fields
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 33 degrees C / 91 degrees F
CPU temperature 30 degrees C / 86 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 98 percent
Model RE-3.0
Serial ID 210865700363
Start time 2004-08-05 18:42:05 PDT
Uptime 9 days, 22 hours, 48 minutes, 20 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.02 0.00
lcc2-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 34 degrees C / 93 degrees F
CPU temperature 35 degrees C / 95 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 2 percent
Interrupt 0 percent
Idle 98 percent
Model RE-4.0
Serial ID P11123900126
Start time 2004-08-05 18:42:05 PDT
Uptime 9 days, 22 hours, 49 minutes, 4 seconds
Load averages: 1 minute 5 minute 15 minute
0.01 0.01 0.0
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V1.0.17
lcc2-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V1.0.0
Description (M40 router only) Display System Control Board (SCB) status information.
Output Fields Table 60 lists the output fields for the show chassis scb command. Output fields are
listed in the approximate order in which they appear.
Description (M40e and M160 routers only) Display Switching and Forwarding Module (SFM)
status information.
sfm-slot—(Optional) Display status information about the SFM in the specified slot
only. For the M40e router, replace sfm-slot with 0 or 1. For the M160 router, replace
sfm-slot with a value from 0 through 3.
Output Fields Table 61 lists the output fields for the show chassis sfm command. Output fields are
listed in the approximate order in which they appear.
....
Packet scheduling mode : Disabled
Description (M320 routers and T-series routing platform only) Display Switch Interface Boards
(SIB) status information.
Options none—(Routing matrix only) Display the SIB status for the TX Matrix platform and
its attached T640 routing nodes.
lcc number—(Routing matrix only) (Optional) Display SIB status information for a
specified T640 routing node (or line-card chassis) that is connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display SIB status information for the
TX Matrix platform (or switch-card chassis).
Output Fields Table 62 lists the output fields for the show chassis sibs command. Output fields are
listed in the approximate order in which they appear.
Table 62: show chassis sibs Output Fields
lcc0-re0:
--------------------------------------------------------------------------
Slot State Uptime
0 Empty
1 Empty
2 Empty
3 Disconnected 7 days, 21 hours, 46 minutes, 53 seconds
4 Online 7 days, 21 hours, 46 minutes, 52 seconds
...
Description (T-series routing platform only) Display Switch Processor Mezzanine Board (SPMB)
status information.
Options none—(Routing matrix only) Display SPMB status for the TX Matrix platform and its
attached T640 routing nodes.
lcc number—(Routing matrix only) (Optional) Display information about the SPMB
on a specified T640 routing node (or line-card chassis) that is connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display information about the SPMB on the
TX Matrix platform (or switch-card chassis).
Output Fields Table 63 lists the output fields for the show chassis spmb command. Output fields
are listed in the approximate order in which they appear.
Table 63: show chassis spmb Output Fields
Field Name Field Description
Slot SPMB slot number: 0 or 1.
State SPMB status: Online or Offline.
Total CPU Utilization (%) Total percentage of CPU being used by the SPMB processor.
Interrupt CPU Utilization (%) Of the total CPU being used by the SPMB processor, the percentage
being used for interrupts.
Memory Heap Utilization (%) Percentage of heap space (dynamic memory) being used by the FPC
processor. If this number exceeds 80 percent, there may be a
software problem (memory leak).
Buffer Utilization (%) Percentage of buffer space being used by the SPMB processor for
buffering internal messages.
Start time Time at which the SPMB last came online.
Uptime How long the SPMB has been up and running.
Description (T-series routing platform only) Display Switch Processor Mezzanine Board (SPMB)
Switch Interface Board (SIB) status information.
Options none—(Routing matrix only) Display the SIB status for the TX Matrix platform and
its attached T640 routing nodes.
lcc number—(Routing matrix only) (Optional) Display SIB status information for a
specified T640 routing node (or line-card chassis) that is connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display SIB status information for the
TX Matrix platform (or switch-card chassis).
Additional Information On a T-series routing platform, you can use either this command or the show
chassis sibs command to produce the same output. The show chassis sibs
command is supported on the M320 router and on the T-series routing platform.
List of Sample Output show chassis spmb sibs (T320) on page 219
show chassis spmb sibs (Routing Matrix) on page 220
show chassis spmb sibs lcc (Routing Matrix) on page 220
show chassis spmb sibs scc (Routing Matrix) on page 220
Output Fields Table 64 lists the output fields for the show chassis spmb sibs command. Output
fields are listed in the approximate order in which they appear.
Table 64: show chassis spmb sibs Output Fields
State SIB status: Disconnected, Online, Offline, Spare, Empty, Fault, and Check.
Uptime How long the SIB has been up and running.
show chassis spmb sibs user@host> show chassis spmb sibs lcc 0
lcc (Routing Matrix) lcc0-re0:
--------------------------------------------------------------------------
Slot State Uptime
0 Empty
1 Empty
2 Empty
3 Disconnected 8 days, 48 minutes, 58 seconds
4 Online 8 days, 48 minutes, 57 seconds
show chassis spmb sibs user@host> show chassis spmb sibs scc
scc (Routing Matrix) scc-re0:
--------------------------------------------------------------------------
Slot State Uptime
0 Empty
1 Empty
2 Empty
3 Offline
4 Online 8 days, 54 minutes, 1 second
Description (M20 routers only) Display status information about the System and Switch Board
(SSB).
slot—(Optional) Display information about the SSB in the specified slot. Replace slot
with 0 or 1.
Output Fields Table 65 lists the output fields for the show chassis ssb command. Output fields are
listed in the approximate order in which they appear.
Table 65: show chassis ssb Output Fields
...
Description (M320 routers only) Display information about the external clock source currently
used for chassis synchronization.
Output Fields Table 66 lists the output fields for the show chassis synchronization command.
Output fields are listed in the approximate order in which they appear.
Table 66: show chassis synchronization Output Fields
Selected for Number of seconds this clock has been the master or backup clock
source.
Selected since Time stamp for establishment as master or backup clock source.
Deviation (in ppm) Difference in clock timing, in parts per million (ppm).
Last deviation (in ppm) Previous difference in clock timing, if any, in ppm.
Configured sources Information of clock sources eligible for selection as master clock.
Source Information following concerns external source A or B.
Priority Indicates priority of external clock sources:
! primary—Source is a primary reference.
! secondary—Source is a secondary reference.
Table 67 summarizes the command-line interface (CLI) commands you can use to
perform and monitor CLI management functions. Commands are listed in
alphabetical order.
Task Command
Clear the logical router view and return to a full router view. clear cli logical-router on page 226
Set the CLI to complete partial command entries. set cli complete-on-space on page 227
Set the current working directory. set cli directory on page 228
Set the maximum time that an individual session can be idle before the user is logged set cli idle-timeout on page 229
off the router.
Set the CLI to the specified logical routing instance. set cli logical-router on page 230
Set the CLI prompt. set cli prompt on page 231
Set the CLI to prompt you to restart the router after a software upgrade. set cli restart-on-upgrade on page 232
Set the number of lines on the screen. set cli screen-length on page 233
Set the number of characters on a line. set cli screen-width on page 234
Set the terminal type. set cli terminal on page 235
Timestamp CLI output. set cli timestamp on page 236
Set the system date and time. set date on page 237
Display all CLI settings. show cli on page 238
Display login permissions for the current user. show cli authorization on page 239
Display the current working directory. show cli directory on page 241
Display a list of previous CLI commands. show cli history on page 242
NOTE: For information about how to configure CLI parameters, see the JUNOS CLI
User Guide.
! 225
JUNOS 8.1 System Basics and Services Command Reference
Description Clear the logical router view and return to a full router view. In a logical router view,
the output of the command displays information related to the logical router only.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
user@host>
Description 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
set cli In the following example, pressing the spacebar changes the partial command entry
complete-on-space from com to complete-on-space. The example shows how adding the keyword off at
the end of the command disables command completion.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Set the maximum time that an individual session can be idle before the user is
logged off the router.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
user@host:log-router-A>
Options string—CLI prompt string. To include spaces in the prompt, enclose the string in
quotation marks. By default, the string is username@hostname.
Output Fields When you enter this command, the new CLI prompt is displayed.
Description For an individual session, set the CLI to prompt you to restart the router after
upgrading the software.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Options 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.
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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Options 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
Enclose the format in single quotation marks ( ‘ ). Do not use spaces. Use a
hyphen ( - ) or similar character to separate placeholders.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
set date
Options 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
show cli
Output Fields Table 68 lists the output fields for the show cli command. Output fields are listed in
the approximate order in which they appear.
Table 68: show cli Output Fields
Output Fields Table 69 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 69: show cli authorization Output Fields
Output Fields Table 70 lists the output fields for the show cli directory command. Output fields are
listed in the approximate order in which they appear.
Table 70: show cli directory Output Fields
Output Fields Table 71 lists the output fields for the show cli history command. Output fields are
listed in the approximate order in which they appear.
Table 71: show cli history Output Fields
Table 72 summarizes the command-line interface (CLI) commands you can use to
perform and monitor file management functions. Commands are listed in
alphabetical order.
Task Command
Remove contents of a log file. clear log on page 244
Archive files or archive and compress files. file archive on page 245
Calculate checksums. file checksum md5 on page 246
Compare two files. file compare on page 247
Copy files. file copy on page 249
Delete files. file delete on page 250
List files and directories on the router. file list on page 251
NOTE: See also the monitor list, monitor start, and monitor stop commands, which
are documented in “Real-Time Router Monitoring Operational Mode Commands”
on page 51.
For information about how to configure file parameters, see the JUNOS System
Basics Configuration Guide.
! 243
JUNOS 8.1 System Basics and Services Command Reference
clear log
all—(Optional) Truncate the specified log file and delete all archived versions of it.
Output Fields See file list on page 251 for an explanation of output fields.
clear log The following sample commands list log file information, clear the contents of a log
file, and then display the updated log file information:
file archive
Description Archive, and optionally compress, one or multiple local system files as a single file,
locally or at a remote location.
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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
file archive The following sample command archives all message files in the local directory
(Multiple Files) /var/log/messages as the single file messages-archive.tar in the same directory:
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:
file archive The following sample command archives and compresses all message files in the
(With Compression) local directory /var/log/messages as the single file messages-archive.tgz in the
same directory:
Output Fields When you enter this command, you are provided feedback on the status of your
request.
file compare
Description 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,x xx,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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
file compare files user@host> file compare files /tmp/one /tmp/two context
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 user@host> file compare files /tmp/one /tmp/two unified
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;
}
file compare files user@host> file compare files /tmp/one /tmp/two unified ignore-white-space
unified --- /tmp/one Wed Dec 3 09:13:10 2003
ignore-white-space +++ /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>; # SECRET-DATA
}
file copy
Description Copy files from one place to another on the local router or between the local router
and a remote system.
List of Sample Output file copy (A File from the Router to a PC) on page 249
file copy (A Configuration File Between Routing Engines) on page 249
file copy (A Log File Between Routing Engines) on page 249
Output Fields When you enter this command, you are provided feedback on the status of your
request.
file copy The following sample command copies a configuration file from Routing Engine 0
(A Configuration File to Routing Engine 1:
Between Routing
Engines) user@host> file copy /config/juniper.conf re1:/var/tmp/copied-juniper.conf
file copy (A Log File The following sample command copies a log file from Routing Engine 0 to Routing
Between Routing Engine 1:
Engines)
user@host> file copy lcc0-re0:/var/log/chassisd lcc0-re1:/var/tmp
file delete
Options 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
file list
filename—(Optional) Display a list of files. For a routing matrix, the filename must
include the chassis information.
Additional information The default directory is the home directory of the user logged into the router. 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
esw_filter_tnp_addr*
esw_getstats*
esw_phy*
esw_stats*
file rename
Options source—Original name of the file. For a routing matrix, the filename must include
the chassis information.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
file rename 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.
file rename The following example lists the files in /var/tmp, renames one of the files, and then
(Routing Matrix) displays the list of files again to reveal the newly named file.
/var/tmp:
.pccardd
sartre.conf
snmpd
syslogd.core-tarball.0.tgz
user@host> file rename lcc0-re0:/var/tmp/snmpd /var/tmp/snmpd.rr
user@host> file list lcc0-re1:/var/tmp
lcc0-re1:
--------------------------------------------------------------------------
/var/tmp:
.pccardd
sartre.conf
snmpd.rr
syslogd.core-tarball.0.tgz
file show
Options filename—Name of a file. For a routing matrix, the filename must include the
chassis information.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
####################################################################
# Basic stuff
####################################################################
define msgbuf
printf "%s", msgbufp->msg_ptr
end
# hex dump of a block of memory
# usage: dump address length
define dump
p $arg0, $arg1
set $ch = $arg0
set $j = 0
set $n = $arg1
while ($j < $n)
#printf "%x %x ",&$ch[$j],$ch[$j]
printf "%x ",$ch[$j]
set $j = $j + 1
if (!($j % 16))
printf "\n"
end
end
end
show log
Description List log files, display log file contents, or display information about users who have
logged in to the router.
filename—(Optional) Display the log messages in the specified log file. For the
routing matrix, the filename must include the chassis information.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Table 73 summarizes the command-line interface (CLI) commands you can use to
perform and monitor Packet Forwarding Engine management functions.
Commands are listed in alphabetical order.
Task Command
Display Packet Forwarding Engine Compact Forwarding Engine Board show pfe cfeb on page 261
(CFEB) status and statistics information.
Display Packet Forwarding Engine Forwarding Engine Board (FEB) status show pfe feb on page 264
and statistics information.
Display Packet Forwarding Engine statistics for the specified Flexible PIC show pfe fpc on page 267
Concentrator (FPC).
(J-series routing platform only) Display Packet Forwarding Engine show pfe fwdd on page 269
forwarding process (fwdd) status and statistics information.
(Routing matrix only) Display Packet Forwarding Engine information for the show pfe lcc on page 272
specified T640 routing node (or line-card chassis).
Display Packet Forwarding Engine next-hop information. show pfe next-hop on page 275
Display the routes in the Packet Forwarding Engine forwarding table. show pfe route on page 277
(M40 routers only) Display Packet Forwarding Engine System Control Board show pfe scb on page 280
(SCB) status and statistics information.
(M40e and M160 routers only) Display Packet Forwarding Engine Switching show pfe sfm on page 282
and Forwarding Module (SFM) status and statistics information.
(M20 routers only) Display Packet Forwarding Engine System and Switch show pfe ssb on page 284
Board (SSB) status and statistics information.
Display Packet Forwarding Engine direct memory access (DMA) statistics. show pfe statistics dma on page 287
Display Packet Forwarding Engine error statistics. show pfe statistics error on page 290
Display IPv4 Packet Forwarding Engine statistics. show pfe statistics ip on page 292
Display Packet Forwarding Engine IPv6 statistics. show pfe statistics ip6 on page 295
Display Packet Forwarding Engine notification statistics. show pfe statistics notification on page 298
Display Packet Forwarding Engine polled I/O (PIO) statistics. show pfe statistics pio on page 300
Display Packet Forwarding Engine traffic statistics. show pfe statistics traffic on page 301
Display Packet Forwarding Engine status information. show pfe terse on page 304
! 259
JUNOS 8.1 System Basics and Services Command Reference
NOTE: For information about how to configure PFE parameters, see the JUNOS
System Basics Configuration Guide.
260 !
Chapter 9: Packet Forwarding Engine Operational Mode Commands
Description (M7i routers only) Display Packet Forwarding Engine Compact Forwarding Engine
Board (CFEB) status and statistics information.
Description (M5 and M10 routers only) Display Packet Forwarding Engine Forwarding Engine
Board (FEB) status and statistics information.
Description Display Packet Forwarding Engine statistics for the specified Flexible PIC
Concentrator (FPC).
Options slot—FPC slot number, for example, 0. The number of slots depends on the routing
platform.
…
21 0
PFE socket-buffer bytes pending transmit:
bucket count
------ -----
0 52273
1 0
…
21 0
Description (J-series routing platform only) Display Packet Forwarding Engine forwarding
process (fwdd) status and statistics information.
Description (Routing matrix only) Display Packet Forwarding Engine status and statistics for the
specified T640 routing node (or line-card chassis).
Options lcc number—Slot number of the T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
fpc slot—(Routing matrix only) (Optional) Show the next hops for a Flexible PIC
Concentrator (FPC) slot.
If you specify the number of a T640 routing node by using the lcc number
option (the recommended method), replace slot with a value from 0 through 7.
Otherwise, replace slot with a value from 0 through 31. For example, the
following commands have the same result:
lcc number—(Routing matrix only) (Optional) Slot number of the T640 routing node
(or line-chard chassis) that houses the FPC. Replace number with a value from
0 through 3.
Nexthop Info:
ID Type Interface Next Hop Addr Protocol Encap MTU
----- -------- ------------- --------------- ---------- ------------ ----
5 Mcast - default IPv4 - 0
6 Bcast - - IPv4 - 0
8 Discard - - IPv4 - 0
9 MDiscard - - IPv4 - 0
13 Mcast - default IPV6 - 0
17 MDiscard - - IPV6 - 0
18 Reject - - IPV6 - 0
24 Discard - - None - 0
68 Local - 192.168.66.113 IPv4 - 0
69 Resolve fxp0.0 - IPv4 Unspecified 0
70 Unicast fxp0.0 192.168.71.254 IPv4 Unspecified 0
256 Local - 10.71.71.1 IPv4 - 0
257 Local - 127.0.0.1 IPv4 - 0
258 Mcast .local..1 default IPv4 Unspecified 0
259 Bcast .local..1 - IPv4 Unspecified 0
261 Discard .local..1 - IPv4 Unspecified 0
262 MDiscard .local..1 - IPv4 Unspecified 0
269 Mcast .local..1 default IPV6 Unspecified 0
271 Discard .local..1 - IPV6 Unspecified 0
...
Description 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 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 Routing Protocols and Policies Command
Reference.
fpc slot—(Routing matrix only) (Optional) Show the routes for a Flexible PIC
Concentrator (FPC) slot:
If you specify the number of a T640 routing node by using the lcc number
option (the recommended method), replace slot with a value from 0 through 7.
Otherwise, replace slot with a value from 0 through 31. For example, the
following commands have the same result:
prefix prefix—(Optional) IPv4 or IPv6 prefix for which to show table entries.
lcc number—(Routing matrix only) (Optional) Slot number of the T640 routing node
(or line-card chassis) that houses the FPC. Replace number with a value from 0
through 3.
...
show pfe route lcc user@host> show pfe route lcc 2 summary
summary
(Routing Matrix) Slot 0
Slot 1
Slot 16
Slot 17
Description (M40 routers only) Display Packet Forwarding Engine System Control Board (SCB)
status and statistics information.
Description (M40e and M160 routers only) Display Packet Forwarding Engine Switching and
Forwarding Module (SFM) status and statistics information.
Options slot—Display statistics from the specified SFM slot. Replace slot with a value from
0 through 3.
Additional Information This command applies only to systems with multiple SFMs.
Description (M20 routers only) Display Packet Forwarding Engine System and Switch Board
(SSB) status and statistics information.
SSB status:
Slot: Present
State: Online
Last State Change: 2005-03-06 03:10:28 PST
Uptime (total): 11:23:27
Failures: 0
Pending: 0
Description Display Packet Forwarding Engine direct memory access (DMA) statistics.
Options none—Display all Packet Forwarding Engine direct memory access statistics.
fpc slot—(Routing matrix only) (Optional) Display statistics for a Flexible PIC
Concentrator (FPC) slot.
If you specify the number of a T640 routing node by using the lcc number
option (the recommended method), replace slot with a value from 0 through 7.
Otherwise, replace slot with a value from 0 through 31. For example, the
following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display statistics for a specific T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
DMA Errors:
DMA Requests:
Requests available: 256, Requests used: 0
show pfe statistics dma user@host> show pfe statistics dma lcc 2
lcc (Routing Matrix)
Slot 0
DMA Statistics:
DMA Errors:
DMA Requests:
Requests available: 768, Requests used: 0
DMA Statistics:
DMA Errors:
DMA Requests:
Requests available: 768, Requests used: 0
Slot 1
DMA Statistics:
DMA Errors:
DMA Requests:
Requests available: 768, Requests used: 0
Slot 16
DMA Statistics:
DMA Errors:
DMA Requests:
Requests available: 768, Requests used: 0
DMA Statistics:
DMA Errors:
DMA Requests:
Requests available: 768, Requests used: 0
Slot 17
DMA Statistics:
DMA Errors:
DMA Requests:
Requests available: 768, Requests used: 0
fpc slot—(Routing matrix only) (Optional) Display error statistics for a Flexible PIC
Concentrator (FPC) slot. If you specify the number of a T640 routing node by
using the lcc number option (the recommended method), replace slot with a
value from 0 through 7. Otherwise, replace slot with a value from 0 through 31.
For example, the following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display error statistics for a specific
T640 routing node (or line-card chassis) that is connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
4 5 6 7
---------- ---------- ---------- ----------
0 0 0 0 scan fail
0 0 0 0 A1->B FCS error
0 0 0 0 A2->B FCS error
0 0 0 0 correctable ECC error
0 0 0 0 uncorrectable ECC error
0 0 0 0 multiple ECC errors
0 0 0 0 B->HS link error
0 0 0 0 A1->Bm error
0 0 0 0 A2->Bo error
0 0 0 0 write buffer overflow
0 0 0 0 Bo FIFO sync error
0 0 0 0 Bo FIFO size error
0 0 0 0 Bo stream stuck error
0 0 0 0 Bo SRAM parity error
LCHIP 0 1 2 3
-------------------------------------------------------
Lin PIF: 0 0 0 0
Lin SRCTL: 0 0 0 0
Lout NLIF: 0 0 0 0
Lout DESRD: 0 0 0 0
Lout HDRF: 0 0 0 0
Slot 1
LCHIP 0 1 2 3
-------------------------------------------------------
Lin PIF: 0 0 0 0
Lin SRCTL: 0 0 0 0
Lout NLIF: 0 0 0 0
Lout DESRD: 0 0 0 0
Lout HDRF: 0 0 0 0
fpc slot—(Routing matrix only) (Optional) Display statistics for a Flexible PIC
Concentrator (FPC) slot. If you specify the number of a T640 routing node by
using the lcc number option (the recommended method), replace slot with a
value from 0 through 7. Otherwise, replace slot with a value from 0 through 31.
For example, the following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display error statistics for a specific
T640 routing node (or line-card chassis) that is connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
Output Fields Table 74 lists the output fields for the show pfe statistics ip command. Output fields
are listed in the approximate order in which they appear.
fpc slot—(Routing matrix only) (Optional) Display statistics for a Flexible PIC
Concentrator slot. If you specify the number of a T640 routing node by using
the lcc number option (the recommended method), replace slot with a value
from 0 through 7. Otherwise, replace slot with a value from 0 through 31. For
example, the following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display statistics for a specific T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
List of Sample Output show pfe statistics ip6 icmp on page 297
Output Fields Table 75 on page 296 lists the output fields for the show pfe statistics ip6
command. Output fields are listed in the approximate order in which they appear.
show pfe statistics ip6 user@host> show pfe statistics ip6 icmp
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
0 IP fragments
0 ICMP errors
Options none—(Routing matrix only) Display statistics about the Packet Forwarding Engine
notification on the TX Matrix platform and its attached T640 routing nodes.
fpc slot—(Routing matrix only) (Optional) Display notification for a Flexible PIC
Concentrator (FPC) slot. If you specify the number of a T640 routing node by
using the lcc number option (the recommended method), replace slot with a
value from 0 through 7. Otherwise, replace slot with a value from 0 through 31.
For example, the following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display notification for a specific T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
Slot 1
...
Options none—(Routing matrix only) Display statistics about the Packet Forwarding Engine
polled I/O on the TX Matrix platform and its attached T640 routing nodes.
fpc slot—(Routing matrix only) (Optional) Display statistics for a Flexible PIC
Concentrator (FPC) slot. If you specify the number of a T640 routing node by
using the lcc number option (the recommended method), replace slot with a
value from 0 through 7. Otherwise, replace slot with a value from 0 through 31.
For example, the following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display statistics for a specific T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
PIO Statistics:
show pfe statistics pio user@host> show pfe statistics pio lcc 0
lcc (Routing Matrix) Slot 0
PIO Statistics (chip 0):
425582 PIO reads
120303 PIO writes
PIO Statistics (chip 1):
406993 PIO reads
117769 PIO writes
...
fpc slot—(T-Series and M320 routers only) (Optional) Display statistics for a Flexible
PIC Concentrator (FPC) slot. If you specify the number of a T640 routing node
by using the lcc number option (the recommended method), replace slot with a
value from 0 through 7. Otherwise, replace slot with a value from 0 through 31.
For example, the following commands have the same result:
lcc number—(Routing matrix only) (Optional) Display statistics for a specific T640
routing node (or line-card chassis) that is connected to a TX Matrix platform.
Replace number with a value from 0 through 3.
Output Fields Table 76 lists the output fields for the show pfe statistics traffic command. Output
fields are listed in the approximate order in which they appear.
Packet Forwarding Engine Information about Packet Forwarding Engine local traffic:
Local Traffic statistics
! 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.
Packet Forwarding Engine Information about Packet Forwarding Engine hardware discards:
Hardware Discard
statistics ! 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.
Options none—(Routing matrix only) Display brief information about the Packet Forwarding
Engine on the TX Matrix platform and its attached T640 routing nodes.
Table 77 summarizes the command-line interface (CLI) commands you can use to
access remote systems. Commands are listed in alphabetical order.
Task Command
Open a Secure Shell (SSH) connection to a remote system. ssh on page 306
NOTE: To configure SSH and Telnet parameters, see the JUNOS System Basics
Configuration Guide.
! 305
JUNOS 8.1 System Basics and Services Command Reference
ssh
Description Use the Secure Shell (SSH) program to open a connection between a local router
and a remote system and execute commands on the remote system. You can issue
the ssh command from the JUNOS CLI to log in to a remote system or from a
remote system to log in to the local router. When executing this command, you
include one or more CLI commands by enclosing them in quotation marks and
separating the commands with semicolons:
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.
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 System Basics Configuration Guide.
306 ! ssh
Chapter 10: Remote System Access Operational Mode Commands
Beginning with Release 8.0, 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
System Basics Configuration Guide.
If you use SSH to connect between a router running JUNOS Release 5.x and one
running Release 4.x, the console displays warnings because of minor discrepancies
between the two implementations: “Warning: Server lies about size of server host
key: actual size is 1023 bits vs. announced 1024. Warning: This may be due to an
old implementation of ssh.” The warnings are informational and do not affect SSH
operation.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
ssh ! 307
JUNOS 8.1 System Basics and Services Command Reference
telnet
Type Ctrl+] to escape from the telnet session to the telnet command level, and
then type quit to exit from telnet.
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.
Additional Information Beginning with Release 8.0, 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 System Basics Configuration Guide.
308 ! telnet
Chapter 10: Remote System Access Operational Mode Commands
Output Fields When you enter this command, you are provided feedback on the status of your
request.
telnet ! 309
JUNOS 8.1 System Basics and Services Command Reference
310 ! telnet
Chapter 11
Simple Network Management Protocol
Operational Mode Commands
Table 78 summarizes the command-line interface (CLI) commands that allow you to
monitor the Simple Network Management Protocol (SNMP). Commands are listed
in alphabetical order.
Task Command
Clear SNMP statistics. clear snmp statistics on page 312
NOTE: For information about how to configure SNMP, see the JUNOS Network
Management Configuration Guide.
! 311
JUNOS 8.1 System Basics and Services Command Reference
Output Fields See show snmp statistics on page 326 for an explanation of output fields.
clear snmp statistics In the following example, SNMP statistics are displayed before and after the clear
snmp statistics command is issued:
Description Display information about Simple Network Management Protocol (SNMP) health
monitor alarms and logs.
Options none—Display information about all health monitor alarms and logs.
Output Fields Table 79 describes the output fields for the show snmp health-monitor command.
Output fields are listed in the approximate order in which they appear.
Variable OID Object ID to which the variable name is resolved. The format is x.x.x.x. detail
Owner Name of the entry configured by the user. If the entry was created through the detail
CLI, the owner has monitor prepended to it.
Creator Mechanism by which the entry was configured (Health Monitor). detail
Sample interval Time period between samples (in seconds). detail
Rising threshold Upper limit threshold value as a percentage of the maximum possible value. detail
Falling threshold Lower limit threshold value as a percentage of the maximum possible value. detail
Rising event index Event triggered when the rising threshold is crossed. detail
Falling event index Event triggered when the falling threshold is crossed. detail
Description Display information about Simple Network Management Protocol (SNMP) inform
requests.
Output Fields Table 80 describes the output fields for the show snmp inform-statistics command.
Output fields are listed in the approximate order in which they appear.
walk—Retrieve and display the SNMP object values that are associated with the
requested object identifier (OID). When you use this option, the JUNOS
software displays the objects below the subtree that you specify.
Output Fields Table 81 describes the output fields for the show snmp mib command. Output fields
are listed in the approximate order in which they appear.
show snmp mib get user@host> show snmp mib get sysObjectID.0
sysObjectID.0 = jnxProductNameM20
show snmp mib get user@host> show snmp mib get “sysObjectID.0 sysUpTime.0”
(Multiple Objects) sysObjectID.0 = jnxProductNameM20
sysUpTime.0 = 1640992
show snmp mib walk user@host> show snmp mib walk system
name sysDescr.0 = Juniper Networks, Inc. m20 internet router, kernel
JUNOS release #0: 2004-1 Build date: build date UTC Copyright (c) 1996-2004
Juniper Networks, Inc.
sysObjectID.0 = jnxProductNameM20
sysUpTime.0 = 1640992
sysContact.0 = Your contact
sysName.0 = my router
sysLocation.0 = building 1
sysServices.0 = 4
Description Display information about Simple Network Management Protocol (SNMP) Remote
Monitoring (RMON) alarms and events.
Output Fields Table 82 describes the output fields for the show snmp rmon command. Output
fields are listed in the approximate order in which they appear.
Variable name Name of the SNMP object instance being monitored. All levels
Event Index Event identifier. All levels
Type Type of notification made when an event is triggered. It can be one of the detail
following:
! log—A system log message is generated and an entry is made to the log table.
! snmptrap—An SNMP trap is sent to the configured destination.
! log and trap—A system log message is generated, an entry is made to the log
table, and an SNMP trap is sent to the configured destination.
! none—Neither log nor trap will be sent.
Last Event Date and time of the last event. It has the format yyyy-mm-dd hh:mm:ss timezone. brief
Community Identifies the trap group used for sending the SNMP trap. detail
Variable OID Object ID to which the variable name is resolved. The format is x.x.x.x. detail
Sample type Method of sampling the monitored variable and calculating the value to compare detail
against the upper and lower thresholds. It can have the value of absolute value or
delta value.
Startup alarm Alarm that might be sent when this entry is first activated, depending on the detail
following criteria:
! Alarm is sent when one of the following situations exists:
! Value of the alarm is above or equal to the rising threshold and the startup
type is either rising alarm or rising or falling alarm.
! Value of the alarm is below or equal to the falling threshold and the startup
type is either falling alarm or rising or falling alarm.
! Alarm is not sent when one of the following situations exists:
! Value of the alarm is above or equal to the rising threshold and the startup
type is falling alarm.
! Value of the alarm is below or equal to the falling threshold and the startup
type is rising alarm.
! Value of the alarm is between the thresholds.
Owner Name of the entry configured by the user. If the entry was created through the detail
CLI, the owner has monitor prepended to it.
Creator Mechanism by which the entry was configured (CLI or SNMP). detail
Sample interval Time period between samples (in seconds). detail
Rising threshold Upper limit threshold value configured by the user. detail
Falling threshold Lower limit threshold value configured by the user. detail
Rising event index Event triggered when the rising threshold is crossed. detail
Falling event index Event triggered when the falling threshold is crossed. detail
Current value Current value of the monitored variable in the most recent sample interval. detail
Alarm
Index State Variable name
1 falling threshold crossed ifInOctets.1
Event
Index Type Last Event
1 log and trap 2002-01-30 01:13:01 PST
show snmp rmon alarms user@host> show snmp rmon alarms detail
detail
Alarm Index 1:
Variable name ifInOctets.1
Variable OID 1.3.6.1.2.1.2.2.1.10.1
Sample type delta value
Startup alarm rising or falling alarm
Owner monitor
Creator CLI
State falling threshold crossed
Sample interval 60 seconds
Rising threshold 100000
Falling threshold 80000
Rising event index 1
Falling event index 1
Current value 0
show snmp rmon events user@host> show snmp rmon events detail
detail
Event Index 1:
Type log and trap
Community boy-elroy
Last event 2002-01-30 01:13:01 PST
Creator CLI
State active
Description Display statistics about Simple Network Management Protocol (SNMP) packets sent
and received by the router.
Output Fields Table 83 describes the output fields for the show snmp statistics command. Output
fields are listed in the approximate order in which they appear.
show snmp v3
Description Display the Simple Network Management Protocol version 3 (SNMPv3) operating
configuration.
Additional Information To edit the default display of the show snmp v3 command, specify options in the
show statement at the [edit snmp v3] hierarchy level.
Output Fields Table 84 describes the output fields for the show snmp v3 command. Output fields
are listed in the approximate order in which they appear.
Access control:
Group Context Security Read Write Notify
prefix model/level view view view
g1 usm/privacy v1 v1
g2 usm/authent v1 v1
g3 usm/none v1 v1
Table 85 summarizes the command-line interface (CLI) commands you can use to
perform and monitor system software management functions. Commands are
listed in alphabetical order.
Task Command
Clear the Address Resolution Protocol (ARP) table. clear arp on page 337
Delete an existing rescue configuration. request system configuration rescue delete on page 351
Save the most recently committed configuration as the rescue request system configuration rescue save on page 352
configuration.
(J-series routing platform only) Upgrade or downgrade firmware. request system firmware on page 353
(J-series routing platform only) Add a license key. request system license add on page 357
(J-series routing platform only) Delete a license key. request system license delete on page 358
(J-series routing platform only) Save installed license keys to a file request system license save on page 359
or URL.
Log out a user from the configuration database. request system logout on page 360
Abort a previously scheduled partition request. request system partition abort on page 361
Schedule the hard disk for partitioning. request system partition hard-disk on page 362
! 333
JUNOS 8.1 System Basics and Services Command Reference
Task Command
Power off the routing software request system power-off on page 363
Reboot the routing software. request system reboot on page 365
Back up the file systems on the router. request system snapshot on page 368
Install software bundles or packages onto the router. request system software add on page 372
Remove software bundles or packages from the router. request system software delete on page 376
(J-series routing platform only) Delete the backup JUNOS software file request system software delete-backup on page 378
(if it exists) to free up compact flash drive space.
Roll back to a previously installed version. request system software rollback on page 379
Check candidate software compatibility against the current request system software validate on page 381
configuration.
Free storage space on the router by rotating log files and deleting request system storage cleanup on page 383
unnecessary files.
Restart a JUNOS software process. restart on page 385
Display the contents of the ARP table. show arp on page 389
Display the current running system configuration. show configuration on page 391
Display Domain Name System (DNS) hostname information. show host on page 393
Display Network Time Protocol (NTP) peers. show ntp associations on page 394
Display variables returned by NTP peers. show ntp status on page 396
Display state and checksum values for files in a file system. show system audit on page 398
(J-series routing platform only) Display autoinstallation status show system autoinstallation status on page 402
information.
Display boot messages. show system boot-messages on page 403
Display system memory and buffer usage information. show system buffers on page 406
Display information about a pending commit operation. show system commit on page 408
Display directory and number of files queued for archival transfer. show system configuration archival on page 410
Display information about the rescue configuration. show system configuration rescue on page 411
Display information about active IP sockets on the Routing Engine. show system connections on page 412
Display directory usage information. show system directory-usage on page 415
(J-series routing platform only) Display system firmware information. show system firmware on page 417
(J-series routing platform only) Display a list of installed licenses. show system license on page 418
Display software processes running on the router. show system processes on page 421
Display statistics about queues on interfaces. show system queues on page 427
Display any pending system reboots or halts. show system reboot on page 429
View or compare previous configurations. show system rollback on page 430
(J-series routing platform only) Display client binding information. show system services dhcp binding on page 431
(J-series routing platform only) Display DHCP client-detected conflicts show system services dhcp conflict on page 433
for IP addresses.
(J-series routing platform only) Display global configuration settings show system services dhcp global on page 434
for a DHCP server.
334 !
Chapter 12: System Software Operational Mode Commands
Task Command
(J-series routing platform only) Display IP address pools defined for a show system services dhcp pool on page 435
DHCP server.
(J-series routing platform only) Display statistics associated with a show system services dhcp statistics on page 437
DHCP server.
Display information about a Service Deployment System (SDX) client. show system services service-deployment on page 439
Display information about the backup software that located in the show system snapshot on page 440
/altroot and /altconfig file systems.
Display JUNOS software extensions. show task memory on page 494 show system software on page 441
Display system-wide protocol-related statistics. show system statistics on page 443
Display system-wide Address Resolution Protocol (ARP) statistics. show system statistics arp on page 452
Display system-wide Connectionless Network Layer (CLNL) statistics. show system statistics clnl on page 454
Display system-wide End System-to-Intermediate System (ES-IS) show system statistics esis on page 456
statistics.
Display system-wide Internet Control Message Protocol (ICMP) show system statistics icmp on page 457
statistics.
Display system-wide ICMP version 6 statistics. show system statistics icmp6 on page 458
Display system-wide Internet Group Management Protocol (IGMP) show system statistics igmp on page 459
statistics.
Display system-wide IPv4 statistics. show system statistics ip on page 460
Display system-wide IPv6 statistics. show system statistics ip6 on page 462
Display system-wide Multiprotocol Label Switching (MPLS) statistics. show system statistics mpls on page 464
Display system-wide Reliable Datagram Protocol (RDP) statistics. show system statistics rdp on page 465
Display system-wide Transmission Control Protocol (TCP) statistics. show system statistics tcp on page 466
Display system-wide Trivial Network Protocol (TNP) statistics. show system statistics tnp on page 469
Display system-wide Trivial User Datagram Protocol (TUDP) statistics. show system statistics tudp on page 471
Display system-wide User Datagram Protocol (UDP) statistics. show system statistics udp on page 472
Display system-wide Virtual Private LAN Services (VPLS) statistics. show system statistics vpls on page 473
Display statistics about the amount of free disk space in the router’s show system storage on page 475
file systems.
View configurations of the primary and secondary Routing Engines. show system switchover on page 477
Display the current time and information about how long the router, show system uptime on page 479
router software, and routing protocols have been running.
Display users currently logged in to the router. show system users on page 481
Display JUNOS kernel memory usage. show system virtual-memory on page 483
Display routing protocol tasks on the Routing Engine. show task on page 490
Display I/O statistics for routing protocol tasks on the Routing Engine. show task io on page 492
Display memory utilization for routing protocol tasks on the Routing show task memory on page 494
Engine.
Display the hostname and version information about the software show version on page 497
running on the router.
! 335
JUNOS 8.1 System Basics and Services Command Reference
Task Command
Display the hostname and version information about the software show version invoke-on on page 498
running on a routing platform with two Routing Engines.
Create a UNIX-level shell. start shell on page 502
NOTE: For information about the request system certificate add and show system
certificate commands, see “IP Security Operational Mode Commands” on
page 627.
NOTE: For information about how to configure system software parameters, see
the JUNOS System Basics Configuration Guide.
336 !
Chapter 12: System Software Operational Mode Commands
clear arp
Description Remove entries from the Address Resolution Protocol (ARP) table for the current CLI
view. To clear entries for a specific logical router, you must first enter the set cli
logical-router logical-router-name command, and then issue the clear arp command.
vpn vpn—(Optional) Clear entries from the ARP table for the specified virtual private
network (VPN).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Required Privilege Level maintenance (or the actual user who scheduled the commit)
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Clear any pending system software reboots or halts. When used on a routing matrix
without any options, the default behavior clears all pending system software
reboots or halts on all T640 routing nodes connected to the TX Matrix platform.
all-lcc—(Routing matrix only) (Optional) Clear all halt or reboot requests for all T640
routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Clear all halt or reboot requests for a
specific T640 routing node (or line-card chassis) that is connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Clear all halt or reboot requests for the
TX Matrix platform (or switch-card chassis).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
lcc0-re0:
--------------------------------------------------------------------------
No shutdown/reboot scheduled.
lcc2-re0:
--------------------------------------------------------------------------
No shutdown/reboot scheduled.
Description (J-series routing platform only) Remove obsolete IP address bindings on a Dynamic
Host Configuration Protocol (DHCP) server and return them to the IP address pool.
List of Sample Output clear system services dhcp binding on page 341
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (J-series routing platform only) Remove IP addresses from the Dynamic Host
Configuration Protocol (DHCP) server conflict list and return them to the IP address
pool.
Options address—(Optional) Remove a specific IP address from the conflict list and return it
to the address pool.
List of Sample Output clear system services dhcp conflict on page 342
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (J-series routing platform only) Clear Dynamic Host Configuration Protocol (DHCP)
server statistics.
List of Sample Output clear system services dhcp statistics on page 343
Output Fields When you enter this command, you are provided feedback on the status of your
request.
configure
Syntax configure
<exclusive>
<private>
Description 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.
Options 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.
Additional Information For more information about the different methods of entering configuration mode
and the restrictions that apply, see the JUNOS System Basics Configuration Guide.
Output Fields When you enter this command, you are placed in configuration mode and the
system prompt changes from hostname> to hostname#.
[edit]
user@host#
344 ! configure
Chapter 12: System Software Operational Mode Commands
op
Syntax op filename
<argument-name argument-value>
Additional Information For more information about JUNOS op scripts, see the JUNOS Configuration and
Diagnostic Automation Guide.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
op ! 345
JUNOS 8.1 System Basics and Services Command Reference
request message
Description Display a message on the screens of all users who are logged in to the router or on
specific screens.
Options all—Display a message on the terminal of all users who are currently logged in.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request message user@host> request message message “Maintenance window in 10 minutes” user maria
message Message from user@host on ttyp0 at 20:27 ...
Maintenance window in 10 minutes
EOF
Description On a routing platform with two Routing Engines, specify a tty connection for login.
lcc number—(Routing matrix only) (Optional) Log in to a specific T640 routing node
(or line-card chassis) that is connected to a TX Matrix platform. Replace number
with a value from 0 through 3.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Display information about the system. Issue this command before contacting
customer support, and then include the command output in your support request.
Options all-lcc—(Routing matrix only) (Optional) Display system information for all T640
routing nodes connected to a TX Matrix platform.
scc—(Routing matrix only) (Optional) Display system information for the TX Matrix
platform (or switch-card chassis).
Additional Information The output of this command can be lengthy. We recommend that you redirect the
output to a file. This command is a combination of the following commands:
! show version
List of Sample Output request support information | save filename on page 349
request support information scc (Routing Matrix) on page 349
Output Fields See the output field descriptions for the commands listed in the “Additional
Information” section.
scc-re0:
--------------------------------------------------------------------------
Current time: 2004-09-15 00:49:06 PDT
System booted: 2004-09-14 12:53:26 PDT (11:55:40 ago)
Protocols started: 2004-09-14 12:54:19 PDT (11:54:47 ago)
Last configured: 2004-09-14 13:07:47 PDT (11:41:19 ago) by regress
12:49AM PDT up 11:56, 3 users, load averages: 0.00, 0.02, 0.03
lcc0-re0:
--------------------------------------------------------------------------
Current time: 2004-09-15 00:49:06 PDT
System booted: 2004-09-14 15:36:41 PDT (09:12:25 ago)
Last configured: 2004-09-14 15:38:06 PDT (09:11:00 ago) by root
12:49AM PDT up 9:12, 0 users, load averages: 0.13, 0.05, 0.02
lcc2-re0:
--------------------------------------------------------------------------
Current time: 2004-09-15 00:49:06 PDT
System booted: 2004-09-14 15:36:47 PDT (09:12:19 ago)
Last configured: 2004-09-14 15:38:09 PDT (09:10:57 ago) by root
12:49AM PDT up 9:12, 0 users, load averages: 0.00, 0.00, 0.00
scc-re0:
--------------------------------------------------------------------------
Hostname: hostA
Model: TX Matrix
JUNOS Base OS boot [7.0I20040914_1707_mapte]
JUNOS Base OS Software Suite [7.0I20040907_1922_rtuplur]
JUNOS Kernel Software Suite [7.0I20040914_1707_mapte]
JUNOS Packet Forwarding Engine Support (T-Series) [7.0I20040914_1707_mapte]
JUNOS Routing Software Suite [7.0I20040914_1707_mapte]
JUNOS Online Documentation [7.0I20040914_1707_mapte]
JUNOS Crypto Software Suite [7.0I20040914_1707_mapte]
JUNOS Support Tools Package [7.0-20040908.0]
lcc0-re0:
--------------------------------------------------------------------------
Hostname: hostB
Model: t640
JUNOS Base OS boot [7.0I20040914_1707_mapte]
JUNOS Base OS Software Suite [7.0I20040907_1922_rtuplur]
JUNOS Kernel Software Suite [7.0I20040914_1707_mapte]
JUNOS Packet Forwarding Engine Support (T-Series) [7.0I20040914_1707_mapte]
JUNOS Routing Software Suite [7.0I20040914_1707_mapte]
JUNOS Online Documentation [7.0I20040914_1707_mapte]
JUNOS Crypto Software Suite [7.0I20040914_1707_mapte]
lcc2-re0:
--------------------------------------------------------------------------
Hostname: dewey
Model: t640
JUNOS Base OS boot [7.0I20040914_1707_mapte]
JUNOS Base OS Software Suite [7.0I20040907_1922_rtuplur]
JUNOS Kernel Software Suite [7.0I20040914_1707_mapte]
JUNOS Packet Forwarding Engine Support (T-Series) [7.0I20040914_1707_mapte]
JUNOS Routing Software Suite [7.0I20040914_1707_mapte]
JUNOS Online Documentation [7.0I20040914_1707_mapte]
JUNOS Crypto Software Suite [7.0I20040914_1707_mapte]
...
List of Sample Output request system configuration rescue delete on page 351
Description 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.
List of Sample Output request system configuration rescue save on page 352
Output Fields When you enter this command, you are provided feedback on the status of your
request.
all-lcc—(Optional) (Routing matrix only) Halt all T640 routing nodes (or line-card
chassis) connected to the TX Matrix platform.
lcc number—(Optional) (Routing matrix only) Halt a T640 routing node that is
connected to the TX Matrix platform. Replace number with a value from
0 through 3.
scc—(Optional) (Routing matrix only) Halt only the master Routing Engine or the
backup Routing Engine on the TX Matrix platform (or switch-card chassis). If
you issue the command from the master Routing Engine, the master SCC is
halted. If you issue the command from the backup Routing Engine, the backup
SCC is halted.
Additional Information On the M7i router, the request system halt command does not immediately power
down the Packet Forwarding Engine. The power-down process can take as long as
5 minutes.
On a routing matrix, if you issue the request system halt command on the TX
Matrix master Routing Engine, all the master Routing Engines connected to the
routing matrix are halted. If you issue this command on the backup Routing Engine,
all the backup Routing Engines connected to the routing matrix are halted.
If you issue the request system halt both-routing-engines command on the TX Matrix,
all the Routing Engines on the routing matrix are halted.
NOTE: If you have a router with two Routing Engines and you want to shut the
power off to the router 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request system halt The following example, which assumes that the time is 5 PM (1700), illustrates
(In 2 Hours) three different ways to request the system to stop 2 hours from now:
request system halt To stop the system at 1:20 AM, enter the following command. Because 1:20 AM is
(at 1:20 AM) the next day, you must specify the absolute time.
Options filename—License key from a file or URL. Specify the filename or the URL where the
key is located.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (J-series routing platform only) Delete a license key. You can delete only one license
at a time.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (J-series routing platform only) Save installed license keys to a file or URL.
Options filename—License key from a file or URL. Specify the filename or the URL where the
key is located.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Syntax request system logout (pid pid | terminal terminal | user username)
<all>
Description Log out users from the router and the configuration database. If a user held the
configure exclusive lock, this command clears the exclusive lock.
Options 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.
all—(Optional) Log out all sessions owned by a particular PID, terminal session, or
user. (On a TX Matrix platform, this command is broadcast to all chassis.)
Additional Information For information about using the configure exclusive command, see the JUNOS
System Basics Configuration Guide.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request system logout user@host> request system logout user tammy all
Connection closed by foreign host.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description 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.
Options all-lcc—(Routing matrix only) (Optional) Schedule a partition of the hard disk for all
T640 routing nodes (or line-card chassis) connected to the TX Matrix platform
at their next reboot.
lcc number—(Routing matrix only) (Optional) Schedule a partition of the hard disk
on a specific T640 routing node that is connected to a TX Matrix platform at its
next reboot. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Schedule a partition of the hard disk for the
TX Matrix platform (or switch-card chassis).
Additional Information To immediately partition the hard disk, use the request system reboot command. To
cancel the partition request, use the request system partition abort command.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
all-lcc—(Optional) (Routing matrix only) Power off all T640 routing nodes (or
line-card chassis) connected to the TX Matrix platform.
lcc number—(Optional) (Routing matrix only) Power off a T640 routing node that is
connected to the TX Matrix platform. Replace number with a value from
0 through 3.
scc—(Optional) (Routing matrix only) Power off only the master Routing Engine or
the backup Routing Engine on the TX Matrix platform (or switch-card chassis).
If you issue the command from the master Routing Engine, the master SCC is
powered off. If you issue the command from the backup Routing Engine, the
backup SCC is powered off.
at time—(Optional) Time at which to power off the software, specified in one of the
following ways:
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.
in minutes—(Optional) Number of minutes from now to power off the software. This
option is an alias for the at +minutes option.
Additional Information On a routing matrix, if you issue the request system power-off command on the TX
Matrix master Routing Engine, all the master Routing Engines connected to the
routing matrix are powered off. If you issue this command on the backup Routing
Engine, all the backup Routing Engines connected to the routing matrix are
powered off.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request system user@host> request system power-off message “This router will be powered off in
power-off 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
This router will be powered off in 30 minutes. Please save your data and log out
immediately.
Shutdown NOW!
[pid 5177]
all-lcc—(Routing matrix only) (Optional) Reboot all T640 routing nodes (or line-card
chassis) connected to the TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Number of a T640 routing node that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
scc—(Routing matrix only) (Optional) Reboot the Routing Engine on the TX Matrix
platform (or switch-card chassis). If you issue the command from the re0, re0 is
rebooted; if you issue the command from re1, re1 is rebooted.
Additional Information Reboot requests are recorded in the system log files, which you can view with the
show log command. 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.
On a routing matrix, if you issue the request system reboot command on the master
Routing Engine, all the master Routing Engines connected to the routing matrix are
rebooted. If you issue this command on the backup Routing Engine, all the backup
Routing Engines connected to the routing matrix are rebooted.
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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request system reboot user@host> request system reboot at 2300 message “Maintenance time!”
(at 2300) Reboot the system ? [yes,no] (no) yes
shutdown: [pid 186]
*** System shutdown message from [email protected] ***
System going down at 23:00
request system reboot The following example, which assumes that the time is 5 PM (17:00), illustrates
(In 2 Hours) three different ways to request the system to reboot in two hours:
request system reboot To reboot the system at 1:20 AM, enter the following command. Because 1:20 AM
(At 1:20 AM) is the next day, you must specify the absolute time.
Description Back up the currently running and active file system partitions on the router to
standby partitions that are not running. Specifically, the root file system (/) is
backed up to /altroot, and /config is backed up to /altconfig. The root and /config
file systems are on the router’s flash drive, and the /altroot and /altconfig file
systems are on the router’s hard drive.
CAUTION: 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.
Options none—Back up the currently running and active file system partitions on the router
to standby partitions that are not running.
all-lcc—(Routing matrix only) (Optional) Archive data and executable areas for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Archive data and executable areas for
a specific T640 routing node (or line-card chassis) that is connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Archive data and executable areas for a
TX Matrix platform (or switch-card chassis).
config-size size—(J-series routing platform only) (Optional) Specify the size of the
config partition, in megabytes. The default value is 10 percent of physical
memory on the boot partition. The config partition is mounted on /config, and
the configuration files are stored in this partition. This option causes the boot
medium to be partitioned.
data-size size—(J-series routing platform only) (Optional) Specify the size of the data
partition, in megabytes. The default value is 0 MB. The data partition is
mounted on /data. This space is not used by the router, and can be used for
extra storage. This option causes the boot medium to be partitioned.
factory—(J-series routing platform only) (Optional) Copy only default files that were
loaded on the primary compact flash drive when it was shipped from the
factory, plus the rescue configuration if one has been set. After the boot
medium is created with the factory option, it can operate in only the primary
compact flash drive.
media type—(J-series routing platform only) (Optional) Specify the boot device the
software is copied to:
root-size size—(J-series routing platform only) (Optional) Specify the size of the root
partition, in megabytes. The default value is one-third of the physical memory
minus the config, data, and swap partitions. The root partition is mounted on /
and does not include configuration files. This option causes the boot medium to
be partitioned.
swap-size size—(J-series routing platform only) (Optional) Specify the size of the
swap partition, in megabytes. The default value is one-third of the physical
memory on a boot medium larger than 128 MB, or 0 MB on a smaller boot
device. The swap partition is used for swap files and software failure memory
snapshots. Software failure memory snapshots are saved to the boot medium
only if it is specified as the dump device in the system dump-device
configuration hierarchy. This option causes the boot medium to be partitioned.
Additional Information Before upgrading the software on the router, 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 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.
On a routing matrix, if you issue the request system snapshot command on the
master Routing Engine, all the master Routing Engines connected to the routing
matrix are backed up. If you issue this command on the backup Routing Engine, all
the backup Routing Engines connected to the routing matrix are backed up.
You cannot issue the request system snapshot command when you enable flash
disk mirroring. We recommend that you disable flash disk mirroring when you
upgrade or downgrade the software. For more information, see the JUNOS System
Basics Configuration Guide.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
lcc2-re0:
--------------------------------------------------------------------------
Copying '/' to '/altroot' .. (this may take a few minutes)
Copying '/config' to '/altconfig' .. (this may take a few minutes)
The following filesystems were archived: / /config
NOTE: On a J-series Services Router, when you install the software from a remote
location, the package is removed at the earliest opportunity in order to make room
for the installation to be completed. If you copy the software to a local directory on
the router and then install the new package, use the unlink option to achieve the
same effect and allow the installation to be completed.
reboot—(Optional) After adding the software package or bundle, reboot the system.
Additional Information Before upgrading the software on the router, 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 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:
By default, when you issue the request system software add package-name
command on a TX Matrix master Routing Engine, all the T640 master Routing
Engines that are connected to it are upgraded to the same version of software. If
you issue the same command on the TX Matrix backup Routing Engine, all the T640
backup Routing Engines that are connected to it are upgraded to the same version
of software.
List of Sample Output request system software add validate on page 374
Output Fields When you enter this command, you are provided feedback on the status of your
request.
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.
Options software-package—Software package or bundle name. You can delete any or all of
the following software bundles or packages:
Additional information Before upgrading the software on the router, 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 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.
List of Sample Output request system software delete jdocs on page 377
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request system The following example displays the system software packages before and after the
software delete jdocs jdocs package is deleted through the request system software delete command:
Comment:
JUNOS Base OS Software Suite [7.2R1.7]
Comment:
JUNOS Crypto Software Suite [7.2R1.7]
Comment:
JUNOS Online Documentation [7.2R1.7]
Comment:
JUNOS Kernel Software Suite [7.2R1.7]
...
Comment:
JUNOS Base OS Software Suite [7.2R1.7]
Comment:
JUNOS Crypto Software Suite [7.2R1.7]
Comment:
JUNOS Kernel Software Suite [7.2R1.7]
...
Description (J-series routing platform only) Delete the backup JUNOS software file (if it exists) to
free up compact flash drive space. After running this command, you can no longer
use the request system software rollback command to revert to the earlier version of
the JUNOS software.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Revert to the software that was loaded at the last successful request system software
add command.
Options none—(Routing matrix only) Revert to the set of software as of the last successful
request system software add on the TX Matrix platform and its attached T640
routing nodes.
lcc number—(Routing matrix only) (Optional) Attempt to roll back to the previous set
of packages on a T640 routing node (or line-card chassis) connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Attempt to roll back to the previous set of
packages on the TX Matrix platform (or switch-card chassis).
Additional Information On the J-series routing platform, you can use this command to roll back to a
previous software package when the current upgrade has been successful or has
failed. On M-series and T-series routing platforms, 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
/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 ...
Description Validate candidate software against the current configuration of the router.
scc—(Routing matrix only) (Optional) Validate the software bundle or package for
the TX Matrix platform (or switch-card chassis.
Additional Information By default, when you issue the request system software validate command on a TX
Matrix master Routing Engine, all the T640 master Routing Engines that are
connected to it are validated. If you issue the same command on the TX Matrix
backup Routing Engine, all the T640 backup Routing Engines that are connected to
it are upgraded to the same version of software.
List of Sample Output request system software validate (Successful Case) on page 381
request system software validate (Failure Case) on page 382
Output Fields When you enter this command, you are provided feedback on the status of your
request.
lcc0-re0:
gzip: stdin: not in gzip format
tar: child returned status 1
ERROR: Not a valid package: /var/tmp/test
Description Free storage space on the router by rotating log files and proposing a list of files for
deletion. User input is required for file deletion.
Options dry-run—(Optional) List files proposed for deletion (without deleting them).
Additional Information 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.
List of Sample Output request system storage cleanup dry-run on page 383,
request system storage cleanup on page 383
Output Fields When you enter this command, you are provided feedback on the status of your
request.
restart
Syntax restart
<adaptive-services | audit-process | chassis-control | class-of-service | disk-monitoring |
dynamic-flow-capture | ecc-error-logging | event-processing | firewall | interface-control |
ipsec-key-management | kernel-replication | l2-learning | l2tp-service | lacp |
mib-process | pgm | pic-services-logging | ppp | pppoe | redundancy-interface-process |
remote-operations | routing <logical-router logical-router-name> | sampling |
service-deployment | snmp>
<gracefully | immediately | soft>
Syntax restart
(Routing Matrix) <adaptive-services | audit-process | chassis-control | class-of-service | disk-monitoring |
dynamic-flow-capture | ecc-error-logging | event-processing | firewall | interface-control |
ipsec-key-management | kernel-replication | l2-learning | l2tp-service | lacp |
link-management | mib-process | pgm | pic-services-logging | ppp | pppoe |
redundancy-interface-process | remote-operations | routing <logical-router
logical-router-name> | sampling | service-deployment | snmp>
<all | all-lcc | lcc number>
<gracefully | immediately | soft>
Syntax restart
(J-series Routing <adaptive-services | audit-process | chassis-control | class-of-service | dhcp |
Platform) dialer-services | dlsw | event-processing | firewall | interface-control |
ipsec-key-management | isdn-signaling | l2-learning | l2tp-service | mib-process |
network-access-service | pgm | ppp | pppoe | remote-operations | routing <logical-router
logical-router-name> | sampling | service-deployment | snmp | usb-control |
web-management>
<gracefully | immediately | soft>
restart ! 385
JUNOS 8.1 System Basics and Services Command Reference
dhcp—(J-series routing platform 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.
dlsw—(J-series routing platform only) (Optional) Restart the data link switching
(DLSw) service.
l2tp-service—(Optional) (M10, M10i, and M7i routers only) Restart the Layer 2
Tunneling Protocol (L2TP) process, which establishes L2TP tunnels and
Point-to-Point Protocol (PPP) sessions through L2TP tunnels.
386 ! restart
Chapter 12: System Software Operational Mode Commands
snmp—(Optional) Restart the SNMP process, which provides the router’s SNMP
master agent.
all—(Routing matrix only) (Optional) Restart the software process on all chassis.
all-lcc—(Routing matrix only) (Optional) Restart the software process on all T640
routing nodes connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Restart the software process for a
specific T640 routing node that is connected to a TX Matrix platform. Replace
number with a value from 0 through 3.
restart ! 387
JUNOS 8.1 System Basics and Services Command Reference
Output Fields When you enter this command, you are provided feedback on the status of your
request.
388 ! restart
Chapter 12: System Software Operational Mode Commands
show arp
Description Display all entries in the Address Resolution Protocol (ARP) table. To display entries
for a particular logical router only, first enter the set cli logical-router
logical-router-name command, and then enter the show arp command.
Output Fields Table 86 describes the output fields for the show arp command. Output fields are
listed in the approximate order in which they appear.
TTE (expiration-time option only) Amount of time, in seconds, until ARP entry is set to
expire.
show configuration
Description Display the configuration that currently is running on the router, which is the last
committed configuration.
! chassis—Chassis configuration.
! class-of-service—Class-of-service configuration.
! firewall—Firewall configuration.
! groups—Configuration groups.
! interfaces—Interface configuration.
! security—Security configuration.
Additional Information 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.
Output Fields This command displays information about the current running configuration.
show host
Additional Information The show host command displays the raw data received from the DNS server.
Description Display Network Time Protocol (NTP) peers and their state.
Output Fields Table 87 describes the output fields for the show ntp associations command. Output
fields are listed in the approximate order in which they appear.
Description Display the values of internal variables returned by Network Time Protocol (NTP)
peers.
Additional Information 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 System Basics Configuration Guide.
Description Display the state and checksum values for file systems.
Options none—Display the state and checksum values for all file systems.
all-lcc—(Routing matrix only) (Optional) Display file system MD5 hash and
permissions information for all T640 routing nodes (or line-card chassis)
connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display file system MD5 hash and
permissions information for a specific T640 routing node (or line-card chassis)
that is connected to a TX Matrix platform. Replace number with a value from
0 through 3.
scc—(Routing matrix only) (Optional) Display file system MD5 hash and
permissions information for the TX Matrix platform (or switch-card chassis).
Additional Information To redirect the output to a file, issue the following command:
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.
By default, when you issue the show system audit command on a TX Matrix master
Routing Engine, the command is broadcast to all the T640 master Routing Engines
connected to it. If you issue the command on the TX Matrix backup Routing Engine,
the command is broadcast to all the T640 backup Routing Engines that are
connected to it.
# .
/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 \
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
# .
/set type=file uid=0 gid=0 mode=0555 nlink=1 flags=none
. type=dir nlink=20 size=512 time=1094982121.0
COPYRIGHT mode=0644 size=4735 time=986012708.0 \
md5digest=78396df1404ad742e6eb1be28f0cd63b
kernel type=link mode=0700 size=17 time=1090266262.0 \
link=/packages/jkernel
# ./altconfig
altconfig type=dir nlink=2 size=512 time=1089801320.0
# ./altconfig
..
# ./altroot
altroot type=dir nlink=2 size=512 time=1089801320.0
# ./altroot
..
# ./b
b type=dir mode=0755 nlink=2 size=512 time=1093961429.0
# ./b
..
# ./bin
/set type=file uid=0 gid=0 mode=0700 nlink=1 flags=none
bin type=dir mode=0755 nlink=2 size=512 time=1089843059.0
[ type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/test
cat type=link size=27 time=1090266270.0 \
link=/packages/mnt/jbase/bin/cat
chmod type=link size=29 time=1090266270.0 \
link=/packages/mnt/jbase/bin/chmod
cp type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/cp
csh type=link size=27 time=1090266270.0 \
link=/packages/mnt/jbase/bin/csh
date type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/date
dd type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/dd
df type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/df
echo type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/echo
ed type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/ed
expr type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/expr
hostname type=link size=32 time=1090266270.0 \
link=/packages/mnt/jbase/bin/hostname
kill type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/kill
ln type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/ln
ls type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/ls
mkdir type=link size=29 time=1090266270.0 \
link=/packages/mnt/jbase/bin/mkdir
mv type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/mv
ps type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/ps
pwd type=link size=27 time=1090266270.0 \
link=/packages/mnt/jbase/bin/pwd
rcp type=link size=27 time=1090266270.0 \
link=/packages/mnt/jbase/bin/rcp
red type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/ed
rm type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/rm
rmdir type=link size=29 time=1090266270.0 \
link=/packages/mnt/jbase/bin/rmdir
sh type=link size=26 time=1090266270.0 \
link=/packages/mnt/jbase/bin/sh
sleep type=link size=29 time=1090266270.0 \
link=/packages/mnt/jbase/bin/sleep
stty type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/stty
sync type=link size=28 time=1090266270.0 \
link=/packages/mnt/jbase/bin/sync
# ./boot
/set type=file uid=0 gid=0 mode=0444 nlink=1 flags=none
boot type=dir mode=0555 nlink=3 size=512 time=1095069935.0
boot0 size=512 time=1094978286.0 \
md5digest=6f780822dd4ae482a20462b66e542cca
boot1 mode=0555 size=512 time=1094978294.0 \
md5digest=8d112b09df342cd0b60fdb9bdcde8e07
boot2 mode=0555 size=7680 time=1094978294.0 \
md5digest=28eb58c4068c6b85717e1484f9e028e4
cdboot mode=0555 size=165888 time=1094978298.0 \
md5digest=1474c6b800dfc82ba552d7c36116d07d
kgzldr.o size=5996 time=1094982121.0 \
md5digest=c53dc948eb07e2ea4eb0413e4c4634a3
loader mode=0555 size=163840 time=1094978298.0 \
md5digest=82d9dc2d31033476bfb61bb7264c4fed
loader.4th size=9237 time=986013631.0 \
md5digest=43144391465ad50267d31e0a320be1de
...
Description Display initial messages generated by the system kernel upon startup. These
messages are the contents of /var/run/dmesg.boot.
Options all-lcc—(Routing matrix only) (Optional) Display boot time messages for all T640
routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display boot time messages for a
specific T640 routing node connected to a TX Matrix platform. Replace number
with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display boot time messages for the TX Matrix
platform (or switch-card chassis).
Additional information By default, when you issue the show system boot-messages command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
[email protected]:/build/benten-b/7.0/20040912.0/obj-i386/sys/compile/J
UNIPER
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 601368936 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x387f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,
PSE36,PN,MMX,FXSR,SSE>
real memory = 2147467264 (2097136K bytes)
sio0: gdb debugging port
avail memory = 2084040704 (2035196K bytes)
Preloaded elf kernel "kernel" at 0xc06d9000.
DEVFS: ready for devices
Pentium Pro MTRR support enabled
md0: Malloc disk
DRAM Data Integrity Mode: ECC Mode with h/w scrubbing
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcic-pci0: <TI PCI-1410 PCI-CardBus Bridge> irq 15 at device 1.0 on pci0
pcic-pci0: TI12XX PCI Config Reg: [pwr save][pci only]
fxp0: <Intel Embedded 10/100 Ethernet> port 0x1000-0x103f mem
0xfb800000-0xfb81ffff,0xfb820000-0xfb820fff irq 9 at device 3.0 on pci0
fxp1: <Intel Embedded 10/100 Ethernet> port 0x1040-0x107f mem
0xfb840000-0xfb85ffff,0xfb821000-0xfb821fff irq 11 at device 4.0 on pci0
...
Description 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, as
well as the routing and management traffic from IP (that is, from OSPF, BGP, SNMP,
ping operations, and so on).
Options all-lcc—(Routing matrix only) (Optional) Show buffer statistics for all T640 routing
nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Show buffer statistics for a specific
T640 routing node (or line-card chassis) that is connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Show buffer statistics for the TX Matrix
platform (or switch-card chassis).
Additional Information By default, when you issue the show system buffers command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 88 describes the output fields for the show system buffers command. Output
fields are listed in the approximate order in which they appear.
Description Display the pending commit operation (if any) and the commit history.
Output Fields Table 89 describes the output fields for the show system commit command. Output
fields are listed in the approximate order in which they appear.
Description Display directory and number of files queued for archival transfer.
Description 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.
Options none—Display information about all active IP sockets on the Routing Engine.
all-lcc—(Routing matrix only) (Optional) Display system connection activity for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system connection activity for
a specific T640 routing node that is connected to a TX Matrix platform. Replace
number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system connection activity for the
TX Matrix platform (or switch-card chassis).
Additional information By default, when you issue the show system connections command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 90 describes the output fields for the show system connections command.
Output fields are listed in the approximate order in which they appear.
all-lcc—(Routing matrix only) (Optional) Display directory information for all T640
routing nodes (or line-card chassis) connected to a TX Matrix platform.
List of Sample Output show system directory-usage scc (Routing Matrix) on page 415
Output Fields Table 91 describes the output fields for the show system directory-usage command.
Output fields are listed in the approximate order in which they appear.
89K /var/tmp/instmp.oMIDbl/bin
/var/tmp/instmp.byhMjR
4.6M /var/tmp/instmp.byhMjR/packages
/var/tmp/instmp.6fqHf3
1.7M /var/tmp/instmp.6fqHf3/packages
/var/tmp/instmp.mljECe
4.6M /var/tmp/instmp.mljECe/packages
Output Fields Table 92 lists the output fields for the show system firmware command. Output
fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display licenses and information about how they are
used.
keys—(Optional) Display a list of license keys. Use this information to verify that
each expected license key is present.
Output Fields Table 93 lists the output fields for the show system license command. Output fields
are listed in the approximate order in which they appear.
License usage:
Licenses Licenses Licenses
Feature name used installed needed
j-flow 0 1 0
bgp-reflection 1 1 0
dlsw 1 1 0
Licenses installed:
License identifier: G03000002223
State: valid
License version: 2
Valid for device: JN001875AB
Features:
bgp-reflection - Border Gateway Protocol route reflection
Description Display information about software processes that are running on the router and
that have controlling terminals.
Additional information By default, when you issue the show system processes command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 94 describes the output fields for the show system processes command.
Output fields are listed in the approximate order in which they appear.
Mem: 25M Active, 3976K Inact, 19M Wired, 8346K Buf, 202M Free
Swap: 528M Total, 64K Used, 528M Free
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 COMMAND
544 root 30 0 604K 768K RUN 0:00 0.00% 0.00% top
3 root 28 0 0K 12K psleep 0:00 0.00% 0.00% vmdaemon
4 root 28 0 0K 12K update 0:03 0.00% 0.00% update
528 aviva 18 0 660K 948K pause 0:00 0.00% 0.00% tcsh
204 root 18 0 300K 544K pause 0:00 0.00% 0.00% csh
131 root 18 0 332K 532K pause 0:00 0.00% 0.00% cron
186 root 18 0 196K 68K pause 0:00 0.00% 0.00% watchdog
27 root 10 0 512M 16288K mfsidl 0:00 0.00% 0.00% mount_mfs
1 root 10 0 620K 344K wait 0:00 0.00% 0.00% init
304 root 3 0 884K 900K ttyin 0:00 0.00% 0.00% bash
200 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% getty
203 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% getty
202 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% getty
201 root 3 0 180K 540K ttyin 0:00 0.00% 0.00% getty
194 root 2 0 2248K 1640K select 0:11 0.00% 0.00% rpd
205 root 2 0 964K 800K select 0:12 0.00% 0.00% tnp.chassisd
189 root 2 -12 352K 740K select 0:03 0.00% 0.00% xntpd
114 root 2 0 296K 612K select 0:00 0.00% 0.00% amd
188 root 2 0 780K 600K select 0:00 0.00% 0.00% dcd
527 root 2 0 176K 580K select 0:00 0.00% 0.00% rlogind
195 root 2 0 212K 552K select 0:00 0.00% 0.00% inetd
Mem: 25M Active, 3976K Inact, 19M Wired, 8346K Buf, 202M Free
Swap: 528M Total, 64K Used, 528M Free
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
527 root 2 0 176K 580K select 0:00 0.04% 0.04% rlogind
543 root 30 0 604K 768K RUN 0:00 0.00% 0.00% top
Options all-lcc—(Routing matrix only) (Optional) Display system queue statistics for all LCC
chassis attached to the routing matrix.
lcc number—(Routing matrix only) (Optional) Display queue statistics for a specific
T640 routing node that is connected to a TX Matrix platform. Replace number
with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display queue statistics for the TX Matrix
platform.
Additional Information By default, when you issue the show system queues command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 95 lists the output fields for the show system queues command. Output fields
are listed in the approximate order in which they appear.
scc—(Routing matrix only) (Optional) Display halt or reboot request information for
the TX Matrix platform (or switch-card chassis).
Additional information By default, when you issue the show system reboot command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
lcc2-re0:
--------------------------------------------------------------------------
No shutdown/reboot scheduled.
Description (J-series routing platform only) Display Dynamic Host Configuration Protocol
(DHCP) server client binding information.
List of Sample Output show system services dhcp binding on page 432
show system services dhcp binding address on page 432
show system services dhcp binding address detail on page 432
Output Fields Table 96 describes the output fields for the show system services dhcp binding
command. Output fields are listed in the approximate order in which they appear.
show system services user@host> show system services dhcp binding 192.168.1.3
dhcp binding address
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 30 aced-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 user@host> show system services dhcp binding 192.168.1.3 detail
dhcp binding address
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 DHCP
Obtained at 2004-05-02 13:01:42 PDT
Expires at 2004-05-03 13:01:42 PDT
State active
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
Description (J-series routing platform only) Display Dynamic Host Configuration Protocol
(DHCP) client-detected conflicts for IP addresses.
Additional Information When a conflict is detected, the DHCP server removes the address from the address
pool.
List of Sample Output show system services dhcp conflict on page 433
Output Fields Table 97 describes the output fields for the show system services dhcp conflict
command. Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) 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.
List of Sample Output show system services dhcp global on page 434
Output Fields Table 98 describes the output fields for the show system services dhcp global
command. Output fields are listed in the approximate order in which they appear.
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
Description (J-series routing platform only) Display Dynamic Host Configuration Protocol
(DHCP) server IP address pools.
List of Sample Output show system services dhcp pool on page 435
show system services dhcp pool subnet-address on page 436
show system services dhcp pool subnet-address detail on page 436
Output Fields Table 99 describes the output fields for the show system services dhcp pool
command. Output fields are listed in the approximate order in which they appear.
show system services user@host> show system services dhcp pool 3.3.3.0/24
dhcp pool
subnet-address Pool information:
Subnet 3.3.3.0/24
Address range 3.3.3.2 - 3.3.3.254
Addresses assigned 2/253
show system services user@host> show system services dhcp pool 3.3.3.0/24 detail
dhcp pool
subnet-address detail Pool information:
Subnet 3.3.3.0/24
Address range 3.3.3.2 - 3.3.3.254
Addresses assigned 2/253
Active: 1, Excluded: 1
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
Description (J-series routing platform only) Display Dynamic Host Configuration Protocol
(DHCP) server statistics.
List of Sample Output show system services dhcp statistics on page 437
Output Fields Table 100 describes the output fields for the show system services dhcp statistics
command. Output fields are listed in the approximate order in which they appear.
Messages received Number of the following message types sent from DHCP clients and
received by the DHCP server:
! BOOTREQUEST
! DHCPDECLINE
! DHCPDISCOVER
! DHCPINFORM
! DHCPRELEASE
! DHCPREQUEST
Packets dropped:
Total 0
Bad hardware address 0
Bad opcode 0
Invalid server address 0
No available addresses 0
No interface match 0
No routing instance match 0
No valid local address 0
Packet too short 0
Read error 0
Send error 0
Messages received:
BOOTREQUEST 0
DHCPDECLINE 0
DHCPDISCOVER 0
DHCPINFORM 0
DHCPRELEASE 0
DHCPREQUEST 0
Messages sent:
BOOTREPLY 0
DHCPACK 0
DHCPOFFER 0
DHCPNAK 0
Description 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.
lcc number—(Routing matrix only) (Optional) Display the system software running
on a T640 routing node (or line-card chassis) that is connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
backup—(J-series routing platform only) (Optional) Display the status of old system
software packages only.
Comment:
JUNOS Base OS Software Suite [7.2R1.7]
Comment:
JUNOS Crypto Software Suite [7.2R1.7]
Comment:
JUNOS Online Documentation [7.2R1.7]
Comment:
JUNOS Kernel Software Suite [7.2R1.7]
Comment:
JUNOS Packet Forwarding Engine Support (M20/M40) [7.2R1.7]
Comment:
JUNOS Routing Software Suite [7.2R1.7]
Comment:
JUNOS Base OS boot [7.2R1.7]
all-lcc—(Routing matrix only) (Optional) Display system statistics for a protocol for
all T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
scc—(Routing matrix only) (Optional) Display system statistics for a protocol for the
TX Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
echo reply: 75
0 messages with bad code fields
0 messages less than the minimum length
0 messages with bad checksum
0 messages with bad source address
0 messages with bad length
0 echo drops with broadcast or multicast destination address
0 timestamp drops with broadcast or multicast destination address
Input histogram:
echo: 75
router advertisement: 130
75 message responses generated
tcp:
3844 packets sent
3618 data packets (1055596 bytes)
0 data packets (0 bytes) retransmitted
0 resends initiated by MTU discovery
205 ack-only packets (148 packets delayed)
0 URG only packets
0 window probe packets
0 window update packets
1079 control packets
5815 packets received
3377 acks (for 1055657 bytes)
24 duplicate acks
0 acks for unsent data
2655 packets (15004 bytes) received in-sequence
1 completely duplicate packet (0 bytes)
0 old duplicate packets
0 packets with some dup. data (0 bytes duped)
0 out-of-order packets (0 bytes)
0 packets (0 bytes) of data after window
0 window probes
7 window update packets
0 packets received after close
0 discarded for bad checksums
0 discarded for bad header offset fields
0 discarded because packet too short
1 connection request
32 connection accepts
0 bad connection attempts
0 listen queue overflows
33 connections established (including accepts)
30 connections closed (including 0 drops)
27 connections updated cached RTT on close
27 connections updated cached RTT variance on close
0 connections updated cached ssthresh on close
0 embryonic connections dropped
3374 segments updated rtt (of 3220 attempts)
0 retransmit timeouts
0 connections dropped by rexmit timeout
0 persist timeouts
0 connections dropped by persist timeout
344 keepalive timeouts
0 keepalive probes sent
0 connections dropped by keepalive
1096 correct ACK header predictions
1314 correct data packet header predictions
32 syncache entries added
0 retransmitted
0 dupsyn
0 dropped
32 completed
0 bucket overflow
0 cache overflow
0 reset
0 stale
0 aborted
0 badack
0 unreach
0 zone failures
0 cookies sent
0 cookies received
0 ACKs sent in response to in-window but not exact RSTs
0 ACKs sent in response to in-window SYNs on established connections
0 rcv packets dropped by TCP due to bad address
0 out-of-sequence segment drops due to insufficient memory
1058 RST packets
0 ICMP packets ignored by TCP
0 send packets dropped by TCP due to auth errors
0 rcv packets dropped by TCP due to auth errors
udp:
3658884 datagrams received
0 with incomplete header
0 with bad data length field
0 with bad checksum
3657342 dropped due to no socket
3657342 broadcast/multicast datagrams dropped due to no socket
0 dropped due to full socket buffers
0 not for hashed pcb
4291311496 delivered
1551 datagrams output
ipsec:
0 inbound packets processed successfully
0 inbound packets violated process security policy
0 inbound packets with no SA available
0 invalid inbound packets
0 inbound packets failed due to insufficient memory
0 inbound packets failed getting SPI
0 inbound packets failed on AH replay check
0 inbound packets failed on ESP replay check
0 inbound AH packets considered authentic
0 inbound AH packets failed on authentication
0 inbound ESP packets considered authentic
0 inbound ESP packets failed on authentication
0 outbound packets processed successfully
0 outbound packets violated process security policy
0 outbound packets with no SA available
0 invalid outbound packets
0 outbound packets failed due to insufficient memory
0 outbound packets with no route
igmp:
17186 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent
arp:
44181302 datagrams received
2 ARP requests received
2028 ARP replies received
3156 resolution requests received
0 packets reconstructed
0 packets destined to dead nexthop
0 packets discarded due to no route
0 Error pdu rate drops
0 ER pdu generation failure
esis:
0 total pkts received
0 total packets consumed by protocol
0 pdus received with bad checksum
0 pdus received with bad version number
0 pdus received with bad type field
0 short pdus received
0 bogus sdl size
0 bad header length
0 unknown or unsupported protocol
0 no free memory in socket buffer
0 send packets discarded
0 sbappend failure
0 mcopy failure
0 ISO family not configured
tnp:
146776365 unicast packets received
0 broadcast packets received
0 fragmented packets received
0 hello packets dropped
0 fragments dropped
0 fragment reassembly queue flushes
0 hello packets received
0 control packets received
49681642 rdp packets received
337175 udp packets received
96757548 tunnel packets received
0 input packets discarded with no protocol
Options all-lcc—(Routing matrix only) (Optional) Display system-wide ARP statistics for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for ARP for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for ARP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics arp command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for CLNL for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for CLNL for
a specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for CLNL for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics clnl command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
0 packets reconstructed
0 packets destined to dead nexthop
0 packets discarded due to no route
0 Error pdu rate drops
0 ER pdu generation failure
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for ES-IS for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for ES-IS for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for ES-IS for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics esis command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for ICMP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for ICMP for
a specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for ICMP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics icmp command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Description Display system-wide Internet Control Message Protocol for IPv6 (ICMP6) statistics.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for ICMPv6 for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for ICMPv6
for a specified T640 routing node (or line-card chassis) connected to a TX
Matrix platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for ICMPv6 for the
TX Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics icmpv6 command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for IGMP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for IGMP for
a specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for IGMP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics igmp command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for IPv4 for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for IPv4 for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for IPv4 for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics ip command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for IPv6 for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for IPv6 for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for IPv6 for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics ip6 command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Mbuf statistics:
0 packets whose headers are not continuous
0 tunneling packets that can't find gif
0 packets discarded due to too may headers
0 failures of source address selection
0 forward cache hit
0 forward cache miss
0 packets destined to dead next hop
0 option packets dropped due to rate limit
0 packets dropped (src and int don't match)
0 packets dropped due to bad protocol
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for MPLS for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for MPLS for
a specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for MPLS for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics mpls command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for RDP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for RDP for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for RDP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics rdp command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for TCP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for TCP for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for TCP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics tcp command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for TNP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for TNP for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for TNP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics tnp command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for TUDP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for TUDP for
a specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for TUDP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics tudp command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for UDP for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for UDP for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for UDP for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics udp command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Options all-lcc—(Routing matrix only) (Optional) Display system statistics for VPLS for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display system statistics for VPLS for a
specified T640 routing node (or line-card chassis) connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display system statistics for VPLS for the TX
Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show system statistics vpls command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Description Display statistics about the amount of free disk space in the router’s file systems.
Options none—Display standard information about the amount of free disk space in the
router’s file systems.
all-lcc—(Routing matrix only) (Optional) Display system storage statistics for all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Display storage statistics for a specific
T640 routing node (or line-card chassis) that is connected to a TX Matrix
platform. Replace number with a value from 0 through 3.
scc—(Routing matrix only) (Optional) Display storage statistics for the TX Matrix
platform (or switch-card chassis).
Additional Information By default, when you issue the show system storage command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 101 describes the output fields for the show system storage command. Output
fields are listed in the approximate order in which they appear.
Description Display whether graceful 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.
Options all-lcc—(Routing matrix only) (Optional) Display Routing Engine graceful switchover
information for all T640 routing nodes (or line-card chassis) connected to a
TX Matrix platform.
Additional information By default, when you issue the show system switchover command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 102 describes the output fields for the show system switchover command.
Output fields are listed in the approximate order in which they appear.
lcc2-re0:
--------------------------------------------------------------------------
Multichassis replication: On
Configuration database: Ready
Kernel database: Ready
Description Display the current time and information about how long the router, router
software, and routing protocols have been running.
Options all-lcc—(Routing matrix only) (Optional) Show the time since the system booted and
processes started on all T640 routing nodes (or line-card chassis) connected to
a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Show the time since the system
booted and processes started on a specific T640 routing node (or line-card
chassis) that is connected to a TX Matrix platform. Replace number with a value
from 0 through 3.
scc—(Routing matrix only) (Optional) Show the time since the system booted and
processes started on the TX Matrix platform (or switch-card chassis).
Additional information By default, when you issue the show system uptime command on a TX Matrix
master Routing Engine, the command is broadcast to all the T640 master Routing
Engines connected to it. Likewise, if you issue the same command on the TX Matrix
backup Routing Engine, the command is broadcast to all the T640 backup Routing
Engines that are connected to it.
Output Fields Table 103 describes the output fields for the show system uptime command. Output
fields are listed in the approximate order in which they appear.
lcc2-re0:
--------------------------------------------------------------------------
Current time: 2004-09-13 09:55:35 PDT
System booted: 2004-09-12 03:23:43 PDT (1d 06:31 ago)
Last configured: 2004-09-13 03:05:36 PDT (06:49:59 ago) by root
9:55AM PDT up 1 day, 6:32, 1 user, load averages: 0.02, 0.01, 0.00
Description List information about the users who are currently logged in to the router.
Options none—List information about the users who are currently logged in to the router.
all-lcc—(Routing matrix only) (Optional) Show users who are currently logged on all
T640 routing nodes (or line-card chassis) connected to a TX Matrix platform.
lcc number—(Routing matrix only) (Optional) Show users who are currently logged
onto a specific T640 routing node (or line-card chassis) that is connected to a
TX Matrix platform. Replace number with a value from 0 through 3.
Additional Information By default, when you issue the show system users command on a TX Matrix master
Routing Engine, the command is broadcast to all the T640 master Routing Engines
connected to it. Likewise, if you issue the same command on the TX Matrix backup
Routing Engine, the command is broadcast to all the T640 backup Routing Engines
that are connected to it.
Output Fields Table 104 describes the output fields for the show system users command. Output
fields are listed in the approximate order in which they appear.
show system users lcc user@host> show system users lcc 2 no-resolve
no-resolve
(Routing Matrix) lcc2-re0:
--------------------------------------------------------------------------
10:34AM PDT up 1 day, 7:11, 5 users, load averages: 0.03, 0.01, 0.00
USER TTY FROM LOGIN@ IDLE WHAT
root d0 - 3:21AM 7:12 /bin/csh
regress p0 scc-re0 10:15AM - telnet hostA
regress p1 scc-re0 10:16AM - telnet hostA
regress p2 scc-re0 10:19AM - telnet hostA
regress p3 scc-re0 10:24AM - telnet hostA
Description Display the usage of JUNOS kernel memory listed first by size of allocation and then
by type of usage. Use show system virtual-memory for troubleshooting with Juniper
Networks Customer Support.
Options all-lcc—(Routing matrix only) (Optional) Display kernel dynamic memory usage
information for all T640 routing nodes (or line-card chassis) connected to a
TX Matrix platform.
Additional Information By default, when you issue the show system virtual-memory command on a TX
Matrix master Routing Engine, the command is broadcast to all the T640 master
Routing Engines connected to it. Likewise, if you issue the same command on the
TX Matrix backup Routing Engine, the command is broadcast to all the T640
backup Routing Engines that are connected to it.
Output Fields Table 105 lists the output fields for the show system virtual-memory command.
Output fields are listed in the approximate order in which they appear.
64K 20 0 22 5 0
128K 5 0 5 5 0
256K 2 0 2 5 0
512K 1 0 1 5 0
...
...
show task
Options none—Display all routing protocol tasks on the Routing Engine on all logical routers.
Output Fields Table 106 describes the output fields for the show task command. Output fields are
listed in the approximate order in which they appear.
show task io
Description Display I/O statistics for routing protocol tasks on the Routing Engine.
Options none—Display I/O statistics for routing protocol tasks on the Routing Engine on all
logical routers.
Output Fields Table 107 describes the output fields for the show task io command. Output fields
are listed in the approximate order in which they appear.
KRT 0 0 0 0 0
Redirect 0 0 0 0 0
...
Description Display memory utilization for routing protocol tasks on the Routing Engine.
Options none—Display standard information about memory utilization for routing protocol
tasks on the Routing Engine on all logical routers.
brief | detail | history | summary—(Optional) Display the specified level of output. Use
the history option to display a history of memory utilization information.
Output Fields Table 108 describes the output fields for the show task memory command. Output
fields are listed in the approximate order in which they appear.
cos_nhm_nh 8 12 1 12 1 12
sockaddr_un.tag 8 12 3 36 4 48
gw_entry_list 8 12 1 12 1 12
bgp_riblist_01 8 12 1 12 2 24
ospf_intf_ev 8 12 - - 6 72
krt_remnant_rt 8 12 T - - 5 60
...
-------------------------------------------------------------------------
164108 221552
show version
Description Display the hostname and version information about the software running on the
router.
Options none—Display standard information about the hostname and version of the
software running on the router.
lcc number—(Optional) Display the hostname and version information about the
software running on a T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
scc—(Optional) Display the hostname and version information about the software
running on the TX Matrix platform (or switch-card chassis).
Additional Information By default, when you issue the show version command on a TX Matrix master
Routing Engine, the command is broadcast to all the T640 master Routing Engines
connected to it. Likewise, if you issue the same command on the TX Matrix backup
Routing Engine, the command is broadcast to all the T640 backup Routing Engines
that are connected to it.
Description Display the hostname and version information about the software running on a
routing platform with two Routing Engines.
List of Sample Output show version invoke-on all-routing-engines (Routing Matrix) on page 498
show version invoke-on other-routing-engine (Routing Matrix) on page 500
scc-re1:
--------------------------------------------------------------------------
Hostname: bob1
Model: TX Matrix
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
JUNOS Support Tools Package [7.1-20041025.1]
lcc0-re0:
--------------------------------------------------------------------------
Hostname: cas
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc0-re1:
--------------------------------------------------------------------------
Hostname: cas1-lcc0
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc1-re0:
--------------------------------------------------------------------------
Hostname: jas
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc1-re1:
--------------------------------------------------------------------------
Hostname: jas1
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc2-re0:
--------------------------------------------------------------------------
Hostname: dew
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc2-re1:
--------------------------------------------------------------------------
Hostname: dew1
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc3-re0:
--------------------------------------------------------------------------
Hostname: wa
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc3-re1:
--------------------------------------------------------------------------
Hostname: wa1
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041025.1]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc0-re1:
--------------------------------------------------------------------------
Hostname: cas1-lcc0
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc1-re1:
--------------------------------------------------------------------------
Hostname: jas1
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc2-re1:
--------------------------------------------------------------------------
Hostname: dew1
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041024.0]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
lcc3-re1:
--------------------------------------------------------------------------
Hostname: wa1
Model: t640
JUNOS Base OS boot [7.1-20041024.0]
JUNOS Base OS Software Suite [7.1-20041025.1]
JUNOS Kernel Software Suite [7.1-20041024.0]
JUNOS Packet Forwarding Engine Support (T-Series) [7.1-20041024.0]
JUNOS Routing Software Suite [7.1-20041024.0]
JUNOS Online Documentation [7.1-20041024.0]
JUNOS Crypto Software Suite [7.1-20041024.0]
start shell
Description Exit from the CLI environment and create a UNIX-level shell.
Additional Information When you are in the shell, the shell prompt has the following format. Note that a
space appears after the percent sign (%).
username@hostname%
root@router%
Output Fields When you enter this command, you are provided feedback on the status of your
request.
test configuration
Description 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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Table 109 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot class of service (CoS). Commands are listed in
alphabetical order.
Task Command
Display the entire CoS configuration, including show class-of-service on page 509
system-chosen defaults.
(J-series routing platform only) Display trigger show class-of-service adaptive-shaper on page 511
points and associated rates for CoS adaptive
shapers.
For each CoS classifier, display the mapping of show class-of-service classifier on page 512
code point value to forwarding class and loss
priority.
Display the mapping of CoS code point aliases to show class-of-service code-point-aliases on page 514
corresponding bit patterns.
Display data points for each CoS random early show class-of-service drop-profile on page 515
detection (RED) drop profile.
(M320 routers and T-series routing platform only) show class-of-service fabric scheduler-map on page 516
Display the mapping of CoS schedulers to switch
fabric traffic priorities and a summary of
scheduler parameters for each priority.
(M320 routers and T-series routing platform only) show class-of-service fabric statistics on page 517
Display CoS switch fabric queue statistics.
Display the mapping of forwarding class names to show class-of-service forwarding-class on page 519
queue numbers.
Display entire CoS configuration as it exists in the show class-of-service forwarding-table on page 520
forwarding table.
Display the mapping of code point value to queue show class-of-service forwarding-table classifier on page 522
number and loss priority for each classifier as it
exists in the forwarding table.
For each logical interface, display either the table show class-of-service forwarding-table classifier mapping on page 523
index of the classifier for a given code point type
or the queue number (if it is a fixed classification)
in the forwarding table.
! 507
JUNOS 8.1 System Basics and Services Command Reference
Task Command
Display the data points of all random early show class-of-service forwarding-table drop-profile on page 524
detection (RED) drop profiles as they exist in the
forwarding table.
(M320 routers and T-series routing platform only) show class-of-service forwarding-table fabric scheduler-map on page 526
Display the scheduler map information as it exists
in the forwarding table for switch fabric.
(J-series routing platform only) Display the show class-of-service forwarding-table loss-priority-map on page 527
mapping of code point value to loss priority as it
exists in the forwarding table.
(J-series routing platform only) For each logical show class-of-service forwarding-table loss-priority-map mapping on page 528
interface, display the loss priority table index.
Display mapping of queue number and loss show class-of-service forwarding-table rewrite-rule on page 529
priority to code point value for each rewrite rule as
it exists in the forwarding table.
For each logical interface, display the table show class-of-service forwarding-table rewrite-rule mapping on page 530
identifier of the rewrite rule map for each code
point type.
For each physical interface, display the scheduler show class-of-service forwarding-table scheduler-map on page 531
map information as it exists in the forwarding
table.
For Adaptive Services (AS) PIC link services IQ show class-of-service fragmentation-map on page 533
interfaces (lsq) only, display fragmentation
properties for specific forwarding classes.
Display the logical and physical interface show class-of-service interface on page 534
associations for the classifier, rewrite rules, and
scheduler map objects.
(J-series routing platform only) Display mapping of show class-of-service loss-priority-map on page 536
code point value to loss priority.
Display the mapping of forwarding classes and show class-of-service rewrite-rule on page 537
loss priority to code point values.
(M-series and T-series routing platforms only) show class-of-service routing-instance on page 539
Display mapping of CoS objects to routing
instances.
Display mapping of schedulers to forwarding show class-of-service scheduler-map on page 540
classes and a summary of scheduler parameters
for each entry.
For Gigabit Ethernet IQ and Channelized IQ PICs show class-of-service traffic-control-profile on page 542
only, display traffic shaping and scheduling
profiles.
(J-series routing platform only) Display virtual show class-of-service virtual-channel on page 543
channel information.
(J-series routing platform only) Display virtual show class-of-service virtual-channel-group on page 544
channel group information.
NOTE: For information about how to configure CoS, see the JUNOS Class of Service
Configuration Guide. For information about the related show interfaces queue
command, see the JUNOS Interfaces Command Reference.
508 !
Chapter 13: Class-of-Service Operational Mode Commands
show class-of-service
Output Fields See the output field descriptions for the remaining commands in this chapter.
Description (J-series routing platform only) Display trigger points and associated rates for
class-of-service (CoS) adaptive shapers.
Output Fields Table 110 describes the output fields for the show class-of-service adaptive-shaper
command. Output fields are listed in the approximate order in which they appear.
Description For each class-of-service (CoS) classifier, display the mapping of code point value to
forwarding class and loss priority.
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.
List of Sample Output show class-of-service classifier type ieee-802.1 on page 513
Output Fields Table 111 describes the output fields for the show class-of-service classifier
command. Output fields are listed in the approximate order in which they appear.
Description Display the mapping of class-of-service (CoS) code point aliases to corresponding
bit patterns.
Output Fields Table 112 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.
Description Display data points for each class-of-service (CoS) random early detection (RED)
drop profile.
Output Fields Table 113 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.
Description (M320 routers and T-series routing platform only) Display the mapping of
class-of-service (CoS) schedulers to switch fabric traffic priorities and a summary of
scheduler parameters for each priority.
Output Fields Table 114 describes the output fields for the show class-of-service fabric
scheduler-map command. Output fields are listed in the approximate order in which
they appear.
Description (M320 routers and T-series routing platform only) Display class-of-service (CoS)
switch fabric queue statistics.
source fpc-number—(Optional) Display details for the specified source FPC. The FPC
number is a value from 0 through 7.
Output Fields Table 115 describes the output fields for the show class-of-service fabric statistics
command. Output fields are listed in the approximate order in which they appear.
Output Fields Table 116 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.
Description Display the entire class-of-service (CoS) configuration as it exists in the forwarding
table. Executing this command is equivalent to executing all show class-of-service
forwarding-table commands in succession.
Options lcc number—(Routing matrix only) (Optional) Display the forwarding table
configuration for a specific T640 routing node (or line-card chassis) that is
connected to a TX Matrix platform. Replace number with a value from
0 through 3.
Output Fields See the output field descriptions for the remaining show class-of-service
forwarding-table commands in this chapter.
Table Index/
Interface Index Q num Table type
sp-0/0/0.1001 66 11 IPv4 precedence
sp-0/0/0.2001 67 11 IPv4 precedence
sp-0/0/0.16383 68 11 IPv4 precedence
fe-0/0/0.0 69 11 IPv4 precedence
Priority low
PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-low: 1
Entry 1 (Scheduler index: 18, Forwarding-class #: 3):
Tx rate: 0 Kb (5%), Buffer size: 5 percent
Priority low
PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-low: 1
...
Description Display the mapping of code point value to queue number and loss priority for each
classifier as it exists in the forwarding table.
Output Fields Table 117 describes the output fields for the show class-of-service forwarding-table
classifier command. Output fields are listed in the approximate order in which they
appear.
Description 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.
List of Sample Output show class-of-service forwarding -table classifier mapping on page 523
Output Fields Table 118 describes the output fields for the show class-of-service forwarding-table
classifier mapping command. Output fields are listed in the approximate order in
which they appear.
Description Display the data points of all random early detection (RED) drop profiles as they
exist in the forwarding table.
Output Fields Table 119 describes the output fields for the show class-of-service forwarding-table
drop-profile command. Output fields are listed in the approximate order in which
they appear.
Description (M320 routers and T-series routing platform only) Display the scheduler map
information as it exists in the forwarding table for switch fabric.
Additional Information For information about how PLP priority is assigned to packets, see the JUNOS Class
of Service Configuration Guide.
List of Sample Output show class-of-service forwarding-table fabric scheduler-map on page 526
Output Fields Table 120 describes the output fields for the show class-of-service forwarding-table
fabric scheduler-map command. Output fields are listed in the approximate order in
which they appear.
Description (J-series routing platform only) Display the mapping of code point value to loss
priority as it exists in the forwarding table.
Output Fields Table 121 describes the output fields for the show class-of-service forwarding-table
loss-priority-map command. Output fields are listed in the approximate order in
which they appear.
Description (J-series routing platform only) For each logical interface, display the loss priority
table index.
List of Sample Output show class-of-service forwarding-table loss-priority-map mapping on page 528
Output Fields Table 122 describes the output fields for the show class-of-service forwarding-table
loss-priority-map mapping command. Output fields are listed in the approximate
order in which they appear.
Description Display mapping of queue number and loss priority to code point value for each
rewrite rule as it exists in the forwarding table.
Output Fields Table 123 describes the output fields for the show class-of-service forwarding-table
rewrite-rule command. Output fields are listed in the approximate order in which
they appear.
Description For each logical interface, display the table identifier of the rewrite rule map for
each code point type.
List of Sample Output show class-of-service forwarding-table rewrite-rule mapping on page 530
Output Fields Table 124 describes the output fields for the show class-of-service forwarding-table
rewrite-rule mapping command. Output fields are listed in the approximate order in
which they appear.
Description For each physical interface, display the scheduler map information as it exists in the
forwarding table.
Output Fields Table 125 describes the output fields for the show class-of-service forwarding-table
scheduler-map command. Output fields are listed in the approximate order in which
they appear.
Interface: at-6/1/0 (Index: 10, Map index: 17638, Num of queues: 2):
Entry 0 (Scheduler index: 6090, Forwarding-class #: 0):
Traffic chunk: Max = 0 bytes, Min = 0 bytes
Tx rate: 0 Kb (30%), Max buffer delay: 39 bytes (0%)
Priority high
PLP high: 25393, PLP low: 24627, TCP PLP high: 25393, TCP PLP low: 8742
Entry 1 (Scheduler index: 38372, Forwarding-class #: 1):
Traffic chunk: Max = 0 bytes, Min = 0 bytes
Tx rate: 0 Kb (40%), Max buffer delay: 68 bytes (0%)
Priority low
PLP high: 25393, PLP low: 24627, TCP PLP high: 25393, TCP PLP low: 8742
Description For Adaptive Services (AS) PIC link services IQ interfaces (lsq) only, display
fragmentation properties for specific forwarding classes.
Output Fields Table 126 describes the output fields for the show class-of-service fragmentation-map
command. Output fields are listed in the approximate order in which they appear.
Description Display the logical and physical interface associations for the classifier, rewrite rules,
and scheduler map objects.
Options none—Display CoS associations for all physical and logical interfaces.
Output Fields Table 127 describes the output fields for the show class-of-service interface
command. Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display mapping of code point value to loss priority.
Output Fields Table 128 describes the output fields for the show class-of-service loss-priority-map
command. Output fields are listed in the approximate order in which they appear.
Description Display the mapping of forwarding classes and loss priority to code point values.
type type—(Optional) Display the rewrite rule of specified type. The rewrite rule type
can be one of the following:
List of Sample Output show class-of-service rewrite-rule type dscp on page 538
Output Fields Table 129 describes the output fields for the show class-of-service rewrite-rule
command. Output fields are listed in the approximate order in which they appear.
Description (M-series and T-series routing platforms only) Display mapping of CoS objects to
routing instances.
Output Fields Table 130 describes the output fields for the show class-of-service routing-instance
command. Output fields are listed in the approximate order in which they appear.
Output Fields Table 131 describes the output fields for the show class-of-service scheduler-map
command. Output fields are listed in the approximate order in which they appear.
Description For Gigabit Ethernet IQ and Channelized IQ PICs only, display traffic shaping and
scheduling profiles.
Output Fields Table 132 describes the output fields for the show class-of-service
traffic-control-profile command. Output fields are listed in the approximate order in
which they appear.
Output Fields Table 133 describes the output fields for the show class-of-service virtual-channel
command. Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display virtual channel group information.
Output Fields Table 134 describes the output fields for the show class-of-service
virtual-channel-group command. Output fields are listed in the approximate order in
which they appear.
Services ! 545
JUNOS 8.1 System Basics and Services Command Reference
546 ! Services
Chapter 14
Compressed Real-Time Transport
Protocol Operational Mode Commands
Table 135 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot Compressed Real-Time Transport Protocol (CRTP)
services. Commands are listed in alphabetical order.
Task Command
Clear CRTP flows statistics. clear services crtp statistics on page 548
Display CRTP output. show services crtp on page 549
Display CRTP flows. show services crtp flows on page 551
NOTE: For information about how to configure CRTP services, see the JUNOS
Services Interfaces Configuration Guide.
! 547
JUNOS 8.1 System Basics and Services Command Reference
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Output Fields Table 136 lists the output fields for the show services crtp command. Output fields
are listed in the approximate order in which they appear.
Output Fields Table 137 lists the output fields for the show services crtp flows command. Output
fields are listed in the approximate order in which they appear.
Table 138 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot class-of-service (CoS ) services on the
Adaptive Services PIC. Commands are listed in alphabetical order.
Task Command
Clear CoS statistics. clear services cos statistics on page 554
NOTE: CoS services are supported on the adaptive services interface on the
following routing platforms:
CoS services are also supported on the redundant adaptive services interface
(rspnumber) on M-series and T-series routing platforms.
NOTE: For information about how to configure CoS services, see the JUNOS
Services Interfaces Configuration Guide.
! 553
JUNOS 8.1 System Basics and Services Command Reference
Description Clear statistics for class-of-service (CoS) code point bit patterns and forwarding
classes as configured in CoS services for the AS PIC.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Display the mapping of class-of-service (CoS) code point aliases to corresponding
bit patterns and the mapping of forwarding class names to queue numbers as
configured in CoS services for the AS PIC.
Output Fields Table 139 describes the output fields for the show services cos statistics command.
Output fields are listed in the approximate order in which they appear.
111100 0 0
111101 0 0
111110 0 0
111111 0 0
Forwarding class Packets in Packets out
0 0 0
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
11 0 0
12 0 0
13 0 0
14 0 0
15 0 0
show services cos The output for the show services cos statistics brief command is identical to that for
statistics brief the show services cos statistics command. For sample output, see show services
cos statistics on page 556.
show services cos The output for the show services cos statistics detail command is identical to that
statistics detail for the show services cos statistics command. For sample output, see show services
cos statistics on page 556.
show services cos The output for the show services cos statistics extensive command is identical to
statistics extensive that for the show services cos statistics command. For sample output, see show
services cos statistics on page 556.
Table 140 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot data link switching (DLSw) on J-series routing platforms.
Commands are listed in alphabetical order.
Task Command
Clear DLSw reachability. clear dlsw reachability on page 560
Display information about the cached media access control show dlsw reachability on page 566
(MAC) entries.
Display logical link control type 2 (LLC2) redundancy information show llc2 redundancy on page 567
for DLSw.
Display LLC2 redundancy statistics. show llc2 redundancy interface statistics on page 568
Display LLC2 redundancy MAC translation information. show llc2 redundancy mac-translation on page 569
Display LLC2 redundancy tracking information. show llc2 redundancy track on page 570
NOTE: For information about how to configure DLSw, see the JUNOS Services
Interfaces Configuration Guide or the J-series Services Router Advanced WAN Access
Configuration Guide.
! 559
JUNOS 8.1 System Basics and Services Command Reference
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (J-series routing platform only) Display information about data link switching
(DLSw) capabilities of a specific remote peer or all peers.
Output Fields Table 141 describes the output fields for the show dlsw capabilities command.
Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display information about configured data link
switching (DLSw) circuits.
Output Fields Table 142 describes the output fields for the show dlsw circuits command. Output
fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display data link switching (DLSw) peer status.
Output Fields Table 143 describes the output fields for the show dlsw peers command. Output
fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display media access control (MAC) and IP
addresses of remote data link switching (DLSw) peers.
Output Fields Table 144 describes the output fields for the show dlsw reachability command.
Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display logical link control type 2 (LLC2) redundancy
information for data link switching (DLSw).
Table 145 describes the output fields for the show llc2 redundancy command.
Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display logical link control type 2 (LLC2) redundancy
interface statistics for data link switching (DLSw).
Output Fields Table 146 lists the output fields for the show llc2 redundancy interface statistics
command. Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display Logical Link Control type 2 (LLC2)
redundancy MAC translation information for data link switching (DLSw).
Output Fields Table 147 lists the output fields for the show llc2 redundancy mac-translation
command. Output fields are listed in the approximate order in which they appear.
Description (J-series routing platform only) Display Logical Link Control type 2 (LLC2)
redundancy tracking information for data link switching (DLSw).
Output Fields Table 148 lists the output fields for the show llc2 redundancy track command. Output
fields are listed in the approximate order in which they appear.
Table 149 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot flow collection and monitoring services. In the table, the
commands are grouped by functionality. In the remainder of this chapter, they are
listed strictly in alphabetical order.
Display available PICs for the service and show services accounting status on page 599
redundancy model.
Display the CPU usage of the PIC. show services accounting usage on page 600
Dynamic Flow Clear dynamic flow capture information. clear services dynamic-flow-capture on page 575
Capture
Display information for a content show services dynamic-flow-capture content-destination on
destination. page 601
Display information for a control source. show services dynamic-flow-capture control-source on
page 602
Display dynamic flow capture statistics. show services dynamic-flow-capture statistics on page 604
! 573
JUNOS 8.1 System Basics and Services Command Reference
Display the number of active flow statistics. show passive-monitoring flow on page 583
Display memory and flow record statistics. show passive-monitoring memory on page 585
Display available PICs for the service and show passive-monitoring status on page 586
redundancy model.
Display the CPU usage of the PIC. show passive-monitoring usage on page 587
NOTE: For information about how to configure flow collection and monitoring
services, see the JUNOS Services Interfaces Configuration Guide.
574 !
Chapter 17: Flow Collection and Monitoring Operational Mode Commands
Description (M320 routers and T-series routing platforms only) Clear dynamic flow capture
information for specified capture group.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers and T-series routing platform only) Clear statistics
for one passive monitoring interface or for all passive monitoring interfaces.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers and T-series routing platform only) Clear statistics
for one flow collector interface or for all flow collector interfaces.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers and T-series routing platform only) Switch to the
primary File Transfer Protocol (FTP) server that is configured as a flow collector.
clear-files—(Optional) Request clearing of existing data files in the FTP wait queue
when the switch takes place.
clear-logs—(Optional) Request clearing of existing logs when the switch takes place.
List of Sample Output request services flow-collector change-destination primary interface on page 578
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers and T-series routing platform only) Switch to the
secondary File Transfer Protocol (FTP) server that is configured as a flow collector.
clear-files—(Optional) Request clearing of existing data files in the FTP wait queue
when the switch takes place.
clear-logs—(Optional) Request clearing of existing logs when the switch takes place.
List of Sample Output request services flow-collector change-destination secondary interface on page 579
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers and T-series routing platform only) Transfer a test
file to the primary or secondary File Transfer Protocol (FTP) server that is
configured as a flow collector. This command verifies that the output side of the
flow collector interface is operating properly.
interface all | cp-fpc/pic/port)—Transfer a test file of flows from all configured flow
collector interfaces or from only the specified interface.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display passive
monitoring error statistics.
Output Fields Table 150 lists the output fields for the show passive-monitoring error command.
Output fields are listed in the approximate order in which they appear.
Error information
Packets dropped (no Number of packets dropped because of memory shortage.
memory)
Packets dropped (not IP) Number of non-IP packets dropped.
Packets dropped (not IPv4) Number of packets dropped because they failed the IPv4 version check.
Packets dropped (header too Number of packets dropped because the packet length or IP header length was too small.
small)
Memory allocation failures Number of flow record memory allocation failures. A small number reflects failures to replenish
the free list. A large number indicates the monitoring station is almost out of memory space.
Memory free failures Number of flow record memory free failures.
Memory free list failures Number of flow records received from free list that failed. Memory is nearly exhausted or too
many new flows greater than 128 KB are being created per second.
Memory warning Whether the flows have exceeded 1 million packets per second (Mpps) on a Monitoring Services
PIC or 2 Mpps on a Monitoring Services II PIC. The response can be Yes or No.
Memory overload Whether the memory has been overloaded. The response can be Yes or No.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display passive
flow statistics.
Output Fields Table 151 lists the output fields for the show passive-monitoring flow command.
Output fields are listed in the approximate order in which they appear.
Flow information
Flow packets Number of packets received by an operational PIC.
Flow bytes Number of bytes received by an operational PIC.
Flow packets 10-second rate Number of packets per second handled by the PIC and displayed as a 10-second average.
Flow bytes 10-second rate Number of bytes per second handled by the PIC and displayed as a 10-second average.
Active flows Number of currently active flows tracked by the PIC.
Total flows Total number of flows received by an operational PIC.
Flows exported Total number of flows exported by an operational PIC.
Flows packets exported Total number of cflowd packets exported by an operational PIC.
Flows inactive timed out Total number of flows that are exported because of inactivity.
Flows active timed out Total number of long-lived flows that are exported because of an active timeout.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display passive
monitoring memory and flow record statistics
Options * | all | mo-fpc/pic/port—Display memory and flow record statistics for monitoring
interfaces. Use a wildcard character, specify all interfaces, or provide a specific
interface name.
Output Fields Table 152 lists the output fields for the show passive-monitoring memory command.
Output fields are listed in the approximate order in which they appear.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display passive
monitoring status.
Output Fields Table 153 lists the output fields for the show passive-monitoring status command.
Output fields are listed in the approximate order in which they appear.
Group index Integer that represents the monitoring group of which the PIC is a member. Group index is a
mapping from the group name to an index. It is not related to the number of monitoring groups.
Export interval Configured export interval for cflowd records, in seconds.
Export format Configured export format (only cflowd version 5 is supported).
Protocol Protocol the PIC is configured to monitor (only IPv4 is supported).
Engine type Configured engine type that is inserted in output cflowd packets.
Engine ID Configured engine ID that is inserted in output cflowd packets.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display passive
monitoring usage statistics.
Output Fields Table 154 lists the output fields for the show passive-monitoring usage command.
Output fields are listed in the approximate order in which they appear.
Description Display information about the aggregated active flows being processed by the
accounting service.
limit limit-value—(Optional) Limit the display output to this number of flows. The
default is no limit.
order (bytes | packets)—(Optional) Display the flow with the ordering of the highest
number, either by byte count or by packet count.
Additional Information For information about aggregation configuration options, see the JUNOS Services
Interfaces Configuration Guide.
List of Sample Output show services accounting aggregation protocol-port detail on page 589
show services accounting aggregation source-destination- prefix order packet detail on
page 590
show services accounting aggregation source-destination- prefix extensive limit on
page 590
Output Fields Table 155 lists the output fields for the show services accounting aggregation
command. Output fields are listed in the approximate order in which they appear.
Output Fields Table 156 lists the output fields for the show services accounting errors command.
Output fields are listed in the approximate order in which they appear.
List of Sample Output show services accounting flow name on page 593
Output Fields Table 157 lists the output fields for the show services accounting flow command.
Output fields are listed in the approximate order in which they appear.
Description Display information about the flows being processed by the accounting service.
filters—(Optional) Filter the display output of the currently active flow records. The
following filters query actively changing data structures and result in different
results for multiple invocations:
order (bytes | packets)—(Optional) Display the flow with the ordering of the highest
number, either by byte count or by packet count.
Additional Information When no PIC is active, or when no route record has been downloaded from the
PIC, this command reports no flows, even though packets are being sampled. This
command displays information about two concurrent sessions only. If a third
session is attempted, the command pauses with no output until one of the previous
sessions is completed.
List of Sample Output show services accounting flow-detail name service-name extensive on page 596
show services accounting flow-detail limit order bytes on page 596
show services accounting flow-detail source-port on page 596
Output Fields Table 158 lists the output fields for the show services accounting flow-detail
command. Output fields are listed in the approximate order in which they appear.
show services user@host> show services accounting flow-detail name cf-2 extensive
accounting flow-detail Service Accounting interface: mo-0/2/0, Local interface index: 145
name service-name Service name: cf-2
extensive TOS: 0, Protocol: udp(17), TCP flags: 0
Source address: 10.10.10.1, Source prefix length: 0, Destination address:
20.20.20.20,
Destination prefix length: 0, Source port: 1173, Destination port: 69
Input SNMP interface index: 65, Output SNMP interface index: 0, Source-AS: 0,
Destination-AS: 0
Start time: 62425, End time: 635265, Packet count: 165845, Byte count: 9453165
show services The output of the following command is displayed over 141 columns, not the
accounting flow-detail standard 80 columns. In this sample, the output is split into three sections, with
limit order bytes ellipses (...) indicating where the sections are continued.
show services user@host> show services accounting flow-detail name cf-2 detail source-port
accounting flow-detail 1173
source-port Service Accounting interface: mo-0/2/0, Local interface index: 145
Service name: cf-2
Protocol: udp(17), Source address: 10.10.10.1, Source port: 1173, Destination
address:
20.20.20.20, Destination port: 69
Start time: 62425, End time: 811115, Packet count: 142438, Byte count: 8118966
Output Fields Table 159 lists the output fields for the show services accounting memory command.
Output fields are listed in the approximate order in which they appear.
List of Sample Output show services accounting packet-size-distribution name service-name on page 598
Output Fields Table 160 lists the output fields for the show services accounting
packet-size-distribution command. Output fields are listed in the approximate order
in which they appear.
Description Display available Physical Interface Cards (PICs) for accounting services.
List of Sample Output show services accounting status name service-name on page 599
Output Fields Table 161 lists the output fields for the show services accounting status command.
Output fields are listed in the approximate order in which they appear.
Group index Integer that represents the monitoring group of which the PIC is a member. Group index is a
mapping from the group name to an index. It is not related to the number of monitoring groups.
Export interval (in seconds) Configured export interval for cflowd records, in seconds.
Export format Configured export format (only cflowd version 5 is supported).
Protocol Protocol the PIC is configured to monitor (only IPv4 is supported).
Engine type Configured engine type that is inserted in output cflowd packets.
Engine ID Configured engine ID that is inserted in output cflowd packets.
Description Display the CPU usage of PIC used for active flow monitoring.
name service-name—(Optional) Display CPU usage for the specified service name.
Additional Information When no route record has been downloaded from the PIC, this command reports
no flows, even though packets are being sampled.
Output Fields Table 162 lists the output fields for the show services accounting usage command.
Output fields are listed in the approximate order in which they appear.
Description (M320 routers and T-series routing platforms only) Display information about the
content destination that receives packets from the dynamic flow capture (DFC)
interface.
Output Fields Table 163 lists the output fields for the show services dynamic-flow-capture
content-destination command. Output fields are listed in the approximate order in
which they appear.
Description (M320 routers and T-series routing platform only) Display information about the
control source that makes dynamic flow capture requests to the dynamic flow
capture interface.
Output Fields Table 164 lists the output fields for the show services dynamic-flow-capture
control-source command. Output fields are listed in the approximate order in which
they appear.
Table 164: show services dynamic flow capture control-source Output Fields
Description (M320 routers and T-series routing platform only) Display statistics information
about the capture group specified for dynamic flow capture.
Output Fields Table 165 lists the output fields for the show services dynamic-flow-capture statistics
command. Output fields are listed in the approximate order in which they appear.
Control protocol drops Control protocol packets dropped for the following reasons:
! Not IP packets—Dropped packets were not IP packets.
! Not UDP packets—Dropped packets were not User Datagram
Protocol (UDP) packets.
! Invalid destination address—Dropped packets had invalid destination
addresses.
! No memory—Packets dropped because of insufficient memory.
! Unauthorized control source—Packets dropped because the control
source was not authenticated.
! Bad request—Packets dropped because the request was invalid.
! Unknown control source—Packets dropped because the control
source was not known.
! Not DTCP—Dropped packets did not adhere to the control protocol
format.
! Bad cmdline—Packets dropped because of a version mismatch.
! Other—Packets dropped for other reasons or undetermined causes.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display
information about flow collector files.
Options all | cp-fpc/pic/port—Display file information for all configured flow collector
interfaces or for the specified interface.
Additional Information No entries are displayed for files that have been successfully transferred.
List of Sample Output show services flow-collector file interface extensive on page 607
Output Fields Table 166 lists the output fields for the show services flow-collector file interface
command. Output fields are listed in the approximate order in which they appear.
show services user@host> show services flow-collector file interface cp-3/2/0 extensive
flow-collector file Filename: cFlowd-py69Ni69-0-20031112_014301-so_3_0_0_0.bcp.bi.gz
interface extensive Throughput:
Flow records: 188365, per second: 238, peak per second: 287
Uncompressed bytes: 21267756, per second: 27007, peak per second: 32526
Compressed bytes: 2965643, per second: 0, peak per second: 22999
Status:
Compressed blocks: 156, Block count: 156
State: Active, Transfer attempts: 0
Description (M40e, M160, and M320 routers and T-series routing platform only) Display the
number of packets received by collector interfaces from monitoring interfaces.
List of Sample Output show services flow-collector input interface on page 608
Output Fields Table 167 lists the output fields for the show services flow-collector input interface
command. Output fields are listed in the approximate order in which they appear.
Description (M40e, M160, and M320 routers and T-series routing platform only) Display overall
statistics for the flow collector application.
List of Sample Output show services flow-collector interface extensive on page 612
Output Fields Table 168 lists the output fields for the show services flow-collector interface
command. Output fields are listed in the approximate order in which they appear.
Files File statistics, incremented since the PIC last booted: detail extensive
! Files created—Total number of files created on this PIC.
! Files exported—Number of files successfully created and exported.
! Files destroyed—(extensive output only) Number of files successfully
exported and files dropped by the flow collection interface.
Throughput Throughput statistics: detail extensive
! Uncompressed bytes—Total uncompressed data size for all files created on
this PIC.
! per second—Average number of uncompressed bytes per second.
! peak per second—Peak number of uncompressed bytes per second.
! Compressed bytes—Total compressed data size for all files created on this
PIC.
! per second—Average number of compressed bytes per second.
! peak per second—Peak number of compressed bytes per second.
Packet drops Number of packets dropped for the following causes: extensive
! No memory—Packets dropped because of insufficient memory.
! Not IP—Packets dropped because they are not IP packets.
! Not IPv4—Packets dropped because they are not IP version 4 packets.
! Too small—Packets dropped because each packet was smaller than the size
reported in its header.
! Fragments—Packets dropped because of fragmentation. Fragments are not
reassembled.
! ICMP—Packets dropped because they are not ICMP packets.
! TCP—Packets dropped because they are not TCP packets.
! Unknown—Packets dropped because of undetermined causes.
! Not JUNOS flow—Packets dropped because they are not interpreted by the
JUNOS software. The JUNOS software interprets only IPv4, UDP cflowd
version 5 packets.
File transfer File transfer statistics: detail extensive
! FTP bytes—Total number of bytes transferred to the FTP server, including
those dropped during transfer.
! FTP files—Total number of FTP transfers attempted by the server.
! FTP failure—Total number of FTP failures encountered by the server.
Files File statistics, incremented since the PIC last booted: detail extensive
! Files created—Total number of files created on this PIC.
! Files exported—Number of files successfully created and exported.
! Files destroyed—(extensive output only) Number of files successfully
exported and files dropped by the flow collection interface.
Throughput Throughput statistics: detail extensive
! Uncompressed bytes—Total uncompressed data size for all files created on
this PIC.
! per second—Average number of uncompressed bytes per second.
! peak per second—Peak number of uncompressed bytes per second.
! Compressed bytes—Total compressed data size for all files created on this
PIC.
! per second—Average number of compressed bytes per second.
! peak per second—Peak number of compressed bytes per second.
Packet drops Number of packets dropped for the following causes: extensive
! No memory—Packets dropped because of insufficient memory.
! Not IP—Packets dropped because they are not IP packets.
! Not IPv4—Packets dropped because they are not IP version 4 packets.
! Too small—Packets dropped because each packet was smaller than the size
reported in its header.
! Fragments—Packets dropped because of fragmentation. Fragments are not
reassembled.
! ICMP—Packets dropped because they are not ICMP packets.
! TCP—Packets dropped because they are not TCP packets.
! Unknown—Packets dropped because of undetermined causes.
! Not JUNOS flow—Packets dropped because they are not interpreted by the
JUNOS software. The JUNOS software interprets only IPv4, UDP cflowd
version 5 packets.
File transfer File transfer statistics: detail extensive
! FTP bytes—Total number of bytes transferred to the FTP server, including
those dropped during transfer.
! FTP files—Total number of FTP transfers attempted by the server.
! FTP failure—Total number of FTP failures encountered by the server.
Export channel: 1
Current server: Primary
Primary server state: OK, Secondary server state: Not configured
Table 169 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot the intrusion detection service (IDS). Commands are
listed in alphabetical order.
Task Command
Clear (set to zero) IDS events and event clear services ids on page 616
information.
Clear the IDS events for a particular address that clear services ids destination-table on page 617
might be under attack.
Clear the IDS attack source and destination clear services ids pair-table on page 618
address pair table.
Clear all IDS events for addresses that are clear services ids source-table on page 619
suspected attackers.
Display IDS event information. show services ids on page 620
NOTE: IDS is supported on the adaptive services interface on the following routing
platforms:
NOTE: For information about how to configure IDS, see the JUNOS Services
Interfaces Configuration Guide.
! 615
JUNOS 8.1 System Basics and Services Command Reference
Options none—Clear all IDS events for all adaptive services interfaces for all service sets,
and clear and reset IDS.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Clear the intrusion detection service (IDS) events for a particular address that might
be under attack.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Clear the intrusion detection service (IDS) attack source and destination address
pair table.
Options none—Clear the attack source and destination address pair table.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Clear all intrusion detection service (IDS) events for addresses that are suspected
attackers.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description Display information about intrusion detection service (IDS) events. All events
gathered by IDS are reported as anomalies. For example, events such as create
forward or watch flow, FTP passive, and FTP active are genuinely allowed by the
stateful firewall but are logged as anomalies to track the rates and number for these
events.
Output Fields Table 170 lists the output fields for the show services ids command. Output fields
are listed in the approximate order in which they appear.
show services ids user@host> show services ids destination-table extensive order anomalies
destination-table Interface: sp-0/2/0, Service set: ss1
extensive order IDS sorting order: Anomalies
anomalies Source address Dest address Time Flags Application
15.1.1.1 -> 15.99.1.1 1m28s junos-ftp
Bytes: 1065, Packets: 18, Flows: 1, Anomalies: 10
Anomaly description Count Rate(eps) Elapsed
creating forward or watch flow 1 15.6 1m28s
Number of open sessions exceeds IDS limit 9 0.8 18s
show services ids user@host> show services ids pair-table extensive limit 3
pair-table extensive Interface: sp-1/3/0, Service set: null-sfw
limit Sorting order: Packets
Source address Dest address Time Flags Application
show services ids user@host> show services ids source-table extensive limit 3
source-table extensive Interface: sp-1/3/0, Service set: null-sfw
limit Sorting order: Packets
Source address Dest address Time Flags Application
10.58.255.18 -> any 40m 0s SYN cookie
Bytes: 250.0 m, Packets: 1978.0 k, Flows: 356.0 k, Anomalies: 387.0 k
Anomalies Count Rate(eps) Elapsed
TCP source or destination port zero 37.0 k 9.8 6m26s
First packet of TCP session not SYN 160.0 k 0.0 40s
TCP source or destination port zero 69.0 k 62.5 7m45s
UDP source or destination port zero 68.0 k 56.2 7m45s
ICMP header length check failed 319 0.1 7m49s
IP fragment assembly timeout 89.0 k 4.4 7m26s
UDP header length check failed 39 0.0 8m17s
TCP header length check failed 46 0.0 8m4s
Table 171 on page 628 summarizes the command-line interface (CLI) commands
you can use to monitor and troubleshoot IP Security (IPSec) services. In the table,
the commands are grouped by the interfaces on which they are supported:
In the remainder of this chapter, the commands are listed in alphabetical order.
! 627
JUNOS 8.1 System Basics and Services Command Reference
628 !
Chapter 19: IP Security Operational Mode Commands
NOTE: For information about how to configure IPSec services, see the JUNOS
Services Interfaces Configuration Guide for adaptive services interfaces and the
JUNOS System Basics Configuration Guide for encryption interfaces.
! 629
JUNOS 8.1 System Basics and Services Command Reference
Description (Encryption interface on M-series and T-series routing platforms only) Clear
information about the current Internet Key Exchange (IKE) security association.
This command is valid for dynamic security associations only.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Encryption interface on M-series and T-series routing platforms only) Clear
information about the current IP Security (IPSec) security association. This
command is valid for dynamic security associations only. When this command is
issued, a new security association is created.
Output Fields See the show ipsec security-associations on page 662 for an explanation of output
fields.
clear ipsec Output from the show ipsec security-associations detail command is displayed
security-associations before and after the clear ipsec security-associations command is issued:
Description (Adaptive services interfaces only) Delete certificate authority (CA) digital
certificates from the routing platform.
List of Sample Output clear security pki ca-certificate all on page 632
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interfaces only) Delete manually generated local digital certificate
requests from the routing platform.
Options all—Delete all local digital certificate requests from the routing platform.
List of Sample Output clear security pki certificate-request all on page 633
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interfaces only) Delete certificate revocation lists (CRLs) from the
routing platform.
List of Sample Output clear security pki crl ca-profile all on page 634
Output Fields When you enter this command, you are provided feedback on the status of your
request.
clear security pki crl user@host> clear security pki crl ca-profile all
ca-profile all
Description (Adaptive services interfaces only) Delete local digital certificates, certificate
requests, and the corresponding public/private key pairs from the routing platform.
Options all—Delete all local digital certificates, certificate requests, and the corresponding
public/private key pairs from the routing platform.
List of Sample Output clear security pki local-certificate all on page 635
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interfaces only) Delete digital certificates from the IPSec
configuration memory cache.
List of Sample Output clear services ipsec-vpn certificates all on page 636
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interface only) Clear Internet Key Exchange (IKE) security
associations.
List of Sample Output clear services ipsec-vpn ipsec security-associations on page 639
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Options remote-gateway address—(Optional) Clear statistics for the specified remote system.
List of Sample Output clear services ipsec-vpn ipsec statistics on page 638
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interface only) Clear IP Security (IPSec) security associations.
List of Sample Output clear services ipsec-vpn ipsec security-associations on page 639
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Encryption interface on M-series and T-series routing platforms only) 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.
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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security user@host> request security certificate enroll filename host.crt subject
certificate (signed) 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. <--------------
Syntax request security certificate enroll filename filename ca-file ca-file ca-name ca-name
encoding (binary | perm) url url
Description (Encryption interface on M-series and T-series routing platforms only) Obtain a
certificate from a certificate authority (CA). The results are saved in a specified file
to the /var/etc/ikecert directory.
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.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security user@host> request security certificate enroll filename ca_verisign ca-file
certificate (unsigned) verisign ca-name juniper.net url
http://pilotonsiteipsec.verisign.com/cgi-bin/pkiclient.exe
URL: http://pilotonsiteipsec.verisign.com/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. <--------------
Description (Encryption interface on M-series and T-series routing platforms only) Generate a
public and private key pair for a digital certificate.
size key-size—(Optional) Key size, in bits. The key size can be 512, 1024, or 2048.
The default value is 1024.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interfaces only) Request a digital certificate from a certificate
authority (CA) online by using the Simple Certificate Enrollment Protocol (SCEP).
List of Sample Output request security pki ca-certificate enroll on page 643
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security pki user@host> request security pki ca-certificate enroll ca-profile entrust
ca-certificate enroll Received following certificates:
Certificate: C=us, O=juniper, CN=First Officer
Fingerprint: 46:71:15:34:f0:a6:41:76:65:81:33:4f:68:47:c4:df:78:b8:e3:3f
Certificate: C=us, O=juniper, CN=First Officer
Fingerprint: bc:78:87:9b:a7:91:13:20:71:db:ac:b5:56:71:42:ad:1a:b6:46:17
Certificate: C=us, O=juniper
Fingerprint: 00:8e:6f:58:dd:68:bf:25:0a:e3:f9:17:70:d6:61:f3:53:a7:79:10
Do you want to load the above CA certificate ? [yes,no] (no) yes
Description (Adaptive services interfaces only) Manually load a certificate authority (CA) digital
certificate from a specified location.
List of Sample Output request security pki ca-certificate load on page 644
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security pki user@host> request security pki ca-certificate load ca-profile ca-private
ca-certificate load filename pki-file
Syntax request security pki crl load ca-profile ca-profile-name filename path/filename
Description (Adaptive services interfaces only) Manually install a certificate revocation list (CRL)
on the routing platform from a specified location.
List of Sample Output request security pki crl load on page 645
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security pki crl user@host> request security pki crl load ca-profile ca-private filename pki-file
load
Description (Adaptive services interfaces only) Manually generate a local digital certificate
request in the Public-Key Cryptography Standards #10 (PKCS-10) format.
! CN—Common name
! O—Organization name
! ST—State
! C—Country
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Adaptive services interfaces only) Generate a Public Key Infrastructure (PKI) public
and private key pair for a local digital certificate.
size—(Optional) Key pair size. The key pair size can be 512, 1024, or 2048 bits.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security pki user@host> request security pki generate-key-pair certificate-id billy size 2048
generate-key-pair Generated key pair billy, key size 2048 bits
Description (Adaptive services interfaces only) Request that a CA enroll and install a local digital
certificate online by using the Simple Certificate Enrollment Protocol (SCEP).
! CN—Common name
! O—Organization name
! ST—State
! C—Country
List of Sample Output request security pki local-certificate enroll on page 650
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security pki user@host> request security pki local-certificate enroll certificate-id
local-certificate enroll r3-entrust-scep ca-profile entrust domain-name router3.juniper.net subject
"CN=router3,OU=Engineering,O=juniper,C=US" challenge-password 123
Certificate enrollment has started. To view the status of your enrollment, check
the key management process (kmd) log file at /var/log/kmd. Please save the
challenge-password for revoking this certificate in future. Note that this
password is not stored on the router.
Syntax request security pki local-certificate load certificate-id certificate-id-name filename path
Description (Adaptive services interfaces only) Manually load a local digital certificate from a
specified location.
List of Sample Output request security pki local-certificate load on page 651
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request security pki user@host> request security pki local-certificate load filename
local-certificate load /tmp/router2-cert certificate-id local-entrust2
Local certificate local-entrust2 loaded successfully
Description (Encryption interface on M-series and T-series routing platforms only) Manually
switch from the primary to the backup encryption services interface, or switch from
the primary to the backup IP Security (IPSec) tunnel.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Syntax request services ipsec-vpn ipsec switch tunnel local-gateway address remote-gateway
address
<routing-instance instance-name>
Description (Adaptive services interface only) Manually switch between primary and backup IP
Security (IPSec) tunnels.
List of Sample Output request services ipsec-vpn ipsec switch tunnel on page 653
Output Fields When you enter this command, you are provided feedback on the status of your
request.
request services user@host> request services ipsec-vpn ipsec switch tunnel local-gateway 10.1.1.1
ipsec-vpn ipsec switch remote gateway 10.100.10.1
tunnel
Description (Encryption interface on M-series and T-series routing platforms only) Add a
certificate provided by the Juniper Networks certificate authority (CA).
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (Encryption interface on M-series and T-series routing platforms only) Display
information about Internet Key Exchange (IKE) security associations.
Output Fields Table 172 lists the output fields for the show ike security-associations command.
Output fields are listed in the approximate order in which they appear.
Description (Encryption interface on M-series and T-series routing platforms only) Display
information about the IPSec certificate database.
Options none—Display standard information about all of the entries in the IPSec certificate
database.
Output Fields Table 173 lists the output fields for the show ipsec certificates command. Output
fields are listed in the approximate order in which they appear.
Validity period starts Start time that the certificate is valid, in the format yyyy mon dd, hh:mm:ss detail
GMT.
Validity period ends End time that the certificate is valid, in the format yyyy mon dd, hh:mm:ss detail
GMT.
Alternative name Auxiliary identity for the certificate. It can be dns-name, email-address, detail
information ip-address, or uri (uniform resource identifier).
Issuer Information about the entity that has signed and issued the CRL as detail
described in RFC 2459, Internet X.509 Public Key Infrastructure Certificate
and CRL Profile.
Description (Encryption interface on M-series and T-series routing platforms only) Display
information about IPSec redundancy.
Output Fields Table 174 lists the output fields for the show ipsec redundancy command. Output
fields are listed in the approximate order in which they appear.
Table 174: show ipsec redundancy Output Fields
Description (Encryption interface on M-series and T-series routing platforms only) Display
information about the IPSec security associations applied to the local or transit
traffic stream.
Output Fields Table 173 lists the output fields for the show ipsec certificates command. Output
fields are listed in the approximate order in which they appear.
Description (Adaptive services interfaces only) Display information about certificate authority
(CA) digital certificates installed in the routing platform.
Output Fields Table 176 lists the output fields for the show security pki ca-certificate command.
Output fields are listed in the approximate order in which they appear.
Subject Details of the digital certificate holder organized using the distinguished name detail
format. Possible subfields are:
! Common name—Name of the requestor.
! Organization—Organization of origin.
! Organizational unit—Department within an organization.
! State—State of origin.
! Country—Country of origin.
Public key algorithm Encryption algorithm used with the private key, such as rsaEncryption(1024 bits). All levels
Signature algorithm Encryption algorithm that the CA used to sign the digital certificate, such as detail
sha1WithRSAEncryption.
Fingerprint Secure Hash Algorithm (SHA1) and Message Digest 5 (MD5) hashes used to identify detail
the digital certificate.
Distribution CRL Distinguished name information and the URL for the certificate revocation list (CRL) detail
server.
Use for key Use of the public key, such as Certificate signing, CRL signing, Digital signature, or Key detail
encipherment.
Description (Adaptive services interfaces only) Display information about manually generated
local digital certificate requests that are stored in the routing platform.
Options none—(same as brief) Display information about all local digital certificate requests.
Output Fields Table 177 lists the output fields for the show security pki certificate-request
command. Output fields are listed in the approximate order in which they appear.
Alternate subject Domain name or IP address of the device related to the digital certificate. detail
Validity Time period when the digital certificate is valid. Values are: All levels
! Not before—Start time when the digital certificate becomes valid.
! Not after—End time when the digital certificate becomes invalid.
Public key algorithm Encryption algorithm used with the private key, such as rsaEncryption(1024 bits). All levels
Public key Public key verification status: Failed or Passed. The detail output also provides the All levels
verification status verification hash.
Description (Adaptive services interfaces only) Display information about the certificate
revocation lists (CRLs) that are stored in the routing platform.
Output Fields Table 178 shows the output fields for the show security pki crl command. Output
fields are listed in the approximate order in which they appear.
Effective date Date and time the certificate revocation list becomes valid. All levels
Next update Date and time the routing platform will download the latest version of the certificate All levels
revocation list.
Revocation List List of digital certificates that have been revoked before their expiration date. Values Detail
are:
! Serial number—Unique serial number of the digital certificate
! Revocation date—Date and time that the digital certificate was revoked.
Description (Adaptive services interfaces only) Display information about the local digital
certificates and the corresponding public keys installed in the routing platform.
Options none—(same as brief) Display information about all local digital certificates and
corresponding public keys.
Output Fields Table 179 lists the output fields for the show security pki local-certificate command.
Output fields are listed in the approximate order in which they appear.
Subject Details of the digital certificate holder organized using the distinguished name format. detail
Possible subfields are:
! Common name—Name of the authority.
! Organization—Organization of origin.
! Organizational unit—Department within an organization.
! State—State of origin.
! Country—Country of origin.
Public key algorithm Encryption algorithm used with the private key, such as rsaEncryption(1024 bits). All levels
Public key Public key verification status: Failed or Passed. The detail output also provides the All levels
verification status verification hash.
Signature algorithm Encryption algorithm that the CA used to sign the digital certificate, such as detail
sha1WithRSAEncryption.
Fingerprint Secure Hash Algorithm (SHA1) and Message Digest 5 (MD5) hashes used to identify the detail
digital certificate.
Distribution CRL Distinguished name information and URL for the certificate revocation list (CRL) server. detail
Use for key Use of the public key, such as Certificate signing, CRL signing, Digital signature, or Key detail
encipherment.
Description (Adaptive services interfaces only) Display local and remote certificates installed in
the IPSec configuration memory cache that are used for the IKE negotiation.
Options none—(same as brief) Display information about local and remote certificates
associated with all service sets.
Output Fields Table 180 lists the output fields for the show services ipsec-vpn certificates
command. Output fields are listed in the approximate order in which they appear.
Public key algorithm Specifies the encryption algorithm used with the private key, such as detail
rsaEncryption(1024 bits).
Signature algorithm Encryption algorithm that the CA used to sign the digital certificate, such as detail
sha1WithRSAEncryption.
Fingerprint Secure Hash Algorithm (SHA1) and Message Digest 5 (MD5) hashes used to identify detail
the digital certificate.
Description (Adaptive services interface only) Display information for Internet Key Exchange
(IKE) security associations. If no security association is specified, the information
for all security associations is displayed.
Options none—(same as brief) Display standard information for all IPSec security
associations.
List of Sample Output show services ipsec-vpn ike security-associations detail on page 679
Output Fields Table 181 lists the output fields for the show services ipsec-vpn ike
security-associations command. Output fields are listed in the approximate order in
which they appear.
show services ipsec-vpn user@host> show services ipsec-vpn ike security-associations detail
ike IKE peer 4.4.4.4
security-associations Role: Initiator, State: Matured
detail Initiator cookie: cf22bd81a7000001, Responder cookie: fe83795c2800002e
Exchange type: Main, Authentication method: Pre-shared-keys
Local: 4.4.4.5:500, Remote: 4.4.4.4:500
Lifetime: Expires in 187 seconds
Algorithms:
Authentication : md5
Encryption : 3des-cbc
Pseudo random function: hmac-md5
Traffic statistics:
Input bytes : 1000
Output bytes : 1280
Input packets: 5
Output packets: 9
Flags: Caller notification sent
IPsec security associations: 2 created, 0 deleted
Phase 2 negotiations in progress: 1
Description (Adaptive services interface only) Display IPSec security associations for the
specified service set. If no service set is specified, the security associations for all
service sets are displayed.
Options none—Display standard information about IPSec security associations for all
service sets.
List of Sample Output show services ipsec-vpn ipsec security associations extensive on page 682
Output Fields Table 182 lists the output fields for the show services ipsec-vpn ipsec
security-associations command. Output fields are listed in the approximate order in
which they appear.
show services ipsec-vpn user@host> show services ipsec-vpn ipsec security-associations extensive
ipsec security Service set: service-set-1
associations extensive Rule: _junos_, Term: term-1, Tunnel index: 1
Local gateway: 101.101.101.2, Remote gateway: 14.14.14.4
IPSec inside interface: sp-2/0/0.1
Local identity: ipv4_subnet(any:0,[0..7]=0.0.0.0/0)
Remote identity: ipv4_subnet(any:0,[0..7]=0.0.0.0/0)
Primary remote gateway: 101.101.101.1, State: Standby
Backup remote gateway: 14.14.14.4, State: Active
Failover counter: 1
Description (Adaptive services interface only) Display IPSec statistics for the specified service
set. If no service set is specified, the statistics for all service sets are displayed.
List of Sample Output show services ipsec-vpn ipsec statistics detail on page 684
show services ipsec-vpn ipsec statistics remote-gw on page 684
Output Fields Table 183 lists the output fields for the show services ipsec-vpn ipsec statistics
command. Output fields are listed in the approximate order in which they appear.
show services ipsec-vpn user@host> show services ipsec-vpn ipsec statistics detail
ipsec statistics detail PIC: sp-3/1/0, Service set: service-set-1
show services ipsec-vpn user@host> show services ipsec-vpn ipsec statistics remote-gw 22.22.2.1
ipsec statistics PIC: sp-3/1/0, Service set: service-set-2
remote-gw
Local gateway: 22.22.1.1, Remote gateway: 22.22.2.1, Tunnel index: 2
ESP Statistics:
Encrypted bytes: 0
Decrypted bytes: 0
Encrypted packets: 0
Decrypted packets: 0
AH Statistics:
Input bytes: 0
Output bytes: 0
Input packets: 0
Output packets: 0
Errors:
AH authentication failures: 0, Replay errors: 0
ESP authentication failures: 0, Decryption errors: 0
Bad headers: 0 Bad trailers: 0
Description (Encryption interface on M-series and T-series routing platforms only) Display
installed certificates signed by the Juniper Networks certificate authority.
Options none—Display all installed certificates signed by the Juniper Networks certificate
authority.
Output Fields Table 184 lists the output fields for the show ipsec redundancy command. Output
fields are listed in the approximate order in which they appear.
Table 184: show ipsec redundancy Output Fields
Table 185 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot Layer 2 Tunneling Protocol (L2TP) services. Commands
are listed in alphabetical order.
Task Command
Clear L2TP multilink bundles. clear services l2tp multilink on page 690
NOTE: For information about how to configure L2TP services, see the JUNOS
Services Interfaces Configuration Guide.
! 689
JUNOS 8.1 System Basics and Services Command Reference
Syntax clear services l2tp multilink (all <statistics> | bundle-id number <statistics> |
statistics (all | bundle-id number))
Description (M10i and M7i routers only) Close Layer 2 Tunneling Protocol (L2TP) multilink
sessions or clear session statistics.
Options all <statistics>—Close all L2TP multilink sessions or clear statistics for all L2TP
multilink sessions.
statistics (all | bundle-id number)—Clear all session statistics or clear statistics for the
specified multilink bundle ID.
List of Sample Output clear services l2tp multilink statistics all on page 690
Output Fields When you enter this command, you are provided feedback on the status of your
request.
clear services l2tp user@host> clear services l2tp multilink statistics all
multilink statistics all Multilink 1 statistics cleared
Description (M10i and M7i routers only) Close Layer 2 Tunneling Protocol (L2TP) sessions, or
clear session statistics.
interface sp-fpc/pic/port—Clear statistics for only the L2TP tunnels using the
specified adaptive services interface.
local-gateway gateway-address—Clear statistics for only the L2TP tunnels that have
the specified local gateway address.
local-tunnel-id tunnel-id—Clear statistics for only the L2TP tunnels that have the
specified local tunnel identifier.
peer-gateway gateway-address—Clear statistics for only the L2TP tunnels that have
the specified peer gateway address.
tunnel-group group-name—Clear statistics for only the L2TP tunnels that have the
specified tunnel group.
List of Sample Output clear services l2tp session statistics all on page 692
Output Fields When you enter this command, you are provided feedback on the status of your
request.
clear services l2tp user@host> clear services l2tp session statistics all
session statistics all Session 26497 statistics cleared
Syntax clear services l2tp tunnel statistics (all statistics | interface sp-fpc/pic/port |
local-gateway gateway-address | local-gateway-name gateway-name | local-tunnel-id
tunnel-id | peer-gateway gateway-address | peer-gateway-name gateway-name |
tunnel-group group-name)
Description (M10i and M7i routers only) Clear Layer 2 Tunneling Protocol (L2TP) statistics.
interface sp-fpc/pic/port—Clear statistics for only the L2TP tunnels using the
specified adaptive services interface.
local-gateway gateway-address—Clear statistics for only the L2TP tunnels that have
the specified local gateway address.
local-tunnel-id tunnel-id—Clear statistics for only the L2TP tunnels that have the
specified local tunnel identifier.
peer-gateway gateway-address—Clear statistics for only the L2TP tunnels that have
the specified peer gateway address.
tunnel-group group-name—Clear statistics for only the L2TP tunnels that have the
specified tunnel group.
Additional Information To display information about L2TP CPU and memory usage, you can include the
tunnel group name in the show commands described in “Service Sets Operational
Mode Commands” on page 711.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Description (M10i and M7i routers only) Display L2TP output organized by multilink bundle.
List of Sample Output show services l2tp multilink extensive on page 695
Output Fields Table 186 lists the output fields for the show services l2tp multilink command.
Output fields are listed in the approximate order in which they appear.
Description (M10i and M7i routers only) Display a list of active L2TP sessions.
brief | detail | extensive | statistics—Display the specified level of output. Use the
statistics option to display packet and byte counts for each session.
user username—(Optional) Display L2TP session information for only the specified
username.
LIst of Sample Output show services l2tp session extensive on page 699
Output Fields Table 187 lists the output fields for the show services l2tp session command.
Output fields are listed in the approximate order in which they appear.
LCP renegotiation Whether Link Control Protocol (LCP) renegotiation is configured: On or Off. to be provided
Authentication Type of authentication algorithm used: Challenge Handshake to be provided
Authentication Protocol (CHAP) or Password Authentication Protocol (PAP).
Interface ID Identifier used to look up the logical interface for this session. to be provided
Interface unit Logical interface for this session. to be provided
Call serial number Unique serial number assigned to the call. to be provided
Create time Date and time when the call was created. to be provided
Up time Length of time elapsed since the call became active, in hours, minutes, and to be provided
seconds.
Idle time Length of time elapsed since the call became idle, in hours, minutes, and to be provided
seconds.
Statistics since Date and time when collection of the following statistics began: to be provided
! Control Tx—Amount of control information transmitted, in packets and
bytes.
! Control Rx—Amount of control information received, in packets and
bytes.
! Data Tx—Amount of data transmitted, in packets and bytes.
! Data Rx—Amount of data received, in packets and bytes.
! Errors Tx—Number of errors transmitted, in packets.
! Errors Rx—Number of errors received, in packets.
Description (M10i and M7i routers only) Display Layer 2 Tunneling Protocol (L2TP) summary
information.
Options none—Display L2TP summary information for all adaptive services interfaces.
Output Fields Table 188 lists the output fields for the show services l2tp summary command.
Output fields are listed in the approximate order in which they appear.
Table 188: show services l2tp summary Output Fields
Description (M10i and M7i routers only) Display a list of active Layer 2 Tunneling Protocol
(L2TP) tunnels.
List of Sample Output show services l2tp tunnel extensive on page 703
Output Fields Table 189 on page 702 lists the output fields for the show services l2tp tunnel
command. Output fields are listed in the approximate order in which they appear.
Description (M10i and M7i routers only) Display a list of active Layer 2 Tunneling Protocol
(L2TP) users.
user username—(Optional) Display L2TP user information for only the specified
username.
List of Sample Output show services l2tp user extensive on page 706
Output Fields Table 189 lists the output fields for the show services l2tp tunnel command. Output
fields are listed in the approximate order in which they appear.
LCP renegotiation Whether Link Control Protocol (LCP) renegotiation is configured: On or Off. to be provided
Authentication Type of authentication algorithm used: Challenge Handshake to be provided
Authentication Protocol (CHAP) or Password Authentication Protocol (PAP).
Interface ID Name of the logical unit. to be provided
Interface unit Logical unit number. to be provided
Call serial number Unique serial number assigned to the call. to be provided
Create time Date and time when the call was created. to be provided
Up time Amount of time elapsed since the call became active, in hours, minutes, to be provided
and seconds.
Idle time Amount of time elapsed since the call became idle, in hours, minutes, and to be provided
seconds.
Statistics sine Date and time when collection of the following statistics began: to be provided
! Control Tx—Amount of control information transmitted, in packets and
bytes.
! Control Rx—Amount of control information received, in packets and
bytes.
! Data Tx—Amount of data transmitted, in packets and bytes.
! Data Rx—Amount of data received, in packets and bytes.
! Errors Tx—Number of errors transmitted, in packets.
! Errors Rx—Number of errors received, in packets.
show services l2tp user user@host> show services l2tp user extensive
extensive Interface: sp-1/2/0, Tunnel group: group1, Tunnel local ID: 62746
Session local ID: 56793, Session remote ID: 53304
State: Established, Mode: shared
Local IP: 10.128.1.1:1701, Remote IP: 10.128.1.2:1701
Username: usr1@juniper_1.net, Assigned IP address: 10.50.2.1/32
Local name: router-1, Remote name: router-2
Local MRU: 4000, Remote MRU: 1500, Tx speed: 64000, Rx speed: 64000
Bearer type: 2, Framing type: 1
LCP renegotiation: Off, Authentication: CHAP, Interface ID: unit_20
Interface unit: 20, Call serial number: 4137941434
Create time: Tue Mar 23 14:13:15 2004, Up time: 01:16:41
Idle time: 00:00:00
Statistics since: Tue Mar 23 14:13:13 2004
Packets Bytes
Control Tx 4 88
Control Rx 2 28
Data Tx 0 0
Data Rx 461 29.0k
Errors Tx 0
Errors Rx 0
Interface: sp-1/2/0, Tunnel group: group_company_dns, Tunnel local ID: 37266
Session local ID: 39962, Session remote ID: 53303
State: Established, Username: usr1@company_dns.com, Mode: shared
Local IP: 10.128.11.1:1701, Remote IP: 10.128.11.2:1701
Username: usr1@company_dns.com, Assigned IP address: 10.48.1.1/32
Local name: router-1, Remote name: router-2
Local MRU: 4470, Remote MRU: 4470, Tx speed: 155000000,
Rx speed: 155000000
Bearer type: 2, Framing type: 1
LCP renegotiation: Off, Authentication: CHAP, Interface ID: unit_31
Interface unit: 31, Call serial number: 4137941433
Create time: Tue Mar 23 14:13:17 2004, Up time: 01:16:39
Idle time: 01:16:36
Statistics since: Tue Mar 23 14:13:15 2004
Packets Bytes
Control Tx 6 196
Control Rx 4 150
Data Tx 0 0
Data Rx 1 80
Errors Tx 0
Errors Rx 0
Table 191 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot Network Address Translation (NAT) services.
Task Command
Display information about NAT pools. show services nat pool on page 708
NOTE: For information about how to configure NAT services, see the JUNOS
Services Interfaces Configuration Guide.
! 707
JUNOS 8.1 System Basics and Services Command Reference
List of Sample Output show services nat pool brief on page 708
show services nat pool detail on page 709
Output Fields Table 192 lists the output fields for the show services nat pool command. Output
fields are listed in the approximate order in which they appear.
show services nat pool user@host> show services nat pool brief
brief Interface: sp-1/3/0, Service set: blue
NAT pool Type Address Port Ports used
pool1 static 100.100.100.100-100.100.100.100
pool2 static 200.200.200.200-200.200.200.200
pool3 dynamic 210.210.210.210-210.210.210.230 65530-65535 0
show services nat pool user@host> show services nat pool detail
detail Interface: sp-1/2/0, Service set: set1
NAT pool: pool1, Translation type: static
Address range: 100.100.100.100-100.100.100.100
NAT pool: pool2, Translation type: static
Address range: 200.200.200.200-200.200.200.200
NAT pool: pool3, Translation type: dynamic
Address range: 210.210.210.210-210.210.210.230, Port range: 65530-65535,
Ports in use: 0, Out of port errors: 0, Max ports used: 0
Table 193 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot service sets. Commands are listed in alphabetical order.
Task Command
Clear service sets statistics. clear services service-sets statistics packet-drops on page 712
Display service sets CPU utilization. show services service-sets cpu-usage on page 713
Display services sets memory utilization. show services service-sets memory-usage on page 714
Display service sets statistics. show services service-sets statistics packet-drops interface on page 715
Display service sets summary information. show services service-sets summary on page 716
NOTE: Service sets are supported on the adaptive services interface on the
following routing platforms:
Service sets are also supported on the redundant adaptive services interface
(rspnumber) on M-series and T-series routing platforms.
NOTE: For information about how to configure service sets, see the JUNOS Services
Interfaces Configuration Guide.
! 711
JUNOS 8.1 System Basics and Services Command Reference
Description Clear dropped-packet statistics for one adaptive services interface or for all adaptive
services interfaces.
List of Sample Output clear services service-sets statistics packet-drops on page 712
Output Fields When you enter this command, you are provided feedback on the status of your
request.
Options none—Display CPU usage for all adaptive services interfaces and service sets.
Output Fields Table 194 lists the output fields for the show services service-sets cpu-usage
command. Output fields are listed in the approximate order in which they appear.
Table 194: show services service-sets cpu-usage Output Fields
zone—(Optional) Display the memory usage zone of the adaptive services interface
or of an individual service set.
Output Fields Table 195 lists the output fields for the show services service-sets memory-usage
command. Output fields are listed in the approximate order in which they appear.
Table 195: show services service-sets memory-usage Output Fields
Description Display the number of dropped packets for service sets exceeding CPU limits or
memory limits.
Options none—Display the number of dropped service sets packets for all adaptive services
interfaces.
List of Sample Output show services service-sets statistics packet-drops interface on page 715
Output Fields Table 196 lists the output fields for the show services service-sets packet-drops
command. Output fields are listed in the approximate order in which they appear.
Table 196: show services service-sets packet-drops Output Fields
show services user@host> show services service-sets statistics packet-drops interface sp-1/0/0
service-sets statistics
packet-drops interface Cpu limit Memory limit Flow limit
Interface Service Set Drops Drops Drops
sp-1/0/0 sset1 0 0 0
Options none—Display service set summary information for all adaptive services interfaces.
Output Fields Table 197 lists the output fields for the show services service-sets summary
command. Output fields are listed in the approximate order in which they appear.
Table 197: show services service-sets summary Output Fields
Table 198 summarizes the command-line interface (CLI) commands you can use to
monitor and troubleshoot stateful firewall services. Commands are listed in
alphabetical order.
Task Command
Clear stateful firewall flows. clear services stateful-firewall flows on page 718
Clear stateful firewall Session Initiation Protocol clear services stateful-firewall sip-call on page 721
(SIP) call information.
Clear stateful firewall SIP register information. clear services stateful-firewall sip-register on page 724
Clear stateful firewall statistics. clear services stateful-firewall statistics on page 727
Display stateful firewall conversation information. show services stateful-firewall conversations on page 728
Display stateful firewall flow information. show services stateful-firewall flows on page 732
Display stateful firewall SIP call information. show services stateful-firewall sip-call on page 736
Display stateful firewall SIP register information. show services stateful-firewall sip-register on page 740
Display stateful firewall statistics. show services stateful-firewall statistics on page 744
Display statistics information for the application show services stateful-firewall statistics application-protocol sip on page 750
protocol SIP.
NOTE: Stateful firewall services are supported on the adaptive services interface on
the following routing platforms:
Stateful firewall services are also supported on the redundant adaptive services
interface (rspnumber) on M-series and T-series routing platforms. For information
about how to configure stateful firewall services, see the JUNOS Services Interfaces
Configuration Guide.
! 717
JUNOS 8.1 System Basics and Services Command Reference
! bootp—Bootstrap protocol
! exec—Exec
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
protocol—(Optional) Clear stateful firewall flows for one of the following IP protocol
types:
Output Fields Table 199 lists the output fields for the clear services stateful-firewall flows
command. Output fields are listed in the approximate order in which they appear.
Table 199: clear services stateful-firewall flows Output Fields
Description Clear Session Initiation Protocol (SIP) call information in stateful firewall flows.
Options none—Clear stateful firewall statistics for all interfaces and all service sets.
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
! ipv6—IPv6 within IP
Output Fields Table 200 lists the output fields for the clear services stateful-firewall sip-call
command. Output fields are listed in the approximate order in which they appear.
Table 200: clear services stateful-firewall sip-call Output Fields
Description Clear Session Initiation Protocol (SIP) register information in stateful firewall flows.
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
! ipv6—IPv6 within IP
Output Fields Table 201 lists the output fields for the clear services stateful-firewall sip-register
command. Output fields are listed in the approximate order in which they appear.
Table 201: clear services stateful-firewall sip-register Output Fields
Options none—Clear stateful firewall statistics for all interfaces and all service sets.
Output Fields When you enter this command, you are provided feedback on the status of your
request.
! bootp—Bootstrap protocol
! exec—Exec
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
Output Fields Table 202 lists the output fields for the show services stateful-firewall conversations
command. Output fields are listed in the approximate order in which they appear.
Service set Name of a service set. Individual empty service sets are not displayed, but if to be provided
no service set has any flows, a flow table header is printed for each service
set.
Conversation Information about a group of related flows. to be provided
! ALG Protocol—Application-level gateway protocol.
! Number of initiators—Number of flows that initiated a session.
! Number of responders—Number of flows that responded in a session.
Source NAT Original and translated source addresses are displayed if Network Address to be provided
Translation (NAT) is configured on this particular flow or conversation.
Frm Count Number of frames in the flow. to be provided
Destin NAT Original and translated destination IP addresses are displayed if NAT is to be provided
configured on this particular flow or conversation.
Byte count Number of bytes forwarded in the flow. to be provided
TCP established Whether a TCP connection was established: Yes or No. to be provided
TCP window size Negotiated TCP connection window size, in bytes. to be provided
Flow
Prot Source Dest State Dir Frm count
! bootp—Bootstrap protocol
! exec—Exec
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
Output Fields Table 203 lists the output fields for the show services stateful-firewall flows
command. Output fields are listed in the approximate order in which they appear.
Dir Direction of the flow. It can be input (I) or output (O). to be provided
Flow
Prot Source Dest State Dir Frm count
TCP 10.58.255.178:23 -> 10.59.16.100:4000 Forward O
TCP 10.58.255.50:33005-> 10.58.255.178:23 Forward I 1
Source NAT 10.58.255.50:33005-> 10.59.16.100:4000
Destin NAT 10.58.255.178:23 -> 0.0.0.0:4000
Description Display stateful firewall Session Initiation Protocol (SIP) call information.
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
! ipv6—IPv6 within IP
List of Sample Output show services stateful-firewall sip-call extensive on page 739
Output Fields Table 204 lists the output fields for the show services stateful-firewall sip-call
command. Output fields are listed in the approximate order in which they appear.
Number of initiator flows Number of control, contact, or media initiator flows. to be provided
Number of responder flows Number of control, contact, or media responder flows. to be provided
protocol Protocol used for this flow. to be provided
source-prefix Source prefix of the flow in the format source-prefix:port. to be provided
destination-prefix Destination prefix of the flow. to be provided
state Status of the flow: to be provided
! Drop—Drop all packets in the flow without a response.
! Forward—Forward the packet in the flow without examining it.
! Reject—Drop all packets in the flow with a response.
! Unknown—Unknown status.
! Watch—Inspect packets in the flow.
direction Direction of the flow: input (I), output (O), or unknown (U). to be provided
frame-count Number of frames in the flow. to be provided
Flow role Role of the flow that is under evaluation: Initiator, Master, Responder, or to be provided
Unknown.
Timeout Lifetime of the flow, in seconds. to be provided
Description Display stateful firewall Session Initiation Protocol (SIP) register information.
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
! ipv6—IPv6 within IP
List of Sample Output show services stateful-firewall sip-register extensive on page 743
Output Fields Table 205 lists the output fields for the show services stateful-firewall sip-register
command. Output fields are listed in the approximate order in which they appear.
Table 205: show services stateful-firewall sip-register Output Fields
SIP Register: Protocol: UDP, Registered IP: 10.20.170.112, Port: 5060, Acked
Expiration timeout: 36000, Timeout remaining: 35549
From: : [email protected]:0;
To: : [email protected]:0;
Call ID: : [email protected]
! bootp—Bootstrap protocol
! exec—Exec
! h323—H.323 standards
! login—Login
! netbios—NetBIOS
! netshow—NetShow
! realaudio—RealAudio
! shell—Shell
! sqlnet—SQLNet
! traceroute—Traceroute
! winframe—WinFrame
List of Sample Output show services stateful-firewall statistics extensive on page 749
Output Fields Table 206 lists the output fields for the show services stateful-firewall statistics
command. Output fields are listed in the approximate order in which they appear.
UDP errors:
IP data length less than minimum UDP header length (8 bytes): 0
Source or destination port is zero: 0
UDP port scan (ICMP error seen for UDP flow): 0
ICMP errors:
IP data length less than minimum ICMP header length (8 bytes): 0
ICMP error length inconsistencies: 0
Ping duplicate sequence number: 0
Ping mismatched sequence number: 0
ALG drops:
BOOTP: 0, DCE-RPC: 0, DCE-RPC portmap: 0
DNS: 0, Exec: 0, FTP: 0
H323: 0, ICMP: 0, IIOP: 0
Login: 0, Netbios: 0, Netshow: 0
Realaudio: 0, RPC: 0, RPC portmap: 0
RTSP: 0, Shell: 0
SNMP: 0, Sqlnet: 0, TFTP: 0
Traceroute: 0
List of Sample Output show services stateful-firewall statistics application-protocol-sip on page 751
Output Fields Table 207 lists the output fields for the show services stateful-firewall statistics
application-protocol-sip command. Output fields are listed in the approximate order
in which they appear.
Table 207: show services stateful-firewall statistics application-protocol-sip
Output Fields
Field Name Field Description
Interface Name of an adaptive services interface.
Service set Name of the service set flow.
ALG Name of the application-layer gateway.
Active SIP call count Number of active SIP calls.
Active SIP registration count Number of active SIP registrations.
REGISTER Number of new, invalid, and retransmitted register requests sent
to the SIP registrar.
INVITE Number of new, invalid, and retransmitted invite messages sent
by user agent clients.
ReINVITE Number of new, invalid, and retransmitted reinvite messages sent
by user agent clients.
ACK Number of new, invalid, and retransmitted ACK messages
received (in response to a SIP Call Invite message).
BYE Number of new, invalid, and retransmitted requests to terminate
SIP dialogues.
CANCEL Number of new, invalid, and retransmitted SIP request
cancellations.
SUBSCRIBE Number of new, invalid, and retransmitted SIP requests to
subscribe for event notifications.
NOTIFY Number of new, invalid, and retransmitted event notifications in
SIP dialogues.
OPTIONS Number of new, invalid, and retransmitted requests to query SIP
capabilities.
INFO Number of new, invalid, and retransmitted requests carrying
application-level information.
UPDATE Number of new, invalid, and retransmitted SIP dialogue updates.
REFER Number of new, invalid, and retransmitted requests to the
recipient to contact a third party.
BYE 0 0
CANCEL 0 0
SUBSCRIBE 0 0
NOTIFY 0 0
OPTIONS 0 0
INFO 0 0
UPDATE 0 0
REFER 0 0
Provisional responses (18x): 0, OK responses to INVITEs: 0
OK responses to non-INVITEs: 2, Redirection (3xx) responses: 0
Request failure (4xx) responses: 0, Server failure (5xx) responses: 0
Global failure (6xx) responses: 0, Invalid responses: 0
Response (all) retransmits: 0
Parser:
Syntax errors: 0, Content errors: 0, Unknown methods: 0
Indexes ! 753
JUNOS 8.1 System Basics and Services Command Reference
754 ! Indexes
Index
A E1 test
aborting partitioning operation..................................361 starting ................................................................26
accounting profiles stopping ...............................................................27
records, displaying ..................................................86 E3 test
status, displaying .....................................................82 starting ................................................................28
active flow monitoring stopping ...............................................................29
aggregated flows, displaying................................588 T1 test
available PICs, displaying .....................................599 starting ................................................................37
CPU usage, displaying ..........................................600 stopping ...............................................................38
error statistics, displaying ....................................591 T3 test
flow statistics, displaying .....................................593 starting ................................................................39
flows, detailed information, displaying ..............594 stopping ...............................................................40
memory statistics, displaying ..............................597 bit error rate test See BERT
packet size distribution, displaying .....................598 boot messages, displaying ..........................................403
adaptive shapers, displaying ......................................511 buffers, displaying system ..........................................406
Address Resolution Protocol See ARP
aggregated flows, displaying ......................................588 C
alarms, displaying CB
chassis ....................................................................113 environmental information, displaying ..............131
health monitor .......................................................313 Ethernet switch, displaying port information ....159
RMON .....................................................................323 operation of, controlling .........................................93
system ....................................................................397 SPMB operation, restarting ..................................108
/altconfig directory.......................................................368 certificates
/altroot directory ..........................................................368 for IKE negotiation, displaying ............................674
archival configuration installed, displaying ..............................................686
displaying ...............................................................410 key pairs, generating ............................................642
archiving files ...............................................................245 PKI
arithmetic and relational operators CA certificates, clearing ...................................632
for monitor traffic command .................................65 CA certificates, displaying ...............................665
ARP table CA certificates, loading manually ...................644
clearing ...................................................................337 certificate revocation lists, clearing ...............634
displaying ...............................................................389 certificate revocation lists, displaying............670
associations, clearing ..................................................639 certificate revocation lists, loading
ATM nodes, reachability ..................................................7 manually........................................................645
authorization See permissions key pair, generating .........................................648
autoinstallation, displaying the status of...................402 local certificates, clearing ................................635
local certificates, displaying ............................672
B local certificates, loading manually ................651
backing up partitions ..................................................368 local certificates, requesting manually ..........646
backup JUNOS software files, deleting ......................378 local certificates, requesting online ...............643
backup software, displaying information..................440 local certificates, requesting that
BERT CA install .......................................................649
DS0 test local certificates, requests, clearing ...............633
starting ................................................................24 local certificates, requests, displaying ...........668
stopping ..............................................................25
Index ! 755
JUNOS 8.1 System Basics and Services Command Reference
provided by Juniper Networks, adding............... 654 CLNS node reachability, checking .................................8
signed certificate, obtaining ................................ 640 commit operations, pending
unsigned certificate, obtaining ............................ 641 clearing ...................................................................338
CFEB displaying ...............................................................408
operation, controlling ............................................. 94 comparing files ............................................................247
statistics, displaying .............................................. 261 completing partial command entry ..........................227
status, displaying .................................................. 115 Compressed Real-Time Transport Protocol
chassis See CRTP
alarm conditions, displaying ............................... 113 compressing files .........................................................245
craft interface display messages /config directory ...........................................................368
clearing the display of ....................................... 92 configuration
displaying.......................................................... 111 deleting rescue configuration ..............................351
displaying through the CLI .............................. 117 displaying
stopping the display of .................................... 111 archival configuration ......................................410
environmental information, displaying.............. 122 CoS .....................................................................509
Ethernet switch information, displaying ............ 159 current configuration .......................................391
firmware version, displaying ............................... 176 previous configuration ....................................430
forwarding process, displaying ........................... 178 rescue configuration ........................................411
installed hardware, displaying............................. 183 saving rescue configuration .................................352
location, displaying ............................................... 200 syntax, verifying....................................................503
MAC addresses, displaying .................................. 202 configuration mode, entering.....................................344
serial numbers, displaying ................................... 183 conflicting IP addresses, displaying ...........................433
switch fabric status connections
FPCs, displaying ............................................... 165 IP sockets, displaying active ................................412
SIBs, displaying ................................................ 168 SSH, opening .........................................................306
switch fabric topology, displaying ...................... 171 testing
synchronization source information, ATM connections .................................................7
displaying ........................................................... 223 CLNS connections ................................................8
checksum general connections.............................................4
calculating for a file .............................................. 246 MPLS Layer 2 circuit connections ....................10
displaying values for all files ................................ 398 MPLS Layer 2 VPN connections .......................12
class of service See CoS MPLS Layer 3 VPN connections .......................14
cleanup, storage space ................................................ 383 MPLS LDP connections .....................................16
CLI MPLS LSP-endpoint connections ......................18
command completion .......................................... 227 MPLS RSVP connections ...................................20
command history content destination, displaying ..................................601
displaying.......................................................... 242 Control Board See CB
current working directory control source, displaying ...........................................602
displaying.......................................................... 241 conventions, documentation ........................................ xx
setting ................................................................ 228 copying
date files..........................................................................249
setting ................................................................ 237 CoS
exiting to create UNIX-level shell ........................ 502 adaptive shaper information, displaying ............511
idle timeout, setting .............................................. 229 configuration, displaying ......................................509
logical router view, clearing ................................. 226 forwarding table, displaying
logical routing instance, setting........................... 230 classifier information .......................................523
permissions, displaying ........................................ 239 code point value to loss priority .....................522
prompt, setting ...................................................... 231 code point value to loss priority, J-series ......527
restart, after software upgrade ............................ 232 code point value to queue number ................522
screen length, setting ........................................... 233 configuration ....................................................520
screen width, setting ............................................ 234 loss priority table indexes, J-series ................528
settings, displaying ............................................... 238 RED drop profiles.............................................524
terminal type, setting ........................................... 235 rewrite rules ......................................................529
timestamp, setting ................................................ 236 rewrite rules, table identifiers ........................530
756 ! Index
Index
Index ! 757
JUNOS 8.1 System Basics and Services Command Reference
F passive
facilities data link See FDL error statistics, displaying ...............................581
far-end alarm and control See FEAC flow statistics, displaying ................................583
FDL memory and flow statistics, displaying .........585
loopback test, performing ...................................... 30 status, displaying .............................................586
payload loopback test, performing ....................... 31 usage statistics, displaying ..............................587
FEAC forwarding classes, displaying............................519, 555
line loopback test, initiating .................................. 32 forwarding process, displaying ..................................178
line loopback test, terminating.............................. 33 forwarding table
FEB CoS information, displaying
firmware version, displaying ............................... 176 classifier information .......................................523
statistics, displaying .............................................. 264 code point value to loss priority .....................522
status, displaying .................................................. 175 code point value to loss priority, J-series ......527
file systems code point value to queue number ................522
checksum values, displaying ............................... 398 configuration ....................................................520
free disk space, displaying ................................... 475 loss priority per classifier ................................522
partitions, backing up ........................................... 368 loss priority table indexes, J-series ................528
files RED drop profiles.............................................524
archiving ................................................................ 245 rewrite rules ......................................................529
calculating checksum ........................................... 246 scheduler map ..................................................531
comparing .............................................................. 247 switch fabric scheduler map ...........................526
compressing .......................................................... 245 FPC
contents, displaying .............................................. 254 environmental information, displaying ..............134
copying ................................................................... 249 firmware version, displaying ...............................176
deleting................................................................... 250 installed, displaying list ........................................183
list of, displaying ................................................... 251 operation of, controlling .........................................95
log file, clearing ..................................................... 244 statistics, displaying ..............................................267
renaming ................................................................ 253 status, displaying ...................................................179
status of, displaying ................................................ 59 switch fabric status, displaying ...........................165
firmware FPM
chassis, displaying ................................................ 176 environmental information, displaying ..............138
system, displaying ................................................ 417 resychronizing craft interface status.....................96
upgrading J-series PIMs ........................................ 353 fragmentation map
flow collector services CoS information, displaying ................................533
interface files, displaying ..................................... 606 free disk space, displaying ..........................................475
packets received, displaying ................................ 608 freeing up storage space .............................................383
primary server, switching to................................ 578 Front Panel Module See FPM
secondary server, switching to............................ 579
statistics G
displaying.......................................................... 609 graceful switchover, displaying ..................................477
dropped-packet, clearing ................................ 712
interface, clearing ............................................ 577 H
test file, transferring ............................................. 580 halts
flow monitoring pending
active clearing ..............................................................339
aggregated flows, displaying .......................... 588 displaying ..........................................................429
CPU usage, displaying ..................................... 600 requesting ..............................................................354
detailed information, displaying .................... 594 hard disk
error statistics, displaying ............................... 591 partitioning
flow statistics, displaying ................................ 593 aborting .............................................................361
memory statistics, displaying ......................... 597 requesting .........................................................362
packet size distribution, displaying ............... 598 hardware, installed, displaying...................................183
PICs, displaying available ............................... 599 health monitor alarms, displaying .............................313
758 ! Index
Index
Index ! 759
JUNOS 8.1 System Basics and Services Command Reference
760 ! Index
Index
Index ! 761
JUNOS 8.1 System Basics and Services Command Reference
762 ! Index
Index
Index ! 763
JUNOS 8.1 System Basics and Services Command Reference
764 ! Index
Index of Commands
C clear system services dhcp statistics command ......343
clear arp command .....................................................337 configure command ....................................................344
clear chassis display message command ...................92
clear cli logical-router command ...............................226 F
clear dlsw reachability command..............................560 file archive command .................................................245
clear ike security-associations command .................630 file checksum md5 command ...................................246
clear ipsec security-associations command .............631 file compare command ...............................................247
clear log command ......................................................244 file copy command ......................................................249
clear passive-monitoring statistics command ..........576 file delete command ...................................................250
clear security pki ca-certificate command ................632 file list command .........................................................251
clear security pki certificate-request command .......633 file rename command.................................................253
clear security pki crl command .................................634 file show command .....................................................254
clear security pki local-certificate command............635
clear services cos statistics command ......................554 M
clear services crtp statistics command .....................548 monitor interface command ........................................52
clear services dynamic-flow-capture command ......575 monitor label-switched-path command ......................56
clear services flow-collector statistics command .....577 monitor list command ..................................................59
clear services ids command .......................................616 monitor start command................................................60
clear services ids destination-table command .........617 monitor stop command ................................................61
clear services ids pair-table command .....................618 monitor traffic command .............................................62
clear services ids source-table command .................619 mtrace command ..........................................................67
clear services ipsec-vpn certificates command........636 mtrace from-source command ....................................68
clear services ipsec-vpn ike security-associations mtrace monitor command ...........................................71
command ..................................................................637 mtrace to-gateway command ......................................72
clear services ipsec-vpn ipsec security-associations
command ..................................................................639 O
clear services ipsec-vpn ipsec statistics op command ................................................................345
command .................................................................638
clear services l2tp multilink command .....................690 P
clear services l2tp session command .......................691 ping atm command .........................................................7
clear services l2tp session statistics command........691 ping clns command .........................................................8
clear services l2tp tunnel statistics command .........693 ping command .................................................................4
clear services service-sets statistics packet-drops ping mpls l2circuit command ......................................10
command ..................................................................712 ping mpls l2vpn command ..........................................12
clear services stateful-firewall flows command .......718 ping mpls l3vpn command ..........................................14
clear services stateful-firewall sip-call command ....721 ping mpls ldp command ...............................................16
clear services stateful-firewall sip-register ping mpls lsp-end-point command .............................18
command .................................................................724 ping mpls rsvp command .............................................20
clear services stateful-firewall statistics
command .................................................................727
R
clear snmp statistics command .................................312 request chassis cb command .......................................93
clear system commit command ................................338 request chassis cfeb command ....................................94
clear system reboot command ..................................339 request chassis fpc command ......................................95
clear system services dhcp binding command ........341 request chassis fpm resync command .......................96
clear system services dhcp conflict command ........342 request chassis lcc command ......................................97
request chassis mcs command.................................... 98 request system software delete command ..............376
request chassis pcg command..................................... 99 request system software delete-backup
request chassis pic command.................................... 100 command .................................................................378
request chassis routing-engine master request system software rollback command ...........379
command ................................................................. 101 request system software validate command ...........381
request chassis scg command ................................... 104 request system storage cleanup command..............383
request chassis sfm command .................................. 105 restart command .........................................................385
request chassis sfm master switch command ......... 106
request chassis sib command .................................... 107 S
request chassis spmb restart command ................... 108 set chassis display message command ..................... 111
request chassis ssb master switch command .......... 109 set cli complete-on-space command .........................227
request chassis synchronization switch set cli directory command .........................................228
command ................................................................. 110 set cli idle-timeout command ....................................229
request ipsec switch command ................................. 652 set cli logical-router .....................................................230
request message command ....................................... 346 set cli prompt command ............................................231
request routing-engine login command ................... 347 set cli restart-on-upgrade command .........................232
request security certificate command ...................... 640 set cli screen-length command ..................................233
request security key-pair command ......................... 642 set cli screen-width command ...................................234
request security pki ca-certificate enroll set cli terminal command ..........................................235
command ................................................................. 643 set cli timestamp command ......................................236
request security pki ca-certificate load set date command.......................................................237
command ................................................................. 644 show accounting profile command .............................82
request security pki crl load ....................................... 645 show accounting records command ...........................86
request security pki generate-certificate-request show arp command ....................................................389
command ................................................................. 646 show chassis alarms command ................................. 113
request security pki generate-key-pair command ... 648 show chassis cfeb command ..................................... 115
request security pki local-certificate enroll show chassis craft-interface command .................... 117
command ................................................................. 649 show chassis environment cb command ................. 131
request security pki local-certificate load show chassis environment command ......................122
command ................................................................. 651 show chassis environment fpc command ................134
request services flow-collector show chassis environment fpm command ..............138
change-destination primary interface show chassis environment mcs command .............. 141
command ................................................................. 578 show chassis environment pcg command ...............143
request services flow-collector show chassis environment routing engine
change-destination secondary interface command .................................................................148
command ................................................................. 579 show chassis environment scg command ...............150
request services flow-collector test-file-transfer show chassis environment sfm command...............152
command .................................................................. 580 show chassis environment sib command ................155
request services ipsec-vpn ipsec switch tunnel show chassis ethernet-switch command ..................159
command .................................................................. 653 show chassis fabric fpcs command...........................165
request support information command ................... 348 show chassis fabric sibs command ...........................168
request system certificate add command ................ 654 show chassis fabric topology command ...................171
request system firmware command ......................... 353 show chassis feb command .......................................175
request system halt command .................................. 354 show chassis firmware command .............................176
request system license add command ..................... 357 show chassis forwarding command..........................178
request system license delete command ................. 358 show chassis fpc command .......................................179
request system license save command .................... 359 show chassis hardware command ............................183
request system logout command .............................. 360 show chassis lccs command ......................................199
request system partition abort command................ 361 show chassis location command ...............................200
request system partition hard-disk command ......... 362 show chassis mac-addresses command ...................202
request system power-off command ........................ 363 show chassis pic command .......................................204
request system reboot command ............................. 365 show chassis routing-engine command ...................206
request system snapshot command ......................... 368 show chassis scb command ....................................... 212
request system software add command .................. 372 show chassis sfm command ...................................... 213
show chassis spmb command ................................... 217 show host command ...................................................393
show chassis ssb command ....................................... 221 show ike security-associations command ................655
show chassis synchronization command .................223 show ipsec certificates command .............................659
show class-of-service adaptive-shaper command ...511 show ipsec redundancy command............................661
show class-of-service classifier command ................512 show ipsec security-associations command.............662
show class-of-service code-point-alias command ....514 show llc2 redundancy command ..............................567
show class-of-service command ................................509 show llc2 redundancy interface statistics
show class-of-service drop-profile command...........515 command .................................................................568
show class-of-service fabric scheduler-map show llc2 redundancy mac-translation
command .................................................................516 command .................................................................569
show class-of-service fabric statistics command .....517 show llc2 redundancy track command.....................570
show class-of-service forwarding-class command...519 show log command .....................................................256
show class-of-service forwarding-table show ntp associations command ..............................394
command .................................................................520 show ntp status command .........................................396
show class-of-service forwarding-table show passive-monitoring error command ...............581
drop-profile command ............................................524 show passive-monitoring flow command ................583
show class-of-service forwarding-table show passive-monitoring memory command .........585
rewrite-rule command ............................................529 show passive-monitoring status command ..............586
show class-of-service forwarding-table show passive-monitoring usage command ..............587
rewrite-rule mapping command ............................530 show pfe cfeb command ............................................261
show class-of-service forwarding-table show pfe feb command ..............................................264
scheduler-map command .......................................531 show pfe fpc command ..............................................267
show class-of-service forwarding-table classifier show pfe fwdd command ...........................................269
command ..................................................................522 show pfe lcc command ...............................................272
show class-of-service forwarding-table classifier show pfe next-hop command ....................................275
mapping command ..................................................523 show pfe route command ..........................................277
show class-of-service forwarding-table fabric show pfe scb command ..............................................280
scheduler-map command ........................................526 show pfe sfm command .............................................282
show class-of-service forwarding-table show pfe ssb command ..............................................284
loss-priority-map command ....................................527 show pfe statistics dma command ............................287
show class-of-service forwarding-table show pfe statistics error command ...........................290
loss-priority-map mapping command....................528 show pfe statistics ip command ................................292
show class-of-service fragmentation-map show pfe statistics ip6 command ..............................295
command .................................................................533 show pfe statistics notification command ................298
show class-of-service interface command ................534 show pfe statistics pio command ..............................300
show class-of-service loss-priority-map show pfe statistics traffic command .........................301
command .................................................................536 show pfe terse command ...........................................304
show class-of-service rewrite-rule command ...........537 show security pki ca-certificate command ...............665
show class-of-service routing-instance command ...539 show security pki certificate-request command ......668
show class-of-service scheduler-map command .....540 show security pki crl command .................................670
show class-of-service traffic-control-profile show security pki local-certificate command ...........672
command .................................................................542 show services accounting
show class-of-service virtual-channel command .....543 packet-size-distribution command ........................598
show class-of-service virtual-channel-group show services accounting aggregation command ...588
command .................................................................544 show services accounting errors command .............591
show cli authorization command ..............................239 show services accounting flow command ................593
show cli command ......................................................238 show services accounting flow-detail command .....594
show cli directory command .....................................241 show services accounting memory command ........597
show cli history command .........................................242 show services accounting status command .............599
show configuration command ...................................391 show services accounting usage command .............600
show dlsw capabilities command..............................561 show services cos statistics diffserv command .......555
show dlsw circuits command ....................................562 show services crtp command ....................................549
show dlsw peers command .......................................564 show services crtp flows command ..........................551
show dlsw reachability command .............................566