Junos Reference
Junos Reference
Release 9.0
This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto.
This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software
included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright © 1979, 1980, 1983, 1986, 1988,
1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.
GateD software copyright © 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by
Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s HELLO routing protocol.
Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD software copyright © 1988, Regents of the
University of California. All rights reserved. Portions of the GateD software copyright © 1991, D. L. S. Associates.
This product includes software developed by Maker Communications, Inc., copyright © 1996, 1997, Maker Communications, Inc.
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.
Writing: Philomena Dolla, Roy Spencer, Andrea Couvrey, and Alan Twhigg
Editing: Stella Hackell, Nancy Kurahashi, Sonia Saruba, Joanne McClintock
Cover Design: Edmonds Design
Revision History
1 February 2008— 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.
ii ■
End User License Agreement
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY DOWNLOADING,
INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER
OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS
AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE,
AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are 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.
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.
■ iii
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.
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 xv
Part 13 Index
Index 729
Index of Commands and Statements 737
vi ■
Table of Contents
About This Guide xv
Objectives ......................................................................................................xv
Audience ......................................................................................................xvi
Supported Routing Platforms ........................................................................xvi
Using the Indexes ........................................................................................xvii
Documentation Conventions .......................................................................xvii
List of Technical Publications ......................................................................xviii
Documentation Feedback ............................................................................xxv
Requesting Technical Support ......................................................................xxv
Table of Contents ■ ix
JUNOS 9.0 Interfaces Command Reference
x ■ Table of Contents
Table of Contents
Table of Contents ■ xi
JUNOS 9.0 Interfaces Command Reference
Part 13 Index
Index ...........................................................................................................729
Index of Commands and Statements ..........................................................737
This preface provides the following guidelines for using the JUNOS™ Software Interfaces
Command Reference:
■ Objectives on page xv
■ Audience on page xvi
■ Supported Routing Platforms on page xvi
■ Using the Indexes on page xvii
■ Documentation Conventions on page xvii
■ List of Technical Publications on page xviii
■ Documentation Feedback on page xxv
■ Requesting Technical Support on page xxv
Objectives
This reference provides descriptions of the JUNOS software commands that you use
to monitor and troubleshoot all interfaces on the router, including physical interfaces,
service interfaces, the loopback interface, the management Ethernet interface, and
the discard interface.
NOTE: This guide documents Release 9.0 of the JUNOS software. For additional
information about the JUNOS software—either corrections to or information that
might have been omitted from this guide—see the software release notes at
http://www.juniper.net/.
Objectives ■ xv
JUNOS 9.0 Interfaces Command Reference
For information about related tasks performed by Network Operations Center (NOC)
personnel, see the JUNOS Interfaces Network Operations Guide.
Audience
This guide is designed for network administrators who are configuring and monitoring
a Juniper Networks M-series, MX-series, T-series, or J-series 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:
■ Border Gateway Protocol (BGP)
■ Distance Vector Multicast Routing Protocol (DVMRP)
■ Intermediate System-to-Intermediate System (IS-IS)
■ Internet Control Message Protocol (ICMP) router discovery
■ Internet Group Management Protocol (IGMP)
■ Multiprotocol Label Switching (MPLS)
■ Open Shortest Path First (OSPF)
■ Protocol-Independent Multicast (PIM)
■ Resource Reservation Protocol (RSVP)
■ Routing Information Protocol (RIP)
■ Simple Network Management Protocol (SNMP)
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.
xvi ■ Audience
About This Guide
Documentation Conventions
Table 1 on page xvii defines notice icons used in this guide.
Table 2 on page xvii defines the text and syntax conventions used in this guide.
Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen. No alarms currently active
Italic text like this ■ Introduces important new terms. ■ A policy term is a named structure
■ Identifies book names. that defines match conditions and
actions.
■ Identifies RFC and Internet draft
titles. ■ JUNOS System Basics Configuration
Guide
■ RFC 1997, BGP Communities
Attribute
Italic text like this Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name
Plain text like this Represents names of configuration ■ To configure a stub area, include
statements, commands, files, and the stub statement at the [edit
directories; IP addresses; configuration protocols ospf area area-id]
hierarchy levels; or labels on routing hierarchy level.
platform components. ■ The console port is labeled
CONSOLE.
< > (angle brackets) Enclose optional keywords or variables. stub <default-metric metric>;
# (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 [
substitute one or more values. community-ids ]
> (bold right angle bracket) Separates levels in a hierarchy of J-Web In the configuration editor hierarchy,
selections. select Protocols>Ospf.
Table 6 on page xxiv lists additional books on Juniper Networks solutions that you can
order through your bookstore. A complete list of such books is available at
http://www.juniper.net/books.
Book Description
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.
Multiplay Solutions Describes how you can deploy IPTV and voice over IP (VoIP)
services in your network.
MX-series Solutions Guide Describes common configuration scenarios for the Layer 2 features
supported on the MX-series routers, including basic bridged VLANs
with normalized VLAN tags, aggregated Ethernet links, bridge
domains, Multiple Spanning Tree Protocol (MSTP), and integrated
routing and bridging (IRB).
Book Description
Secure Configuration Guide for Common Criteria Provides an overview of secure Common Criteria and JUNOS-FIPS
and JUNOS-FIPS protocols for the JUNOS software and describes how to install and
configure secure Common Criteria and JUNOS-FIPS on a routing
platform.
Software Installation and Upgrade Guide Describes the JUNOS software components and packaging and
explains 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 explains how
to configure basic system parameters, supported protocols and
software processes, authentication, and a variety of utilities for
managing your router on the network.
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
Reference use to monitor and troubleshoot routing policies and protocols,
including firewall filters.
System Basics and Services Command Reference Describes the JUNOS software operational mode commands you
use to monitor and 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 class of service (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.
Book Description
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.
NETCONF API Guide Describes how to use the NETCONF API to monitor and configure
Juniper Networks routing platforms.
JUNOS Configuration and Diagnostic Automation Describes how to use the commit script and self-diagnosis features
Guide of the JUNOS software. This guide explains how to enforce custom
configuration rules defined in scripts, how to use commit script
macros to provide simplified aliases for frequently used
configuration statements, and how to configure diagnostic event
policies.
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's Physical Interface Cards (PICs).
Each platform has its own PIC guide.
DPC Guide Describes the Dense Port Concentrators (DPCs) for all MX-series
routers.
JUNOScope Documentation
JUNOScope Software User Guide Describes the JUNOScope software graphical user interface (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.
Book Description
Getting Started Guide Provides an overview, basic instructions, and specifications for
J-series routing platforms. 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 Guide Explains how to configure the interfaces on J-series Services Routers
for basic IP routing with standard routing protocols, ISDN backup,
and digital subscriber line (DSL) connections.
Advanced WAN Access Configuration Guide Explains how to configure J-series Services Routers in virtual private
networks (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.
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
summarize known problems with the hardware and accompanying
software. Each platform has its own release notes.
JUNOScope 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.
AIS Release Notes Summarize AIS new features and guidelines, identify known and
resolved problems, provide information that might have been
omitted from the manuals, and provide initial setup, upgrade, and
downgrade procedures.
AIS AI Script Release Notes Summarize AI Scripts new features, identify known and resolved
problems, provide information that might have been omitted from
the manuals, and provide instructions for automatic and manual
installation, including deleting and rolling back.
J-series Services Router Release Notes Briefly describe 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.
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.
To configure and operate a J-series Services Router running JUNOS software with
enhanced services, you must also use the configuration statements and operational
mode commands documented in JUNOS configuration guides and command
references. To configure and operate a WX Integrated Services Module, you must
also use WX documentation.
Book Description
JUNOS Software with Enhanced Services Design Provides guidelines and examples for designing and
and Implementation Guide implementing IP Security (IPSec) virtual private networks
(VPNs), firewalls, and routing on J-series routers running
JUNOS software with enhanced services.
JUNOS Software with Enhanced Services J-series Explains how to quickly set up a J-series router. This
Services Router Quick Start document contains router declarations of conformity.
JUNOS Software with Enhanced Services J-series Provides an overview, basic instructions, and specifications
Services Router Getting Started Guide for J-series Services Routers. This guide explains how to
prepare a site, unpack and install the router, replace router
hardware, and establish basic router connectivity. This guide
contains hardware descriptions and specifications.
Book Description
JUNOS Software with Enhanced Services Provides instructions for migrating an SSG device running
Migration Guide ScreenOS software or a J-series router running the JUNOS
software to JUNOS software with enhanced services.
JUNOS Software with Enhanced Services Explains how to configure J-series router interfaces for basic
Interfaces and Routing Configuration Guide IP routing with standard routing protocols, ISDN service,
firewall filters (access control lists), and class-of-service (CoS)
traffic classification.
JUNOS Software with Enhanced Services Security Explains how to configure and manage security services
Configuration Guide such as stateful firewall policies, IPSec VPNs, firewall screens,
Network Address translation (NAT) and Router interface
modes, Public Key Cryptography, and Application Layer
Gateways (ALGs).
JUNOS Software with Enhanced Services Shows how to monitor the router and routing operations,
Administration Guide firewall and security services, system alarms and events,
and network performance. This guide also shows how to
administer user authentication and access, upgrade software,
and diagnose common problems.
JUNOS Software with Enhanced Services CLI Provides the complete JUNOS software with enhanced
Reference services configuration hierarchy and describes the
configuration statements and operational mode commands
not documented in the standard JUNOS manuals.
WXC Integrated Services Module Installation and Explains how to install and initially configure a WXC
Configuration Guide Integrated Services Module in a J-series router for application
acceleration.
JUNOS Software with Enhanced Services Release Summarize new features and known problems for a
Notes particular release of JUNOS software with enhanced services
on J-series routers, including J-Web interface features and
problems. The release notes also contain corrections and
updates to the manuals and software upgrade and
downgrade instructions for JUNOS software with enhanced
services.
Book Description
Interdomain Multicast Provides background and in-depth analysis of multicast routing using Protocol Independent
Routing Multicast sparse mode (PIM SM) and Multicast Source Discovery Protocol (MSDP); details
any-source and source-specific multicast delivery models; explores multiprotocol BGP (MBGP)
and multicast IS-IS; explains Internet Gateway Management Protocol (IGMP) versions 1, 2, and
3; lists packet formats for IGMP, PIM, and MSDP; and provides a complete glossary of multicast
terms.
JUNOS Cookbook Provides detailed examples of common JUNOS software configuration tasks, such as basic router
configuration and file management, security and access control, logging, routing policy, firewalls,
routing protocols, MPLS, and VPNs.
Book Description
MPLS-Enabled Applications Provides an overview of Multiprotocol Label Switching (MPLS) applications (such as Layer 3
virtual private networks [VPNs], Layer 2 VPNs, virtual private LAN service [VPLS], and
pseudowires), explains how to apply MPLS, examines the scaling requirements of equipment
at different points in the network, and covers the following topics: point-to-multipoint label
switched paths (LSPs), DiffServ-aware traffic engineering, class of service, interdomain traffic
engineering, path computation, route target filtering, multicast support for Layer 3 VPNs, and
management and troubleshooting of MPLS networks.
OSPF and IS-IS: Choosing an Explores the full range of characteristics and capabilities for the two major link-state routing
IGP for Large-Scale Networks protocols: Open Shortest Path First (OSPF) and IS-IS. Explains architecture, packet types, and
addressing; demonstrates how to improve scalability; shows how to design large-scale networks
for maximum security and reliability; details protocol extensions for MPLS-based traffic
engineering, IPv6, and multitopology routing; and covers troubleshooting for OSPF and IS-IS
networks.
Routing Policy and Protocols Provides a brief history of the Internet, explains IP addressing and routing (Routing Information
for Multivendor IP Networks Protocol [RIP], OSPF, IS-IS, and Border Gateway Protocol [BGP]), explores ISP peering and
routing policies, and displays configurations for both Juniper Networks and other vendors'
routers.
The Complete IS-IS Protocol Provides the insight and practical solutions necessary to understand the IS-IS protocol and how
it works by using a multivendor, real-world approach.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can 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
■ Document part number
■ Page number
■ Software release version (not required for Network Operations Guides [NOGs])
■ JTAC Hours of Operation —The JTAC centers have resources available 24 hours
a day, 7 days a week, 365 days a year.
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with
the following features:
■ Find CSC offerings: http://www.juniper.net/customers/support/
■ Search for known bugs: http://www2.juniper.net/kb/
■ Find product documentation: http://www.juniper.net/techpubs/
■ Find solutions and answer questions using our Knowledge Base:
http://kb.juniper.net/
To verify service entitlement by product serial number, use our Serial Number
Entitlement (SNE) Tool located at https://tools.juniper.net/SerialNumberEntitlementSearch/
.
About Interfaces ■ 1
JUNOS 9.0 Interfaces Command Reference
2 ■ About Interfaces
Chapter 1
Interface Types
On the M-series and T-series platforms, when you display information about an
interface, you specify the interface type, the slot in which the Flexible PIC
Concentrator (FPC) is installed, the slot on the FPC in which the Physical Interface
Card (PIC) is located, and the configured port number.
In the physical part of the interface name, a hyphen (-) separates the media type
from the FPC number, and a slash (/) separates the FPC, PIC, and port numbers:
type-fpc/pic/port
On the J-series routing platform, when you display information about an interface,
you specify the interface type, the slot in which the Physical Interface Module (PIM)
is installed, 0, and the configured port number.
In the physical part of the interface name, a hyphen (-) separates the media type
from the PIM number, and a slash (/) separates the PIM, 0, and port numbers:
type-pim/0/port
type-fpc/pic/port.logical
type-pim/0/port.logical
A colon (:) separates the physical and virtual parts of the interface name:
■ M-series and T-series routing platforms:
type-fpc/pic/port:channel
type-fpc/pic/port:channel:channel
type-fpc/pic/port:channel:channel:channel
type-pim/0/port:channel
type-pim/0/port:channel:channel
type-pim/0/port:channel:channel:channel
* (asterisk) Match any string of characters in that position in the interface name. For example, so*
matches all SONET/SDH interfaces.
“[character<character...>]” Match one or more individual characters in that position in the interface name. For
example, so-“[03]”* matches all SONET/SDH interfaces in slots 0 and 3.
“[!character<character...>]” Match all characters except the ones included in the brackets. For example, so-“[!03]”*
matches all SONET/SDH interfaces except those in slots 0 and 3.
“[character1-character1character2]” Match a range of characters. For example, so-“[0-3]”* matches all SONET/SDH interfaces
in slots 0, 1, 2, and 3.
“[!character1-character2]” Match all characters that are not in the specified range of characters. For example,
so-“[!0-3]”* matches all SONET/SDH interfaces in slots 4, 5, 6, and 7.
The following examples illustrate the use of wildcards with operational mode
commands:
Discard Interface
The discard (dsc) interface is not a physical interface, but a virtual interface that
discards packets. You can configure one discard interface. This interface allows you
to identify the ingress point of a denial-of-service (DoS) attack. When your network
is under attack, the target host IP address is identified, and the local policy forwards
attacking packets to the discard interface. Traffic routed out of the discard interface
is silently discarded.
Loopback Interface
The JUNOS software automatically configures one loopback interface (lo0), choosing
the first interface to come online as the default. You can also configure the loopback
interface.
When you enter the show interfaces command, the loopback interface and its logical
interfaces are displayed:
For more information, see “Management Ethernet and Internal Ethernet Interface
Operational Mode Commands” on page 707.
Discard Interface ■ 7
JUNOS 9.0 Interfaces Command Reference
The JUNOS software also creates the internal Ethernet interface, fxp1, which connects
the Routing Engine (re0) to the Packet Forwarding Engine. If the routing platform
has redundant Routing Engines, another internal Ethernet interface, fxp2, is created
to connect the second Routing Engine (re1) to the Packet Forwarding Engine.
When you enter the show interfaces command, the management Ethernet and internal
Ethernet interfaces (and logical interfaces) are displayed:
Nonconfigurable Interfaces
The JUNOS software internally generates the nonconfigurable interfaces described
in Table 8 on page 9. For information about related configurable tunnel interfaces,
see “Services Interfaces” on page 14.
8 ■ Nonconfigurable Interfaces
Chapter 1: Interface Types
Related Configurable
Syntax Description Tunnel Interface
ip-pim/0/port
mt-pim/0/port
Physical Interfaces
On M-series and T-series routing platforms, physical interfaces are installed on PICs
and use the syntax type-fpc/pic/port. On the J-series routing platform, physical
interfaces are installed on PIMs and use the syntax type-pim/0/port. Physical interfaces
are described in the following sections:
■ M-series and T-series Physical Interfaces on page 9
■ MX-series Physical Interfaces on page 12
■ J-series Physical Interfaces on page 12
Physical Interfaces ■ 9
JUNOS 9.0 Interfaces Command Reference
Gigabit Ethernet
Channelized STM1 IQ
Channelized STM1 IQ
Channelized OC12 IQ
Channelized OC3 IQ
Channelized OC12 IQ
Channelized T1 IQ
Channelized OC3 IQ
Channelized OC12 IQ
10 ■ Physical Interfaces
Chapter 1: Interface Types
Channelized DS3 IQ
Channelized E1
Channelized E1 IQ
Channelized OC3 IQ
Channelized OC12 IQ
Channelized STM1 IQ
E1 e1-fpc/pic/port Channelized E1 IQ
Channelized STM1
Channelized STM1 IQ
E1
E3 e3-fpc/pic/port E3
E3 IQ
Channelized OC12 IQ
Channelized OC12 IQ
Physical Interfaces ■ 11
JUNOS 9.0 Interfaces Command Reference
Channelized DS3 IQ
Channelized OC3 IQ
Channelized OC12 IQ
Channelized T1 IQ
Multichannel DS3
T1 (all)
Channelized OC3 IQ
Channelized OC12
Channelized OC12 IQ
DS3
T3 (all)
Gigabit Ethernet
12 ■ Physical Interfaces
Chapter 1: Interface Types
D-channel dc-pim/0/portpim
Dialer dlnumber
E1 e1-pim/0/port Dual-Port E1
E3 e3-pim/0/port E3
T1 t1-pim/0/port Dual-Port T1
T3 t3-pim/0/port T3 (all)
NOTE: ADSL interfaces and SHDSL interfaces are supported on the J-series routing
platform only. Both interfaces are configured over an underlying ATM interface. For
more information, see “ATM Interface Operational Mode Commands” on page 367.
NOTE: Point-to-Point Protocol over Ethernet (PPPoE) interfaces (pp0) are supported
on the J-series routing platform and the M120 Internet router only. A PPPoE interface
is configured over an underlying Ethernet interface. For more information, see “PPPoE
Interface Operational Mode Commands” on page 277.
Physical Interfaces ■ 13
JUNOS 9.0 Interfaces Command Reference
Services Interfaces
Services interfaces provide specific capabilities for manipulating traffic before it is
delivered to its destination.
NOTE: On M-series and T-series routing platforms, services interfaces are installed
on PICs. On the J-series routing platform, services interfaces are software-based.
MultiServices
Tunnel Services
MultiServices
Tunnel Services
MultiServices
14 ■ Services Interfaces
Chapter 1: Interface Types
Link Services
MultiServices
Tunnel Services
Link Services
MultiServices
Tunnel Services
Link Services
MultiServices
Tunnel Services
Link Services
MultiServices
Tunnel Services
Encryption es-fpc/pic/port ES
Monitoring Services II
MultiServices
MultiServices
Services Interfaces ■ 15
JUNOS 9.0 Interfaces Command Reference
Link Services
MultiServices
Tunnel Services
Interface Syntax
GRE gr-pim/0/port
16 ■ Services Interfaces
Chapter 2
Common Interface Commands
Task Command
Clear the channel service unit (CSU) alarm and defect counters. clear interfaces interval on page 19
Display brief information about all configured interfaces. show interfaces brief on page 23
Display detailed information about all configured interfaces. show interfaces detail on page 28
Display extensive information about all configured interfaces. show interfaces extensive on page 30
Display all firewall filters that are installed on each interface. show interfaces filters on page 33
Display CSU interface alarm and error counts for the past 24 hours. show interfaces interval on page 35
Display media-specific information about all configured network show interfaces media on page 37
interfaces.
Display all firewall policers that are installed on each interface. show interfaces policers on page 39
Display class-of-service (CoS) information per physical interface. show interfaces queue on page 41
Display the routing protocol process view of the router's interfaces show interfaces routing on page 63
status.
Display a summary of the routing protocol process view of the router’s show interfaces routing summary on page 66
interfaces status.
Display information about the SNMP index of an interface. show interfaces snmp-index on page 68
Display information about interfaces grouped by source class. show interfaces source-class on page 69
■ 17
JUNOS 9.0 Interfaces Command Reference
Task Command
Display static interface statistics, such as errors. show interfaces statistics on page 71
NOTE: For information about the monitor interface and monitor traffic commands,
see the JUNOS System Basics and Services Command Reference. For information about
the show interfaces controller command, see the channelized interfaces chapters in
this reference.
18 ■
Chapter 2: Common Interface Commands
clear interfaces interval The following example displays the output for a T3 interface before and after the
clear interfaces command is entered:
Additional Information For interfaces that carry IPv4, IPv6, or Multiprotocol Label Switching (MPLS) traffic,
you can maintain packet counts based on the entry and exit points for traffic passing
through your network. Entry and exit points are identified by source and destination
prefixes grouped into sets defined as source classes and destination classes. For
more information, see the JUNOS Network Interfaces Configuration Guide.
Destination class Name of destination class usage (DCU) counters per class for this
interface.
Packets Bytes
Source class (packet-per-second) (bits-per-second)
gold1 0 0
( 0) ( 0)
gold2 0 0
( 0) ( 0)
gold3 0 0
( 0) ( 0)
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.27.248/24, Local: 10.27.248.1, Broadcast: 10.27.248.255,
Generation: 152
Protocol iso, MTU: 4470, Generation: 157, Route table: 2
Flags: Protocol-Down, Is-Primary
0 best-effort 66 66 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
% bps % usec
0 best-effort 95 95000000 95 0 low none
3 network-control 5 5000000 5 0 low none
Logical interface fe-0/2/0.0 (Index 66) (SNMP ifIndex 46) (Generation 133)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: DCU, SCU-out
Packets Bytes
Destination class (packet-per-second) (bits-per-second)
silv1_new 0 0
( 0) ( 0)
silv2_new 0 0
( 0) ( 0)
silv_misc 0 0
( 0) ( 0)
silver0 0 0
( 0) ( 0)
silver2 0 0
( 0) ( 0)
silver3 0 0
( 0) ( 0)
silver4 0 0
( 0) ( 0)
silver5 0 0
( 0) ( 0)
silver6 0 0
( 0) ( 0)
silver7 0 0
( 0) ( 0)
silver9 0 0
( 0) ( 0)
Packets Bytes
Source class (packet-per-second) (bits-per-second)
gold1 0 0
( 0) ( 0)
gold2 16600 1062400
( 0) ( 0)
gold3 0 0
( 0) ( 0)
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.1.1/24, Local: 12.1.1.1, Broadcast: 12.1.1.255,
Generation: 150
Additional Information For information about how to configure firewall filters, see the JUNOS Policy
Framework Configuration Guide. For related operational mode commands, see the
JUNOS Routing Protocols and Policies Command Reference.
Input Filter Name of the firewall filter to be evaluated when packets are
received on the interface.
Output Filter Name of the firewall filter to be evaluated when packets are
transmitted on the interface.
hh:mm-current Time of day (in hours and minutes) at the beginning of the latest
counter interval. The value of the latest counter interval is always
less than 15 minutes.
hh:mm-hh:mm Time of day (in hours and minutes) at the beginning and end of
each 15-minute interval.
alarm or event: n Count of alarms and events within each 15-minute interval. The
specific alarm or event depends on the interface media type. For
a description of the alarm or event listed, see the interface-type
media field (for example, T1 media) under the show interfaces
command for the particular interface type in which you are
interested.
Interval Total Sum of all the alarm and defect counters for the last 24-hour period.
Additional Information Output from both the show interfaces interface-name detail and the show interfaces
interface-name extensive commands includes all the information displayed in the
output from the show interfaces media command.
One field unique to the show interfaces media command is interface-type errors (for
example, SONET errors). This field appears for channelized E3, channelized T3,
channelized OC, E1, E3, SONET, T1, and T3 interfaces. The information provided in
this output field is also provided in the output from the show interfaces interface-name
command. (For example, for SONET interfaces, these fields are SONET section, SONET
line, and SONET path). For a description of errors, see the chapter with the particular
interface type in which you are interested.
show interfaces media The following example displays the output fields unique to the show interfaces media
(SONET/SDH) command for a SONET interface (with no level of output specified):
user@host> show interfaces media so-4/1/2
Physical interface: so-4/1/2, Enabled, Physical link is Up
Interface index: 168, SNMP ifIndex: 495
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC48,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags : Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 1783 (00:00:00 ago), Output: 1786 (00:00:08 ago)
LCP state: Opened
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Not-configured
CoS queues : 8 supported
Last flapped : 2005-06-15 12:14:59 PDT (04:31:29 ago)
Input rate : 0 bps (0 pps)
Output rate : 0 bps (0 pps)
SONET alarms : None
SONET defects : None
SONET errors:
BIP-B1: 121, BIP-B2: 916, REI-L: 0, BIP-B3: 137, REI-P: 16747, BIP-BIP2: 0
Received path trace: routerb so-1/1/2
Transmitted path trace: routera so-4/1/2
Additional Information For information about how to configure policers, see the JUNOS Policy Framework
Configuration Guide. For related operational mode commands, see the JUNOS Routing
Protocols and Policies Command Reference.
Input Policer Policer to be evaluated when packets are received on the interface.
It has the format interface-name-in-policer.
Options none—Show detailed CoS queue statistics for all physical interfaces.
Additional Information On the M-series routing platform (except for the M320 and M120 routers), this
command is valid only for a PIC installed on an enhanced Flexible PIC Concentrator
(FPC).
Queue statistics for aggregated interfaces are supported on the M-series and T-series
routing platforms only. Statistics for an aggregated interface are the summation of
the queue statistics of the child links of that aggregated interface. You can view the
statistics for a child interface by using the show interfaces statistics command for
that child interface.
When you configure tricolor marking on a 10-port 1-Gigabit Ethernet PIC, for queues
6 and 7 only, the output does not display the number of queued bytes and packets,
or the number of bytes and packets dropped because of RED. If you do not configure
tricolor marking on the interface, these statistics are available for all queues.
For Gigabit Ethernet IQ2 PICs, the show interfaces queue command output does not
display the number of tail-dropped packets. This limitation does not apply to
Forwarding Engine chassis queues.
When fragmentation occurs on the egress interface, the first set of packet counters
shows the postfragmentation values. The second set of packet counters (under the
Packet Forwarding Engine Chassis Queues field) shows the prefragmentation values.
For information about how to configure CoS, see the JUNOS Network Interfaces
Configuration Guide. For related CoS operational mode commands, see the JUNOS
System Basics and Services Command Reference.
Enabled State of the interface. Possible values are described in “Enabled Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence.
Forwarding classes Total number of forwarding classes supported on the specified interface.
supported
Forwarding classes in Total number of forwarding classes in use on the specified interface.
use
Ingress queues On Gigabit Ethernet IQ2 PICs only, total number of ingress queues supported on the specified
supported interface.
Ingress queues in use On Gigabit Ethernet IQ2 PICs only, total number of ingress queues in use on the specified interface.
Output queues Total number of output queues supported on the specified interface.
supported
Output queues in use Total number of output queues in use on the specified interface.
Egress queues Total number of egress queues supported on the specified interface.
supported
Egress queues in use Total number of egress queues in use on the specified interface.
Ingress queues in use Total number of ingress queues supported on the specified interface. Displayed on IQ2 interfaces.
Queue counters CoS queue number and its associated user-configured forwarding class name. Displayed on IQ2
(Ingress) interfaces.
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED mechanism.
Burst size (Logical interfaces on IQ PICs only) Maximum number of bytes up to which the logical interface can
burst. The burst size is based on the shaping rate applied to the interface.
NOTE: For Gigabit Ethernet IQ2 interfaces, the Queued Packets count is calculated by the JUNOS
software assuming that one frame buffer represents one packet. If the queued packets are very large
or very small, the calculation might not be completely accurate for transit traffic. The count is
completely accurate for traffic terminated on the router.
Queued Bytes Number of bytes queued to this queue. The byte counts vary by PIC type. For more information,
see Table 21 on page 45.
Transmitted Packets Number of packets transmitted by this queue. When fragmentation occurs on the egress interface,
the first set of packet counters shows the postfragmentation values. The second set of packet counters
(displayed under the Packet Forwarding Engine Chassis Queues field) shows the prefragmentation
values.
Transmitted Bytes Number of bytes transmitted by this queue. The byte counts vary by PIC type. For more information,
see Table 21 on page 45.
RED-dropped packets Number of packets dropped because of random early detection (RED).
■ (M-series and T-series routing platforms only) On M320 and M120 routers and the T-series
routing platform, the total number of dropped packets is displayed. On all other M-series routers,
the output classifies dropped packets into the following categories:
■ Low, non-TCP—Number of low-loss priority non-TCP packets dropped because of RED.
■ Low, TCP—Number of low-loss priority TCP packets dropped because of RED.
■ High, non-TCP—Number of high-loss priority non-TCP packets dropped because of RED.
■ High, TCP—Number of high-loss priority TCP packets dropped because of RED.
■ (J-series routing platform and MX-series routers with enhanced DPCs only) The output classifies
dropped packets into the following categories:
■ Low—Number of low-loss priority packets dropped because of RED.
■ Medium-low—Number of medium-low loss priority packets dropped because of RED.
■ Medium-high—Number of medium-high loss priority packets dropped because of RED.
■ High—Number of high-loss priority packets dropped because of RED.
RED-dropped bytes Number of bytes dropped because of RED. The byte counts vary by PIC type. For more information,
see Table 21 on page 45.
■ (M-series and T-series routing platforms only) On M320 and M120 routers and the T-series
routing platform, only the total number of dropped bytes is displayed. On all other M-series
routers, the output classifies dropped bytes into the following categories:
■ Low, non-TCP—Number of low-loss priority non-TCP bytes dropped because of RED.
■ Low, TCP—Number of low-loss priority TCP bytes dropped because of RED.
■ High, non-TCP—Number of high-loss priority non-TCP bytes dropped because of RED.
■ High, TCP—Number of high-loss priority TCP bytes dropped because of RED.
■ (J-series routing platform only) The output classifies dropped bytes into the following categories:
■ Low—Number of low-loss priority bytes dropped because of RED.
■ Medium-low—Number of medium-low loss priority bytes dropped because of RED.
■ Medium-high—Number of medium-high loss priority bytes dropped because of RED.
■ High—Number of high-loss priority bytes dropped because of RED.
Byte counts vary by PIC type. Table 21 on page 45 shows how the byte counts on
the outbound interfaces vary depending on the PIC type. Table 21 on page 45 is
based on the assumption that outbound interfaces are sending IP traffic with 478 bytes
per packet.
Gigabit Interface Queued: 490 bytes per packet, representing The 12 additional bytes include
Ethernet IQ PIC 478 bytes of Layer 3 packet + 12 bytes 6 bytes for the destination MAC
address + 4 bytes for the VLAN +
Transmitted: 490 bytes per packet, representing 2 bytes for the Ethernet type.
478 bytes of Layer 3 packet + 12 bytes
For RED dropped, 6 bytes are added
RED dropped: 496 bytes per packet representing for the source MAC address.
478 bytes of Layer 3 packet + 18 bytes
Non-IQ PIC Interface Queued: 478 bytes of Layer 3 packet + the full The Layer 2 overhead is 14 bytes for
Layer 2 overhead. non-VLAN traffic and 18 bytes for
VLAN traffic.
Transmitted: 478 bytes of Layer 3 packet + the full
Layer 2 overhead.
IQ PIC with a Interface Queued: 482 bytes per packet, representing The additional 4 bytes are for the
SONET/SDH 478 bytes of Layer 3 packet + 4 bytes Layer 2 Point-to-Point Protocol (PPP)
interface header.
Transmitted: 482 bytes per packet, representing
478 bytes of Layer 3 packet + 4 bytes
Packet Queued: 478 bytes per packet, representing For transmitted packets, the
forwarding 478 bytes of Layer 3 packet additional 8 bytes includes 4 bytes for
component the PPP header and 4 bytes for a
Transmitted: 486 bytes per packet, representing cookie.
478 bytes of Layer 3 packet + 8 bytes
Non-IQ PIC Interface Queued: 478 bytes per packet, representing For transmitted packets, the
with a 478 bytes of Layer 3 packet additional 5 bytes includes 4 bytes for
SONET/SDH the PPP header and 1 byte for the
interface Transmitted: 483 bytes per packet, representing packet loss priority (PLP).
478 bytes of Layer 3 packet + 5 bytes
1-port 10 Interface Queued: 120 bytes of Layer 3 packet Calculated for LAN-PHY signal in an
Gigabit an OC-192 payload for an IP packet
Ethernet IQ2 Transmitted: 148 bytes per packet, representing of 120 bytes. The total overhead is the
PIC 120 bytes of Layer 3 packet + 28 bytes of SONET LAN PHY overhead plus the SONET
and Ethernet overhead overhead.
show interfaces queue The following example shows that the aggregated Ethernet interface, ae1, has traffic
(Aggregated Ethernet on on queues af1 and af12:
a T320 Router)
user@host> show interfaces queue ae1
Physical interface: ae1, Enabled, Physical link is Up
Interface index: 158, SNMP ifIndex: 33 Forwarding classes: 8 supported, 8 in use
Output queues: 8 supported, 8 in use
Queue: 0, Forwarding classes: be
Queued:
Packets : 5 0 pps
Bytes : 242 0 bps
Transmitted:
Packets : 5 0 pps
Bytes : 242 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 1, Forwarding classes: af1
Queued:
Packets : 42603765 595484 pps
Bytes : 5453281920 609776496 bps
Transmitted:
Packets : 42603765 595484 pps
Bytes : 5453281920 609776496 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 2, Forwarding classes: ef1
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 3, Forwarding classes: nc
Queued:
Packets : 45 0 pps
Bytes : 3930 0 bps
Transmitted:
Packets : 45 0 pps
Bytes : 3930 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 4, Forwarding classes: af11
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 5, Forwarding classes: ef11
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 6, Forwarding classes: af12
Queued:
Packets : 31296413 437436 pps
Bytes : 4005940864 447935200 bps
Transmitted:
Packets : 31296413 437436 pps
Bytes : 4005940864 447935200 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 7, Forwarding classes: nc2
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Transmitted:
Packets : 76397439 487512 pps
Bytes : 4125461868 210602376 bps
Tail-dropped packets : Not Available
RED-dropped packets : 72053285 459783 pps
Low : 72053285 459783 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 3890877444 198626472 bps
Low : 3890877444 198626472 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 410278257 473940 pps
Bytes : 22156199518 204742296 bps
Transmitted:
Packets : 4850003 4033 pps
Bytes : 261900162 1742256 bps
Tail-dropped packets : Not Available
RED-dropped packets : 405425693 469907 pps
Low : 405425693 469907 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 21892988124 203000040 bps
Low : 21892988124 203000040 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Forwarding classes: 16 supported, 4 in use
Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets : 76605230 485376 pps
Bytes : 5209211400 264044560 bps
Transmitted:
Packets : 76444631 484336 pps
Bytes : 5198235612 263478800 bps
Tail-dropped packets : Not Available
RED-dropped packets : 160475 1040 pps
Low : 160475 1040 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 10912300 565760 bps
Low : 10912300 565760 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 4836136 3912 pps
Bytes : 333402032 2139056 bps
Transmitted:
Packets : 3600866 1459 pps
Bytes : 244858888 793696 bps
Tail-dropped packets : Not Available
RED-dropped packets : 1225034 2450 pps
Low : 1225034 2450 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 83302312 1333072 bps
Low : 83302312 1333072 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 7055 1 pps
Bytes : 451552 512 bps
Transmitted:
Packets : 7055 1 pps
Bytes : 451552 512 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Forwarding classes: 16 supported, 4 in use Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets : 1031 0 pps
Bytes : 143292 0 bps
Transmitted:
Packets : 1031 0 pps
Bytes : 143292 0 bps
Tail-dropped packets : Not Available
RL-dropped packets : 0 0 pps
RL-dropped bytes : 0 0 bps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RL-dropped packets : 0 0 pps
RL-dropped bytes : 0 0 bps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RL-dropped packets : 0 0 pps
RL-dropped bytes : 0 0 bps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 77009 11 pps
Bytes : 6894286 7888 bps
Transmitted:
Packets : 77009 11 pps
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Forwarding classes: 8 supported, 4 in use
Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets : Not Available
Bytes : 0 0 bps
Transmitted:
Packets : 3 0 pps
Bytes : 126 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : Not Available
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : Not Available
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : Not Available
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Packet Forwarding Engine Chassis Queues:
Queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets : 80564692 0 pps
Bytes : 3383717100 0 bps
Transmitted:
Packets : 80564692 0 pps
Bytes : 3383717100 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Forwarding classes: 16 supported, 4 in use
Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Options none—Display standard information about the state of all router interfaces on all
logical routers.
Additional Information For information about how to configure routing protocols, see the JUNOS Routing
Protocols Configuration Guide. For information about related operational mode
commands for routing instances and protocols, see the JUNOS Routing Protocols and
Policies Command Reference.
Index Interface index number, which reflects its initialization sequence. detail
Change Reflects one or more of the following recent changes to the interface: detail
■ Add—The interface was just added.
■ Address—The interface's link-layer address has changed.
■ Delete—The interface is being deleted.
■ Encapsulation—The type of encapsulation on the interface has changed.
■ Metric—The interface's metric value has changed.
■ MTU—The interface's maximim transmission unit size has changed.
■ UpDown—The interface has made an up or down transition.
Up/down transitions Number of times the interface has gone from Down to Up. detail
Protocol address Information about the configuration of protocols on the interface: detail
■ Address—Address configured on the interface for the protocol type.
■ State—State (Up or down) and type of interface.
■ Change—Reflects one or more of the following recent changes to the
interface:
■ Add—The interface was just added.
■ Address—The interface's address has changed.
■ Broadcast—The interface's broadcast address has changed.
■ Delete—The interface is being deleted.
■ Netmask—The interface's netmask has changed.
■ UpDown—The interface has made an up or down transition.
■ Preference—Preference value for the route for this address.
■ Metric—Metric value on the interface for the protocol type.
■ MTU—Maximim transmission unit value of the interface.
■ Local address—On a point-to-point link, the address of the local side of
the link. Not used for multicast links.
■ Destination—For a point-to-point link, the address of the remote side of
the link. For multicast links, the network address.
INET 192.168.2.130
INET enabled
at-1/0/0.3 Up CCC enabled
at-1/0/0.2 Up CCC enabled
at-1/0/0.0 Up ISO enabled
INET 192.168.90.10
INET enabled
lo0.0 Up ISO 47.0005.80ff.f800.0000.0108.0001.1921.6800.5061.00
ISO enabled
INET 127.0.0.1
fxp1.0 Up
fxp0.0 Up INET 192.168.6.90
Options none—Display summary information about the state of all router interfaces on all
logical routers.
Additional Information For information about how to configure routing protocols, see the JUNOS Routing
Protocols Configuration Guide. For information about related operational mode
commands for routing instances and protocols, see the JUNOS Routing Protocols and
Policies Command Reference.
n protocol protocol Type and number of routing protocols and number of related
interfaces interfaces in the up state.
Trans Number of times the interface has transitioned from Down to Up).
Additional Information Output from both the show interfaces interface-name detail and the show interfaces
interface-name extensive command includes all the information displayed in the output
from the show interfaces snmp-index command.
Additional Information For interfaces that carry IPv4, IPv6, or Multiprotocol Label Switching (MPLS) traffic,
you can maintain packet counts based on the entry and exit points for traffic passing
through your network. Entry and exit points are identified by source and destination
prefixes grouped into sets defined as source classes and destination classes. For
more information, see the JUNOS Network Interfaces Configuration Guide.
Source class Source class usage (SCU) counters per class for this interface.
( 0) ( 0)
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10.27.245/24, Local: 10.27.245.2,
Broadcast: 10.27.245.255
Protocol iso, MTU: 1497
Flags: Is-Primary
Logical interface ae0.0 (Index 67) (SNMP ifIndex 139) (Generation 145)
Flags: SNMP-Traps Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 508 0 28544 0
Output: 509 0 35698 0
Link:
ge-3/3/8.0
Input : 508 0 28544 0
Output: 0 0 0 0
ge-3/3/9.0
Input : 0 0 0 0
Output: 0 0 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-3/3/8.0 0 0 0 0
ge-3/3/9.0 0 0 0 0
Egress queues: 8 supported, 8 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Additional Information Interfaces are always displayed in numerical order, from the lowest to the highest
FPC slot number. Within that slot, the lowest PIC slot is shown first. On an individual
PIC, the lowest port number is always first.
lsi up up
mtun up up
This chapter explains the content of the following fields, which appear in the output
of most show interfaces commands:
■ Destination Class Field on page 77
■ Enabled Field on page 78
■ Filters Field on page 78
■ Flags Fields on page 78
■ Label-Switched Interface Traffic Statistics Field on page 82
■ Policer Field on page 83
■ Protocol Field on page 83
■ RPF Failures Field on page 84
■ Source Class Field on page 84
For the logical interface, the Destination class field provides the names of destination
class usage (DCU) counters per family and per class for a particular interface. The
counters display packets and bytes arriving from designated user-selected prefixes.
For example:
Packets Bytes
Destination class (packet-per-second) (bits-per-second)
Enabled Field
For the physical interface, the Enabled field provides information about the state of
the interface, displaying one or more of the following values:
■ Administratively down, Physical link is Down—The interface is turned off, and the
physical link is inoperable and cannot pass packets even when it is enabled.
■ Administratively down, Physical link is Up—The interface is turned off, but the
physical link is operational and can pass packets when it is enabled.
■ Enabled, Physical link is Down—The interface is turned on, but the physical link
is inoperable and cannot pass packets.
■ Enabled, Physical link is Up—The interface is turned on, and the physical link is
operational and can pass packets.
Filters Field
For the logical interface, the Filters field provides the name of the firewall filters to
be evaluated when packets are received or transmitted on the interface. The format
is Filters: Input: filter-name and Filters: Output: filter-name. For example:
Flags Fields
The following sections provide information about flags that are specific to interfaces:
■ Addresses, Flags on page 79
■ Device Flags on page 79
■ Family Flags on page 80
■ Interface Flags on page 80
■ Link Flags on page 81
■ Logical Interface Flags on page 82
78 ■ Enabled Field
Chapter 3: Common Output Fields
Addresses, Flags
The Addresses, Flags field, which provides information about the addresses configured
for the protocol family on the logical interface, displays one or more of the following
values:
■ Dest-route-down—The routing process detected that the link was not operational
and changed the interface routes to nonforwarding status
■ Is-Default—This address is the default address of the router. The default address
is used as the source address by SNMP, ping, traceroute, and other network
utilities.
■ Is-Preferred—This address is the default local address for packets originating from
the local router and sent to destinations on the subnet.
■ Is-Primary—This address is the default local address for broadcast and multicast
packets originated locally and sent out the interface.
■ Preferred—This address is a candidate to become the preferred address.
■ Primary—This address is a candidate to become the primary address.
Device Flags
The Device flags field, which provides information about the physical device, displays
one or more of the following values:
■ Down—Device has been administratively disabled.
■ Hear-Own-Xmit—Device receives its own transmissions.
■ Link-Layer-Down—The link-layer protocol has failed to connect with the remote
endpoint.
■ Loopback—Device is in physical loopback.
■ Loop-Detected—The link layer has received frames that it sent, thereby detecting
a physical loopback.
■ No-Carrier—On media that support carrier recognition, no carrier is currently
detected.
■ No-Multicast—Device does not support multicast traffic.
■ Present—Device is physically present and recognized.
■ Promiscuous—Device is in promiscuous mode and recognizes frames addressed
to all physical addresses on the media.
■ Quench—Transmission on the device is quenched, because the output buffer
is overflowing
■ Recv-All-Multicasts—Device is in multicast promiscuous mode and therefore
provides no multicast filtering.
■ Running—Device is active and enabled.
Flags Fields ■ 79
JUNOS 9.0 Interfaces Command Reference
Family Flags
The Family flags field, which provides information about the protocol family on the
logical interface, displays one or more of the following values:
■ DCU—Destination class usage is enabled.
■ Dest-route-down—The software detected that the link is down and has stopped
forwarding the link's interface routes.
■ Down—Protocol is inactive.
■ Is-Primary—Interface is the primary one for the protocol.
■ MTU-Protocol-Adjusted—The effective MTU is not the configured value in the
software.
■ No-Redirects—Protocol redirects are disabled.
■ Primary—Interface can be considered for selection as the primary family address.
■ Protocol-Down—Protocol failed to negotiate correctly.
■ SCU-in—Interface is configured for source class usage input.
■ SCU-out—Interface is configured for source class usage output.
■ Unnumbered—Protocol family is configured for unnumbered Ethernet. An
unnumbered Ethernet interface borrows an IPv4 address from another interface,
which is referred to as the donor interface.
■ Up–Protocol is configured and operational.
■ uRPF—Unicast Reverse Path Forwarding is enabled.
Interface Flags
The Interface flags field, which provides information about the physical interface,
displays one or more of the following values:
■ Admin-Test—Interface is in test mode and some sanity checking, such as loop
detection, is disabled.
■ Disabled—Interface is administratively disabled.
■ Down—A hardware failure has occurred.
■ Hardware-Down—Interface is nonfunctional or incorrectly connected.
■ Link-Layer-Down—Interface keepalives have indicated that the link is incomplete.
■ No-Multicast—Interface does not support multicast traffic.
■ No-receive No-transmit—Passive monitor mode is configured on the interface.
■ Point-To-Point—Interface is point to point.
■ Pop all MPLS labels from packets of depth—MPLS labels are removed as packets
arrive on an interface that has the pop-all-labels statement configured. The depth
value can be one of the following:
■ 1—Takes effect for incoming packets with one label only.
80 ■ Flags Fields
Chapter 3: Common Output Fields
■ [ 1 2 ]—Takes effect for incoming packets with either one or two labels.
Link Flags
The Link flags field, which provides information about the physical link, displays one
or more of the following values:
■ ACFC—Address control field compression is configured. The Point-to-Point
Protocol (PPP) session negotiates the ACFC option.
■ Give-Up—Link protocol does not continue connection attempts after repeated
failures.
■ Loose-LCP—PPP does not use Link Control Protocol (LCP) to indicate whether
the link protocol is operational.
■ Loose-LMI—Frame Relay does not use the Local Management Interface (LMI) to
indicate whether the link protocol is operational.
■ Loose-NCP—PPP does not use the Network Control Protocol (NCP) to indicate
whether the device is operational.
■ No-Keepalives—Link protocol keepalives are disabled.
■ PFC—Protocol field compression is configured. The PPP session negotiates the
PFC option.
Flags Fields ■ 81
JUNOS 9.0 Interfaces Command Reference
When you use the vrf-table-label statement to configure a VRF routing table, a
label-switched interface (LSI) logical interface label is created and mapped to the VRF
routing table.
Any routes present in a VRF routing table and configured with the vrf-table-label
statement are advertised with the LSI logical interface label allocated for the VRF
routing table. When packets for this VPN arrive on a core-facing interface, they are
treated as if the enclosed IP packet arrived on the LSI interface and are then forwarded
and filtered based on the correct table. For more information on the vrf-table-label
statement, including a list of supported interfaces, see the JUNOS VPNs Configuration
Guide.
If you configure the family mpls statement at the [edit interfaces interface-name unit
logical-unit-number] hierarchy level and you also configure the vrf-table-label statement
at the [edit routing-instances routing-instance-name] hierarchy level, the output for the
show interface interface-name extensive command includes the following output fields
about the LSI traffic statistics:
■ Input bytes—Number of bytes entering the LSI and the current throughput rate
in bits per second (bps).
■ Input packets—Number of packets entering the LSI and the current throughput
rate in packets per second (pps).
The following example shows the LSI traffic statistics that you might see as a part of
the output of the show interface interface-name extensive command:
Policer Field
For the logical interface, the Policer field provides the policers that are to be evaluated
when packets are received or transmitted on the interface. The format is Policer:
Input: type-fpc/picport-in-policer, Output: type-fpc/pic/port-out-policer. For example:
Protocol Field
For the logical interface, the Protocol field indicates the protocol family or families
that are configured on the interface, displaying one or more of the following values:
■ aenet—Aggregated Ethernet. Displayed on Fast Ethernet interfaces that are part
of an aggregated Ethernet bundle.
■ ccc—Circuit cross-connect (CCC). Configured on the logical interface of CCC
physical interfaces.
■ inet—IP version 4 (IPv4). Configured on the logical interface for IPv4 protocol
traffic, including Open Shortest Path First (OSPF), Border Gateway Protocol (BGP),
Internet Control Message Protocol (ICMP), and Internet Protocol Control Protocol
(IPCP).
■ inet6—IP version 6 (IPv6). Configured on the logical interface for IPv6 protocol
traffic, including Routing Information Protocol for IPv6 (RIPng), Intermediate
System-to-Intermediate System (IS-IS), and BGP.
■ iso—International Organization for Standardization (ISO). Configured on the
logical interface for IS-IS traffic.
■ mlfr-uni-nni—Multilink Frame Relay (MLFR) FRF.16 user-to-network
network-to-network (UNI NNI). Configured on the logical interface for link services
bundling.
■ mlfr-end-to-end—Multilink Frame Relay end-to-end. Configured on the logical
interface for multilink bundling.
■ mlppp—MLPPP. Configured on the logical interface for multilink bundling.
■ mpls—Multiprotocol Label Switching (MPLS). Configured on the logical interface
for participation in an MPLS path.
■ tcc—Translational cross-connect (TCC). Configured on the logical interface of
TCC physical interfaces.
■ tnp—Trivial Network Protocol. Used to communicate between the Routing Engine
and the routing platform's packet forwarding components. The JUNOS software
automatically configures this protocol family on the routing platform's internal
interfaces only.
■ vpls—Virtual private LAN service (VPLS). Configured on the logical interface on
which you configure VPLS.
Policer Field ■ 83
JUNOS 9.0 Interfaces Command Reference
For the logical interface, the RPF Failures field provides information about the amount
of incoming traffic (in packets and bytes) that failed a unicast reverse path forwarding
(RPF) check on a particular interface. The format is RPF Failures: Packets: xx, Bytes:
yy. For example:
For the logical interface, the Source class field provides the names of source class
usage (SCU) counters per family and per class for a particular interface. The counters
display packets and bytes arriving from designated user-selected prefixes. For
example:
Packets Bytes
Source class (packet-per-second) (bits-per-second)
Ethernet Interfaces ■ 85
JUNOS 9.0 Interfaces Command Reference
86 ■ Ethernet Interfaces
Chapter 4
Ethernet Interface Operational Mode
Commands
Task Command
Clear learned MAC addresses from the hardware and MAC database. clear interfaces mac-database on page 89
Static MAC addresses are not cleared.
Clear statistics that are collected for every MAC address, including clear interfaces mac-database statistics on page 90
policer statistics, on a given physical or logical interface.
Clear statistics that are collected for interface sets. clear interfaces interface-set statistics on page 22
Clear Operation, Administration, and Management (OAM) connectivity clear oam ethernet connectivity-fault-management
fault management linktrace database information. linktrace path-database on page 92
Clear Operation, Administration, and Management (OAM) link fault clear oam ethernet link-fault-management
management state information and restart the link discovery process state on page 93
on Ethernet interfaces.
Clear Operation, Administration, and Management (OAM) statistics link clear oam ethernet link-fault-management
fault management statistics for Ethernet interfaces. statistics on page 94
Display status information about aggregated Fast Ethernet or Gigabit show interfaces (Aggregated Ethernet) on page 95
Ethernet router interfaces.
Display information about IP demultiplexing interfaces using an show interfaces demux0 (Demux
underlying Ethernet interface. Interfaces) on page 252
Display the transceiver temperature, laser bias current, laser output show interfaces diagnostics optics (10-Gigabit
power, receive optical power, and related alarms for 10-Gigabit Ethernet Ethernet) on page 145
dense wavelength-division multiplexing (DWDM) interfaces.
Display status information about Fast Ethernet interfaces. show interfaces (Fast Ethernet) on page 104
Display status information about 10-Gigabit Ethernet router interfaces. show interfaces (10-Gigabit Ethernet) on page 126
■ 87
JUNOS 9.0 Interfaces Command Reference
Task Command
Display information about Gigabit Ethernet or 10-Gigabit Ethernet router show interfaces interface-set (Ethernet Interface
interface sets. Set) on page 135
Display information about Gigabit Ethernet or 10-Gigabit Ethernet router show interfaces interface-set queue on page 137
interface set queues.
Display information about integrated routing and bridging interfaces. show interfaces irb on page 162
Display MAC address information for Gigabit Ethernet router interfaces. show interfaces mac-database (Gigabit
Ethernet) on page 168
Display Link Aggregation Control Protocol (LACP) information for show lacp interfaces on page 171
aggregated, Fast Ethernet, or Gigabit Ethernet router interfaces.
Display IEEE 802.1ag OAM connectivity fault management forwarding show oam ethernet connectivity-fault-management
state information for Ethernet interfaces. forwarding-state on page 180
Display OAM connectivity fault management information for Ethernet show oam ethernet connectivity-fault-management
interfaces. interfaces on page 184
Display OAM connectivity fault management linktrace path database show oam ethernet connectivity-fault-management
information. linktrace path-database on page 192
Display OAM connectivity fault management maintenance association show oam ethernet connectivity-fault-management
end point (MEP) database information. mep-database on page 188
Display OAM connectivity fault management path database information show oam ethernet connectivity-fault-management
for hosts configured with MEP. path-database on page 194
Display OAM fault management statistics for Ethernet interfaces. show oam ethernet
link-fault-management on page 175
Trace the path between two Etherent OAM end points. traceroute ethernet on page 196
For more information about monitoring and troubleshooting Ethernet interfaces, see
“Investigate Fast Ethernet and Gigabit Ethernet Interfaces” in the JUNOS Interfaces
Operations Guide.
88 ■
Chapter 4: Ethernet Interface Operational Mode Commands
Options (interface-name | all)—Clear MAC database statistics for the specified physical or logical
gigabit or 10-Gigabit Ethernet interface. Specify all to clear the MAC database
statistics for all interfaces.
Options (interface-set-name | all)—Clear queue statistics for the specified gigabit or 10-Gigabit
Ethernet interface set. Specify all to clear queue statistics for all interface sets.
clear oam ethernet user@host> clear oam ethernet connectivity-fault-management linktrace path-database
connectivity-fault- maintenance-domain md1 maintenance-association ma3 00058573e483
management linktrace This command produces no output.
path-database
Options none—Clear OAM link fault management state information and restart the link
discovery process on all Ethernet interfaces.
clear oam ethernet user@host> clear oam ethernet link-fault-management state ge-0/3/3
link-fault-management Cleared link-fault-management state for interface ge-0/3/3
state
Options none—Clear OAM link fault management statistics from all Ethernet interfaces.
Options aenumber—Display standard information about the specified aggregated Fast Ethernet
or Gigabit Ethernet interface.
Physical Interface
Physical interface Name of the physical interface and state of the interface. All levels
Enabled State of the physical interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Index number of the physical interface, which reflects its initialization sequence. All levels
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
MTU Maximum transmission unit size on the physical interface. All levels
Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback: All levels
Local or Remote.
Minimum links Number of child links that must be operational for the aggregate interface to All levels
needed be operational.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hours:minutes:seconds timezone
(hours:minutes:seconds ago). For example, Last flapped: 2002-04-26 10:52:40
PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface
■ Output packets—Number of packets transmitted on the interface.
Output errors Output errors on the interface. The following paragraphs explain the counters detail extensive
whose meaning might not be obvious:
■ Carrier transitions —Number of times the interface has gone from down
to up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on the detail extensive
statistics physical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface (which reflects its initialization sequence). detail extensive none
SNMP ifIndex SNMP interface index number of the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Statistics Information about the number of packets, packets per second, number of detail extensive none
bytes, and bytes per second on this aggregate interface.
■ Bundle—Information about input and output bundle rates.
■ Link—(detail and extensive only) Information about specific links in the
aggregate, including link state and input and output rates.
■ Marker Statistics—(detail and extensive only) Information about 802.3ad
marker protocol statistics on the specified links.
■ Marker Rx—Number of valid marker PDUs received on this
aggregation port.
■ Resp Tx—Number of marker response PDUs transmitted on this
aggregation port.
■ Unknown Rx—Number of frames received that either carry the slow
protocols Ethernet type value (43B.4) but contain an unknown
protocol data unit (PDU), or are addressed to the slow protocols group
MAC address (43B.3) but do not carry the slow protocols Ethernet
type.
■ Illegal Rx—Number of frames received that carry the slow protocols
Ethernet type value (43B.4) but contain a badly formed PDU or an
illegal value of protocol subtype (43B.4).
protocol-family Protocol family configured on the logical interface. Possible values are described brief
in “Protocol Field” on page 83.
Protocol Protocol family configured on the logical interface. Possible values are described detail extensive none
in “Protocol Field” on page 83.
MTU Maximum transmission unit size on the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about protocol family flags. Possible values are described in “Family detail extensive none
Flags” on page 80.
Addresses, Flags Information about address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface ae0.0 (Index 72) (SNMP ifIndex 60) (Generation 18)
Flags: SNMP-Traps 16384 Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 0 0 0 0
Output: 0 0 0 0
Link:
fe-0/1/0.0
Input : 0 0 0 0
Output: 0 0 0 0
fe-0/1/2.0
Input : 0 0 0 0
Output: 0 0 0 0
fe-0/1/3.0
Input : 0 0 0 0
Output: 0 0 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
fe-0/1/0.0 0 0 0 0
fe-0/1/2.0 0 0 0 0
fe-0/1/3.0 0 0 0 0
Protocol inet, MTU: 1500, Generation: 37, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.100.1/24, Local: 10.100.1.2, Broadcast: 10.100.1.255,
Generation: 49
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface ae0.0 (Index 72) (SNMP ifIndex 60) (Generation 18)
Flags: SNMP-Traps 16384 Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 1 0 60 0
Output: 0 0 0 0
Link:
fe-0/1/0.0
Input : 0 0 0 0
Output: 0 0 0 0
fe-0/1/2.0
Input : 0 0 0 0
Output: 0 0 0 0
fe-0/1/3.0
Input : 1 0 60 0
Output: 0 0 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
fe-0/1/0.0 0 0 0 0
fe-0/1/2.0 0 0 0 0
fe-0/1/3.0 0 0 0 0
Protocol inet, MTU: 1500, Generation: 37, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.100.1/24, Local: 10.100.1.2, Broadcast: 10.100.1.255,
Generation: 49
0 best-effort 0 859777 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
0 best-effort 0 1897615 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 662505 0
Logical interface ae0.451 (Index 69) (SNMP ifIndex 167) (Generation 601)
Flags: SNMP-Traps VLAN-Tag [ 0x8100.451 ] Encapsulation: VLAN-VPLS
Statistics Packets pps Bytes bps
Bundle:
Input : 289 0 25685 376
Output: 1698 4 130375 3096
Link:
ge-1/2/0.451
Input : 289 0 25685 376
Output: 0 0 0 0
ge-1/2/1.451
Input : 0 0 0 0
Output: 1698 4 130375 3096
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-1/2/0.451 0 0 0 0
ge-1/2/1.451 0 0 0 0
Protocol vpls, MTU: 1518, Generation: 849, Route table: 3
Flags: Is-Primary
Logical interface ae0.452 (Index 70) (SNMP ifIndex 170) (Generation 602)
Flags: SNMP-Traps VLAN-Tag [ 0x8100.452 ] Encapsulation: VLAN-VPLS
Statistics Packets pps Bytes bps
Bundle:
Input : 293 1 26003 1072
Output: 1694 3 130057 2400
Link:
ge-1/2/0.452
Input : 293 1 26003 1072
Output: 1694 3 130057 2400
ge-1/2/1.452
Input : 0 0 0 0
Output: 0 0 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-1/2/0.452 0 0 0 0
ge-1/2/1.452 0 0 0 0
Protocol vpls, MTU: 1518, Generation: 850, Route table: 3
Flags: None
...
Options interface-type—On M-series and T-series routing platforms, the interface type is
fe-fpc/pic/port. On the J-series routing platform, the interface type is fe-pim/0/port.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Index number of the physical interface, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
MTU Maximum transmission unit size on the physical interface. All levels
Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback: All levels
Local or Remote.
LAN-PHY mode 10-Gigabit Ethernet interface operating in Local Area Network Physical Layer All levels
Device (LAN PHY) mode. LAN PHY allows 10-Gigabit Ethernet wide area links
to use existing Ethernet applications.
WAN-PHY mode 10-Gigabit Ethernet interface operating in Wide Area Network Physical Layer All levels
Device (WAN PHY) mode. WAN PHY allows 10-Gigabit Ethernet wide area links
to use fiber-optic cables and other devices intended for SONET/SDH.
Unidirectional Unidirectional link mode status for 10-Gigabit Ethernet interface: Enabled or All levels
Disabled for parent interface; Rx-only or Tx-only for child interfaces.
Auto-negotiation (Gigabit Ethernet interfaces) Autonegotiation status: Enabled or Disabled. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Wavelength (10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM] interfaces) All levels
Displays the configured wavelength, in nanometers (nm).
Frequency (10-Gigabit Ethernet DWDM interfaces only) Displays the frequency associated All levels
with the configured wavelength, in terahertz (THz).
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Gigabit Ethernet and 10-Gigabit Ethernet IQ PICs count the overhead and CRC
bytes.
For Gigabit Ethernet IQ PICs, the input byte counts vary by interface type. For
more information, see Table 29 on page 127.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded. L3
incomplete errors can be ignored by configuring the ignore-l3-incompletes
statement.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ FIFO errors—Number of FIFO errors in the receive direction that are
reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is
probably malfunctioning.
■ Resource errors—Sum of transmit drops.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC or PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC
supports only full-duplex operation, so for Gigabit Ethernet PICs, this
number should always remain 0. If it is nonzero, there is a software bug.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ FIFO errors—Number of FIFO errors in the send direction as reported by
the ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
(Egress)
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Ingress queues Total number of ingress queues supported on the specified interface. Displayed extensive
on IQ2 interfaces.
Queue counters CoS queue number and its associated user-configured forwarding class name. extensive
(Ingress) Displayed on IQ2 interfaces.
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Active alarms and Ethernet-specific defects that can prevent the interface from passing packets. detail extensive none
Active defects When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
These fields can contain the value None or Link.
■ None—There are no active defects or alarms.
■ Link—Interface has lost its link state, which usually means that the cable
is unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
PCS statistics (10-Gigabit Ethernet interfaces) Displays Physical Coding Sublayer (PCS) fault detail extensive
conditions from the WAN PHY or the LAN PHY device.
■ Bit errors—High bit error rate. Indicates the number of bit errors when
the PCS receiver is operating in normal mode.
■ Errored blocks—Loss of block lock. The number of errored blocks when
PCS receiver is operating in normal mode.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
MAC statistics Receive and Transmit statistics reported by the PIC's MAC subsystem, including extensive
the following:
■ Total octets and total packets—Total number of octets and packets. For
Gigabit Ethernet IQ PICs, the received octets count varies by interface
type. For more information, see Table 29 on page 127.
■ Unicast packets, Broadcast packets, and Multicast packets—Number of
unicast, broadcast, and multicast packets.
■ CRC/Align errors—Total number of packets received that had a length
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, and had either a bad FCS with an integral number of
octets (FCS Error) or a bad FCS with a nonintegral number of octets
(Alignment Error).
■ FIFO error—Number of FIFO errors that are reported by the ASIC on the
PIC. If this value is ever nonzero, the PIC is probably malfunctioning.
■ MAC control frames—Number of MAC control frames.
■ MAC pause frames—Number of MAC control frames with pause operational
code.
■ Oversized frames—Number of frames that exceed 1518 octets.
■ Jabber frames—Number of frames that were longer than 1518 octets
(excluding framing bits, but including FCS octets), and had either an FCS
error or an alignment error. This definition of jabber is different from the
definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4
(10BASE2). These documents define jabber as the condition in which any
packet exceeds 20 ms. The allowed range to detect jabber is from 20 ms
to 150 ms.
■ Fragment frames—Total number of packets that were less than 64 octets
in length (excluding framing bits, but including FCS octets), and had either
an FCS error or an alignment error. Fragment frames normally increment
because both runts (which are normal occurrences caused by collisions)
and noise hits are counted.
■ VLAN tagged frames—Number of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is
tagged or not.
■ Code violations—Number of times an event caused the PHY to indicate
“Data reception error” or “invalid data symbol error.”
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Filter statistics Receive and Transmit statistics reported by the PIC's MAC address filter extensive
subsystem. The filtering is done by the content-addressable memory (CAM)
on the PIC. The filter examines a packet's source and destination MAC addresses
to determine whether the packet should enter the system or be rejected.
■ Input packet count—Number of packets received from the MAC hardware
that the filter processed.
■ Input packet rejects—Number of packets that the filter rejected because
of either the source MAC address or the destination MAC address.
■ Input DA rejects—Number of packets that the filter rejected because the
destination MAC address of the packet is not on the accept list. It is normal
for this value to increment. When it increments very quickly and no traffic
is entering the router from the far-end system, either there is a bad ARP
entry on the far-end system, or multicast routing is not on and the far-end
system is sending many multicast packets to the local router (which the
router is rejecting).
■ Input SA rejects—Number of packets that the filter rejected because the
source MAC address of the packet is not on the accept list. The value in
this field should increment only if source MAC address filtering has been
enabled. If filtering is enabled, if the value increments quickly, and if the
system is not receiving traffic that it should from the far-end system, it
means that the user-configured source MAC addresses for this interface
are incorrect.
■ Output packet count—Number of packets that the filter has given to the
MAC hardware.
■ Output packet pad count—Number of packets the filter padded to the
minimum Ethernet size (60 bytes) before giving the packet to the MAC
hardware. Usually, padding is done only on small ARP packets, but some
very small IP packets can also require padding. If this value increments
rapidly, either the system is trying to find an ARP entry for a far-end
system that does not exist or it is misconfigured.
■ Output packet error count—Number of packets with an indicated error that
the filter was given to transmit. These packets are usually aged packets
or are the result of a bandwidth problem on the FPC hardware. On a
normal system, the value of this field should not increment.
■ CAM destination filters, CAM source filters—Number of entries in the CAM
dedicated to destination and source MAC address filters. There can only
be up to 64 source entries. If source filtering is disabled, which is the
default, the values for these fields should be 0.
PMA PHY (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information: extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. Any state other than OK indicates a problem.
Subfields are:
■ PHY Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
WIS section (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information: extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. Any state other than OK indicates a problem.
Subfields are:
■ BIP-B1—Bit interleaved parity for SONET section overhead
■ SEF—Severely errored framing
■ LOL—Loss of light
■ LOF—Loss of frame
■ ES-S—Errored seconds (section)
■ SES-S—Severely errored seconds (section)
■ SEFS-S—Severely errored framing seconds (section)
WIS line (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects, extensive
plus counts of specific SONET errors with detailed information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B2—Bit interleaved parity for SONET line overhead
■ REI-L—Remote error indication (near-end line)
■ RDI-L—Remote defect indication (near-end line)
■ AIS-L—Alarm indication signal (near-end line)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ ES-L—Errored seconds (near-end line)
■ SES-L—Severely errored seconds (near-end line)
■ UAS-L—Unavailable seconds (near-end line)
■ ES-LFE—Errored seconds (far-end line)
■ SES-LFE—Severely errored seconds (far-end line)
■ UAS-LFE—Unavailable seconds (far-end line)
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
WIS path (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects, extensive
plus counts of specific SONET errors with detailed information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. Any state other than OK indicates a problem.
Subfields are:
■ BIP-B3—Bit interleaved parity for SONET section overhead
■ REI-P—Remote error indication
■ LOP-P—Loss of pointer (path)
■ AIS-P—Path alarm indication signal
■ RDI-P—Path remote defect indication
■ UNEQ-P—Path unequipped
■ PLM-P—Path payload label mismatch
■ ES-P—Errored seconds (near-end STS path)
■ SES-P—Severely errored seconds (near-end STS path)
■ UAS-P—Unavailable seconds (near-end STS path)
■ SES-PFE—Severely errored seconds (far-end STS path)
■ UAS-PFE—Unavailable seconds (far-end STS path)
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Received path (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET/SDH interfaces allow extensive
trace, Transmitted path trace bytes to be sent inband across the SONET/SDH link. Juniper Networks
path trace and other router manufacturers use these bytes to help diagnose
misconfigurations and network errors by setting the transmitted path trace
message so that it contains the system hostname and name of the physical
interface. The received path trace value is the message received from the router
at the other end of the fiber. The transmitted path trace value is the message
that this router transmits.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
VLAN-Tag Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN brief detail extensive
tag or for both the outer and inner (In) VLAN tags. none
■ push—An outer VLAN tag is pushed in front of the existing VLAN tag.
■ pop—The outer VLAN tag of the incoming frame is removed.
■ swap—The outer VLAN tag of the incoming frame is overwritten with the
user specified VLAN tag information.
■ push—An outer VLAN tag is pushed in front of the existing VLAN tag.
■ push-push—Two VLAN tags are pushed in from the incoming frame.
■ swap-push—The outer VLAN tag of the incoming frame is replaced by a
user-specified VLAN tag value. A user-specified outer VLAN tag is pushed
in front. The outer tag becomes an inner tag in the final frame.
■ swap-swap—Both the inner and the outer VLAN tags of the incoming frame
are replaced by the user specified VLAN tag value.
■ pop-swap—The outer VLAN tag of the incoming frame is removed, and
the inner VLAN tag of the incoming frame is replaced by the user-specified
VLAN tag value. The inner tag becomes the outer tag in the final frame.
■ pop-pop—Both the outer and inner VLAN tags of the incoming frame are
removed.
Protocol Protocol family. Possible values are described in “Protocol Field” on page 83. detail extensive none
MTU Maximum transmission unit size on the logical interface. detail extensive none
Traffic statistics Number and rate of bytes and packets received and transmitted on the specified detail extensive
interface set.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.set
■ Input packets, Output packets—Number of packets received and transmitted
on the interface set.
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on the extensive
statistics logical interface if IPv6 statistics tracking is enabled.
Local statistics Number and rate of bytes and packets destined to the router. extensive
Transit statistics Number and rate of bytes and packets transiting the switch. extensive
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Route table in which the logical interface address is located. For example, 0 detail extensive none
refers to the routing table inet.0.
Flags Information about protocol family flags. Possible values are described in “Family detail extensive
Flags” on page 80.
Donor interface (Unnumbered Ethernet) Interface from which an unnumbered Ethernet interface detail extensive none
borrows an IPv4 address.
Table 28: Fast Ethernet and Gigabit Ethernet show interfaces Output Fields (continued)
Preferred source (Unnumbered Ethernet) Secondary IPv4 address of the donor loopback interface detail extensive none
address that acts as the preferred source address for the unnumbered Ethernet interface.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Flags Information about address flag (possible values are described in “Addresses, detail extensive none
Flags” on page 79).
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
FIFO errors 0 0
MAC control frames 0 0
MAC pause frames 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
VLAN tagged frames 0
Code violations 0
Filter statistics:
Input packet count 0
Input packet rejects 0
Input DA rejects 0
Input SA rejects 0
Output packet count 1
Output packet pad count 0
Output packet error count 0
CAM destination filters: 1, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link partner: Full-duplex, Flow control: None, Remote fault: Ok
Local resolution:
Packet Forwarding Engine configuration:
Destination slot: 0
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 950000000 95 0 low none
3 network-control 5 50000000 5 0 low none
Logical interface fe-0/0/0.0 (Index 66) (SNMP ifIndex 198) (Generation 67)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 105, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255,
Generation: 136
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface ge-3/0/2.0 (Index 72) (SNMP ifIndex 69) (Generation 140)
Flags: SNMP-Traps 0x4000
VLAN-Tag [0x8100.512 0x8100.513 ] In(pop-swap 0x8100.530)
Out(swap-push 0x8100.512 0x8100.513)
Encapsulation: VLAN-CCC
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol ccc, MTU: 1522, Generation: 149, Route table: 0
Flags: Is-Primary
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface ge-7/1/3.0 (Index 70) (SNMP ifIndex 85) (Generation 150)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes : 812400
Output bytes : 1349206
Input packets: 9429
Output packets: 9449
For Gigabit Ethernet IQ PICs, traffic and MAC statistics output varies. Table 29 on page
127 describes the traffic and MAC statistics for two sample interfaces, each of which
is sending traffic in packets of 500 bytes (including 478 bytes for the Layer 3 packet,
18 bytes for the Layer 2 VLAN traffic header, and 4 bytes for cyclic redundancy check
[CRC] information). In Table 29 on page 127, the ge-0/3/0 interface is the inbound
physical interface, and the ge-0/0/0 interface is the outbound physical interface. On
both interfaces, traffic is carried on logical unit .50 (VLAN 50).
Table 29: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type
Interface Type Sample Command Byte and Octet Counts Include Comments
Inbound physical show interfaces Traffic statistics: The additional 4 bytes are
interface ge-0/3/0 extensive for the CRC.
Input bytes: 496 bytes per packet, representing
the Layer 2 packet
MAC statistics:
Outbound physical show interfaces Traffic statistics: For input bytes, the
interface ge-0/0/0 extensive additional 12 bytes
Input bytes: 490 bytes per packet, representing includes 6 bytes for the
the Layer 3 packet + 12 bytes destination MAC address
+ 4 bytes for VLAN + 2
MAC statistics: bytes for the Ethernet type.
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface xe-5/0/0.0 (Index 71) (SNMP ifIndex 95) (Generation 195)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ] Encapsulation: ENET2
Traffic statistics:
Input bytes : 0
Output bytes : 46
Input packets: 0
Output packets: 1
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 46
Input packets: 0
Output packets: 1
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Filter statistics:
Input packet count 0
Input packet rejects 0
Input DA rejects 0
Input SA rejects 0
Output packet count 0
Output packet pad count 0
Output packet error count 0
CAM destination filters: 0, CAM source filters: 0
PMA PHY: Seconds Count State
PLL lock 0 0 OK
PHY light 63159 1 Light Missing
WIS section:
BIP-B1 0 0
SEF 434430 434438 Defect Active
LOS 434430 1 Defect Active
LOF 434430 1 Defect Active
ES-S 434430
SES-S 434430
SEFS-S 434430
WIS line:
BIP-B2 0 0
REI-L 0 0
RDI-L 0 0 OK
AIS-L 434430 1 Defect Active
BERR-SF 0 0 OK
BERR-SD 0 0 OK
ES-L 434430
SES-L 434430
UAS-L 434420
ES-LFE 0
SES-LFE 0
UAS-LFE 0
WIS path:
BIP-B3 0 0
REI-P 0 0
LOP-P 0 0 OK
AIS-P 434430 1 Defect Active
RDI-P 0 0 OK
UNEQ-P 0 0 OK
PLM-P 0 0 OK
ES-P 434430
SES-P 434430
UAS-P 434420
ES-PFE 0
SES-PFE 0
UAS-PFE 0
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace: orissa so-1/0/0
6f 72 69 73 73 61 20 73 6f 2d 31 2f 30 2f 30 00 orissa so-1/0/0.
Packet Forwarding Engine configuration:
Destination slot: 1
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % bytes
0 best-effort 95 950000000 95 0 low none
3 network-control 5 50000000 5 0 low none
Mode, Unidirectional Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Mode) Unidirectional: Enabled,
Loopback: None, Source filtering: Disabled, Flow control: Enabled
Device flags : Present Running
...
...
Filter statistics:
Output packet count 328810554250
Output packet pad count 0
Output packet error count 0
...
Logical interface xe-7/0/0-tx.0 (Index 73) (SNMP ifIndex 138) (Generation 139)
...
Filter statistics:
Input packet count 328775015056
Input packet rejects 1
Input DA rejects 0
...
Logical interface xe-7/0/0-rx.0 (Index 72) (SNMP ifIndex 120) (Generation 138)
Output bytes : 0
Input packets: 0
Output packets: 0
Protocol inet, MTU: 1500, Generation: 145, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.1.1/24, Local: 192.1.1.1, Broadcast: 192.1.1.255,
Generation: 139
Protocol multiservice, MTU: Unlimited, Generation: 146, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__
Table 30 on page 135 describes the information for the show interfaces interface-set
command.
Physical Interface
Interface set Name of the interface set or sets. All levels
Traffic statistics Number and rate of bytes and packets received and transmitted on the specified detail
interface set.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface set
■ Input packets, Output packets—Number of packets received and transmitted
on the interface set.
Egress queues Total number of egress queues supported on the specified interface set. detail
supported
Egress queues in Total number of egress queues used on the specified interface set. detail
use
Queue counters Queued packets, Transmitted packets, and Dropped packets statistics for the four detail
forwarding classes.
Table 31 on page 137 describes the information for the show interfaces interface-set
queue command.
Physical Interface
Table 31: Ethernet show interfaces interface-set queue Output Fields (continued)
Interface set index Index number of the interface set. All levels
Forwarding classes Total number of forwarding classes supported on the specified interface set. All levels
supported
Forwarding classes Total number of forwarding classes used on the specified interface set. All levels
in use
Egress queues Total number of egress queues supported on the specified interface set. All levels
supported
Egress queues in Total number of egress queues used on the specified interface set. All levels
use
Ingress queues Total number of ingress queues supported on the specified interface set.
supported
Ingress queues in Total number of ingress queues used on the specified interface set.
use
Queue Egress or ingress queue number for the statistics being displayed. All levels
Forwarding classes Forwarding class name for the statistics being displayed. All levels
Queued Packet and Byte statistics for the specified queue. All levels
■ Packets—Number of packets queued and input rate in packets per second.
■ Bytes—Number of bytes queued and input rate in bytes per second.
Transmitted Packet and Byte statistics for the specified forwarding class. All levels
■ Packets—Number of packets transmitted and transmit rate in packets per
second.
■ Bytes—Number of bytes transmitted and transmit rate in bytes per second.
■ Tail-dropped packets—Number of packets tail dropped.
■ RED-dropped packets—Number of RED-dropped packets for the low,
medium-low, medium-high, and high loss priorities.
■ RED-dropped bytes—Number of RED-dropped bytes for the low, medium-low,
medium-high, and high loss priorities.
Transmitted:
Packets : 1077474 1 pps
Bytes : 73268340 688 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 2921008 0 pps
Low : 2921008 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 198628544 0 bps
Low : 198628544 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
...
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
RED-dropped bytes : 0 0 bps
Forwarding classes: 16 supported, 4 in use
Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets : 5417304 13797 pps
Bytes : 368429508 7506096 bps
Transmitted:
Packets : 5014996 12769 pps
Bytes : 341019728 6946560 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 402189 1028 pps
Low : 402189 1028 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 27348852 559536 bps
Low : 27348852 559536 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 5770534 3963 pps
Bytes : 396943252 2156144 bps
Transmitted:
Packets : 3945152 1457 pps
Bytes : 268270336 792608 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 1815141 2506 pps
Low : 1815141 2506 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 123429524 1363536 bps
Low : 123429524 1363536 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queued:
Packets : 5350989 3904 pps
Bytes : 368412924 2124048 bps
Transmitted:
Packets : 3790469 1465 pps
Bytes : 257751892 796960 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 1550282 2439 pps
Low : 1550282 2439 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 105419176 1327088 bps
Low : 105419176 1327088 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
Low : 0 0 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 0 0 bps
Low : 0 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 108241516 0 bps
Low : 108241516 0 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
Additional Information XENPAK Multisource Agreement (MSA) optics, 300-pin MSA optics, bidirectional
small form-factor pluggable transceiver (SFP) optics, SFP optics, 10-gigabit small
form-factor pluggable transceiver (XFP) optics, and Optical Transport Network (OTN)
optics are supported. The 300-pin MSA tool kit polls the PIC and the XENPAK driver
polls the XENPAK transceiver in 1-second intervals for diagnostics data, alarms, and
warnings and stores them into memory. The alarms will not cause the links to go
down or the LEDs to change color, nor generate SNMP traps. Changes in alarm and
warning status will generate system log messages.
Thresholds that trigger a high alarm, low alarm, high warning, or low warning are
set by the transponder vendors. Generally, a high alarm or low alarm indicates that
the optics module is not operating properly. This information can be used to diagnose
why a PIC is not working.
NOTE: Some 10-Gigabit Ethernet XENPAK transceivers do not support all optical
diagnostics. If the diagnostics are not supported, you will see N/A in the following
fields in the output: Laser bias current, Laser output power, Laser rx power, and Module
temperature.
Table 32: 10-Gigabit Ethernet 300-Pin MSA Optics show interfaces diagnostics optics Output Fields
Table 32: 10-Gigabit Ethernet 300-Pin MSA Optics show interfaces diagnostics optics Output Fields (continued)
Laser bias current Magnitude of the laser bias power setting current, in milliamperes. The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm). This is a software
equivalent to the LsPOWMON pin in hardware.
Receiver signal average Average received optical power, in mW and dBm. This indicator is a software equivalent to the
optical power RxPOWMON pin in hardware. Average optical power is vendor-specific. For example:
Modulator temperature (Opnext 300-pin MSA transponders only) Modulator temperature alarm: On or Off.
alarm
Tx multiplexer FIFO error Transmit multiplexer first in, first out (FIFO) error alarm: On or Off.
alarm
Tx loss of PLL lock Transmit loss of phase-locked loop (PLL) lock alarm: On or Off.
alarm
Rx loss of AC power (Opnext 300-pin MSA transponders only) Receive loss of AC power alarm: On or Off.
alarm
Rx loss of PLL lock Receive loss of phase-locked loop (PLL) lock alarm: On or Off.
alarm
Table 33 on page 146 lists the output fields for the show interfaces diagnostics optics
command when the router is operating with bidirectional SFP optics. Output fields
are listed in the approximate order in which they appear.
Table 33: 10-Gigabit Ethernet Bidirectional SFP Optics show interfaces diagnostics optics Output Fields
Table 33: 10-Gigabit Ethernet Bidirectional SFP Optics show interfaces diagnostics optics Output
Fields (continued)
Laser bias current Magnitude of the laser bias power setting current, in milliamperes. The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm).
Module temperature Temperature of the XFP optics module, in Celsius and Fahrenheit.
Laser bias current high Laser bias power setting high alarm. Displays on or off.
alarm
Laser bias current low Laser bias power setting low alarm. Displays on or off.
alarm
Laser bias current high Laser bias power setting high warning. Displays on or off.
warning
Laser bias current low Laser bias power setting low warning. Displays on or off.
warning
Laser output power high Laser output power high alarm. Displays on or off.
alarm
Laser output power low Laser output power low alarm. Displays on or off.
alarm
Laser output power high Laser output power high warning. Displays on or off.
warning
Laser output power low Laser output power low warning. Displays on or off.
warning
Table 33: 10-Gigabit Ethernet Bidirectional SFP Optics show interfaces diagnostics optics Output
Fields (continued)
Laser rx power high Receive laser power high alarm. Displays on or off.
alarm
Laser rx power low Receive laser power low alarm. Displays on or off.
alarm
Laser rx power high Receive laser power high warning. Displays on or off.
warning
Laser rx power low Receive laser power low warning. Displays on or off.
warning
Laser bias current high Vendor-specified threshold for the laser bias current high alarm: 70.000 mA.
alarm threshold
Laser bias current low Vendor-specified threshold for the laser bias current low alarm: 0.0002 mA.
alarm threshold
Laser bias current high Vendor-specified threshold for the laser bias current high warning: 65.000 mA.
warning threshold
Laser bias current low Vendor-specified threshold for the laser bias current low warning: 0.0002 mA.
warning threshold
Laser output power high Vendor-specified threshold for the laser output power high alarm: 1.0000 mW or 0.00 dBm.
alarm threshold
Laser output power low Vendor-specified threshold for the laser output power low alarm: 0.0560 mW or -12.52 dBm.
alarm threshold
Laser output power high Vendor-specified threshold for the laser output power high warning: 0.6300 mW or -2.01 dBm.
warning threshold
Laser output power low Vendor-specified threshold for the laser output power low warning: 0.0890 mW or -10.51 dBm.
warning threshold
Module temperature Vendor-specified threshold for the module temperature high alarm: 100° C or 212° F.
high alarm threshold
Module temperature low Vendor-specified threshold for the module temperature low alarm: -50° C or -58° F.
alarm threshold
Module temperature Vendor-specified threshold for the module temperature high warning: 95 ° C or 203 ° F.
high warning threshold
Module temperature low Vendor-specified threshold for the module temperature low warning: -48° C or -54° F.
warning threshold
Table 33: 10-Gigabit Ethernet Bidirectional SFP Optics show interfaces diagnostics optics Output
Fields (continued)
Laser rx power high Vendor-specified threshold for the laser Rx power high alarm: 1.9953 mW or 3.00 dBm.
alarm threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low alarm: 0.0001 mW or -40.00 dBm.
alarm threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high warning: 1.0000 mW or 0.00 dBm.
warning threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low warning: 0.0010 mW or -30.00 dBm.
warning threshold
Table 34 on page 149 lists the output fields for the show interfaces diagnostics optics
command when the router is operating with SFP MSA optics. Output fields are listed
in the approximate order in which they appear.
Table 34: 10-Gigabit Ethernet SFP MSA Optics show interfaces diagnostics Output Fields
Laser bias current high Laser bias current high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser bias current low Laser bias current low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Table 34: 10-Gigabit Ethernet SFP MSA Optics show interfaces diagnostics Output Fields (continued)
Laser output power high Laser output power high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser output power low Laser output power low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Module temp high alarm Module temperature high alarm: On or Off. Alarm ranges are vendor-specific.
Module temp low alarm Module temperature low alarm: On or Off. Alarm ranges are vendor-specific.
Laser rx power high Laser receive power high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser rx power low Laser receive power low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser bias current high Laser bias current high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser bias current low Laser bias current low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser output power high Laser output power high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser output power low Laser output power low warning: On or Off. Warning ranges are vendor-specific.
warning
Module temperature Module temperature high warning: On or Off. Warning ranges are vendor-specific.
high warning
Module temperature low Module temperature low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser rx power high Laser receive power high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser rx power low Laser receive power low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser bias current high Laser bias current high alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Laser bias current low Laser bias current low alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Laser bias current high Laser bias current high warning threshold. Warning ranges are vendor-specific.
warning threshold
Laser bias current low Laser bias current low warning threshold. Warning ranges are vendor-specific.
warning threshold
Laser output power high Laser output power high alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Table 34: 10-Gigabit Ethernet SFP MSA Optics show interfaces diagnostics Output Fields (continued)
Laser output power low Laser output power low alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Laser output power high Laser output power high warning threshold. Warning ranges are vendor-specific.
warning threshold
Laser output power low Laser output power low warning threshold. Warning ranges are vendor-specific.
warning threshold
Module temperature Module temperature high alarm threshold. Alarm threshold ranges are vendor-specific.
high alarm threshold
Module temperature low Module temperature low alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Module temperature Module temperature high warning threshold. Warning ranges are vendor-specific.
high warning threshold
Module temperature low Module temperature low warning threshold. Warning ranges are vendor-specific.
warning threshold
Module voltage high Module voltage high alarm threshold. Alarm ranges are vendor-specific.
alarm threshold
Module voltage low Module voltage low alarm threshold. Alarm ranges are vendor-specific.
alarm threshold
Module voltage high Module voltage high warning threshold. Warning ranges are vendor-specific.
warning threshold
Module voltage low Module voltage high warning threshold. Warning ranges are vendor-specific.
warning threshold
Laser rx power high Laser receive power high alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Laser rx power low Laser receive power low alarm threshold. Alarm threshold ranges are vendor-specific.
alarm threshold
Laser rx power high Laser receive power high warning threshold. Warning threshold ranges are vendor-specific.
warning threshold
Laser rx power high low Laser receive power high warning threshold. Warning threshold ranges are vendor-specific.
threshold
Table 35 on page 152 lists the output fields for the show interfaces diagnostics optics
command when the router is operating with XFP optics. Output fields are listed in
the approximate order in which they appear.
Table 35: 10-Gigabit Ethernet XFP Optics show interfaces diagnostics optics Output Fields
Laser bias current Magnitude of the laser bias power setting current, in milliamperes. The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm). This is a software
equivalent to the LsPOWMON pin in hardware.
Module temperature Temperature of the XFP optics module, in Celsius and Fahrenheit.
Laser bias current high Laser bias power setting high alarm. Displays on or off.
alarm
Laser bias current low Laser bias power setting low alarm. Displays on or off.
alarm
Laser bias current high Laser bias power setting high warning. Displays on or off.
warning
Laser bias current low Laser bias power setting low warning. Displays on or off.
warning
Laser output power high Laser output power high alarm. Displays on or off.
alarm
Laser output power low Laser output power low alarm. Displays on or off.
alarm
Laser output power high Laser output power high warning. Displays on or off.
warning
Laser output power low Laser output power low warning. Displays on or off.
warning
Laser rx power high Receive laser power high alarm. Displays on or off.
alarm
Laser rx power low Receive laser power low alarm. Displays on or off.
alarm
Table 35: 10-Gigabit Ethernet XFP Optics show interfaces diagnostics optics Output Fields (continued)
Laser rx power high Receive laser power high warning. Displays on or off.
warning
Laser rx power low Receive laser power low warning. Displays on or off.
warning
Module not ready alarm Module not ready alarm. When on, indicates the module has an operational fault. Displays on or off.
Module power down Module power down alarm. When on, module is in a limited power mode, low for normal operation.
alarm Displays on or off.
Tx data not ready alarm Any condition leading to invalid data on the transmit path. Displays on or off.
Tx not ready alarm Any condition leading to invalid data on the transmit path. Displays on or off.
Tx CDR loss of lock Transmit clock and data recovery (CDR) loss of lock. Loss of lock on the transmit side of the CDR.
alarm Displays on or off.
Rx not ready alarm Any condition leading to invalid data on the receive path. Displays on or off.
Rx loss of signal alarm Receive Loss of Signal alarm. When on, indicates insufficient optical input power to the module.
Displays on or off.
Rx CDR loss of lock Receive CDR loss of lock. Loss of lock on the receive side of the CDR. Displays on or off.
alarm
Laser bias current high Vendor-specified threshold for the laser bias current high alarm: 130.000 mA.
alarm threshold
Laser bias current low Vendor-specified threshold for the laser bias current low alarm: 10.000 mA.
alarm threshold
Laser bias current high Vendor-specified threshold for the laser bias current high warning: 120.000 mA.
warning threshold
Laser bias current low Vendor-specified threshold for the laser bias current low warning: 12.000 mA.
warning threshold
Laser output power high Vendor-specified threshold for the laser output power high alarm: 0.8910 mW or -0.50 dBm.
alarm threshold
Laser output power low Vendor-specified threshold for the laser output power low alarm: 0.2230 mW or -6.52 dBm.
alarm threshold
Laser output power high Vendor-specified threshold for the laser output power high warning: 0.7940 mW or -100 dBm.
warning threshold
Laser output power low Vendor-specified threshold for the laser output power low warning: 0.2510 mW or -600 dBm.
warning threshold
Module temperature Vendor-specified threshold for the module temperature high alarm: 90° C or 194° F.
high alarm threshold
Table 35: 10-Gigabit Ethernet XFP Optics show interfaces diagnostics optics Output Fields (continued)
Module temperature low Vendor-specified threshold for the module temperature low alarm: -5° C or 23° F.
alarm threshold
Module temperature Vendor-specified threshold for the module temperature high warning: 85 ° C or 185 ° F.
high warning threshold
Module temperature low Vendor-specified threshold for the module temperature low warning: 0° C or 32° F.
warning threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high alarm: 1.2589 mW or 1.00 dBm.
alarm threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low alarm: 0.0323 mW or -14.91 dBm.
alarm threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high warning: 1.1220 mW or 0.50 dBm.
warning threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low warning: 0.0363 mW or -14.40 dBm.
warning threshold
Table 36 on page 154 lists the output fields for the show interfaces diagnostics optics
command generated from 10-Gigabit Ethernet XENPAK OTN optics.
Table 36: XENPAK OTN Optics show interfaces diagnostics optics Output Fields
Laser bias current high Laser bias current high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser bias current low Laser bias current low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser output power high Laser output power high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser output power low Laser output power low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Module temp high alarm Module temperature high alarm: On or Off. Alarm ranges are vendor-specific.
Table 36: XENPAK OTN Optics show interfaces diagnostics optics Output Fields (continued)
Module temp low alarm Module temperature low alarm: On or Off. Alarm ranges are vendor-specific.
Laser rx power high Laser receive power high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser rx power low Laser receive power low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser bias current high Laser bias current high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser bias current low Laser bias current low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser output power high Laser output power high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser output power low Laser output power low warning: On or Off. Warning ranges are vendor-specific.
warning
Module temp high Module temperature high warning: On or Off. Warning ranges are vendor-specific.
warning
Module temp low Module temperature low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser rx power high Laser receive power high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser rx power low Laser receive power low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser bias current high Vendor-specified threshold for the laser bias current high alarm: 31.000 mA.
alarm threshold
Laser bias current low Vendor-specified threshold for the laser bias current low alarm: 10.000 mA.
alarm threshold
Laser output power high Vendor-specified threshold for the laser output power high alarm: 6.000 mW or 7.78 dBm.
alarm threshold
Laser output power low Vendor-specified threshold for the laser output power low alarm: 0.100 mW or -10.00 dBm.
alarm threshold
Module temperature Vendor-specified threshold for the module temperature high alarm: 85° C or 185° F.
high alarm threshold
Module temperature low Vendor-specified threshold for the module temperature low alarm: 0° C or 32° F.
alarm threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high alarm: 1.000 mW or 0.00 dBm.
alarm threshold
Table 36: XENPAK OTN Optics show interfaces diagnostics optics Output Fields (continued)
Laser rx power low Vendor-specified threshold for the laser Rx power low alarm: 0.001 mW or -30.00 dBm.
alarm threshold
Laser bias current high Vendor-specified threshold for the laser bias current high warning: 28.000 mA.
warning threshold
Laser bias current low Vendor-specified threshold for the laser bias current low warning: 11.000 mA.
warning threshold
Laser output power high Vendor-specified threshold for the laser output power high warning: 5.000 mW or 6.99 dBm.
warning threshold
Laser output power low Vendor-specified threshold for the laser output power low warning: 0.500 mW or -3.01 dBm.
warning threshold
Module temperature Vendor-specified threshold for the module temperature high warning: 70° C or 158° F.
high warning threshold
Module temperature low Vendor-specified threshold for the module temperature low warning: 10° C or 50° F.
warning threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high warning: 0.501 mW or -3.00 dBm.
warning threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low warning: 0.001 mW or -28.86 dBm.
warning threshold
Options brief | detail | extensive | terse—(Optional) Display the specified level of output.
Additional Information Integrated routing and bridging (IRB) provides simultaneous support for Layer 2
bridging and Layer 3 IP routing on the same interface. IRB enables you to route local
packets to another routed interface or to another bridging domain that has a Layer
3 protocol configured.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the physical interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Link-level type Encapsulation being used on the physical interface. detail extensive brief
none
Clocking Reference clock source: Internal or External. Always unspecified on IRB detail extensive brief
interfaces.
Speed Speed at which the interface is running. Always unspecified on IRB interfaces. detail extensive brief
Device flags Information about the physical device. Possible values are described in “Device detail extensive brief
Flags” on page 79. none
Interface flags Information about the interface. Possible values are described in “Interface detail extensive brief
Flags” on page 80. none
Link type Physical interface link type: full duplex or half duplex. detail extensive
none
Link flags Information about the link. Possible values are described in “Link detail extensive none
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hours:minutes:seconds timezone
(hours:minutes:seconds ago). For example, Last flapped: 2002-04-26 10:52:40
PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface
■ Output packets—Number of packets transmitted on the interface.
IPv6 transit statistics Number of IPv6 transit bytes and packets received and transmitted on the detail extensive
physical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters detail extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt
threshold.
■ Giants—Number of frames received that are larger than the giant
threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters detail extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down
to up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the DPC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface (which reflects its initialization sequence). detail extensive
none
SNMP ifIndex SNMP interface index number of the logical interface. detail extensive
none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical detail extensive
Interface Flags” on page 82.
Traffic statistics Number and rate of bytes and packets received and transmitted on the logical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface
■ Output packets—Number of packets transmitted on the interface.
IPv6 transit statistics Number of IPv6 transit bytes and packets received and transmitted on the detail extensive
logical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. detail extensive
Transit statistics Statistics for traffic transiting the router. detail extensive
Protocol Protocol family configured on the logical interface. Possible values are described detail extensive
in “Protocol Field” on page 83.
MTU Maximum transmission unit size on the logical interface. detail extensive
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, detail extensive
0 refers to the routing table inet.0.
Addresses, Flags Information about address flags. Possible values are described in “Addresses, detail extensive
Flags” on page 79.
Policer The policer that is to be evaluated when packets are received or transmitted detail extensive
on the interface.
Flags Information about the logical interface. Possible values are described in “Logical detail extensive
Interface Flags” on page 82.
Logical interface irb.0 (Index 68) (SNMP ifIndex 70) (Generation 143)
Flags: Hardware-Down SNMP-Traps 0x4000 Encapsulation: ENET2
Bandwidth: 1000mbps
Routing Instance: customer_0 Bridging Domain: bd0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Options ge-fpc/pic/port—Display MAC addresses that have been learned on all logical interfaces
on a particular physical interface.
Additional Information On IQ2 PIC interfaces, the default value for maximum retention of entries in the
MAC address table has changed, for cases in which the table is not full. The new
holding time is 12 hours. The previous retention time of 3 minutes is still in effect
when the table is full.
Physical Interface
Physical interface Name of the physical interface.
Enabled State of the physical interface. Possible values are described in “Enabled Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence.
Loopback Whether loopback is enabled and the type of loopback: local or remote.
Device flags Information about the physical device. Possible values are described in “Device Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link Flags” on page 81.
Logical Interface
Logical interface Name of the logical interface.
Index Logical interface index number, which reflects its initialization sequence.
Flags Information about the logical interface (possible values are described in “Logical Interface
Flags” on page 82).
MAC address, Input MAC address and corresponding number of input frames, input bytes, output frames, and output
frames, Input bytes, bytes.
Output frames, Output
bytes
Policer Statistics (Displayed for mac-address option only) Display information about policers applied to a logical
interface-MAC pair.
■ Policer type—Type of policer that is out of spec with respect to the configuration. It can be one
or more of the following:
■ Input premium—Number of high-priority rating out-of-spec frames or bytes received.
■ Output premium—Number of high-priority rating out-of-spec frames or bytes sent.
■ Input aggregate—Total number of out-of-spec frames or bytes received.
■ Output aggregate—Total number of out-of-spec frames or bytes sent.
■ Discarded Frames—Number of discarded frames.
■ Discarded Bytes—Number of discarded bytes.
■ Exp—Expired state. Yes indicates the actor or partner is in an expired state. No indicates the
actor or partner is not in an expired state.
■ Def—Default. Yes indicates that the actor's receive machine is using the default operational
partner information, administratively configured for the partner. No indicates the operational
partner information in use has been received in an LACP PDU.
■ Dist—Distribution of outgoing frames. No indicates distribution of outgoing frames on the link
is currently disabled and is not expected to be enabled. Otherwise, the value is Yes.
■ Col—Collection of incoming frames.Yes indicates collection of incoming frames on the link is
currently enabled and is not expected to be disabled. Otherwise, the value is No.
■ Syn—Synchronization. If the value is Yes, the link is considered “in sync.” It has been allocated
to the correct link aggregation group, the group has been associated with a compatible aggregator,
and the identity of the link aggregation group is consistent with the system ID and operational
key information transmitted. If the value is No, the link is currently “out of sync,” not in the
right aggregation.
■ Aggr—Ability of aggregation port to aggregate (Yes) or to operate only as an individual link (No).
■ Timeout—LACP timeout preference. Periodic transmissions of LACP PDUs occur at either a slow
or fast transmission rate, depending upon the expressed LACP timeout preference (Long Timeout
or Short Timeout).
■ Activity—Actor or partner's port activity. Passive indicates the port's preference for not
transmitting LAC PDUs unless its partner's control value is Active. Active indicates the port's
preference to participate in the protocol regardless of the partner's control value.
Flags Information about the interface. Possible values are described in “Link All levels
Flags” on page 81.
■ Remote-Stable—Indicates remote OAM client acknowledgment of and
satisfaction with local OAM state information. False indicates that remote
DTE either has not seen or is unsatisfied with local state information.True
indicates that remote DTE has seen and is satisfied with local state
information.
■ Local-Stable—Indicates local OAM client acknowledgment of and
satisfaction with remote OAM state information. False indicates that local
DTE either has not seen or is unsatisfied with remote state information.
True indicates that local DTE has seen and is satisfied with remote state
information.
■ Remote-State-Valid—Indicates the OAM client has received remote state
information found within Local Information TLVs of received Information
OAM PDUs. False indicates that OAM client has not seen remote state
information. True indicates that the OAM client has seen remote state
information.
Remote loopback Indicates the remote loopback status. An OAM entity can put its remote peer All levels
status into loopback mode using the Loopback control OAM PDU. In loopback mode,
every frame received is transmitted back on the same port (except for OAM
PDUs, which are needed to maintain the OAM session).
Variable request The total number of variable request PDUs received. detail
Variable response The total number of variable response PDUs received. detail
Loopback control The total number of loopback control PDUs received. detail
Organization The total number of vendor organization specific PDUs received. detail
specific
Variable request The total number of variable request PDUs transmitted. detail
Variable response The total number of variable response PDUs transmitted. detail
Loopback control The total number of loopback control PDUs transmitted. detail
Organization The total number of vendor organization specific PDUs transmitted. detail
specific
Window The symbol error event window in the received PDU. detail
The protocol default value is the number of symbols that can be received in
one second on the underlying physical layer.
Threshold The number of errored symbols in the period required for the event to be detail
generated.
Errors in period The number of symbol errors in the period reported in the received event PDU. detail
Total errors The number of errored symbols that have been reported in received event detail
TLVs since the OAM sublayer was reset.
Window The duration of the window in terms of the number of 100 ms period intervals. detail
Threshold The number of detected errored frames required for the event to be generated. detail
Errors in period The number of detected errored frames in the period. detail
Total errors The number of errored frames that have been reported in received event TLVs detail
since the OAM sublayer was reset.
Errors in period The number of frame seconds errors in the period. detail
Total errors The number of frame seconds errors that have been reported in received event detail
TLVs since the OAM sublayer was reset.
Window The symbol error event window in the transmitted PDU. detail
Threshold The number of errored symbols in the period required for the event to be detail
generated.
Errors in period The number of symbol errors in the period reported in the transmitted event detail
PDU.
Total errors The number of errored symbols reported in event TLVs that have been detail
transmitted since the OAM sublayer was reset.
Window The duration of the window in terms of the number of 100 ms period intervals. detail
Threshold The number of detected errored frames required for the event to be generated. detail
Errors in period The number of detected errored frames in the period. detail
Total errors The number of errored frames that have been detected since the OAM sublayer detail
was reset.
Filter action Filter action for messages at the level. All levels
Table 41: show oam ethernet connectivity-fault-management forwarding-state Output Fields (continued)
6 Drop none
7 down Receive none
Level: 1
Filter action: Drop
Nexthop type: none
Level: 2
Filter action: Drop
Nexthop type: none
Level: 3
Filter action: Drop
Nexthop type: none
Level: 4
Filter action: Drop
Nexthop type: none
Level: 5
Filter action: Drop
Nexthop type: none
Level: 6
Filter action: Drop
Nexthop type: none
Level: 7
Direction: down
Filter action: Receive
Nexthop type: none
Level: 0
Filter action: Drop
Nexthop type: none
Level: 1
Filter action: Drop
Nexthop type: none
...
type index
0 Drop none
1 Drop none
2 Drop none
3 Drop none
4 Drop none
5 Drop none
6 Drop none
7 down Receive none
Link status Local link status. Up, down, or oam-down. All levels
Table 42: show oam ethernet connectivity-fault-management interfaces Output Fields (continued)
MEP identifier Maintenance association end point (MEP) identifier. All levels
MAC address MAC address configured for the MEP. detail extensive
MEP status Indicates the status of the Connectivity Fault Management (CFM) protocol detail extensive
running on the MEP: Running, inactive, disabled, or unsupported.
Remote MEP not Whether the remote MEP is not receiving connectivity check messages (CCMs). detail extensive
receiving CCM
Erroneous CCM Whether erroneous CCMs have been received. detail extensive
received
Cross-connect CCM Whether cross-connect CCMs have been received. detail extensive
received
RDI sent by some Whether the remote defect indication (RDI) bit is set in messages that have detail extensive
MEP been received. The absence of the RDI bit in a CCM indicates that the
transmitting MEP is receiving CCMs from all configured MEPs.
CCMs received out Number of CCMs received out of sequence. detail extensive
of sequence
Sequence number Sequence number of next LTM request to be transmitted. detail extensive
of next LTM request
Table 42: show oam ethernet connectivity-fault-management interfaces Output Fields (continued)
...
show oam ethernet user@host> show oam ethernet connectivity-fault-management interfaces detail
connectivity-fault- Interface name: ge-5/2/9.0, Interface status: Active, Link status: Up
management interfaces Maintenance domain name: md0, Format: string, Level: 5
Maintenance association name: ma1, Format: string
detail
Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
MEP identifier: 1, Direction: down, MAC address: 00:90:69:0b:4b:94
MEP status: running
Defects:
Remote MEP not receiving CCM : no
Erroneous CCM received : yes
Cross-connect CCM received : no
RDI sent by some MEP : yes
Statistics:
CCMs sent : 76
CCMs received out of sequence : 0
LTMs sent : 0
LTMs received : 0
LTRs sent : 0
LTRs received : 0
Sequence number of next LTM request : 0
Remote MEP count: 2
Identifier MAC address State Interface
2001 00:90:69:0b:7f:71 ok ge-5/2/9.0
4001 00:90:69:0b:09:c5 ok ge-5/2/9.0
show oam ethernet user@host> show oam ethernet connectivity-fault-management interfaces extensive
connectivity-fault- Interface name: ge-5/2/9.0, Interface status: Active, Link status: Up
management interfaces Maintenance domain name: md0, Format: string, Level: 5
Maintenance association name: ma1, Format: string
extensive
Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
MEP identifier: 1, Direction: down, MAC address: 00:90:69:0b:4b:94
MEP status: running
Defects:
Remote MEP not receiving CCM : no
Erroneous CCM received : yes
Cross-connect CCM received : no
RDI sent by some MEP : yes
Statistics:
CCMs sent : 76
CCMs received out of sequence : 0
LTMs sent : 0
LTMs received : 0
LTRs sent : 0
LTRs received : 0
Sequence number of next LTM request : 0
Remote MEP count: 2
Identifier MAC address State Interface
2001 00:90:69:0b:7f:71 ok ge-5/2/9.0
4001 00:90:69:0b:09:c5 ok ge-5/2/9.0
show oam ethernet user@host> show oam ethernet connectivity-fault-management interfaces level 7
connectivity-fault- Interface Link Status Level MEP Neighbours
management interfaces Identifier
ge-3/0/0.0 Up Active 7 201 0
level
xe-0/0/0.0 Up Active 7 203 1
Table 43: show oam ethernet connectivity-fault-management mep-database Output Fields (continued)
Priority Priority used for CCMs and linktrace messages transmitted by the MEP.
Remote MEP not Whether the remote MEP is not receiving CCMs.
receiving CCM
RDI sent by some MEP Whether the remote defect indication (RDI) bit is set in messages that have been received. The
absence of the RDI bit in a CCM indicates that the transmitting MEP is receiving CCMs from all
configured MEPs.
Sequence number of Sequence number of the next linktrace message request to be transmitted.
next LTM request
State (remote MEP) State of the remote MEP: idle, start, ok, or failed.
Table 43: show oam ethernet connectivity-fault-management mep-database Output Fields (continued)
Type Whether the remote MEP MAC address was learned using automatic discovery or configured.
Interface The interface of the remote MEP. A seven-digit number is appended if CFM is configured to run on
a routing instance of type VPLS.
Last flapped Date, time, and how long ago the remote MEP interface went from down to up. The format is Last
flapped: year-month-day hours:minutes:seconds timezone (hours:minutes:seconds ago). For example, Last
flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Remote defect Whether the remote defect indication (RDI) bit is set in messages that have been received/transmitted.
indication
Port status TLV The number of port status type length values (TLVs) received by the remote MEP in OAM protocol
data units.
Interface status TLV The number of interface status type length values (TLVs) received by the remote MEP in OAM protocol
data units.
Table 44: show oam ethernet connectivity-fault-management linktrace path-database Output Fields
Linktrace to MAC address of the 802.1ag node to which the linktrace message is targeted.
Interface Interface used by the local MEP to send the linktrace message (LTM).
Local Mep MEP identifier of the local MEP originating the linktrace.
TTL Number of hops remaining in the linktrace message (LTM). The time to live (TTL) is decremented at
each hop.
Source MAC address MAC address of the 802.1ag maintenance intermediate point (MIP) that is forwarding the LTM.
Table 44: show oam ethernet connectivity-fault-management linktrace path-database Output Fields (continued)
Next hop MAC address MAC address of the 802.1ag node that is the next hop in the LTM path.
Transaction Identifier A 4-byte identifier maintained by the MEP. Each LTM uses a transaction identifier. The transaction
identifier is maintained globally across all maintenance domains. Use the transaction identifier to
match an incoming linktrace responses (LTR), with a previously sent LTM.
show oam ethernet user@host> show oam ethernet connectivity-fault-management linktrace path-database
connectivity-fault- maintenance-domain MD1 maintenance-association MA1 00:01:02:03:04:05
management linktrace Linktrace to 00:01:02:03:04:05, Interface : ge-5/0/0.0
Maintenance Domain: MD1, Level: 7
path-database
Maintenance Association: MA1, Local Mep: 1
show oam ethernet user@host> show oam ethernet connectivity-fault-management linktrace path-database
connectivity-fault- maintenance-domain MD2 maintenance-association MA2 00:06:07:08:09:0A
management linktrace Linktrace to 00:06:07:08:09:0A, Interface : ge-5/0/1.0
Maintenance Domain: MD2, Level: 6
path-database (Two
Maintenance Association: MA2, Local Mep: 10
traceroute commands)
Hop TTL Source MAC address Next hop MAC address
Transaction Identifier:100002
1 63 00:00:aa:aa:aa:aa 00:00:bb:bb:bb:bb
2 62 00:00:bb:bb:bb:bb 00:00:cc:cc:cc:cc
3 61 00:00:cc:cc:cc:cc 00:06:07:08:09:0A
4 60 00:06:07:08:09:0A 00:00:00:00:00:00
Transaction Identifier:100003
1 63 00:00:aa:aa:aa:aa 00:00:bb:bb:bb:bb
2 62 00:00:bb:bb:bb:bb 00:00:cc:cc:cc:cc
3 61 00:00:cc:cc:cc:cc 00:06:07:08:09:0A
4 60 00:06:07:08:09:0A 00:00:00:00:00:00
traceroute ethernet
Before using the traceroute command, you can verify the remote MEP’s MAC address
using the show oam ethernet connectivity-fault-management path-database command.
ttl value—Number of hops to use in the linktrace request. Range is 1 to 255 hops.
Default is 4.
wait seconds—Maximum time to wait for a response to the traceroute request. Range
is 1 to 255 seconds. Default is 5.
Transaction Identifier A 4-byte identifier maintained by the MEP. Each LTM uses a
transaction identifier. The transaction identifier is maintained
globally across all Maintenance Domains. Use the transaction
identifier to match an incoming linktrace response (LTR), with a
previously sent LTM.
Source MAC address MAC address of the 802.1ag maintenance point that is sending the
linktrace message.
Next-hop MAC address MAC address of the 802.1ag node that is the next hop in the LTM
path.
Table 47 on page 199 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot Virtual Router Redundancy Protocol (VRRP) on
Ethernet, Fast Ethernet, Gigabit Ethernet, 10-Gigabit Ethernet, and logical tunnel
interfaces. Commands are listed in alphabetical order.
Task Command
■ 199
JUNOS 9.0 Interfaces Command Reference
clear vrrp
show vrrp
Options none—(Same as brief) Display brief status information about all VRRP interfaces.
Interface index Physical interface index number, which reflects its initialization sequence. extensive
Active Total number of VRRP groups that are active (that is, whose interface state is extensive
either up or down).
Interface VRRP PDU Nonerrored statistics for the logical interface: extensive
statistics
■ Advertisement sent—Number of VRRP advertisement protocol data units
(PDUs) that the interface has transmitted.
■ Advertisement received—Number of VRRP advertisement PDUs received
by the interface.
■ Packets received—Number of VRRP packets received for VRRP groups on
the interface.
■ No group match received—Number of VRRP packets received for VRRP
groups that do not exist on the interface.
Interface VRRP PDU Errored statistics for the logical interface: extensive
error statistics
■ Invalid IPAH next type received—Number of packets received that use the
IP Authentication Header protocol (IPAH) and that do not encapsulate
VRRP packets.
■ Invalid VRRP ttl value received—Number of packets received whose IP time-
to-live (TTL) value is not 255.
■ Invalid VRRP version received—Number of packets received whose VRRP
version is not 2.
■ Invalid VRRP pdu type received—Number of packets received whose VRRP
PDU type is not 1.
■ Invalid VRRP authentication type received—Number of packets received
whose VRRP authentication is not none, simple, or md5.
■ Invalid VRRP IP count received—Number of packets received whose VRRP
IP count exceeds 8.
■ Invalid VRRP checksum received—Number of packets received whose VRRP
checksum does not match the calculated one.
Index Physical interface index number, which reflects its initialization sequence. detail extensive
SNMP ifIndex SNMP index number for the physical interface. detail extensive
Type and Address Identifier for the address and the address itself: brief none summary
■ lcl—Configured local interface address.
■ mas—Address of the master virtual router. This address is displayed only
when the local interface is acting as a backup router.
■ vip—Configured virtual IP addresses.
Authentication type Configured VRRP authentication type: none, simple, or md5. detail extensive
Preempt Whether preemption is allowed on the interface: yes or no. detail extensive
Accept-data mode Whether the interface is configured to accept packets destined for the virtual detail extensive
IP address: yes or no.
VIP count Number of virtual IP addresses that have been configured on the interface. detail extensive
Advertisement timer How long, in seconds, until the advertisement timer expires. detail extensive
Master router IP address of the interface that is acting as the master. detail extensive
Virtual router uptime How long, in seconds, that the virtual router has been up. detail extensive
Master router How long, in seconds, that the master route has been up. detail extensive
uptime
Virtual MAC MAC address associated with the virtual IP address. detail extensive
Current priority Current operational priority for being the VRRP master. detail extensive
Configured priority Configured base priority for being the VRRP master. detail extensive
Priority hold-time Minimum time interval, in seconds, between successive changes to the current detail extensive
priority. Disabled indicates no minimum interval.
Remaining-time (track option only) Displays the time remaining in the priority hold-time interval. detail
Interface tracking Whether interface tracking is enabled or disabled. When enabled, the output detail extensive
also displays the number of tracked interfaces.
Int state/Interface Current operational state of the tracked interface: up or down. detail extensive
state
Int speed/Speed Current operational speed, in bits per second, of the tracked interface. detail extensive
Incurred priority cost Operational priority cost incurred due to the state and speed of this tracked detail extensive
interface. This cost is applied to the configured priority to obtain the current
priority.
Threshold Speed below which the corresponding priority cost is incurred. In other words, detail extensive
when the speed of the interface drops below the threshold speed, the
corresponding priority cost is incurred.
An entry of down means that the corresponding priority cost is incurred when
the interface is down.
Route tracking Whether route tracking is enabled or disabled. When enabled, the output also detail extensive
displays the number of tracked routes.
VRF name The VPN routing and forwarding (VRF) routing instance that the tracked route detail extensive
is in.
Route state The state of the route being tracked: up, down, or unknown. detail extensive
Priority cost Configured priority cost. This value is incurred when the interface speed drops detail extensive
below the corresponding threshold or when the tracked route goes down.
Active Whether the threshold is active (*). If the threshold is active, the corresponding detail extensive
priority cost is incurred.
Group VRRP PDU Number of VRRP advertisements sent and received by the group. extensive
statistics
Group VRRP PDU Errored statistics for the VRRP group: extensive
error statistics
■ Bad authentication type received—Number of VRRP PDUs received with
an invalid authentication type. The received authentication can be none,
simple, or md5 and must be the same for all routing platforms in the VRRP
group.
■ Bad password received—Number of VRRP PDUs received with an invalid
key (password). The password for simple authentication must be the same
for all routing platforms in the VRRP group
■ Bad MD5 digest received—Number of VRRP PDUs received for which the
MD5 digest computed from the VRRP PDU differs from the digest expected
by the VRRP instance configured on the router.
■ Bad advertisement timer received—Number of VRRP PDUs received with
an advertisement time interval that is inconsistent with the one in use
among the routers in the VRRP group.
■ Bad VIP count received—Number of VRRP PDUs whose virtual IP address
counts differ from the count that has been configured on the VRRP
instance.
■ Bad VIPADDR received—Number of VRRP PDUs whose virtual IP addresses
differ from the list of virtual IP addresses configured on the VRRP instance.
Group state State transition statistics for the VRRP group: extensive
transition statistics
■ Idle to master transitions—Number of times that the VRRP instance
transitioned from the idle state to the master state.
■ Idle to backup transitions—Number of times that the VRRP instance
transitioned from the idle state to the backup state.
■ Backup to master transitions—Number of times that the VRRP instance
transitioned from the backup state to the master state.
■ Master to backup transitions—Number of times that the VRRP instance
transitioned from the master state to the backup state.
vip fe80::12:1:1:99
vip fec0::12:1:1:99
fe-0/0/2.131 up 1 master A 0.364 lcl fec0::13:1:1:1
vip fe80::13:1:1:99
vip fec0::13:1:1:99
show vrrp brief The output for the show vrrp brief command is identical to that for the show vrrp
command. For sample output, see show vrrp on page 205
fec0::13:1:1:99
Advertisement timer: 0.396s, Master router: fe80::13:1:1:1
Virtual router uptime: 00:04:04, Master router uptime: 00:03:58
Virtual MAC: 00:00:5e:00:02:01
Tracking: disabled
Group VRRP PDU statistics
Advertisement sent : 186
Advertisement received : 0
Group VRRP PDU error statistics
Bad authentication type received: 0
Bad password received : 0
Bad MD5 digest received : 0
Bad advertisement timer received: 0
Bad VIP count received : 0
Bad VIPADDR received : 0
Group state transition statistics
Idle to master transitions : 0
Idle to backup transitions : 1
Backup to master transitions : 1
Master to backup transitions : 0
Table 49 on page 213 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot digital transmission interfaces (T1, E1, T3, and
E3). Commands are listed in alphabetical order.
Task Command
Display status information about T1 or E1 show interfaces (T1 or E1) on page 214
interfaces.
Display status information about T3 or E3 show interfaces (T3 or E3) on page 231
interfaces.
NOTE: Because the output for the E1 and T1 interfaces is almost identical, the
command and output are explained once, with notations included for any differences.
The same is true for the E3 and T3 interfaces.
■ 213
JUNOS 9.0 Interfaces Command Reference
Options interface-type—On M-series and T-series routing platforms, the T1 interface type is
t1-fpc/pic/port, whereas the E1 interface type is e1-fpc/pic/port. On the J-series
routing platform, the T1 interface type is t1-pim/0/port, whereas the E1 interface
type is e1-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 bits. All levels
Framing Physical layer framing format used on the link: G704, G704-NO-CRC4, or All levels
Unframed. The default is G704.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalives. detail extensive none
■ interval seconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a default
of 10 seconds.
■ down-count number—The number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
■ up-count number—The number of keepalive packets a destination must
receive to change a link's status from down to up. The range is 1 through
255, with a default of 1.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. (When no level of output detail extensive none
is specified, the word statistics is not part of the field name and the last seen
text is not displayed.)
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago).—Time since the last keepalive packet was
received, in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
LMI settings (Frame Relay) Settings for Local Management Interface (LMI) can be either detail extensive none
ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default. The
format is (ANSI or ITU) LMI settings: value, value... xx seconds, where value can
be:
■ n391dte—DTE full status polling interval (1–255)
■ n392dce—DCE error threshold (1–10)
■ n392dte—DTE error threshold (1–10)
■ n393dce—DCE monitored event count (1–10)
■ n393dte—DTE monitored event count (1–10)
■ t391dte—DTE polling timer (5–30 seconds)
■ t392dce—DCE polling verification timer (5–30 seconds)
LMI (Frame Relay) Local Management Interface (LMI) packet statistics: detail extensive none
■ Input—Number of packets coming in on the interface (nn) and how much
time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).
■ Output—Number of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn
(last sent hh:mm:ss ago).
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data communications equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no Local Management Interface (LMI) packet was reported for
n392dte or n393dce intervals. (See LMI settings.)
Nonmatching (Frame Relay. Displayed only from the DTE.) Number of DLCIs configured from detail extensive none
DCE-end DLCIs the DCE.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Down—CHAP authentication is incomplete (not yet completed or has
failed).
■ Not-configured—CHAP is not configured on the interface.
■ Opened—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ SRAM errors—Number of hardware errors that occurred in the static RAM
(SRAM) on the PIC or PIM. If the value of this field increments, the PIC or
PIM is malfunctioning.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC or PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
DS1 alarms E1 media-specific defects that can prevent the interface from passing packets. detail extensive none
When a defect persists for a certain amount of time, it is promoted to an alarm.
DS1 defects Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
The following lists all possible alarms and defects. For complete explanations
of most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.
■ AIS—Alarm indication signal.
■ LOF—Loss of frame.
■ LOS—Loss of signal.
■ YLW—Yellow alarm. Indicates errors at the remote site receiver.
DS1 BERT BERT (bit error rate test) checks the quality of the line. This output appears detail extensive none
configuration only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—The queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority. Possible values are low and high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics (Frame Relay) Number and rate of bytes and packets received and transmitted detail extensive
on the logical interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Local statistics (Frame Relay) Statistics for traffic received from and transmitted to the Routing detail extensive
Engine. When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. It takes awhile (generally, less
than 1 second) for this counter to stabilize.
Transit statistics (Frame Relay) Statistics for traffic transiting the router. When a burst of traffic detail extensive
is received, the value in the output packet rate field might briefly exceed the
peak cell rate. This counter normally stabilizes in less than 1 second.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mlfr, or detail extensive none
mpls.
Multilink bundle Interface name for the multilink bundle, if configured. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive none
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive none
information is displayed: Flags, Total down time, Last down, and Traffic statistics
or (Input packets, Output packets). Flags can be one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when the link is active, but no information is received from
the DCE.
■ DCE-Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ DCE-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 40 40 0
PCV 0 0
CS 0 0
CRC 154 15400
...
Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 42 42 0
CS 0 0
LES 1
ES 1
SES 1
SEFS 1
BES 0
UAS 0
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 1514, Runt threshold: 3
Timeslots : All active
Line encoding: B8ZS
Buildout : 0 to 132 feet
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1
Packet Forwarding Engine configuration:
Destination slot: 1, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 1459200 95 0 low none
3 network-control 5 76800 5 0 low none
0 limited 0 0 0
1 expedited-fo 0 0 0
2 real-plus 0 0 0
3 network-cont 15 15 0
DCE statistics:
Enquiries received : 0
Full enquiries received : 0
Enquiry responses sent : 0
Full enquiry responses sent : 0
Common statistics:
Unknown messages received : 0
Asynchronous updates received : 0
Out-of-sequence packets received : 0
Keepalive responses timedout : 1
CoS queues : 8 supported
Last flapped : 2005-11-30 14:50:34 PST (4d 20:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 0 0 bps
Output bytes : 225 0 bps
Input packets: 0 0 pps
Output packets: 15 0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 17, Errors: 0, Drops: 0, Aged packets: 0,
MTU errors: 0, Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 limited 0 0 0
1 expedited-fo 0 0 0
2 real-plus 0 0 0
3 network-cont 15 15 0
Line encoding: HDB3, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 3, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 limited 95 1945600 95 0 low none
3 network-control 5 102400 5 0 low none
Logical interface e1-3/0/0.0 (Index 72) (SNMP ifIndex 32) (Generation 26)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 1500, Generation: 32, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.1.3/24, Local: 10.1.3.1, Broadcast: 10.1.3.255,
Generation: 42
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:01:21 sec, Last down: 00:01:21 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1
Options interface-type—On M-series and T-series routing platforms, the T3 interface type is
t3-fpc/pic/port, whereas the E3 interface type is e3-fpc/pic/port On the J-series
routing platform, the T3 interface type is t3-pim/0/port, whereas the E3 interface
type is e3-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 bits. All levels
Mode (T3 only) Whether C-bit parity mode or M13 mode is enabled. All levels
Long buildout (T3 only) Buildout setting: less than 255 feet (68 meters) or greater than 255 All levels
feet and shorter than 450 feet (137 meters).
Framing (E3 only) Physical layer framing format used on the link. It can be G751 or All levels
Unframed. The default is G751.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalives. detail extensive none
■ interval seconds—Time in seconds between successive keepalive requests.
The range is 10 seconds through 32,767 seconds, with a default of 10
seconds.
■ down-count number—Number of keepalive packets a destination must fail
to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
■ up-count number—Number of keepalive packets a destination must receive
to change a link's status from down to up. The range is 1 through 255,
with a default of 1.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. detail extensive none
or Keepalive
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
received, in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
LMI settings (Frame Relay) Local Management Interface (LMI) settings (ANSI or ITU). ANSI detail extensive none
LMI settings is the default. The format is LMI settings: value, value... xx seconds,
where value can be:
■ n391dte—DTE full status polling interval (1–255)
■ n392dce—DCE error threshold (1–10)
■ n392dte—DTE error threshold (1–10)
■ n393dce—DCE monitored event count (1–10)
■ n393dte—DTE monitored event count (1–10)
■ t391dte—DTE polling timer (5–30 seconds)
■ t392dce—DCE polling verification timer (5–30 seconds)
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data communications equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no LMI packet was reported for n392dte or n393dce intervals.
(See LMI settings.)
Nonmatching (Frame Relay. Displayed only from the DTE.) Number of DLCIs configured from detail extensive none
DCE-end DLCIs the DCE.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Resp-received—Response received for the challenge sent, but CHAP
not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response sent for the challenge received.
■ Chap-Chal-sent—Challenge sent.
■ Chap-Chal-received—Challenge received but response not yet sent.
■ Down—CHAP authentication is incomplete (not yet completed or has
failed).
■ Not-configured—CHAP is not configured on the interface.
■ Opened—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (year-month-day
hour:minute:second ago) . For example, Last flapped: 2002-04-26 10:52:40 PDT
(04:33:20 ago).
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface
■ Output packets—Number of packets received on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—(T3 only) Number of frames received that are smaller than the
runt threshold.
■ Giants—(T3 only) Number of frames received that are larger than the giant
threshold.
■ Bucket Drops—Drops resulting from the traffic load exceeding the interface
transmit/receive leaky bucket configuration. The default is off.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ SRAM errors—Number of hardware errors that occurred in the static RAM
(SRAM) on the PIC or PIM. If the value of this field increments, the PIC or
PIM is malfunctioning.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments (perhaps once every 10 seconds), the cable, the far-end system,
or the PIC or PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Active alarms E3 media-specific defects that can render the interface unable to pass packets. detail extensive none
When a defect persists for a certain amount of time, it is promoted to an alarm.
Active defects Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
■ AIS—Alarm indication signal
■ EXZ—Excessive zeros
■ FERF—Far-end receive failures
■ IDLE—Idle code detected
■ LCD—Loss of cell delineation
■ LCV—Line code violation
■ LOF—Loss of frame
■ LOS—Loss of signal
■ PLL—Phase-locked loop
■ YLW—Remote defect indication
DSU configuration Information about the DSU configuration. The last three lines (Bit count, Error extensive
bit count, and LOS information ) are displayed only if a BERT has ever been run
on the interface.
■ Compatibility mod—CSU/DSU compatibility mode: None, Larscom, Kentrox,
or Digital-Link.
■ Scrambling—Payload scrambling: Enabled or Disabled.
■ Subrate—Configured subrate setting. Applies only when Digital-Link
compatibility mode is used. The subrate can be Disabled or display units
in Kbps.
■ FEAC loopbac—(T3) Whether a far-end alarm and control (FEAC) loopback
is Active or Inactive. This feature is used to send alarm or status information
from the far-end terminal back to the near-end terminal and to initiate
T3 loopbacks at the far-end terminal from the near-end terminal.
■ Response—Whether the FEAC signal is Enabled or Disabled.
■ Count—Number of FEAC loopbacks.
DS3 (or E3) BERT BERT (bit error rate test) checks the quality of the line. This output appears detail extensive none
configuration only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—The queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. detail extensive none
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. extensive
Flags Information about the interface. Possible values are described in “Interface detail extensive none
Flags” on page 80.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics (Frame Relay) Number and rate of bytes and packets received and transmitted detail extensive
on the logical interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Local statistics (Frame Relay) Statistics for traffic received from and transmitted to the Routing detail extensive
Engine. When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. It takes awhile (generally, less
than 1 second) for this counter to stabilize.
Transit statistics (Frame Relay) Statistics for traffic transiting the router. When a burst of traffic detail extensive
is received, the value in the output packet rate field might briefly exceed the
peak cell rate. This counter normally stabilizes in less than 1 second.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mlfr, or detail extensive none
mpls.
Multilink bundle (Multilink) Interface name for the multilink bundle. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive none
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive none
information is displayed: Flags, Total down time, Last down, and Traffic statistics
(or Input packets, Output packets). Flags is one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when the link is active, but no information is received from
the DCE.
■ DCE Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ DCE-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 6 6 0
Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 7 7 0
DSU configuration:
Compatibility mode: None, Scrambling: Disabled, Subrate: Disabled
FEAC loopback: Inactive, Response: Disabled, Count: 0
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, O.151, Pseudorandom (9), Induced error rate: 10e-0
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 42499200 95 0 low none
3 network-control 5 2236800 5 0 low none
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:00:06 sec, Last down: 00:00:06 ago
Input packets : 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 43 43 0
Logical interface e3-1/2/0.0 (Index 66) (SNMP ifIndex 57) (Generation 15)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 24, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 38
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:00:16 sec, Last down: 00:00:16 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1
Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 44 44 0
Logical interface e3-1/2/0.0 (Index 66) (SNMP ifIndex 57) (Generation 15)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 24, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 38
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:00:19 sec, Last down: 00:00:19 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1
Table 52 on page 251 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot IP demultiplexing (demux) interfaces. Commands
are listed in alphabetical order.
Task Command
■ 251
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. brief detail extensive
media statistics none
Interface index Index number of the physical interface, which reflects its initialization sequence. brief detail extensive
media statistics none
Enabled State of the interface. Possible values are described in “Enabled brief detail extensive
Field” on page 78. media statisticsnone
Physical link Status of the physical link (Up or Down). detail extensive media
statistics none
Interface index Index number of the physical interface, which reflects its initialization sequence. detail extensive media
statistics none
SNMP ifIndex SNMP index number for the physical interface. detail extensive media
statistics none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Type Type of interface. Software-Pseudo indicates a standard software interface with brief detail extensive
no associated hardware device. media statistics none
Link-level type Encapsulation being used on the physical interface. brief detail extensive
MTU Maximum transmission unit size on the physical interface. brief detail extensive
media statistics
Clocking Reference clock source: Internal (1) or External (2). brief detail extensive
media statistics
Device flags Information about the physical device. Possible values are described in “Device brief detail extensive
Flags” on page 79. media statistics none
Interface flags Information about the interface. Possible values are described in “Interface brief detail extensive
Flags” on page 80. media statistics none
Link flags Information about the link. Possible values are described in “Link detail extensive media
Flags” on page 81. statistics none
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive media
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second statistics none
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared statistics
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
■ IPv6 transit statistics—Number of IPv6 transit bytes and packets received
and transmitted on the physical interface if IPv6 statistics tracking is
enabled.
■ Input bytes—Number of bytes received on the interface
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive statistics
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Giants—Number of frames received that are larger than the giant packet
threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ Resource errors—Sum of transmit drops.
Input Rate Input rate in bits per second (bps) and packets per second (pps). media statistics none
Output errors Output errors on the interface. The following paragraphs explain the counters extensive statistics
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC or PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Output Rate Output rate in bps and pps. media statistics none
Logical Interface
Logical interface Name of the logical interface. brief detail extensive
statistics none
Index Index number of the logical interface, which reflects its initialization sequence. detail extensive
statistics none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive
statistics none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical brief detail extensive
Interface Flags” on page 82. statistics none
Traffic statistics Number and rate of bytes and packets received and transmitted on the specified detail extensive
interface set.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface set.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface set.
■ IPv6 transit statistics—Number of IPv6 transit bytes and packets received
and transmitted on the logical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Local statistics Number of transit bytes and packets received and transmitted on the local detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Transit statistics Number and rate of bytes and packets transiting the switch. detail extensive
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
IPv6 Transit Number of IPv6 transit bytes and packets received and transmitted on the detail extensive
statistics logical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Protocol Protocol family. Possible values are described in “Protocol Field” on page 83. detail extensive
statistics none
MTU Maximum transmission unit size on the logical interface. detail extensive
statistics none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Route table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about protocol family flags. Possible values are described in “Family detail extensive
Flags” on page 80. statistics none
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Logical interface demux0.0 (Index 87) (SNMP ifIndex 84) (Generation 312)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Traffic statistics:
Input bytes : 0
Output bytes : 1554
Input packets: 0
Output packets: 37
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 1554
Input packets: 0
Output packets: 37
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Protocol inet, MTU: 1500, Generation: 395, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 11.1.1/24, Local: 11.1.1.1, Broadcast: 11.1.1.255,
Generation: 434
Table 54 on page 261 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot Point-to-Point Protocol (PPP) interfaces.
Commands are listed in alphabetical order.
Task Command
Display PPP address pool information. show ppp address-pool on page 263
Display PPP session information for an interface. show ppp interface on page 265
■ 261
JUNOS 9.0 Interfaces Command Reference
Address range Range of sequentially ordered IP addresses contained in the address pool. detail
Number of assigned Fixed IP address that is to be given to remote users when they dial in. This is All levels
addresses a host-only IP address (subnet mask is 255.255.255.255) and is only for single
connection receiver profiles.
Number of Number of IP addresses that are available for allocation and used by PPP All levels
addresses sessions.
configured
Assigned addresses Addresses assigned to PPP sessions from the address pool. detail
Level of
Field Name Field Description Output
Session Name of the logical interface on which the session is running. All levels
Phase PPP process phase: Authenticate, Pending, Establish, LCP, Network, and Disabled. All levels
Session flags Special conditions present in the session: Bundled, TCC, No-keepalives, Looped, Monitored, and All levels
NCP-only.
protocol State Protocol state information. See specific protocol state fields for information. None
specified
Level of
Field Name Field Description Output
Level of
Field Name Field Description Output
Authentication CHAP or PAP authentication state information. For CHAP authentication: None
specified
■ Chap-ans-rcvd—Packet was sent from the peer, indicating that the peer received the
Chap-resp-sent packet.
■ Chap-ans-sent—Packet was sent from the authenticator, indicating that the authenticator
received the peer's Chap-resp-rcvd packet.
■ Chap-chal-rcvd—Challenge packet has been received by the peer.
■ Chap-chal-sent—Challenge packet has been sent by the authenticator to begin the CHAP
protocol or has been transmitted at any time during the Network-Layer Protocol (NCP)
phase to ensure that the connection has not been altered.
■ Chap-resp-rcvd—CHAP response packet has been received by the authenticator.
■ Chap-resp-sent—CHAP response packet has been sent to the authenticator.
■ Closed—Link is not available for authentication.
■ Failure—Authenticator compares the response value in the response packet from the peer
with its own response value, but the value does not match. Authentication fails.
■ Success—Authenticator compares the response value in the response packet from the
peer with its own response value, and the value matches. Authentication is successful.
For PAP authentication:
■ Pap-resp-sent—PAP response sent to peer (ACK/NACK)t.
■ Pap-req-rcvd—PAP request packet received from peer.
■ Pap-resp-rcvd—PAP response received from the peer (ACK/NACK).
■ Pap-req-sent—PAP request packet sent to the peer.
■ Closed—Link is not available for authentication.
■ Failure—Authenticator compares the response value in the response packet from the peer
with its own response value, but the value does not match. Authentication fails.
■ Success—Authenticator compares the response value in the response packet from the
peer with its own response value, and the value matches. Authentication is successful.
Level of
Field Name Field Description Output
Level of
Field Name Field Description Output
OSINLCP State OSI Network Layer Control Protocol (OSINLCP) protocol state information: extensive
■ State:
■ Ack-rcvd—Configure-Request has been sent and Configure-Ack has been received.
■ Ack-sent—Configure-Request and Configure-Ack have both been sent, but
Configure-Ack has not yet been received.
■ Closed—Link is not available for traffic.
■ Opened—Link is administratively available for traffic.
■ Req-sent—Attempt has been made to configure the connection.
■ Last started—OSINLCP state start time.
■ Last completed—OSINCLP state completion time.
Negotiated options:
Local address: 10.10.10.1, Remote address: 10.10.10.2
show ppp interface terse user@host> show ppp interface so-1/3/0 terse
Session name Session type Session phase Session flags
so-1/3/0.0 PPP Authenticate Monitored
Sessions in Number of PPP sessions disabled. Number of sessions where the link is either none detail
disabled phase administratively or physically down. Once the PPP process learns from the
kernel that Layer 2 is ready to send and receive traffic, it will do a phase
transition from disabled to established. When LCP and NCP transitions through
states, links transition to the establish phase when terminate packets are
exchanged or some other failure, such as authentication or expiration of a
timer occurs.
Sessions in Number of PPP sessions in establish phase. In order to establish none detail
establish phase communications over a point-to-point link, each end of the PPP link must first
send LCP packets to configure and test the data link.
Sessions in Number of PPP sessions in authenticate phase. Each end of the PPP link must none detail
authenticate phase first send LCP packets to configure the data link during the link establishment
phase. After the link has been established, PPP provides for an optional
authentication phase before proceeding to the Network-Layer Protocol (NLP)
phase.
Sessions in network Number of PPP sessions in the network phase. After a link has been established none detail
phase and optional facilities have been negotiated as needed by the LCP, PPP must
send Network Control Protocol (NCP) packets to choose and configure one or
more network-layer protocols, such as IP, IPX, or AppleTalk. Once each of the
chosen network-layer protocols has been configured, datagrams from each
network-layer protocol can be sent over the link.
Bundles in pending Number of unique bundles to which PPP links are referring. none detail
phase
Type (continued) ■ ML bundle settings—Multilink bundle settings. Stores the context detail
information for a MLPPP bundle.
■ PPP LCP session—PPP Link Control Protocol session, used for establishing,
configuring, and testing the data-link connection. Stores the information
for an LCP session, such as negotiated options, current state, and statistics.
■ PPP NCP session—PPP Network Control Protocol (NCP) phase in the PPP
link connection process. Stores the information for an NCP session, such
as negotiated options, current state, address family, and statistics.
■ Physical interface—Stores the information about the physical interface that
PPP obtains from the kernel.
■ Access profile—Stores the information found at the [edit access profile]
hierarchy level for each profile.
■ ML wait entry—Created when there are MLPPP links joining a bundle.
before its addition to the PPP process. Links are saved here, and when
the bundle is added, are properly assigned to the bundle.
■ Group profile—Stores information set in the PPP stanza of a group profile,
such as the primary and secondary Domain Name System (DNS), primary
and secondary NDNS, and address pool name.
■ Profile client—Stores the per-client information of the access profile
(information obtained from the [set access profile name client client-name]
hierarchy level.
■ PPP Auth session—PPP authentication session. Stores all the session-specific
authentication protocol parameters.
■ Logical interface—Stores the information about the logical interface that
PPP obtains from the kernel.
■ Non-tagged—Generic catch-all for allocations not of a particular structure
type.
Free Number of instances of the structure that are on the free list. Types with a detail
number in the Free column are pooled structures, and are typically types that
are often used.
Limit Maximum number of instances that can be on the free list. Types with a number detail
in the Limit column are pooled structures, and are typically types that are often
used.
Total size Total amount of memory being used by a type of structure (includes active and detail
free instances).
Session flags Special conditions present in the session, such as Bundled, TCC,
No-keepalives, Looped, Monitored, and NCP-only.
Table 59 on page 277 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot Point-to-Point Protocol over Ethernet (PPPoE)
interfaces. Commands are listed in alphabetical order.
Task Command
■ 277
JUNOS 9.0 Interfaces Command Reference
NOTE: PPPoE interfaces are supported on Fast Ethernet and ATM-over-ADSL and
ATM-over-SHDSL interfaces on the J-series routing platform. PPPoE interfaces connect
multiple PPPoE-client hosts on an Ethernet LAN to a remote site through a J-series
Services Router. The J-series router can only be configured as a PPPoE client. Hosts
share a common digital subscriber line (DSL), a cable modem, or a wireless connection
to the Internet. For information about how to configure PPPoE interfaces, see the
J-series Services Router Basic LAN and WAN Access Configuration Guide or the JUNOS
Network Interfaces Configuration Guide.
For information about monitoring and troubleshooting Fast Ethernet interfaces, see
“Ethernet Interface Operational Mode Commands” on page 87.
NOTE: PPPoE interfaces are supported on Gigabit Ethernet and 10-Gigabit Ethernet
interfaces on the M120 routing platform. The M120 router can only be configured
as a PPPoE access concentrator.
278 ■
Chapter 9: PPPoE Interface Operational Mode Commands
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link type Physical interface link type: full duplex or half duplex. All levels
Link flags Information about the interface. Possible values are described in “Link All levels
Flags” on page 81.
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on the detail extensive
statistics physical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions —Number of times the interface has gone from down
to up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of B chip Tx drops and IXP Tx net transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number (which reflects its initialization sequence). detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. This counter usually takes less than 1 second
to stabilize.
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on the detail extensive
statistics logical interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. This counter usually takes less than 1 second
to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
This counter usually takes less than 1 second to stabilize.
Keepalive settings (PPP and HDLC) Configured settings for keepalives. detail extensive
■ interval seconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a default
of 10 seconds.
■ down-countnumber—The number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
■ up-count number—The number of keepalive packets a destination must
receive to change a link's status from down to up. The range is 1 through
255, with a default of 1.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. detail extensive
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time the last keepalive packet was received,
in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time the last keepalive packet was sent,
in the format hh:mm:ss.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
LCP state (PPP) Link Control Protocol state. none detail extensive
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol none detail extensive
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Protocol Protocol family configured on the logical interface. detail extensive none
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive none
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the addresses configured for the protocol family. Possible detail extensive none
values are described in “Addresses, Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Logical interface pp0.0 (Index 72) (SNMP ifIndex 72) (Generation 14)
Flags: Hardware-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionDown, Session ID: None,
Service name: None, Configured AC name: sapphire,
Auto-reconnect timeout: 100 seconds, Idle timeout: Never,
Underlying interface: at-5/0/0.0 (Index 70)
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
LCP state: Not-configured
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 100, Generation: 14, Route table: 0
Flags: User-MTU, Negotiate-Address
Traffic statistics:
Input bytes : 972192 0 bps
Output bytes : 975010 0 bps
Input packets: 1338 0 pps
Output packets: 1473 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Logical interface pp0.0 (Index 69) (SNMP ifIndex 96) (Generation 194)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionUp, Session ID: 26,
Session AC name: None, AC MAC address: 00:17:cb:48:c8:12,
Service name: None, Configured AC name: None,
Auto-reconnect timeout: Never, Idle timeout: Never,
Underlying interface: ge-3/0/1.0 (Index 67)
Traffic statistics:
Input bytes : 252
Output bytes : 296
Input packets: 7
Output packets: 8
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 252
Output bytes : 296
Input packets: 7
Output packets: 8
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 1 (last seen 00:00:00 ago)
Output: 1 (last sent 00:00:03 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
PAP state: Closed
Protocol inet, MTU: 1492, Generation: 171, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.12.12.2, Local: 12.12.12.1, Broadcast: Unspecified,
Generation: 206
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface, which reflects its initialization sequence. detail extensive none
Service name Type of service required (can be used to indicate an ISP name or a class or detail extensive none
quality of service).
AC MAC address MAC address of the access concentrator. detail extensive none
Auto-reconnect Time after which to try to reconnect after a PPPoE session is terminated, in detail extensive none
timeout seconds.
Idle timeout Length of time (in seconds) that a connection can be idle before disconnecting. detail extensive none
Packet Type Number of packets sent and received during the PPPoE session, categorized extensive
by packet type and packet errors:
■ PADI—PPPoE Active Discovery Initiation packets.
■ PADO—PPPoE Active Discovery Offer packets.
■ PADR—PPPoE Active Discovery Request packets.
■ PADS—PPPoE Active Discovery Session-Confirmation packets.
■ PADT—PPPoE Active Discovery Termination packets.
■ Service name error—Packets for which the Service-Name request could
not be honored.
■ AC system error—Packets for which the access concentrator experienced
an error in performing the host request. For example, the host had
insufficient resources to create a virtual circuit.
■ Generic error—Packets that indicate an unrecoverable error occurred.
■ Malformed packets—Malformed or short packets that caused the packet
handler to discard the frame as unreadable.
■ Unknown packets—Unrecognized packets.
Timeout Information about timeouts that occurred during the PPPoE session: extensive
■ PADI—No PADO packet has been received within the timeout period.
■ PADO—No PADR packet has been received within the timeout period.
(This value is always zero and is not supported.)
■ PADR—No PADS packet has been received within the timeout period.
Active PPPoE sessions Total number of active PPPoE sessions and the number of packets sent and received during the
PPPoE session, categorized by packet type and packet errors:
■ PADI—PPPoE Active Discovery Initiation packets.
■ PADO—PPPoE Active Discovery Offer packets.
■ PADR—PPPoE Active Discovery Request packets.
■ PADS—PPPoE Active Discovery Session-Confirmation packets.
■ PADT—PPPoE Active Discovery Termination packets.
■ Service name error—Packets for which the Service-Name request could not be honored.
■ AC system error—Packets for which the access concentrator experienced an error in performing
the host request. For example, the host had insufficient resources to create a virtual circuit.
■ Generic error—Packets that indicate an unrecoverable error occurred.
■ Malformed packets—Malformed or short packets that caused the packet handler to discard the
frame as unreadable.
■ Unknown packets—Unrecognized packets.
Timeouts Information about timeouts that occurred during the PPPoE session:
■ PADI—No PADR packet has been received within the timeout period. (This value is always zero
and is not supported.)
■ PADO—No PPPoE Active Discovery Offer packet has been received within the timeout period.
■ PADR—No PADS packet has been received within the timeout period.
PADI 0 0
PADO 0 0
PADR 0 0
PADS 0 0
PADT 0 0
Service name error 0 0
AC system error 0 0
Generic error 0 0
Malformed packets 0 0
Unknown packets 0 0
Timeouts
PADI 0
PADO 0
PADR 0
version n PPPoE version number and RFC. For example, version 1, rfc 2516.
Maximum Sessions Maximum active sessions supported per router. The default is 256 sessions.
PADI resend timeout Initial time, in seconds, that the router waits to receive a PADO packet for the PADI packet sent.
This timeout doubles for each successive PADI packet sent.
PADR resend timeout Initial time, in seconds, that the router waits to receive a PADS packet for the PADR packet sent.
This timeout doubles for each successive PADR packet sent.
Max resend timeout Maximum value, in seconds, that the PADI or PADR resend timer can accept. The maximum value
is 64.
Max Configured AC Time, in seconds, within which the configured access concentrator must respond.
timeout
Table 64 on page 299 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot serial interfaces. Commands are listed in
alphabetical order.
Task Command
Display status information about serial interfaces. show interfaces (Serial) on page 300
■ 299
JUNOS 9.0 Interfaces Command Reference
Options interface-type—On M-series and T-series routing platforms, the interface type is
se-fpc/pic/port. On the J-series routing platform, the interface type is
se-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
MTU Maximum transmission unit (MTU) size on the physical interface. All levels
Maximum speed Maximum speed. The nonconfigurable value is 16,384 kbps. detail extensive none
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalive packets. All levels
■ Interval seconds—Time between successive keepalive requests. The range
of values, in seconds, is 10 to 32,767. The default value is 10.
■ Up-count number—Number of keepalive packets a destination must receive
to change a link's status from down to up. The range of values is 1 to 255.
The default value is 1.
■ Down-count number—Number of keepalive packets a destination must fail
to receive before the network takes a link down. The range is 1 to 255.
The default value is 3.
Keepalive (PPP and HDLC) Information about keepalive packets. brief none
■ Input: number (hh:mm:ss ago)—Number of keepalive packets received by
PPP and the time since the last keepalive packet was received.
■ Output: number (hh:mm:ss ago)—Number of keepalive packets sent by PPP
and the time since the last keepalive packet was sent.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. detail extensive
■ Input: number (last seen hh:mm:ssago)—Number of keepalive packets
received by PPP and the time since the last keepalive packet was received.
■ Output: number(last seen hh:mm:ss ago)—Number of keepalive packets
sent by PPP and the time since the last keepalive packet was sent.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Giants—Number of frames received that are larger than the giant threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeds the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. Displayed detail extensive
supported with the statistics option.
Egress queues in Total number of egress queues in use on the specified interface. Displayed with detail extensive
use the statistics option.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
Displayed with the statistics option.
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—The queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority. Possible values are low and high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if there is excess
bandwidth available. If none is configured, the queue transmits
beyond the configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
source and destination address are also displayed.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about protocol family flags. Possible values are described in “Family detail extensive
Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Keepalive statistics:
Input : 37 (last seen 00:00:06 ago)
Output: 35 (last sent 00:00:01 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues : 8 supported, 8 maximum usable queues
Last flapped : 2006-04-26 15:10:18 PDT (00:06:02 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 928 40 bps
Output bytes : 1023 48 bps
Input packets: 76 0 pps
Output packets: 77 0 pps
Serial media information:
Line protocol: eia530
Resync history:
Sync loss count: 0
Data signal:
Rx Clock: OK
Control signals:
Local mode: DTE
To DCE: DTR: up, RTS: up
From DCE: CTS: up, DCD: up, DSR: up
Clocking mode: loop-timed
Clock rate: 8.0 MHz
Loopback: none
Tx clock: non-invert
Line encoding: nrz
Logical interface se-5/0/0.0 (Index 73) (SNMP ifIndex 27) (Generation 12)
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps
Encapsulation: PPP
Logical interface se-5/0/0.0 (Index 73) (SNMP ifIndex 27) (Generation 12)
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps
Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 17, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 13.0.0.0/30, Local: 13.0.0.2, Broadcast: 13.0.0.3,
Generation: 23
0 best-effort 24 24 0
1 expedited-fo 0 0 0
2 bulk 0 0 0
4 voip 0 0 0
Logical interface se-6/0/0.0 (Index 75) (SNMP ifIndex 69) (Generation 141)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 256, Generation: 145, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 11.11.11/24, Local: 11.11.11.2, Broadcast: 11.11.11.255,
Generation: 157
Table 66 on page 315 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot aggregated SONET/SDH interfaces and
SONET/SDH interfaces. Commands are listed in alphabetical order.
Task Command
Monitor Automatic Protection Switching (APS) information. show aps on page 316
Display status information about aggregated SONET/SDH interfaces. show interfaces (Aggregated SONET/SDH) on page
320
Display status information about SONET/SDH interfaces. show interfaces (SONET/SDH) on page 327
Display the transceiver temperature, laser bias current, laser output show interfaces diagnostics optics (SONET) on page
power, receive optical power, and related alarms for SONET interfaces. 354
For more information about monitoring and troubleshooting SONET interfaces, see
“Investigate SONET Interfaces” in the JUNOS Interfaces Network Operations Guide.
■ 315
JUNOS 9.0 Interfaces Command Reference
show aps
Options none—(Same as brief) Display brief information about APS for all groups and
SONET/SDH interfaces.
Intf state State of the circuit and interface in the format circuit-state, interface-state: All levels
For circuit-state:
■ enabled
■ disabled
■ invalid
■ unknown
For interface-state:
■ admin down
■ degraded
■ down
■ invalid
■ nonexistent
■ unknown
■ up
Neighbor Address and state of neighbor interface. If the working and protect interfaces detail extensive
are on the same router, the neighbor address is displayed as 0.0.0.0.
neighbor interface State of the neighbor interface: enabled or disabled. detail extensive
dead Number of seconds before the neighbor is declared dead detail extensive
Channel state Circuit that has been selected: Working or Protect. detail extensive
Local-mode Mode in which the local router is configured to interoperate with SONET extensive
line-terminating equipment (LTE): unidirectional or bidirectional. The parenthetical
value represents the mode type in the K2 byte.
neighbor-mode Mode in which the neighboring device is operating: unidirectional or bidirectional. extensive
The parenthetical value represents the mode type in the K2 byte.
Protect circuit is on Interface name of the APS protect circuit, displayed when both the working detail extensive
circuit and protect circuit are on the same router.
Working circuit is on Interface name of the APS working circuit, displayed when both the working detail extensive
circuit and protect circuit are on the same router.
Req K1 Value of the SONET/SDH K1 byte requested to be transmitted by this circuit. extensive
rcv K1 Value of the SONET/SDH K1 byte received on this interface. (Valid only on the extensive
protect circuit.)
xmit K1 Value of the SONET/SDH K1 byte being transmitted on this interface. (Valid extensive
only on the protect circuit.)
nbr K1 Value of the SONET/SDH K1 byte requested to be transmitted by the neighbor. extensive
nbr paired req Nonzero if the neighbor is requesting a particular K1 value because of a change extensive
in the paired circuit.
Revert time Configured time to wait after the working circuit has become functional before extensive
making the working circuit active again.
neighbor revert time Configured time, on the neighbor interface, to wait after the working circuit extensive
has again become functional before making the working circuit active again.
Hello due in Time until the next hello packet is sent. extensive
show aps brief The output for the show aps brief command is identical to that for the show aps
command. For sample output, see show aps on page 318.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Minimum links Number of child links that must be operational for the aggregated interface to detail extensive none
needed be operational.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Keepalive settings (PPP and HDLC) Configured settings for keepalives. All levels
■ interval seconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a default
of 10 seconds.
■ up-count number—The number of keepalive packets a destination must
receive to change a link's status from down to up. The range is1 through
255, with a default of 1.
■ down-count number—The number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number of bytes and packets received and transmitted on the physical interface, detail extensive
and the traffic rate in bits per seconds (bps).
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Giants—Number of frames received that are larger than the giant threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeds the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface's index number (which reflects its initialization sequence). detail extensive none
SNMP ifIndex Logical interface's SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82
Statistics Information about fragments and packets received and sent by the router All detail extensive none
references to traffic direction (input or output) are defined with respect to the
router. Input fragments received by the router are assembled into input packets;
output packets are segmented into output fragments for transmission out of
the router.
Statistics include input and output counts for packets, packets per second (pps),
bytes, and bytes per second (Bps) for the following entities:
■ Bundle—Information about bundles.
■ Link—Information about links used in the multilink operation.
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
source and destination address are also displayed.
Protocol Protocol family configured on the logical interface. detail extensive none
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface as0.0 (Index 79) (SNMP ifIndex 55) (Generation 18)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Bandwidth: 311040kbps
Statistics Packets pps Bytes bps
Bundle:
Input : 1334 2 13332 232
Output: 0 0 0 0
Link:
so-0/0/0.0 <-- down
Input : 0 0 0 0
Output: 0 0 0 0
so-0/0/1.0
Input : 541 1 5406 120
Output: 0 0 0 0
so-0/0/2.0
Input : 793 1 7926 112
Output: 0 0 0 0
Protocol inet, MTU: 4470, Generation: 38, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.100.1.1, Local: 10.100.1.2, Broadcast: Unspecified,
Generation: 40
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface as0.0 (Index 79) (SNMP ifIndex 55) (Generation 18)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Bandwidth: 311040kbps
Statistics Packets pps Bytes bps
Bundle:
Input : 1475 1 14742 136
Output: 0 0 0 0
Link:
so-0/0/0.0 <-- down
Input : 0 0 0 0
Output: 0 0 0 0
so-0/0/1.0
Input : 598 0 5976 24
Output: 0 0 0 0
so-0/0/2.0
Input : 877 1 8766 112
Output: 0 0 0 0
Protocol inet, MTU: 4470, Generation: 38, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.100.1.1, Local: 10.100.1.2, Broadcast: Unspecified,
Generation: 40
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Clocking SONET/SDH reference clock source: Internal or External. Clocking is configured All levels
and displayed only for channel 0.
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 bits. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
ANSI or ITU LMI (Frame Relay) Settings for Local Management Interface (LMI). The format is All levels
settings (ANSI or ITU) LMI settings: value, value... xx seconds, where value can be:
LMI Input: value (hh:mm:ss ago), Output: value (hh:mm:ss ago) brief none
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data circuit-terminating equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no LMI packet was reported for n392dte or n393dce intervals.
(See LMI settings.)
Nonmatching (Frame Relay. Displayed only from the DTE) Number of DLCIs configured from detail extensive
DCE-end DLCIs the DCE.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalives. All levels
■ interval seconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a default
of 10 seconds.
■ down-count number—The number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
■ up-count number—The number of keepalive packets a destination must
receive to change a link's status from down to up. The range is 1 through
255, with a default of 1.
Keepalive or (PPP and HDLC) Information about keepalive packets. All levels
Keepalive statistics
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
received, in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour: minute: second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number of bytes and packets received and transmitted on the physical interface, detail extensive
and the traffic rate in bits per seconds (bps).
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Giants—Number of frames received that are larger than the giant threshold.
■ Bucket Drops—Drops resulting from the traffic load exceeding the interface
transmit/receive leaky bucket configuration. The default is off.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ HS link FIFO overflows—Number of FIFO overflows on the high-speed links
between the ASICs responsible for handling the router interfaces.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ HS link FIFO underflows—Number of FIFO underflows on the high-speed
links between the ASICs responsible for handling the router interfaces.
■ MTU errors—Number of packets whose size exceeds the MTU of the
interface.
IPv6 transit Number of transit bytes and packets received and transmitted on the physical detail extensive
statistics interface if IPv6 statistics tracking is enabled.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
SONET alarms (SONET) SONET media-specific alarms and defects that prevents the interface All levels
from passing packets. When a defect persists for a certain period, it is promoted
SONET defects to an alarm. Based on the router configuration, an alarm can ring the red or
yellow alarm bell on the router or light the red or yellow alarm LED on the craft
interface. See these fields for possible alarms and defects: SONET PHY,
SONET section, SONET line, and SONET path.
Link (For 4-port OC192c PIC operating in OC768-over-4xOC192 mode) The link extensive
number. Errors and alarms are displayed for each link.
SONET PHY Counts of specific SONET errors with detailed information. extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SONET section Counts of specific SONET errors with detailed information. extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B1—Bit interleaved parity for SONET section overhead
■ SEF—Severely errored framing
■ LOL—Loss of light
■ LOF—Loss of frame
■ ES-S—Errored seconds (section)
■ SES-S—Severely errored seconds (section)
■ SEFS-S—Severely errored framing seconds (section)
SONET line Active alarms and defects, plus counts of specific SONET errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B2—Bit interleaved parity for SONET line overhead
■ REI-L—Remote error indication (near-end line)
■ RDI-L—Remote defect indication (near-end line)
■ AIS-L—Alarm indication signal (near-end line)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ ES-L—Errored seconds (near-end line)
■ SES-L—Severely errored seconds (near-end line)
■ UAS-L—Unavailable seconds (near-end line)
■ ES-LFE—Errored seconds (far-end line)
■ SES-LFE—Severely errored seconds (far-end line)
■ UAS-LFE—Unavailable seconds (far-end line)
SONET path Active alarms and defects, plus counts of specific SONET errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other thanOK indicates a problem.
Subfields are:
■ BIP-B3—Bit interleaved parity for SONET section overhead
■ REI-P—Remote error indication
■ LOP-P—Loss of pointer (path)
■ AIS-P—Path alarm indication signal
■ RDI-P—Path remote defect indication
■ UNEQ-P—Path unequipped
■ PLM-P—Path payload label mismatch
■ ES-P—Errored seconds (near-end STS path)
■ SES-P—Severely errored seconds (near-end STS path)
■ UAS-P—Unavailable seconds (near-end STS path)
■ ES-PFE—Errored seconds (far-end STS path)
■ SES-PFE—Severely errored seconds (far-end STS path)
■ UAS-PFE—Unavailable seconds (far-end STS path)
Received SONET Values of the received and transmitted SONET overhead: extensive
overhead
■ C2—Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
Transmitted SONET
overhead ■ F1—Section user channel byte. This byte is set aside for the purposes of
users.
■ K1 and K2—These bytes are allocated for APS signaling for the protection
of the multiplex section.
■ J0—Section trace. This byte is defined for STS-1 number 1 of an STS-N
signal. Used to transmit a 1-byte fixed-length string or a 16-byte message
so that a receiving terminal in a section can verify its continued connection
to the intended transmitter.
■ S1—Synchronization status. The S1 byte is located in the first STS-1 of
an STS-N.
■ Z3 and Z4—Allocated for future use.
SDH alarms SDH media-specific defects that can prevent the interface from passing packets. All levels
When a defect persists for a certain period, it is promoted to an alarm. Based
SDH defects on the router configuration, an alarm can ring the red or yellow alarm bell on
the router or light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.
SDH PHY Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SDH regenerator Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ RS-BIP8—24-bit BIP for multiplex section overhead (B2 bytes)
■ OOF—Out of frame
■ LOS—Loss of signal
■ LOF—Loss of frame
■ RS-ES—Errored seconds (near-end regenerator section)
■ RS-SES—Severely errored seconds (near-end regenerator section)
■ RS-SEFS—Severely errored framing seconds (regenerator section)
SDH multiplex Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ MS-BIP24—8-bit BIP for high-order path overhead (B3 byte)
■ MS-FEBE—Far-end block error (multiplex section)
■ MS-FERF—Far-end remote fail (multiplex section)
■ MS-AIS—Alarm indication signal (multiplex section)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ MS-ES—Errored seconds (near-end multiplex section)
■ MS-SES—Severely errored seconds (near-end multiplex section)
■ MS-UAS—Unavailable seconds (near-end multiplex section)
■ MS-ES-FE—Errored seconds (far-end multiplex section)
■ MS-SES-FE—Severely errored seconds (far-end multiplex section)
■ MS-UAS-FE—Unavailable seconds (far-end multiplex section)
SDH path Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ HP-BIP8—8-bit BIP for regenerator section overhead (B1 byte)
■ HP-FEBE—Far-end block error (high-order path)
■ HP-LOP—Loss of pointer (high-order path)
■ HP-AIS—High-order-path alarm indication signal
■ HP-FERF—Far-end remote fail (high-order path)
■ HP-UNEQ—Unequipped (high-order path)
■ HP-PLM—Payload label mismatch (high-order path)
■ HP-ES—Errored seconds (near-end high-order path)
■ HP-SES—Severely errored seconds (near-end high-order path)
■ HP-UAS—Unavailable seconds (near-end high-order path)
■ HP-ES-FE—Errored seconds (far-end high-order path)
■ HP-SES-FE—Severely errored seconds (far-end high-order path)
■ HP-UAS-FE—Unavailable seconds (far-end high-order path)
Received SDH Values of the received and transmitted SONET overhead: extensive
overhead
■ C2—Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
Transmitted SDH
overhead ■ F1—Section user channel byte. This byte is set aside for the purposes of
users.
■ K1 and K2—These bytes are allocated for APS signaling for the protection
of the multiplex section.
■ J0—Section trace. This byte is defined for STS-1 number 1 of an STS-N
signal. Used to transmit a 1-byte fixed-length string or a 16-byte message
so that a receiving terminal in a section can verify its continued connection
to the intended transmitter.
■ S1—Synchronization status. The S1 byte is located in the first STS-1 of
an STS-N.
■ Z3 and Z4—Allocated for future use.
Received path trace SONET/SDH interfaces allow path trace bytes to be sent inband across the extensive
SONET/SDH link. Juniper Networks and other router manufacturers use these
Transmitted path bytes to help diagnose misconfigurations and network errors by setting the
trace transmitted path trace message so that it contains the system hostname and
name of the physical interface. The received path trace value is the message
received from the router at the other end of the fiber. The transmitted path
trace value is the message that this router transmits.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—The queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority. Possible values are low and high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. detail extensive none
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Multilink bundle (If the logical interface is configured as part of a multilink bundle.) Interface detail extensive none
name for the multilink bundle.
AS bundle (If the logical interface is configured as part of an aggregated SONET bundle.) detail extensive
AS bundle number.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when the link is active, but no information is received from
the DCE.
■ Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ Dce-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface so-0/0/0.0 (Index 66) (SNMP ifIndex 43) (Generation 19)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 48, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.0/30, Local: 10.0.12.1, Broadcast: 10.0.12.3,
Generation: 48
Protocol iso, MTU: 4470, Generation: 49, Route table: 0
Flags: Protocol-Down
Protocol mpls, MTU: 4458, Generation: 50, Route table: 0
Flags: Protocol-Down, Is-Primary
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface so-0/0/0.0 (Index 66) (SNMP ifIndex 43) (Generation 19)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
PPP parameters:
PPP loopback clear timer: 3 sec
Protocol inet, MTU: 4470, Generation: 48, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.0/30, Local: 10.0.12.1, Broadcast: 10.0.12.3,
Generation: 48
Protocol iso, MTU: 4470, Generation: 49, Route table: 0
Flags: Protocol-Down
Protocol mpls, MTU: 4458, Generation: 50, Route table: 0
Flags: Protocol-Down, Is-Primary
MS-ES-FE 3
0 best-effort 18 18 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
0 best-effort 18 18 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
SEFS-S 108
SONET line:
BIP-B2 0 0
REI-L 0 0
RDI-L 1 1 OK
AIS-L 107 1 OK
BERR-SF 0 0 OK
BERR-SD 44 2 OK
ES-L 108
SES-L 108
UAS-L 97
ES-LFE 1
SES-LFE 1
UAS-LFE 0
SONET path:
BIP-B3 0 0
REI-P 0 0
LOP-P 1 1 OK
AIS-P 107 1 OK
RDI-P 1 1 OK
UNEQ-P 0 0 OK
PLM-P 1 1 OK
ES-P 108
SES-P 108
UAS-P 97
ES-PFE 1
SES-PFE 1
UAS-PFE 0
Received SONET overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0xcf, C2(cmp) : 0xcf, F2 : 0x00
Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0xcf, F2 : 0x00, Z3 : 0x00
Z4 : 0x00
Received path trace: R2 so-0/0/0
52 32 20 73 6f 2d 30 2f 30 2f 30 00 00 00 00 00 R2 so-0/0/0.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a ................
Transmitted path trace: R1 so-0/0/0
52 31 20 73 6f 2d 30 2f 30 2f 30 00 00 00 00 00 R1 so-0/0/0.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 147744000 95 0 low none
3 network-control 5 7776000 5 0 low none
Logical interface so-0/0/0.0 (Index 79) (SNMP ifIndex 43) (Generation 28)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 49, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.0.12.2, Local: 10.0.12.1, Broadcast: Unspecified,
Generation: 61
Protocol iso, MTU: 4470, Generation: 50, Route table: 0
Flags: None
Protocol mpls, MTU: 4450, Generation: 51, Route table: 0
DLCI 16
Flags: Down, DCE-Unconfigured
Total down time: 00:05:42 sec, Last down: 00:05:42 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1
0 best-effort 2 2 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface so-0/2/0.0 (Index 70) (SNMP ifIndex 47) (Generation 231)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet6, MTU: 4470, Generation: 433, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: abcd::a18:104/126, Local: abcd::a18:105,
Broadcast: Unspecified, Generation: 683
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::2a0:a5ff:fe56:52a,
Broadcast: Unspecified, Generation: 684
Additional Information 300-pin Multisource Agreement (MSA) optics, XENPAK MSA optics, and XFP optics
are supported. The 300-pin MSA tool kit polls the PIC and the XENPAK driver polls
the XENPAK transceiver in 1-second intervals for diagnostics data, alarms, and
warnings and stores them into memory. The alarms will not cause the links to go
down or the LEDs to change color or generate SNMP traps. Changes in alarm and
warning status will generate system log messages.
Thresholds that trigger a high alarm, low alarm, high warning, or low warning are
set by the transponder vendors. Generally, a high alarm or low alarm indicates that
the optics module is not operating properly. This information can be used to diagnose
why a PIC is not working.
Table 70: 300-Pin MSA Optics show interfaces diagnostics optics Output Fields
Laser bias current Magnitude of the laser bias power setting current, in milliamperes. This indicator is a software
equivalent to the LsBIASMON pin in hardware.
Laser output power Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm). This is a software
equivalent to the LsPOWMON pin in hardware.
Receiver signal average Average received optical power, in mW and dBm. This indicator is a software equivalent to the
optical power RxPOWMON pin in hardware. Average optical power is vendor-specific. For example:
Table 70: 300-Pin MSA Optics show interfaces diagnostics optics Output Fields (continued)
Modulator temperature (Opnext 300-pin MSA transponders only) Modulator temperature alarm: On or Off.
alarm
Tx multiplexer FIFO error Transmit multiplexer first in, first out (FIFO) error alarm: On or Off.
alarm
Tx loss of PLL lock Transmit loss of phase-locked loop (PLL) lock alarm: On or Off.
alarm
Rx loss of AC power (Opnext 300-pin MSA transponders only) Receive loss of AC power alarm: On or Off.
alarm
Rx loss of PLL lock Receive loss of phase-locked loop (PLL) lock alarm: On or Off.
alarm
Table 71 on page 355 lists the output fields for the show interfaces diagnostics optics
command when the router is operating with next-generation SONET/SDH SFP optics.
Output fields are listed in the approximate order in which they appear.
Table 71: 10-Gigabit Ethernet next-generation SONET/SDH SFP Optics show interfaces diagnostics optics
Output Fields
Laser bias current Magnitude of the laser bias power setting current, in milliamperes. The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm).
Module temperature Temperature of the XFP optics module, in Celsius and Fahrenheit.
Table 71: 10-Gigabit Ethernet next-generation SONET/SDH SFP Optics show interfaces diagnostics optics
Output Fields (continued)
Laser bias current high Laser bias power setting high alarm. Displays on or off.
alarm
Laser bias current low Laser bias power setting low alarm. Displays on or off.
alarm
Laser bias current high Laser bias power setting high warning. Displays on or off.
warning
Laser bias current low Laser bias power setting low warning. Displays on or off.
warning
Laser output power high Laser output power high alarm. Displays on or off.
alarm
Laser output power low Laser output power low alarm. Displays on or off.
alarm
Laser output power high Laser output power high warning. Displays on or off.
warning
Laser output power low Laser output power low warning. Displays on or off.
warning
Laser rx power high Receive laser power high alarm. Displays on or off.
alarm
Table 71: 10-Gigabit Ethernet next-generation SONET/SDH SFP Optics show interfaces diagnostics optics
Output Fields (continued)
Laser rx power low Receive laser power low alarm. Displays on or off.
alarm
Laser rx power high Receive laser power high warning. Displays on or off.
warning
Laser rx power low Receive laser power low warning. Displays on or off.
warning
Laser bias current high Vendor-specified threshold for the laser bias current high alarm: 80.000 mA.
alarm threshold
Laser bias current low Vendor-specified threshold for the laser bias current low alarm: 2.000 mA.
alarm threshold
Laser bias current high Vendor-specified threshold for the laser bias current high warning: 70.000 mA.
warning threshold
Laser bias current low Vendor-specified threshold for the laser bias current low warning: 4.000 mA.
warning threshold
Laser output power high Vendor-specified threshold for the laser output power high alarm: 1.2600 mW or 1.00 dBm.
alarm threshold
Laser output power low Vendor-specified threshold for the laser output power low alarm: 0.0440 mW or -13.57 dBm.
alarm threshold
Laser output power high Vendor-specified threshold for the laser output power high warning: 0.7950 mW or -1.00 dBm.
warning threshold
Laser output power low Vendor-specified threshold for the laser output power low warning: 0.0700 mW or -11.55 dBm.
warning threshold
Module temperature Vendor-specified threshold for the module temperature high alarm: 110° C or 230° F.
high alarm threshold
Module temperature low Vendor-specified threshold for the module temperature low alarm: -40° C or -40° F.
alarm threshold
Module temperature Vendor-specified threshold for the module temperature high warning: 93° C or 199° F.
high warning threshold
Module temperature low Vendor-specified threshold for the module temperature low warning: -30° C or -22° F.
warning threshold
Table 71: 10-Gigabit Ethernet next-generation SONET/SDH SFP Optics show interfaces diagnostics optics
Output Fields (continued)
Laser rx power high Vendor-specified threshold for the laser Rx power high alarm: 1.1749 mW or 0.70 dBm.
alarm threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low alarm: 0.0039 mW or -24.09 dBm.
alarm threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high warning: 0.7942 mW or 1.00 dBm.
warning threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low warning: 0.0100 mW or -20.00 dBm.
warning threshold
Table 72 on page 358 lists the output fields for the show interfaces diagnostics optics
command generated from XENPAK MSA optics.
Table 72: XENPAK MSA Optics show interfaces diagnostics optics Output Fields
Laser bias current high Laser bias current high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser bias current low Laser bias current low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser output power high Laser output power high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser output power low Laser output power low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Module temp high alarm Module temperature high alarm: On or Off. Alarm ranges are vendor-specific.
Module temp low alarm Module temperature low alarm: On or Off. Alarm ranges are vendor-specific.
Laser rx power high Laser receive power high alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Table 72: XENPAK MSA Optics show interfaces diagnostics optics Output Fields (continued)
Laser rx power low Laser receive power low alarm: On or Off. Alarm ranges are vendor-specific.
alarm
Laser bias current high Laser bias current high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser bias current low Laser bias current low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser output power high Laser output power high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser output power low Laser output power low warning: On or Off. Warning ranges are vendor-specific.
warning
Module temp high Module temperature high warning: On or Off. Warning ranges are vendor-specific.
warning
Module temp low Module temperature low warning: On or Off. Warning ranges are vendor-specific.
warning
Laser rx power high Laser receive power high warning: On or Off. Warning ranges are vendor-specific.
warning
Laser rx power low Laser receive power low warning: On or Off. Warning ranges are vendor-specific.
warning
Table 73 on page 359 lists the output fields for the show interfaces diagnostics optics
command when the router is operating with XFP optics. Output fields are listed in
the approximate order in which they appear.
Table 73: XFP Optics show interfaces diagnostics optics Output Fields
Link (For 4-port OC-192c PIC is operating in OC768-over-4xOC192 mode) The link number. Diagnostics
and alarms are displayed for each link.
Laser bias current Magnitude of the laser bias power setting current, in milliamperes. The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm). This is a software
equivalent to the LsPOWMON pin in hardware.
Module temperature Temperature of the XFP optics module, in Celsius and Fahrenheit.
Table 73: XFP Optics show interfaces diagnostics optics Output Fields (continued)
Laser bias current high Laser bias power setting high alarm. Displays on or off.
alarm
Laser bias current low Laser bias power setting low alarm. Displays on or off.
alarm
Laser bias current high Laser bias power setting high warning. Displays on or off.
warning
Laser bias current low Laser bias power setting low warning. Displays on or off.
warning
Laser output power high Laser output power high alarm. Displays on or off.
alarm
Laser output power low Laser output power low alarm. Displays on or off.
alarm
Laser output power high Laser output power high warning. Displays on or off.
warning
Laser output power low Laser output power low warning. Displays on or off.
warning
Laser rx power high Receive laser power high alarm. Displays on or off.
alarm
Laser rx power low Receive laser power low alarm. Displays on or off.
alarm
Laser rx power high Receive laser power high warning. Displays on or off.
warning
Laser rx power low Receive laser power low warning. Displays on or off.
warning
Module not ready alarm Module not ready alarm. When on, indicates the module has an operational fault. Displays on or off.
Module power down Module power down alarm. When on, module is in a limited power mode, low for normal operation.
alarm Displays on or off.
Tx data not ready alarm Any condition leading to invalid data on the transmit path. Displays on or off.
Table 73: XFP Optics show interfaces diagnostics optics Output Fields (continued)
Tx not ready alarm Any condition leading to invalid data on the transmit path. Displays on or off.
Tx CDR loss of lock Transmit clock and data recovery (CDR) loss of lock. Loss of lock on the transmit side of the CDR.
alarm Displays on or off.
Rx not ready alarm Any condition leading to invalid data on the receive path. Displays on or off.
Rx loss of signal alarm Receive Loss of Signal alarm. When on, indicates insufficient optical input power to the module.
Displays on or off.
Rx CDR loss of lock Receive CDR loss of lock. Loss of lock on the receive side of the CDR. Displays on or off.
alarm
Laser bias current high Vendor-specified threshold for the laser bias current high alarm: 130.000 mA.
alarm threshold
Laser bias current low Vendor-specified threshold for the laser bias current low alarm: 10.000 mA.
alarm threshold
Laser bias current high Vendor-specified threshold for the laser bias current high warning: 120.000 mA.
warning threshold
Laser bias current low Vendor-specified threshold for the laser bias current low warning: 12.000 mA.
warning threshold
Laser output power high Vendor-specified threshold for the laser output power high alarm: 0.8910 mW or -0.50 dBm.
alarm threshold
Laser output power low Vendor-specified threshold for the laser output power low alarm: 0.2230 mW or -6.52 dBm.
alarm threshold
Laser output power high Vendor-specified threshold for the laser output power high warning: 0.7940 mW or -100 dBm.
warning threshold
Laser output power low Vendor-specified threshold for the laser output power low warning: 0.2510 mW or -600dBm.
warning threshold
Module temperature Vendor-specified threshold for the module temperature high alarm: 90 C or 194 F.
high alarm threshold
Module temperature low Vendor-specified threshold for the module temperature low alarm: -5 C or 23 F.
alarm threshold
Module temperature Vendor-specified threshold for the module temperature high warning: 85 C or 185 F.
high warning threshold
Module temperature low Vendor-specified threshold for the module temperature low warning: 0 C or 32 F.
warning threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high alarm: 1.2589 mW or 1.00 dBm.
alarm threshold
Table 73: XFP Optics show interfaces diagnostics optics Output Fields (continued)
Laser rx power low Vendor-specified threshold for the laser Rx power low alarm: 0.0323 mW or -14.91 dBm.
alarm threshold
Laser rx power high Vendor-specified threshold for the laser Rx power high warning: 1.1220 mW or 0.50 dBm.
warning threshold
Laser rx power low Vendor-specified threshold for the laser Rx power low warning: 0.0363 mW or -14.40 dBm.
warning threshold
Table 74 on page 367 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot Asynchronous Transfer Mode (ATM) interfaces
on M-series and T-series routing platforms, and ATM-over-asymmetrical digital
subscriber line (ADSL) and ATM-over-symmetric high-speed digital subscriber line
(SHDSL) interfaces on the J-series routing platform. An ATM-over-ADSL interface and
an ATM-over-SHDSL interface is configured over an underlying ATM interface.
Task Command
Display status information about ATM interfaces. show interfaces (ATM) on page 368
NOTE: For information about monitoring and troubleshooting PPPoE interfaces (pp0),
which are used in conjunction with ATM-over-ADSL interfaces, see “PPPoE Interface
Operational Mode Commands” on page 277 For more information about monitoring
and troubleshooting ATM interfaces, see “Investigate ATM Interfaces” in the JUNOS
Interfaces Network Operations Guide.
■ 367
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface: All levels
■ ATM-CCC-CELL-RELAY—ATM cell relay for CCC.
■ ATM-CCC-VC-MUX—ATM virtual circuit (VC) for CCC.
■ ATM-CISCO-NLPID—Cisco-compatible ATM NLPID encapsulation.
■ ATM-MIPP-LLC—ATM MLPPP over ATM Adaptation Layer 5 (AAL5)/logical
link control (LLC).
■ ATM-NLPID—ATM NLPID encapsulation.
■ ATM-PPP-LLC—ATM PPP over AAL5/LLC.
■ ATM-PPP-VC-MUX—ATM PPP over raw AAL5.
■ ATM-PVC—ATM permanent virtual circuits.
■ ATM-SNAP—ATM LLC/SNAP encapsulation.
■ ATM-TCC-SNAP—ATM LLC/SNAP for translational cross-connection.
■ ATM-TCC-VC-MUX—ATM VC for translational cross-connection.
■ ATM-VC-MUX—ATM VC multiplexing.
■ ETHER-OVER-ATM-LLC—Ethernet over ATM (LLC/SNAP) encapsulation.
■ ETHER-VPLS-OVER-ATM-LLC—Ethernet VPLS over ATM (bridging)
encapsulation.
Speed Speed at which the interface is running as represented by the interface type All levels
(for example, OC3, ADSL2+, and SHDSL(2-wire).
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Current address Ethernet MAC address for this interface for Ethernet over ATM encapsulation. detail extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and frame check sequence
(FCS) errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's random early detection (RED)
mechanism.
■ Invalid VCs—Number of cells that arrived for a nonexistent VC.
■ Framing errors—Sum of AAL5 packets that have FCS errors, reassembly
timeout errors, and length errors.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly, increasing only when the cable is unplugged, the
far-end system is powered down and then up, or another problem occurs.
If it increments quickly (perhaps once every 10 seconds), the cable, the
far-end system, or the PIC or PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
SONET alarms SONET media-specific defects that prevent the interface from passing packets. detail extensive none
When a defect persists for a certain period, it is promoted to an alarm. Based
SONET defects on the router configuration, an alarm can ring the red or yellow alarm bell on
the router or light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SONET PHY, SONET section, SONET line,
and SONET path.
SONET PHY Counts of specific SONET errors with detailed information. extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SONET section Counts of specific SONET errors with detailed information. extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B1—Bit interleaved parity for SONET section overhead
■ SEF—Severely errored framing
■ LOL—Loss of light
■ LOF—Loss of frame
■ ES-S—Errored seconds (section)
■ SES-S—Severely errored seconds (section)
■ SEFS-S—Severely errored framing seconds (section)
SONET line Active alarms and defects, plus counts of specific SONET errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B2—Bit interleaved parity for SONET line overhead
■ REI-L—Remote error indication (near-end line)
■ RDI-L—Remote defect indication (near-end line)
■ AIS-L—Alarm indication signal (near-end line)
■ BERR-SF—Bit error rate fault signal failure
■ BERR-SD—Bit error rate defect signal degradation
■ ES-L—Errored seconds (near-end line)
■ SES-L—Severely errored seconds (near-end line)
■ UAS-L—Unavailable seconds (near-end line)
■ ES-LFE—Errored seconds (far-end line)
■ SES-LFE—Severely errored seconds (far-end line)
■ UAS-LFE—Unavailable seconds (far-end line)
SONET path Active alarms and defects, plus counts of specific SONET errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B3—Bit interleaved parity for SONET section overhead
■ REI-P—Remote error indication
■ LOP-P—Loss of pointer (path)
■ AIS-P—Path alarm indication signal
■ RDI-P—Path remote defect indication
■ UNEQ-P—Path unequipped
■ PLM-P—Path payload label mismatch
■ ES-P—Errored seconds (near-end STS path)
■ SES-P—Severely errored seconds (near-end STS path)
■ UAS-P—Unavailable seconds (near-end STS path)
■ ES-PFE—Errored seconds (far-end STS path)
■ SES-PFE—Severely errored seconds (far-end STS path)
■ UAS-PFE—Unavailable seconds (far-end STS path)
Received SONET Values of the received and transmitted SONET overhead: extensive
overhead
■ C2—Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
Transmitted SONET
overhead ■ F1—Section user channel byte. This byte is set aside for the purposes of
users.
■ K1 and K2—These bytes are allocated for APS signaling for the protection
of the multiplex section.
■ J0—Section trace. This byte is defined for STS-1 number 1of an STS-N
signal. Used to transmit a 1-byte fixed-length string or a 16-byte message
so that a receiving terminal in a section can verify its continued connection
to the intended transmitter.
■ S1—Synchronization status. The S1 byte is located in the first STS-1 of
an STS-N.
■ Z3 and Z4—Allocated for future use.
SDH alarms SDH media-specific defects that can prevent the interface from passing packets. All levels
When a defect persists for a certain period, it is promoted to an alarm. Based
SDH defects on the router configuration, an alarm can ring the red or yellow alarm bell on
the router or light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.
SDH PHY Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SDH regenerator Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ RS-BIP8—24-bit BIP for multiplex section overhead (B2 bytes)
■ OOF—Out of frame
■ LOS—Loss of signal
■ LOF—Loss of frame
■ RS-ES—Errored seconds (near-end regenerator section)
■ RS-SES—Severely errored seconds (near-end regenerator section)
■ RS-SEFS—Severely errored framing seconds (regenerator section)
SDH multiplex Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ MS-BIP24—8-bit BIP for high-order path overhead (B3 byte)
■ MS-FEBE—Far-end block error (multiplex section)
■ MS-FERF—Far-end remote fail (multiplex section)
■ MS-AIS—alarm indication signal (multiplex section)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ MS-ES—Errored seconds (near-end multiplex section)
■ MS-SES—Severely errored seconds (near-end multiplex section)
■ MS-UAS—Unavailable seconds (near-end multiplex section)
■ MS-ES-FE—Errored seconds (far-end multiplex section)
■ MS-SES-FE—Severely errored seconds (far-end multiplex section)
■ MS-UAS-FE—Unavailable seconds (far-end multiplex section)
SDH path Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ HP-BIP8—8-bit BIP for regenerator section overhead (B1 byte)
■ HP-FEBE—Far-end block error (high-order path)
■ HP-LOP—Loss of pointer (high-order path)
■ HP-AIS—High-order-path alarm indication signal
■ HP-FERF—Far-end remote fail (high-order path)
■ HP-UNEQ—Unequipped (high-order path)
■ HP-PLM—Payload label mismatch (high-order path)
■ HP-ES—Errored seconds (near-end high-order path)
■ HP-SES—Severely errored seconds (near-end high-order path)
■ HP-UAS—Unavailable seconds (near-end high-order path)
■ HP-ES-FE—Errored seconds (far-end high-order path)
■ HP-SES-FE—Severely errored seconds (far-end high-order path)
■ HP-UAS-FE—Unavailable seconds (far-end high-order path)
Received SDH Values of the received and transmitted SONET overhead: extensive
overhead
■ C2—Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
Transmitted SDH
overhead ■ F1—Section user channel byte. This byte is set aside for the purposes of
users.
■ K1 and K2—These bytes are allocated for APS signaling for the protection
of the multiplex section.
■ J0—Section trace. This byte is defined for STS-1 number 1of an STS-N
signal. Used to transmit a 1-byte fixed-length string or a 16-byte message
so that a receiving terminal in a section can verify its continued connection
to the intended transmitter.
■ S1—Synchronization status. The S1 byte is located in the first STS-1 of
an STS-N.
■ Z3 and Z4—Allocated for future use.
Received path trace SONET/SDH interfaces allow path trace bytes to be sent inband across the extensive
SONET/SDH link. Juniper Networks and other router manufacturers use these
Transmitted path bytes to help diagnose misconfigurations and network errors by setting the
trace transmitted path trace message so that it contains the system hostname and
name of the physical interface. The received path trace value is the message
received from the router at the other end of the fiber. The transmitted path
trace value is the message that this router transmits.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue. The default
is 25 percent.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer%.—Percentage of buffer space allocated to the queue. The default
is 25 percent.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is configured
in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue:
■ exact—The queue transmits only up to the configured bandwidth,
even if excess bandwidth is available.
■ none—The queue transmits beyond the configured bandwidth if
bandwidth is available.
Traffic statistics:
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Protocol Protocol family configured on the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
VCI (continued) ■ Transmit weight cells—(ATM2 only) Amount of bandwidth assigned to this All levels
queue.
■ ATM per-VC transmit statistics:
■ Tail queue packet drops—Number of packets dropped because of
bandwidth constraints. Indicates that packets are queued to send out
at a rate faster than allowed.
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.220.24/30, Local: 192.168.220.26,
Broadcast: 192.168.220.27
Protocol iso, MTU: 4470
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Resource errors: 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
LOC : OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,
Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,
Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 1
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 147744000 95 0 low none
3 network-control 5 7776000 5 0 low none
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface at-0/2/1.0 (Index 75) (SNMP ifIndex 51) (Generation 25)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 62, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.6, Local: 10.0.12.5, Broadcast: Unspecified,
Generation: 58
Protocol iso, MTU: 4470, Generation: 63, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Logical interface at-0/2/1.32767 (Index 76) (SNMP ifIndex 50) (Generation 26)
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Resource errors: 0
Egress queues: 4 supported, 4 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface at-0/2/1.0 (Index 75) (SNMP ifIndex 51) (Generation 25)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 62, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.6, Local: 10.0.12.5, Broadcast: Unspecified,
Generation: 58
Protocol iso, MTU: 4470, Generation: 63, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Logical interface at-0/2/1.32767 (Index 76) (SNMP ifIndex 50) (Generation 26)
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.59.5, Local: 10.0.59.6
Protocol iso, MTU: 4470
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10
Input packets : 0
Output packets: 0
0 best-effort 44 44 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 6 6 0
Output packets: 0
Logical interface at-0/3/1.0 (Index 78) (SNMP ifIndex 77) (Generation 20)
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 38, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.59.5, Local: 10.0.59.6, Broadcast: Unspecified,
Generation: 44
Protocol iso, MTU: 4470, Generation: 39, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Logical interface at-0/3/1.32767 (Index 79) (SNMP ifIndex 76) (Generation 21)
Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes : 360
Output bytes : 3302
Input packets: 6
Output packets: 50
Local statistics:
Input bytes : 360
Output bytes : 3302
Input packets: 6
Output packets: 50
VCI 0.16
Flags: Active, ILMI
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 2640
Input packets: 0
Output packets: 44
VCI 0.4
Flags: Active, OAM
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 312
Output bytes : 312
Input packets: 6
Output packets: 6
OAM F4 cell statistics:
Total received: 6, Total sent: 6
Loopback received: 6, Loopback sent: 6
Last received: 00:00:29, Last sent: 00:00:29
RDI received: 0, RDI sent: 0
AIS received: 0, AIS sent: 0
Resource errors: 0
Egress queues: 4 supported, 4 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 62 62 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 10 10 0
PHY Light 0 0 OK
SONET section:
BIP-B1 0 0
SEF 0 0 OK
LOS 0 0 OK
LOF 0 0 OK
ES-S 0
SES-S 0
SEFS-S 0
SONET line:
BIP-B2 0 0
REI-L 0 0
RDI-L 0 0 OK
AIS-L 0 0 OK
BERR-SF 0 0 OK
BERR-SD 0 0 OK
ES-L 0
SES-L 0
UAS-L 0
ES-LFE 0
SES-LFE 0
UAS-LFE 0
SONET path:
BIP-B3 0 0
REI-P 0 0
LOP-P 0 0 OK
AIS-P 0 0 OK
RDI-P 0 0 OK
UNEQ-P 1 1 OK
PLM-P 0 0 OK
ES-P 1
SES-P 1
UAS-P 0
ES-PFE 0
SES-PFE 0
UAS-PFE 0
Received SONET overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x13, C2(cmp) : 0x13, F2 : 0x00
Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x13, F2 : 0x00, Z3 : 0x00
Z4 : 0x00
ATM status:
HCS state: Sync
LOC : OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,
Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,
Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 0
VPI 0
Flags: Active, OAM, Shaping
CBR, Peak: 50kbps
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
Logical interface at-0/3/1.0 (Index 78) (SNMP ifIndex 77) (Generation 20)
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 38, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.59.5, Local: 10.0.59.6, Broadcast: Unspecified,
Generation: 44
Protocol iso, MTU: 4470, Generation: 39, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Logical interface at-0/3/1.32767 (Index 79) (SNMP ifIndex 76) (Generation 21)
Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:
Physical Interface
ADSL alarms Number and type of ADSL alarms. See “ADSL media” for details. detail extensive none
ADSL defects Number and type of ADSL defects. See “ADSL media” for details. detail extensive none
ADSL status Operational information for ATM-over-ADSL interfaces. detail extensive none
■ Modem status—Status of the modem: Down, Training, or Showtime.
■ DSL mode—Configured line type of the digital subscriber line: adsl2plus,
ansi-dmt, auto, itu-dmt, or itu-dmt-bis.
■ Last fail code—Reason for failure: ATU-C not detected, incompatible line
condition, protocol error, message error, spurious ATU detected, forced
silence, unselectable operation mode, or none.
■ Subfunction—Specified analog front-end chip and discrete front.
■ Seconds in showtime—Number of seconds the ADSL connection is in
showtime.
ADSL media Information about ADSL media-specific defects that can prevent the interface extensive
from passing packets. The following information is displayed for each defect:
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. A state other than OK indicates a problem.
ADSL Statistics Information about the ADSL terminal unit-remote (ATU-R) at the far end of the detail extensive
connection and the ADSL terminal unit-central office (ATU-C) at the near end:
■ Attenuation (dB)—Attenuation in decibels.
■ Capacity used (%)—Percentage of capacity used.
■ Noise margin (dB)—Maximum extraneous signal allowed without causing
the output to deviate from an allowable level, in decibels.
■ Output power (dBm)—Amount of power used by the ATM-over-ADSL
interface.
■ Bit rate (kbps)—Speed of data transfer on the ATM-over-ADSL interface,
in kilobits per second.
■ CRC—Number of cyclic redundancy check errors.
■ FEC—Number of forward error corrections.
■ HEC—Number of header error checksums.
■ Received cells—Number of cells received through the interface.
■ Transmitted cells—Number of cells sent through the interface.
Flags: Active
Total down time: 0 sec, Last down: Never
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
4 be-class 0 0 0
5 ef-class 0 0 0
6 af-class 0 0 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 1500, Generation: 12, Route table: 0
Flags: None
VCI 0.128
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
4 be-class 0 0 0
5 ef-class 0 0 0
6 af-class 0 0 0
LOC : OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,
Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,
Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 5
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 7600000 95 0 low none
3 network-control 5 400000 5 0 low none
SHDSL alarms Number and type of SHDSL alarms. See "SHDSL media" for details. detail extensive none
SHDSL defects Number and type of SHDSL defects. See "SHDSL media" for details. detail extensive none
SHDSL media Information about the SHDSL media-specific defects that can prevent the extensive
interface from passing packets. The following information is displayed for each
defect:
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. A state other than OK indicates a problem.
SHDSL status Operational information for ATM-over-SHDSL interfaces. detail extensive none
■ Line termination—SHDLS transceiver unit- remote (STU-R) (Only customer
premises equipment is supported.)
■ Annex—Either Annex A or Annex B. Annex A is supported in North
America, and Annex B is supported in Europe.
■ Line mode—SHDSL mode configured on the G.SHDLS Physical Interface
Module (PIM), either 2-wire or 4-wire.
■ Modem status—Data.
■ Bit rate (kbps)—Speed of data transfer on the ATM-over-G.SHDSL interface,
in kilobits per second.
■ Last fail mode—Code for the last interface failure.
■ Framer mode—Framer mode of the underlying interface: ATM.
■ Dying gasp —Ability of a J-series router that has lost power to send a
message informing the attached DSL access multiplexer (DSLAM) that it
is about to go offline: Enabled or Disabled.
■ Framer sync status—Framer synchronization status: In sync or Out of sync
(OOS).
■ Chipset version—Version number of the chipset on the interface.
■ Firmware version—Version number of the firmware on the interface.
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
Logical interface at-4/0/0.32767 (Index 69) (SNMP ifIndex 43)
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Table 78 on page 417 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot Integrated Local Management Interface (ILMI)
operations on ATM1 and ATM2 intelligent queuing (IQ) interfaces. Commands are
listed in alphabetical order.
Task Command
Clear (set to zero) ILMI statistics. clear ilmi statistics on page 418
■ 417
JUNOS 9.0 Interfaces Command Reference
show ilmi
all | interface interface-name—(Optional) Display IP addresses and port names for all
ILMI-enabled ATM devices or for a particular device.
Field
Name Field Description
Field
Name Field Description
Table 81 on page 425 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot Integrated Services Digital Network (ISDN)
interfaces. Commands are listed in alphabetical order.
Task Command
Clear ISDN Q.921 statistics. clear isdn q921 statistics on page 427
Clear ISDN Q.931 statistics. clear isdn q931 statistics on page 428
Display ISDN services default software values. show dialer defaults on page 429
Display ISDN dialer interface information. show dialer interfaces on page 431
Display ISDN dialer pool information. show dialer pools on page 433
Display ISDN B-channel interface information. show interfaces (ISDN B-Channel) on page 435
Display ISDN Basic Rate Interface (BRI) information. show interfaces (ISDN BRI) on page 441
Display ISDN D-channel interface information. show interfaces (ISDN D-channel) on page 445
Display ISDN dialer interface information. show interfaces (ISDN Dialer) on page 451
Display Layer 2 ISDN status and statistics. show isdn q921 statistics on page 462
Display Layer 3 ISDN status and statistics. show isdn q931 statistics on page 464
■ 425
JUNOS 9.0 Interfaces Command Reference
NOTE: ISDN is supported on the J-series routing platform only. J-series Services
Routers can be configured to "fail over" to an ISDN interface when the primary
connection experiences interruptions in Internet connectivity. The following interfaces
support ISDN backup connectivity: E1, E3, Fast Ethernet, generic routing encapsulation
(GRE), Point-to-Point Protocol over Ethernet (PPPoE), serial, T1, and T3. For
information about how to configure ISDN interfaces, see the J-series Services Router
Basic LAN and WAN Access Configuration Guide or the JUNOS Network Interfaces
Configuration Guide.
426 ■
Chapter 14: ISDN Interface Operational Mode Commands
Options none—Clear ISDN Q.921 statistics for all Basic Rate Interface (BRI) interfaces.
br-pim/0/port— (Optional) Clear ISDN Q.921 statistics for the specified BRI interface
only.
Options none—Clear ISDN Q.931 statistics for all Basic Rate Interface (BRI) interfaces.
br-pim/0/port—(Optional) Clear ISDN Q.931 statistics for the specified BRI interface
only.
Idle timeout Length of time (in seconds) that a connection can be idle before
disconnecting.
Activation delay Length of time (in seconds) to wait before enabling the interface
after the primary interface has failed.
Deactivation delay Length of time (in seconds) to wait before disabling the interface
after the primary interface is operational.
Dialer watch initial route Length of time (in seconds) before a route is checked for status.
check time
Dialer load threshold Bandwidth threshold percentage used for adding interfaces. Another
link is added to the multilink bundle when the bandwidth reaches
the threshold value you set. The range of values is 0 through 100.
When the value is set to 0, all available channels are dialed. The
default value is 100.
Dialer load interval Interval used to calculate the average load on the network. The
range of values, in seconds, is 20 through 180, configurable in
intervals of 10 seconds. The default value is 60.
Dialer redial delay Delay, in seconds, between two successive calls made by the dialer
(for dialout). The default value is 3 seconds.
Dialer callback wait period For interfaces configured for ISDN with callback, the amount of
time the dialer waits before calling back the caller. The default value
is 5 seconds.
Options none—(Same as detail) Display detailed information about all ISDN dialer interfaces.
Dial strings Dialing number for the ISDN connection. detail none
Subordinate Associated B-channel or USB modem interface name and SNMP index number. All levels
interfaces
Activation delay Length of time (in seconds) to wait before enabling the interface after the detail none
primary interface has failed.
Deactivation delay Length of time (in seconds) to wait before disabling the interface after the detail none
primary interface is operational.
Initial route check Wait period (in seconds) for the software to check if the primary interface is detail none
delay up after the router comes up. The range is from 1 through 300 seconds. The
default is 120 seconds.
Redial delay (Available on interfaces configured for ISDN dial-out.) Delay, in seconds, detail none
between two successive calls made. The range is from 2 to 255. The default
value is 3.
Callback wait period Time, in seconds, that the dialer waits before it calls back the caller ID. The detail none
default value is 5.
Load threshold Bandwidth threshold percentage used for adding interfaces. Another link is detail none
added to the multilink bundle when the load reaches the threshold value you
set. The range of values is from 0 to 100. The default value is 100.
Load interval Interval used to calculate the average load on the network. By default, the detail none
average interface load is calculated every 60 seconds.
show dialer interfaces The output for the show dialer interfaces detail command is identical to that for
detail the show dialer interfaces command. For sample output, see show dialer
interfaces on page 432.
Options none—(Same as detail) Display detailed information about all ISDN dialer pools.
Dialer Interfaces
Name Name of configured dialer interfaces. All levels
Subordinate Interfaces
Name Name of each physical ISDN interface configured as part of the dialer interface. All levels
show dialer pools detail The output for the show dialer pools detail command is identical to that for the show
dialer pools command. For sample output, see show dialer pools on page 434.
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
MTU Maximum transmission unit (MTU)—Size of the largest packet to be transmitted. All levels
Parent Name and interface index of the interface to which a particular child interface detail extensive none
belongs. None indicates that this is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link detail extensive
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Current address Configured media access control (MAC) address. detail extensive
CoS queues Number of class-of-service (CoS) queues configured. detail extensive none
Last flapped Date, time, and length of time since the interface changed its status from down detail extensive none
to up.
Input rate Input rate in bits per second (bps) and packets per second (pps). none specified
Statistics last Time when the interface statistics were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the logical detail extensive
and physical interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface (which reflects its initialization sequence). detail extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
0 best-effort 13 13 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface bc-4/0/0:1.0 (Index 74) (SNMP ifIndex 79) (Generation 140)
Flags: Point-To-Point SNMP-Traps Encapsulation: 64
0 best-effort 13 13 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Options br-pim/0/port—Display standard information about the specified ISDN BRI interface.
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number that reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. All levels
MTU Maximum transmission unit (MTU)—Size of the largest packet to be transmitted. All levels
Parent Name and interface index of the interface to which a particular child interface detail extensive none
belongs. None indicates that this is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link detail extensive none
Flags” on page 81.
Physical info Information about the physical interface. detail extensive none
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Hardware address Media access control (MAC) address of the interface. detail extensive
Last flapped Date, time, and length of time since the interface changed its status from down detail extensive none
to up.
Input rate Input rate in bits per second (bps) and packets per second (pps). none specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the logical detail extensive
and physical interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Output errors ■ Carrier transitions —Number of times the interface has gone from down extensive
to up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Physical Interface
Physical Interface Name of the physical interface type. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number that reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. All levels
MTU Maximum transmission unit—Size of the largest packet to be transmitted. All levels
Parent Name and interface index of the interface to which a particular child interface detail extensive none
belongs. None indicates that this is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link detail extensive none
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Last flapped Date, time, and length of time since the interface changed its status from down detail extensive none
to up.
Input rate Input rate in bits per second (bps) and packets per second (pps). none specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Output errors ■ Carrier transitions —Number of times the interface has gone from down extensive
to up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC Red mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface (which reflects its initialization sequence). detail extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the logical interface.
■ Output packets—Number of packets transmitted on the logical interface
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Logical interface dc-4/0/0.32767 (Index 73) (SNMP ifIndex 74) (Generation 139)
Output errors:
Carrier transitions: 5, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
ISDN alarms : None
ISDN media: Seconds Count State
LOF 1874 2 0K
LOS 1874 2 0K
Logical interface dc-4/0/0.32767 (Index 73) (SNMP ifIndex 74) (Generation 139)
Options dlnumber—Display standard information about the specified ISDN dialer interface.
Physical Interface
Physical Interface Name of the physical interface type. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number that reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Type of encapsulation configured on the physical interface. All levels
MTU Maximum transmission unit (MTU)—Size of the largest transmitted packet. All levels
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Last flapped Date, time, and length of time since the interface status changed from down detail extensive none
to up.
Input rate Input rate in bits per second (bps) and packets per second (pps). none specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface (which reflects its initialization sequence). detail extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Dialer Information about the status and configuration of the dialer interface: All levels
■ State—State of the interface: Active or Inactive.
■ Dial pool—Dial pool name.
■ Dial strings—Dialing number for the ISDN connection.
■ Subordinate interfaces—Associated B-channel interface name and SNMP
index number.
■ Activation delay—Length of time (in seconds) to wait before enabling the
interface after the primary interface has failed.
■ Deactivation delay—Length of time (in seconds) to wait before disabling
the interface after the primary interface is operational.
■ Initial route check delay—Wait period (in seconds) for the software to check
if the primary interface is up after the router comes up. The range is from
1 through 300 seconds. The default is 120 seconds.
■ Redial delay—(Available on interfaces configured for ISDN dial-out.) Delay,
in seconds, between two successive calls made. The range of values is 2
to 255. The default value is 3.
■ Callback wait period—Time, in seconds, that the dialer waits before it calls
back the caller ID. The default value is 5.
■ Load threshold—Bandwidth threshold percentage used for adding
interfaces. Another link is added to the multilink bundle when the load
reaches the threshold value you set. The range of values is 0 to 100. The
default value is 100.
■ Load interval—Interval used to calculate the average load on the network.
By default, the average interface load is calculated every 60 seconds.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the logical interface.
■ Output packets—Number of packets transmitted on the logical interface
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
This counter normally stabilizes in less than 1 second.
Keepalive statistics Information about keepalive packets. (When no level of output is specified, the detail extensive none
word statistics is not part of the field name and the last seen text is not
displayed.)
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
received, in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
CHAP state Displays the state of the Challenge Handshake Authentication Protocol (CHAP) detail extensive none
during its transaction.
■ Chap-Resp-received—Response received for the challenge sent, but CHAP
not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response sent for the challenge received.
■ Chap-Chal-sent—Challenge sent.
■ Chap-Chal-received—Challenge received but response not yet sent.
■ Down—CHAP authentication is incomplete (not yet completed or has
failed).
■ Not-configured—CHAP is not configured on the interface.
■ Opened—CHAP authentication was successful.
protocol family Protocol family configured on the logical interface. If the family is inet, the IP brief
address of the logical interface and the IP address on the remote side of the
connection are included.
Protocol Protocol family configured on the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Logical interface dl0.0 (Index 76) (SNMP ifIndex 78) (Generation 142)
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 10
Dial strings: 5551212
Subordinate interfaces: bc-4/0/0:1 (Index 151)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 64kbps
Traffic statistics:
Input bytes : 1092
Output bytes : 131459
Input packets: 13
Output packets: 10848
Local statistics:
Input bytes : 1092
Output bytes : 131459
Input packets: 13
Output packets: 10848
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 5413 (last seen 00:00:03 ago)
Output: 5417 (last sent 00:00:02 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.40.1, Local: 10.0.40.2, Broadcast: Unspecified,
Generation: 142
Logical interface dl0.0 (Index 76) (SNMP ifIndex 78) (Generation 142)
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 10
Dial strings: 5551212
Subordinate interfaces: bc-4/0/0:1 (Index 151)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 64kbps
Traffic statistics:
Input bytes : 1092
Output bytes : 131459
Input packets: 13
Output packets: 10848
Local statistics:
Input bytes : 1092
Output bytes : 131459
Input packets: 13
Output packets: 10848
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 5413 (last seen 00:00:07 ago)
Output: 5417 (last sent 00:00:06 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.40.1, Local: 10.0.40.2, Broadcast: Unspecified,
Generation: 142
Call Direction Indicates whether the call is a Dialout call, Dialincall, or Callback
call.
Duration Length of time (in seconds) that the ISDN call is connected.
Direction Indicates whether the call is a Dialout call, Dialin call, or Callback
call.
RNR 0 0
REJ 0 0
SABME 1 0
DISC 0 0
UA 0 1
DM 0 0
FRMR 0 0
XID 0 0
UI 1 1
Options none—Display standard ISDN status information for all Basic Rate Interface (BRI)
interfaces.
Table 94 on page 471 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot channelized E1 interfaces. Commands are listed
in alphabetical order.
Task Command
Display the interface names of the physical show interfaces controller (Channelized
channelized E1 IQ interface and the channels E1 IQ) on page 486
configured on each interface.
NOTE: For more information about the channel type and level of channelization,
and for information about the number of channels that are supported on the
channelized E1 interface, see the JUNOS Network Interfaces Configuration Guide.
■ 471
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 bits. All levels
Framing Physical layer framing format used on the link. It can be G704, G704-NO-CRC4, All levels
or Unframed. The default is G704.
Parent (Channelized E1 IQ interfaces only) Name and interface index of the interface All levels
to which a particular child interface belongs. None indicates that this interface
is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalives. detail extensive none
■ Interval seconds—Time in seconds between successive keepalive requests.
The range is 10 seconds through 32,767 seconds, with a default of 10
seconds.
■ Down-count number—Number of keepalive packets a destination must fail
to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
■ Up-count number—Number of keepalive packets a destination must receive
to change a link's status from down to up. The range is 1 through 255,
with a default of 1.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. detail extensive none
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
received, in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
LMI settings (Frame Relay) Settings for link management can be either ANSI LMI settings detail extensive none
or ITU LMI settings. ANSI LMI settings is the default. The format is (ANSI or ITU)
LMI settings: value, value... xx seconds, where value can be:
LMI (Frame Relay) Statistics about the link management. detail extensive none
■ Input—Number of packets coming in on the interface (nn) and how much
time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago)
■ Output—Number of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn
(last sent hh:mm:ss ago).
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data circuit-terminating equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no LMI packet was reported forn392dte or n393dce intervals.
(See LMI settings).
Nonmatching (Frame Relay, displayed only from the DTE) Number of DLCIs configured from detail extensive none
DCE-end DLCIs the DCE.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone(hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Traffic statistics Number of bytes and packets received and transmitted on the physical interface. detail extensive
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Giants—Number of frames received that are larger than the giant threshold.
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), then either the cable,
the far-end system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
DS1 alarms E1 media-specific defects that can render the interface unable to pass packets. detail extensive none
When a defect persists for a certain amount of time, it is promoted to an alarm.
DS1 defects Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
The following lists all possible alarms and defects. For complete explanations
of most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.
■ LOS—Loss of signal.
■ LOF—Loss of frame.
■ AIS—Alarm indication signal.
■ YLW—Yellow alarm. Indicates errors at the remote site receiver.
E1 media Active alarms and defects, plus counts of specific E1 errors with detailed extensive
information.
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Interface transmit Names of the transmit queues and their associated statistics for each DS0 extensive
queues channel on the Channelized E1 to DS0 PIC.
■ B/W—Queue bandwidth as a percentage of the total interface bandwidth.
■ WRR—Weighted round robin (in percent).
■ Packets—Number of packets transmitted.
■ Bytes—Number of bytes transmitted.
■ Drops—Number of packets dropped.
■ Errors—Number of packet errors.
DSx BERT BERT (bit error rate test) checks the quality of the line. This output appears detail extensive none
configuration only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte —Packet Level Protocol byte.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
■ bandwidth%—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority. Possible values are low and high.
■ Limit—Displayed if rate limiting is configured for the queue: none or
exact. If exact is configured, the queue transmits only up to the
configured bandwidth, even if excess bandwidth is available. If none
is configured, the queue transmits beyond the configured bandwidth
if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Table 95: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Number and rate of bytes and packets received and transmitted on the logical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface
■ Output packets—Number of packets transmitted on the interface.
Local statistics (Frame Relay) Statistics for traffic received from and transmitted to the Routing detail extensive
Engine. When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. It takes awhile (generally, less
than 1 second) for this counter to stabilize.
Transit statistics (Frame Relay) Statistics for traffic transiting the router. When a burst of traffic detail extensive
is received, the value in the output packet rate field might briefly exceed the
peak cell rate. It takes awhile (generally, less than 1 second) for this counter
to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mpls. detail extensive none
Multilink bundle (Multilink) Interface name for the multilink bundle, if configured. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive none
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when link is active, but no information is received from the
DCE.
■ Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ Dce-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
% bps % usec
0 best-effort 95 1945600 95 0 low none
3 network-control 5 102400 5 0 low none
Logical interface ds-0/3/4:1.0 (Index 74) (SNMP ifIndex 64) (Generation 13)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol mlppp, Multilink bundle: ls-0/1/0.0, MTU: 1514, Generation: 24,
Route table: 0
Logical interface ds-0/3/4:5.0 (Index 78) (SNMP ifIndex 73) (Generation 17)
Controller Physical channelized interface name and the names of any channels
configured on it.
ds-1/2/3:1 up up
ds-1/2/3:2 up up
Display channelized OC3 IQ interface information. show interfaces (Channelized OC3 IQ) on page 488
Display status information about channelized OC12 interfaces. show interfaces (Channelized OC12) on page 506
Display channelized OC12 IQ interface information. show interfaces (Channelized OC12 IQ) on page 510
Display the interface names of the physical channelized OC3 IQ show interfaces controller (Channelized OC3
interface and the channels configured on each interface. IQ) on page 514
Display the interface names of the physical channelized OC12 IQ show interfaces controller (Channelized OC12
interface and the channels configured on each interface. IQ) on page 515
NOTE: For more information about the channel type and level of channelization,
and for information about the number of channels that are supported on channelized
OC interfaces, see the JUNOS Network Interfaces Configuration Guide.
■ 487
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Clocking SONET/SDH reference clock source. It can be Internal or External. Clocking is All levels
configured and displayed only for channel 0.
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
SONET loopback Whether loopback is enabled on a SONET/SDH interface, and the type of All levels
loopback (local or remote).
FCS Frame check sequence on the interface (either 16 or 32). The default is 16-bit. All levels
Parent Name and interface index of the interface to which a particular child interface All levels
belongs. None indicates that this interface is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
ANSI or ITU LMI (Frame Relay) Settings for Local Management Interface (LMI). The format is All levels
settings (ANSI or ITU) LMI settings: value, value... nn seconds, where value can be:
LMI statistics (Frame Relay) Statistics about the link management. detail extensive
■ Input—Number of packets coming in on the interface (nn) and how much
time has passed since the last packet arrived. The format is Input: nn (last
sent hh:mm:ss ago).
■ Output—Number of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn
(last sent hh:mm:ss ago).
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data circuit-terminating equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no LMI packet was reported for n392dte or n393dce intervals.
(See LMI settings.)
Nonmatching (Frame Relay) Number of DLCIs configured from the DCE, displayed only from detail extensive none
DCE-end DLCIs the DTE.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hh:mm:ss timezone year-month-day (hh:mm:ss
ago) . For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
DS1 alarms E1or T1 media-specific defects that can prevent the interface from passing detail extensive none
packets. When a defect persists for a certain period, it is promoted to an alarm.
DS1 defects Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
The following lists all possible alarms and defects. For complete explanations
of most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.
■ LOS—Loss of signal.
■ LOF—Loss of frame.
■ AIS—Alarm indication signal.
■ YLW—Yellow alarm. Indicates errors at the remote site receiver.
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Giants—Number of frames received that are larger than the giant threshold.
■ Bucket Drops—Drops caused by traffic load exceeding the interface
transmit/receive leaky bucket configuration. The default is off.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ SRAM errors—Number of hardware errors that occurred in the static RAM
(SRAM) on the PIC. If the value of this field increments, the PIC is
malfunctioning.
■ HS link FIFO overflows—Number of FIFO overflows on the high-speed links
between the ASICs responsible for handling the router interfaces.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions —Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ HS link FIFO underflows—Number of FIFO underflows on the high-speed
links between the ASICs responsible for handling the router interfaces.
■ MTU errors—Number of packets whose size exceeds the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Active alarms Defects that can prevent the interface from passing packets: detail extensive
■ None—There are no active defects or alarms.
Active defects
■ LOF—Loss of frame.
SONET alarms Media-specific defects that can prevent the interface from passing packets. All levels
When a defect persists for a certain amount of time, it is promoted to an alarm.
SONET defects Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router or light the red or yellow alarm LED on the craft interface.
See these fields for possible alarms and defects: SONET PHY, SONET section,
SONET line, and SONET path.
Subfields are:
■ BIP-B2—Bit interleaved parity for SONET line overhead
■ REI-V—Remote error indication (near-end VT)
■ LOP-V—Loss of pointer (near-end VT)
■ AIS-V—Alarm indication signal (near-end VT)
■ RDI-V—Remote defect indication (near-end VT)
■ UNEQ-V—Unequipped (near-end VT)
■ PLM-V—Payload label mismatch (near-end VT)
■ ES-V—Errored seconds (near-end VT)
■ SES-V—Severely errored seconds (near-end VT)
■ UAS-V—Unavailable seconds (near-end VT)
■ ES-VFE—Errored seconds (far-end VT)
■ SES-VFE—Severely errored seconds (far-end VT)
■ UAS-VFE—Unavailable seconds (far-end VT)
SONET PHY Counts of specific SONET errors with detailed information: extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SONET section Counts of specific SONET errors with detailed information: extensive
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B1—Bit interleaved parity for SONET section overhead
■ SEF—Severely errored framing
■ LOS—Loss of signal
■ LOL—Loss of light
■ LOF—Loss of frame
■ ES-S—Errored seconds (section)
■ SES-S—Severely errored seconds (section)
■ SEFS-S—Severely errored framing seconds (section)
SONET line Active alarms and defects, plus counts of specific SONET errors with detailed extensive
information:
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State —State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B2—Bit interleaved parity for SONET line overhead
■ REI-L—Remote error indication (near-end line)
■ RDI-L—Remote defect indication (near-end line)
■ AIS-L—Alarm indication signal (near-end line)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ ES-L—Errored seconds (near-end line)
■ SES-L—Severely errored seconds (near-end line)
■ UAS-L—Unavailable seconds (near-end line)
■ ES-LFE—Errored seconds (far-end line)
■ SES-LFE—Severely errored seconds (far-end line)
■ UAS-LFE—Unavailable seconds (far-end line)
SONET path Active alarms and defects, plus counts of specific SONET errors with detailed extensive
information:
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ BIP-B3—Bit interleaved parity for SONET section overhead
■ REI-P—Remote error indication
■ LOP-P—Loss of pointer (path)
■ AIS-P—Path alarm indication signal
■ RDI-P—Path remote defect indication
■ UNEQ-P—Path unequipped
■ PLM-P—Path payload label mismatch
■ ES-P—Errored seconds (near-end STS path)
■ SES-P—Severely errored seconds (near-end STS path)
■ UAS-P—Unavailable seconds (near-end STS path)
■ ES-PFE—Errored seconds (far-end STS path)
■ SES-PFE—Severely errored seconds (far-end STS path)
■ UAS-PFE—Unavailable seconds (far-end STS path)
Received SONET Values of the received and transmitted SONET/SDH overhead: extensive
overhead
F1—Section user channel byte. This byte is set aside for the purposes of users.
Transmitted SONET
overhead S1—Synchronization Status (S1). The S1 byte is located in the first STS-1 of an
STS-N. Bits 5 through 8 convey the synchronization status of the network
element.
SDH alarms SDH media-specific defects that can prevent the interface from passing packets. All levels
When a defect persists for a certain period, it is promoted to an alarm. Based
SDH defects on the router configuration, an alarm can ring the red or yellow alarm bell on
the router or light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.
SDH PHY Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SDH regenerator Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ RS-BIP8—24-bit BIP for multiplex section overhead (B2 bytes)
■ OOF—Out of frame
■ LOS—Loss of signal
■ LOF—Loss of frame
■ RS-ES—Errored seconds (near-end regenerator section)
■ RS-SES—Severely errored seconds (near-end regenerator section)
■ RS-SEFS—Severely errored framing seconds (regenerator section)
SDH multiplex Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ MS-BIP24—8-bit BIP for high-order path overhead (B3 byte)
■ MS-FEBE—Far-end block error (multiplex section)
■ MS-FERF—Far-end remote fail (multiplex section)
■ MS-AIS—alarm indication signal (multiplex section)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ MS-ES—Errored seconds (near-end multiplex section)
■ MS-SES—Severely errored seconds (near-end multiplex section)
■ MS-UAS—Unavailable seconds (near-end multiplex section)
■ MS-ES-FE—Errored seconds (far-end multiplex section)
■ MS-SES-FE—Severely errored seconds (far-end multiplex section)
■ MS-UAS-FE—Unavailable seconds (far-end multiplex section
SDH path Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ HP-BIP8—8-bit BIP for regenerator section overhead (B1 byte)
■ HP-FEBE—Far-end block error (high-order path)
■ HP-LOP—Loss of pointer (high-order path)
■ HP-AIS—High-order-path alarm indication signal
■ HP-FERF—Far-end remote fail (high-order path)
■ HP-UNEQ—Unequipped (high-order path)
■ HP-PLM—Payload label mismatch (high-order path)
■ HP-ES—Errored seconds (near-end high-order path)
■ HP-SES—Severely errored seconds (near-end high-order path)
■ HP-UAS—Unavailable seconds (near-end high-order path)
■ HP-ES-FE—Errored seconds (far-end high-order path)
■ HP-SES-FE—Severely errored seconds (far-end high-order path)
■ HP-UAS-FE—Unavailable seconds (far-end high-order path)
Received SDH Values of the received and transmitted SONET overhead: extensive
overhead
■ C2—Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
Transmitted SDH
overhead ■ F1—Section user channel byte. This byte is set aside for the purposes of
users.
■ K1 and K2—These bytes are allocated for APS signaling for the protection
of the multiplex section.
■ J0—Section trace. This byte is defined for STS-1 number 1of an STS-N
signal. Used to transmit a 1-byte fixed-length string or a 16-byte message
so that a receiving terminal in a section can verify its continued connection
to the intended transmitter.
■ S1—Synchronization status. The S1 byte is located in the first STS-1 of
an STS-N.
■ Z3 and Z4—Allocated for future use.
Received path trace Channelized OC12 interfaces allow path trace bytes to be sent inband across extensive
the SONET/SDH link. The received path trace value is the message received
Transmitted path from the router at the other end of the fiber. The transmitted path trace value
trace is the message that this router transmits. This information is specific to each
of the 12 channelized OC12 interfaces.
DS3 media Counts of T3 media-specific errors. For detailed definitions of the T3 (DS-3) extensive
error events (BPV, EXZ, LCV, PCV, and CCV) and performance parameters
(LES, PES, PSES, CES, CSES, SEFS, and UAS), see RFC 2496.
Interface transmit Name of the transmit queues and their associated statistics for each DS3 channel extensive
queues on the Channelized OC12 PIC.
■ B/W—Queue bandwidth as a percentage of the total interface bandwidth.
■ WRR—Weighted round-robin (in percent).
■ Packets—Number of packets transmitted.
■ Bytes—Number of bytes transmitted.
■ Drops—Number of packets dropped.
■ Errors—Number of packet errors.
DSU configuration Information about the DSU configuration. The last three lines (Bit count, Error extensive
bit count, and LOS information) are displayed only if a BERT has ever been run
on the interface.
■ Compatibility mode—CSU/DSU compatibility mode: None, Larscom, Kentrox,
or Digital-Link.
■ Scrambling—Payload scrambling. It can beEnabled or Disabled.
■ Subrate—Configured subrate setting. Applies only whenDigital-Link
compatibility mode is used. It can be Disabled or display units in kbps.
■ FEAC loopback—(T3) Whether a far-end alarm and control (FEAC) loopback
isActive or Inactive. This feature is used to send alarm or status information
from the far-end terminal back to the near-end terminal and to initiate
T3 loopbacks at the far-end terminal from the near-end terminal.
■ Response—Whether the FEAC signal isEnabled or Disabled.
■ Count—Number of FEAC loopbacks.
BERT configuration (DS interfaces) BERT (bit error rate test) checks the quality of the line. This detail extensive none
output appears only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—The queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority: low and high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input rate—Rate of bits and packets received on the interface.
■ Output rate—Rate of bits and packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. detail extensive none
Multilink bundle (If the logical interface is configured as part of a multilink bundle.) Interface detail extensive none
name for the multilink bundle.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive none
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when the link is active, but no information is received from
the DCE.
■ Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ Dce-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
UAS-PFE 0
Received SONET overhead:
C2 : 0xff, C2(cmp) : 0x01, F2 : 0x00, Z3 : 0x00
Z4 : 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
C2 : 0x01, F2 : 0x00, Z3 : 0x00, Z4 : 0x00
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace: router-1 coc1-0/0/0:1
6b 61 76 65 72 69 20 63 6f 63 31 2d 30 2f 30 2f router-1 coc1-0/0/0:1
30 3a 31 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
HDLC configuration:
Giant threshold: 1514, Runt threshold: 2
Timeslots : 1-5
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS0 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x00)
Common statistics:
Unknown messages received : 0
Asynchronous updates received : 0
Out-of-sequence packets received : 0
Keepalive responses timedout : 0
Nonmatching DCE-end DLCIs:
2
Hold-times : Up 0 ms, Down 0 ms
Last flapped : 2002-05-23 16:59:03 PDT (18:23:58 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 1700 0 bps
Output bytes : 1714 0 bps
Input packets: 123 0 pps
Output packets: 124 0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 1100817, Bucket drops: 0,
Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0
DS3 alarms : None
SONET alarms : None
DS3 defects : None
SONET defects : None
DS3 media: Seconds Count State
AIS 0 0 OK
LOF 18 1 OK
LOS 0 0 OK
IDLE 0 0 OK
YELLOW 0 0 OK
BPV 0 0
EXZ 0 0
LCV 0 0
PCV 36 122399
CCV 72 91948
LES 0
PES 18
PSES 18
CES 18
CSES 18
SEFS 18
UAS 0
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
DSU configuration:
Compatibility mode: None, Scrambling: Disabled, Subrate: Disabled
FEAC loopback: Inactive, Response: Disabled, Count: 0
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: Unknown (0), Induced error rate: 10e-0
Interface transmit queues:
B/W WRR Packets Bytes Drops Errors
Queue0 95 95 0 0 0 0
Queue1 5 5 529 6348 0 0
SONET PHY: Seconds Count State
PLL Lock 0 0 OK
PHY Light 20 1 OK
SONET section:
BIP-B1 0 0
SEF 20 1 OK
LOS 20 1 OK
LOF 20 1 OK
ES-S 20
SES-S 20
SEFS-S 20
SONET line:
BIP-B2 0 0
REI-L 0 0
RDI-L 0 0 OK
AIS-L 0 0 OK
BERR-SF 18 1 OK
BERR-SD 2 1 OK
ES-L 20
SES-L 20
UAS-L 10
ES-LFE 0
SES-LFE 0
UAS-LFE 0
SONET path:
BIP-B3 0 0
REI-P 0 0
LOP-P 20 1 OK
AIS-P 0 0 OK
RDI-P 0 0 OK
UNEQ-P 0 0 OK
PLM-P 20 1 OK
ES-P 20
SES-P 20
UAS-P 10
ES-PFE 0
SES-PFE 0
UAS-PFE 0
Received SONET overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x04, C2(cmp) : 0x04, F2 : 0x00
Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00, V5 : 0x00
V5(cmp) : 0x00
Transmitted SONET overhead:
F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x04, F2 : 0x00, Z3 : 0x00
Z4 : 0x00, V5 : 0x00
Received path trace: t3-0/3/0:0
74 33 2d 30 2f 33 2f 30 3a 30 00 00 00 00 0d 0a t3-0/3/0:0......
Transmitted path trace: t3-0/3/0:0
74 33 2d 30 2f 33 2f 30 3a 30 00 00 00 00 00 00 t3-0/3/0:0......
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 42499200 95 0 low none
3 network-control 5 2236800 5 0 low none
Logical interface t3-0/3/0:0.0 (Index 11) (SNMP ifIndex 268) (Generation 499)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 578, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 22.22.22.1, Local: 22.22.22.2, Broadcast: Unspecified,
Generation: 98
DLCI 100
For SONET mode, the interface type can be one of the following:
■ type-fpc/pic/port—For the physical channelized OC12 IQ interface, type is
coc12. For the clear channel, type is so (for OC12).
■ type-fpc/pic/port:channel—At the first level of channelization, type can be
coc1(channelized OC1), ct3 (from coc1), so (for OC3), or t3.
■ type-fpc/pic/port:channel:channel—At the second level of channelization, type
can be ct1 (from ct3or coc1) or t1 (from ct3 or coc1).
■ type-fpc/pic/port:channel:channel:channel—At the third level of channelization,
type is ds (from ct1).
For SDH mode, the interface type can be one of the following:
■ type-fpc/pic/port—For the physical channelized OC12 IQ interface, type is
cstm4. For the clear channel, type is so (for SONET/SDH (vc-4-4c)).
■ type-fpc/pic/port:channel—At the first level of channelization,type can be so
(from cstm4) or cau4 (from cstm4).
■ type-fpc/pic/port:channel:channel—At the second level of channelization, type
can be ct3or t3 (from or cau4).
■ type-fpc/pic/port:channel:channel:channel—At the third level of channelization,
type is ct1 or t1 (from ct3).
■ type-fpc/pic/port:channel:channel:channel—At the fourth level of
channelization, type is ds (from ct1).
Controller Physical channelized interface name and the names of any channels
configured on it.
Controller Physical channelized interface name and the names of any channels
configured on it.
t1-4/2/0:4:28 up up
t3-4/2/0:5 up up
coc1-4/2/0:6 up up
t1-4/2/0:6:1 up up
t1-4/2/0:6:2 up up
...
t1-4/2/0:6:28 up up
coc1-4/2/0:7 up up
ct1-4/2/0:7:1 up up
ds-4/2/0:7:1:1 up up
ds-4/2/0:7:1:2 up up
...
ds-4/2/0:7:1:24 up up
ct1-4/2/0:7:2 up up
ds-4/2/0:7:2:1 up up
ds-4/2/0:7:2:2 up up
...
ds-4/2/0:7:2:6 up up
t1-4/2/0:7:3 up up
t1-4/2/0:7:4 up up
...
t1-4/2/0:7:28 up up
so-4/2/0:8 up up
Table 101 on page 517 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot channelized STM1 interfaces. Commands are
listed in alphabetical order.
Task Command
Display the interface names of the physical show interfaces controller (Channelized
channelized STM1 IQ interface and the channels STM1 IQ) on page 535
configured on each interface.
NOTE: For more information about the channel type and level of channelization,
and for information about the number of channels that are supported on the
channelized STM1 interface, see the JUNOS Network Interfaces Configuration Guide.
■ 517
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 All levels
bits.
Framing Physical layer framing format used on the link. It can be G704, G704-NO-CRC4, All levels
or Unframed. The default is G704.
Parent (Channelized STM1 IQ interfaces only) Name and interface index of the interface All levels
to which a particular child interface belongs. None indicates that this interface
is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalives. detail extensive none
■ intervalseconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a default
of 10 seconds.
■ down-count number—The number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is1 through
255, with a default of 3.
■ up-count number—The number of keepalive packets a destination must
receive to change a link's status from down to up. The range is 1 through
255, with a default of 1.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. detail extensive none
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
received, in the formathh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
ANSI LMI settings (Frame Relay) Local Management Interface settings. The format is (ANSI or ITU) detail extensive none
or LMI settings: value, value... xx seconds, where value can be:
ITU LMI settings
■ n391dte—DTE full status polling interval (1- 255)
■ n392dce—DCE error threshold (1-10)
■ n392dte—DTE error threshold (1-10)
■ n393dce—DCE monitored event count (1-10)
■ n393dte—DTE monitored event count (1-10)
■ t391dte—DTE polling timer (5-30 seconds)
■ t392dce—DCE polling verification timer (5-30 seconds)
LMI (Frame Relay) Statistics about the link management. detail extensive none
■ Input—Number of packets coming in on the interface (nn) and how much
time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).
■ Output—Number of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn
(last seen hh:mm:ss ago).
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data circuit-terminating equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no LMI packet was reported for n392dte or n393dce intervals.
(See LMI settings.)
Nonmatching (Frame Relay, displayed only from the DTE) Number of DLCIs configured from detail extensive none
DCE-end DLCIs the DCE.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
■ L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ SRAM errors—Number of hardware errors that occurred in the static RAM
(SRAM) on the PIC. If the value of this field increments, the PIC is
malfunctioning.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
DS1 alarms E1 media-specific defects that can prevent the interface from passing packets. detail extensive none
When a defect persists for a certain period, it is promoted to an alarm. Based
DS1 defects on the router configuration, an alarm can ring the red or yellow alarm bell on
the router, or turn on the red or yellow alarm LED on the craft interface. The
following lists all possible alarms and defects. For complete explanations of
most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.
■ LOS—Loss of signal.
■ LOF—Loss of frame.
■ AIS—Alarm indication signal.
■ YLW—Yellow alarm. Indicates errors at the remote site receiver.
SDH alarms SDH media-specific defects that can prevent the interface from passing packets. All levels
When a defect persists for a certain period, it is promoted to an alarm. Based
SDH defects on the router configuration, an alarm can ring the red or yellow alarm bell on
the router or light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.
E1 media Active alarms and defects, plus counts of specific E1 errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Interface transmit Names of the transmit queues and their associated statistics for each E1 channel extensive
queues on the Channelized STM1-to-E1 PIC.
■ B/W—Queue bandwidth as a percentage of the total interface bandwidth.
■ WRR—Weighted round-robin (in percent).
■ Packets—Number of packets transmitted.
■ Bytes—Number of bytes transmitted.
■ Drops—Number of packets dropped.
■ Errors—Number of packet errors.
DS1 BERT BERT (bit error rate test) checks the quality of the line. This output appears detail extensive none
configuration only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
SDH PHY Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ PLL Lock—Phase-locked loop
■ PHY Light—Loss of optical signal
SDH regenerator Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ RS-BIP8—24-bit BIP for multiplex section overhead (B2 bytes)
■ OOF—Out of frame
■ LOS—Loss of signal
■ LOF—Loss of frame
■ RS-ES—Errored seconds (near-end regenerator section)
■ RS-SES—Severely errored seconds (near-end regenerator section)
■ RS-SEFS—Severely errored framing seconds (regenerator section)
SDH multiplex Active alarms and defects, plus counts of specific SDH errors with detailed extensive
section information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ MS-BIP24—8-bit BIP for high-order path overhead (B3 byte)
■ MS-FEBE—Far-end block error (multiplex section)
■ MS-FERF—Far-end remote fail (multiplex section)
■ MS-AIS—alarm indication signal (multiplex section)
■ BERR-SF—Bit error rate fault (signal failure)
■ BERR-SD—Bit error rate defect (signal degradation)
■ MS-ES—Errored seconds (near-end multiplex section)
■ MS-SES—Severely errored seconds (near-end multiplex section)
■ MS-UAS—Unavailable seconds (near-end multiplex section)
■ MS-ES-FE—Errored seconds (far-end multiplex section)
■ MS-SES-FE—Severely errored seconds (far-end multiplex section)
■ MS-UAS-FE—Unavailable seconds (far-end multiplex section)
SDH path Active alarms and defects, plus counts of specific SDH errors with detailed extensive
information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ HP-BIP8—8-bit BIP for regenerator section overhead (B1 byte)
■ HP-FEBE—Far-end block error (high-order path)
■ HP-LOP—Loss of pointer (high-order path)
■ HP-AIS—High-order-path alarm indication signal
■ HP-FERF—Far-end remote fail (high-order path)
■ HP-UNEQ—Unequipped (high-order path)
■ HP-PLM—Payload label mismatch (high-order path)
■ HP-ES—Errored seconds (near-end high-order path)
■ HP-SES—Severely errored seconds (near-end high-order path)
■ HP-UAS—Unavailable seconds (near-end high-order path)
■ HP-ES-FE—Errored seconds (far-end high-order path)
■ HP-SES-FE—Severely errored seconds (far-end high-order path)
■ HP-UAS-FE—Unavailable seconds (far-end high-order path)
SDH tu Active alarms and defects, plus counts of specific SDH tributary unit (TU) errors extensive
with detailed information.
■ Seconds—Number of seconds the defect has been active.
■ Count—Number of times that the defect has gone from inactive to active.
■ State—State of the error. State other than OK indicates a problem.
Subfields are:
■ TU-BIP-2—Bit interleaved parity for SONET line overhead
■ TU-FEBE—(near-end TU)
■ TU-LOP—Loss of pointer (near-end TU)
■ TU-AIS—Alarm indication signal (near-end TU)
■ TU-FERF—(near-end TU)
■ TU-UNEQ—Unequipped (near-end TU)
■ TU-PLM—Payload label mismatch (near-end TU)
■ TU-ES—Errored seconds (near-end TU)
■ TU-SES—Severely errored seconds (near-end TU)
■ TU-UAS—Unavailable seconds (near-end TU)
■ TU-ES-FE—Errored seconds (far-end TU)
■ TU-SES-FE—Severely errored seconds (far-end TU)
■ TU-UAS-FE—Unavailable seconds (far-end TU)
Received SDH Values of the received and transmitted SONET overhead: extensive
overhead
■ C2—Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
Transmitted SDH
overhead ■ F1—Section user channel byte. This byte is set aside for the purposes of
users.
■ K1 and K2—These bytes are allocated for APS signaling for the protection
of the multiplex section.
■ J0—Section trace. This byte is defined for STS-1 number 1 of an STS-N
signal. Used to transmit a 1-byte fixed-length string or a 16-byte message
so that a receiving terminal in a section can verify its continued connection
to the intended transmitter.
■ S1—Synchronization status. The S1 byte is located in the first STS-1 of
an STS-N signal.
■ Z3 and Z4—Allocated for future use.
Received path trace Channelized OC12 interfaces allow path trace bytes to be sent inband across extensive
the SONET/SDH link. The received path trace value is the message received
Transmitted path from the router at the other end of the fiber. The transmitted path trace value
trace is the message that this router transmits. This information is specific to each
of the 12 channelized OC12 interfaces.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive none
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when the link is active, but no information is received from
the DCE.
■ Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ Dce-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
V5(cmp) : 0x02
Transmitted SDH overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x02, F2 : 0x00, Z3 : 0x00
Z4 : 0x00, V5 : 0x02
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Packet Forwarding Engine configuration:
Destination slot: 1, PLP byte: 2 (0x07)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 1945600 95 0 low none
3 network-control 5 102400 5 0 low none
Logical interface e1-1/0/0:1.0 (Index 10) (SNMP ifIndex 369) (Generation 496)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 575, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 19.19.19.3, Local: 19.19.19.4, Broadcast: Unspecified,
Generation: 975
DLCI 100
Flags: Active, Dce-configured
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :2 Inactive DLCI : 0
Speed: OC3, Loopback: None, Parent: None Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags : Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent : 43186
Full enquiries sent : 8515
Enquiry responses received : 43185
Full enquiry responses received : 8515
DCE statistics:
Enquiries received : 0
Full enquiries received : 0
Enquiry responses sent : 0
Full enquiry responses sent : 0
Common statistics:
Unknown messages received : 0
Asynchronous updates received : 0
Out-of-sequence packets received : 0
Keepalive responses timedout : 0
Nonmatching DCE-end DLCIs:
2
Last flapped : 2003-02-06 15:01:56 PST (07:15:06 ago)
...
Controller Physical channelized interface name and the names of any channels
configured on it.
Table 104 on page 537 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot channelized T1 and T3 interfaces. Commands
are listed in alphabetical order.
Task Command
Display status information about channelized DS3-to-DS0 interfaces. show interfaces (Channelized DS3-to-DS0) on page 538
Display status information about channelized DS3-to-DS1 interfaces. show interfaces (Channelized DS3-to-DS1) on page 549
Display channelized T1 IQ interface information. show interfaces (Channelized T1 IQ) on page 552
Display channelized T3 IQ interface information. show interfaces (Channelized T3 IQ) on page 564
Display the interface names of the physical channelized T1 IQ show interfaces controller (Channelized T1
interface and the channels configured on each interface. IQ) on page 566
Display the interface names of the physical channelized T3 IQ show interfaces controller (Channelized T3 IQ) on page
interface and the channels configured on each interface. 567
NOTE: For more information about the channel type and level of channelization,
and for information about the number of channels that are supported on the different
types of channelized T1 and T3 interfaces, see the JUNOS Network Interfaces
Configuration Guide.
■ 537
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 bits. All levels
Mode Whether C-bit parity mode or M13 mode is enabled. All levels
Framing Physical layer framing format used on the link. It can be ESF or SF. The default All levels
is ESF.
Parent (Channelized IQ interfaces only) Name and interface index of the interface to All levels
which a particular child interface belongs. None indicates that this interface is
the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Keepalive settings (PPP and HDLC) Configured settings for keepalives. detail extensive none
■ interval seconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a default
of 10 seconds.
■ down-count number—The number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is 1 through
255, with a default of 3.
■ up-count number—The number of keepalive packets a destination must
receive to change a link's status from down to up. The range is 1 through
255, with a default of 1.
Keepalive statistics (PPP and HDLC) Information about keepalive packets. detail extensive none
■ Input—Number of keepalive packets received by PPP.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
received, in the format hh:mm:ss.
■ Output—Number of keepalive packets sent by PPP and how long ago the
last keepalive packets were sent and received.
■ (last seen 00:00:00 ago)—Time since the last keepalive packet was
sent, in the format hh:mm:ss.
LMI settings (Frame Relay) Settings for Local Management Interface (LMI) can be either detail extensive none
ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default. The format
is (ANSI or ITU) LMI settings: value, value, value...xx seconds, where value can
be:
■ n391dte—DTE full status polling interval (1?255)
■ n392dce—DCE error threshold (1–10)
■ n392dte—DTE error threshold (1–10)
■ n393dce—DCE monitored event count (1–10)
■ n393dte—DTE monitored event count (1–10)
■ t391dte—DTE polling timer (5–30 seconds)
■ t392dce—DCE polling verification timer (5–30 seconds)
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into theSuccess state. (Most likely with RADIUS
authentication).
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone hh:mm:ss ago). For
example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Giants—Number of frames received that are larger than the giant threshold.
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Counter increments when the software could not find
a valid logical interface for an incoming frame.
■ L2 mismatch timeouts—Count of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ SRAM errors—Number of hardware errors that occurred in the static RAM
(SRAM) on the PIC. If the value in this field increments, the PIC is
malfunctioning.
■ HS link CRC errors—Count of errors on the high-speed links between the
ASICs responsible for handling the router interfaces.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly, (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
DS1 alarms Media-specific defects that can render the interface unable to pass packets. detail extensive none
When a defect persists for a certain amount of time, it is promoted to an alarm.
DS1 defects Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
■ LOS—Loss of signal.
■ LOF—Loss of frame.
■ AIS—Alarm indication signal.
■ YLW—Yellow alarm. Indicates errors at the remote site receiver.
DS3 media Counts of T3 media-specific errors. For detailed definitions of the T3 (DS-3) extensive
error events (BPV, EXZ, LCV, PCV, and CCV) and performance parameters
(LES, PES, PSES, CES, CSES, SEFS, and UAS), see RFC 2496.
■ PLL Lock—Phase-locked loop out of lock
■ Reframing—Frame alignment recovery time
■ AIS—Alarm indication signal
■ LOF—Loss of frame
■ LOS—Loss of signal
■ IDLE—Idle code detected
■ YELLOW—Remote defect indication
■ BPV—Bipolar violation
■ EXZ—Excessive zeros
■ LCV—Line code violation
■ PCV—Pulse code violation
■ CCV—C-bit coding violation
■ LES—Line error seconds
■ PES—P-bit errored seconds
■ PSES—P-bit errored seconds (section)
■ CES—C-bit errored seconds
■ CSES—C-bit severely errored seconds
■ SEFS—Severely errored framing seconds
■ UAS—Unavailable seconds
Interface transmit Name of the transmit queues and their associated statistics for each DS1 channel extensive
queues on the Channelized DS3-to-DS1 PIC.
■ B/W—Queue bandwidth as a percentage of the total interface bandwidth.
■ WRR—Weighted round-robin (in percent).
■ Packets—Number of packets transmitted.
■ Bytes—Number of bytes transmitted.
■ Drops—Number of packets dropped.
■ Errors—Number of packet errors.
DS1 or DS3 BERT BERT (bit error rate test) checks the quality of the line. This output appears detail extensive none
configuration only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
■ CoS transmit queue—The queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue only
transmits up to the configured bandwidth, even if excess bandwidth
is available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface All levels
Flags” on page 82.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive none
Redundant Link (LSQ redundancy) Backup link for Link Services IQ redundancy. detail extensive none
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Loopback Whether loopback is enabled and the type of loopback (local or remote). All levels
FCS Frame check sequence on the interface (either 16 or 32). The default is 16 bits. All levels
Framing Physical layer framing format used on the link. It can be ESF or SF. The default All levels
is ESF.
Parent Name and interface index of the interface to which a particular child interface All levels
belongs. None indicates that this interface is the top level.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
LMI settings (Frame Relay) Settings for Local Management Interface (LMI) can be either detail extensive none
ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default. The format
is (ANSI or ITU) LMI settings: value, value... xx seconds, where value can be:
■ n391dte—DTE full status polling interval (1–255)
■ n392dce—DCE error threshold (1–10)
■ n392dte—DTE error threshold (1–10)
■ n393dce—DCE monitored event count (1–10)
■ n393dte—DTE monitored event count (1–10)
■ t391dte—DTE polling timer (5–30 seconds)
■ t392dce—DCE polling verification timer (5–30 seconds)
DTE statistics (Frame Relay) Statistics about messages transmitted from the data terminal detail extensive none
equipment (DTE) to the data communication equipment (DCE):
■ Enquiries sent—Number of link status enquiries sent from the DTE to the
DCE.
■ Full enquiries sent—Number of full enquiries sent from the DTE to the
DCE.
■ Enquiry responses received—Number of enquiry responses received by
the DTE from the DCE.
■ Full enquiry responses received—Number of full enquiry responses sent
from the DTE to the DCE.
DCE statistics (Frame Relay) Statistics about messages transmitted from the DCE to the DTE: detail extensive none
■ Enquiries received—Number of enquiries received by the DCE from the
DTE.
■ Full enquiries received—Number of full enquiries received by the DCE from
the DTE.
■ Enquiry responses sent—Number of enquiry responses sent from the DCE
to the DTE.
■ Full enquiry responses sent—Number of full enquiry responses sent from
the DCE to the DTE.
Common statistics (Frame Relay) Statistics about messages sent between the DTE and the DCE: detail extensive none
■ Unknown messages received—Number of received packets that do not fall
into any category.
■ Asynchronous updates received—Number of link status peer changes
received.
■ Out-of-sequence packets received—Number of packets for which the
sequence of the packets received is different from the expected sequence.
■ Keepalive responses timedout—Number of keepalive responses that timed
out when no LMI packet was reported for n392dte or n393dce intervals.
(See LMI settings.)
Nonmatching (Frame Relay) Number of DLCIs configured from the DCE, displayed only from detail extensive none
DCE-end DLCIs the DTE.
LCP state (PPP) Link Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—LCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—LCP is not configured on the interface.
■ Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication Protocol detail extensive none
(CHAP) during its transaction.
■ Chap-Chal-received—Challenge was received but response not yet sent.
■ Chap-Chal-sent—Challenge was sent.
■ Chap-Resp-received—Response was received for the challenge sent, but
CHAP has not yet moved into theSuccess state. (Most likely with RADIUS
authentication.)
■ Chap-Resp-sent—Response was sent for the challenge received.
■ Closed—CHAP authentication is incomplete.
■ Failure—CHAP authentication failed.
■ Not-configured—CHAP is not configured on the interface.
■ Success—CHAP authentication was successful.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Giants—Number of frames received that are larger than the giant threshold.
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example, a
frame with less than 20 bytes of available IP header is discarded.
■ L2 channel errors—Counter increments when the software could not find
a valid logical interface for an incoming frame.
■ L2 mismatch timeouts—Count of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
■ HS link CRC errors—Count of errors on the high-speed links between the
ASICs responsible for handling the router interfaces.
■ SRAM errors—Number of hardware errors that occurred in the static RAM
(SRAM) on the PIC. If the value in this field increments, the PIC is
malfunctioning.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ MTU errors—Number of packets whose size exceeds the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
DS1 alarms DS1 Media-specific defects that can render the interface unable to pass packets. detail extensive none
defects When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
■ LOS—Loss of signal.
■ LOF—Loss of frame.
■ AIS—Alarm indication signal.
■ YLW—Yellow alarm. Indicates errors at the remote site receiver.
DS0 or DS1 BERT BERT (bit error rate test) checks the quality of the line. This output appears detail extensive none
configuration only when a BERT is run on the interface.
■ BERT time period—Configured total time period that the BERT is to run.
■ Elapsed—Actual time elapsed since the start of the BERT (in seconds).
■ Induced error rate—Configured rate at which the bit errors are induced in
the BERT pattern.
■ Algorithm—Type of algorithm selected for the BERT.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ PLP byte—Packet Level Protocol byte.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface All levels
Flags” on page 82.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
DLCI (Frame Relay) DLCI number of the logical interface. The following DLCI detail extensive none
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:
■ Active—Set when the link is active and the DTE and DCE are exchanging
information.
■ Down—Set when the link is active, but no information is received from
the DCE.
■ Unconfigured—Set when the corresponding DLCI in the DCE is not
configured.
■ Configured—Set when the corresponding DLCI in the DCE is configured.
■ Dce-configured—Displayed when the command is issued from the DTE.
DLCI statistics (Frame Relay) Data-link connection identifier (DLCI) statistics. detail extensive none
■ Active DLCI—Number of active DLCIs.
■ Inactive DLCI—Number of inactive DLCIs.
YELLOW 0 0 OK
BPV 0 0
EXZ 0 0
LCV 0 0
PCV 0 0
CS 0 0
LES 0
ES 0
SES 0
SEFS 0
BES 0
UAS 0
Line encoding: B8ZS
Buildout : 0 to 132 feet
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0,
MTU errors: 0, Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 1 1 0
DS1 alarms : None
DS1 defects : None
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 1514, Runt threshold: 2
Timeslots : All active
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag:
flags, Start end flag: shared
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x00)
Controller Physical channelized interface name and the names of any channels
configured on it.
show interfaces The following sample output displays the channelized T1 IQ interface when it is
controller (T1 IQ) configured as a clear-channel T1 interface:
(Clear-Channel T1)
user@host> show interfaces controller ct1-0/2/0
show interfaces The following sample output displays the channelized T1 IQ interfaces when it is
controller (T1 IQ) configured down to the channelized DS level:
(Channelized DS)
user@host> show interfaces controller ct1-0/2/1
Controller Admin Link
ct1-0/2/1 up up
ds-0/2/1:1 up up
ds-0/2/1:2 up up
Controller Physical channelized interface name and the names of any channels
configured on it.
Table 109 on page 571 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot adaptive services interfaces and redundant
adaptive services interfaces.
Task Command
Switch between primary and secondary adaptive services interfaces. request interface (revert | switchover) on page 572
Display status information about individual adaptive services show interfaces (Adaptive Services) on page 573
interfaces.
Display detailed status information about redundant adaptive services show interfaces (Redundant Adaptive
configurations. Services) on page 580
Display general status information about redundant adaptive services show interfaces redundancy on page 582
configurations.
■ 571
JUNOS 9.0 Interfaces Command Reference
Release Information Command introduced before JUNOS Release 7.4. Support for rlsq interfaces added
in JUNOS Release 7.6.
Description (M-series and T-series routing platforms only) Manually revert to the primary adaptive
services interface or link services IQ interface, or switch from primary to the
secondary interface.
Options (revert | switchover)—The revert keyword restores active processing to the primary
adaptive services (sp) or link services IQ (lsq) interface. The switchover keyword
transfers active processing to the secondary (backup) interface.
Options interface-type—On M-series and T-series routing platforms, the interface type is sp-
fpc/pic/port. On the J-series routing platform, the interface type is sp-pim/0/port.
Table 110: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Table 110: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields (continued)
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link type Physical interface link type: Full-Duplex or Half-Duplex. detail extensive none
Link flags Information about the link. Possible values are described in “Link detail extensive none
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Table 110: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields (continued)
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Frames received smaller than the runt threshold.
■ Giants—Frames received larger than the giant threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Table 110: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields (continued)
Traffic statistics Number and rate of bytes and packets received and transmitted on the logical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes generally less than 1 second for the counter to stabilize.
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Local statistics:
Input bytes : 125147
Output bytes : 1483113
Input packets: 3061
Output packets: 3048
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 9192, Generation: 20, Route table: 1
Flags: Receive-options, Receive-TTL-Exceeded
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.0.34, Local: 10.0.0.1, Broadcast: Unspecified,
Generation: 22
Logical interface rsp0.0 (Index 68) (SNMP ifIndex 42) (Generation 30)
Flags: Point-To-Point SNMP-Traps Encapsulation: Adaptive-Services
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 9192, Generation: 37, Route table: 0
Flags: Receive-options, Receive-TTL-Exceeded
Table 112 on page 583 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot encryption interfaces.
Task Command
Display status information about encryption show interfaces (Encryption) on page 584
interfaces.
■ 583
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
Device flags Information about the physical device. Possible values are described in “Link All levels
Flags” on page 81.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
■ Anti-replay failures—Total number of antireplay failures seen on all tunnels
configured on the ES PIC.
■ Authentication—Total number of authentication failures seen on all tunnels
configured on the ES PIC.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 3800, Generation: 22, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.10.0.2, Local: 10.10.0.1, Broadcast: Unspecified,
Generation: 26
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Table 114 on page 591 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot flow collector and flow monitoring interfaces.
Commands are listed in alphabetical order.
Table 114: Flow Collector and Monitoring Interface Operational Mode Commands
Task Command
Display status information about dynamic flow show interfaces (Dynamic Flow
capture interfaces. Capture) on page 592
Display status information about flow collector show interfaces (Flow Collector) on page 596
interfaces.
■ 591
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled Sate of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Link-level type Encapsulation type used on the physical interface. All levels
Table 115: Dynamic Flow Capture show interfaces Output Fields (continued)
MTU Maximum Transmit Unit (MTU). Size of the largest packet to be transmitted. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input rate, Output rate—Number of bits per second (packets per second)
received and transmitted on the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Table 115: Dynamic Flow Capture show interfaces Output Fields (continued)
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Flags Information about the logical interface; values are described in “Logical Interface All levels
Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Protocol Protocol family configured on the logical interface (such as iso or inet6). detail extensive none
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Addresses associated with the logical interface and information about the detail extensive none
address flags. Possible values are described in “Addresses, Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Physical Interface
Physical Interface Name of the physical interface type. All levels
Enabled State of the interface type. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. All levels
MTU Maximum Transmit Unit (MTU). Size of the largest packet to be transmitted. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive none
Hardware address Media access control (MAC) address of the interface. detail extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Output errors ■ Carrier transitions —Number of times the interface has gone from down extensive
to up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface All levels
Flags” on page 82.
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface (such as iso or inet6). detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Route table in which this address exists; for example, Route table:0 refers to detail extensive
inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Logical interface cp-5/0/0.0 (Index 74) (SNMP ifIndex 53) (Generation 28)
Flags: Point-To-Point SNMP-Traps Encapsulation: Flow-collection
Traffic statistics:
Input bytes : 1064651568
Output bytes : 37144290
Input packets: 711324
Output packets: 713672
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 1064651568 0 bps
Output bytes : 37144290 0 bps
Input packets: 711324 0 pps
Output packets: 713672 0 pps
Protocol inet, MTU: 9192, Generation: 39, Route table: 0
Flags: Receive-options, Receive-TTL-Exceeded
Addresses, Flags: Is-Preferred Is-Primary
Destination: 4.0.0.2, Local: 4.0.0.1, Broadcast: Unspecified,
Generation: 40
Logical interface cp-5/0/0.1 (Index 75) (SNMP ifIndex 54) (Generation 29)
Flags: Point-To-Point SNMP-Traps Encapsulation: Flow-collection
Traffic statistics:
Input bytes : 976793823
Output bytes : 34099481
Input packets: 652729
Output packets: 655127
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 976793823 0 bps
Output bytes : 34099481 0 bps
Input packets: 652729 0 pps
Output packets: 655127 0 pps
Protocol inet, MTU: 9192, Generation: 40, Route table: 0
Flags: Receive-options, Receive-TTL-Exceeded
Addresses, Flags: Is-Preferred Is-Primary
Destination: 4.1.1.2, Local: 4.1.1.1, Broadcast: Unspecified,
Generation: 42
Logical interface cp-5/0/0.2 (Index 80) (SNMP ifIndex 55) (Generation 30)
Flags: Point-To-Point SNMP-Traps Encapsulation: Flow-collection
Traffic statistics:
Input bytes : 0
Output bytes : 3723079376
Input packets: 0
Output packets: 2495372
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 3723079376 43816664 bps
Input packets: 0 0 pps
Output packets: 2495372 3670 pps
Protocol inet, MTU: 9192, Generation: 41, Route table: 0
Flags: Receive-options, Receive-TTL-Exceeded
Addresses, Flags: Is-Preferred Is-Primary
Destination: 4.2.2.2, Local: 4.2.2.1, Broadcast: Unspecified,
Generation: 44
Logical interface cp-5/0/0.16383 (Index 81) (SNMP ifIndex 56) (Generation 31)
...
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. All levels
MTU Maximum Transmit Unit (MTU). Size of the largest packet to be transmitted. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Hardware address Media access control (MAC) address of the interface. detail extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago)
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC Red mechanism.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface All levels
Flags” on page 82.
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface (such as iso or inet6). detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Route table in which this address exists; for example, Route table:0 refers to detail extensive
inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Logical interface mo-4/0/0.0 (Index 83) (SNMP ifIndex 43) (Generation 26)
Flags: Point-To-Point SNMP-Traps Encapsulation: Adaptive-Services
Traffic statistics:
Input bytes : 756781796
Logical interface mo-4/0/0.16383 (Index 84) (SNMP ifIndex 58) (Generation 27)
...
Table 118 on page 607 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot link services, link services IQ, and multilink
services interfaces.
Task Command
Display status information about link services show interfaces (Link Services) on page 608
interfaces.
Display status information about link services IQ show interfaces (Link Services IQ) on page
interfaces. 622
Display status information about redundant link show interfaces (Redundant Link Services
services IQ interfaces. IQ) on page 644
■ 607
JUNOS 9.0 Interfaces Command Reference
Syntax For Multilink Frame Relay user-to-user network-to-network interface (UNI NNI):
Options interface-type—On M-series and T-series routing platforms, the interface type is
ls-fpc/pic/port. On the J-series routing platform, the interface type is ls-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Link-level type Encapsulation being used on the physical interface: Multilink-Frame-Relay-UNI-NNI All levels
(default), LinkService, Frame-relay, Frame-relay-ccc, or Frame-relay-tcc.
MTU Maximum transmission unit size on the physical interface. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago) . For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold time up and hold time down, in milliseconds, in the detail extensive
format Up n ms, Down n ms.
Multilink Frame Multilink Frame Relay UNI NNI only) Configured information about Multilink detail extensive none
Relay UNI NNI Frame Relay bundle options.
bundle options
■ Device type—DCE (Data Communication Equipment) or DTE (Data Terminal
Equipment).
■ MRRU—Configured size of the maximum received reconstructed unit
(MRRU): 1500 to 4500 bytes. The default is 1524 bytes.
■ Fragmentation threshold—Configured fragmentation threshold: 128 through
16,320 bytes, in integer multiples of 64 bytes. The default setting is 0,
which disables fragmentation.
■ Red differential delay limit—Red differential delay limit among bundle links
has been reached, indicating an action will occur.
■ Yellow differential delay limit—Yellow differential delay among bundle links
has been reached, indicating a warning will occur.
■ Red differential delay action—Type of actions taken when the red differential
delay exceeds the red limit: Disable link transmit or Remove link from service.
■ Reassembly drop timer—Drop timeout value to provide a recovery
mechanism if individual links in the link services bundle drop one or more
packets: 1 through 127 milliseconds. By default, the drop timeout
parameter is 0 (disabled). A value that is under 5 ms is not recommended.
■ Links needed to sustain bundle—Minimum number of links to sustain the
bundle: 1 through 8.
■ LIP Hello timer—Link Interleaving Protocol hello timer: 1 through 180
seconds.
■ Acknowledgement timer—Maximum period to wait for an add link
acknowledgement, hello acknowledgement, or remove link
acknowledgement: 1 through 10 seconds.
■ Acknowledgement retries—Number of retransmission attempts to be
made for consecutive hello or remove link messages after the
expiration of the acknowledgement timer: 1 through 5.
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface. All references to traffic direction (input or output) are defined with
respect to the router. Input fragments received by the router are assembled
into input packets; output packets are segmented into output fragments for
transmission out of the router.
Multilink Frame Information about Multilink Frame Relay bundle errors. detail extensive
Relay UNI NNI
■ Packet drops—Number of packets dropped.
bundle errors
■ Fragment drops—Number of fragments dropped.
■ MRRU exceeded—Number of times a packet was dropped because the
configured MRRU value was exceeded.
■ Exception events—Exception events counter.
Multilink Frame Information about Multilink Frame Relay bundles. detail extensive
Relay UNI NNI
■ Fragments—Bundle fragment information.
bundle statistics
■ Input—Total number and rate of frames and packets received, in
Frames, fps (frames per second), Bytes, and bps (bits per second).
■ Output—Total number and rate of frames and packets transmitted,
in Frames, fps, Bytes, and bps.
Multilink Frame ■ Active bundle links—Number of bundle links that are currently active. detail extensive none
Relay UNI NNI ■ Removed bundle links—Number of bundle links that have been removed
bundle links (RED differential delay action).
information
■ Disabled bundle links—Number of bundle links that have been disabled
(RED differential delay action).
Multilink Frame (Multilink Frame Relay UNI NNI only) Display information for each active bundle detail extensive
Relay UNI NNI link.
active bundle links
■ Frames—Number of multilink control frames received on this bundle link.
statistics
■ fps—Rate of multilink control frames received on this bundle link (in
frames per second).
■ Bytes—Number of bytes received on this bundle link.
■ bps—Number of bits per second received on this bundle link.
■ interface-name—Name of the bundle link interface.
■ Input—Total number and rate of frames and packets received.
■ Output—Total number and rate of frames and packets transmitted.
■ Current differential delay—Compare this bundle link's round trip time to
the average of all bundle links' round trip times in ms (milliseconds).
■ Recent high differential delay—Highest differential delay value from the
latest 10 intervals, in milliseconds.
■ Times over red diff delay—Number of times this bundle link exceeded the
configured red differential delay limit.
■ Times over yellow diff delay—Number of times this bundle link exceeded
the configured yellow differential delay limit.
Frame exceptions For Multilink Frame Relay end-to-end only. Information about framing detail extensive
exceptions. Includes events recorded under Exception Events for each logical
interface.
■ Oversized frames—Number of frames received that exceed maximum
frame length. Maximum length is 4500 Kb (kilobits).
■ Errored input frames—Number of input frame errors.
■ Input on disabled link/bundle—Number of frames received on disabled
links. These frames can result either from an inconsistent configuration,
or from a bundle or link being brought up or down with traffic actively
flowing through it.
■ Output for disabled link/bundle—Number of frames sent for a disabled or
unavailable link. These frames can result either from an inconsistent
configuration, or from a bundle being brought up or down while traffic is
flowing through it.
■ Queuing drops—Total number of packets dropped before traffic enters the
link services IQ interface. Indicates that the interface is becoming
oversubscribed.
Buffering exceptions For Multilink Frame Relay end-to-end only. Information about buffering detail extensive
exceptions. Includes events recorded under Exception Events for each logical
interface.
■ Packet data buffer overflow—Packet buffer memory is full. This overflow
can occur when the aggregate data rate exceeds the physical link services
interface capacity.
■ Fragment data buffer overflow—Fragment buffer memory is full. This
overflow can occur when excessive differential delay is experienced across
the links within a single bundle, or when the aggregate data rate exceeds
the physical link services interface capacity. Check the logical interface
exception event counters to determine which bundle is responsible.
Assembly For Multilink Frame Relay end-to-end only. Information about assembly detail extensive
exceptions exceptions. Includes events recorded under Exception Events for each logical
interface.
Assembly ■ Fragment timeout—The drop timer expired while a fragment sequence detail extensive
exceptions number was outstanding. Occurs only if the drop timer is enabled. This
(continued) timeout can occur if the differential delay across the links in a bundle
exceeds the drop-timer setting, or if a multilink packet is lost in transit
while the drop timer is enabled. These events do not necessarily indicate
any problem with the operation of the physical link services interface
itself, but can occur when one or more individual links drop traffic. Check
the logical interface exception event counters to determine which bundle
is responsible.
■ Missing sequence number—A gap was detected in the sequence numbers
of fragments on a bundle. These events do not necessarily indicate any
problem with the operation of the physical link services interface itself,
but can occur when one or more individual links drop traffic. Check the
logical interface exception event counters to determine which bundle is
responsible.
■ Out-of-order sequence number—Two frames with out-of-order sequence
numbers within a single link. This event indicates that an individual link
within a bundle reordered traffic, making the multilink interface unable
to correctly process the resulting stream. Check the logical interface
exception event counters to determine which bundle is responsible.
■ Out-of-range sequence number—Received a frame with an out-of-range
sequence number. These events can occur when a large amount of
multilink-encapsulated traffic is lost or the multilink peer is reset, so that
a large jump in sequence numbers results. A small number of these events
can occur when the far end of a bundle is taken down or brought up.
Check the logical interface exception event counters to determine which
bundle is responsible.
Hardware errors For Multilink Frame Relay end-to-end only. Information about hardware errors. detail extensive
■ Data memory error—A memory error was detected on the interface DRAM.
Indicates possible hardware failure. Contact Juniper Networks technical
support.
■ Control memory error—A memory error was detected on the interface
DRAM. Indicates possible hardware failure. Contact Juniper Networks
technical support.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Bundle options For Multilink Frame Relay end-to-end interfaces only: detail extensive none
■ MRRU—Configured size of the maximum received reconstructed unit
(MRRU): 1500 to 4500 bytes. The default is 1524 bytes.
■ Drop timer period—Drop timeout value to provide a recovery mechanism
if individual links in link services bundle drop one or more packets: 1
through 127 milliseconds. Values under 5 milliseconds are not
recommended. The default setting is 0, which disables the timer.
■ Sequence number format—(MLPPP) Short sequence number header format.
■ Fragmentation threshold—Configured fragmentation threshold: 128 through
16,320 bytes, in integer multiples of 64 bytes. The default setting is 0,
which disables fragmentation.
■ Links needed to sustain bundle—Minimum number of links to sustain the
bundle: 1 through 8.
■ Interleave fragments—State of the process that interleaves long packets
with high-priority ones. Only Disabled is currently supported.
■ Remote MRRU—MRRU value received from remote peer. If negotiation
has not been initiated, the default value is displayed.
Bundle status ■ MRRU exceeded—Number of reassembled packets exceeding the MRRU. detail extensive none
(MLPPP) or This counter is not implemented in this release.
Multilink class ■ Fragment timeout—Drop timer expired while a fragment sequence number
status was outstanding. Occurs only if the drop timer is enabled. This timeout
(MC-MLPPP) can occur if the differential delay across the links in a bundle exceeds the
(continued) drop-timer setting, or if a multilink packet is lost in transit while the drop
timer is enabled.
■ Missing sequence number—Gap detected in the sequence numbers of
fragments on a bundle.
■ Out-of-order sequence number—Two frames with out-of-order sequence
numbers within a single link. This event indicates that an individual link
within a bundle reordered traffic, making the multilink interface unable
to correctly process the resulting stream.
■ Out-of-range sequence number—Frame with an out-of-range sequence
number. These events can occur when a large amount of
multilink-encapsulated traffic is lost or the multilink peer is reset, so that
a large jump in sequence numbers results. A small number of these events
can occur when the far end of a bundle is taken down or brought up.
■ Packet data buffer overflow—Packet buffer memory full. This overflow can
occur when the aggregate data rate exceeds the physical link services IQ
interface capacity.
■ Fragment data buffer overflow—Fragment buffer memory full. This overflow
can occur when excessive differential delay is experienced across the links
within a single bundle, or when the aggregate data rate exceeds the
physical link services IQ capacity.
Statistics Information about fragments and packets received and sent by the router. All detail extensive
references to traffic direction (input or output) are defined with respect to the
router. Input fragments received by the router are assembled into input packets;
output packets are segmented into output fragments for transmission out of
the router.
■ Bundle—Information about bundles.
■ Link—Information about links used in the multilink operation.
Protocol Protocol family configured on the logical interface. detail extensive none
MTU MTU size on the logical interface. If the MTU value is negotiated down to meet detail extensive none
the MRRU requirement on the remote side, this value is marked Adjusted.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which this address exists. For example, Route table:0 refers detail extensive
to inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Output bytes : 0
Input packets: 0
Output packets: 0
Multilink Frame Relay UNI NNI bundle errors:
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Exception events 0
Multilink Frame Relay UNI NNI bundle statistics
Frames fps Bytes bps
Fragments:
Input : 0 0 0 0
Output: 824 0 17304 320
Packets:
Input : 0 0 0 0
Output: 824 0 17304 320
Multilink Frame Relay UNI NNI bundle links info:
Active bundle links 4
Removed bundle links 0
Disabled bundle links 0
Multilink Frame Relay UNI NNI active bundle links statistics:
Frames fps Bytes bps
t1-0/2/0:0.0
Input : 0 0 0 0
Output: 206 0 4326 80
Current differential delay 0.2 ms
Recent high differential delay 3.8 ms
Times over red diff delay 0
Times over yellow diff delay 0
LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
Rcv: 2 2 0 206 207 0 0
Xmt: 2 1 0 207 206 0 0
t1-0/2/0:1.0
Input : 0 0 0 0
Output: 206 0 4326 80
Current differential delay 0.2 ms
Recent high differential delay 3.7 ms
Times over red diff delay 0
Times over yellow diff delay 0
LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
Broadcast: Unspecified,
Generation: 85
Options lsq-fpc/pic/port—Display standard status information about the specified link services
IQ interface.
Additional Information Link services IQ interfaces are similar to link services interfaces. The important
difference is that link services IQ interfaces fully support JUNOS class-of-service (CoS)
components.
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Link-level type Encapsulation being used on the physical interface: Multilink-Frame-Relay-UNI-NNI All levels
(default), LinkService, Frame-relay, Frame-relay-ccc, or Frame-relay-tcc.
MTU Maximum transmission unit size on the physical interface. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago) . For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input rate (Redundant LSQ) Rate of bits and packets received on the interface. None specified
Output rate (Redundant LSQ) Rate of bits and packets transmitted on the interface. None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface. All references to traffic direction (input or output) are defined with
respect to the router. Input fragments received by the router are assembled
into input packets; output packets are segmented into output fragments for
transmission out of the router.
Frame exceptions Information about framing exceptions. Includes events recorded under Exception extensive
Events for each logical interface.
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Buffering exceptions Information about buffering exceptions. Includes events recorded under extensive
Exception Events for each logical interface.
Assembly (Multilink Frame Relay end-to-end only) Information about assembly exceptions. extensive
exceptions Includes events recorded under Exception Events for each logical interface.
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Hardware errors (Multilink Frame Relay end-to-end only) Information about hardware errors. extensive
(sticky)
■ Data memory error—A memory error was detected on the interface DRAM.
Indicates possible hardware failure. Contact Juniper Networks technical
support.
■ Control memory error—A memory error was detected on the interface
DRAM. Indicates possible hardware failure. Contact Juniper Networks
technical support.
Egress queues Total number of egress queues supported on the specified interface. detail extensive none
Queue counters Queue number and its associated user-configured forwarding class name. detail extensive none
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Logical Interface
Logical interface Name of the logical interface All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Bundle options (Multilink Frame Relay end-to-end interfaces only) detail extensive none
■ MRRU—Configured size of the maximum received reconstructed unit
(MRRU): 1500 through 4500 bytes. The default is 1504 bytes.
■ Drop timer period—Drop timeout value to provide a recovery mechanism
if individual links in link services bundle drop one or more packets: 0
though 2000 milliseconds. Values under 5 ms are not recommended.
The default setting is 0, which disables the timer.
■ Sequence number format—Short sequence number header format (MLPPP
only).
■ Fragmentation threshold—Configured fragmentation threshold: 64 through
16,320 bytes, in integer multiples of 64 bytes. The default setting is 0,
which disables fragmentation.
■ Links needed to sustain bundle—Minimum number of links to sustain the
bundle: 1 through 8.
■ Multilink classes—Number of multilink classes negotiated.
■ Link layer overhead—Percentage of bundle bandwidth to be set aside for
link-layer overhead.
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Statistics Information about fragments and packets received and sent by the router. All detail extensive
references to traffic direction (input or output) are defined with respect to the
router. Input fragments received by the router are assembled into input packets;
output packets are segmented into output fragments for transmission out of
the router. Each field has columns that indicate the number of frames received
and transmitted, frames per second (fps), the number of bytes received and
transmitted, and bits per second (bps).
■ Bundle—Information for each active bundle link.
■ Fragments: Input and Output—Total number and rate of fragments
received and transmitted.
■ Packets: Input and Output—Total number and rate of packets received
and transmitted.
■ Multilink class—(MC-MLPPP only) Information about multiclass links
used in the multilink operation.
■ Link—Information about links used in the multilink operation.
■ Link name—Interface name of the link services IQ channel and state
information (physical link up or down).
■ Input and Output—Total number and rate of fragments and packets
received and transmitted.
NCP state (PPP) Network Control Protocol state. detail extensive none
■ Conf-ack-received—Acknowledgement was received.
■ Conf-ack-sent—Acknowledgement was sent.
■ Conf-req-sent—Request was sent.
■ Down—NCP negotiation is incomplete (not yet completed or has failed).
■ Not-configured—NCP is not configured on the interface.
■ Opened—NCP negotiation is successful.
Protocol Protocol family configured on the logical interface. detail extensive none
MTU MTU size on the logical interface. If the MTU value is negotiated down to meet detail extensive none
the MRRU requirement on the remote side, this value is marked Adjusted.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Routing table in which this address exists. For example, Route table:0 refers detail extensive
to inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the addresses configured on the logical interface. Possible detail extensive none
values are described in “Addresses, Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Generation Unique number for use by Juniper Networks technical support. detail extensive
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Encapsulation Encapsulation being used: PPP, Multilink PPP or Multilink-FR. All levels
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago) . For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Bundle links Information about the bundled links. detail extensive none
Iinformation
■ Active bundle links—Number of active links.
■ Removed bundle links—Information about links used in the multilink
operation.
■ Disabled bundle links—Number of disabled links.
Bundle options (Multilink Frame Relay end-to-end interfaces only) detail extensive none
■ MRRU—Configured size of the maximum received reconstructed unit
(MRRU): 1500 through 4500 bytes. The default is 1504 bytes.
■ Drop timer period—Drop timeout value to provide a recovery mechanism
if individual links in link services bundle drop one or more packets: 0
though 2000 milliseconds. Values under 5 ms are not recommended.
The default setting is 0, which disables the timer.
■ Inner PPP Protocol field compression —Inner PPP protocol compression is
enabled or disabled.
■ Sequence number format—Short sequence number header format (MLPPP
only).
■ Fragmentation threshold—Configured fragmentation threshold: 64 through
16,320 bytes, in integer multiples of 64 bytes. The default setting is 0,
which disables fragmentation.
■ Links needed to sustain bundle—Minimum number of links to sustain the
bundle: 1 through 8.
■ Multilink classes—Number of multilink classes negotiated.
■ Link layer overhead—Percentage of bundle bandwidth to be set aside for
link-layer overhead.
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Table 120: Link Services IQ and Redundant Link Services IQ show interfaces Output Fields (continued)
Statistics Information about frames, bytes, and bits per second received and sent by the extensive
router. All references to traffic direction (input or output) are defined with
respect to the router. Each field has columns that indicate the number of frames
received and transmitted, frames per second (fps), the number of bytes received
and transmitted, and bits per second (bps).
■ Bundle—Information for each active bundle link.
■ Multilink: Input and Ouput—Total number and rate of multilink frames,
bytes, and bits per second received and transmitted.
■ Network: Input and Output—Total number of multilink frames, bytes,
and bits per second received and transmitted.
■ Link—Information about links used in the multilink operation.
■ Link name is the interface name of the link services IQ channel and
state information (physical link up or down) and up time.
■ Input and Output—Total number and rate of frames, bytes, and bits
per second received and transmitted.
Multilink detail Frames, bytes, and bits per second received and sent by the bundle. All extensive
statistics references to traffic direction (input or output) are defined with respect to the
router. Each field has columns that indicate the number of frames received
and transmitted, frames per second (fps), the number of bytes received and
transmitted, and bits per second (bps).
■ Bundle—Information for the bundle link.
■ Fragments: Input and Output—Total number and rate of multilink
fragments received and transmitted.
■ Non-fragments: Input and Output—Total number and rate of
nonfragmented multilink frames received and transmitted.
■ LFI: Input and Output—Total number and rate of link fragmented and
interleaved frames and bytes.
Protocol Protocol family configured on the logical interface. detail extensive none
MTU MTU size on the logical interface. If the MTU value is negotiated down to meet detail extensive none
the MRRU requirement on the remote side, this value is marked Adjusted.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Routing table in which this address exists. For example, Route table:0 refers detail extensive
to inet.0.
Addresses, Flags Information about the addresses configured on the logical interface. Possible detail extensive none
values are described in “Addresses, Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
0 be 0 0 0
1 ef 0 0 0
2 af 0 0 0
3 nc 0 0 0
0 be 0 0 0
1 ef 0 0 0
2 af 0 0 0
3 nc 0 0 0
Input : 14096 0 0 0
Output: 0 0 0 0
Link:
ds-1/0/2:1:1.0, Enabled, Physical link is Up
Input : 20972 151 2030595 118080
Output: 16184 116 2048468 118488
ds-1/0/2:1:2.0, Enabled, Physical link is Up
Input : 12747 88 2011168 113552
Output: 16187 118 2048077 119000
Protocol inet, MTU: 1500 [Adjusted], Generation: 14, Route table: 0
Flags: User-MTU, MTU-Protocol-Adjusted
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.1.0/30, Local: 10.0.1.2, Broadcast: Unspecified,
Generation: 18
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive
none
SNMP ifIndex SNMP index number for the physical interface. detail extensive
none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface: Multilink. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second none
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface. All references to traffic direction (input or output) are defined with
respect to the router. Input fragments received by the router are assembled
into input packets; output packets are segmented into output fragments for
transmission out of the router.
Frame exceptions Information about framing exceptions. Includes events recorded under Exception extensive
Events for each logical interface:
Buffering exceptions Information about buffering exceptions. Includes events recorded under extensive
Exception Events for each logical interface.
Assembly Information about assembly exceptions. Includes events recorded under extensive
exceptions Exception Events for each logical interface.
Logical Interface
Logical interface Logical interface name. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive
none
Flags Logical interface flags. Possible values are described in “Logical Interface detail extensive
Flags” on page 82. none
Remote MRRU MRRU value received from remote peer. If negotiation has not been initiated, detail extensive
the default value is displayed. none
Statistics Information about fragments and packets received and sent by the router. All detail extensive
references to traffic direction (input or output) are defined with respect to the
router. Input fragments received by the router are assembled into input packets;
output packets are segmented into output fragments for transmission out of
the router.
■ Bundle—Information about bundles.
■ Link—Information about links used in the multilink operation.
MTU MTU size on the logical interface. If the MTU value is negotiated down to meet detail extensive
the MRRU requirement on the remote side, this value is marked Adjusted. none
Flags Information about the protocol family flags. Possible values are described in detail extensive
“Family Flags” on page 80. none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Route table in which this address exists. For example, Route table:0 refers to detail extensive
inet.0.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive
Flags” on page 79. none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Fragments:
Input : 5 0 450 0
Output: 6 0 499 0
Packets:
Input : 5 0 450 0
Output: 12 0 1202 0
Link:
t1-0/1/0:11.0
Input : 1 0 90 0
Output: 1 0 92 0
t1-0/1/0:12.0
Input : 1 0 90 0
Output: 1 0 92 0
t1-0/1/0:10.0
Input : 1 0 90 0
Output: 1 0 92 0
t1-0/1/0:14.0
Input : 1 0 90 0
Output: 1 0 92 0
t1-0/1/0:13.0
Input : 1 0 90 0
Output: 1 0 92 0
t1-0/1/0:8.0
Input : 0 0 0 0
Output: 0 0 0 0
t1-0/1/0:9.0
Input : 0 0 0 0
Output: 0 0 0 0
Protocol inet, MTU: 1500 [Adjusted], Flags: Generation: 752 Route table: 0
Addresses, Flags: Is-Preferred Is-Primary, MTU-Protocol-Adjusted
Destination: 1.1.2.2, Local: 1.1.2.1, Broadcast: Unspecified,
Generation: 1090
Protocol iso, MTU: 1500 [Adjusted], Flags: Is-Primary,
Generation: 753 Route table: 0
Options rlsqnumber—Redundant link services IQ interface name. The logical interface number
range of values is 0 through 127.
none—Display standard status information about the specified redundant link services
IQ configuration.
0 be 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface rlsq0.0 (Index 72) (SNMP ifIndex 88) (Generation 31)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: Multilink-PPP
Bandwidth: 0
Bundle options:
MRRU 1504
Remote MRRU N/A
Drop timer period 2000
Sequence number format long (24 bits)
Fragmentation threshold 0
Links needed to sustain bundle 1
Multilink classes 0
Link layer overhead 4.0 %
Bundle status:
Received sequence number 0xffffff
Transmit sequence number 0x0
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Fragment timeout 0
Missing sequence number 0
Out-of-order sequence number 0
Out-of-range sequence number 0
Packet data buffer overflow 0
Fragment data buffer overflow 0
Statistics Frames fps Bytes bps
Bundle:
Fragments:
Input : 3 0 255 0
Output: 3 0 264 0
Packets:
Input : 3 0 252 0
Output: 0 0 0 0
Link:
t1-1/3/0:1.0
Input : 3 0 255 0
Output: 0 0 0 0
t1-1/3/0:2.0
Input : 0 0 0 0
Output: 3 0 264 0
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
Protocol inet, MTU: 1500, Generation: 43, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 2.2.2.0/30, Local: 2.2.2.1, Broadcast: Unspecified,
Generation: 45
show interfaces The output for the show interfaces rlsq extensive command is identical to that for
extensive (Redundant the show interfaces rlsq detail command. For sample output, see show interfaces
Link Services IQ) detail (Redundant Link Services IQ) on page 645.
Table 122 on page 649 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot tunnel services interfaces. Commands are listed
in alphabetical order.
Task Command
Display status information about generic routing encapsulation (GRE) show interfaces (GRE) on page 650
interfaces.
Display status information about IP-over-IP interfaces. show interfaces (IP-over-IP) on page 655
Display status information about logical tunnel interfaces. show interfaces (Logical Tunnel) on page 659
Display status information about IP multicast encapsulation and show interfaces (Multicast Tunnel) on page 664
de-encapsulation tunnel interfaces.
Display status information about Protocol Independent Multicast (PIM) show interfaces (PIM) on page 667
de-encapsulation and encapsulation tunnel interfaces.
Display status information about virtual loopback tunnel interfaces. show interfaces (Virtual Loopback
Tunnel) on page 671
■ 649
JUNOS 9.0 Interfaces Command Reference
Options interface-type—On M-series and T-series routing platforms, the interface type is
gr-fpc/pic/port. On the J-series routing platform, the interface type is gr-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Device Flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface Flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
IP-Header IP header of the logical interface. If the tunnel key statement is configured, this All levels
information is included in the IP Header entry.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input rate—Rate of bits and packets received on the interface.
■ Output rate—Rate of bits and packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive none
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. detail extensive none
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
show interfaces The output for the show interfaces extensive command is identical to that for the
extensive (GRE) show interfaces detail command. For sample output, see show interfaces detail
(GRE) on page 653.
Options interface-type—On M-series and T-series routing platforms, the interface type is
ip-fpc/pic/port. On the J-series routing platform, the interface type is ip-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input rate—Rate of bits and packets received on the interface.
■ Output rate—Rate of bits and packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. detail extensive none
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
show interfaces The output for the show interfaces extensive command is identical to that for the
extensive (IP-over-IP) show interfaces detail command. For sample output, see show interfaces detail
(IP-over-iP) on page 658.
Options interface-type—On M-series and T-series routing platforms, the interface type is
lt-fpc/pic/port. On the J-series routing platform, the interface type is lt-pim/0/port.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Type Type of interface. Software-Pseudo indicates a standard software interface with All levels
no associated hardware device.
Clocking Reference clock source: Internal or External when configured. Otherwise, All levels
Unspecified.
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Errors—Sum of the incoming frame aborts and FCS errors.
■ Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
■ Framing errors—Number of packets received with an invalid frame
checksum (FCS).
■ Runts—Number of frames received that are smaller than the runt threshold.
■ Giants—Number of frames received that are larger than the giant threshold.
■ Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually,
this field reports protocols that the JUNOS software does not handle.
■ Resource errors—Sum of transmit drops.
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes—Rate of bytes received on the interface.
■ Output bytes—Rate of bytes transmitted on the interface.
■ Input packets—Rate of packets received on the interface.
■ Output packets—Rate of packets transmitted on the interface.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
Protocol Protocol family configured on the logical interface, such as iso, inet6, mpls. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Route table in which this address exists. For example, Route table:0 refers to detail extensive
inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Logical interface lt-1/0/0.0 (Index 66) (SNMP ifIndex 467) (Generation 3024)
Flags: Point-To-Point SNMP-Traps 16384 DLCI 100 Encapsulation: FR-NLPID
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4470, Generation: 7034, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.1.1/24, Local: 10.1.1.1, Broadcast: Unspecified,
Generation: 2054
Options interface-type—On M-series and T-series routing platforms, the interface type is
mt-fpc/pic/port. On the J-series routing platform, the interface type is
mt-pim/0/port.
Additional Information The multicast tunnel interface has two logical interfaces: encapsulation and
de-encapsulation. These interfaces are automatically created by the JUNOS software
for every multicast-enabled VPN routing and forwarding (VRF) instance. The
encapsulation interface carries multicast traffic traveling from the edge interface to
the core interface. The de-encapsulation interface carries traffic coming from the
core interface to the edge interface.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical All levels
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Options interface-type—On M-series and T-series routing platforms, the PIM de-encapsulation
interface type is pd-fpc/pic/port. On the J-series routing platform, it is
pd-pim/0/port. On M-series and T-series routing platforms, the PIM encapsulation
interface type is pe-fpc/pic/port. On the J-series routing platform, it is
pe-pim/0/port.
Physical Interface
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Table 128: Virtual Loopback Tunnel show interfaces Output Fields (continued)
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Logical Interface
Logical interface Name of the logical interface All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Bandwidth Bandwidth allotted to the logical interface, in kilobytes per second. All levels
Table 128: Virtual Loopback Tunnel show interfaces Output Fields (continued)
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes—Number of bytes received on the interface.
■ Output bytes—Number of bytes transmitted on the interface.
■ Input packets—Number of packets received on the interface.
■ Output packets—Number of packets transmitted on the interface.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is received, detail extensive
the value in the output packet rate field might briefly exceed the peak cell rate.
It takes awhile (generally, less than 1 second) for this counter to stabilize.
protocol-family Protocol family configured on the logical interface. Possible values are described brief
in “Family Flags” on page 80.
Protocol Protocol family configured on the logical interface. Possible values are described detail extensive none
in “Family Flags” on page 80.
MTU Maximum transmission unit size on the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about protocol family flags. Possible values are described in “Family detail extensive none
Flags” on page 80.
Speed: 800mbps
Device flags : Present Running
Logical interface vt-1/2/0.0 (Index 76) (SNMP ifIndex 57) (Generation 17)
Flags: Point-To-Point 16384 Encapsulation: Virtual-loopback-tunnel
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: Unlimited, Generation: 33, Route table: 0
Flags: None
Protocol mpls, MTU: Unlimited, Generation: 34, Route table: 0
Flags: None
Logical interface vt-1/2/0.0 (Index 76) (SNMP ifIndex 57) (Generation 17)
Flags: Point-To-Point 16384 Encapsulation: Virtual-loopback-tunnel
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Table 129 on page 677 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot the Avaya TGM550 VoIP module on J2320,
J2350, J4350, and J6350 Services Routers. You can also monitor the Telephony
Interfaces Modules (TIMs) to a limited extent. Commands are listed in alphabetical
order.
Task Command
Remove the Media Gateway Controller (MGC) list clear tgm fpc on page 678
configured on the TGM550 module.
Provide a method for user authentication on the request tgm login fpc on page 679
TGM550 modules.
Configure the MGC list on the TGM550 module. set tgm fpc on page 680
Display information about TGM550 module show tgm fpc on page 689
connectivity and digital signal processor (DSP)
capacity.
Display online and offline status of Avaya VoIP show tgm telephony-interface-module
Telephony Interface Modules (TIMs). status on page 690
■ 677
JUNOS 9.0 Interfaces Command Reference
Options slot-number—FPC slot number in which the TGM550 VoIP module is installed.
Options slot-number—Number of the slot in which the TGM550 VoIP module is installed.
request tgm login fpc user@host> request tgm login fpc 2 user jnpr
Options slot-number—Number of the slot in which the TGM550 VoIP module is installed.
set tgm fpc user@host> set tgm fpc 2 media-gateway-controller [173.26.232.77 10.10.10.30
10.10.10.40]
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Link-level type Encapsulation being used on the physical interface—VP-AV. All levels
Speed Speed in megabits per second (mbps) at which the interface is running. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Link type Physical interface link type: Full-Duplex or Half-Duplex. detail extensive none
Link flags Information about the link. Possible values are described in “Link All levels
Flags” on page 81.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None specified
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone from down to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
up, or another problem occurs. If the number of carrier transitions
increments quickly, increasing only when the cable is unplugged, the
far-end system is powered down and then up, or another problem occurs.
If it increments quickly (perhaps once every 10 seconds), the cable, the
far-end system, or the PIC or PIM is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue. The default
is 25 percent.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue. The default
is 25 percent.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is configured
in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible values
are none and exact:
■ exact—The queue transmits only up to the configured bandwidth,
even if excess bandwidth is available.
■ none—The queue transmits beyond the configured bandwidth if
bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Protocol Protocol family configured on the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface vp-2/0/0.0 (Index 73) (SNMP ifIndex 47) (Generation 142)
Flags: Point-To-Point SNMP-Traps Encapsulation: VP-AV
Protocol inet, MTU: 1500, Generation: 147, Route table: 0
Flags: None
Filters: Input: pcap, Output: pcap
Addresses, Flags: Is-Preferred Is-Primary
Destination: 31.31.31.20, Local: 33.33.33.1, Broadcast: Unspecified,
Generation: 154
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Logical interface vp-2/0/0.0 (Index 73) (SNMP ifIndex 47) (Generation 142)
Flags: Point-To-Point SNMP-Traps Encapsulation: VP-AV
Protocol inet, MTU: 1500, Generation: 147, Route table: 0
Flags: None
Filters: Input: pcap, Output: pcap
Addresses, Flags: Is-Preferred Is-Primary
Destination: 31.31.31.20, Local: 33.33.33.1, Broadcast: Unspecified,
Generation: 154
Reported bearer If dynamic CAC is configured on more than one active interface, the TGM550 VoIP module reports
bandwidth limit the bearer bandwidth limit (BBL) of the active interface with the highest activation priority.
If more than one active interface has the same activation priority, the BBL is reported as the number
of those interfaces times their lowest BBL. For example if two interfaces with the same activation
priority have BBLs of 2000 Kbps and 1500 Kbps, the reported BBL is 3000 Kbps (2 x 1500 Kbps).
The operational state is the physical state of the interface. If the interface is physically operational,
even if it is not configured, the operational state is Up. An operational state of Down indicates a
problem with the physical interface.
Bearer bandwidth limit Maximum bandwidth available for voice traffic on the interface.
(Kbps)
Options slot-number—Number of the slot in which the TGM550 VoIP module is installed.
Media gateway controller(s) Displays the IP addresses of the Media Gateway Controllers (MGCs)
configured in the MGC list for the TGM550 VoIP module.
The first MGC in the list is the primary MGC. The TGM550 VoIP
module searches for the primary MGC first. If it cannot connect to
the primary MGC or loses its connection to the primary MGC, it
attempts to connect to the next MGC in the list, and so on.
DSP Capacity Displays the DSP capacity of the TGM VoIP module board in terms
of the number of voice channels supported.
Table 134 on page 693 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot the discard (dsc) interface.
Task Command
The discard interface is not a physical interface, but a virtual interface that discards
packets. You can configure one discard interface. The discard interface allows you
to identify the ingress point of a denial-of-service (DoS) attack. When your network
is under attack, the target host IP address is identified, and the local policy forwards
attacking packets to the discard interface. Traffic routed out of the discard interface
is silently discarded.
If an output filter is attached to the interface, the action specified by the filter causes
the packets to be logged or counted before the traffic is discarded. For a complete
discussion about using the discard interface to protect your network against DoS
attacks, see the JUNOS Policy Framework Configuration Guide.
Statistics and media displayed by the show interfaces command are not relevant for
the discard interface and always show values of 0.
■ 693
JUNOS 9.0 Interfaces Command Reference
media—This option is not relevant for the discard interface and always shows a value
of 0.
statistics—This option is not relevant for the discard interface and always shows a
value of 0.
Physical Interface
Physical interface Name of the physical interface, whether the interface is enabled, and the state All levels
of the physical interface: Up or Down.
Interface index Physical interface's index number, which reflects its initialization sequence. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Type Type of interface. Software-Pseudo indicates a standard software interface with All levels
no associated hardware device.
Link-level type Encapsulation being used on the physical interface. All levels
Clocking Reference clock source. It can be Internal or External. brief detail extensive
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link type Encapsulation being used on the physical interface. detail extensive
Link flags Information about the link. Possible values are described in “Link detail extensive
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Current address, Configured MAC address and hardware MAC address. detail extensive
Hardware address
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Output errors (Extensive only) Output errors on the interface. The following paragraphs detail extensive
explain the counters whose meaning might not be obvious:
■ Carrier transitions—Number of times the interface has gone fromdown to
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
■ Errors—Sum of the outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet that is dropped by the ASIC's RED mechanism.
■ MTU errors—Number of packets whose size exceeded the MTU of the
interface.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive
SNMP ifIndex Logical interface SNMP interface index number. detail extensive
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface. Possible values are described in “Logical All levels
Interface Flags” on page 82.
Protocol Protocol family configured on the logical interface, such as iso, inet6, or mpls. All levels
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Routing table in which the logical interface address is located. For example, 0 detail extensive
refers to the routing table inet.0.
Table 136 on page 699 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot the local loopback interface (lo0).
Task Command
The JUNOS software automatically configures one local loopback interface (lo0),
choosing the first interface to come online as the default. You can also configure the
loopback interface and one or more addresses on the interface. If you configure the
loopback interface, it is automatically used for unnumbered interfaces.
A local loopback loops packets, including both data and timing information, back on
the local Physical Interface Card (PIC) or Physical Interface Module (PIM). When you
configure a local loopback, the interface transmits packets to the channel services
unit (CSU) built into the interface. These packets are transmitted onto the circuit
toward the far-end device. The PIC or PIM receives back its own transmission and
ignores any data sent from the physical circuit and the CSU.
To test a local loopback, issue the show interfaces interface-name command. If PPP
keepalives transmitted on the interface are received by the PIC or PIM, the
Device Flags field contains the output Loop-Detected.
For more information about using the loopback interface to monitor and troubleshoot
various interface types, see the JUNOS Interfaces Network Operations Guide.
■ 699
JUNOS 9.0 Interfaces Command Reference
NOTE: Logical interface lo0.16385 is the loopback interface for the internal routing
instance. Created by the internal routing service process, this interface facilitates
internal traffic. It prevents any filter created on loopback lo0.0 from blocking internal
traffic.
Options lo0—Display standard status information about the local loopback interface.
Physical Interface
Physical Interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link detail extensive none
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Hardware address Media access control (MAC) address of the interface. detail extensive
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive
SNMP ifIndex Logical interface SNMP interface index number. detail extensive
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface brief detail extensive
Flags” on page 82.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Local statistics Statistics for traffic received from and transmitted to the Routing Engine. When detail extensive
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
Protocol Protocol family configured on the logical interface (such as iso or inet6). detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Route table in which this address exists; for example, Route table:0 refers to detail extensive
inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about the address flags. Possible values are described in “Addresses, detail extensive
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Addresses
Local: 127.0.0.1
Protocol iso, MTU: Unlimited
Flags: None
Addresses, Flags: Is-Default Is-Primary
Local: 49.0004.1000.0000.0001
Input packets: 0
Output packets: 0
Table 138 on page 707 summarizes the command-line interface (CLI) commands you
can use to monitor and troubleshoot the management Ethernet interface and, in the
case of M-series and T-series routing platforms, the internal Ethernet interface.
Table 138: Management Ethernet and Internal Ethernet Interface Operational Mode Commands
Task Command
Monitor the M-series and T-series management Ethernet and show interfaces (M-series and T-series Management and
internal Ethernet interfaces. Internal Ethernet) on page 708
Monitor the J-series management Ethernet interface. show interfaces (J-series Management Ethernet) on page 716
On the M-series and T-series routing platforms, the JUNOS software automatically
creates the routing platform's management Ethernet interface, fxp0, which is an
out-of-band management interface for connecting to the router, and the internal
Ethernet interface, fxp1, which connects the Routing Engine to the Packet Forwarding
Engine. If the platform has redundant Routing Engines, another internal Ethernet
interface, fxp2, is created to connect the second Routing Engine (re1) to the Packet
Forwarding Engine.
On the J-series routing platform, the JUNOS software automatically creates the routing
platform's management Ethernet interface, fe-0/0/0, which is an out-of-band
management interface for connecting to the router.
■ 707
JUNOS 9.0 Interfaces Command Reference
Options fxp(0 | 1)—Display standard information about the management Ethernet or internal
Ethernet interface, respectively.
708 ■ show interfaces (M-series and T-series Management and Internal Ethernet)
Chapter 27: Management Ethernet and Internal Ethernet Interface Operational Mode Commands
Table 139: M-series and T-series Management and Internal Ethernet show interfaces Output Fields
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled Field” on page All levels
78
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. All levels
MTU Maximum transmission unit (MTU)—Size of the largest packet to be transmitted. All levels
Device flags Information about the physical device. Possible values are described in “Device All levels
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface All levels
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link detail extensive
Flags” on page 81.
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Hardware address Media access control (MAC) address of the interface. detail extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input packets Number of packets received on the physical interface. None specified
Output packets Number of packets transmitted on the physical interface. None specified
show interfaces (M-series and T-series Management and Internal Ethernet) ■ 709
JUNOS 9.0 Interfaces Command Reference
Table 139: M-series and T-series Management and Internal Ethernet show interfaces Output Fields (continued)
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the logical detail extensive
and physical interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ Resource errors—Sum of transmit drops.
Logical Interface
Logical interface Name of the logical interface All levels
Index Logical interface index number, which reflects its initialization sequence. detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface All levels
Flags” on page 82.
710 ■ show interfaces (M-series and T-series Management and Internal Ethernet)
Chapter 27: Management Ethernet and Internal Ethernet Interface Operational Mode Commands
Table 139: M-series and T-series Management and Internal Ethernet show interfaces Output Fields (continued)
Protocol Protocol family configured on the logical interface (such as iso or inet6). detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route table Route table in which this address exists. For example, Route table:0 refers to detail extensive
inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive none
“Family Flags” on page 80.
Addresses, Flags Information about address flags. Possible values are described in “Addresses, detail extensive none
Flags” on page 79.
Destination IP address of the remote side of the connection. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
show interfaces (M-series and T-series Management and Internal Ethernet) ■ 711
JUNOS 9.0 Interfaces Command Reference
712 ■ show interfaces (M-series and T-series Management and Internal Ethernet)
Chapter 27: Management Ethernet and Internal Ethernet Interface Operational Mode Commands
show interfaces (M-series and T-series Management and Internal Ethernet) ■ 713
JUNOS 9.0 Interfaces Command Reference
714 ■ show interfaces (M-series and T-series Management and Internal Ethernet)
Chapter 27: Management Ethernet and Internal Ethernet Interface Operational Mode Commands
show interfaces (M-series and T-series Management and Internal Ethernet) ■ 715
JUNOS 9.0 Interfaces Command Reference
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in “Enabled All levels
Field” on page 78.
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive
Table 140: J-series Management Ethernet show interfaces Output Fields (continued)
SNMP ifIndex SNMP index number for the physical interface. detail extensive
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation type used on the physical interface. brief detail extensive
MTU Maximum transmission unit (MTU). Size of the largest packet to be transmitted. brief detail extensive
Loopback Whether loopback is enabled and the type of loopback (either local or remote). brief detail extensive
Flow control Whether flow control is enabled or disabled. brief detail extensive
Device flags Information about the physical device. Possible values are described in “Device brief detail extensive
Flags” on page 79.
Interface flags Information about the interface. Possible values are described in “Interface brief detail extensive
Flags” on page 80.
Link flags Information about the link. Possible values are described in “Link brief detail extensive
Flags” on page 81.
CoS queues Number of CoS queues supported on this interface. detail extensive
Hold-times Current interface hold-time up and hold-time down. Value is in milliseconds. detail extensive
Hardware address Media access control (MAC) address of the interface. detail extensive
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Table 140: J-series Management Ethernet show interfaces Output Fields (continued)
Output errors ■ Carrier transitions—Number of times the interface has gone from down to extensive
up. This number does not normally increment quickly, increasing only
when the cable is unplugged, the far-end system is powered down and
then up, or another problem occurs. If the number of carrier transitions
increments quickly, possibly once every 10 seconds, the cable, the remote
system, or the interface is malfunctioning.
■ Errors—Sum of outgoing frame aborts and FCS errors.
■ Drops—Number of packets dropped by the output queue of the I/O
Manager ASIC. If the interface is saturated, this number increments once
for every packet dropped by the ASIC RED mechanism.
■ Collisions—Number of Ethernet collisions.
■ Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or
possibly malfunctioning hardware.
■ HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
■ FIFO errors—Number of FIFO errors in the receive direction as reported
by the ASIC on the PIM. If this value is ever nonzero, the PIM is probably
malfunctioning.
■ MTU errors—Number of packets larger than the MTU threshold.
■ Resource errors—Sum of transmit drops.
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
■ Queued packets—Number of queued packets.
■ Transmitted packets—Number of transmitted packets.
■ Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
Table 140: J-series Management Ethernet show interfaces Output Fields (continued)
Active alarms and Ethernet-specific defects that can prevent the interface from passing packets. detail extensive
Active defects When a defect persists for a certain period, it is promoted to an alarm. Based
on the router configuration, an alarm can ring the red or yellow alarm bell on
the router, or turn on the red or yellow alarm LED on the craft interface. These
fields can contain the value None or Link.
■ None—There are no active defects or alarms.
■ Link—Interface has lost its link state, which usually means that the cable
is unplugged, the far-end system has been turned off, or the PIM is
malfunctioning.
MAC statistics Statistics reported by the PIM's MAC subsystem, including the following: extensive
■ Total octets and total packets —Total number of sent and received octets
and packets.
■ Unicast, broadcast, and multicast packets—Number of unicast, broadcast,
and multicast packets.
■ CRC/Align errors—Total number of packets received that had a length
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, but had either a bad FCS with an integral number of
octets (FCS error) or a bad FCS with a nonintegral number of octets
(alignment error).
■ FIFO errors—Number of FIFO errors that are reported by the ASIC on the
PIM. If this value is ever nonzero, the PIC is probably malfunctioning.
■ MAC control frames—Number of MAC control frames.
■ MAC pause frames—Number of MAC control frames with pause operational
code.
■ Oversized frames—Number of frames that exceed the MTU.
■ Jabber frames—Number of packets received that were longer than 1518
octets (excluding framing bits, but including FCS octets), and had either
an FCS error or an alignment error. This definition of jabber is different
from the definition in IEEE-802.3 section 8.2.1.5 (10Base5) and section
10.3.1.4 (10Base2). These documents define jabber as the condition in
which any packet exceeds 20 ms. The allowed range to detect jabber is
between 20 ms and 150 ms.
■ Fragment frames—Total number of packets received that were less than
64 octets (excluding framing bits, but including FCS octets), and had either
an FCS error or an alignment error. Fragment frames normally increment
because both runts (which are normal occurrences caused by collisions)
and noise hits are counted.
■ VLAN tagged frames—Number of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is
tagged or not.
■ Code violations—Number of times an event caused the PHY to indicate
“Data reception error”or “invalid data symbol error”.
Table 140: J-series Management Ethernet show interfaces Output Fields (continued)
Filter statistics Statistics reported by the PIM's MAC address filter subsystem. The filtering is extensive
done by the content-addressable memory (CAM) on the PIM. The filter examines
a packet's source and destination MAC addresses to determine whether the
packet should enter the system or be rejected.
■ Input packet count—Number of packets received from the MAC hardware
that the filter processed.
■ Input packet rejects—Number of packets that the filter rejected because
of either the source MAC address or the destination MAC address.
■ Input DA rejects—Number of packets that the filter rejected because the
destination MAC address of the packet is not on the accept list. It is normal
for this value to increment. When it increments very quickly and no traffic
is entering the router from the far-end system, either a bad ARP entry
exists on the far-end system, or multicast routing is not on and the far-end
system is sending many multicast packets to the local router (which the
router is rejecting).
■ Input SA rejects—Number of packets that the filter rejected because the
source MAC address of the packet is not on the accept list. The value in
this field should increment only if source MAC address filtering has been
enabled. If filtering is enabled, if the value increments quickly, and if the
system is not receiving traffic that it should from the far-end system, it
means that the user-configured source MAC addresses for this interface
are incorrect.
■ Output packet count—Number of packets that the filter has given to the
MAC hardware.
■ Output packet pad count—Number of packets the filter padded to the
minimum Ethernet size (60 bytes) before giving the packet to the MAC
hardware. Usually, padding is done only on small ARP packets, but some
very small IP packets can also require padding. If this value increments
rapidly, either the system is trying to find an ARP entry for a far-end
system that does not exist or it is misconfigured.
■ Output packet error count—Number of packets with an indicated error that
the filter was given to transmit. These packets are usually aged packets
or are the result of a bandwidth problem. On a normal system, the value
of this field should not increment.
■ CAM destination filters, CAM source filters—Number of entries in the CAM
dedicated to destination and source MAC address filters. There can only
be up to 64 source entries. If source filtering is disabled, which is the
default, the values for these fields should be 0.
Table 140: J-series Management Ethernet show interfaces Output Fields (continued)
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine configuration
■ Destination slot—FPC slot number.
■ CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
■ bandwidth %—Percentage of bandwidth allocated to the queue.
■ Bandwidth bps—Bandwidth allocated to the queue (in bps).
■ buffer %—Percentage of buffer space allocated to the queue.
■ Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is
configured in terms of time.
■ Priority—Queue priority: low or high.
■ Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Logical interface index number, which reflects its initialization sequence. All levels
SNMP ifIndex Logical interface SNMP interface index number. All levels
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Flags Information about the logical interface; values are described in “Logical Interface brief detail extensive
Flags” on page 82.
Table 140: J-series Management Ethernet show interfaces Output Fields (continued)
Traffic statistics Total number of bytes and packets received and transmitted on the logical extensive
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might
briefly exceed the peak cell rate. It takes awhile (generally, less than 1 second)
for this counter to stabilize.
■ Input bytes, Output bytes—Number of bytes received and transmitted on
the interface.
■ Input packets, Output packets—Number of packets received and transmitted
on the interface.
Protocol Protocol family configured on the logical interface (such as iso or inet6). All levels
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Route Table Route table in which this address exists. for example, Route table:0 refers to All levels
inet.0.
Flags Information about the protocol family flags. Possible values are described in detail extensive
“Family Flags” on page 80.
Addresses, Flags Information about address flags. Possible values are described in “Addresses, detail extensive
Flags” on page 79.
Generation Unique number for use by Juniper Networks technical support only. detail extensive
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
4 be-class 0 0 0
5 ef-class 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
4 be-class 0 0 0
5 ef-class 0 0 0
Index ■ 727
JUNOS 9.0 Interfaces Command Reference
728 ■ Index
Index
at- interface............................................................10, 13
described........................................................10, 13
Symbols See also ATM interfaces
! See also ATM-over-ADSL interfaces
in interface names..................................................5 See also ATM-over-SHDSL interfaces
#, comments in configuration statements.................xviii ATM interfaces
( ), in syntax descriptions..........................................xviii status information, displaying.............................368
* ATM-over-ADSL interfaces
in interface names..................................................5 status information, displaying.............................400
10-Gigabit Ethernet interfaces ATM-over-SHDSL interfaces
DWDM status information, displaying.............................408
data and alarms, displaying.........................145 Automatic Protection Switching See APS
status information, displaying.....................135, 137
< >, in syntax descriptions......................................xviii
[] B
in interface names..................................................5 B-channel interface See ISDN
[ ], in configuration statements..................................xviii Basic Rate Interface See ISDN
{ }, in configuration statements................................xviii bc- interface.................................................................13
| (pipe), in syntax descriptions...................................xviii described..............................................................13
See also ISDN
br- interface.................................................................13
A described..............................................................13
adaptive services interfaces.......................................573 See also ISDN
status information, displaying.............................573 braces, in configuration statements...........................xviii
Addresses, flags field, content......................................79 brackets
ADSL angle, in syntax descriptions..............................xviii
ATM-over-ADSL interfaces square, in configuration statements...................xviii
status information, displaying......................400
aenumber interface................................................10, 12
described........................................................10, 12 C
See also aggregated Ethernet interfaces cau4- interface.............................................................10
aggregated Ethernet interfaces described..............................................................10
status information, displaying...............................95 See also channelized OC12 IQ and channelized
aggregated SONET/SDH interfaces STM1 IQ interfaces
status information, displaying.............................320 ce1- interface...............................................................10
APS described..............................................................10
real-time information, displaying........................316 See also channelized E1 IQ interfaces
asnumber interface......................................................10 channelized AU-4 IQ interfaces See channelized STM1
described..............................................................10 IQ interfaces and channelized OC12 IQ interfaces
See also aggregated SONET/SDH interfaces channelized DS3-to-DS0 interfaces
asymmetric digital subscriber line See ADSL status information, displaying.............................538
Asynchronous Transfer Mode See ATM channelized DS3-to-DS1 interfaces
status information, displaying.............................549
channelized E1 interfaces
status information, displaying.............................472
Index ■ 729
JUNOS 9.0 Interfaces Command Reference
730 ■ Index
Index
Index ■ 731
JUNOS 9.0 Interfaces Command Reference
732 ■ Index
Index
Index ■ 733
JUNOS 9.0 Interfaces Command Reference
show interfaces (Channelized OC3 IQ) command......488 show interfaces demux0 (Demux Interfaces)
show interfaces (Channelized STM1 IQ) command...............................................................252
command...............................................................532 show interfaces descriptions command.......................25
show interfaces (Channelized STM1) command.........518 show interfaces destination-class command................26
show interfaces (Channelized T1 IQ) command.........552 show interfaces detail command..................................28
show interfaces (Channelized T3 IQ) command.........564 show interfaces diagnostics optics (10-Gigabit Ethernet)
show interfaces (discard) command...........................694 command...............................................................145
show interfaces (Dynamic Flow Capture) show interfaces diagnostics optics (SONET)
command...............................................................592 command...............................................................354
show interfaces (Encryption) command.....................584 show interfaces extensive command...........................30
show interfaces (Fast Ethernet) command.................104 show interfaces filters command.................................33
show interfaces (Flow Collector) command................596 show interfaces interface-set command.....................135
show interfaces (Flow Monitoring) command............602 show interfaces interface-set queue command..........137
show interfaces (Gigabit Ethernet) command.............120 show interfaces interval command..............................35
show interfaces (GRE) command...............................650 show interfaces irb command....................................162
show interfaces (IP-over-IP) command.......................655 show interfaces mac-database (Gigabit Ethernet)
show interfaces (ISDN B-channel) command..............435 command...............................................................168
show interfaces (ISDN BRI) command........................441 show interfaces media command................................37
show interfaces (ISDN D-channel) command.............445 show interfaces queue command.................................41
show interfaces (ISDN dialer) command....................451 show interfaces redundancy command......................582
show interfaces (J-series Management Ethernet) show interfaces routing command...............................63
command...............................................................716 show interfaces routing summary command...............66
show interfaces (Link Services IQ) command.............622 show interfaces snmp-index command........................68
show interfaces (Link Services) command..................608 show interfaces source-class command.......................69
show interfaces (Logical Tunnel) command...............659 show interfaces statistics command.............................71
show interfaces (Loopback) command.......................700 show interfaces terse command..................................74
show interfaces (M-series and T-series Management show isdn calls command..........................................460
and Internal Ethernet) command...........................708 show isdn history command......................................461
show interfaces (Multicast Tunnel) command............664 show isdn q921 statistics command..........................462
show interfaces (Multilink Services) command...........636 show isdn q931 statistics command..........................464
show interfaces (PIM) command................................667 show isdn status command........................................467
show interfaces (PPPoE) command............................281 show lacp interfaces command..................................171
show interfaces (Redundant Adaptive Services) show oam ethernet connectivity-fault-management
command...............................................................580 forwarding-state command....................................180
show interfaces (Redundant Link Services IQ) show oam ethernet connectivity-fault-management
command...............................................................644 interfaces command...............................................184
show interfaces (Serial) command.............................300 show oam ethernet connectivity-fault-management
show interfaces (SONET/SDH) command...................327 linktrace path-database command..........................192
show interfaces (T1 or E1) command.........................214 show oam ethernet connectivity-fault-management
show interfaces (T3 or E3) command.........................231 mep-database command........................................188
show interfaces (Virtual Loopback Tunnel) show oam ethernet connectivity-fault-management
command...............................................................671 path-database command........................................194
show interfaces brief command...................................23 show oam ethernet link-fault-management
show interfaces controller (Channelized E1 IQ) command...............................................................175
command...............................................................486 show ppp address-pool command..............................263
show interfaces controller (Channelized OC12 IQ) show ppp interface command....................................265
command...............................................................515 show ppp statistics command....................................271
show interfaces controller (Channelized OC3 IQ) show ppp summary command..................................275
command...............................................................514 show pppoe interfaces command..............................291
show interfaces controller (Channelized STM1 IQ) show pppoe statistics command................................294
command...............................................................535 show pppoe version command..................................296
show interfaces controller (Channelized T1 IQ) show tgm dynamic-call-admission-control
command...............................................................566 command...............................................................688
show interfaces controller (Channelized T3 IQ) show tgm fpc command............................................689
command...............................................................567 dsp-capacity........................................................689
734 ■ Index
Index
T
T-series physical interfaces.............................................9
T-series services interfaces...........................................14
T1 interfaces
status information, displaying.............................214
t1- interface.................................................................12
See also channelized DS3-to-DS1 interfaces
See also channelized T3 IQ interfaces
T3 interfaces
status information, displaying.............................231
t3- interface.................................................................12
See also channelized T3 IQ interfaces
tap interface...................................................................9
described................................................................9
See also nonconfigurable interfaces
technical support
contacting JTAC...................................................xxv
TGM550 module
CAC information, displaying...............................688
FPCs, displaying..................................................689
interfaces, displaying..........................................681
MGC list, configuring...................................679, 680
MGC, list, clearing...............................................678
TIM status, displaying.........................................690
Index ■ 735
JUNOS 9.0 Interfaces Command Reference
736 ■ Index
Index of Commands and Statements
show interfaces (Aggregated SONET/SDH)
command...............................................................320
Symbols show interfaces (ATM) command...............................368
show interfaces (ATM-over-ADSL) command.............400
show interfaces (ATM-over-SHDSL) command...........408
C show interfaces (Channelized DS3-to-DS0)
clear ilmi statistics command.....................................418 command...............................................................538
clear interfaces interface-set statistics show interfaces (Channelized DS3-to-DS1)
command...........................................................22, 91 command...............................................................549
clear interfaces interval command...............................19 show interfaces (Channelized E1 IQ) command.........482
clear interfaces mac-database command.....................89 show interfaces (Channelized E1) command..............472
clear interfaces mac-database statistics command.......90 show interfaces (Channelized OC12 IQ)
clear interfaces statistics command.............................21 command...............................................................510
clear isdn q921 statistics command...........................427 show interfaces (Channelized OC12) command.........506
clear isdn q931 statistics command...........................428 show interfaces (Channelized OC3 IQ) command......488
clear oam ethernet connectivity-fault-management show interfaces (Channelized STM1 IQ)
linktrace path-database command............................92 command...............................................................532
clear oam ethernet link-fault-management state show interfaces (Channelized STM1) command.........518
command.................................................................93 show interfaces (Channelized T1 IQ) command.........552
clear oam ethernet link-fault-management statistics show interfaces (Channelized T3 IQ) command.........564
command.................................................................94 show interfaces (discard) command...........................694
clear ppp statistics command.....................................262 show interfaces (Dynamic Flow Capture)
clear pppoe sessions command.................................279 command...............................................................592
clear pppoe statistics command.................................280 show interfaces (Encryption) command.....................584
clear tgm fpc command.............................................678 show interfaces (Fast Ethernet) command.................104
clear vrrp command...................................................200 show interfaces (Flow Collector) command................596
show interfaces (Flow Monitoring) command............602
show interfaces (Gigabit Ethernet) command.............120
R show interfaces (GRE) command...............................650
request interface (revert | switchover) command.......572 show interfaces (IP-over-IP) command.......................655
request tgm login fpc command................................679 show interfaces (ISDN B-channel) command..............435
show interfaces (ISDN BRI) command........................441
show interfaces (ISDN D-channel) command.............445
S show interfaces (ISDN dialer) command....................451
set tgm fpc command................................................680 show interfaces (J-series Management Ethernet)
show aps command...................................................316 command...............................................................716
show dialer defaults command..................................429 show interfaces (Link Services IQ) command.............622
show dialer interfaces command...............................431 show interfaces (Link Services) command..................608
show dialer pools command......................................433 show interfaces (Logical Tunnel) command...............659
show ilmi command..................................................419 show interfaces (Loopback) command.......................700
show ilmi statistics command....................................420 show interfaces (M-series and T-series Management
show interfaces and Internal Ethernet) command...........................708
TGM550 module.................................................681 show interfaces (Multicast Tunnel) command............664
show interfaces (10-Gigabit Ethernet) command........126 show interfaces (Multilink Services) command...........636
show interfaces (Adaptive Services) command..........573 show interfaces (PIM) command................................667
show interfaces (Aggregated Ethernet) command........95 show interfaces (PPPoE) command............................281